[jira] Commented: (SCM-275) Need to allow setting of the project directory, not just assume the artifactId
[ http://jira.codehaus.org/browse/SCM-275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_121449 ] Michael Semb Wever commented on SCM-275: and a link to that maven issue? > 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 >Assignee: Emmanuel Venisse > > 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
[jira] Commented: (SCM-275) Need to allow setting of the project directory, not just assume the artifactId
[
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:
https://{removed}/trunk/m2_refapp/BasePOM
A child of BasePOM called ProjectPOM would then have it's scm url interpreted
as:
https://{removed}/trunk/m2_refapp/BasePOM/ProjectPOM
And likewise a child of ProjectPOM called ArtifactPOM would have an interpreted
url as such:
https://{removed}/trunk/m2_refapp/BasePOM/ProjectPOM/ArtifactPOM
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
[jira] Commented: (SCM-275) Need to allow setting of the project directory, not just assume the artifactId
[ http://jira.codehaus.org/browse/SCM-275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_85811 ] Dan Tran commented on SCM-275: -- This is an issue already already filed against maven, dont know where it is thou. What I proposed is a workaround solution. I will keep this issue open until i find the original one. > 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
[jira] Commented: (SCM-275) Need to allow setting of the project directory, not just assume the artifactId
[ 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
[jira] Commented: (SCM-275) Need to allow setting of the project directory, not just assume the artifactId
[ http://jira.codehaus.org/browse/SCM-275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_85804 ] Dan Tran commented on SCM-275: -- in your connection, change dukesbankear to DukesBankEAR, this way maven can locate your source correctly > 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
[jira] Commented: (SCM-275) Need to allow setting of the project directory, not just assume the artifactId
[
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:svn:https://{removed}/m2_refapp
scm:svn:https://{removed}/m2_refapp
https://{removed}/m2_refapp/
This resolves exactly like it should... However, the child that inherits from
it resolves like so (these are excerpts):
dukesbankear
scm:svn:https://{removed}/m2_refapp/dukesbankear
scm:svn:https://{removed}/m2_refapp/dukesbankear
https://{removed}/m2_refapp/dukesbankear
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
[jira] Commented: (SCM-275) Need to allow setting of the project directory, not just assume the artifactId
[ http://jira.codehaus.org/browse/SCM-275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_85792 ] Dan Tran commented on SCM-275: -- You need to set the connection and developerConnection as well. > 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
[jira] Commented: (SCM-275) Need to allow setting of the project directory, not just assume the artifactId
[ http://jira.codehaus.org/browse/SCM-275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_85780 ] Jason Melnick commented on SCM-275: --- lol - wrong element on my part :) The element (of the scm) does in fact work properly when the scm information is declared within that project. However, when declaring the scm info in a parent pom it takes the url specified in the parent and appends the artifactId of the child onto the end (when used on the child project). I'd like to have the ability to set the scm information in a parent and then configure it separately in a child pom if at all possible.. I apologize for setting this as a major issue as it's not... However, for ease of use I think it would be beneficial. > 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
[jira] Commented: (SCM-275) Need to allow setting of the project directory, not just assume the artifactId
[ http://jira.codehaus.org/browse/SCM-275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_85775 ] Dan Tran commented on SCM-275: -- use the element. -D > 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
[jira] Commented: (SCM-275) Need to allow setting of the project directory, not just assume the artifactId
[ http://jira.codehaus.org/browse/SCM-275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_85774 ] Jason Melnick commented on SCM-275: --- I'm not sure I understand what you mean. Are you talking about the element? If so this will affect how the site is deployed and has a high probability of being different than the scm directory. > 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
[jira] Commented: (SCM-275) Need to allow setting of the project directory, not just assume the artifactId
[ http://jira.codehaus.org/browse/SCM-275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_85688 ] Dan Tran commented on SCM-275: -- you will need to configure your pom's url when artifactId and directory name are not the same. > 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
