[ 
http://jira.codehaus.org/browse/SCM-275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_85815
 ] 

Jason Melnick commented on SCM-275:
-----------------------------------

I looked for an existing against SCM, but didn't find one - although there may 
be one for M2 in general.

Another observation:

An inherited SCM URL assumes the svn path is inheritance based as well - for 
example:

SCM info in BasePOM as: 

<url>https://{removed}/trunk/m2_refapp/BasePOM</url>

A child of BasePOM called ProjectPOM would then have it's scm url interpreted 
as:

<url>https://{removed}/trunk/m2_refapp/BasePOM/ProjectPOM</url>

And likewise a child of ProjectPOM called ArtifactPOM would have an interpreted 
url as such:

<url>https://{removed}/trunk/m2_refapp/BasePOM/ProjectPOM/ArtifactPOM</url>

I'm thinking that these issues could be resolved by adding the following 
configuration options:

String defaultLocation - The location, relative to the scm base url, of this 
project.

boolean autoResolve - If true it would locate the svn project based on the way 
it currently works (but taking into account the new defaultLocation config 
option. If false it would just use the base scm url and append either the 
artifactId (by default) or the provided defaultLocation option.

I'm sure that it's not that simple under the covers, but I do think that this 
would provide the flexibility that is necessary.

> 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

        

Reply via email to