[ http://jira.codehaus.org/browse/MNG-1709?page=all ]
Kenney Westerhof updated MNG-1709:
----------------------------------
Fix Version/s: (was: 2.0.5)
2.0.6
> Project source path not generated correctly
> -------------------------------------------
>
> Key: MNG-1709
> URL: http://jira.codehaus.org/browse/MNG-1709
> Project: Maven 2
> Issue Type: Bug
> Components: Inheritence and Interpolation
> Reporter: Mike Perham
> Fix For: 2.0.6
>
>
> Maven's project reports require the source directories to reflect the
> artifactId of the related POM. We do not currently use that format and find
> that the source repository path, for instance, is not generated correctly in
> our case. I don't know if it is possible to support our source layout:
> wsf/
> pom.xml
> support/
> pom.xml (artifactId = wsf-support)
> common/
> pom.xml (artifactId = wsf-common-support)
> We do this so that our directory structure is not redundant, as the maven
> structure is now:
> maven-scm/
> maven-scm-providers/
> maven-scm-provider-perforce/
> Is there any way to support this type of layout? I would like to specify the
> top-level repository location and have maven figure out the correct structure
> to tack on to the end of the URL. The generated repository URL is:
> http://<server>/wsf/wsf-support/wsf-common-support
> when it should be:
> http://<server>/wsf/support/common
> If you are not going to support this alternative multi-module layout, could
> you document the existing naming standards required when doing this type of
> inheritance? The current documentation
> [http://maven.apache.org/guides/mini/guide-multi-module.html] is somewhat
> lacking. :-)
--
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
