[
http://jira.codehaus.org/browse/MSITE-132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103351
]
John Allen commented on MSITE-132:
----------------------------------
Denis,
Ahh, it's only if you have no distroManagement section that it invents the path
and this is why I've never seen it (we use a flat project structure and thus
have to declare distroManagement and project.URL in every POM as maven's
default assumptions are wrong for us). Seems a reasonable fix, will apply to my
local patched plugin and play.
> 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
