[ 
http://jira.codehaus.org/browse/MSITE-132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103350
 ] 

John Allen commented on MSITE-132:
----------------------------------

Jorg,

The logic of stage is fairly obvious. one is simulating the real world 
deployment, where projects and modules from the internet namespace are mapped 
to residing within a root node of a filesystem. Your expectation regarding what 
the site:stage plugin should do and how it should do it is wrong. Adjust your 
expectation and you will be happier.


> Use <artefactID> instead of <name> for directories
> --------------------------------------------------
>
>                 Key: MSITE-132
>                 URL: http://jira.codehaus.org/browse/MSITE-132
>             Project: Maven 2.x Site Plugin
>          Issue Type: Improvement
>         Environment: maven-2.0.4 on any operating system with the latests 
> released plugins (after the doxia-1.0-alpha-8.pom bug)
>            Reporter: Jörg Hohwiller
>         Attachments: MSITE-132.patch
>
>
> The <name> of a project in the POM may contain characters that cause trouble 
> when used in directory names.
> E.g. my open-source project: 
> http://svn.projxpert.com/mmm/trunk/
> Uses names such as "MMM::Configuration". Now when I stage the site of the 
> entire project, the relative link "MMM::Configuration" causes mozilla to say 
> something like "Unknown protocol 'mmm:'".
> Could you please use the artefactId instead. 
> I think personally think that this is a lot better anyways.
> BTW - Thanks for your greate work. M2 is awesome!!!

-- 
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


Reply via email to