maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason van Zyl (JIRA)" <>
Subject [jira] Closed: (MNG-1709) Project source path not generated correctly
Date Wed, 30 Dec 2009 00:27:55 GMT


Jason van Zyl closed MNG-1709.

       Resolution: Won't Fix
    Fix Version/s:     (was: 2.2.x)

> Project source path not generated correctly
> -------------------------------------------
>                 Key: MNG-1709
>                 URL:
>             Project: Maven 2 & 3
>          Issue Type: Bug
>          Components: Inheritance and Interpolation
>            Reporter: Mike Perham
> 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
> 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
[] is somewhat lacking. :-)

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message