[jira] Updated: (SCM-182) git provider
[
http://jira.codehaus.org/browse/SCM-182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Venisse updated SCM-182:
-
Component/s: (was: maven-scm-site)
maven-scm-provider-git
> git provider
>
>
> Key: SCM-182
> URL: http://jira.codehaus.org/browse/SCM-182
> Project: Maven SCM
> Issue Type: New Feature
> Components: maven-scm-provider-git
> Environment: Developed on Mac OS X 10.3.9 with git 1.2.4
>Reporter: Dominik Winter
> Attachments: git.patch, git.tar.bz2, SCM-182.patch
>
>
> Please find the git provider as attachment.
> Usefulness:
> I used the git provider together with
> [http://maven.apache.org/plugins/maven-release-plugin|maven-release-plugin],
> it works fine for that use case.
> Open issues:
> - the JUnit tests are "proprietary", not yet TCK. I'll fix that.
> If you want to run the tests, you must have git installed and it must be in
> your {{PATH}}.
> To run git:
> - on *Windows*: use [Cygwin|http://www.cygwin.com] and install the binutils,
> openssh, openssl, rsync, curl
> than you are able to compile and install git
> - on Linux: there are packages somewhere
> - on Mac OS X: use the [DarwinPorts|http://www.darwinports.org/]
--
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: (MNG-1944) cyclic dependencies causes maven to not include all transitive dependencies
[ http://jira.codehaus.org/browse/MNG-1944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_89887 ] Joerg Schaible commented on MNG-1944: - Artifacts from projects not using Maven are uploaded with hand-crafted POMs ... ;-) > cyclic dependencies causes maven to not include all transitive dependencies > --- > > Key: MNG-1944 > URL: http://jira.codehaus.org/browse/MNG-1944 > Project: Maven 2 > Issue Type: Bug > Components: POM >Affects Versions: 2.0.1 >Reporter: Brian Fox >Priority: Critical > Fix For: 2.1.x > > > Try including dom4j 1.5.2 and see what dependencies are resolved. dom4j > depends on jaxen, which depends on dom4j. When maven sees the cyclic > dependency, it stops processing the jaxen dependency. This leaves everything > else jaxen depends on not included in the final artifact list. This is mvn -x > output: > dom4j:dom4j:jar:1.5.2 (selected for compile) > [DEBUG] stax:stax-api:jar:1.0 (selected for compile) > [DEBUG] pull-parser:pull-parser:jar:2 (selected for compile) > [DEBUG] jaxme:jaxme-api:jar:0.3 (selected for compile) > [WARNING] > This artifact has been relocated to xml-apis:xml-apis:1.0.b2. > [DEBUG] xml-apis:xml-apis:jar:1.0.b2 (selected for compile) > [DEBUG] msv:xsdlib:jar:20030807 (selected for compile) > [DEBUG] xpp3:xpp3:jar:1.1.3.3 (selected for compile) > [DEBUG] dom4j:dom4j:jar:1.5.2 (removed - causes a cycle in the > graph) > [DEBUG] jaxen:jaxen:jar:1.1-beta-4 (selected for compile) > [DEBUG] msv:relaxngDatatype:jar:20030807 (selected for compile) > Notice that xerces and xom and everything else jaxen depends on isn't > included. > Taking dom4j out of the jaxen pom locally causes everything to be included: > [DEBUG] com.stchome.maven.mojo:helloUser:jar:1.0-SNAPSHOT (selected for null) > [DEBUG] dom4j:dom4j:jar:1.5.2 (selected for compile) > [DEBUG] stax:stax-api:jar:1.0 (selected for compile) > [DEBUG] pull-parser:pull-parser:jar:2 (selected for compile) > [DEBUG] jaxme:jaxme-api:jar:0.3 (selected for compile) > [WARNING] > This artifact has been relocated to xml-apis:xml-apis:1.0.b2. > [DEBUG] xml-apis:xml-apis:jar:1.0.b2 (selected for compile) > [DEBUG] msv:xsdlib:jar:20030807 (selected for compile) > [DEBUG] xpp3:xpp3:jar:1.1.3.3 (selected for compile) > [DEBUG] jaxen:jaxen:jar:1.1-beta-4 (selected for compile) > [DEBUG] jdom:jdom:jar:b10 (selected for compile) > [DEBUG] xom:xom:jar:1.0b3 (selected for compile) > [DEBUG] xerces:xmlParserAPIs:jar:2.6.1 (selected for compile) > [DEBUG] xerces:xercesImpl:jar:2.2.1 (selected for compile) > [DEBUG] xalan:xalan:jar:2.6.0 (selected for compile) > [WARNING] > This artifact has been relocated to xml-apis:xml-apis:1.0.b2. > [DEBUG] xml-apis:xml-apis:jar:1.0.b2 (selected for compile) > [WARNING] > This artifact has been relocated to com.ibm.icu:icu4j:2.6.1. > [DEBUG] com.ibm.icu:icu4j:jar:2.6.1 (selected for compile) > [WARNING] > This artifact has been relocated to javax.servlet:servlet-api:2.4. > [DEBUG] javax.servlet:servlet-api:jar:2.4 (selected for compile) > [WARNING] > This artifact has been relocated to org.ccil.cowan.tagsoup:tagsoup:0.9.7. > [DEBUG] org.ccil.cowan.tagsoup:tagsoup:jar:0.9.7 (selected for > compile) > [DEBUG] xerces:xmlParserAPIs:jar:2.6.1 (removed - nearer found: 2.6.2) > [DEBUG] xerces:xmlParserAPIs:jar:2.6.2 (selected for compile) > [DEBUG] xerces:xercesImpl:jar:2.2.1 (removed - nearer found: 2.6.2) > [DEBUG] xerces:xercesImpl:jar:2.6.2 (selected for compile) > [DEBUG] msv:relaxngDatatype:jar:20030807 (selected for compile) -- 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: (MNG-2205) "provided" scope dependencies must be transitive
[ http://jira.codehaus.org/browse/MNG-2205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_89888 ] Joerg Schaible commented on MNG-2205: - No, you're using "provided" in a wrong manner. A provided means that the artifact is available in the target environment i.e. if you build an enterprise application for a J2EE server you can safely assume that javamail or activation is available, since it is part of the JEE stack. In your case you are introducing a runtime dependency and you should use therefore scope "runtime". > "provided" scope dependencies must be transitive > > > Key: MNG-2205 > URL: http://jira.codehaus.org/browse/MNG-2205 > Project: Maven 2 > Issue Type: Bug > Components: Dependencies >Reporter: David Boden >Priority: Critical > Fix For: 2.1.x > > > A provided scope dependency can also be thought of as "compile-only". > Project A requires Sybase JConnect on the runtime classpath. Project A > declares a "provided" dependency on Sybase JConnect. > Project B depends upon Project A. Project B declares a "compile" dependency > on Project A. > Project C depends upon Project B. Project C declares a "compile" dependency > on Project B. > C > | - compile dependency > B > | - compile dependency > A > | - provided dependency > Sybase JConnect > So, does Project C transitively depend on Sybase JConnect. Yes, of course! > The "provided" dependency needs to be transitive. > Ultimately, when Project C gets deployed, Sybase JConnect needs to be > somewhere on the runtime classpath in order for the application to function. > It's valid for Project C to assume that Sybase JConnect is available and use > JDBC all over the Project C code. Project C is safe to do this because it can > happily deduce that Sybase JConnect will be there in the runtime environment > because Project A NEEDS IT. > I've got Use Cases all over my aggregated build which make it absolutely > critical and common sense that provided scope dependencies are transitive. > For the (very rare) odd case where you don't want to inherit provided > dependencies, you can them. -- 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: (MPMD-28) Support for multi-projects poms
[ http://jira.codehaus.org/browse/MPMD-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_89890 ] Damien Lecan commented on MPMD-28: -- It works perfectly for me ! Thanks a lot for this nice feature > Support for multi-projects poms > --- > > Key: MPMD-28 > URL: http://jira.codehaus.org/browse/MPMD-28 > Project: Maven 2.x Pmd Plugin > Issue Type: Improvement > Components: CPD, PMD >Reporter: Torsten Curdt > Assigned To: Daniel Kulp > Fix For: 2.2 > > Attachments: maven-pmd-plugin-20061020-1242.patch, > maven-pmd-plugin-20061020-1445.patch, multiproject.diff > > > Added support for multi-projects so if you set "aggregate" to "true" the > parent project will generate the report and the childs will not execute it > anymore -- 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] Created: (MDEP-69) Version 2.0-alpha-2 was incorrectly deployed to central repository (POM is missing)
Version 2.0-alpha-2 was incorrectly deployed to central repository (POM is missing) --- Key: MDEP-69 URL: http://jira.codehaus.org/browse/MDEP-69 Project: Maven 2.x Dependency Plugin Issue Type: Bug Affects Versions: 2.0-alpha-2 Reporter: Stepan Roh Assigned To: Brian Fox Priority: Blocker http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-dependency-plugin/2.0-alpha-2/ does not contain pom file http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-dependency-plugin/2.0-alpha-2/maven-dependency-plugin-2.0-alpha-2.pom (as opposed to 2.0-alpha-1 which does). This causes builds to fail with Internal error in the plugin manager executing goal 'org.apache.maven.plugins:maven-dependency-plugin:2.0-alpha-2:resolve-plugins': Unable to find the mojo 'org.apache.maven.plugins:maven-dependency-plugin:2.0-alpha-2:resolve-plugins' in the plugin 'org.apache.maven.plugins:maven-dependency-plugin' org/codehaus/plexus/archiver/ArchiverException Please fix as soon as possible. -- 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] Created: (MAVENUPLOAD-1416) eva-properties-0.2.2
eva-properties-0.2.2 Key: MAVENUPLOAD-1416 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1416 Project: maven-upload-requests Issue Type: Task Reporter: Maximilian Antoni Thank you for uploading. -- 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: (MNG-2205) "provided" scope dependencies must be transitive
[ http://jira.codehaus.org/browse/MNG-2205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_89894 ] David Boden commented on MNG-2205: -- That's why JConnect is a terrible example. A better example of this sort of dependency is XML Beans. XML Beans will not work based on a "runtime" dependency because your code will require it on the compilation classpath. If all your products depend on XML Beans, you want to be able to declare it as a base dependency and have all your modules inherit that dependency. > "provided" scope dependencies must be transitive > > > Key: MNG-2205 > URL: http://jira.codehaus.org/browse/MNG-2205 > Project: Maven 2 > Issue Type: Bug > Components: Dependencies >Reporter: David Boden >Priority: Critical > Fix For: 2.1.x > > > A provided scope dependency can also be thought of as "compile-only". > Project A requires Sybase JConnect on the runtime classpath. Project A > declares a "provided" dependency on Sybase JConnect. > Project B depends upon Project A. Project B declares a "compile" dependency > on Project A. > Project C depends upon Project B. Project C declares a "compile" dependency > on Project B. > C > | - compile dependency > B > | - compile dependency > A > | - provided dependency > Sybase JConnect > So, does Project C transitively depend on Sybase JConnect. Yes, of course! > The "provided" dependency needs to be transitive. > Ultimately, when Project C gets deployed, Sybase JConnect needs to be > somewhere on the runtime classpath in order for the application to function. > It's valid for Project C to assume that Sybase JConnect is available and use > JDBC all over the Project C code. Project C is safe to do this because it can > happily deduce that Sybase JConnect will be there in the runtime environment > because Project A NEEDS IT. > I've got Use Cases all over my aggregated build which make it absolutely > critical and common sense that provided scope dependencies are transitive. > For the (very rare) odd case where you don't want to inherit provided > dependencies, you can them. -- 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: (MAVENUPLOAD-1412) Springframework repository sync
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_89896 ] Grzegorz Slowikowski commented on MAVENUPLOAD-1412: --- And what about http://repo1.maven.org/maven2/org/springframework/spring/maven-metadata.xml file? The latest version there is 2.0-m4. Is this file used? > Springframework repository sync > --- > > Key: MAVENUPLOAD-1412 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1412 > Project: maven-upload-requests > Issue Type: Task >Reporter: Avi Cherry > Assigned To: Carlos Sanchez > > It appears that the spring framework is not being automatically synced with > the project's repository. The included URL points at the project's maven > repository. Thanks. -- 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] Closed: (SCM-183) Added listFiles to ScmProvider
[ http://jira.codehaus.org/browse/SCM-183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse closed SCM-183. Assignee: Emmanuel Venisse Resolution: Fixed > Added listFiles to ScmProvider > -- > > Key: SCM-183 > URL: http://jira.codehaus.org/browse/SCM-183 > Project: Maven SCM > Issue Type: New Feature > Components: maven-scm-api >Reporter: Zsolt Koppany > Assigned To: Emmanuel Venisse > Fix For: 1.0 > > Attachments: scm-maven.patch, scm-maven.patch > > > This patch adds "listFiles" method to "ScmProvider" and contains the > implementation for subversion. -- 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] Updated: (SCM-207) Implementing update and checkout command
[ http://jira.codehaus.org/browse/SCM-207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated SCM-207: - Fix Version/s: (was: 1.0) future > Implementing update and checkout command > - > > Key: SCM-207 > URL: http://jira.codehaus.org/browse/SCM-207 > Project: Maven SCM > Issue Type: Improvement > Components: maven-scm-provider-vss >Affects Versions: 1.0-beta-3 >Reporter: Thorsten Riek > Fix For: future > > Attachments: SCM-207-02-maven-scm-provider-vss.patch, > SCM-207-maven-scm-provider-vss.patch > > > Implemented with VSS GET command. Update ignores writable resources. Checkout > overwrites writable resources. -- 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] Updated: (SCM-214) Provide ability to bootstrap project just by groupId and artifactId
[ http://jira.codehaus.org/browse/SCM-214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated SCM-214: - Fix Version/s: (was: 1.0) future > Provide ability to bootstrap project just by groupId and artifactId > --- > > Key: SCM-214 > URL: http://jira.codehaus.org/browse/SCM-214 > Project: Maven SCM > Issue Type: Improvement > Components: maven-plugin >Reporter: Andreas Schildbach > Fix For: future > > > It'll be great if I could just check out the CVS head / SVN trunk of a > project by something like > mvn svn:checkout -DgroupId=myGroupId -DartifactId=myArtifactId > Maven would get the latest associated POM, read the repository location from > the SCM entries, and proceed with checking out as you would expect it. > Then, I'd just have to cd to the newly created directory and issue > mvn eclipse:eclipse (or the equivalent for your favourite IDE) > This enhancement is also targetted at the M2 plugin, for which I did not find > any JIRA project. -- 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] Closed: (MDEP-69) Version 2.0-alpha-2 was incorrectly deployed to central repository (POM is missing)
[ http://jira.codehaus.org/browse/MDEP-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Fox closed MDEP-69. - Resolution: Fixed Fix Version/s: 2.0-alpha-2 This was supposed to be staged first, but there where issues with the release and it apparently deployed before I caught it. The release is staged in this repository: http://people.apache.org/~brianf/staging-repository/ once the vote passes, this will be moved into central. I removed the alpha-2 folder from the rsync folder so it should update central shortly. > Version 2.0-alpha-2 was incorrectly deployed to central repository (POM is > missing) > --- > > Key: MDEP-69 > URL: http://jira.codehaus.org/browse/MDEP-69 > Project: Maven 2.x Dependency Plugin > Issue Type: Bug >Affects Versions: 2.0-alpha-2 >Reporter: Stepan Roh > Assigned To: Brian Fox >Priority: Blocker > Fix For: 2.0-alpha-2 > > > http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-dependency-plugin/2.0-alpha-2/ > does not contain pom file > http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-dependency-plugin/2.0-alpha-2/maven-dependency-plugin-2.0-alpha-2.pom > (as opposed to 2.0-alpha-1 which does). This causes builds to fail with > Internal error in the plugin manager executing goal > 'org.apache.maven.plugins:maven-dependency-plugin:2.0-alpha-2:resolve-plugins': > Unable to find the mojo > 'org.apache.maven.plugins:maven-dependency-plugin:2.0-alpha-2:resolve-plugins' > in the plugin 'org.apache.maven.plugins:maven-dependency-plugin' > org/codehaus/plexus/archiver/ArchiverException > Please fix as soon as possible. -- 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: (MAVENUPLOAD-1412) Springframework repository sync
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_89899 ] Tomislav Stojcevich commented on MAVENUPLOAD-1412: -- Sorry to bump in on this issue but the spring-2.0.3-sources.jar in the repo does not match the spring-src.zip file contained in the spring-framework-2.0.3.zip file downloadable from sourceforge. The one in the repo is missing several packages. Where do I file an issue for that? > Springframework repository sync > --- > > Key: MAVENUPLOAD-1412 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1412 > Project: maven-upload-requests > Issue Type: Task >Reporter: Avi Cherry > Assigned To: Carlos Sanchez > > It appears that the spring framework is not being automatically synced with > the project's repository. The included URL points at the project's maven > repository. Thanks. -- 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] Closed: (SCM-84) Develop VSS Provider for Maven-SCM
[ http://jira.codehaus.org/browse/SCM-84?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse closed SCM-84. --- Assignee: Emmanuel Venisse Resolution: Fixed Fix Version/s: 1.0-beta-4 > Develop VSS Provider for Maven-SCM > -- > > Key: SCM-84 > URL: http://jira.codehaus.org/browse/SCM-84 > Project: Maven SCM > Issue Type: New Feature > Components: maven-scm-provider-vss >Reporter: George Gastaldi > Assigned To: Emmanuel Venisse > Fix For: 1.0-beta-4 > > Attachments: maven-scm-provider-vss-unfinished.zip, > maven-scm-provider-vss.zip > > -- 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] Closed: (SCM-57) m2 maven-scm-plugin should use the same configurations/properties with M1 plugin
[ http://jira.codehaus.org/browse/SCM-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse closed SCM-57. --- Assignee: Emmanuel Venisse Resolution: Won't Fix > m2 maven-scm-plugin should use the same configurations/properties with M1 > plugin > > > Key: SCM-57 > URL: http://jira.codehaus.org/browse/SCM-57 > Project: Maven SCM > Issue Type: Bug > Components: maven-plugin >Affects Versions: 1.0-alpha-3 > Environment: xp >Reporter: Dan Tran > Assigned To: Emmanuel Venisse > Attachments: AbstractScmMojo.java, PerforceCheckOutCommand.java, > ServerBasedScmProviderRepository.java > > > I think m2 should try to make scm plugin configuration compatible with m2 -- 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] Updated: (SCM-33) Collect more information into the ScmFile
[ http://jira.codehaus.org/browse/SCM-33?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated SCM-33: Fix Version/s: future > Collect more information into the ScmFile > - > > Key: SCM-33 > URL: http://jira.codehaus.org/browse/SCM-33 > Project: Maven SCM > Issue Type: Improvement >Reporter: Trygve Laugstol > Fix For: future > > > These are fields that should be put into the ScmFile: > * Developer ID > * Timestamp > * Change set id/number > * Version id/number -- 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] Updated: (SCM-257) The perforce provider should provide an "update" functionality for the SCM plugin's "update" command that is semantically correct.
[
http://jira.codehaus.org/browse/SCM-257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Venisse updated SCM-257:
-
Fix Version/s: future
> The perforce provider should provide an "update" functionality for the SCM
> plugin's "update" command that is semantically correct.
> --
>
> Key: SCM-257
> URL: http://jira.codehaus.org/browse/SCM-257
> Project: Maven SCM
> Issue Type: Improvement
> Components: maven-scm-provider-perforce
> Environment: All OS, maven 2.x SCM plugin linked to perforce
>Reporter: Dana Lacoste
> Fix For: future
>
>
> The perforce provider implements the update command as a checkout.
> This is not semantically correct in the following situations:
> 1 - If no changes are pending, the update command should not do anything
> 2 - If some files are changed, only those files should be updated.
> (The checkout command checks out all files, regardless of what already exists)
> This is particularly daunting if (in my case :) there is a very large
> directory structure in perforce that does not change regularly (checking out
> a 4GB fileset that hasn't changed is, effectively, wasted time.)
> (As this is my first time using JIRA feel free to correct any of the settings
> I've made)
> Testing info:
> Although I don't have any JUnit experience, a test case can be made simply:
> 1 - create a perforce repository with two files in it (and configure maven to
> use it)
> 2 - run "mvn scm:checkout" to obtain the files
> 3 - modify one of the files on another system, check the modified file into
> perforce
> 4 - run "mvn scm:update" and only the modified file should be checked out.
> Implementation Ideas:
> Somehow the "scm:update" command will need to know that the files already
> exist. The most simple way is to require that ${P4CLIENT} be set and simply
> to run "p4 sync ..." in the directory involved (or, similarly, "p4 sync
> ${path}..." using the path that's defined in the scm URL) and to allow
> perforce to do the work of figuring out what's needed.
--
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] Closed: (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:all-tabpanel ] Emmanuel Venisse closed SCM-275. Assignee: Emmanuel Venisse Resolution: Won't Fix It isn't a maven-scm issue but a 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 > Assigned To: 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] Updated: (SCM-142) Starteam tree stale
[ http://jira.codehaus.org/browse/SCM-142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated SCM-142: - Fix Version/s: future > Starteam tree stale > --- > > Key: SCM-142 > URL: http://jira.codehaus.org/browse/SCM-142 > Project: Maven SCM > Issue Type: Bug > Components: maven-scm-provider-starteam > Environment: continuum-1.0.2 >Reporter: Bob Herrmann > Fix For: future > > > It only takes a few changes to starteam for the checked out filesystem to > become hopelessly stale. The only recovery option is to completely remove > all files and startover. Either the code checking out is not handing the > timestamps correctly, or starteam command line has problems keeping a checked > out tree in sync (this more likely - as we also see this problem with AntHill > when using it's incremental builder.) Possible fixes might be to detect > 'unknown' status's and flush the checked out tree. Or try using the 2005 bco > command instead of stcmd. -- 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] Updated: (SCM-271) Allow scm:checkin to run without a pom
[ http://jira.codehaus.org/browse/SCM-271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated SCM-271: - Fix Version/s: future > Allow scm:checkin to run without a pom > --- > > Key: SCM-271 > URL: http://jira.codehaus.org/browse/SCM-271 > Project: Maven SCM > Issue Type: Improvement > Components: maven-plugin >Affects Versions: 1.0-beta-4 > Environment: windows, starteam, linux >Reporter: Dan Tran > Fix For: future > > > any objections? -- 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] Updated: (SCM-153) Continuum fails while trying to build from clearcase
[ http://jira.codehaus.org/browse/SCM-153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated SCM-153: - Fix Version/s: future > Continuum fails while trying to build from clearcase > > > Key: SCM-153 > URL: http://jira.codehaus.org/browse/SCM-153 > Project: Maven SCM > Issue Type: Bug > Components: maven-scm-provider-clearcase >Affects Versions: 1.0-beta-3 > Environment: Clearcase UCM / Windows XP / Snapshot view >Reporter: David Dandeneau > Fix For: future > > > When trying to perform a build from continuum I receive the following error: > Provider message: The cleartool command failed. > Command output: > --- > cleartool: Error: A registry entry already exists for > "dandendj-LNGDAYD-4130684-maven-7". > --- > This happens on the second time through. On the first time through I receive: > org.apache.maven.continuum.execution.ContinuumBuildExecutorException: Could > not find Maven project descriptor. > at > org.apache.maven.continuum.execution.maven.m2.MavenTwoBuildExecutor.updateProjectFromCheckOut(MavenTwoBuildExecutor.java:111) > at > org.apache.maven.continuum.core.action.UpdateProjectFromWorkingDirectoryContinuumAction.execute(UpdateProjectFromWorkingDirectoryContinuumAction.java:62) > at > org.apache.maven.continuum.buildcontroller.DefaultBuildController.build(DefaultBuildController.java:169) > at > org.apache.maven.continuum.buildcontroller.BuildProjectTaskExecutor.executeTask(BuildProjectTaskExecutor.java:53) > at > org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable.run(ThreadedTaskQueueExecutor.java:103) > at java.lang.Thread.run(Thread.java:595) -- 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] Updated: (SCM-54) API enhancement for SSCM vendor compatability
[ http://jira.codehaus.org/browse/SCM-54?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated SCM-54: Fix Version/s: future > API enhancement for SSCM vendor compatability > - > > Key: SCM-54 > URL: http://jira.codehaus.org/browse/SCM-54 > Project: Maven SCM > Issue Type: Improvement > Components: maven-scm-api >Reporter: Mike Esler > Fix For: future > > > As discussed on the mailing list, we should add a reserved/uunreserved > boolean to the checkout command. > Also, provide a bind() command which binds a local directory to an > SCM-controlled project. There should be a corresponding release() method as > well. > Thus, the calling pattern to get files out of a repository would always be a > 2-step process: > bind(localDirectory, remoteProject) > checkout(localDirectory, fileset, reserved/unreserved) > This will open the door for integrations with a lot of SCM vendors, and allow > us to clean up the SCM provider in the Wagon code. -- 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] Updated: (SCM-42) Create a ChangeSorter for sort and group ChangeSet list
[ http://jira.codehaus.org/browse/SCM-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated SCM-42: Fix Version/s: future > Create a ChangeSorter for sort and group ChangeSet list > --- > > Key: SCM-42 > URL: http://jira.codehaus.org/browse/SCM-42 > Project: Maven SCM > Issue Type: Improvement > Components: maven-scm-api >Affects Versions: 1.0-alpha-2 >Reporter: Emmanuel Venisse > Assigned To: Emmanuel Venisse > Fix For: future > > -- 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] Updated: (SCM-156) Add TCK tests for Perforce
[ http://jira.codehaus.org/browse/SCM-156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated SCM-156: - Fix Version/s: future > Add TCK tests for Perforce > -- > > Key: SCM-156 > URL: http://jira.codehaus.org/browse/SCM-156 > Project: Maven SCM > Issue Type: Task > Components: maven-scm-provider-perforce >Reporter: Emmanuel Venisse > Fix For: future > > > They'll be run only by developers that have Perforce installed -- 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] Updated: (SCM-262) scm:tag for subversion tagging from local version of code, not directly from repository
[ http://jira.codehaus.org/browse/SCM-262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated SCM-262: - Fix Version/s: future > scm:tag for subversion tagging from local version of code, not directly from > repository > --- > > Key: SCM-262 > URL: http://jira.codehaus.org/browse/SCM-262 > Project: Maven SCM > Issue Type: Bug >Reporter: Stephan Heilner > Fix For: future > > > In theory, you shouldn't tag or branch from a local and potentially different > version of the code. From what I can tell, the scm:tag imports your existing > code into a new tag. With subversion, tagging is very lightweight if you do > a 'svn copy trunk_url tag_url'. The way it currently works make sense for > other repositories such as CVS but not for subversion. -- 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] Updated: (SCM-167) Check out complains about missing directory.
[ http://jira.codehaus.org/browse/SCM-167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated SCM-167: - Fix Version/s: future > Check out complains about missing directory. > - > > Key: SCM-167 > URL: http://jira.codehaus.org/browse/SCM-167 > Project: Maven SCM > Issue Type: Bug > Components: maven-scm-provider-clearcase >Affects Versions: 1.0-beta-2 > Environment: Using Continuum 1.0.2 on HP-UX 11 with Java 1.4.2.04 and > ClearCase 2003.06.00. >Reporter: Fredrik Rubensson > Fix For: future > > > When doing a build in Continuum using ClearCase as SCM it fails with the > message: "Working directory > "/proj/so/ext/continuum/apps/continuum/working-directory/1/.." does not > exist!" which is true. Further investigations into the source code > (ClearCaseCheckout.java) reveals that the directory in question is removed a > couple of lines above the call to clearcase that results in this error. There > is even a comment in the code that says that ClearCase need a non-existant > directory for this command to work. Maybe this is different for different OSs > and/or ClearCase versions? -- 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] Updated: (SCM-157) Add TCK tests for Clearcase
[ http://jira.codehaus.org/browse/SCM-157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated SCM-157: - Fix Version/s: future > Add TCK tests for Clearcase > --- > > Key: SCM-157 > URL: http://jira.codehaus.org/browse/SCM-157 > Project: Maven SCM > Issue Type: Task > Components: maven-scm-provider-clearcase >Reporter: Emmanuel Venisse > Fix For: future > > > They'll be run only by developers that have Clearcase installed. > It will be great if we can have them for all type of Clearcase -- 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] Updated: (SCM-38) Ability to assign an issue tracking to add, lock, and checkin
[ http://jira.codehaus.org/browse/SCM-38?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated SCM-38: Fix Version/s: future > Ability to assign an issue tracking to add, lock, and checkin > - > > Key: SCM-38 > URL: http://jira.codehaus.org/browse/SCM-38 > Project: Maven SCM > Issue Type: New Feature > Components: maven-scm-api >Affects Versions: 1.0-alpha-1 > Environment: xp, maven 1.0.2 >Reporter: Dan Tran > Fix For: future > > > Clearcase and starteam (if configured) insist to have an associate issue > id ( ie activity in clearcase, CR/activity/task in starteam) during lock, > add, and checkin commands. > Suggest to add "issue" argument for those commands in maven-scm-api interface -- 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] Updated: (SCM-281) Perforce problem: incorrect client spec is used
[ http://jira.codehaus.org/browse/SCM-281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated SCM-281: - Fix Version/s: future > Perforce problem: incorrect client spec is used > --- > > Key: SCM-281 > URL: http://jira.codehaus.org/browse/SCM-281 > Project: Maven SCM > Issue Type: Bug > Components: maven-scm-provider-perforce >Affects Versions: 1.0-beta-4 >Reporter: Anton Katernoga > Assigned To: Mike Perham > Fix For: future > > Attachments: patch.p4.txt > > > I have 2 projects set up which use the same perforce scm url. One is run each > 5 mins, the other is a nightly tests build. I've noticed that the latter > never gets run-the message is that the dir is up-to date. It appeared that > after the first project is run, its client spec is set to system variable in > PerforceCheckOutCommand (maven-scm perforce provider) class and afterwards > the value of the var is used instead of a correct client spec. I didn't > remove the property set, as it is a fix to SCM-165, but rather the place > where prop is used. Now works fine. > Patch is attached. -- 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] Updated: (SCM-269) Perforce support doesn't work when there's a space in the local path
[
http://jira.codehaus.org/browse/SCM-269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Venisse updated SCM-269:
-
Fix Version/s: future
> Perforce support doesn't work when there's a space in the local path
>
>
> Key: SCM-269
> URL: http://jira.codehaus.org/browse/SCM-269
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-perforce
>Affects Versions: 1.0-beta-4
>Reporter: David Jackman
> Assigned To: Mike Perham
> Fix For: future
>
>
> Create a view of a Maven project in Perforce in a local directory whose path
> contains a space. Perform some SCM goal (I was trying to scm:update). It
> won't work. The error message is very cryptic ("Unable to sync. Are you
> logged in?"). From the looks of it, the client command (which is run just
> before the sync command) has problems, but these problems aren't reported. I
> think the main problem is the fact that the local path is used in the client
> name, and client names can't contain spaces. Other elements of the client
> (root and view) also will contain spaces, but I don't know if Perforce has a
> problem with these.
--
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] Updated: (SCM-117) Add parameters to scm configuration element
[ http://jira.codehaus.org/browse/SCM-117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated SCM-117: - Fix Version/s: future > Add parameters to scm configuration element > --- > > Key: SCM-117 > URL: http://jira.codehaus.org/browse/SCM-117 > Project: Maven SCM > Issue Type: Wish > Components: maven-scm-provider-starteam >Affects Versions: 1.0-beta-2 >Reporter: Aviran Mordo > Assigned To: Dan Tran > Fix For: future > > > It would be very nice to have the ability to add parameters to the scm > element. For instance to add parameter to always force checkout. for instance > in Starteam I would like to add -o so every time stcmd is called the > parameters will be concatenated to the command line -- 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] Updated: (SCM-71) Implement accurev provider
[ http://jira.codehaus.org/browse/SCM-71?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated SCM-71: Fix Version/s: future > Implement accurev provider > -- > > Key: SCM-71 > URL: http://jira.codehaus.org/browse/SCM-71 > Project: Maven SCM > Issue Type: New Feature > Components: maven-scm-provider-accurev >Reporter: Emmanuel Venisse > Fix For: future > > > I look at documentation, and it's very easy to do (works like cvs or svn) > http://www.accurev.com/download/docs/AccuRev_User_CLI.pdf -- 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] Updated: (SCM-132) extssh connection method not shown
[ http://jira.codehaus.org/browse/SCM-132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated SCM-132: - Fix Version/s: future > extssh connection method not shown > -- > > Key: SCM-132 > URL: http://jira.codehaus.org/browse/SCM-132 > Project: Maven SCM > Issue Type: Bug > Components: maven-scm-provider-cvs > Environment: Windows 2000; Java 1.4 JDK, Maven 2.01 maven-scm-plugin > 1.0-alpha-2 >Reporter: Todd Nine > Fix For: future > > > When attemping to perform a release from a project checked out from eclipse I > receive the following error. > [INFO] [release:prepare] > [INFO] Verifying there are no local modifications ... > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] An error is occurred in the status process. > Embedded error: Error! > [INFO] > > [INFO] Trace > org.apache.maven.lifecycle.LifecycleExecutionException: An error is occurred > in the status process. > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:555) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:485) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:455) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:303) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:216) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:139) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:249) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:324) > at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) > at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) > at org.codehaus.classworlds.Launcher.main(Launcher.java:375) > Caused by: org.apache.maven.plugin.MojoExecutionException: An error is > occurred in the status process. > at > org.apache.maven.plugins.release.PrepareReleaseMojo.checkForLocalModifications(PrepareReleaseMojo.java:514) > at > org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareReleaseMojo.java:201) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:432) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:530) > ... 16 more > Caused by: org.apache.maven.scm.ScmException: Error! > at > org.apache.maven.plugins.release.helpers.ScmHelper.checkResult(ScmHelper.java:124) > at > org.apache.maven.plugins.release.helpers.ScmHelper.getStatus(ScmHelper.java:175) > at > org.apache.maven.plugins.release.PrepareReleaseMojo.checkForLocalModifications(PrepareReleaseMojo.java:510) > ... 19 more > Since Eclipse is a commonly used IDE, is it possible to add the extssh > connection parameter. Below is my scm from my pom.xml > > scm:cvs:ext:[EMAIL > PROTECTED]:/a01/proj/CVS:webservices/ServiceProviders > scm:cvs:ext:[EMAIL > PROTECTED]:/a01/proj/CVS:webservices/ServiceProviders > HEAD > > http://empt.ata.com/cgi-bin/cvsweb.cgi/webservices/ServiceProviders/?cvsroot=ATA.com-Development > -- 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] Updated: (SCM-23) Capabilities query support.
[ http://jira.codehaus.org/browse/SCM-23?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated SCM-23: Fix Version/s: future > Capabilities query support. > --- > > Key: SCM-23 > URL: http://jira.codehaus.org/browse/SCM-23 > Project: Maven SCM > Issue Type: New Feature > Components: maven-scm-api >Reporter: Trygve Laugstol > Fix For: future > > > The API needs methods for querying the SCM implementations about their > features. Some SCMs doesn't support branches, some doesn't support moving > files etc. The two things that needs to be done is: > * Find all possible features that the SCMs can have. > * Make a scalable/forward compatible way to query for features. -- 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] Updated: (SCM-273) Each provider must provide a facilty to detect whether it can run on a given system
[ http://jira.codehaus.org/browse/SCM-273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated SCM-273: - Fix Version/s: future > Each provider must provide a facilty to detect whether it can run on a given > system > --- > > Key: SCM-273 > URL: http://jira.codehaus.org/browse/SCM-273 > Project: Maven SCM > Issue Type: New Feature > Components: maven-scm-api >Reporter: Jason van Zyl > Fix For: future > > > For pure java libraries this is easy. For command line tools we need to be > able to figure out whether a given provider can actually run. This will help > with general installation niceties in continuum but will also allow us to > create profile activators based on whether we can actually run the tests > cases for a given scm provider. -- 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] Updated: (SCM-252) ClearCaseUpdateConsumer for I18N
[
http://jira.codehaus.org/browse/SCM-252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Venisse updated SCM-252:
-
Fix Version/s: future
> ClearCaseUpdateConsumer for I18N
> -
>
> Key: SCM-252
> URL: http://jira.codehaus.org/browse/SCM-252
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-clearcase
>Affects Versions: 1.0-beta-3
> Environment: does not dependency
>Reporter: komusubi
> Fix For: future
>
>
> It can't get updateFiles list way of indexOf("Loading") method because I
> use Japanese version.
> It might use ResourceBundle ??
> I have to need fix it because use with continuum, so I can give you a patch,
> but how should I do?
--
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] Updated: (SCM-69) Improve error message when commit over https fails
[ http://jira.codehaus.org/browse/SCM-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated SCM-69: Fix Version/s: future > Improve error message when commit over https fails > -- > > Key: SCM-69 > URL: http://jira.codehaus.org/browse/SCM-69 > Project: Maven SCM > Issue Type: Improvement > Components: maven-scm-provider-svn >Reporter: Jason van Zyl > Fix For: future > > > On the codehaus machine I had not set myself up with a password before I > attempted to commit with SVN via https. The error message that was presented > was "Error!" which isn't very helpful :-) -- 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] Updated: (SCM-158) Add TCK tests for Starteam
[ http://jira.codehaus.org/browse/SCM-158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated SCM-158: - Fix Version/s: future > Add TCK tests for Starteam > -- > > Key: SCM-158 > URL: http://jira.codehaus.org/browse/SCM-158 > Project: Maven SCM > Issue Type: Task > Components: maven-scm-provider-starteam >Reporter: Emmanuel Venisse > Assigned To: Dan Tran > Fix For: future > > > They'll be run only by developers that have Starteam installed -- 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] Updated: (SCM-227) Document use cases for maven-scm-plugin
[ http://jira.codehaus.org/browse/SCM-227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated SCM-227: - Fix Version/s: future > Document use cases for maven-scm-plugin > --- > > Key: SCM-227 > URL: http://jira.codehaus.org/browse/SCM-227 > Project: Maven SCM > Issue Type: Improvement > Components: maven-plugin >Affects Versions: 1.0-beta-3 >Reporter: Yuri Schimke > Fix For: future > > > I'm creating a new issue, instead of opening SCM-221 because its really a > broader issue. > We are using perforce, but I am not putting this against it, because I hope > it will work consistently across all providers. > Its confusing exactly which scenarios are supported by the maven plugin. It > seems to work great with the release plugin, but using the scm plugin > directly is not straightforward. > There is probably only a handful of reasons people will be using the scm > plugin directly, rather than part of something like the release plugin, these > include. > 1) scm:update or scm:status - to sync or check an existing checkout against > HEAD or label. i.e. cruisecontrol. > - in perforce this would use an existing clientspec. > 2) scm:checkout - to get a new working directory that then supports > scm:status, scm:update etc > - in perforce this would be a new persistent clientspec. > 3) export files from source control e.g. "cvs export", > - in perforce this would be a new temporary clientspec. > In terms of the direction of the project, the use of system properties seems > a bit brittle as these providers might be used multiple times within a mvn > build. i.e. the release plugin, checks the local status 1), then does a > clean checkout 3). Although I guess the release plugin might just set these > option in code anyway, ignoring the system property. > Examples of the problems we are having, scm:checkout works well, but then > trying to use scm:update gives you wrong results. Without the page showing > the typical use cases of the scm plugin (regardless of SCM provider), its > hard to work out if something is a bug or just not supported. -- 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] Updated: (SCM-240) add support for tagging a revision
[ http://jira.codehaus.org/browse/SCM-240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated SCM-240: - Fix Version/s: future > add support for tagging a revision > -- > > Key: SCM-240 > URL: http://jira.codehaus.org/browse/SCM-240 > Project: Maven SCM > Issue Type: Improvement > Components: maven-plugin, maven-scm-api >Reporter: Sharmarke Aden > Fix For: future > > > I am not sure if this functionality can be supported by all scm providers but > in subversion one can tag a revision using the copy command. I would love to > see support added to SCM so that a) one can determine the current working > revision and b) based on the working revision ID create a tag. In subversion > on can do this by using the following set of commands. > #get the working copy revision information > svn info > #create a tag from the trunk using revision 1204 > svn copy -r1204 http://svn.example.com/repos/calc/trunk > http://svn.example.com/repos/calc/tags/release-1.0 -m "revision tag" > Notes: > My understanding is that SCM API currently does support getting the revision > of the current working copy. -- 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] Updated: (SCM-21) separate revision and tag handling
[
http://jira.codehaus.org/browse/SCM-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Venisse updated SCM-21:
Fix Version/s: future
> separate revision and tag handling
> --
>
> Key: SCM-21
> URL: http://jira.codehaus.org/browse/SCM-21
> Project: Maven SCM
> Issue Type: Task
> Components: maven-scm-api
>Reporter: Brett Porter
> Fix For: future
>
>
> while in CVS revision# and tag are handled in the same way, the concepts can
> be separated and will make other SCMs easier.
> for example, in subversion, valid revisions are:
> rev#
> HEAD
> BASE
> COMMITTED
> PREV
> {DATE}
> tags are normal checkouts from a different base.
> In CVS, revisions are:
> rev# (per file only really makes sense here, but can apply to several)
> HEAD
> SOME_BRANCH_TAG
> {DATE}
--
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] Updated: (SCM-246) p4 command reports most or all errors on stderr but maven-scm-provider-perforce throws away stderr
[ http://jira.codehaus.org/browse/SCM-246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated SCM-246: - Fix Version/s: future > p4 command reports most or all errors on stderr but > maven-scm-provider-perforce throws away stderr > -- > > Key: SCM-246 > URL: http://jira.codehaus.org/browse/SCM-246 > Project: Maven SCM > Issue Type: Bug > Components: maven-scm-provider-perforce > Environment: I tested this with whatever version came down by default > & then with the lastest svn trunk. The fixes & affects versions available in > this issue form don't seem to match the versions available. > [EMAIL PROTECTED] maven-scm-provider-perforce]$ p4 -V > Perforce - The Fast Software Configuration Management System. > Copyright 1995-2006 Perforce Software. All rights reserved. > Rev. P4/LINUX24X86/2006.1/101890 (2006/06/21). > [EMAIL PROTECTED] maven-scm-provider-perforce]$ p4 info > User name: tparker > Client name: tua > Client host: tua.uiactive.com > Client unknown. > Current directory: > /u01/tomp/maven-scm/maven-scm-providers/maven-scm-provider-perforce > Client address: 172.18.1.29:52715 > Server address: sydb.bullant.local:1666 > Server root: P:\P4ROOT > Server date: 2006/10/31 16:47:50 +1100 AUS Eastern Daylight Time > Server version: P4D/NTX86/2005.2/93627 (2006/02/14) > Server license: Bullant Software (fka Bullant Technology - fna Softblocks > Pty.) 40 users (support expired 2006/10/04) >Reporter: Tom Parker > Fix For: future > > Attachments: maven-scm-provider-perforce.patch > > > This applies to most or all commands in maven-scm-provider-perforce. I was > unable to fix some basic scm configuration issues until I downloaded the > maven-scm-provider-perforce source and hacked it to consume and report the p4 > command's stderr as well as stdout. > The attached patch fixes the problem for diff, checkin, checkout and tag. My > solution naively consumes stdout until it is finished and then consums > stderr. This isn't ideal if the output order is significant, but for the > errors situations I was dealing with, it worked fine. I had a brief search > for an InputStreamMultiplexer but found nothing. I have included todos to > improve this. > There is much potential for reuse between the classes in > maven-scm-provider-perforce, I have included todo's stating as such. > I have not fixed all the perforce commands. Sorry. -- 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] Updated: (SCM-223) VSS add command
[ http://jira.codehaus.org/browse/SCM-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated SCM-223: - Fix Version/s: future > VSS add command > --- > > Key: SCM-223 > URL: http://jira.codehaus.org/browse/SCM-223 > Project: Maven SCM > Issue Type: New Feature > Components: maven-scm-provider-vss >Reporter: Thorsten Riek > Fix For: future > > Attachments: SCM-223-02-maven-scm-provider-vss.patch, > SCM-223-03-maven-scm-provider-vss.patch, SCM-223-maven-scm-provider-vss.patch > > > Some minor changes and VSS add command implementation. -- 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] Updated: (SCM-258) The perforce provider should be able to accept complex filespecs using a clientspec rather than the path in the SCM url
[ http://jira.codehaus.org/browse/SCM-258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated SCM-258: - Fix Version/s: future > The perforce provider should be able to accept complex filespecs using a > clientspec rather than the path in the SCM url > --- > > Key: SCM-258 > URL: http://jira.codehaus.org/browse/SCM-258 > Project: Maven SCM > Issue Type: Improvement > Components: maven-scm-provider-perforce > Environment: All OS, Maven 2.x using the SCM plugin to talk to > perforce >Reporter: Dana Lacoste > Fix For: future > > > One of the strengths of perforce is the ability to do fairly complex actions > with the clientspec. > For example: > 1 - Checkout two file structures into one location: > //depot1/tree1/... //client/project/tree1 > //depot2/tree2/... //client/project/tree2 > 2 - Rename file structures at checkout time : > //depot/tree/sample-configuration.xml //client/tree/configuration.xml > The SCM URL format doesn't allow this (and implementing it would be difficult) > Currently, the perforce provider doesn't seem to allow a way to use an > existing clientspec (all codepaths seem to create a new clientspec based on > the URL) > If the provider could allow an existing clientspec to define the file > structure, this functionality could be enabled. > Testing: > I don't have any JUnit experience, but I think this could be tested by: > 1 - Create a clientspec that defines some complex content, for example: > //depot/project/src/... //clientspec/project/src/... > //ThirdParty/... //clientspec/project/ThirdParty/... > 2 - run "mvn scm:checkout" and all files should be checked out. > Implementation Ideas: > I can see multiple ways of doing this, depending on the > restrictions/conventions required > A - Use the existing "bootstrap/target/checkout" dynamic directory structure > - Using "p4 client -o" with the given/predefined/assumed clientspec, > alter the p4_root (the line containing "Root:") and do a "p4 sync -f" >(Definition of the clientspec ideas defined separately below) > B - Assume the clientspec has a defined "Root:" and use that for the purposes > of "locating" files (needed for tag/editing/checkin purposes) > - As I'm only checking out, I really don't know how this would affect a > checkin :) > C - Separate from above, how to define which clientspec to use: > - In the SCM URL, perhaps with scm:perforce:[EMAIL > PROTECTED]:port:@clientspec_name > (the second @ being a placeholder for a delimiter) > - As an environment variable (perhaps the existing > maven.scm.perforce.clientspec.name, > enabling this functionality (re-use vs. re-create) with a different > property > - Defined in the settings.xml or in the pom.xml in the SCM configuration > properties > I'm sure more details will be required, this is only what I've identified > within my particular situation. -- 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] Updated: (SCM-182) git provider
[
http://jira.codehaus.org/browse/SCM-182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Venisse updated SCM-182:
-
Fix Version/s: future
> git provider
>
>
> Key: SCM-182
> URL: http://jira.codehaus.org/browse/SCM-182
> Project: Maven SCM
> Issue Type: New Feature
> Components: maven-scm-provider-git
> Environment: Developed on Mac OS X 10.3.9 with git 1.2.4
>Reporter: Dominik Winter
> Fix For: future
>
> Attachments: git.patch, git.tar.bz2, SCM-182.patch
>
>
> Please find the git provider as attachment.
> Usefulness:
> I used the git provider together with
> [http://maven.apache.org/plugins/maven-release-plugin|maven-release-plugin],
> it works fine for that use case.
> Open issues:
> - the JUnit tests are "proprietary", not yet TCK. I'll fix that.
> If you want to run the tests, you must have git installed and it must be in
> your {{PATH}}.
> To run git:
> - on *Windows*: use [Cygwin|http://www.cygwin.com] and install the binutils,
> openssh, openssl, rsync, curl
> than you are able to compile and install git
> - on Linux: there are packages somewhere
> - on Mac OS X: use the [DarwinPorts|http://www.darwinports.org/]
--
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] Updated: (SCM-121) Intermittent CVS test failures
[ http://jira.codehaus.org/browse/SCM-121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated SCM-121: - Fix Version/s: future > Intermittent CVS test failures > -- > > Key: SCM-121 > URL: http://jira.codehaus.org/browse/SCM-121 > Project: Maven SCM > Issue Type: Bug > Components: maven-scm-provider-cvs >Affects Versions: 1.0-beta-3 >Reporter: Mike Perham > Fix For: future > > Attachments: cvs.exe > > > Dan and I continue to have test failures when trying to compile the cvs > plugin in our environment. I emailed these problems to the scm-dev list > about a week ago. -- 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] Updated: (SCM-243) SVN provider reports a warning for 'X' status as unknown, but it's an external link
[ http://jira.codehaus.org/browse/SCM-243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated SCM-243: - Fix Version/s: future > SVN provider reports a warning for 'X' status as unknown, but it's an > external link > --- > > Key: SCM-243 > URL: http://jira.codehaus.org/browse/SCM-243 > Project: Maven SCM > Issue Type: Bug > Components: maven-scm-provider-svn >Affects Versions: 1.0-beta-3 > Environment: Windows XP SP2, Sun JDK 1.4.2_12, Maven 2.0.4, SVN 1.4.0 >Reporter: Nathan Beyer (Cerner) >Priority: Minor > Fix For: future > > > When performing a 'release:prepare' on a project that contains an > 'svn:externals' linked folder, the following warnings and messages are > produced. > [INFO] Unknown file status: 'X'. > [WARNING] Unexpected input, the line must be at least seven characters long. > Line: ''. > [INFO] Unknown file status: 'P'. > I'm not sure what's causing the "unexpected input" and "P" message, but the > "X" message is from a folder in the project that is pulled into the working > copy via the svn:externals property [1]. This is an SVN property that's set > on a folder and makes the SVN client perform an additional "unversioned" > checkout of a URL. The externals will only exist in the working copy. When > the "svn status" is run on a project an external item is given the status > "X". As such, the status X can safely be ignored and treated as either "no > modification" or "ignored" would be. > Here's a dump of the help from svn status for more information. > C:\temp>svn help status > status (stat, st): Print the status of working copy files and directories. > usage: status [PATH...] > With no args, print only locally modified items (no network access). > With -u, add working revision and server out-of-date information. > With -v, print full revision information on every item. > The first six columns in the output are each one character wide: > First column: Says if item was added, deleted, or otherwise changed > ' ' no modifications > 'A' Added > 'C' Conflicted > 'D' Deleted > 'I' Ignored > 'M' Modified > 'R' Replaced > 'X' item is unversioned, but is used by an externals definition > '?' item is not under version control > > [1] > http://svnbook.red-bean.com/nightly/en/svn.advanced.props.html#svn.advanced.props.special.externals -- 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] Updated: (SCM-39) Ability to checkout/update selective modules under root
[ http://jira.codehaus.org/browse/SCM-39?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated SCM-39: Fix Version/s: future > Ability to checkout/update selective modules under root > --- > > Key: SCM-39 > URL: http://jira.codehaus.org/browse/SCM-39 > Project: Maven SCM > Issue Type: New Feature > Components: maven-scm-api >Affects Versions: 1.0-alpha-1 > Environment: XP, maven 1.0.2 >Reporter: Dan Tran > Fix For: future > > > Legacy applications contain lots of unwanted source under SCM root. > Politically, it is impossible to remove them out of system. > And therefore, checkout and update operations can be very slow. > Suggest to add "includes "excludes" to checkout/update > command interfaces to only checkout/update wanted modules/directories > under SCM root. -- 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] Updated: (SCM-133) Merge redundant repository classes
[ http://jira.codehaus.org/browse/SCM-133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated SCM-133: - Fix Version/s: future > Merge redundant repository classes > -- > > Key: SCM-133 > URL: http://jira.codehaus.org/browse/SCM-133 > Project: Maven SCM > Issue Type: Improvement > Components: maven-scm-api >Affects Versions: 1.0-beta-2 >Reporter: Mike Perham > Fix For: future > > > Currently there are: > com.apache.maven.scm.repository.ScmRepository > com.apache.maven.scm.provider.ScmProviderRepository > The comment at the top of the former says: > * @todo clarify need - should be able to merge with ScmProviderRepository? -- 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] Updated: (SCM-34) Add PVCS support
[ http://jira.codehaus.org/browse/SCM-34?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated SCM-34: Fix Version/s: future > Add PVCS support > > > Key: SCM-34 > URL: http://jira.codehaus.org/browse/SCM-34 > Project: Maven SCM > Issue Type: Improvement > Components: maven-scm-provider-pvcs > Environment: any >Reporter: Nauman > Fix For: future > > Attachments: MNG-SCM-34-maven-scm.patch, MNG-SCM-34-maven-scm.patch > > > Please add pvcs support this will increase the potential number of developers > who can use maven dramatically. > I searched through the User and Developers archives for the keyword pvcs and > did not find any reference to either 1. A request to add support or 2. A > discussion of why this support should not be added. -- 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] Updated: (SCM-267) Branches setting is being used as a tag
[ http://jira.codehaus.org/browse/SCM-267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated SCM-267: - Fix Version/s: future > Branches setting is being used as a tag > --- > > Key: SCM-267 > URL: http://jira.codehaus.org/browse/SCM-267 > Project: Maven SCM > Issue Type: Bug >Affects Versions: 1.0-beta-4 > Environment: Windows XP >Reporter: Damon Jacobsen > Fix For: future > > > Using pom build of : > > > > org.apache.maven.plugins > maven-scm-plugin > 1.0-beta-4 > > > > > > > returns : > [ERROR] svn: URL 'svn://172.22.248.151/svn/dirty/pcs/tags/premaven' doesn't > exist > as you can see.. it is looking in tags for my branch, not branches. It should > be looking in 'svn://172.22.248.151/svn/dirty/pcs/branches/premaven' -- 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] Updated: (SCM-261) Synergy provider assumes instance of 1 for projects... won't work for distributed CM (and some other scenarios)
[
http://jira.codehaus.org/browse/SCM-261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Venisse updated SCM-261:
-
Fix Version/s: future
> Synergy provider assumes instance of 1 for projects... won't work for
> distributed CM (and some other scenarios)
> ---
>
> Key: SCM-261
> URL: http://jira.codehaus.org/browse/SCM-261
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-synergy
>Affects Versions: 1.0-beta-4
> Environment: All Synergy environments
>Reporter: Body Mass
> Fix For: future
>
>
> We've started testing and hit our first snag:
> A unique locator in synergy is: ~::
> The new snergy provider appears to assume thie instance is 1, and cannot find
> projects whose instance is not 1. This is not a valid for a Distributed CM
> install, for example, where 1 cannot be the instance number as Synergy will
> not allow it. This instance can be any string, and should be specified in the
> SCM URL or some other appropriate configuration mechanism.
> For example following is a query that works against my developer workspace.
> This same funkiness for DCM also applies to task names, but I can't get that
> far in testing due to the project problem.
> ccm> query -u
> is_task_in_folder_of(is_folder_in_rp_of('Arc_Workspace~k1gmd00:project:arc#1'))
> arc#6602 completed k1gmd00 task arc
> arc#6607 completed k1gmd00 task arc
> arc#6619 completed k1jcs01 task arc
> arc#6620 completed k1jcs01 task arc
> arc#6630 completed k1gmd00 task arc
> arc#6632 completed k1gmd00 task arc
> arc#6634 completed k1jcs01 task arc
> arc#6637 completed k1gmd00 task arc
> arc#6638 completed k1gmd00 task arc
> arc#6644 completed k1jcs01 task arc
> arc#6645 completed k1jcs01 task arc
> arc#6646 completed k1gmd00 task arc
> arc#6647 completed k1jcs01 task arc
> arc#6648 completed k1gmd00 task arc
> arc#6649 completed k1jcs01 task arc
> arc#6652 completed k1gmd00 task arc
> arc#6656 completed k1gmd00 task arc
> arc#6657 completed k1jcs01 task arc
--
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] Updated: (SCM-274) Support tagging with non-standard svn repository layout
[ http://jira.codehaus.org/browse/SCM-274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated SCM-274: - Fix Version/s: future > Support tagging with non-standard svn repository layout > > > Key: SCM-274 > URL: http://jira.codehaus.org/browse/SCM-274 > Project: Maven SCM > Issue Type: Improvement > Components: maven-scm-provider-svn >Reporter: Alexander Schwartz > Fix For: future > > > There is a non-standard, but common svn repository layout & tagging/branching > convention: The repository has three top-level folders >/trunk >/branches >/tags > If a module is tagged it is copied into to the tag base followed by the tag > name and by the full module path. > Example: Assume we would like to tag version 1.1.0 of the module > org/sample/module1. We use the tag "org_sample_module1_20070118_1_1_0". > After tagging the repo looks as follows. >/trunk > /org/sample/module1/pom.xml > /branches > /tags > /org_sample_module1_20070118_1_1_0/org/sample/module1/pom.xml > (There are several good arguments for such an repository layout. > My main argument is that this layout communicates what is in a tag directory.) > The following modifications are necessary to resolve this issue: > -- A new property "modulePath" is introduced. It contains the relative > module path (here: "org/sample/module1"). > -- Before the svn tag command is executed a series of scm mkdir commands is > executed to create the parent directories. > If this issue is accepted I am going to provide a patch. -- 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] Updated: (SCM-5) Create user guide/Guide for the impatient programmer (gipper)
[ http://jira.codehaus.org/browse/SCM-5?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated SCM-5: --- Fix Version/s: 1.0 > Create user guide/Guide for the impatient programmer (gipper) > - > > Key: SCM-5 > URL: http://jira.codehaus.org/browse/SCM-5 > Project: Maven SCM > Issue Type: Task > Components: documentation >Affects Versions: 1.0-alpha-1 >Reporter: Jason van Zyl > Fix For: 1.0 > > -- 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] Updated: (SCM-209) Specifying working directory for Runtime.exec() on linux has no effect
[
http://jira.codehaus.org/browse/SCM-209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Venisse updated SCM-209:
-
Fix Version/s: future
> Specifying working directory for Runtime.exec() on linux has no effect
> --
>
> Key: SCM-209
> URL: http://jira.codehaus.org/browse/SCM-209
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-perforce
>Affects Versions: 1.0-beta-3
>Reporter: John Didion
> Assigned To: Mike Perham
> Fix For: future
>
>
> Passing the working directory as an argument to Runtime.exec seems to have no
> effect on linux...perforce still goes with whatever the VM's initial working
> directory was. You need to set -d to make it use the correct one.
> In PerforceScmProvider.createP4Command():
> command.createArgument().setValue("-d");
> command.createArgument().setValue(workingDir.getAbsolutePath());
--
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] Updated: (SCM-263) Subversion http url should support password on the url
[ http://jira.codehaus.org/browse/SCM-263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated SCM-263: - Fix Version/s: 1.0 > Subversion http url should support password on the url > -- > > Key: SCM-263 > URL: http://jira.codehaus.org/browse/SCM-263 > Project: Maven SCM > Issue Type: Bug > Components: maven-scm-provider-svn >Affects Versions: 1.0-beta-4 > Environment: xp, linux, >Reporter: Dan Tran > Fix For: 1.0 > > > both cvs and staream urls allow password on url. > currently > scm:svn:http://user:[EMAIL PROTECTED]/path see user:password as username > Having password on url simplifies lots of work my a test application i am > writing > that has no concern about password in the url > comments? why do we not support this feature to beginning with? -- 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] Updated: (SCM-6) Development/Testing guide
[ http://jira.codehaus.org/browse/SCM-6?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated SCM-6: --- Fix Version/s: 1.0 > Development/Testing guide > - > > Key: SCM-6 > URL: http://jira.codehaus.org/browse/SCM-6 > Project: Maven SCM > Issue Type: Task > Components: documentation >Affects Versions: 1.0-alpha-1 >Reporter: Jason van Zyl > Fix For: 1.0 > > > Guide on how to create new scm providers utilizing the abstract scm test case > for easy testing. -- 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] Updated: (SCM-155) Perforce instance for maven-scm testing and continuum testing
[ http://jira.codehaus.org/browse/SCM-155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated SCM-155: - Fix Version/s: 1.0 > Perforce instance for maven-scm testing and continuum testing > - > > Key: SCM-155 > URL: http://jira.codehaus.org/browse/SCM-155 > Project: Maven SCM > Issue Type: Task > Components: maven-scm-provider-perforce >Reporter: Emmanuel Venisse > Assigned To: Emmanuel Venisse > Fix For: 1.0 > > > - Install somewhere an instance of Perforce accessible for all of us > - Add documentation about install/configuration > - Add documentation about what we need on local machine for use it -- 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] Created: (SCM-284) Add a pure java cvs provider
Add a pure java cvs provider Key: SCM-284 URL: http://jira.codehaus.org/browse/SCM-284 Project: Maven SCM Issue Type: Improvement Components: maven-scm-provider-cvs Reporter: Emmanuel Venisse Fix For: 1.0 This provider is required because lot of issues appear with native cvs provider. Lot of official cvs clients doesn't understand some standard parameters -- 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] Updated: (SCM-284) Add a pure java cvs provider
[ http://jira.codehaus.org/browse/SCM-284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated SCM-284: - Fix Version/s: 1.0 > Add a pure java cvs provider > > > Key: SCM-284 > URL: http://jira.codehaus.org/browse/SCM-284 > Project: Maven SCM > Issue Type: Improvement > Components: maven-scm-provider-cvs >Reporter: Emmanuel Venisse > Fix For: 1.0 > > > This provider is required because lot of issues appear with native cvs > provider. Lot of official cvs clients doesn't understand some standard > parameters -- 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-259) Running scm:changelog after scm:update should be made configurable
[ http://jira.codehaus.org/browse/SCM-259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_89908 ] Emmanuel Venisse commented on SCM-259: -- I added a new parameter in update mojo > Running scm:changelog after scm:update should be made configurable > -- > > Key: SCM-259 > URL: http://jira.codehaus.org/browse/SCM-259 > Project: Maven SCM > Issue Type: New Feature > Components: maven-scm-api >Reporter: Jan Hoeve > Assigned To: Emmanuel Venisse >Priority: Minor > Fix For: 1.0 > > > I do have a environment with cruisecontrol as a buildserver and clearcase as > SCM provider. > One entire build loop takes half an hour to complete. This is because the > scm:update command fires an changelog command to get the changed files. > This changelog process takes about 20 minutes to complete. My clearcase view > has some 8500 files in it. > (note: changelog is fired without the startDate, bad for performance on > clearcase). > It would be very nice if there was an option i could pass to mvn scm:update > which skips the changelog process. -- 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] Updated: (SCM-259) Running scm:changelog after scm:update should be made configurable
[ http://jira.codehaus.org/browse/SCM-259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated SCM-259: - Comment: was deleted > Running scm:changelog after scm:update should be made configurable > -- > > Key: SCM-259 > URL: http://jira.codehaus.org/browse/SCM-259 > Project: Maven SCM > Issue Type: New Feature > Components: maven-scm-api >Reporter: Jan Hoeve > Assigned To: Emmanuel Venisse >Priority: Minor > Fix For: 1.0 > > > I do have a environment with cruisecontrol as a buildserver and clearcase as > SCM provider. > One entire build loop takes half an hour to complete. This is because the > scm:update command fires an changelog command to get the changed files. > This changelog process takes about 20 minutes to complete. My clearcase view > has some 8500 files in it. > (note: changelog is fired without the startDate, bad for performance on > clearcase). > It would be very nice if there was an option i could pass to mvn scm:update > which skips the changelog process. -- 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] Updated: (SCM-34) Add PVCS support
[ http://jira.codehaus.org/browse/SCM-34?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] J-C Walmetz updated SCM-34: --- Attachment: maven-scm-provider-pvcs.zip I started to implement a plugin for PVCS. I use it with the release plugin. Example for pom.xml: org.apache.maven.plugins maven-release-plugin https://svn.apache.org/repos/asf/maven/components/releases org.apache.maven.scm 1.0-beta-3 maven-scm-provider-pvcsexe ... scm:pvcs:local://IT/PROJECT/DEV:/current/Sample/trunk scm:pvcs:local://IT/PROJECT/DEV:/current/Sample/trunk > Add PVCS support > > > Key: SCM-34 > URL: http://jira.codehaus.org/browse/SCM-34 > Project: Maven SCM > Issue Type: Improvement > Components: maven-scm-provider-pvcs > Environment: any >Reporter: Nauman > Fix For: future > > Attachments: maven-scm-provider-pvcs.zip, MNG-SCM-34-maven-scm.patch, > MNG-SCM-34-maven-scm.patch > > > Please add pvcs support this will increase the potential number of developers > who can use maven dramatically. > I searched through the User and Developers archives for the keyword pvcs and > did not find any reference to either 1. A request to add support or 2. A > discussion of why this support should not be added. -- 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-34) Add PVCS support
[ http://jira.codehaus.org/browse/SCM-34?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_89910 ] Emmanuel Venisse commented on SCM-34: - Great. Can you add some tests? Did you test it with Continuum? > Add PVCS support > > > Key: SCM-34 > URL: http://jira.codehaus.org/browse/SCM-34 > Project: Maven SCM > Issue Type: Improvement > Components: maven-scm-provider-pvcs > Environment: any >Reporter: Nauman > Fix For: 1.0 > > Attachments: maven-scm-provider-pvcs.zip, MNG-SCM-34-maven-scm.patch, > MNG-SCM-34-maven-scm.patch > > > Please add pvcs support this will increase the potential number of developers > who can use maven dramatically. > I searched through the User and Developers archives for the keyword pvcs and > did not find any reference to either 1. A request to add support or 2. A > discussion of why this support should not be added. -- 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] Updated: (SCM-34) Add PVCS support
[ http://jira.codehaus.org/browse/SCM-34?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated SCM-34: Fix Version/s: (was: future) 1.0 > Add PVCS support > > > Key: SCM-34 > URL: http://jira.codehaus.org/browse/SCM-34 > Project: Maven SCM > Issue Type: Improvement > Components: maven-scm-provider-pvcs > Environment: any >Reporter: Nauman > Fix For: 1.0 > > Attachments: maven-scm-provider-pvcs.zip, MNG-SCM-34-maven-scm.patch, > MNG-SCM-34-maven-scm.patch > > > Please add pvcs support this will increase the potential number of developers > who can use maven dramatically. > I searched through the User and Developers archives for the keyword pvcs and > did not find any reference to either 1. A request to add support or 2. A > discussion of why this support should not be added. -- 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] Created: (MAVENUPLOAD-1417) Add strutstestcase-2.1.3-1.2-2.4
Add strutstestcase-2.1.3-1.2-2.4 Key: MAVENUPLOAD-1417 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1417 Project: maven-upload-requests Issue Type: Task Reporter: Victor Letunovsky Attachments: strutstestcase-2.1.3-1.2-2.4-bundle.jar Bundle attached http://strutstestcase.sourceforge.net/ StrutsTestCase for JUnit is an extension of the standard JUnit TestCase class that provides facilities for testing code based on the Struts framework. -- 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: (MAVENUPLOAD-1417) Add strutstestcase-2.1.3-1.2-2.4
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_89913 ] Victor Letunovsky commented on MAVENUPLOAD-1417: Please help me. This is very urgent for my project. > Add strutstestcase-2.1.3-1.2-2.4 > > > Key: MAVENUPLOAD-1417 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1417 > Project: maven-upload-requests > Issue Type: Task >Reporter: Victor Letunovsky > Attachments: strutstestcase-2.1.3-1.2-2.4-bundle.jar > > > Bundle attached > http://strutstestcase.sourceforge.net/ > StrutsTestCase for JUnit is an extension of the standard JUnit TestCase class > that provides facilities for testing code based on the Struts framework. -- 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: (MAVENUPLOAD-1417) Add strutstestcase-2.1.3-1.2-2.4
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_89912 ] Victor Letunovsky commented on MAVENUPLOAD-1417: URL to attached bundle: http://jira.codehaus.org/secure/attachment/26248/strutstestcase-2.1.3-1.2-2.4-bundle.jar > Add strutstestcase-2.1.3-1.2-2.4 > > > Key: MAVENUPLOAD-1417 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1417 > Project: maven-upload-requests > Issue Type: Task >Reporter: Victor Letunovsky > Attachments: strutstestcase-2.1.3-1.2-2.4-bundle.jar > > > Bundle attached > http://strutstestcase.sourceforge.net/ > StrutsTestCase for JUnit is an extension of the standard JUnit TestCase class > that provides facilities for testing code based on the Struts framework. -- 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: (MEV-510) Missing StrutsTestCase for servlet api 2.4
[ http://jira.codehaus.org/browse/MEV-510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_89914 ] Victor Letunovsky commented on MEV-510: --- Hi Carlos. I have added new issue to maven-upload-requests project: http://jira.codehaus.org/browse/MAVENUPLOAD-1417 Please help me. This is very urgent for my project. Thank you in advance! > Missing StrutsTestCase for servlet api 2.4 > -- > > Key: MEV-510 > URL: http://jira.codehaus.org/browse/MEV-510 > Project: Maven Evangelism > Issue Type: New Feature > Components: Missing POM >Reporter: Victor Letunovsky > Assigned To: Carlos Sanchez > > Missing in repository last version of StrutsTestCase 2.1.3 for JSP API 1.2 > and Servlet API 2.4. > StrutsTestCase hosted on sourceforge.net: > http://strutstestcase.sourceforge.net/ (files: > http://sourceforge.net/project/showfiles.php?group_id=39190) -- 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] Created: (SUREFIRE-308) Setting environment variables in surefire configuration overwrite the existing environment
Setting environment variables in surefire configuration overwrite the existing
environment
--
Key: SUREFIRE-308
URL: http://jira.codehaus.org/browse/SUREFIRE-308
Project: Maven Surefire
Issue Type: Bug
Components: plugin
Affects Versions: 2.3, 2.0 (2.2 plugin)
Environment: Linux
Reporter: Renaud Julienne
It's possible to set additional environment properties in surefire plugin
configuration using:
maven-surefire-plugin
value
As described in plugin documentation, this should ADD the environment variable
NAME to the existing environment when forking to launch the tests.
What happens in fact is that it completely OVERWRITE the existing environment
as soon as you use this configuration property : no more $HOME, no more $PATH,
etc... Whereas when this property is not set, the existing environment ($HOME,
$PATH, ...) remains present.
This is not critical as there is a workaround to still have $HOME or $PATH for
example by setting:
maven-surefire-plugin
value
${env.HOME}
${env.PATH}
but afaic, this remains a high issue.
I did not have time to investigate much, but it seems the problem comes from
org.codehaus.plexus.util.cli.CommandLine, so this bug may be also opened there.
--
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] Created: (MJAVADOC-115) getDocletPath does not return correct path
getDocletPath does not return correct path -- Key: MJAVADOC-115 URL: http://jira.codehaus.org/browse/MJAVADOC-115 Project: Maven 2.x Javadoc Plugin Issue Type: Bug Affects Versions: 2.0 Reporter: Mark Proctor docletArtifacts is now never null, so really need an undefined check on each array entry. Further to that docletPath should always be appened, as its additional path info, at the moment its one or the other. -- 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: (MJAVADOC-115) getDocletPath does not return correct path
[
http://jira.codehaus.org/browse/MJAVADOC-115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_89918
]
Mark Proctor commented on MJAVADOC-115:
---
Please replace the existing method with these two new methods:
/**
* Method to get the path of the doclet artifacts used in the -docletpath
option.
*
* Either docletArtifact or doclectArtifacts can be defined and used, not
both, docletArtifact
* takes precedence over doclectArtifacts. docletPath is always appended to
any result path
* definition.
*
* @return the path to jar file that contains doclet class file separated
with a colon (:)
* on Solaris and a semi-colon (;) on Windows
* @throws MavenReportException
*/
private String getDocletPath()
throws MavenReportException
{
StringBuffer path = new StringBuffer();
if ( !isDocletArtifactEmpty( docletArtifact ) )
{
path.append( getArtifactAbsolutePath( docletArtifact ) );
}
else if ( docletArtifacts != null )
{
for ( int i = 0; i < docletArtifacts.length; i++ )
{
if ( !isDocletArtifactEmpty( docletArtifacts[i] ) )
{
path.append( getArtifactAbsolutePath( docletArtifacts[i] )
);
if ( i < docletArtifacts.length - 1 )
{
path.append( File.pathSeparator );
}
}
}
}
if ( !StringUtils.isEmpty( docletPath ) )
{
path.append( docletPath );
}
if ( StringUtils.isEmpty( path.toString() ) )
{
getLog().warn( "No docletpath option was found. Please review
or "
+ " or ." );
}
return path.toString();
}
private boolean isDocletArtifactEmpty(DocletArtifact docletArtifact) {
if ( docletArtifact == null ) {
return true;
}
return ( StringUtils.isEmpty( docletArtifact.getGroupId() )
&& StringUtils.isEmpty( docletArtifact.getArtifactId() )
&& StringUtils.isEmpty( docletArtifact.getVersion() ) ) ;
}
> getDocletPath does not return correct path
> --
>
> Key: MJAVADOC-115
> URL: http://jira.codehaus.org/browse/MJAVADOC-115
> Project: Maven 2.x Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 2.0
>Reporter: Mark Proctor
>
> docletArtifacts is now never null, so really need an undefined check on each
> array entry. Further to that docletPath should always be appened, as its
> additional path info, at the moment its one or the other.
--
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] Updated: (MNG-2261) Profiles ignored when working with non-projects (such as archetype:create)
[ http://jira.codehaus.org/browse/MNG-2261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MNG-2261: -- Fix Version/s: (was: 2.0.5) 2.0.6 > Profiles ignored when working with non-projects (such as archetype:create) > -- > > Key: MNG-2261 > URL: http://jira.codehaus.org/browse/MNG-2261 > Project: Maven 2 > Issue Type: Bug > Components: General >Affects Versions: 2.0.4 >Reporter: Joakim Erdfelt > Assigned To: John Casey >Priority: Blocker > Fix For: 2.0.6 > > Attachments: MNG-2261-2.patch, MNG-2261.patch > > > Several conditions have to be met to show this bug. > 1) Be in an environment that does not have access to repo1.maven.org, (such > as a corporate environment) > 2) Have no content in your local repository (a fresh install of maven 2.0.4) > 3) Attempt to use a plugin that has no project requirement (such as > archetype:create) > The plugin fails because access to repo1.maven.org cannot be accessed. > Recommended solution: > Create a settings.xml profile that changes the location of the 'central' > repository to point to an internal resource (such as a maven-proxy > installation). > > > > use_internal > > > central > Internal Central Repository > http://repo.internal.com/maven2 > > true > > > true > > > > > > central > Internal Central Repository > http://repo.internal.com/maven2 > > true > > > true > > > > > > > use_internal > > > Try again. > Still fails. > The reason is that the default behaviour for non-project execution is to use > the maven super pom, however there is a bug with that flow that does not > allow for the merging of the settings.xml profiles. -- 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: (MAVENUPLOAD-1412) Springframework repository sync
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_89927 ] Carlos Sanchez commented on MAVENUPLOAD-1412: - we just sync from spring repo, anything related to org/springframework please ask them http://opensource.atlassian.com/projects/spring/browse/SPR > Springframework repository sync > --- > > Key: MAVENUPLOAD-1412 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1412 > Project: maven-upload-requests > Issue Type: Task >Reporter: Avi Cherry > Assigned To: Carlos Sanchez > > It appears that the spring framework is not being automatically synced with > the project's repository. The included URL points at the project's maven > repository. Thanks. -- 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: (MAVENUPLOAD-1417) Add strutstestcase-2.1.3-1.2-2.4
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_89941 ] Carlos Sanchez commented on MAVENUPLOAD-1417: - Missing many required info in pom http://maven.apache.org/guides/mini/guide-central-repository-upload.html > Add strutstestcase-2.1.3-1.2-2.4 > > > Key: MAVENUPLOAD-1417 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1417 > Project: maven-upload-requests > Issue Type: Task >Reporter: Victor Letunovsky > Attachments: strutstestcase-2.1.3-1.2-2.4-bundle.jar > > > Bundle attached > http://strutstestcase.sourceforge.net/ > StrutsTestCase for JUnit is an extension of the standard JUnit TestCase class > that provides facilities for testing code based on the Struts framework. -- 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] Created: (MAVENUPLOAD-1418) resultsetmapper 0.2
resultsetmapper 0.2 --- Key: MAVENUPLOAD-1418 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1418 Project: maven-upload-requests Issue Type: Bug Reporter: Tomislav Stojcevich Attachments: resultsetmapper-0.2-bundle.jar Upload -- 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] Closed: (MAVENUPLOAD-1416) eva-properties-0.2.2
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1416. --- Assignee: Carlos Sanchez Resolution: Fixed > eva-properties-0.2.2 > > > Key: MAVENUPLOAD-1416 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1416 > Project: maven-upload-requests > Issue Type: Task >Reporter: Maximilian Antoni > Assigned To: Carlos Sanchez > > Thank you for uploading. -- 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: (MAVENUPLOAD-1395) Maven-jlex is a maven plugin for jlex, a lexical analyzer generator for Java.
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_89942 ] Carlos Sanchez commented on MAVENUPLOAD-1395: - ERROR 404: Not Found. > Maven-jlex is a maven plugin for jlex, a lexical analyzer generator for Java. > - > > Key: MAVENUPLOAD-1395 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1395 > Project: maven-upload-requests > Issue Type: Task >Reporter: Kevin Conaway > > http://maven-jlex.sourceforge.net/maven-jlex-plugin-1.0-bundle.jar > http://maven-jlex.sourceforge.net/ > http://maven-jlex.sourceforge.net/team-list.html > Maven-jlex is a maven plugin for jlex, a lexical analyzer generator for Java. > It allows users to integreate the generation of lexical analyzers into the > maven build lifecycle -- 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: (MAVENUPLOAD-1415) rails-integration for jruby-extras
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_89943 ] Carlos Sanchez commented on MAVENUPLOAD-1415: - so your groupId should be org.rubyforge.jruby-extras > rails-integration for jruby-extras > -- > > Key: MAVENUPLOAD-1415 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1415 > Project: maven-upload-requests > Issue Type: Task >Reporter: Robert Egglestone > > Please place this release in the maven repository. > It's an add-on for JRuby, hosted as part of ruby-extras. > Release notes: > Java web applications are typically packaged as WAR files in preparation for > distribution and deployment to J2EE servers. Rails Integration allows the > packaging of Ruby on Rails applications in a similar form, to enable seamless > deployment to Java servers. > Documentation can be found at > http://www.headius.com/jrubywiki/index.php/Rails_Integration -- 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] Closed: (MAVENUPLOAD-1414) jline-0.9.91
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1414. --- Assignee: Carlos Sanchez Resolution: Fixed > jline-0.9.91 > > > Key: MAVENUPLOAD-1414 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1414 > Project: maven-upload-requests > Issue Type: Task >Reporter: Marc Prud'hommeaux > Assigned To: Carlos Sanchez > > JLine is a popular Java library for handling console input. It is similar in > functionality to BSD editline and GNU readline. People familiar with the > readline/editline capabilities for modern shells (such as bash and tcsh) will > find most of the command editing features of JLine to be familiar. > FTR, the previous release (0.9.9) was uploaded based on a request at > http://jira.codehaus.org/browse/MAVENUPLOAD-1003 -- 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: (MCHECKSTYLE-54) checkstyle:check does not see provided scope dependencies
[ http://jira.codehaus.org/browse/MCHECKSTYLE-54?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_89944 ] Yoav Shapira commented on MCHECKSTYLE-54: - I didn't have includeTestSourceDirectory set before. Now I've tried setting it, and it makes no difference. > checkstyle:check does not see provided scope dependencies > - > > Key: MCHECKSTYLE-54 > URL: http://jira.codehaus.org/browse/MCHECKSTYLE-54 > Project: Maven 2.x Checkstyle Plugin > Issue Type: Bug >Affects Versions: 2.1 >Reporter: Stephen Duncan Jr >Priority: Critical > > Running checkstyle:check against a project that uses Exceptions from > dependencies that are provided scope causes checktyle errors such as the > following: > name="/share/duncans/workspace/eclipse/cdcie-webapp-feedreader/src/main/java/mil/jfcom/cie/portal/feedreader/converter/ConverterImpl.java"> > > These errors go away when the scope is changed to compile. This does not > happen for checkstyle:checkstyle; the report correct indicates no checkstyle > errors. This is preventing us from using the checkstyle plugin to enforce > checkstyle rules. -- 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] Closed: (MEV-455) bad checksums on repo1.maven.org
[ http://jira.codehaus.org/browse/MEV-455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MEV-455. -- Assignee: Carlos Sanchez (was: Daniel Kulp) Resolution: Fixed removed checksums from central to get them again from apache > bad checksums on repo1.maven.org > > > Key: MEV-455 > URL: http://jira.codehaus.org/browse/MEV-455 > Project: Maven Evangelism > Issue Type: Bug >Reporter: nicolas de loof > Assigned To: Carlos Sanchez > > I'm using Archiva as a maven proxy, that verify checksums when downloading > artifact. My archiva.log shwo some invalid checksum on http://repo1.maven.org > : > commons-chain/commons-chain/1.1/commons-chain-1.1.pom > org/codehaus/plexus/plexus-compiler/1.5.2/plexus-compiler-1.5.2.pom > commons-validator/commons-validator/1.3.0/commons-validator-1.3.0-sources.jar > struts/struts/1.2.9/struts-1.2.9-sources.jar > junit/junit/3.8.2/junit-3.8.2.pom > junit/junit/3.8.2/junit-3.8.2.jar > junit/junit/3.8.2/junit-3.8.2-sources.jar > junit/junit/3.8.2/junit-3.8.2-javadoc.jar > easymock/easymock/1.2_Java1.3/easymock-1.2_Java1.3-sources.jar > org/codehaus/plexus/plexus-compilers/1.5.2/plexus-compilers-1.5.2.pom > org/apache/maven/surefire/surefire-providers/2.0/surefire-providers-2.0.pom > org/apache/maven/plugins/maven-project-info-reports-plugin/maven-metadata.xml > it/could/webdav/0.4/webdav-0.4.pom > com/jcraft/jsch/0.1.27/jsch-0.1.27.pom > com/jcraft/jsch/0.1.27/jsch-0.1.27.jar > it/could/webdav/0.4/webdav-0.4.pom > it/could/webdav/0.4/webdav-0.4.jar -- 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: (CONTINUUM-961) Increase transaction isolation level
[ http://jira.codehaus.org/browse/CONTINUUM-961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_89947 ] thierry lach commented on CONTINUUM-961: I think that this should be moved to alpha-1. There's already a patch, and I suspect (but am not sure) that CONTINUUM-1181 (Postgres abort) will require this in order to work, in addition to using JPOX 1.1.7 > Increase transaction isolation level > > > Key: CONTINUUM-961 > URL: http://jira.codehaus.org/browse/CONTINUUM-961 > Project: Continuum > Issue Type: Improvement > Components: Database >Affects Versions: 1.0.3 >Reporter: Carlos Sanchez > Fix For: 1.1-alpha-2 > > Attachments: continuum_tx_isolation.patch, > continuum_tx_isolation.patch > > > we are using a too low one, read uncommitted > Postgres doesn't even support it, only Read Committed and Serializable > http://www.postgresql.org/docs/7.4/interactive/transaction-iso.html -- 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: (MAVENUPLOAD-1417) Add strutstestcase-2.1.3-1.2-2.4
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_89953 ] Victor Letunovsky commented on MAVENUPLOAD-1417: I'm sorry, but I thought that I should use pom's from previous versions of StrutsTestCase: http://mirrors.ibiblio.org/pub/mirrors/maven2/strutstestcase/strutstestcase/1.9-1.1-2.3/strutstestcase-1.9-1.1-2.3.pom http://mirrors.ibiblio.org/pub/mirrors/maven2/strutstestcase/strutstestcase/2.0-1.1-2.3/strutstestcase-2.0-1.1-2.3.pom http://mirrors.ibiblio.org/pub/mirrors/maven2/strutstestcase/strutstestcase/2.1-1.1-2.2/strutstestcase-2.1-1.1-2.2.pom http://mirrors.ibiblio.org/pub/mirrors/maven2/strutstestcase/strutstestcase/2.1-1.1-2.3/strutstestcase-2.1-1.1-2.3.pom http://mirrors.ibiblio.org/pub/mirrors/maven2/strutstestcase/strutstestcase/2.1.2-1.1-2.3/strutstestcase-2.1.2-1.1-2.3.pom Ok. I added to pom tags , and dependency to javax.servlet 2.4. New bundle is attached. Please, let me know if this information is not enough. Thank you! > Add strutstestcase-2.1.3-1.2-2.4 > > > Key: MAVENUPLOAD-1417 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1417 > Project: maven-upload-requests > Issue Type: Task >Reporter: Victor Letunovsky > Attachments: strutstestcase-2.1.3-1.2-2.4-bundle.jar > > > Bundle attached > http://strutstestcase.sourceforge.net/ > StrutsTestCase for JUnit is an extension of the standard JUnit TestCase class > that provides facilities for testing code based on the Struts framework. -- 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] Updated: (MAVENUPLOAD-1417) Add strutstestcase-2.1.3-1.2-2.4
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Victor Letunovsky updated MAVENUPLOAD-1417: --- Attachment: strutstestcase-2.1.3-1.2-2.4-bundle.jar New bundle with fixed pom. > Add strutstestcase-2.1.3-1.2-2.4 > > > Key: MAVENUPLOAD-1417 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1417 > Project: maven-upload-requests > Issue Type: Task >Reporter: Victor Letunovsky > Attachments: strutstestcase-2.1.3-1.2-2.4-bundle.jar, > strutstestcase-2.1.3-1.2-2.4-bundle.jar > > > Bundle attached > http://strutstestcase.sourceforge.net/ > StrutsTestCase for JUnit is an extension of the standard JUnit TestCase class > that provides facilities for testing code based on the Struts framework. -- 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: (MAVENUPLOAD-1417) Add strutstestcase-2.1.3-1.2-2.4
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_89955 ] Victor Letunovsky commented on MAVENUPLOAD-1417: New bundle with fixed pom: http://jira.codehaus.org/secure/attachment/26253/strutstestcase-2.1.3-1.2-2.4-bundle.jar > Add strutstestcase-2.1.3-1.2-2.4 > > > Key: MAVENUPLOAD-1417 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1417 > Project: maven-upload-requests > Issue Type: Task >Reporter: Victor Letunovsky > Attachments: strutstestcase-2.1.3-1.2-2.4-bundle.jar, > strutstestcase-2.1.3-1.2-2.4-bundle.jar > > > Bundle attached > http://strutstestcase.sourceforge.net/ > StrutsTestCase for JUnit is an extension of the standard JUnit TestCase class > that provides facilities for testing code based on the Struts framework. -- 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] Updated: (CONTINUUM-961) Increase transaction isolation level
[ http://jira.codehaus.org/browse/CONTINUUM-961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell updated CONTINUUM-961: -- Assignee: Jesse McConnell Fix Version/s: (was: 1.1-alpha-2) 1.1-alpha-1 I'll buy that, testing it in redback now and I'll put it into continuum if everything passes > Increase transaction isolation level > > > Key: CONTINUUM-961 > URL: http://jira.codehaus.org/browse/CONTINUUM-961 > Project: Continuum > Issue Type: Improvement > Components: Database >Affects Versions: 1.0.3 >Reporter: Carlos Sanchez > Assigned To: Jesse McConnell > Fix For: 1.1-alpha-1 > > Attachments: continuum_tx_isolation.patch, > continuum_tx_isolation.patch > > > we are using a too low one, read uncommitted > Postgres doesn't even support it, only Read Committed and Serializable > http://www.postgresql.org/docs/7.4/interactive/transaction-iso.html -- 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] Closed: (MPPMD-29) Upgrade to PMD 3.9
[ http://jira.codehaus.org/browse/MPPMD-29?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Theussl closed MPPMD-29. -- Resolution: Fixed > Upgrade to PMD 3.9 > -- > > Key: MPPMD-29 > URL: http://jira.codehaus.org/browse/MPPMD-29 > Project: maven-pmd-plugin > Issue Type: Task >Affects Versions: 1.9 >Reporter: Anthony Whitford > Assigned To: Jeff Jensen > Fix For: 1.10 > > Attachments: maven-pmd-plugin-1.10.jar, maven1-pmd-plugin.zip > > > PMD 3.8 was released October 4, 2006. The Maven plugin should be updated too. > http://sourceforge.net/project/shownotes.php?release_id=452776&group_id=56262 -- 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: (MAVENUPLOAD-1282) PMD 3.9 bundle
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_89958 ] Lukas Theussl commented on MAVENUPLOAD-1282: asm-3.0 is now synced apparently, I think this issue can be closed? > PMD 3.9 bundle > -- > > Key: MAVENUPLOAD-1282 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1282 > Project: maven-upload-requests > Issue Type: Task >Reporter: Tom Copeland > Assigned To: Carlos Sanchez > > PMD is a Java source code analyzer. It finds unused variables, empty catch > blocks, unnecessary object creation, and so forth. -- 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] Created: (MAVEN-1838) Upgrade maven-pmd-plugin to v 1.10
Upgrade maven-pmd-plugin to v 1.10 --- Key: MAVEN-1838 URL: http://jira.codehaus.org/browse/MAVEN-1838 Project: Maven 1.x Issue Type: Sub-task Affects Versions: 1.1-beta-3 Reporter: Lukas Theussl Fix For: 1.1-rc1 -- 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] Updated: (MAVEN-1838) Upgrade maven-pmd-plugin to v 1.10
[ http://jira.codehaus.org/browse/MAVEN-1838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Theussl updated MAVEN-1838: - Assignee: Lukas Theussl Description: http://jira.codehaus.org/browse/MPPMD?report=com.atlassian.jira.plugin.system.project:roadmap-panel Affects Version/s: 1.1-beta-3 Fix Version/s: 1.1-rc1 > Upgrade maven-pmd-plugin to v 1.10 > --- > > Key: MAVEN-1838 > URL: http://jira.codehaus.org/browse/MAVEN-1838 > Project: Maven 1.x > Issue Type: Sub-task >Affects Versions: 1.1-beta-3 >Reporter: Lukas Theussl > Assigned To: Lukas Theussl > Fix For: 1.1-rc1 > > > http://jira.codehaus.org/browse/MPPMD?report=com.atlassian.jira.plugin.system.project:roadmap-panel -- 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-34) Add PVCS support
[ http://jira.codehaus.org/browse/SCM-34?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_89959 ] J-C Walmetz commented on SCM-34: I'll try to add some junit tests (not before one or two weeks). Problem is that tests uses a local install of PVCS (not so easy to execute if you do not have PVCS license). Today my tests are based on a sample project. I use the release plugin to tests my PVCS plugin. That's definitively not unit tests. I'll try to write unit tests and some documentation for the site plugin just to explain what is implemented and what is not implemented. I do not use Continuum > Add PVCS support > > > Key: SCM-34 > URL: http://jira.codehaus.org/browse/SCM-34 > Project: Maven SCM > Issue Type: Improvement > Components: maven-scm-provider-pvcs > Environment: any >Reporter: Nauman > Fix For: 1.0 > > Attachments: maven-scm-provider-pvcs.zip, MNG-SCM-34-maven-scm.patch, > MNG-SCM-34-maven-scm.patch > > > Please add pvcs support this will increase the potential number of developers > who can use maven dramatically. > I searched through the User and Developers archives for the keyword pvcs and > did not find any reference to either 1. A request to add support or 2. A > discussion of why this support should not be added. -- 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] Created: (MNG-2873) Unable to find transitive dependencies when they have been relocated.
Unable to find transitive dependencies when they have been relocated. - Key: MNG-2873 URL: http://jira.codehaus.org/browse/MNG-2873 Project: Maven 2 Issue Type: Bug Components: Artifacts and Repositories Affects Versions: 2.0.5 Reporter: Micah Whitacre I have two projects A and B. Project A is dependent on B. Project B has compile time on project C which is deployed to a repository, repository1. The newest version, 2.0, of project C has since been relocated from oldGroupId to newGroupId. The relocation POMs are working correctly and Project B is able to be built successfully. Project A is not dependent on anything from repository1 it does not list that repository in its own section. When building project A, it tries to resolve the dependencies of B which includes C. However I am currently getting errors when it tries to resolve the C. Below is an example of this error occurring. As you can see the list of remote repositories does not display repository1 as one of the repositories that was checked despite the fact that Project B listed it in its POM. [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. No versions are present in the repository for the artifact with a range [1,) oldGroupId:projectC:jar:null from the specified remote repositories: central (http://repo1.maven.org/maven2), repo2 (http://repo.some-repo.com/repo) If I change project B to not use a range but to instead depend on a non-relocated version of project C everything works fine and I do not get this issue at all. The other and more correct solution to this issue is to update project B to use the new groupIds however it forces me to release project B immediately since all older released versions of B are broken by using the old groupIds an this issue. -- 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-34) Add PVCS support
[ http://jira.codehaus.org/browse/SCM-34?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_89960 ] Emmanuel Venisse commented on SCM-34: - we have two levels of test. The first level is for simple tests that test command line used in specific contexts. This level doesn't require PVCS. It's required so every people can run them The second level is an implementation of our TCK. The TCK is in maven-scm-test module. TCK tests need to use directly the scm tool (PVCS), so all commands are validated like we want. Even if we don't have a PVCS license, it's good to put them in svn, with them, if an other PVCS user want to help, he'll can run them too. > Add PVCS support > > > Key: SCM-34 > URL: http://jira.codehaus.org/browse/SCM-34 > Project: Maven SCM > Issue Type: Improvement > Components: maven-scm-provider-pvcs > Environment: any >Reporter: Nauman > Fix For: 1.0 > > Attachments: maven-scm-provider-pvcs.zip, MNG-SCM-34-maven-scm.patch, > MNG-SCM-34-maven-scm.patch > > > Please add pvcs support this will increase the potential number of developers > who can use maven dramatically. > I searched through the User and Developers archives for the keyword pvcs and > did not find any reference to either 1. A request to add support or 2. A > discussion of why this support should not be added. -- 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-34) Add PVCS support
[ http://jira.codehaus.org/browse/SCM-34?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_89962 ] J-C Walmetz commented on SCM-34: OK, I'll have a look to existing tests for Perforce for example. I suppose that the same problem. > Add PVCS support > > > Key: SCM-34 > URL: http://jira.codehaus.org/browse/SCM-34 > Project: Maven SCM > Issue Type: Improvement > Components: maven-scm-provider-pvcs > Environment: any >Reporter: Nauman > Fix For: 1.0 > > Attachments: maven-scm-provider-pvcs.zip, MNG-SCM-34-maven-scm.patch, > MNG-SCM-34-maven-scm.patch > > > Please add pvcs support this will increase the potential number of developers > who can use maven dramatically. > I searched through the User and Developers archives for the keyword pvcs and > did not find any reference to either 1. A request to add support or 2. A > discussion of why this support should not be added. -- 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] Closed: (MAVENUPLOAD-1282) PMD 3.9 bundle
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1282. --- Resolution: Fixed > PMD 3.9 bundle > -- > > Key: MAVENUPLOAD-1282 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1282 > Project: maven-upload-requests > Issue Type: Task >Reporter: Tom Copeland > Assigned To: Carlos Sanchez > > PMD is a Java source code analyzer. It finds unused variables, empty catch > blocks, unnecessary object creation, and so forth. -- 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: (MAVENUPLOAD-1415) rails-integration for jruby-extras
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_89963 ] Robert Egglestone commented on MAVENUPLOAD-1415: Rubyforge is just a hosting environment, and we wouldn't want to have to change the groupId if we happened to host it elsewhere. Would it help if I asked for http://jruby.org/extras to be setup as a redirect to http://rubyforge.org/projects/jruby-extras? > rails-integration for jruby-extras > -- > > Key: MAVENUPLOAD-1415 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1415 > Project: maven-upload-requests > Issue Type: Task >Reporter: Robert Egglestone > > Please place this release in the maven repository. > It's an add-on for JRuby, hosted as part of ruby-extras. > Release notes: > Java web applications are typically packaged as WAR files in preparation for > distribution and deployment to J2EE servers. Rails Integration allows the > packaging of Ruby on Rails applications in a similar form, to enable seamless > deployment to Java servers. > Documentation can be found at > http://www.headius.com/jrubywiki/index.php/Rails_Integration -- 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] Closed: (CONTINUUM-961) Increase transaction isolation level
[ http://jira.codehaus.org/browse/CONTINUUM-961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell closed CONTINUUM-961. - Resolution: Fixed applied, thanks much...I'll edit the commit message back in to give credit, sorry about that :P > Increase transaction isolation level > > > Key: CONTINUUM-961 > URL: http://jira.codehaus.org/browse/CONTINUUM-961 > Project: Continuum > Issue Type: Improvement > Components: Database >Affects Versions: 1.0.3 >Reporter: Carlos Sanchez > Assigned To: Jesse McConnell > Fix For: 1.1-alpha-1 > > Attachments: continuum_tx_isolation.patch, > continuum_tx_isolation.patch > > > we are using a too low one, read uncommitted > Postgres doesn't even support it, only Read Committed and Serializable > http://www.postgresql.org/docs/7.4/interactive/transaction-iso.html -- 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: (MPPMD-30) Cannot run pmd with Strings rulesets
[
http://jira.codehaus.org/browse/MPPMD-30?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_89968
]
Lukas Theussl commented on MPPMD-30:
Oro is not needed anymore by pmd-3.9, see
http://sourceforge.net/project/shownotes.php?release_id=472435&group_id=56262
and MPPMD-29.
> Cannot run pmd with Strings rulesets
>
>
> Key: MPPMD-30
> URL: http://jira.codehaus.org/browse/MPPMD-30
> Project: maven-pmd-plugin
> Issue Type: Bug
>Affects Versions: 1.9
>Reporter: Lukas Theussl
> Assigned To: Lukas Theussl
> Fix For: 1.10
>
>
> Setting maven.pmd.rulesetfiles=rulesets/strings.xml (which is supported
> according to the faq), the build fails with
> {noformat}
> java.lang.NoClassDefFoundError: org/apache/oro/text/perl/Perl5Util
> {noformat}
> A dependency on oro has to be added.
--
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: (CONTINUUM-1181) Continuum aborts when running Postgres under JBoss
[ http://jira.codehaus.org/browse/CONTINUUM-1181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_89971 ] thierry lach commented on CONTINUUM-1181: - JPOX 1.1.7 does not resolve this issue. Current stack trace from JBoss logs: 2007-03-13 17:33:32,201 [main] INFO ContinuumInitializer:default - Continuum initializer running ... 2007-03-13 17:33:32,201 [main] ERROR [/continuum] - Exception sending context initialized event to listener instance of class org.codehaus.plexus.xwork.PlexusLifecycleListener javax.jdo.JDODataStoreException: Transaction failed to start at org.jpox.store.rdbms.RDBMSNonmanagedTransaction.begin(RDBMSNonmanagedTransaction.java:344) at org.codehaus.plexus.jdo.PlexusJdoUtils.getAllObjectsDetached(PlexusJdoUtils.java:356) at org.codehaus.plexus.jdo.PlexusJdoUtils.getAllObjectsDetached(PlexusJdoUtils.java:346) at org.apache.maven.continuum.store.JdoContinuumStore.getAllObjectsDetached(JdoContinuumStore.java:1302) at org.apache.maven.continuum.store.JdoContinuumStore.getAllObjectsDetached(JdoContinuumStore.java:1287) at org.apache.maven.continuum.store.JdoContinuumStore.getAllObjectsDetached(JdoContinuumStore.java:1282) at org.apache.maven.continuum.store.JdoContinuumStore.getAllObjectsDetached(JdoContinuumStore.java:1277) at org.apache.maven.continuum.store.JdoContinuumStore.getSystemConfiguration(JdoContinuumStore.java:1375) at org.apache.maven.continuum.initialization.DefaultContinuumInitializer.initialize(DefaultContinuumInitializer.java:90) at org.apache.maven.continuum.DefaultContinuum.start(DefaultContinuum.java:2310) at org.codehaus.plexus.personality.plexus.lifecycle.phase.StartPhase.execute(StartPhase.java:33) at org.codehaus.plexus.lifecycle.AbstractLifecycleHandler.start(AbstractLifecycleHandler.java:130) at org.codehaus.plexus.component.manager.AbstractComponentManager.startComponentLifecycle(AbstractComponentManager.java:143) at org.codehaus.plexus.component.manager.AbstractComponentManager.createComponentInstance(AbstractComponentManager.java:133) at org.codehaus.plexus.component.manager.ClassicSingletonComponentManager.getComponent(ClassicSingletonComponentManager.java:87) at org.codehaus.plexus.DefaultComponentLookupManager.lookup(DefaultComponentLookupManager.java:101) at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:310) at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:291) at org.codehaus.plexus.container.initialization.StartLoadOnStartComponentsPhase.execute(StartLoadOnStartComponentsPhase.java:54) at org.codehaus.plexus.DefaultPlexusContainer.initializePhases(DefaultPlexusContainer.java:895) at org.codehaus.plexus.DefaultPlexusContainer.initialize(DefaultPlexusContainer.java:843) at org.codehaus.plexus.DefaultPlexusContainer.construct(DefaultPlexusContainer.java:820) at org.codehaus.plexus.DefaultPlexusContainer.(DefaultPlexusContainer.java:222) at org.codehaus.plexus.DefaultPlexusContainer.(DefaultPlexusContainer.java:236) at org.codehaus.plexus.xwork.PlexusLifecycleListener.contextInitialized(PlexusLifecycleListener.java:76) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3763) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4211) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:759) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:739) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.commons.modeler.BaseModelMBean.invoke(BaseModelMBean.java:503) at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.apache.catalina.core.StandardContext.init(StandardContext.java:5052) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.commons.modeler.BaseModelMBean.invoke(BaseModelMBean.java:503) at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164)
