[MSITE-30] site:deploy incompatibilities with m1.02

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Component/s: site:deploy
• Environment: All
• Assignee: Lukas Theussl
• Reporter: Paul Spencer
• Created: 19/Nov/05 07:07
• Updated: 06/Jan/16 20:03
• Resolved: 29/Jul/09 09:28

Description

Deploying a site in m2 has changed since m1.
1) m1 used the "tar" and "gunzip" command on the remote site, where m2 uses the "unzip" command. This poses a problem for be since my remote site does not support the "unzip" command, thus making the "priority" of this issue major

1.1) Their may be desire to deploy without the use of tools like tar and zip on some site. The deploy would esentailly be a recersive copy

2) No equivelent to m1 property maven.site.chmod.mode. I use this to allow other member is the group update and delete permission

3) No equivelent to m1 property maven.site.publish.clean

Their are other properties for the m1.02 not mentioned above, but I suspect the they can be calculated from m2 files, i.e. pom.xml and settings.xml.

Paul Spencer

Issue Links

• is related to: MSITE-330 Wagon nukes the permission bits of uploaded files.
• is related to: MSITE-339 site:deploy fails on HP-UX due to invalid chmod option
• is related to: MSITE-380 Chmod following scp transfer performs poorly as time goes on
• is superceded by: MSITE-141 Possible security hole when deploying site
• is superceded by: MSITE-250 Allow cleaning of the remote area or staging site
• is superceded by: MSITE-213 site:deploy to support tar gzip