[jira] Created: (MASSEMBLY-511) Multi-Module Project --> One Jar
Multi-Module Project --> One Jar Key: MASSEMBLY-511 URL: http://jira.codehaus.org/browse/MASSEMBLY-511 Project: Maven 2.x Assembly Plugin Issue Type: Improvement Affects Versions: 2.1 Reporter: Tim Brutscher Hello everyone, I use a Maven multi-module project. In default, maven builds one jar for every module. Is it possible, to generate just one jar, including all the modules? Thank you all! Tim -- 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: (MRELEASE-128) SCM properties being replaced during release:perform
[
http://jira.codehaus.org/browse/MRELEASE-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=239589#action_239589
]
Lars Fischer commented on MRELEASE-128:
---
Hello,
I tried to use version 2.1 with this configuration:
scm:svn:svn://${scm.host}/commons/trunk/xyz
scm:svn:svn://${scm.host}/commons/trunk/xyz
http://${scm.host}/cgi-bin/viewvc.cgi/Commons
After releasing, the ${scm.host} in the new snapshot-pom was replaced by the
${scm.host}-value. Is there a way to keep the "${scm.host}"?
> SCM properties being replaced during release:perform
>
>
> Key: MRELEASE-128
> URL: http://jira.codehaus.org/browse/MRELEASE-128
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
> Environment: Windows XP client, Linux repo, CVS, Maven 2.0.4
>Reporter: Craig Dickson
>Assignee: Brett Porter
>Priority: Critical
> Fix For: 2.1
>
> Attachments: after-release-perform-pom.xml,
> after-release-prepre-pom.xml, MNG-128-maven-release-manager.patch,
> MRELEASE-128_cvs_hack_RewritePomsForDevelopmentPhase.java.patch,
> original-pom.xml
>
>
> The section of a pom in CVS for a pom archetype project looks like this
> prior to executing release:prepare :
>
> ${base.cvs.url}:commons-maven/uber-pom
>
> ${base.cvs.url}:commons-maven/uber-pom
> ${base.viewcvs.url}/commons-maven/uber-pom
>
> Then after executing release:prepare, the pom in CVS looks like this (new
> tag is only difference):
>
> ${base.cvs.url}:commons-maven/uber-pom
>
> ${base.cvs.url}:commons-maven/uber-pom
> ${base.viewcvs.url}/commons-maven/uber-pom
> R-1_7
>
> Then after executing release:perform, the pom looks like this in CVS:
>
>
> scm:cvs:pserver:behrcvs.masco-coatings.com:/usr/cvsroot:commons-maven/uber-pom
>
> scm:cvs:pserver:behrcvs.masco-coatings.com:/usr/cvsroot:commons-maven/uber-pom
>
> http://behrcvs.masco-coatings.com/cgi-bin/viewcvs.cgi/commons-maven/uber-pom
>
> Notice that the properties that were there for the base URLs for CVS and
> ViewCVS have been replaced with literal values.
> No other properties in the POM are being replaced
--
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-4865) mvn fails because of null property
mvn fails because of null property -- Key: MNG-4865 URL: http://jira.codehaus.org/browse/MNG-4865 Project: Maven 2 & 3 Issue Type: Bug Components: Command Line Affects Versions: 2.2.1 Environment: windows vista32 Reporter: eric zhu I downloaded maven and ran 'maven -version' under 'C:\workplace\apache-maven-2.2.1\bin' Got the error: java.lang.NullPointerException: key can't be null at java.lang.System.checkKey(System.java:771) at java.lang.System.getProperty(System.java:647) at org.codehaus.classworlds.Configurator.configure(Configurator.java:240) at org.codehaus.classworlds.Launcher.configure(Launcher.java:156) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:426) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) I ran the same on another XP PC with the same source, everything worked fine -- 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: (MENFORCER-108) Documentation/Typo : 'unCheckedPluginsList' is written instead of 'unCheckedPluginList'
Documentation/Typo : 'unCheckedPluginsList' is written instead of 'unCheckedPluginList' --- Key: MENFORCER-108 URL: http://jira.codehaus.org/browse/MENFORCER-108 Project: Maven 2.x Enforcer Plugin Issue Type: Bug Components: Standard Rules Affects Versions: 1.0-beta-1 Reporter: Jonathan Perret Priority: Minor The documentation at http://maven.apache.org/enforcer/enforcer-rules/requirePluginVersions.html uses the element name 'unCheckedPluginsList', both in the parameter list and in the sample, where it should use 'unCheckedPluginList' (note singular 'Plugin'). See http://svn.apache.org/viewvc/maven/enforcer/tags/enforcer-1.0-beta-1/enforcer-rules/src/main/java/org/apache/maven/plugins/enforcer/RequirePluginVersions.java?r1=729232&r2=746626&diff_format=h#l122 for proof that the rule expects 'unCheckedPluginList'. -- 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-2626) XOM 1.2.3
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juven Xu closed MAVENUPLOAD-2626. - Resolution: Fixed xom 1.2.5 is already in maven centra for other versions, please go to https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide or https://docs.sonatype.org/display/Repository/Uploading+3rd-party+Artifacts+to+Maven+Central > XOM 1.2.3 > - > > Key: MAVENUPLOAD-2626 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2626 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Elliotte Rusty Harold >Assignee: Juven Xu > Attachments: repository-upload.png > > > http://xom.nu/ -- 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-2739) Version 2.2-jdk15 of UISpec4J
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juven Xu closed MAVENUPLOAD-2739. - Resolution: Won't Fix Assignee: Juven Xu closing issue, please goto Sonatype OSS repo for uploading bundle https://docs.sonatype.org/display/Repository/Uploading+3rd-party+Artifacts+to+Maven+Central > Version 2.2-jdk15 of UISpec4J > - > > Key: MAVENUPLOAD-2739 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2739 > Project: Maven Upload Requests > Issue Type: New Feature >Reporter: Pascal Pratmarty >Assignee: Juven Xu > > UISpec4J is an Open Source functional and/or unit testing library for > Swing-based Java applications, built on top of the JUnit and TestNG test > harnesses. -- 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-2790) to upload hadoop-gpl-compression jar to the maven repository
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juven Xu closed MAVENUPLOAD-2790. - Resolution: Won't Fix no pgp signature, no javadoc, no sources, rejecting request please go to apache maven repository for uploading asf artifacts into maven central http://www.apache.org/dev/publishing-maven-artifacts.html > to upload hadoop-gpl-compression jar to the maven repository > > > Key: MAVENUPLOAD-2790 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2790 > Project: Maven Upload Requests > Issue Type: New Feature >Reporter: Giridharan Kesavan > > Hadoop testing framework depends on this hadoop-gpl-compression jar. Could > you please help us in pushing it to the maven repo? > Hadoop jira which talks about the test failure due to missing gpl compression > jar file: > https://issues.apache.org/jira/browse/MAPREDUCE-1790 > I'm the build and release engineer for hadoop and I manage hudson for Apache > as Admin. > 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: (MAVENUPLOAD-2350) JCaptcha 1.0
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juven Xu closed MAVENUPLOAD-2350. - Resolution: Won't Fix Assignee: Juven Xu please use Sonatype OSS bundle upload service for this: https://docs.sonatype.org/display/Repository/Uploading+3rd-party+Artifacts+to+Maven+Central > JCaptcha 1.0 > > > Key: MAVENUPLOAD-2350 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2350 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Antoine Véret >Assignee: Juven Xu > > "com.octo.captcha","mavens...@web.sourceforge.net:/home/groups/j/jc/jcaptcha/maven-repo","rsync_ssh","Antoine > Veret","ave...@octo.com",, -- 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-595) junit:junit has wrong release
[ http://jira.codehaus.org/browse/MEV-595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juven Xu closed MEV-595. Resolution: Fixed junit is using Sonatype OSS repo, so metadata is generated by Nexus and correct: http://repo1.maven.org/maven2/junit/junit/maven-metadata.xml > junit:junit has wrong release > - > > Key: MEV-595 > URL: http://jira.codehaus.org/browse/MEV-595 > Project: Maven Evangelism > Issue Type: Bug > Components: Invalid Metadata >Reporter: Justin Edelson > > http://repo1.maven.org/maven2/junit/junit/maven-metadata.xml > says > 3.8.1 > when it should be > 4.4 -- 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-607) Missing checksums for org.codehaus.woodstox wstx-asl 3.2.7
[ http://jira.codehaus.org/browse/MEV-607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juven Xu closed MEV-607. Resolution: Fixed Assignee: Juven Xu fixed, checksums will be in central in 1 hour > Missing checksums for org.codehaus.woodstox wstx-asl 3.2.7 > -- > > Key: MEV-607 > URL: http://jira.codehaus.org/browse/MEV-607 > Project: Maven Evangelism > Issue Type: Bug > Components: Checksum Failure >Reporter: Max Bowsher >Assignee: Juven Xu > > None of the artifacts at > http://repo2.maven.org/maven2/org/codehaus/woodstox/wstx-asl/3.2.7/ have > checksums - painful if you're trying to run your Maven in strict checksum > 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
[jira] Closed: (MEV-641) org.codehaus.woodstox/wstx-asl/3.2.8 - bad md5sum for JAR
[
http://jira.codehaus.org/browse/MEV-641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Juven Xu closed MEV-641.
Resolution: Fixed
Assignee: Juven Xu
fixed
> org.codehaus.woodstox/wstx-asl/3.2.8 - bad md5sum for JAR
> -
>
> Key: MEV-641
> URL: http://jira.codehaus.org/browse/MEV-641
> Project: Maven Evangelism
> Issue Type: Bug
> Components: Checksum Failure
>Reporter: Scott Parkerson
>Assignee: Juven Xu
>
> I found this bad checksum using my Apache Archiva local mirror. From the log
> file:
> {noformat}
> org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors - Transfer
> invalidated from
> http://repo1.maven.org/maven2/org/codehaus/woodstox/wstx-asl/3.2.8/wstx-asl-3.2.8.jar
> : Checksums do not match, policy set to FAIL, deleting checksum files and
> local file
> /srv/apache-archiva-1.2.2/data/repositories/proxy/.workingdirectory6264102556128194981.tmp/wstx-asl-3.2.8.jar
> {noformat}
> Upon downloading the JAR and checking its MD5 sum:
> {noformat}
> eleutheria:~ scott$ curl -s
> http://repo2.maven.org/maven2/org/codehaus/woodstox/wstx-asl/3.2.8/wstx-asl-3.2.8.jar
> | md5
> 28a548e1f88820be76410dbc98731343
> eleutheria:~ scott$ curl
> http://repo2.maven.org/maven2/org/codehaus/woodstox/wstx-asl/3.2.8/wstx-asl-3.2.8.jar.md5
> && echo ''
> f25af24e1256afcc41cf4e81caab958a
> {noformat}
--
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-636) Woodstox Checksum failed
[ http://jira.codehaus.org/browse/MEV-636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juven Xu closed MEV-636. Resolution: Fixed Assignee: Juven Xu fixed > Woodstox Checksum failed > > > Key: MEV-636 > URL: http://jira.codehaus.org/browse/MEV-636 > Project: Maven Evangelism > Issue Type: Bug >Reporter: Erik Martino Hansen >Assignee: Juven Xu > > Downloading: > http://repo1.maven.org/maven2/org/codehaus/woodstox/wstx-asl/3.2.8/wstx-asl-3.2.8.jar > 511K downloaded > [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = > '1930b57270ff5b22e32f20cc895a07ee4a0e84e6'; remote = > 'a16d56474c1ac1496c89aa14cf28bbbd6b457bcc' - RETRYING > Downloading: > http://repo1.maven.org/maven2/org/codehaus/woodstox/wstx-asl/3.2.8/wstx-asl-3.2.8.jar > 511K downloaded > [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = > '1930b57270ff5b22e32f20cc895a07ee4a0e84e6'; remote = > 'a16d56474c1ac1496c89aa14cf28bbbd6b457bcc' - IGNORING -- 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-654) The SHA1 files uploaded to the maven repository are not formatted correctly, and make it impossible to use Commons-Compress with maven or ivy
[ http://jira.codehaus.org/browse/MEV-654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juven Xu closed MEV-654. Resolution: Fixed Assignee: Juven Xu fixed > The SHA1 files uploaded to the maven repository are not formatted correctly, > and make it impossible to use Commons-Compress with maven or ivy > - > > Key: MEV-654 > URL: http://jira.codehaus.org/browse/MEV-654 > Project: Maven Evangelism > Issue Type: Bug >Reporter: Kevin Squire >Assignee: Juven Xu > > In the maven repository at > http://repo1.maven.org/maven2/org/apache/commons/commons-compress/1.0/ (and > mirrors), the SHA1 file for each uploaded file looks like this (shown is > commons-compress-1.0.pom.sha1): > commons-compress-1.0.pom: 3259 80A0 9DBB D0C1 08EC E8E7 733B 462B 00E6 F2A8 > This file is in the wrong format for maven and ivy to parse, causing them not > to be able to download and use commons-compress. > The file should contain only the sha1 hash, with no spaces, as > 325980a09dbbd0c108ece8e7733b462b00e6f2a8 > If possible, please fix (or ask the developer to fix). See corresponding bug > report at https://issues.apache.org/jira/browse/COMPRESS-104 . -- 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-637) Bad Checksum on http://repo1.maven.org/maven2/com/google/inject/guice/2.0/guice-2.0.pom
[ http://jira.codehaus.org/browse/MEV-637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juven Xu closed MEV-637. Resolution: Fixed Assignee: Juven Xu fixed > Bad Checksum on > http://repo1.maven.org/maven2/com/google/inject/guice/2.0/guice-2.0.pom > --- > > Key: MEV-637 > URL: http://jira.codehaus.org/browse/MEV-637 > Project: Maven Evangelism > Issue Type: Bug > Components: Checksum Failure >Reporter: Patrick >Assignee: Juven Xu > > problem while downloading module descriptor: > http://repo1.maven.org/maven2/com/google/inject/guice/2.0/guice-2.0.pom: > invalid sha1: expected=6c5029102c03c627275fe183377c0586a3194425 > computed=3bb8d0283ecfc05ba8dae825e46980d669265333 (219ms) -- 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-608) Bad checksum for maven-remote-resources-plugin-1.0-alpha-3.pom
[
http://jira.codehaus.org/browse/MEV-608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Juven Xu closed MEV-608.
Resolution: Fixed
Assignee: Juven Xu
fixed
> Bad checksum for maven-remote-resources-plugin-1.0-alpha-3.pom
> --
>
> Key: MEV-608
> URL: http://jira.codehaus.org/browse/MEV-608
> Project: Maven Evangelism
> Issue Type: Bug
> Components: Checksum Failure
>Reporter: Benjamin Bentmann
>Assignee: Juven Xu
>
> {noformat}
> Downloading:
> http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-remote-resources-plugin/1.0-alpha-3/maven-remote-resources-plugin-1.0-alpha-3.pom
> 3K downloaded
> [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
> '689ca74e9bddeb5ffeda58b5bc189a8318f88d1d'; remote=
> 'da39a3ee5e6b4b0d3255bfef95601890afd80709' - RETRYING
> Downloading:
> http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-remote-resources-plugin/1.0-alpha-3/maven-remote-resources-plugin-1.0-alpha-3.pom
> 3K downloaded
> [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
> '689ca74e9bddeb5ffeda58b5bc189a8318f88d1d'; remote=
> 'da39a3ee5e6b4b0d3255bfef95601890afd80709' - IGNORING
> {noformat}
--
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: (MASSEMBLY-511) Multi-Module Project --> One Jar
[ http://jira.codehaus.org/browse/MASSEMBLY-511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Casey closed MASSEMBLY-511. Resolution: Not A Bug Assignee: John Casey This is a more appropriate question for the us...@maven.apache.org mailing list. I'd start by setting up a child module with dependencies that will sort its build to the end of the multi-module build order, and configure the maven-assembly-plugin there. Then, try reading this: http://maven.apache.org/plugins/maven-assembly-plugin/examples/multimodule/module-binary-inclusion-simple.html > Multi-Module Project --> One Jar > > > Key: MASSEMBLY-511 > URL: http://jira.codehaus.org/browse/MASSEMBLY-511 > Project: Maven 2.x Assembly Plugin > Issue Type: Improvement >Affects Versions: 2.1 >Reporter: Tim Brutscher >Assignee: John Casey > > Hello everyone, > I use a Maven multi-module project. In default, maven builds one jar for > every module. Is it possible, to generate just one jar, including all the > modules? > Thank you all! > Tim -- 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-612) Bad checksums for org.codehaus.plexus:plexus-lang:1.1
[
http://jira.codehaus.org/browse/MEV-612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Juven Xu closed MEV-612.
Resolution: Fixed
Assignee: Juven Xu
fixed
> Bad checksums for org.codehaus.plexus:plexus-lang:1.1
> -
>
> Key: MEV-612
> URL: http://jira.codehaus.org/browse/MEV-612
> Project: Maven Evangelism
> Issue Type: Bug
> Components: Checksum Failure
>Reporter: Benjamin Bentmann
>Assignee: Juven Xu
>
> {noformat}
> Downloading:
> http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-lang/1.1/plexus-lang-1.1.pom
> 2K downloaded
> [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
> '9d8f550e0115aed8be989ee48064e8212b1b7ca5'; remote =
> 'da39a3ee5e6b4b0d3255bfef95601890afd80709' - RETRYING
> Downloading:
> http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-lang/1.1/plexus-lang-1.1.pom
> 2K downloaded
> [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
> '9d8f550e0115aed8be989ee48064e8212b1b7ca5'; remote =
> 'da39a3ee5e6b4b0d3255bfef95601890afd80709' - IGNORING
> Downloading:
> http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-lang/1.1/plexus-lang-1.1.jar
> 12K downloaded
> [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
> '0fe38d248d8c98518ddf8173d9152c10d0a8be0c'; remote =
> 'da39a3ee5e6b4b0d3255bfef95601890afd80709' - RETRYING
> Downloading:
> http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-lang/1.1/plexus-lang-1.1.jar
> 12K downloaded
> [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
> '0fe38d248d8c98518ddf8173d9152c10d0a8be0c'; remote =
> 'da39a3ee5e6b4b0d3255bfef95601890afd80709' - IGNORING
> {noformat}
--
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-624) Broken checksum files, xalan:xalan, xalan:serializer 2.7.1
[ http://jira.codehaus.org/browse/MEV-624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juven Xu closed MEV-624. Resolution: Fixed Assignee: Juven Xu fixed in central > Broken checksum files, xalan:xalan, xalan:serializer 2.7.1 > -- > > Key: MEV-624 > URL: http://jira.codehaus.org/browse/MEV-624 > Project: Maven Evangelism > Issue Type: Bug > Components: Checksum Failure >Reporter: Max Bowsher >Assignee: Juven Xu > > Downloading: > http://maven2.mxtelecom.com/repository/xalan/xalan/2.7.1/xalan-2.7.1.jar > 3101K downloaded > [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = > '75f1d83ce27bab5f29fff034fc74aa9f7266f22a'; remote = 'SHA1(xalan-2.7.1.jar)=' > - RETRYING > Downloading: > http://maven2.mxtelecom.com/repository/xalan/xalan/2.7.1/xalan-2.7.1.jar > 3101K downloaded > Downloading: > http://maven2.mxtelecom.com/repository/xalan/serializer/2.7.1/serializer-2.7.1.jar > 271K downloaded > [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = > '4b4b18df434451249bb65a63f2fb69e215a6a020'; remote = > 'SHA1(serializer-2.7.1.jar)=' - RETRYING > Please fix these broken checksums -- 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-589) Bad checksums on repo1.maven.org
[ http://jira.codehaus.org/browse/MEV-589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juven Xu closed MEV-589. Resolution: Fixed Assignee: Juven Xu fixed > Bad checksums on repo1.maven.org > > > Key: MEV-589 > URL: http://jira.codehaus.org/browse/MEV-589 > Project: Maven Evangelism > Issue Type: Bug > Components: Checksum Failure >Reporter: Laurent Pereira >Assignee: Juven Xu > > The following artifacts have bad checksums on repo1.maven.org : > org/apache/ws/commons/axiom/axiom-dom/1.2.7/axiom-dom-1.2.7.jar > org/apache/ws/commons/axiom/axiom-impl/1.2.7/axiom-impl-1.2.7.jar > org/apache/ws/commons/axiom/axiom-api/1.2.7/axiom-api-1.2.7.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] Closed: (MEV-635) Bad checksums for com.google.inject.** 2.0
[ http://jira.codehaus.org/browse/MEV-635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juven Xu closed MEV-635. Resolution: Fixed Assignee: Juven Xu fixed > Bad checksums for com.google.inject.** 2.0 > -- > > Key: MEV-635 > URL: http://jira.codehaus.org/browse/MEV-635 > Project: Maven Evangelism > Issue Type: Bug > Components: Checksum Failure >Reporter: Max Bowsher >Assignee: Juven Xu > > The checksums for the 2.0 versions of ALL artifacts under groupId > com.google.inject and children are invalid. -- 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-634) Invalid checksum on central for stax2-api
[ http://jira.codehaus.org/browse/MEV-634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juven Xu closed MEV-634. Resolution: Fixed Assignee: Juven Xu fixed > Invalid checksum on central for stax2-api > - > > Key: MEV-634 > URL: http://jira.codehaus.org/browse/MEV-634 > Project: Maven Evangelism > Issue Type: Bug > Components: Checksum Failure >Reporter: Julien HENRY >Assignee: Juven Xu > > Archiva refuses to download this artifact because checksum is invalid. > I know I can tell Archiva to ignore checksum failures but I guess this is not > the right way to do. > Is it possible to regenerate this checksum? -- 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-666) Invalid checksum file for pom of mysql.mysql-connector-java.5.1.13
[ http://jira.codehaus.org/browse/MEV-666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juven Xu closed MEV-666. Resolution: Fixed Assignee: Juven Xu fixed > Invalid checksum file for pom of mysql.mysql-connector-java.5.1.13 > --- > > Key: MEV-666 > URL: http://jira.codehaus.org/browse/MEV-666 > Project: Maven Evangelism > Issue Type: Bug > Components: Checksum Failure >Reporter: Vincent Hardion >Assignee: Juven Xu > > It seems there are somes problems with artifact and checksum in Maven repo > for mysql.mysql-connector-java.1.5.13 > (http://repo1.maven.org/maven2//mysql/mysql-connector-java/5.1.13/) > The md5 and sha1 files should be : mysql-connector-java-5.1.13.jar.md5 and > mysql-connector-java-5.1.13.jar.sha1 > instead of > mysql-connector-java-5.1.13.md5 and mysql-connector-java-5.1.13.sha1 (jar > extension missed). -- 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: (MSITE-515) site:site/site:deploy is mislinking modules
site:site/site:deploy is mislinking modules
---
Key: MSITE-515
URL: http://jira.codehaus.org/browse/MSITE-515
Project: Maven 2.x Site Plugin
Issue Type: Bug
Components: inheritance
Affects Versions: 2.1.1
Reporter: Benson Margulies
Using 2.1, my parent POM looks like ...
{code}
scp://hudson.basistech.net/home/projects/jug/jdd
${url.base}
jdd.website
${site.deploy.base}
{code}
and has a list of modules.
When I run mvn site:site site:deploy,
the resulting top-level page has links that look like:
{code}
Jester Document Database API
{code}
Note that the module name is in there, TWICE.
--
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-171) Modules in multi-module projects are "built" too often
[ http://jira.codehaus.org/browse/MJAVADOC-171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=239647#action_239647 ] Steve Jerman commented on MJAVADOC-171: --- I think I am running into the same problem with version 2.7 and maven 3. It is trying to fork compilations of sibling projects... Basically it ends up running out of heap space. > Modules in multi-module projects are "built" too often > -- > > Key: MJAVADOC-171 > URL: http://jira.codehaus.org/browse/MJAVADOC-171 > Project: Maven 2.x Javadoc Plugin > Issue Type: Bug >Affects Versions: 2.3 > Environment: Maven 2.0.8, Linux >Reporter: Stefan Seidel >Priority: Critical > Fix For: 2.4 > > Attachments: 2.2.log, 2.3.log, mjavadoc171.patch, mvnexec.zip > > > In a multi-module project, all modules are "built" twice for each module. > This leads to huge performance problems when many modules are in a project. > In the attached sample project, the xmlbeans plugin is executed 27 times for > a project with one parent module and two submodules. 18 of these executions > can be attributed to the javadoc plugin. With version 2.2, only 3 invocations > (once for each project) are caused by the javadoc plugin. -- 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: (MECLIPSE-671) Skipped projects still included as projects in the classpath
Skipped projects still included as projects in the classpath
Key: MECLIPSE-671
URL: http://jira.codehaus.org/browse/MECLIPSE-671
Project: Maven 2.x Eclipse Plugin
Issue Type: Bug
Components: Core : Dependencies resolution and build path (.classpath)
Affects Versions: 2.8
Reporter: Benson Margulies
I have
{code}
true
{code}
in one module. When another module has a dependency on it, m-e-p still creates
a 'src' project style .classpath link, even though there is no project to link
to, instead of creating a 'var' link to the appropriate jar file.
--
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-4866) DefaultLegacySupport leaks MavenSession instances in some cases
DefaultLegacySupport leaks MavenSession instances in some cases --- Key: MNG-4866 URL: http://jira.codehaus.org/browse/MNG-4866 Project: Maven 2 & 3 Issue Type: Bug Affects Versions: 3.0 Reporter: Igor Fedorenko When DefaultLegacySupport is used in conjunction with thread pools (ThreadPoolExecutor for example), MavenSession instance is essentially leaked via InheritableThreadLocal used by DefaultLegacySupport and will not be released to garbage collection until pooled thread is stopped and it's thread locals are cleaned up. This can result in excessive memory usage because repo system cache can be quite big. See also MNG-4860 -- 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: (MNG-4866) DefaultLegacySupport leaks MavenSession instances in some cases
[ http://jira.codehaus.org/browse/MNG-4866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Fedorenko closed MNG-4866. --- Resolution: Fixed Fix Version/s: 3.0.1 Fixed in http://svn.apache.org/viewvc?view=revision&revision=1022613 > DefaultLegacySupport leaks MavenSession instances in some cases > --- > > Key: MNG-4866 > URL: http://jira.codehaus.org/browse/MNG-4866 > Project: Maven 2 & 3 > Issue Type: Bug >Affects Versions: 3.0 >Reporter: Igor Fedorenko >Assignee: Igor Fedorenko > Fix For: 3.0.1 > > > When DefaultLegacySupport is used in conjunction with thread pools > (ThreadPoolExecutor for example), MavenSession instance is essentially leaked > via InheritableThreadLocal used by DefaultLegacySupport and will not be > released to garbage collection until pooled thread is stopped and it's thread > locals are cleaned up. This can result in excessive memory usage because repo > system cache can be quite big. See also MNG-4860 -- 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: (MSHADE-87) Shade with respect of packaging-type
Shade with respect of packaging-type Key: MSHADE-87 URL: http://jira.codehaus.org/browse/MSHADE-87 Project: Maven 2.x Shade Plugin Issue Type: Improvement Affects Versions: 1.4 Reporter: Robert Scholte The current version of the maven-shade-plugin only support jar and equal structured packaging types, but it would be great if it could shade war-files as well. At least the following should be changed: * shaded classes shouldn't be placed in the root, but in WEB-INF/classes * shaded artifacts should be removed from WEB-INF/lib -- 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: (MSITE-515) site:site/site:deploy is mislinking modules
[
http://jira.codehaus.org/browse/MSITE-515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=239664#action_239664
]
Dennis Lundberg commented on MSITE-515:
---
Can you please attach a demo project that we can use to test this issue.
> site:site/site:deploy is mislinking modules
> ---
>
> Key: MSITE-515
> URL: http://jira.codehaus.org/browse/MSITE-515
> Project: Maven 2.x Site Plugin
> Issue Type: Bug
> Components: inheritance
>Affects Versions: 2.1.1
>Reporter: Benson Margulies
>
> Using 2.1, my parent POM looks like ...
> {code}
>
>
> scp://hudson.basistech.net/home/projects/jug/jdd
>
>${url.base}
>
>
> jdd.website
> ${site.deploy.base}
>
>
> {code}
> and has a list of modules.
> When I run mvn site:site site:deploy,
> the resulting top-level page has links that look like:
> {code}
> Jester Document Database API
> {code}
> Note that the module name is in there, TWICE.
--
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: (MSITE-515) site:site/site:deploy is mislinking modules
[
http://jira.codehaus.org/browse/MSITE-515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=239665#action_239665
]
Benson Margulies commented on MSITE-515:
I can try. I have spend much time in the past failing to make small examples
that exhibit this sort of thing.
> site:site/site:deploy is mislinking modules
> ---
>
> Key: MSITE-515
> URL: http://jira.codehaus.org/browse/MSITE-515
> Project: Maven 2.x Site Plugin
> Issue Type: Bug
> Components: inheritance
>Affects Versions: 2.1.1
>Reporter: Benson Margulies
>
> Using 2.1, my parent POM looks like ...
> {code}
>
>
> scp://hudson.basistech.net/home/projects/jug/jdd
>
>${url.base}
>
>
> jdd.website
> ${site.deploy.base}
>
>
> {code}
> and has a list of modules.
> When I run mvn site:site site:deploy,
> the resulting top-level page has links that look like:
> {code}
> Jester Document Database API
> {code}
> Note that the module name is in there, TWICE.
--
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-4864) npe when transferring artifacts
[
http://jira.codehaus.org/browse/MNG-4864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=239670#action_239670
]
jgon2 commented on MNG-4864:
Apache Maven 3.0 (r1004208; 2010-10-04 13:50:56+0200)
Java version: 1.5.0_12
Java home: C:\bea923\jdk150_12\jre
Default locale: en_GB, platform encoding: Cp1252
OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
> npe when transferring artifacts
> ---
>
> Key: MNG-4864
> URL: http://jira.codehaus.org/browse/MNG-4864
> Project: Maven 2 & 3
> Issue Type: Bug
>Affects Versions: 3.0
>Reporter: jgon2
>
> I get the following NPE when running a mvn clean install with an empty local
> repository. The two stracktraces below show that the build breaks with
> different artifacts but always at the same place.
> If I relaunch the build several times, it finally succeeds.
> {code}
> Caused by: java.lang.NullPointerException
> at
> org.apache.maven.cli.ConsoleMavenTransferListener.transferProgressed(ConsoleMavenTransferListener.java:60)
>
> [ERROR] Failed to execute goal on project stdlib-core: Could not resolve
> dependencies for project com.mycompany:stdlib-core:jar:3.0.0-SNAPSHOT: Could
> not transfer artifact org.apache.maven:maven-repository-metadata:jar:2.0.8
> from nexus (http://maven/nexus/content/groups/public): NullPointerException
> -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal on project stdlib-core: Could not resolve dependencies for project
> com.mycompany:stdlib-core:jar:3.0.0-SNAPSHOT: Could not transfer artifact
> org.apache.maven:maven-repository-metadata:jar:2.0.8 from nexus
> (http://maven/nexus/content/groups/public): NullPointerException
> at
> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:190)
>
> at
> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies(LifecycleDependencyResolver.java:104)
>
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved(MojoExecutor.java:244)
>
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:187)
>
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148)
>
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:140)
>
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
>
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
>
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
>
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
>
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:314)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:151)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:445)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:168)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:132)
> 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.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
>
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
>
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> Caused by: org.apache.maven.project.DependencyResolutionException: Could not
> resolve dependencies for project
> com.mycompany:stdlib-core:jar:3.0.0-SNAPSHOT: Could not transfer artifact
> org.apache.maven:maven-repository-metadata:jar:2.0.8 from nexus
> (http://maven/nexus/content/groups/public): NullPointerException
> at
> org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(DefaultProjectDependenciesResolver.java:156)
>
> at
> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:165)
>
> ... 22 more
> Caused by: org.sonatype.aether.resolution.ArtifactResolutionException: Could
> not transfer artifact org.apache.maven:maven-repository-metadata:jar:2.0.8
> from nexus (http://maven/nexus/content/groups/public):
[jira] Commented: (MNG-4864) npe when transferring artifacts
[
http://jira.codehaus.org/browse/MNG-4864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=239689#action_239689
]
Benjamin Bentmann commented on MNG-4864:
bq. Java home: C:\bea923\jdk150_12\jre
Could you please retry this with a Sun/Oracle JRE as this looks like a JRE bug.
> npe when transferring artifacts
> ---
>
> Key: MNG-4864
> URL: http://jira.codehaus.org/browse/MNG-4864
> Project: Maven 2 & 3
> Issue Type: Bug
>Affects Versions: 3.0
>Reporter: jgon2
>
> I get the following NPE when running a mvn clean install with an empty local
> repository. The two stracktraces below show that the build breaks with
> different artifacts but always at the same place.
> If I relaunch the build several times, it finally succeeds.
> {code}
> Caused by: java.lang.NullPointerException
> at
> org.apache.maven.cli.ConsoleMavenTransferListener.transferProgressed(ConsoleMavenTransferListener.java:60)
>
> [ERROR] Failed to execute goal on project stdlib-core: Could not resolve
> dependencies for project com.mycompany:stdlib-core:jar:3.0.0-SNAPSHOT: Could
> not transfer artifact org.apache.maven:maven-repository-metadata:jar:2.0.8
> from nexus (http://maven/nexus/content/groups/public): NullPointerException
> -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal on project stdlib-core: Could not resolve dependencies for project
> com.mycompany:stdlib-core:jar:3.0.0-SNAPSHOT: Could not transfer artifact
> org.apache.maven:maven-repository-metadata:jar:2.0.8 from nexus
> (http://maven/nexus/content/groups/public): NullPointerException
> at
> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:190)
>
> at
> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies(LifecycleDependencyResolver.java:104)
>
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved(MojoExecutor.java:244)
>
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:187)
>
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148)
>
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:140)
>
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
>
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
>
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
>
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
>
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:314)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:151)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:445)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:168)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:132)
> 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.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
>
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
>
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> Caused by: org.apache.maven.project.DependencyResolutionException: Could not
> resolve dependencies for project
> com.mycompany:stdlib-core:jar:3.0.0-SNAPSHOT: Could not transfer artifact
> org.apache.maven:maven-repository-metadata:jar:2.0.8 from nexus
> (http://maven/nexus/content/groups/public): NullPointerException
> at
> org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(DefaultProjectDependenciesResolver.java:156)
>
> at
> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:165)
>
> ... 22 more
> Caused by: org.sonatype.aether.resolution.ArtifactResolutionException: Could
> not transfer artifact org.apache.maven:maven-repository-metadata:jar:2.0.8
> from nexus (http://maven/nexus/content/groups/public): NullPointerException
> at
> org.sonatype.aether.impl.internal.DefaultArtifactRe
[jira] Commented: (MNG-4850) [regression] filePermissions and directoryPermissions in settings.xml are not honoured
[ http://jira.codehaus.org/browse/MNG-4850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=239702#action_239702 ] Derek Ireland commented on MNG-4850: It appears that ... is also being ignored this means we can no longer use pscp on windows. Unfortunately we are using another plugin (tyco) which requires maven 3. > [regression] filePermissions and directoryPermissions in settings.xml are not > honoured > -- > > Key: MNG-4850 > URL: http://jira.codehaus.org/browse/MNG-4850 > Project: Maven 2 & 3 > Issue Type: Bug > Components: Settings >Affects Versions: 3.0-beta-3 >Reporter: Brett Porter >Priority: Minor > Fix For: 3.0.1 > > > The IT MavenITmng3600DeploymentModeDefaultsTest.testitMNG3600ModesSet is > currently failing for all versions of Maven 3. Correspondingly, when using > Maven 3 with an SSH wagon listed as an extension, it deploys successfully but > ignores the above settings, using default file and directory modes. -- 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
