[
http://jira.codehaus.org/browse/SCM-275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_85802
]
Jason Melnick commented on SCM-275:
-----------------------------------
They're all set... here's an example:
ParentPOM
<scm> <connection>scm:svn:https://{removed}/m2_refapp</connection>
<developerConnection>scm:svn:https://{removed}/m2_refapp</developerConnection>
<url>https://{removed}/m2_refapp/</url>
</scm>
This resolves exactly like it should... However, the child that inherits from
it resolves like so (these are excerpts):
<artifactId>dukesbankear</artifactId>
<scm>
<connection>scm:svn:https://{removed}/m2_refapp/dukesbankear</connection>
<developerConnection>scm:svn:https://{removed}/m2_refapp/dukesbankear</developerConnection>
<url>https://{removed}/m2_refapp/dukesbankear</url>
</scm>
It automatically appends the artifactId to each of the URL's in the scm
section- regardless of whether you want it to or not.
> 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
