[
http://jira.codehaus.org/browse/SCM-275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_85808
]
Jason Melnick commented on SCM-275:
-----------------------------------
That's the problem - the scm information isn't contained within the child
project, and I don't want it to be. The scm information is only contained
within the parent POM and is inherited by the child pom.
The child pom takes the scm definitions from the parent and appends its
artifactId to the end of the url.
The child pom that was referenced above was actually output using
help:effective-pom.
> Need to allow setting of the project directory, not just assume the artifactId
> ------------------------------------------------------------------------------
>
> Key: SCM-275
> URL: http://jira.codehaus.org/browse/SCM-275
> Project: Maven SCM
> Issue Type: Improvement
> Components: maven-scm-api
> Reporter: Jason Melnick
>
> The SCM plugin needs to provide a configuration option to set the project's
> name in the repository and not just assume the artifactId is that directory.
> For instance, my artifactId is dukesbankear. However, in SVN it is stored as
> DukesBankEAR. SCM fails when trying to attain any goal because it is looking
> for .../projectpath/dukesbankear instead of .../projectpath/DukesBankEAR...
--
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
