[jira] Created: (SUREFIRE-307) Tests fail if in path with spaces
Tests fail if in path with spaces
-
Key: SUREFIRE-307
URL: http://jira.codehaus.org/browse/SUREFIRE-307
Project: Maven Surefire
Issue Type: Bug
Components: classloading, TestNG support
Affects Versions: 2.3
Environment: Windows XP
Maven 2.0.5
Java 1.6.0
Reporter: Wim Deblauwe
I use TestNG with Surefire. My build fails if my project is in a path with
spaces, because my tests fail. In my tests I have the following code:
new File( getClass().getResource( "sample-java-utils-log.xml" ).toURI() )
This results in the following error:
java.net.URISyntaxException: Illegal character in path at index 18:
file:/C:/Documents and
Settings/wdb/.hudson/jobs/Vigilog/workspace/trunk/target/test-classes/net/sourceforge/vigilog/parse/sample-
java-utils-log.xml
at java.net.URI$Parser.fail(Unknown Source)
at java.net.URI$Parser.checkChars(Unknown Source)
at java.net.URI$Parser.parseHierarchical(Unknown Source)
at java.net.URI$Parser.parse (Unknown Source)
at java.net.URI.(Unknown Source)
at java.net.URL.toURI(Unknown Source)
at
net.sourceforge.vigilog.parse.JavaLoggingXMLFileLogFileParserTest.testParse(JavaLoggingXMLFileLogFileParserTest.java
:38)
If I put my project in a path without spaces, I don't have this problem (I
noticed this problem, because I tried Hudson build server and it checks the
project out to my home directory)
According to Jesse Glick from the Hudson mailing list, the problem is due to
the following fact (full thread:
http://www.nabble.com/Build-fails-under-hudson-due-to-TestNG-unit-tests-tf3354110.html):
Wim Deblauwe wrote:
> If it is any help, this is the source code of IsolatedClassLoader:
> http://svn.apache.org/viewvc/maven/surefire/trunk/surefire-booter/src/main/java/org/apache/maven/surefire/booter/IsolatedClassLoader.java?view=markup
It sure does help, because this class is probably to blame for your problem:
http://svn.apache.org/repos/asf/maven/surefire/trunk/surefire-api/src/main/java/org/apache/maven/surefire/util/UrlUtils.java
Note the call to File.toURL(), deprecated as of JDK 6 because
$ jrunscript
js> println(new java.io.File("/tmp/foo and bar/baz").toURI().toURL())
file:/tmp/foo%20and%20bar/baz
js> println(new java.io.File("/tmp/foo and bar/baz").toURL())
file:/tmp/foo and bar/baz
js> println(new java.io.File("/tmp/foo and bar/baz").toURL().toURI())
script error: sun.org.mozilla.javascript.internal.WrappedException:
Wrapped java.net.URISyntaxException: Illegal character in path at index
13: file:/tmp/foo and bar/baz (#1) in at line number 1
js>
If you want to reproduce this, check out my open source project to a directory
with spaces from: https://vigilog.svn.sourceforge.net/svnroot/vigilog/trunk
and run 'mvn test'.
--
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: (MRELEASE-202) snapshot versions in dependencyManagement are not updated
snapshot versions in dependencyManagement are not updated - Key: MRELEASE-202 URL: http://jira.codehaus.org/browse/MRELEASE-202 Project: Maven 2.x Release Plugin Issue Type: Bug Affects Versions: 2.0-beta-5 Reporter: Brett Porter I believe this is a regression but have not yet confirmed the details. I noticed this happened in the modello alpha-14 release. -- 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: (CONTINUUM-1206) registration validation eamil sender shows as From: "[EMAIL PROTECTED]"
registration validation eamil sender shows as From: "[EMAIL PROTECTED]"
---
Key: CONTINUUM-1206
URL: http://jira.codehaus.org/browse/CONTINUUM-1206
Project: Continuum
Issue Type: Bug
Components: Notifier - Mail
Affects Versions: 1.1
Environment: AIX
Reporter: apache maillist
Priority: Minor
is ${user.name} configurable?
--
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-1205) disable logging of SQL because a warn message is printed in logs for each object not found in database
[ http://jira.codehaus.org/browse/CONTINUUM-1205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lester Ecarma updated CONTINUUM-1205: - Attachment: CONTINUUM-1205.patch Attached patch disables SQL log warnings. Please review. Thanks. > disable logging of SQL because a warn message is printed in logs for each > object not found in database > -- > > Key: CONTINUUM-1205 > URL: http://jira.codehaus.org/browse/CONTINUUM-1205 > Project: Continuum > Issue Type: Task > Components: Web - Configuration >Reporter: Lester Ecarma > Attachments: CONTINUUM-1205.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] Created: (CONTINUUM-1205) disable logging of SQL because a warn message is printed in logs for each object not found in database
disable logging of SQL because a warn message is printed in logs for each object not found in database -- Key: CONTINUUM-1205 URL: http://jira.codehaus.org/browse/CONTINUUM-1205 Project: Continuum Issue Type: Task Components: Web - Configuration Reporter: Lester Ecarma -- 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: (MRM-302) Inconsistent button text and page headers
Inconsistent button text and page headers - Key: MRM-302 URL: http://jira.codehaus.org/browse/MRM-302 Project: Archiva Issue Type: Improvement Components: web application Affects Versions: 1.0 Reporter: Wendy Smoak Priority: Minor For configuration, the button label is 'Settings' but the page header is 'Administration' with a sub-section named 'Configuration'. (In Continuum, the button is 'Configuration' and the page header is 'General Configuration'.) -- 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: (MRM-301) Configuration page should display http proxy settings
Configuration page should display http proxy settings -- Key: MRM-301 URL: http://jira.codehaus.org/browse/MRM-301 Project: Archiva Issue Type: Improvement Components: web application Reporter: Wendy Smoak Priority: Minor When adding a proxied repository, there is a checkbox for 'Use HTTP Proxy'. It's not obvious where to go to set up the proxy. The Configuration -> Settings page only displays information about the index, it should also display the http proxy settings. -- 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] Reopened: (CONTINUUM-1155) Continuum should be able to use cached username/password credentials when the scm provider supports it
[ http://jira.codehaus.org/browse/CONTINUUM-1155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wendy Smoak reopened CONTINUUM-1155: Reopening for documentation. When you add a project to Continuum, you supply a userid and password (if required). IIRC, Continuum used to always pass those credentials along when it did 'svn update'. Is that correct, and how does it work now? See: http://docs.codehaus.org/display/CONTINUUMUSER/Continuum+and+Subversion . > Continuum should be able to use cached username/password credentials when the > scm provider supports it > -- > > Key: CONTINUUM-1155 > URL: http://jira.codehaus.org/browse/CONTINUUM-1155 > Project: Continuum > Issue Type: New Feature > Components: Environmental >Affects Versions: 1.0.3 >Reporter: Edwin Punzalan > Assigned To: Edwin Punzalan > Fix For: 1.1 > > -- 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-31) Multi-module reports do not support custom classpath configurations
[
http://jira.codehaus.org/browse/MCHECKSTYLE-31?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_89430
]
Christian Goetze commented on MCHECKSTYLE-31:
-
I've been trying to get this to work for some time, and I can't seem to get
there...
So I did move the plugin configuration into the section, which at
least caused the cyclic dependency error I saw before (when I used to go away, but now it seems that it won't go more than one level deep,
skipping over module directories that do not contain a src subtree.
INFO]
[INFO] Building SenSage shared artifacts
[INFO]task-segment: [checkstyle:check]
[INFO]
[INFO] Preparing checkstyle:check
[INFO] [checkstyle:checkstyle]
[INFO] Source directory does not exist - skipping report.
[INFO] [checkstyle:check]
[INFO] Unable to perform checkstyle:check, unable to find checkstyle:checkstyle
outputFile.
This is using maven 2.0.5
> Multi-module reports do not support custom classpath configurations
> ---
>
> Key: MCHECKSTYLE-31
> URL: http://jira.codehaus.org/browse/MCHECKSTYLE-31
> Project: Maven 2.x Checkstyle Plugin
> Issue Type: Bug
>Affects Versions: 2.0-beta-1
>Reporter: Mike Perham
> Assigned To: fabrizio giustina
>Priority: Critical
>
> The latest multi-module tip shows the following:
> {noformat}
>
>
>
> org.apache.maven.plugins
> maven-checkstyle-plugin
>
> whizbang/checkstyle.xml
> whizbang/LICENSE.txt
>
>
>
> com.example.whizbang
> build-tools
> 1.0
>
>
>
>
>
> {noformat}
> This is invalid according to the latest 2.0.2 POM schema. is
> not supported in reporting plugins.
> So it seems impossible to provide a custom config in a multi-module build
> without using a network URL as we cannot use File or classpath.
--
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: (CONTINUUM-1204) Fix permissons on the CONTINUUMUSER space
Fix permissons on the CONTINUUMUSER space --- Key: CONTINUUM-1204 URL: http://jira.codehaus.org/browse/CONTINUUM-1204 Project: Continuum Issue Type: Task Components: Documentation Reporter: Wendy Smoak Unlike MAVENUSER, the public Continuum wiki space is not visible unless you're logged in. http://docs.codehaus.org/display/CONTINUUMUSER/Home -- 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: (MRM-300) when a proxied repository is remove, it re-appears when Archiva is restarted
[ http://jira.codehaus.org/browse/MRM-300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed MRM-300. Resolution: Fixed Fix Version/s: 1.0 > when a proxied repository is remove, it re-appears when Archiva is restarted > > > Key: MRM-300 > URL: http://jira.codehaus.org/browse/MRM-300 > Project: Archiva > Issue Type: Bug > Components: design >Reporter: Brett Porter > Assigned To: Brett Porter > Fix For: 1.0 > > > Deleted proxied repositories reappear when Archiva is restarted. > To reproduce: > 1. Log in as admin > 2. Artifact Rpository -> Proxied Repositories > 3. Delete the default 'central' proxied repo > 4. Restart > 5. Repeat steps 1-2 > Result: > The previously deleted proxied repo appears in the list. > Expected Result: > The deleted repo should not appear. > Workaround: > Edit conf/archiva.xml and remove the element. -- 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: (CONTINUUM-1203) java.lang.NullPointerException when saving company details in the "Appearance" configuration
java.lang.NullPointerException when saving company details in the "Appearance" configuration - Key: CONTINUUM-1203 URL: http://jira.codehaus.org/browse/CONTINUUM-1203 Project: Continuum Issue Type: Bug Components: Web - UI Affects Versions: 1.1 Environment: AIX Reporter: apache maillist Priority: Minor Attachments: java.lang.NullPointerException.doc Company Details Enter the details of the company super POM below. If it exists, the organization name, URL and logo will be read from it. Group ID: < I enter my company Group ID > Artifact ID: < I enter my company Artifact ID > when click "Save" I get java.lang.NullPointerException -- 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: (NMAVEN-12) Support for Invoking the MavenEmbedder Methods from .NET Applications
Support for Invoking the MavenEmbedder Methods from .NET Applications - Key: NMAVEN-12 URL: http://jira.codehaus.org/browse/NMAVEN-12 Project: NMaven Issue Type: New Feature Environment: Windows, Linux Reporter: Shane Isbell Priority: Minor As part of the IDE integration, Visual Studio and Sharp Develop need to use maven functionality. This feature will support a way for .NET applications to invoke the MavenEmbedder methods. -- 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: (MECLIPSE-225) Invalid .classpath Entries.
[ http://jira.codehaus.org/browse/MECLIPSE-225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Wolff closed MECLIPSE-225. --- Resolution: Cannot Reproduce Fix Version/s: 2.4 Not sure what was causing the spurious .classpath entries. I'm unable to duplicate the problem in either version 2.3 or 2.4 SNAPSHOT. > Invalid .classpath Entries. > --- > > Key: MECLIPSE-225 > URL: http://jira.codehaus.org/browse/MECLIPSE-225 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Components: dependency resolution >Affects Versions: 2.3 >Reporter: Todd Wolff > Fix For: 2.4 > > > Dependencies with scope 'runtime' and a type other than 'jar', i.e. 'war', > 'sar', etc ..., should not be written to .classpath file. This is typically > the mechanism used to identify an assembly dependency. -- 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-1407) Please sync with jguard repo
Please sync with jguard repo Key: MAVENUPLOAD-1407 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1407 Project: maven-upload-requests Issue Type: Task Reporter: charles gay Please sync with jguard's repo. The shell can be found at http://jguard.sf.net/net.sf.jguard.sh thanks for your great work!! cheers, Charles GAY. www.jguard.net -- 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: (MRM-300) when a proxied repository is remove, it re-appears when Archiva is restarted
[ http://jira.codehaus.org/browse/MRM-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_89410 ] Joakim Erdfelt commented on MRM-300: More accurate to say that the proxied repository is never removed from the on-disk archiva.xml > when a proxied repository is remove, it re-appears when Archiva is restarted > > > Key: MRM-300 > URL: http://jira.codehaus.org/browse/MRM-300 > Project: Archiva > Issue Type: Bug > Components: design >Reporter: Brett Porter > Assigned To: Brett Porter > > Deleted proxied repositories reappear when Archiva is restarted. > To reproduce: > 1. Log in as admin > 2. Artifact Rpository -> Proxied Repositories > 3. Delete the default 'central' proxied repo > 4. Restart > 5. Repeat steps 1-2 > Result: > The previously deleted proxied repo appears in the list. > Expected Result: > The deleted repo should not appear. > Workaround: > Edit conf/archiva.xml and remove the element. -- 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] Work started: (MRM-300) when a proxied repository is remove, it re-appears when Archiva is restarted
[ http://jira.codehaus.org/browse/MRM-300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on MRM-300 started by Brett Porter. > when a proxied repository is remove, it re-appears when Archiva is restarted > > > Key: MRM-300 > URL: http://jira.codehaus.org/browse/MRM-300 > Project: Archiva > Issue Type: Bug > Components: design >Reporter: Brett Porter > Assigned To: Brett Porter > > Deleted proxied repositories reappear when Archiva is restarted. > To reproduce: > 1. Log in as admin > 2. Artifact Rpository -> Proxied Repositories > 3. Delete the default 'central' proxied repo > 4. Restart > 5. Repeat steps 1-2 > Result: > The previously deleted proxied repo appears in the list. > Expected Result: > The deleted repo should not appear. > Workaround: > Edit conf/archiva.xml and remove the element. -- 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: (MRM-300) when a proxied repository is remove, it re-appears when Archiva is restarted
when a proxied repository is remove, it re-appears when Archiva is restarted Key: MRM-300 URL: http://jira.codehaus.org/browse/MRM-300 Project: Archiva Issue Type: Bug Components: design Reporter: Brett Porter Deleted proxied repositories reappear when Archiva is restarted. To reproduce: 1. Log in as admin 2. Artifact Rpository -> Proxied Repositories 3. Delete the default 'central' proxied repo 4. Restart 5. Repeat steps 1-2 Result: The previously deleted proxied repo appears in the list. Expected Result: The deleted repo should not appear. Workaround: Edit conf/archiva.xml and remove the element. -- 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] Deleted: (MCHANGELOG-57) Robisko test
[ http://jira.codehaus.org/browse/MCHANGELOG-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg deleted MCHANGELOG-57: -- > Robisko test > > > Key: MCHANGELOG-57 > URL: http://jira.codehaus.org/browse/MCHANGELOG-57 > Project: Maven 2.x Changelog Plugin > Issue Type: Test > Environment: dfdf >Reporter: Robo N > > fsdfsdffdfs -- 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: (MEV-509) commons-discovery-0.2 invalid version
commons-discovery-0.2 invalid version - Key: MEV-509 URL: http://jira.codehaus.org/browse/MEV-509 Project: Maven Evangelism Issue Type: Bug Components: Invalid POM Reporter: Xavier Hanin The version od commons-discovery-0.2 seems to be incorrect in the following pom: http://repo1.maven.org/maven2/commons-discovery/commons-discovery/0.2/commons-discovery-0.2.pom I believe it should be 0.2, but it's 0.2-dev -- 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: (MCHANGELOG-57) Robisko test
Robisko test Key: MCHANGELOG-57 URL: http://jira.codehaus.org/browse/MCHANGELOG-57 Project: Maven 2.x Changelog Plugin Issue Type: Test Affects Versions: 2.0, 2.0-beta-1 Environment: dfdf Reporter: Robo N Fix For: 2.1 fsdfsdffdfs -- 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: (MCHANGELOG-57) Robisko test
[ http://jira.codehaus.org/browse/MCHANGELOG-57?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_89397 ] Robo N commented on MCHANGELOG-57: -- dfsdfsdf > Robisko test > > > Key: MCHANGELOG-57 > URL: http://jira.codehaus.org/browse/MCHANGELOG-57 > Project: Maven 2.x Changelog Plugin > Issue Type: Test >Affects Versions: 2.0-beta-1, 2.0 > Environment: dfdf >Reporter: Robo N > Fix For: 2.1 > > > fsdfsdffdfs -- 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-2793) Snapshot plugins cannot be resolved correctly with java6
[ http://jira.codehaus.org/browse/MNG-2793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Kulp updated MNG-2793: - Priority: Critical (was: Major) Affects Version/s: 2.0.5 Fix Version/s: 2.0.6 > Snapshot plugins cannot be resolved correctly with java6 > > > Key: MNG-2793 > URL: http://jira.codehaus.org/browse/MNG-2793 > Project: Maven 2 > Issue Type: Bug > Components: Artifacts and Repositories, Dependencies >Affects Versions: 2.0.4, 2.0.5 >Reporter: Daniel Kulp >Priority: Critical > Fix For: 2.0.6 > > Attachments: maven-artifact-manager.patch > > > With java 6, builds that use snapshot repositories are consistently failing > if the snapshots are not available in the local repository. The error is > something like: > [INFO] > > [DEBUG] Retrieving parent-POM: org.apache.maven.plugins:maven-plugins::1 for > project: null:maven-site-plugin:maven-plugin:2.0-beta-5 from the repository. > [DEBUG] Retrieving parent-POM: org.apache.maven:maven-parent::1 for project: > org.apache.maven.plugins:maven-plugins:pom:1 from the repository. > [DEBUG] Retrieving parent-POM: org.apache:apache::1 for project: > org.apache.maven:maven-parent:pom:1 from the repository. > [DEBUG] maven-install-plugin: using locally installed snapshot > [DEBUG] maven-install-plugin: resolved to version 2.2-SNAPSHOT from > repository central > [DEBUG] Skipping disabled repository central > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Error building POM (may not be this project's POM). > Project ID: org.apache.maven.plugins:maven-install-plugin > Reason: Error getting POM for 'org.apache.maven.plugins:maven-install-plugin' > from the repository: Failed to resolve artifact, possibly due to a repository > list that is not appropriately equipped for this artifact's metadata. > org.apache.maven.plugins:maven-install-plugin:pom:2.2-SNAPSHOT > from the specified remote repositories: > apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository), > central (http://repo1.maven.org/maven2) > If the artifacts are first downloaded by building with JDK 1.5, everything > works fine. > After investigating, the problem is in the transforms that the > maven-artifact-manager. With JDK 1.5, the order they run is: > org.apache.maven.artifact.transform.LatestArtifactTransformation > org.apache.maven.artifact.transform.ReleaseArtifactTransformation > org.apache.maven.artifact.transform.SnapshotTransformation > but with Java 6, for some reason, the order is: > org.apache.maven.artifact.transform.SnapshotTransformation > org.apache.maven.artifact.transform.LatestArtifactTransformation > org.apache.maven.artifact.transform.ReleaseArtifactTransformation > The LatestArtifactTransform is what uses to the metadata to determine > the "actual" version number (for the install plugin, 2.2-SNAPSHOT). The > SnapshotTransform then converts that to 2.2-20061118.060401-2 which is what > is then downloaded. However, in the java 6 case, the SnapshotTransform is > run first and since the version is not a "SNAPSHOT" version number, it > doesn't do any processing so then the downloading ends up looking for > 2.2-SNAPSHOT, not the full version, which then fails. > I chatted with brett_ on IRC about this: > [09:46:35] OK. I'm trying to track down why my builds are failing > with JDK 1.6 > [09:46:53] The issue is the transforms are in a different order with > 1.6 than 1.5 > [09:47:17] yikes > [09:47:42] With 1.5, its Latest/Release/Snapshot. > [09:47:46] not sure why that would matter. But I guess sorting the > transforms consistently would help. > [09:47:50] With 1.6, it's Snapshot/Latest/Release > [09:48:06] ok, fairly simple to fix in Maven. > [09:48:10] The Latest needs to be before Snapshot. > [09:49:08] I tried changing the order of things in the > components.xml. Didn't seem to change anything. But this is plexus stuff > which I don't know anything about. > [09:49:22] hmm, it should be populated as a list > [09:49:28] but maybe the list is backed by a map > [09:49:35] Yep. Verified it's and ArrayList > [09:49:51] s/backed/populated by/ > [09:50:48] That would definitely do it. > [09:51:21] Any hints on where to look? > [09:51:48] oh, I would go into plexus > [09:51:52] (or how to debug)? > [09:51:58] sorry, wouldn't > [09:52:13] it's changing too much > [09:52:18] 2.0.5 will be stuck with alpha-10 > [09:52:24] so, need to work around it in Maven > [09:53:00] perhaps just hack the order in the code, and then fix > plexus to honou
[jira] Commented: (MRELEASE-174) mvn release:prepare will not tag in subversion repository
[ http://jira.codehaus.org/browse/MRELEASE-174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_89392 ] Paul Gier commented on MRELEASE-174: Rather than changing the documentation, I think the behavior would make more sense if a dryRun could be followed by a prepare without deleting release.properties. Maybe instead of putting completedPhase=end-release this could be set to a phase called dry-run or something like that. Then the release plugin would see that only a dry run was performed. > mvn release:prepare will not tag in subversion repository > - > > Key: MRELEASE-174 > URL: http://jira.codehaus.org/browse/MRELEASE-174 > Project: Maven 2.x Release Plugin > Issue Type: Bug > Environment: linux ubuntu >Reporter: Andrew >Priority: Minor > > The release plugin won't tag a version in subversion after performing > release:prepare -DdryRun=true. > We are currently using a Subversion 1.4 client and repository server. > Steps to reproduce :- > mvn release:prepare -DdryRun=true > mvn release:prepare (I assume should tag at this point) > No tag is created in repository. > If however the following :- mvn release:prepare -Dresume=false is run after > the release:prepare the tag will be created as expected. > The output from the mvn release:prepare was interesting, it appears that the > release:prepare -DdryRun=true has already performed the release preparation > even though its a dry run. > [EMAIL PROTECTED]:~/development/persistence-r1$ mvn release:prepare > [INFO] Scanning for projects... > [INFO] Searching repository for plugin with prefix: 'release'. > [INFO] > > [INFO] Building Persistence library > [INFO]task-segment: [release:prepare] (aggregator-style) > [INFO] > > [INFO] [release:prepare] > [INFO] Release preparation already completed. You can now continue with > release:perform, or start again using the -Dresume=false flag > [INFO] > > [INFO] BUILD SUCCESSFUL > [INFO] > > [INFO] Total time: 4 seconds > [INFO] Finished at: Thu Nov 09 09:08:23 EST 2006 > [INFO] Final Memory: 5M/10M > [INFO] > > My guess is that the release:prepare -DdryRun=true > shouldn't write completedPhase=end-release to release.properties ? -- 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: (MRM-299) IndexArtifactConsumer is never run during wlking through repository
[ http://jira.codehaus.org/browse/MRM-299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_89391 ] Milosz Witkowski commented on MRM-299: -- :) if someone from devel team will have time: file: /archiva-common/src/main/java/org/apache/maven/archiva/common/consumers/ConsumerFactory.java line: 52 there is : ... consumer = (Consumer) container.lookup( Consumer.ROLE,container.getLookupRealm() ); ... but should be: ... consumer = (Consumer) container.lookup( Consumer.ROLE,name, container.getLookupRealm() ); ... this one fixes problem with wrong initialization of consumers. > IndexArtifactConsumer is never run during wlking through repository > --- > > Key: MRM-299 > URL: http://jira.codehaus.org/browse/MRM-299 > Project: Archiva > Issue Type: Bug > Components: indexing > Environment: Windows XP, JVM 1.5.0_09-b03, plexus, archiva trunk At > revision 515030. >Reporter: Milosz Witkowski >Priority: Minor > > Running archiva on plexus log shows that during walking through repository > index-artifact is never executed. > Instead of it "Artifact Health Consumer" is initiated 3 times. > 2007-03-06 11:08:39,000 [pool-1-thread-1] INFO ConsumerFactory > - Attempting to create consumer [index-artifact] > 2007-03-06 11:08:39,000 [pool-1-thread-1] INFO ConsumerFactory > - Created consumer [index-artifact|Artifact Health Consumer] > 2007-03-06 11:08:39,000 [pool-1-thread-1] INFO ConsumerFactory > - Attempting to create consumer [artifact-health] > 2007-03-06 11:08:39,015 [pool-1-thread-1] INFO ConsumerFactory > - Created consumer [artifact-health|Artifact Health Consumer] > 2007-03-06 11:08:39,015 [pool-1-thread-1] INFO ConsumerFactory > - Attempting to create consumer [metadata-health] > 2007-03-06 11:08:39,015 [pool-1-thread-1] INFO ConsumerFactory > - Created consumer [metadata-health|Artifact Health Consumer] > 2007-03-06 11:08:39,093 [pool-1-thread-1] INFO Discoverer > - Walk Started: [test] /C:/tmp/maven-2.x-repository/ > 2007-03-06 11:08:39,125 [pool-1-thread-1] WARN SQL > - Object with id "javax.xml:jsr173:1.0:pom:" not found ! > 2007-03-06 11:08:39,312 [pool-1-thread-1] WARN SQL > - Object with id "javax.xml:jsr173:1.0:pom:" not found ! > 2007-03-06 11:08:39,328 [pool-1-thread-1] WARN SQL > - Object with id "javax.xml:jsr173:1.0:pom:" not found ! > 2007-03-06 11:08:39,343 [pool-1-thread-1] WARN SQL > - Object with id "jboss:jbpm:3.1.1:jar:" not found ! > 2007-03-06 11:08:39,359 [pool-1-thread-1] WARN SQL > - Object with id "jboss:jbpm:3.1.1:jar:" not found ! > 2007-03-06 11:08:39,375 [pool-1-thread-1] WARN SQL > - Object with id "jboss:jbpm:3.1.1:jar:" not found ! > 2007-03-06 11:08:39,390 [pool-1-thread-1] INFO Discoverer > - Walk Finished: [test] /C:/tmp/maven-2.x-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
[jira] Updated: (MAVENUPLOAD-1406) Jostraca Bundle
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Rodger updated MAVENUPLOAD-1406: Attachment: jostraca-0.4.1.jar > Jostraca Bundle > --- > > Key: MAVENUPLOAD-1406 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1406 > Project: maven-upload-requests > Issue Type: Task >Reporter: Richard Rodger > Attachments: jostraca-0.4.1.jar > > > There are no dependencies as all classes are under the org.jostraca package. -- 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-2860) Empty entry causes OutOfMemoryError
Empty entry causes OutOfMemoryError - Key: MNG-2860 URL: http://jira.codehaus.org/browse/MNG-2860 Project: Maven 2 Issue Type: Bug Components: Reactor and workspace Affects Versions: 2.0.5 Environment: Windows XP SP2 with all available patches Sun JDK 1.6.0 Reporter: Thorsten Heit Priority: Minor Accidentially I forgot to remove an empty entry in my pom.xml. When I tried to fully clean my project and all its subprojects Maven crashes with an OutOfMemoryError after a couple of minutes: [EMAIL PROTECTED] /cygdrive/d/workspaces/sukv-maven $ mvn -e -X clean + Error stacktraces are turned on. Maven version: 2.0.5 [DEBUG] Building Maven user-level plugin registry from: 'D:\Dokumente und Einstellungen\H2841\.m2\plugin-registry.xml' [DEBUG] Building Maven global-level plugin registry from: 'c:\maven-2.0.5\conf\plugin-registry.xml' [INFO] Scanning for projects... [INFO] [ERROR] FATAL ERROR [INFO] [INFO] Java heap space [INFO] [DEBUG] Trace java.lang.OutOfMemoryError: Java heap space at org.codehaus.plexus.util.xml.pull.MXParser.ensurePC(MXParser.java:3047) at org.codehaus.plexus.util.xml.pull.MXParser.nextImpl(MXParser.java:1374) at org.codehaus.plexus.util.xml.pull.MXParser.next(MXParser.java:1090) at org.codehaus.plexus.util.xml.pull.MXParser.nextText(MXParser.java:1055) at org.apache.maven.model.io.xpp3.MavenXpp3Reader.parseScm(MavenXpp3Reader.java:4045) at org.apache.maven.model.io.xpp3.MavenXpp3Reader.parseModel(MavenXpp3Reader.java:2206) at org.apache.maven.model.io.xpp3.MavenXpp3Reader.read(MavenXpp3Reader.java:4422) at org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultMavenProjectBuilder.java:1345) at org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultMavenProjectBuilder.java:1309) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:429) at org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:195) at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:523) at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:455) at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:499) at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:499) at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:499) at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:499) at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:499) at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:499) at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:499) at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:499) at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:499) at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:499) at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:499) at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:499) at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:499) at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:499) at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:499) at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:499) at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:499) at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:499) at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:499) [INFO] [INFO] Total time: 5 minutes 26 seconds [INFO] Finished at: Wed Mar 07 12:40:03 CET 2007 [INFO] Final Memory: 31M/234M [INFO] [EMAIL PROTECTED] /cygdrive/d/workspaces/sukv-maven $ pom.xml to test: module1 ... moduleN Maven doesn't complain about the empty entry, and obviously runs in a recursion in this case. -- 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-2577) Allow interpolation of Properties in settings.xml
[ http://jira.codehaus.org/browse/MNG-2577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_89382 ] Daniel Bechler commented on MNG-2577: - I would be amazed if this patch could be included into the next minor release, because it would make the work with a distributed installation of Maven2 much easier or even possible. > Allow interpolation of Properties in settings.xml > - > > Key: MNG-2577 > URL: http://jira.codehaus.org/browse/MNG-2577 > Project: Maven 2 > Issue Type: Improvement > Components: Settings >Affects Versions: 2.0.4, 2.0.5 >Reporter: Michael Locher >Priority: Critical > Attachments: DefaultMavenSettingsBuilder.java.diff > > > the attached patch (against 2.0.4) allows interpolation of system properties > into the .m2/settings.xml > and interpolation of system properties and the properties of profiles found > in .m2/settings.xml (if they are activeByDefault) into conf/settings.xml > these features are necessary in order to propagate user account settings > defined in user-specific .m2/settings.xml into server sections of the > institution-wide conf/settings.xml -- 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-1406) Jostraca Bundle
Jostraca Bundle --- Key: MAVENUPLOAD-1406 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1406 Project: maven-upload-requests Issue Type: Task Reporter: Richard Rodger There are no dependencies as all classes are under the org.jostraca package. -- 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
