[continuum build trunk - SUCCESS - checkout] Mon Feb 27 01:00:00 GMT 2006
Distribution: http://maven.zones.apache.org/~continuum/builds/trunk/continuum-20060227.010001.war Log: http://maven.zones.apache.org/~continuum/logs/trunk/continuum-build-log-20060227.010001.txt
[continuum build branches/continuum-1.0.x - FAILED - checkout] Mon Feb 27 02:00:00 GMT 2006
Log: http://maven.zones.apache.org/~continuum/logs/branches/continuum-1.0.x/continuum-build-log-20060227.02.txt
[continuum build trunk - FAILED - update] Mon Feb 27 03:00:02 GMT 2006
Log: http://maven.zones.apache.org/~continuum/logs/trunk/continuum-build-log-20060227.030002.txt
[continuum build branches/continuum-1.0.x - SUCCESS - update] Mon Feb 27 03:30:02 GMT 2006
Distribution: http://maven.zones.apache.org/~continuum/builds/branches/continuum-1.0.x/continuum-20060227.033002.tar.gz Log: http://maven.zones.apache.org/~continuum/logs/branches/continuum-1.0.x/continuum-build-log-20060227.033002.txt
[continuum build trunk - SUCCESS - update] Mon Feb 27 04:00:00 GMT 2006
Distribution: http://maven.zones.apache.org/~continuum/builds/trunk/continuum-20060227.040001.war Log: http://maven.zones.apache.org/~continuum/logs/trunk/continuum-build-log-20060227.040001.txt
[jira] Commented: (SCM-165) PerforceChangeLogCommand needs to use the same clientspec as the update command
[ http://jira.codehaus.org/browse/SCM-165?page=comments#action_59517 ] Mike Perham commented on SCM-165: - I don't see how I can make this work in all cases without forcing the user to provide a parameter or use something like the release.properties file that the release plugin uses. I will brainstorm tonight and come up with the best compromise I can. PerforceChangeLogCommand needs to use the same clientspec as the update command --- Key: SCM-165 URL: http://jira.codehaus.org/browse/SCM-165 Project: Maven SCM Type: Bug Components: maven-scm-provider-perforce Versions: 1.0 Reporter: John Didion Assignee: Mike Perham Priority: Critical Attachments: PerforceChangeLogCommand.diff, svn.diff The PerforceChangeLogCommand as written does not work if the update was done with the client spec generated by the checkout/update command. The attached diff will fix the problem. -- 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-2050) Classloader.getResource() doesn't encode blanks
[ http://jira.codehaus.org/browse/MNG-2050?page=comments#action_59505 ] Roland Kofler commented on MNG-2050: This is an java issue since 1.4, long discussed. Sun argue that it is not a bug but a feature ;-) http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4466485 It raised some controversity. I think that mavens classloader should be consistent to suns policy. Classloader.getResource() doesn't encode blanks --- Key: MNG-2050 URL: http://jira.codehaus.org/browse/MNG-2050 Project: Maven 2 Type: Bug Components: General Versions: 2.0.1 Environment: win xp Reporter: Roland Kofler When I'm executing an getClass().getClassLoader().getResource(s); it gives back an URL encoded string in eclipse while Maven2 gives me blanks in my URL: * eclipse file:/C:/Dokumente%20und%20Einstellungen/roland.kofler/systemone/core/target/test-classes/fsm.jpg *maven2 file:/C:/Dokumente und Einstellungen/roland.kofler/systemone/core/target/test-classes/fsm.jpg MY PROBLEM WITH THIS: Because of this behaviour a new URI(file:/C:/Dokumente und Einstellungen/roland.kofler/systemone/core/target/test-classes/fsm.jpg) throws a URISyntaxException. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[repository] Found intermittant issue with disappearing commons-daemon pom
Hi all, I found the cause of builds at the directory project bombing out intermittently due to a missing commons-daemon pom. The pom was there but seems to disappear on occasion. I think this may have something to do with the sync process. Here's what a listing of the daemon area looks like right now: Index of /maven2/commons-daemon/commons-daemon Name http://www.ibiblio.org/maven2/commons-daemon/commons-daemon/?N=D Last modified http://www.ibiblio.org/maven2/commons-daemon/commons-daemon/?M=A Size http://www.ibiblio.org/maven2/commons-daemon/commons-daemon/?S=A Description http://www.ibiblio.org/maven2/commons-daemon/commons-daemon/?D=A [DIR] Parent Directory http://www.ibiblio.org/maven2/commons-daemon/01-Nov-2005 00:12 - [ ] maven-metadata.xml http://www.ibiblio.org/maven2/commons-daemon/commons-daemon/maven-metadata.xml 20-Sep-2005 01:46 1k [ ] maven-metadata.xml.md5 http://www.ibiblio.org/maven2/commons-daemon/commons-daemon/maven-metadata.xml.md5 20-Sep-2005 01:46 1k [ ] maven-metadata.xml.sha1 http://www.ibiblio.org/maven2/commons-daemon/commons-daemon/maven-metadata.xml.sha1 20-Sep-2005 01:46 1k As you can see the pom is no where to be found. Any ideas regarding what's going on? Thanks, Alex Karasulu - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [ibiblio] Upload request for apacheds 1.0-RC1 release
Thanks! Brett Porter wrote: Done. Alex Karasulu wrote: Hiya, The directory team just released 1.0-RC1 it's up here and signed: http://www.apache.org/dist/maven-repository/org/apache/directory/ Could it be uploaded to the repo at ibiblio.org? Thanks, Alex - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: surefire refactoring
Brett Porter wrote: Hi, I have created branches for the test ng support, because it's not really production ready as at the patch Jesse K provided. We've been working through it. I will likely complete it tomorrow, and it will include some refactoring to turn surefire into a provider infrastructure. I'll coordinate with Jason as I think he is expecting to do the same thing. You mean the same pattern as Wagon and SCM? I was just going to bite the bullet and use Plexus as well. Sounds good to me. - Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MSUREFIRE-60) workingDirectory in fork mode is not working
[ http://jira.codehaus.org/browse/MSUREFIRE-60?page=all ] Jason van Zyl closed MSUREFIRE-60: -- Resolution: Fixed Patch applied. workingDirectory in fork mode is not working Key: MSUREFIRE-60 URL: http://jira.codehaus.org/browse/MSUREFIRE-60 Project: Maven 2.x Surefire Plugin Type: Bug Versions: 2.1.3 Environment: xp, linux Reporter: Dan Tran Assignee: Jason van Zyl Priority: Blocker Fix For: 2.1.3 Attachments: MSUREFIRE-60.patch MSUREFIRE-52 resets jvm working directory (user.dir) to the old value. We need to make sure cli's workingDirectory and system property's user.dir to have the same value in fork mode -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNG-2050) Classloader.getResource() doesn't encode blanks
[ http://jira.codehaus.org/browse/MNG-2050?page=comments#action_59519 ] Gili commented on MNG-2050: --- I don't think there is a controversity at all. ClassLoader.getResource() returns a URL. A URL *must* encode spaces using %20 to be valid. The only thing that might be controversial is whether constructing a File out of a URL which contains %20 should automatically translate those %20 back to a space. I happen to think so, but this still has nothing to do with ClassLoader.getResource() -- it *has* to encode spaces to %20. Classloader.getResource() doesn't encode blanks --- Key: MNG-2050 URL: http://jira.codehaus.org/browse/MNG-2050 Project: Maven 2 Type: Bug Components: General Versions: 2.0.1 Environment: win xp Reporter: Roland Kofler When I'm executing an getClass().getClassLoader().getResource(s); it gives back an URL encoded string in eclipse while Maven2 gives me blanks in my URL: * eclipse file:/C:/Dokumente%20und%20Einstellungen/roland.kofler/systemone/core/target/test-classes/fsm.jpg *maven2 file:/C:/Dokumente und Einstellungen/roland.kofler/systemone/core/target/test-classes/fsm.jpg MY PROBLEM WITH THIS: Because of this behaviour a new URI(file:/C:/Dokumente und Einstellungen/roland.kofler/systemone/core/target/test-classes/fsm.jpg) throws a URISyntaxException. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build trunk - SUCCESS - checkout] Mon Feb 27 00:00:00 GMT 2006
Distribution: http://maven.zones.apache.org/~maven/builds/trunk/m2-20060227.01.tar.gz Log: http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060227.01.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build branches/maven-2.0.x - SUCCESS - checkout] Mon Feb 27 00:30:01 GMT 2006
Distribution: http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20060227.003001.tar.gz Log: http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060227.003001.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MEV-348) javax.comm API - upload in iBiblio
javax.comm API - upload in iBiblio -- Key: MEV-348 URL: http://jira.codehaus.org/browse/MEV-348 Project: Maven Evangelism Type: Wish Components: Missing POM Reporter: Subhash Chandran Request for - the Java Communications 3.0 API to be part of the iBiblio repository. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MEV-348) javax.comm API - upload in iBiblio
[ http://jira.codehaus.org/browse/MEV-348?page=all ] Subhash Chandran updated MEV-348: - Attachment: javax-comm-3.0u1.pom javax.comm API - upload in iBiblio -- Key: MEV-348 URL: http://jira.codehaus.org/browse/MEV-348 Project: Maven Evangelism Type: Wish Components: Missing POM Reporter: Subhash Chandran Attachments: javax-comm-3.0u1.pom Request for - the Java Communications 3.0 API to be part of the iBiblio repository. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MAVENUPLOAD-755) ehcache pom for ehcache 1.2 beta 4 broken
ehcache pom for ehcache 1.2 beta 4 broken - Key: MAVENUPLOAD-755 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-755 Project: maven-upload-requests Type: Task Reporter: Greg Luck The pom for ehcache-1.2beta4 is broken. Trying to use it gives: [WARNING] POM for 'ehcache:ehcache:pom:1.2beta4' is invalid. It will be ignored for artifact resolution. Reason: Parse error reading POM. Reason: Duplicated tag: 'groupId' (position: START_TAG seen ...dependency\n groupId... @20:16) A corrected one 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MAVENUPLOAD-755) ehcache pom for ehcache 1.2 beta 4 broken
[ http://jira.codehaus.org/browse/MAVENUPLOAD-755?page=all ] Greg Luck updated MAVENUPLOAD-755: -- Attachment: ehcache-1.2beta4.pom ehcache pom for ehcache 1.2 beta 4 broken - Key: MAVENUPLOAD-755 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-755 Project: maven-upload-requests Type: Task Reporter: Greg Luck Attachments: ehcache-1.2beta4.pom The pom for ehcache-1.2beta4 is broken. Trying to use it gives: [WARNING] POM for 'ehcache:ehcache:pom:1.2beta4' is invalid. It will be ignored for artifact resolution. Reason: Parse error reading POM. Reason: Duplicated tag: 'groupId' (position: START_TAG seen ...dependency\n groupId... @20:16) A corrected one 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNGECLIPSE-83) Hiding of runtime scope
[ http://jira.codehaus.org/browse/MNGECLIPSE-83?page=comments#action_59534 ] Tuomas Kiviaho commented on MNGECLIPSE-83: -- If there would be a bulletproof way to determine wether or not Eclipse project is intended to be run only in container... What I can come up with is the project descriptor ear/war packaging (ear/war) and/or existence of WTP project nature. I'm not pleased with the latter, since it woud be too much to require TPTP usage for test scope dependencies to be considered. POM dependency then again will fail for other standard packaging types like .rar and definetly for vendor spesific types like JBoss .ejb3 and .aop. Hiding of runtime scope --- Key: MNGECLIPSE-83 URL: http://jira.codehaus.org/browse/MNGECLIPSE-83 Project: Maven 2.x Extension for Eclipse Type: Sub-task Reporter: Tuomas Kiviaho Assignee: Eugene Kuleshov The Maven2 dependencies library get's bloated since runtime scope is included as well. After all the plugin is providing build path support so compile and provided plus most likely test since Eclipse can't tell the difference (and system) should be enough. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Reopened: (MRM-41) discover standalone POMs
[ http://jira.codehaus.org/browse/MRM-41?page=all ] John Tolentino reopened MRM-41: --- Test data which was included in the patch was not applied to committed code. This causes build failure on clean checkout. Please reapply patch. discover standalone POMs Key: MRM-41 URL: http://jira.codehaus.org/browse/MRM-41 Project: Maven Repository Manager Type: Task Components: discovery Reporter: Brett Porter Assignee: John Tolentino Fix For: 1.0-alpha-1 Attachments: MRM-41-maven-repository-discovery.diff, MRM-41-maven-repository-discovery.diff, MRM-41-maven-repository-discovery.diff, repository-manager.diff Time Spent: 21 hours Remaining: 0 minutes where the pom is the artifact -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MSUREFIRE-49) environmentVariables does not work with windows
[ http://jira.codehaus.org/browse/MSUREFIRE-49?page=all ] Dan Tran closed MSUREFIRE-49: - Resolution: Cannot Reproduce Not sure why, but latest surefire in svn does not exhibit this problem any more environmentVariables does not work with windows --- Key: MSUREFIRE-49 URL: http://jira.codehaus.org/browse/MSUREFIRE-49 Project: Maven 2.x Surefire Plugin Type: Bug Versions: 2.1.2 Environment: windows Reporter: Dan Tran Fix For: 2.1.3 MSUREFIRE-44 added environmentVariables fields to all additional environment variables to be added to when forking the test It works on UNIX but not windows. Suspect it is platform specific problem for windows in plexus-util's cli library Here is the plugin configuration to reproduce the problem plugin artifactIdmaven-surefire-plugin/artifactId configuration environmentVariables keyvalue/key /environmentVariables forkModeonce/forkMode /configuration /plugin and the stack trace is [[DEBUG] Adding to surefire test classpath: c:\dev\maven\maven-2.0.2\core\plexus- utils-1.1.jar Environment: key=value added. java -classpath C:\Documents and Settings\dtran\.m2\repository\org\apache\maven \surefire\surefire-booter\1.5.3-SNAPSHOT\surefire-booter-1.5.3-SNAPSHOT.jar;c:\d ev\maven\maven-2.0.2\core\plexus-utils-1.1.jar org.apache.maven.surefire.Surefi reBooter C:\dev\maven\src\surefire\surefire [INFO] - --- [ERROR] BUILD ERROR [INFO] - --- [INFO] There are some test failure. [INFO] - --- [DEBUG] Trace org.apache.maven.lifecycle.LifecycleExecutionException: There are some test fail ure. at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa ultLifecycleExecutor.java:556) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi fecycle(DefaultLifecycleExecutor.java:472) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau ltLifecycleExecutor.java:451) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan dleFailures(DefaultLifecycleExecutor.java:303) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen ts(DefaultLifecycleExecutor.java:270) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi fecycleExecutor.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(DelegatingMethodAcces sorImpl.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: There are some test f ailure. at org.apache.maven.test.SurefirePlugin.execute(SurefirePlugin.java:404) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi nManager.java:415) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa ultLifecycleExecutor.java:531) ... 16 more [INFO] - --- [INFO] Total time: 4 seconds [INFO] Finished at: Sat Jan 21 10:18:59 PST 2006 [INFO] Final Memory: 3M/6M [INFO] - --- -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
