[
http://jira.codehaus.org/browse/MSITE-30?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=147488#action_147488
]
Dennis Lundberg commented on MSITE-30:
--------------------------------------
We are talking about a major version upgrade here and all features from a
previous version may not there in the new version, especially if it is a major
rewrite as it is in this case.
In my book the definition of a bug is:
"A feature that is designed to be in the software. When that feature does not
work as designed it's a bug."
That's the reason for me to change the type for this issue.
> site:deploy incompatibilities with m1.02
> ----------------------------------------
>
> Key: MSITE-30
> URL: http://jira.codehaus.org/browse/MSITE-30
> Project: Maven 2.x Site Plugin
> Issue Type: Improvement
> Components: site:deploy
> Environment: All
> Reporter: Paul Spencer
> Fix For: 2.0-beta-8
>
>
> 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
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
