[jira] Created: (MECLIPSE-332) mvn-eclipse-cache.properties is never filled
mvn-eclipse-cache.properties is never filled Key: MECLIPSE-332 URL: http://jira.codehaus.org/browse/MECLIPSE-332 Project: Maven 2.x Eclipse Plugin Issue Type: Bug Affects Versions: 2.4 Reporter: Wouter de Vaal See summary, the file is writen, but no data is in it, resulting in very long builds each time the eclipse update is needed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNG-3246) ScopeArtifactFilter seems not to be able to retrieve artifacts with scope provided
ScopeArtifactFilter seems not to be able to retrieve artifacts with scope provided -- Key: MNG-3246 URL: http://jira.codehaus.org/browse/MNG-3246 Project: Maven 2 Issue Type: Bug Components: Artifacts and Repositories Affects Versions: 2.0.7, 2.0.6, 2.0.5, 2.0.4, 2.0.3, 2.0.2, 2.0.1, 2.0 Reporter: Eric Hartmann Attachments: scopeartifactfilter.patch I'm using the maven ant tasks from a project that cannot be mavenized right now. I'm trying to retrieve the artifacts with scope "provided". The ant task use the ScopeArtifactFilter to retrieve those artifacts. Unfortunately the constructor miss the use of such artifacts. Here is a small patch allowing the use of scope provided and system. This filter does not allow the use of special scopes : I'm using a scope "endorsed" to identify which jar should be in the endorsed directory. As this filter does not compare the scope of artifact with the one used in the constructor, it may be usefull to store the string and in the include function to test the equality in the last else instead of returning always true. But it may not be intended to be used as this ? -- 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-1525) Can't release project with Continuum on Geronimo 2.0.1
Can't release project with Continuum on Geronimo 2.0.1 -- Key: CONTINUUM-1525 URL: http://jira.codehaus.org/browse/CONTINUUM-1525 Project: Continuum Issue Type: Bug Components: Release Affects Versions: 1.1-beta-3 Environment: Linux Reporter: Sebastian Bloch Priority: Blocker Attachments: geronimo-web.xml I've installed Continuum on Geronimo 2.0.1 Everything works fine except realese. When i want to relese there is en exception during "rewrite-poms-for-release": [INFO] Updating local copy against the scm... [INFO] Verifying that there are no local modifications... [INFO] Checking dependencies and plugins for snapshots ... [ERROR] org.apache.maven.shared.release.ReleaseExecutionException: Unable to locate dependency to process in document at org.apache.maven.shared.release.phase.AbstractRewritePomsPhase.updateDomVersion(AbstractRewritePomsPhase.java:597) at org.apache.maven.shared.release.phase.AbstractRewritePomsPhase.rewriteDependencies(AbstractRewritePomsPhase.java:352) at org.apache.maven.shared.release.phase.AbstractRewritePomsPhase.transformDocument(AbstractRewritePomsPhase.java:223) at org.apache.maven.shared.release.phase.AbstractRewritePomsPhase.transformProject(AbstractRewritePomsPhase.java:180) at org.apache.maven.shared.release.phase.AbstractRewritePomsPhase.transform(AbstractRewritePomsPhase.java:116) at org.apache.maven.shared.release.phase.AbstractRewritePomsPhase.execute(AbstractRewritePomsPhase.java:99) at org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:194) at org.apache.maven.shared.release.DefaultReleaseManager.prepareWithResult(DefaultReleaseManager.java:107) at org.apache.maven.continuum.release.executors.PrepareReleaseTaskExecutor.execute(PrepareReleaseTaskExecutor.java:43) at org.apache.maven.continuum.release.executors.AbstractReleaseTaskExecutor.executeTask(AbstractReleaseTaskExecutor.java:67) at org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable$1.run(ThreadedTaskQueueExecutor.java:116) at edu.emory.mathcs.backport.java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:442) at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run(FutureTask.java:176) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690) at java.lang.Thread.run(Thread.java:595) Caused by: org.jdom.JDOMException: java.lang.NoClassDefFoundError: org/jdom/Parent: org/jdom/Parent at org.jdom.xpath.XPath.newInstance(XPath.java:139) at org.apache.maven.shared.release.phase.AbstractRewritePomsPhase.getDependencies(AbstractRewritePomsPhase.java:433) at org.apache.maven.shared.release.phase.AbstractRewritePomsPhase.updateDomVersion(AbstractRewritePomsPhase.java:478) ... 15 more Caused by: java.lang.NoClassDefFoundError: org/jdom/Parent at org.jaxen.jdom.JDOMXPath.(JDOMXPath.java:91) at org.jdom.xpath.JaxenXPath.setXPath(JaxenXPath.java:281) at org.jdom.xpath.JaxenXPath.(JaxenXPath.java:99) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:494) at org.jdom.xpath.XPath.newInstance(XPath.java:129) ... 17 more I've added jdom-1.0.jar to the servers lib, but it didn't help -- 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-547) proxy connectors: cache failures options are confusing
proxy connectors: cache failures options are confusing -- Key: MRM-547 URL: http://jira.codehaus.org/browse/MRM-547 Project: Archiva Issue Type: Bug Components: web application Affects Versions: 1.0-beta-2 Reporter: Brett Porter Priority: Minor I think this should be renamed to just "failures" which can be "cached" or "ignored", or otherwise be changed to a yes/no value for "cached failures". -- 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-548) proxy connectors: default policies are not correct on add
proxy connectors: default policies are not correct on add - Key: MRM-548 URL: http://jira.codehaus.org/browse/MRM-548 Project: Archiva Issue Type: Bug Components: web application Affects Versions: 1.0-beta-2 Reporter: Brett Porter the default for snapshots and releases is "ignored" for updates. This is inconsistent with Maven default behaviour - should it be daily? -- 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-549) proxy connectors: no "always" option for releases and snapshots policies
proxy connectors: no "always" option for releases and snapshots policies Key: MRM-549 URL: http://jira.codehaus.org/browse/MRM-549 Project: Archiva Issue Type: Bug Components: web application Affects Versions: 1.0-beta-2 Reporter: Brett Porter -- 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-550) proxy connectors - move up/down should not show when it's not possible
proxy connectors - move up/down should not show when it's not possible -- Key: MRM-550 URL: http://jira.codehaus.org/browse/MRM-550 Project: Archiva Issue Type: Bug Components: web application Affects Versions: 1.0-beta-3 Reporter: Brett Porter it seems in beta-3 that there was a change to the layout of the proxy connector pages, and it has ordering now. However, "up" still appears on the first one, as does "down" on the last, even though they aren't relevant. -- 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-551) the default default scan cron expression is once a day, should be hourly
the default default scan cron expression is once a day, should be hourly Key: MRM-551 URL: http://jira.codehaus.org/browse/MRM-551 Project: Archiva Issue Type: Bug Components: system Affects Versions: 1.0-beta-2 Reporter: Brett Porter 0 0 0 * * -> 0 0 * * *, I think -- 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-552) Download link should be entitled "Plugin", not "Jar" for maven plugins
Download link should be entitled "Plugin", not "Jar" for maven plugins -- Key: MRM-552 URL: http://jira.codehaus.org/browse/MRM-552 Project: Archiva Issue Type: Bug Components: web application Affects Versions: 1.0-beta-2 Reporter: Brett Porter -- 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: (MRM-551) the default scan cron expression is once a day, should be hourly
[ http://jira.codehaus.org/browse/MRM-551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MRM-551: - Summary: the default scan cron expression is once a day, should be hourly (was: the default default scan cron expression is once a day, should be hourly) > the default scan cron expression is once a day, should be hourly > > > Key: MRM-551 > URL: http://jira.codehaus.org/browse/MRM-551 > Project: Archiva > Issue Type: Bug > Components: system >Affects Versions: 1.0-beta-2 >Reporter: Brett Porter > > 0 0 0 * * -> 0 0 * * *, I think -- 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-553) removing conf/shared.xml from plexus runtime causes save appearance to fail
removing conf/shared.xml from plexus runtime causes save appearance to fail --- Key: MRM-553 URL: http://jira.codehaus.org/browse/MRM-553 Project: Archiva Issue Type: Bug Components: system Affects Versions: 1.0-beta-2 Reporter: Brett Porter -- 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-1772) Please Upload Grester 1.0 Into Maven Public Repository (groupId now altered)
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Nyika closed MAVENUPLOAD-1772. -- Resolution: Fixed Will Correct GroupId and ArtifactIds in a new minor version release > Please Upload Grester 1.0 Into Maven Public Repository (groupId now altered) > > > Key: MAVENUPLOAD-1772 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1772 > Project: maven-upload-requests > Issue Type: New Feature >Reporter: Michael Nyika > Attachments: maven-grester-plugin-1.0-bundle.jar > > > Grester is a Maven2 Plugin for Jester. Grester's groupId for version 1.0 has > been changed to grester.sf.net (from the previous org.apache.maven.plugins > which is reserved for apache.org ). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-3071) Add a command line option to dump the contents of all the classloaders used during an invocation of Maven
[ http://jira.codehaus.org/browse/MNG-3071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Fox updated MNG-3071: --- Fix Version/s: (was: 2.0.8) 2.0.9 bumping to the next version > Add a command line option to dump the contents of all the classloaders used > during an invocation of Maven > - > > Key: MNG-3071 > URL: http://jira.codehaus.org/browse/MNG-3071 > Project: Maven 2 > Issue Type: New Feature >Affects Versions: 2.0.7 >Reporter: Jason van Zyl > Fix For: 2.0.9 > > > It is very annoying to track down what versions of what are being used, so > add a mode to the command line to dump the contents of the class realms being > used. -- 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-2881) Improve logging when downloading snapshots in offline mode
[ http://jira.codehaus.org/browse/MNG-2881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Fox updated MNG-2881: --- Fix Version/s: (was: 2.0.8) 2.0.9 bumping to the next version > Improve logging when downloading snapshots in offline mode > -- > > Key: MNG-2881 > URL: http://jira.codehaus.org/browse/MNG-2881 > Project: Maven 2 > Issue Type: Improvement > Components: Artifacts and Repositories >Affects Versions: 2.0.5 >Reporter: Jason van Zyl >Priority: Minor > Fix For: 2.0.9 > > > Even though the network is not touched we get logging output like this: > --->8--- > [INFO] snapshot > org.codehaus.plexus:plexus-appserver-maven-plugin:2.0-alpha-8-SNAPSHOT: > checking for updates from apache.snapshots > [DEBUG] System is offline. Cannot resolve metadata: > Repository Metadata > -- > GroupId: org.codehaus.plexus > ArtifactId: plexus-appserver-maven-plugin > Metadata Type: > org.apache.maven.artifact.repository.metadata.SnapshotArtifactRepositoryMetadata > --->8--- -- 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-2883) Make sure that the network isn't used for snapshots in offline mode when legacy repositories are used
[ http://jira.codehaus.org/browse/MNG-2883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Fox updated MNG-2883: --- Fix Version/s: (was: 2.0.8) 2.0.9 bumping to the next version > Make sure that the network isn't used for snapshots in offline mode when > legacy repositories are used > - > > Key: MNG-2883 > URL: http://jira.codehaus.org/browse/MNG-2883 > Project: Maven 2 > Issue Type: Task > Components: Artifacts and Repositories >Affects Versions: 2.0.5 >Reporter: Jason van Zyl >Assignee: Jason van Zyl > Fix For: 2.0.9 > > > We determined that the network is not touched for m2 repositories in offline > mode, but make sure the same holds true for legacy repositories. -- 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-2963) Do not update metadata unless the artifact actually made it down
[ http://jira.codehaus.org/browse/MNG-2963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Fox updated MNG-2963: --- Fix Version/s: (was: 2.0.8) 2.0.9 bumping to the next version > Do not update metadata unless the artifact actually made it down > > > Key: MNG-2963 > URL: http://jira.codehaus.org/browse/MNG-2963 > Project: Maven 2 > Issue Type: Bug > Components: Artifacts and Repositories >Affects Versions: 2.0.x >Reporter: Jason van Zyl > Fix For: 2.0.9 > > > We can also have a secondary check to see that if a metadata file contains no > valid versions to nuke it and try to download a valid one. This will correct > anything left over from previous versions of Maven. -- 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-552) Download link should be entitled "Plugin", not "Jar" for maven plugins
[ http://jira.codehaus.org/browse/MRM-552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110297 ] Joakim Erdfelt commented on MRM-552: Current: The download link works off of the filename. The filename does not contain enough information to glean the proper type. Possible: Using maven-.*-plugin or .*-maven-plugin as an identification string is possible. > Download link should be entitled "Plugin", not "Jar" for maven plugins > -- > > Key: MRM-552 > URL: http://jira.codehaus.org/browse/MRM-552 > Project: Archiva > Issue Type: Bug > Components: web application >Affects Versions: 1.0-beta-2 >Reporter: Brett Porter > -- 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-3246) ScopeArtifactFilter seems not to be able to retrieve artifacts with scope provided
[ http://jira.codehaus.org/browse/MNG-3246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Hartmann closed MNG-3246. -- Resolution: Won't Fix After more investigation, it seems that the problem is not here as the recursive resolution of artifact need to be done as it is. The maven-ant-task use this filter and it does not return what I expected but this may be filtered after the resolution. Sorry for the noise. > ScopeArtifactFilter seems not to be able to retrieve artifacts with scope > provided > -- > > Key: MNG-3246 > URL: http://jira.codehaus.org/browse/MNG-3246 > Project: Maven 2 > Issue Type: Bug > Components: Artifacts and Repositories >Affects Versions: 2.0, 2.0.1, 2.0.2, 2.0.3, 2.0.4, 2.0.5, 2.0.6, 2.0.7 >Reporter: Eric Hartmann > Attachments: scopeartifactfilter.patch > > > I'm using the maven ant tasks from a project that cannot be mavenized right > now. > I'm trying to retrieve the artifacts with scope "provided". The ant task use > the ScopeArtifactFilter to retrieve those artifacts. Unfortunately the > constructor miss the use of such artifacts. > Here is a small patch allowing the use of scope provided and system. > This filter does not allow the use of special scopes : I'm using a scope > "endorsed" to identify which jar should be in the endorsed directory. As this > filter does not compare the scope of artifact with the one used in the > constructor, it may be usefull to store the string and in the include > function to test the equality in the last else instead of returning always > true. But it may not be intended to be used as this ? -- 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-1526) the NOTICE file is overzealous in declaring dependencies
the NOTICE file is overzealous in declaring dependencies Key: CONTINUUM-1526 URL: http://jira.codehaus.org/browse/CONTINUUM-1526 Project: Continuum Issue Type: Improvement Affects Versions: 1.1-beta-2 Reporter: Brett Porter Fix For: 1.1-beta-4 we only need to say, for example, software developed by the ASF once, and all the unnamed ones don't need to be there. This might require fixes in the remote reosurces plugin and an update. -- 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] Moved: (MRRESOURCES-24) the NOTICE file is overzealous in declaring dependencies
[ http://jira.codehaus.org/browse/MRRESOURCES-24?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse moved CONTINUUM-1526 to MRRESOURCES-24: Affects Version/s: (was: 1.1-beta-2) 1.0-alpha-5 Fix Version/s: (was: 1.1-beta-4) 1.0-alpha-6 Complexity: (was: Intermediate) Key: MRRESOURCES-24 (was: CONTINUUM-1526) Project: Maven 2.x Remote Resources Plugin (was: Continuum) > the NOTICE file is overzealous in declaring dependencies > > > Key: MRRESOURCES-24 > URL: http://jira.codehaus.org/browse/MRRESOURCES-24 > Project: Maven 2.x Remote Resources Plugin > Issue Type: Improvement >Affects Versions: 1.0-alpha-5 >Reporter: Brett Porter > Fix For: 1.0-alpha-6 > > > we only need to say, for example, software developed by the ASF once, and all > the unnamed ones don't need to be there. > This might require fixes in the remote reosurces plugin and an update. -- 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: (MRRESOURCES-24) the NOTICE file is overzealous in declaring dependencies
[ http://jira.codehaus.org/browse/MRRESOURCES-24?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110319 ] Emmanuel Venisse commented on MRRESOURCES-24: - See comments in CONTINUUM-1388 > the NOTICE file is overzealous in declaring dependencies > > > Key: MRRESOURCES-24 > URL: http://jira.codehaus.org/browse/MRRESOURCES-24 > Project: Maven 2.x Remote Resources Plugin > Issue Type: Improvement >Affects Versions: 1.0-alpha-5 >Reporter: Brett Porter > Fix For: 1.0-alpha-6 > > > we only need to say, for example, software developed by the ASF once, and all > the unnamed ones don't need to be there. > This might require fixes in the remote reosurces plugin and an update. -- 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: (MRRESOURCES-24) the NOTICE file is overzealous in declaring dependencies
[ http://jira.codehaus.org/browse/MRRESOURCES-24?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110324 ] Emmanuel Venisse commented on MRRESOURCES-24: - Fixed in trunk and in apache-jar-resource-bundle 1.3-SNAPSHOT > the NOTICE file is overzealous in declaring dependencies > > > Key: MRRESOURCES-24 > URL: http://jira.codehaus.org/browse/MRRESOURCES-24 > Project: Maven 2.x Remote Resources Plugin > Issue Type: Improvement >Affects Versions: 1.0-alpha-5 >Reporter: Brett Porter > Fix For: 1.0-alpha-6 > > > we only need to say, for example, software developed by the ASF once, and all > the unnamed ones don't need to be there. > This might require fixes in the remote reosurces plugin and an update. -- 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: (MRRESOURCES-24) the NOTICE file is overzealous in declaring dependencies
[ http://jira.codehaus.org/browse/MRRESOURCES-24?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse closed MRRESOURCES-24. --- Assignee: Emmanuel Venisse Resolution: Fixed > the NOTICE file is overzealous in declaring dependencies > > > Key: MRRESOURCES-24 > URL: http://jira.codehaus.org/browse/MRRESOURCES-24 > Project: Maven 2.x Remote Resources Plugin > Issue Type: Improvement >Affects Versions: 1.0-alpha-5 >Reporter: Brett Porter >Assignee: Emmanuel Venisse > Fix For: 1.0-alpha-6 > > > we only need to say, for example, software developed by the ASF once, and all > the unnamed ones don't need to be there. > This might require fixes in the remote reosurces plugin and an update. -- 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-546) Ant 1.6.5 has groupId 'ant', Ant 1.7.0 has groupId 'org.apache.ant', needs "relocation"
[ http://jira.codehaus.org/browse/MEV-546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MEV-546. -- Assignee: Carlos Sanchez Resolution: Won't Fix relocations have some issues, we can't relocate old groups without possible breaking old builds, so your option would be to use exclusions > Ant 1.6.5 has groupId 'ant', Ant 1.7.0 has groupId 'org.apache.ant', needs > "relocation" > --- > > Key: MEV-546 > URL: http://jira.codehaus.org/browse/MEV-546 > Project: Maven Evangelism > Issue Type: Bug > Components: Relocation >Reporter: Brian Topping >Assignee: Carlos Sanchez > > Ant 1.6.5 has groupId 'ant', Ant 1.7.0 has groupId 'org.apache.ant', and it > doesn't appear that the project has been properly relocated. I'm having an > issue with a local dependency on 1.6.5 (which should establish the desired > version with a "nearer" resolution) and the difference in groupId causing > 1.7.0 to be imported transitively. -- 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-548) Broken checksums, junit/junit/maven-metadata.xml
[ http://jira.codehaus.org/browse/MEV-548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MEV-548. -- Assignee: Carlos Sanchez Resolution: Fixed > Broken checksums, junit/junit/maven-metadata.xml > > > Key: MEV-548 > URL: http://jira.codehaus.org/browse/MEV-548 > Project: Maven Evangelism > Issue Type: Bug >Reporter: Max Bowsher >Assignee: Carlos Sanchez > > Checksums for junit/junit/maven-metadata.xml are broken. > Broken checksums in central make it awkward to run with 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] Created: (MAVENUPLOAD-1773) Please upload Grester v1.0.1 to Maven Public Repository
Please upload Grester v1.0.1 to Maven Public Repository --- Key: MAVENUPLOAD-1773 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1773 Project: maven-upload-requests Issue Type: New Feature Reporter: Michael Nyika Changed the groupId to net.sf.grester; artifactId is now grester; version is 1.0.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-78) Suppression filter is ignored
[
http://jira.codehaus.org/browse/MCHECKSTYLE-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110342
]
Dennis Lundberg commented on MCHECKSTYLE-78:
This sound like MCHECKSTYLE-67.
Can you either try 2.2-SNAPSHOT or use the workaround specified in the above
issue?
> Suppression filter is ignored
> -
>
> Key: MCHECKSTYLE-78
> URL: http://jira.codehaus.org/browse/MCHECKSTYLE-78
> Project: Maven 2.x Checkstyle Plugin
> Issue Type: Bug
>Affects Versions: 2.1
> Environment: Redhat Enterprise Linux, maven 2.0.6
>Reporter: Peter F. Peterson
>
> Inside my pom I have
>
> org.apache.maven.plugins
> maven-checkstyle-plugin
>
>
>
>
> ${basedir}/src/checkstyle/suppressions.xml
> LICENSE.txt
> xref
>
>
> And checkstyle fails to find the suppression file which is in the specified
> location. Here is the abbreviated build messages
> [DEBUG] resolveLocation(null, checkstyle-packages.xml)
> [DEBUG]
> resolveLocation(/SNS/users/pf9/eclipse-workspace/sns-translation-core/src/checkstyle/suppressions.xml,
> checkstyle-suppressions.xml)
> [DEBUG] Location is not a URL.
> [DEBUG] Potential File:
> /SNS/users/pf9/eclipse-workspace/sns-translation-core/src/checkstyle/suppressions.xml
> [INFO]
>
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] An error has occurred in Checkstyle report generation.
> Embedded error: failed to load suppressions location:
> /SNS/users/pf9/eclipse-workspace/sns-translation-core/src/checkstyle/suppressions.xml
> Connection timed out
> [INFO]
>
> [DEBUG] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: An error has occurred
> in Checkstyle report generation.
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:564)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecycle(DefaultLifecycleExecutor.java:903)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(DefaultLifecycleExecutor.java:739)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:510)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:272)
> 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.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.plugin.MojoExecutionException: An error has
> occurred in Checkstyle report generation.
> at
> org.apache.maven.reporting.AbstractMavenReport.execute(AbstractMavenReport.java:79)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
> ... 19 more
> Caused by: org.apache.maven.reporting.MavenReportException: failed to load
> suppressions location:
> /SNS/users/pf9/eclipse-workspace/sns-translation-core/src/checkstyle/suppressions.xml
> at
> org.apache.maven.plugin.checkstyle.CheckstyleReport.getSuppressions(CheckstyleReport.java:990)
> at
> org.apache.maven.plugin.checkstyle.CheckstyleReport.executeCheckstyle(CheckstyleReport.java:680)
> at
> org.apache.maven.plugin.checkstyle.CheckstyleReport.executeReport(CheckstyleReport.java:4
[jira] Commented: (MRM-549) proxy connectors: no "always" option for releases and snapshots policies
[ http://jira.codehaus.org/browse/MRM-549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110343 ] Joakim Erdfelt commented on MRM-549: The option for 'ignore' is the same thing. This kinda falls into line with the on-screen instructions and details that I started to outline in MRM-366. > proxy connectors: no "always" option for releases and snapshots policies > > > Key: MRM-549 > URL: http://jira.codehaus.org/browse/MRM-549 > Project: Archiva > Issue Type: Bug > Components: web application >Affects Versions: 1.0-beta-2 >Reporter: Brett Porter > -- 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-3245) Maven Reporting API is binary incompatible in 2.0.8-SNAPSHOT by r579987
[ http://jira.codehaus.org/browse/MNG-3245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110341 ] Vincent Siveton commented on MNG-3245: -- I cannot reproduce your error with both maven and checkstyle snapshot. If you use 2.0.8-SNAPSHOT, try with 2.0.7. FYI, no change in the API had been reported in 2.0.5, 2.0.6 and 2.0.7. > Maven Reporting API is binary incompatible in 2.0.8-SNAPSHOT by r579987 > --- > > Key: MNG-3245 > URL: http://jira.codehaus.org/browse/MNG-3245 > Project: Maven 2 > Issue Type: Bug > Components: Sites & Reporting >Affects Versions: 2.0.8 >Reporter: James William Dumay >Assignee: Vincent Siveton >Priority: Blocker > Fix For: 2.0.8 > > Attachments: maven-doxia-rollback.patch, sample-exception-report.txt > > > See example exception file attached. > I tracked the problem down to this change: > r579987 | vsiveton | 2007-09-27 22:31:07 +1000 (Thu, 27 Sep 2007) | 2 lines > o bumped to the release doxia-sink-api > o used org.apache.maven.doxia.sink.Sink instead of the deprecated > org.codehaus.doxia.sink.Sink > Ill attempt a rollback locally of the change and report back. -- 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: (MWAR-89) filtering ${something.url} ignores my property value and writes http://maven.apache.org/something
[
http://jira.codehaus.org/browse/MWAR-89?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Earl Marwil updated MWAR-89:
Attachment: example.zip
Example from previous post.
> filtering ${something.url} ignores my property value and writes
> http://maven.apache.org/something
> -
>
> Key: MWAR-89
> URL: http://jira.codehaus.org/browse/MWAR-89
> Project: Maven 2.x War Plugin
> Issue Type: Bug
>Affects Versions: 2.0.2
>Reporter: Paul Jungwirth
>Assignee: Stephane Nicoll
>Priority: Minor
> Attachments: example.zip
>
>
> I have a multimodule build, and one of the modules is a war. That module has
> an artifactId of "aardvark." This is aardvark's pom:
>
> ...
>
> http://anywhere.com/
> whatever
>
> ...
>
>
>
> maven-war-plugin
>
>
>
>${basedir}/src/main/resources
>true
>
>
>
>
>
>
>
> Inside src/main/resources, I have a file that includes both ${something.url}
> and ${another.property}. But when I run maven, ${another.property} is
> filtered correctly, while ${something.url} becomes
> "http://maven.apache.org/aardvark."; It ignores my value and writes a URL to
> apache.org instead, appending the artifactId. Weird, huh? This seems to
> happen with any property that ends in ".url." Is this supposed to be a
> feature? I've never seen it documented anywhere.
> Thanks,
> Paul
--
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: (MWAR-89) filtering ${something.url} ignores my property value and writes http://maven.apache.org/something
[
http://jira.codehaus.org/browse/MWAR-89?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110345
]
Earl Marwil commented on MWAR-89:
-
I encountered this bug while attempting to create profiles for development,
testing, and production. The difference in these profiles is in specification
of the database driver, url, and credentials. If I set up the filtering in the
build element in the pom, the filtering works fine and my jdbc.properties file
is situated in WEB-INF/classes. If instead, I want the jdbc.properties file in
WEB-INF/conf, the same filter applied in the maven-war-plugin behaves as
described in this issue, namely, the project.url gets substituted for
${jdbc.url} rather than the value specified for jdbc.url defined in my filter.
I am attaching a minimal project that reproduces these observations in my
environment (Linux, Maven 2.0.7, Java 1.5.0_13, and
maven-war-plugin-2.0.2.jar). I built with the command:
{noformat}
mvn clean compile war:exploded
{noformat}
I have found a couple of other potentially related issues, MWAR-96 and
MRESOURCES-20. I wonder if there is some dependency misalignment in the
plugins. So far I have been unsuccessful in building the maven-war-plugin from
SVN since I keep getting failures on the tests.
> filtering ${something.url} ignores my property value and writes
> http://maven.apache.org/something
> -
>
> Key: MWAR-89
> URL: http://jira.codehaus.org/browse/MWAR-89
> Project: Maven 2.x War Plugin
> Issue Type: Bug
>Affects Versions: 2.0.2
>Reporter: Paul Jungwirth
>Assignee: Stephane Nicoll
>Priority: Minor
> Attachments: example.zip
>
>
> I have a multimodule build, and one of the modules is a war. That module has
> an artifactId of "aardvark." This is aardvark's pom:
>
> ...
>
> http://anywhere.com/
> whatever
>
> ...
>
>
>
> maven-war-plugin
>
>
>
>${basedir}/src/main/resources
>true
>
>
>
>
>
>
>
> Inside src/main/resources, I have a file that includes both ${something.url}
> and ${another.property}. But when I run maven, ${another.property} is
> filtered correctly, while ${something.url} becomes
> "http://maven.apache.org/aardvark."; It ignores my value and writes a URL to
> apache.org instead, appending the artifactId. Weird, huh? This seems to
> happen with any property that ends in ".url." Is this supposed to be a
> feature? I've never seen it documented anywhere.
> Thanks,
> Paul
--
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-549) proxy connectors: no "always" option for releases and snapshots policies
[ http://jira.codehaus.org/browse/MRM-549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110350 ] Joakim Erdfelt commented on MRM-549: I think you might be mis-interpreting the policy settings. See http://docs.codehaus.org/display/MAVENUSER/Archiva+Proxy+Policies > proxy connectors: no "always" option for releases and snapshots policies > > > Key: MRM-549 > URL: http://jira.codehaus.org/browse/MRM-549 > Project: Archiva > Issue Type: Bug > Components: web application >Affects Versions: 1.0-beta-2 >Reporter: Brett Porter > -- 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-548) proxy connectors: default policies are not correct on add
[ http://jira.codehaus.org/browse/MRM-548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110351 ] Joakim Erdfelt commented on MRM-548: I think you might be mis-interpreting the policy settings. See http://docs.codehaus.org/display/MAVENUSER/Archiva+Proxy+Policies > proxy connectors: default policies are not correct on add > - > > Key: MRM-548 > URL: http://jira.codehaus.org/browse/MRM-548 > Project: Archiva > Issue Type: Bug > Components: web application >Affects Versions: 1.0-beta-2 >Reporter: Brett Porter > > the default for snapshots and releases is "ignored" for updates. This is > inconsistent with Maven default behaviour - should it be daily? -- 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-214) scm:tag with scmCommentPrefix
[ http://jira.codehaus.org/browse/MRELEASE-214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110355 ] Nick Stolwijk commented on MRELEASE-214: I've tested this with a recent checkout of the plugin 2.0-beta-7-SNAPSHOT and cannot reproduce it. I've build revision 586102 of the plugin and tested it with the following configuration: org.apache.maven.plugins maven-release-plugin 2.0-beta-7-SNAPSHOT [TRAC-BLA] The [TRAC-BLA] was added to each checkin comment and also was in release.properties. Also tried it with: org.apache.maven.plugins maven-release-plugin 2.0-beta-7-SNAPSHOT and performed mvn release:prepare -DscmCommentPrefix=[TRAC-BLA], same result. I'm on a Linux machine, using Maven 2.0.7 and Java 6. > scm:tag with scmCommentPrefix > - > > Key: MRELEASE-214 > URL: http://jira.codehaus.org/browse/MRELEASE-214 > Project: Maven 2.x Release Plugin > Issue Type: Improvement > Components: scm >Affects Versions: 2.0-beta-5 > Environment: macosx >Reporter: fabio melen >Assignee: Emmanuel Venisse > Fix For: 2.0-beta-5 > > > My svn repository use a pre-commit hook in order to check the commit message > and to validate it (Trac integration). So I'd like that the scm:tag, invoked > from release:prepare, inherits the scmCommentPrefix value. > ciao > fabio -- 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: (MANTTASKS-67) artifact:deploy - The name of deploying element in snapshot repository is wrong
[ http://jira.codehaus.org/browse/MANTTASKS-67?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MANTTASKS-67: --- Assignee: Herve Boutemy Description: The zip file contains test with Ant. To launch it : ant test. I try to deploy a snapshot artifact in repository So, my pom.xml contains a version with the extension '-SNAPSHOT' And in my build file Ant i do this : In the repository the name of the artifact is -SNAPSHOT. instead of .- Another problem, i try to upload 2 attachments with my artifact (javadoc and java-source), and the buildNumber in the meta-data.xml increment by 3 instead of 1 You can test it with : ant testWithAttach was: The zip file contains test with Ant. To launch it : ant test. I try to deploy a snapshot artifact in repository So, my pom.xml contains a version with the extension '-SNAPSHOT' And in my build file Ant i do this : In the repository the name of the artifact is --SNAPSHOT. instead of --.-- Another problem, i try to upload 2 attachments with my artifact (javadoc and java-source), and the buildNumber in the meta-data.xml increment by 3 instead of 1 You can test it with : ant testWithAttach Remaining Estimate: 0 minutes Original Estimate: 0 minutes > artifact:deploy - The name of deploying element in snapshot repository is > wrong > --- > > Key: MANTTASKS-67 > URL: http://jira.codehaus.org/browse/MANTTASKS-67 > Project: Maven 2.x Ant Tasks > Issue Type: Bug > Components: deploy task >Affects Versions: 2.0.6, 2.0.7 >Reporter: David N'DIAYE >Assignee: Herve Boutemy > Fix For: 2.0.8 > > Attachments: MANTTASKS-67.diff, testSnapshots.zip > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > The zip file contains test with Ant. > To launch it : ant test. > I try to deploy a snapshot artifact in repository > So, my pom.xml contains a version with the extension '-SNAPSHOT' > And in my build file Ant i do this : > > > > > In the repository the name of the artifact is > -SNAPSHOT. instead of > .- > Another problem, i try to upload 2 attachments with my artifact (javadoc and > java-source), and the buildNumber in the meta-data.xml increment by 3 instead > of 1 > > > > > > > You can test it with : ant testWithAttach -- 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-78) Suppression filter is ignored
[
http://jira.codehaus.org/browse/MCHECKSTYLE-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110363
]
Peter F. Peterson commented on MCHECKSTYLE-78:
--
Modifying the pom according to 67 seems to have worked. The new config is
org.apache.maven.plugins
maven-checkstyle-plugin
config/sun_checks.xml
${basedir}/src/checkstyle/suppressions.xml
${basedir}/src/checkstyle/suppressions.xml
LICENSE.txt
xref
Alternatively removing the suppressionsFileExpression and using 2.2-SNAPSHOT
does not work.
Thank you for the useful comment for a work-around. I am leaving the ticket
open since either the documentation needs to be updated or the next release
needs to fix this.
> Suppression filter is ignored
> -
>
> Key: MCHECKSTYLE-78
> URL: http://jira.codehaus.org/browse/MCHECKSTYLE-78
> Project: Maven 2.x Checkstyle Plugin
> Issue Type: Bug
>Affects Versions: 2.1
> Environment: Redhat Enterprise Linux, maven 2.0.6
>Reporter: Peter F. Peterson
>
> Inside my pom I have
>
> org.apache.maven.plugins
> maven-checkstyle-plugin
>
>
>
>
> ${basedir}/src/checkstyle/suppressions.xml
> LICENSE.txt
> xref
>
>
> And checkstyle fails to find the suppression file which is in the specified
> location. Here is the abbreviated build messages
> [DEBUG] resolveLocation(null, checkstyle-packages.xml)
> [DEBUG]
> resolveLocation(/SNS/users/pf9/eclipse-workspace/sns-translation-core/src/checkstyle/suppressions.xml,
> checkstyle-suppressions.xml)
> [DEBUG] Location is not a URL.
> [DEBUG] Potential File:
> /SNS/users/pf9/eclipse-workspace/sns-translation-core/src/checkstyle/suppressions.xml
> [INFO]
>
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] An error has occurred in Checkstyle report generation.
> Embedded error: failed to load suppressions location:
> /SNS/users/pf9/eclipse-workspace/sns-translation-core/src/checkstyle/suppressions.xml
> Connection timed out
> [INFO]
>
> [DEBUG] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: An error has occurred
> in Checkstyle report generation.
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:564)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecycle(DefaultLifecycleExecutor.java:903)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(DefaultLifecycleExecutor.java:739)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:510)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:272)
> 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.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.plugin.MojoExecutionException: An error has
> occurred in Checkstyle report generation.
> at
> org.apache.maven.reporting.AbstractMavenReport.execute(AbstractMavenReport.java:79)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
> ... 19 more
> Caused by: org.apache.maven.reporti
[jira] Updated: (MANTTASKS-23) antlib:deploy doesn't set correct snapshot version
[ http://jira.codehaus.org/browse/MANTTASKS-23?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MANTTASKS-23: --- Assignee: Herve Boutemy Description: I'm trying to deploy to maven remote repository jars produced by ant. Those jars are in snapshot version. Whole deployment process is going properly, but something is wrong with names of deployed files. When I'm deploying artifacts using normal 'maven deploy', "SNAPSHOT" in the name is replaced by the current timestamp and the snapshot number (for instance: "20060105.123437-3"). But when I'm deploying with antlib, the name isn't changed. "SNAPSHOT" is still in the name. And when I deploy snapshot again, the old one is replaced by the new one (which also different from behavior of normal 'mvn deploy'). The metadata.xml also is generated incorrectly. Timestamp in snapshot tag is missing: foo foo-jar1 1.0-SNAPSHOT 4 20060209111228 Here's an fragment of my ant script: The artifacts poms are in separate files which contain only artifactId, groupId, version, dependencies and remote repository url. I also tried to deploy using 'mvn -f pom-file.xml deploy' to check if my repository url is specified correctly. And it works. Jar is deployed to remote repository with correct version. was: I'm trying to deploy to maven remote repository jars produced by ant. Those jars are in snapshot version. Whole deployment process is going properly, but something is wrong with names of deployed files. When I'm deploying artifacts using normal 'maven deploy', "SNAPSHOT" in the name is replaced by the current timestamp and the snapshot number (for instance: "20060105.123437-3"). But when I'm deploying with antlib, the name isn't changed. "SNAPSHOT" is still in the name. And when I deploy snapshot again, the old one is replaced by the new one (which also different from behavior of normal 'mvn deploy'). The metadata.xml also is generated incorrectly. Timestamp in snapshot tag is missing: foo foo-jar1 1.0-SNAPSHOT 4 20060209111228 Here's an fragment of my ant script: The artifacts poms are in separate files which contain only artifactId, groupId, version, dependencies and remote repository url. I also tried to deploy using 'mvn -f pom-file.xml deploy' to check if my repository url is specified correctly. And it works. Jar is deployed to remote repository with correct version. Remaining Estimate: 0 minutes Original Estimate: 0 minutes > antlib:deploy doesn't set correct snapshot version > -- > > Key: MANTTASKS-23 > URL: http://jira.codehaus.org/browse/MANTTASKS-23 > Project: Maven 2.x Ant Tasks > Issue Type: Bug > Components: deploy task >Affects Versions: 2.0.4, 2.0.6, 2.0.7 > Environment: win xp, mvn 2.0.2, ant 1.6.5 >Reporter: Michal Stochmialek >Assignee: Herve Boutemy > Fix For: 2.0.8 > > Attachments: MANTTASKS-23.diff, MANTTASKS-23_site.diff, > maven-artifact-ant-MNG-2060.patch > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > I'm trying to deploy to maven remote repository jars produced by > ant. Those jars are in snapshot version. > Whole deployment process is going properly, but something is wrong with names > of deployed files. > When I'm deploying artifacts using normal 'maven deploy', "SNAPSHOT" in > the name is replaced by the current timestamp and the snapshot number (for > instance: "20060105.123437-3"). > But when I'm deploying with antlib, the name isn't changed. "SNAPSHOT" is > still in the name. And when I deploy snapshot again, the old one is > replaced by the new one (which also different from behavior of normal 'mvn > deploy'). > The metadata.xml also is generated incorrectly. Timestamp in snapshot tag is > missing: > > foo > foo-jar1 > 1.0-SNAPSHOT > > > 4 > > 20060209111228 > > > Here's an fragment of my ant script: > > > > > > depends="maven-poms,generate-jars"> > > > > > > > > > > > > > > > > > > > > > > > > The artifacts poms are in separate files which contain only artifactId, > groupId, > version, dependencies and remote repository url. > I also tried to deploy using 'mvn -f pom-file.xml deploy' to check if my > repository > url is specified correctly. And it works. Jar is deployed to remote >
[jira] Closed: (MANTTASKS-67) artifact:deploy - The name of deploying element in snapshot repository is wrong
[ http://jira.codehaus.org/browse/MANTTASKS-67?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed MANTTASKS-67. -- Resolution: Fixed > artifact:deploy - The name of deploying element in snapshot repository is > wrong > --- > > Key: MANTTASKS-67 > URL: http://jira.codehaus.org/browse/MANTTASKS-67 > Project: Maven 2.x Ant Tasks > Issue Type: Bug > Components: deploy task >Affects Versions: 2.0.6, 2.0.7 >Reporter: David N'DIAYE >Assignee: Herve Boutemy > Fix For: 2.0.8 > > Attachments: MANTTASKS-67.diff, testSnapshots.zip > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > The zip file contains test with Ant. > To launch it : ant test. > I try to deploy a snapshot artifact in repository > So, my pom.xml contains a version with the extension '-SNAPSHOT' > And in my build file Ant i do this : > > > > > In the repository the name of the artifact is > -SNAPSHOT. instead of > .- > Another problem, i try to upload 2 attachments with my artifact (javadoc and > java-source), and the buildNumber in the meta-data.xml increment by 3 instead > of 1 > > > > > > > You can test it with : ant testWithAttach -- 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: (MANTTASKS-23) antlib:deploy doesn't set correct snapshot version
[ http://jira.codehaus.org/browse/MANTTASKS-23?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed MANTTASKS-23. -- Resolution: Fixed the updatedBuildNumber is fixed by MANTTASKS-67 > antlib:deploy doesn't set correct snapshot version > -- > > Key: MANTTASKS-23 > URL: http://jira.codehaus.org/browse/MANTTASKS-23 > Project: Maven 2.x Ant Tasks > Issue Type: Bug > Components: deploy task >Affects Versions: 2.0.4, 2.0.6, 2.0.7 > Environment: win xp, mvn 2.0.2, ant 1.6.5 >Reporter: Michal Stochmialek >Assignee: Herve Boutemy > Fix For: 2.0.8 > > Attachments: MANTTASKS-23.diff, MANTTASKS-23_site.diff, > maven-artifact-ant-MNG-2060.patch > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > I'm trying to deploy to maven remote repository jars produced by > ant. Those jars are in snapshot version. > Whole deployment process is going properly, but something is wrong with names > of deployed files. > When I'm deploying artifacts using normal 'maven deploy', "SNAPSHOT" in > the name is replaced by the current timestamp and the snapshot number (for > instance: "20060105.123437-3"). > But when I'm deploying with antlib, the name isn't changed. "SNAPSHOT" is > still in the name. And when I deploy snapshot again, the old one is > replaced by the new one (which also different from behavior of normal 'mvn > deploy'). > The metadata.xml also is generated incorrectly. Timestamp in snapshot tag is > missing: > > foo > foo-jar1 > 1.0-SNAPSHOT > > > 4 > > 20060209111228 > > > Here's an fragment of my ant script: > > > > > > depends="maven-poms,generate-jars"> > > > > > > > > > > > > > > > > > > > > > > > > The artifacts poms are in separate files which contain only artifactId, > groupId, > version, dependencies and remote repository url. > I also tried to deploy using 'mvn -f pom-file.xml deploy' to check if my > repository > url is specified correctly. And it works. Jar is deployed to remote > repository with > correct version. -- 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: (MANTTASKS-85) settings config ignored for remoteRepositories not defined in pom
[ http://jira.codehaus.org/browse/MANTTASKS-85?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MANTTASKS-85: --- Assignee: Herve Boutemy Remaining Estimate: 0 minutes Original Estimate: 0 minutes > settings config ignored for remoteRepositories not defined in pom > - > > Key: MANTTASKS-85 > URL: http://jira.codehaus.org/browse/MANTTASKS-85 > Project: Maven 2.x Ant Tasks > Issue Type: Bug > Components: dependencies task, install-provider task >Affects Versions: 2.0.7 >Reporter: Herve Boutemy >Assignee: Herve Boutemy > Fix For: 2.0.8 > > Attachments: MANTTASKS-85.diff > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > see > http://www.nabble.com/maven-ant-tasks-2.0.7-settings-file-read-hangs-at-install-provider-tf4230543s177.html -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MANTTASKS-85) settings config ignored for remoteRepositories not defined in pom
[ http://jira.codehaus.org/browse/MANTTASKS-85?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed MANTTASKS-85. -- Resolution: Fixed > settings config ignored for remoteRepositories not defined in pom > - > > Key: MANTTASKS-85 > URL: http://jira.codehaus.org/browse/MANTTASKS-85 > Project: Maven 2.x Ant Tasks > Issue Type: Bug > Components: dependencies task, install-provider task >Affects Versions: 2.0.7 >Reporter: Herve Boutemy >Assignee: Herve Boutemy > Fix For: 2.0.8 > > Attachments: MANTTASKS-85.diff > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > see > http://www.nabble.com/maven-ant-tasks-2.0.7-settings-file-read-hangs-at-install-provider-tf4230543s177.html -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MANTTASKS-23) antlib:deploy doesn't set correct snapshot version
[ http://jira.codehaus.org/browse/MANTTASKS-23?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110370 ] Ben Hale commented on MANTTASKS-23: --- Is this being built as CI somewhere? I'd love to test it out. > antlib:deploy doesn't set correct snapshot version > -- > > Key: MANTTASKS-23 > URL: http://jira.codehaus.org/browse/MANTTASKS-23 > Project: Maven 2.x Ant Tasks > Issue Type: Bug > Components: deploy task >Affects Versions: 2.0.4, 2.0.6, 2.0.7 > Environment: win xp, mvn 2.0.2, ant 1.6.5 >Reporter: Michal Stochmialek >Assignee: Herve Boutemy > Fix For: 2.0.8 > > Attachments: MANTTASKS-23.diff, MANTTASKS-23_site.diff, > maven-artifact-ant-MNG-2060.patch > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > I'm trying to deploy to maven remote repository jars produced by > ant. Those jars are in snapshot version. > Whole deployment process is going properly, but something is wrong with names > of deployed files. > When I'm deploying artifacts using normal 'maven deploy', "SNAPSHOT" in > the name is replaced by the current timestamp and the snapshot number (for > instance: "20060105.123437-3"). > But when I'm deploying with antlib, the name isn't changed. "SNAPSHOT" is > still in the name. And when I deploy snapshot again, the old one is > replaced by the new one (which also different from behavior of normal 'mvn > deploy'). > The metadata.xml also is generated incorrectly. Timestamp in snapshot tag is > missing: > > foo > foo-jar1 > 1.0-SNAPSHOT > > > 4 > > 20060209111228 > > > Here's an fragment of my ant script: > > > > > > depends="maven-poms,generate-jars"> > > > > > > > > > > > > > > > > > > > > > > > > The artifacts poms are in separate files which contain only artifactId, > groupId, > version, dependencies and remote repository url. > I also tried to deploy using 'mvn -f pom-file.xml deploy' to check if my > repository > url is specified correctly. And it works. Jar is deployed to remote > repository with > correct version. -- 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: (MANTTASKS-23) antlib:deploy doesn't set correct snapshot version
[ http://jira.codehaus.org/browse/MANTTASKS-23?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110371 ] Carlos Sanchez commented on MANTTASKS-23: - if it is, it should be in http://maven.zones.apache.org/continuum if not you can request it being added in the maven-dev mailing list > antlib:deploy doesn't set correct snapshot version > -- > > Key: MANTTASKS-23 > URL: http://jira.codehaus.org/browse/MANTTASKS-23 > Project: Maven 2.x Ant Tasks > Issue Type: Bug > Components: deploy task >Affects Versions: 2.0.4, 2.0.6, 2.0.7 > Environment: win xp, mvn 2.0.2, ant 1.6.5 >Reporter: Michal Stochmialek >Assignee: Herve Boutemy > Fix For: 2.0.8 > > Attachments: MANTTASKS-23.diff, MANTTASKS-23_site.diff, > maven-artifact-ant-MNG-2060.patch > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > I'm trying to deploy to maven remote repository jars produced by > ant. Those jars are in snapshot version. > Whole deployment process is going properly, but something is wrong with names > of deployed files. > When I'm deploying artifacts using normal 'maven deploy', "SNAPSHOT" in > the name is replaced by the current timestamp and the snapshot number (for > instance: "20060105.123437-3"). > But when I'm deploying with antlib, the name isn't changed. "SNAPSHOT" is > still in the name. And when I deploy snapshot again, the old one is > replaced by the new one (which also different from behavior of normal 'mvn > deploy'). > The metadata.xml also is generated incorrectly. Timestamp in snapshot tag is > missing: > > foo > foo-jar1 > 1.0-SNAPSHOT > > > 4 > > 20060209111228 > > > Here's an fragment of my ant script: > > > > > > depends="maven-poms,generate-jars"> > > > > > > > > > > > > > > > > > > > > > > > > The artifacts poms are in separate files which contain only artifactId, > groupId, > version, dependencies and remote repository url. > I also tried to deploy using 'mvn -f pom-file.xml deploy' to check if my > repository > url is specified correctly. And it works. Jar is deployed to remote > repository with > correct version. -- 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-3247) specifying the dependency order
[ http://jira.codehaus.org/browse/MNG-3247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110407 ] Wendy Smoak commented on MNG-3247: -- This would better asked on the user list where you'll have a wider audience of people who may have run into the same situation. You can find subscription info here: http://maven.apache.org/mail-lists.html Does MNG-3197 apply? Not sure if this is an exact duplicate, but the fix there would probably help. > specifying the dependency order > > > Key: MNG-3247 > URL: http://jira.codehaus.org/browse/MNG-3247 > Project: Maven 2 > Issue Type: Bug > Components: Dependencies >Reporter: madan bysani > > In our project we have two dependency jar files > 1. Product.jar -- that is related to the product > release > 2. customization_product.jar -- has selected class files > from Product.jar that has been modified to be override the > original class files and in addition has new class files as > part of the customization. > Is there any way to specify the order of the jar files for > compilation in the pom.xml > The classpath should look like this for correct compilation. > classpath=customization_product.jar;Product.jar -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-3197) Direct dependencies should come before transitive dependencies in build classpath.
[ http://jira.codehaus.org/browse/MNG-3197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110406 ] Wendy Smoak commented on MNG-3197: -- Related thread: http://www.nabble.com/Classpath-ordering-of-dependencies-tf4402468s177.html > Direct dependencies should come before transitive dependencies in build > classpath. > -- > > Key: MNG-3197 > URL: http://jira.codehaus.org/browse/MNG-3197 > Project: Maven 2 > Issue Type: Improvement >Affects Versions: 2.0.7 >Reporter: Paul Gier > Attachments: MNG-3197-maven-artifact-r574693.patch > > > Currently the transitive dependencies appear to take priority over direct > dependencies in the compile and test classpaths. > For example project A depends on B version 2 and C version 1: > A -> B.2 > A -> C.1 -> B.1 > When the tests are run, the classpath will be in an order similar to: > B.1:C.1:B.2 > Since B.1 comes first in the classpath, it will be used when running the > tests. But it seems that B.2 should be used when testing because it has the > direct 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: (MANTTASKS-90) classifier not supported
classifier not supported Key: MANTTASKS-90 URL: http://jira.codehaus.org/browse/MANTTASKS-90 Project: Maven 2.x Ant Tasks Issue Type: Bug Affects Versions: 2.0.7 Environment: na Reporter: t redeske Priority: Minor while the ant tasks support groupId, artifactId, type, and version, they do not support classifier. -- 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-78) Suppression filter is ignored
[
http://jira.codehaus.org/browse/MCHECKSTYLE-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110395
]
Peter F. Peterson commented on MCHECKSTYLE-78:
--
I've determined what was generating the error. It appears that the change in
checkstyle between 2.0 and 2.1 is that it is now using validation when parsing.
The offending line:
http://www.puppycrawl.com/dtds/suppressions_1_0.dtd";>
is now
http://www.puppycrawl.com/dtds/suppressions_1_0.dtd";>
In case you can't see it, "Puppy Crawl/DTD" became "Puppy Crawl//DTD". The
misdiagnoses is a result of a poor error message
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] An error has occurred in Checkstyle report generation.
Embedded error: failed to load suppressions location:
/SNS/users/pf9/eclipse-workspace/sns-translation-core/src/checkstyle/suppressions.xml
Connection timed out
Which was not clear enough.
> Suppression filter is ignored
> -
>
> Key: MCHECKSTYLE-78
> URL: http://jira.codehaus.org/browse/MCHECKSTYLE-78
> Project: Maven 2.x Checkstyle Plugin
> Issue Type: Bug
>Affects Versions: 2.1
> Environment: Redhat Enterprise Linux, maven 2.0.6
>Reporter: Peter F. Peterson
> Fix For: 2.1
>
>
> Inside my pom I have
>
> org.apache.maven.plugins
> maven-checkstyle-plugin
>
>
>
>
> ${basedir}/src/checkstyle/suppressions.xml
> LICENSE.txt
> xref
>
>
> And checkstyle fails to find the suppression file which is in the specified
> location. Here is the abbreviated build messages
> [DEBUG] resolveLocation(null, checkstyle-packages.xml)
> [DEBUG]
> resolveLocation(/SNS/users/pf9/eclipse-workspace/sns-translation-core/src/checkstyle/suppressions.xml,
> checkstyle-suppressions.xml)
> [DEBUG] Location is not a URL.
> [DEBUG] Potential File:
> /SNS/users/pf9/eclipse-workspace/sns-translation-core/src/checkstyle/suppressions.xml
> [INFO]
>
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] An error has occurred in Checkstyle report generation.
> Embedded error: failed to load suppressions location:
> /SNS/users/pf9/eclipse-workspace/sns-translation-core/src/checkstyle/suppressions.xml
> Connection timed out
> [INFO]
>
> [DEBUG] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: An error has occurred
> in Checkstyle report generation.
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:564)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecycle(DefaultLifecycleExecutor.java:903)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(DefaultLifecycleExecutor.java:739)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:510)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:272)
> 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.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.plugin.MojoExecutionException: An error has
> occurred in Checkstyle report generation.
> at
> org.apache.maven.reporting.AbstractMavenReport.execute(AbstractMavenReport
[jira] Closed: (MCHECKSTYLE-78) Suppression filter is ignored
[
http://jira.codehaus.org/browse/MCHECKSTYLE-78?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter F. Peterson closed MCHECKSTYLE-78.
Resolution: Won't Fix
Fix Version/s: 2.1
Better error messages would have suggested the problem more quickly.
> Suppression filter is ignored
> -
>
> Key: MCHECKSTYLE-78
> URL: http://jira.codehaus.org/browse/MCHECKSTYLE-78
> Project: Maven 2.x Checkstyle Plugin
> Issue Type: Bug
>Affects Versions: 2.1
> Environment: Redhat Enterprise Linux, maven 2.0.6
>Reporter: Peter F. Peterson
> Fix For: 2.1
>
>
> Inside my pom I have
>
> org.apache.maven.plugins
> maven-checkstyle-plugin
>
>
>
>
> ${basedir}/src/checkstyle/suppressions.xml
> LICENSE.txt
> xref
>
>
> And checkstyle fails to find the suppression file which is in the specified
> location. Here is the abbreviated build messages
> [DEBUG] resolveLocation(null, checkstyle-packages.xml)
> [DEBUG]
> resolveLocation(/SNS/users/pf9/eclipse-workspace/sns-translation-core/src/checkstyle/suppressions.xml,
> checkstyle-suppressions.xml)
> [DEBUG] Location is not a URL.
> [DEBUG] Potential File:
> /SNS/users/pf9/eclipse-workspace/sns-translation-core/src/checkstyle/suppressions.xml
> [INFO]
>
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] An error has occurred in Checkstyle report generation.
> Embedded error: failed to load suppressions location:
> /SNS/users/pf9/eclipse-workspace/sns-translation-core/src/checkstyle/suppressions.xml
> Connection timed out
> [INFO]
>
> [DEBUG] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: An error has occurred
> in Checkstyle report generation.
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:564)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecycle(DefaultLifecycleExecutor.java:903)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(DefaultLifecycleExecutor.java:739)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:510)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:272)
> 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.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.plugin.MojoExecutionException: An error has
> occurred in Checkstyle report generation.
> at
> org.apache.maven.reporting.AbstractMavenReport.execute(AbstractMavenReport.java:79)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
> ... 19 more
> Caused by: org.apache.maven.reporting.MavenReportException: failed to load
> suppressions location:
> /SNS/users/pf9/eclipse-workspace/sns-translation-core/src/checkstyle/suppressions.xml
> at
> org.apache.maven.plugin.checkstyle.CheckstyleReport.getSuppressions(CheckstyleReport.java:990)
> at
> org.apache.maven.plugin.checkstyle.CheckstyleReport.executeCheckstyle(CheckstyleReport.java:680)
> at
> org.apache.maven.plugin.checkstyle.CheckstyleReport.executeReport(CheckstyleRepor
[jira] Updated: (MNG-3245) Maven Reporting API is binary incompatible in 2.0.8-SNAPSHOT by r579987
[ http://jira.codehaus.org/browse/MNG-3245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James William Dumay updated MNG-3245: - Attachment: atlassian-user-latest.tar.gz Unpack and run with maven 2.0.8-SNAPSHOT from trunk: mvn clean site > Maven Reporting API is binary incompatible in 2.0.8-SNAPSHOT by r579987 > --- > > Key: MNG-3245 > URL: http://jira.codehaus.org/browse/MNG-3245 > Project: Maven 2 > Issue Type: Bug > Components: Sites & Reporting >Affects Versions: 2.0.8 >Reporter: James William Dumay >Assignee: Vincent Siveton >Priority: Blocker > Fix For: 2.0.8 > > Attachments: atlassian-user-latest.tar.gz, > maven-doxia-rollback.patch, sample-exception-report.txt > > > See example exception file attached. > I tracked the problem down to this change: > r579987 | vsiveton | 2007-09-27 22:31:07 +1000 (Thu, 27 Sep 2007) | 2 lines > o bumped to the release doxia-sink-api > o used org.apache.maven.doxia.sink.Sink instead of the deprecated > org.codehaus.doxia.sink.Sink > Ill attempt a rollback locally of the change and report back. -- 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-3245) Maven Reporting API is binary incompatible in 2.0.8-SNAPSHOT by r579987
[ http://jira.codehaus.org/browse/MNG-3245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110389 ] James William Dumay commented on MNG-3245: -- Vincent, checkout a project that uses site docs. then generate the site using: mvn clean site You should get the exception. Ill upload a testcase for you in a moment. > Maven Reporting API is binary incompatible in 2.0.8-SNAPSHOT by r579987 > --- > > Key: MNG-3245 > URL: http://jira.codehaus.org/browse/MNG-3245 > Project: Maven 2 > Issue Type: Bug > Components: Sites & Reporting >Affects Versions: 2.0.8 >Reporter: James William Dumay >Assignee: Vincent Siveton >Priority: Blocker > Fix For: 2.0.8 > > Attachments: maven-doxia-rollback.patch, sample-exception-report.txt > > > See example exception file attached. > I tracked the problem down to this change: > r579987 | vsiveton | 2007-09-27 22:31:07 +1000 (Thu, 27 Sep 2007) | 2 lines > o bumped to the release doxia-sink-api > o used org.apache.maven.doxia.sink.Sink instead of the deprecated > org.codehaus.doxia.sink.Sink > Ill attempt a rollback locally of the change and report back. -- 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-458) the NOTICE file is overzealous in declaring dependencies
[ http://jira.codehaus.org/browse/MRM-458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110386 ] Brett Porter commented on MRM-458: -- Continuum has recently addressed this so we can leverage the work done there. > the NOTICE file is overzealous in declaring dependencies > > > Key: MRM-458 > URL: http://jira.codehaus.org/browse/MRM-458 > Project: Archiva > Issue Type: Improvement >Affects Versions: 1.0-beta-1 >Reporter: Brett Porter > Fix For: 1.0-beta-3 > > > we only need to say, for example, software developed by the ASF once, and all > the unnamed ones don't need to be there. > This might require fixes in the remote reosurces plugin and an update. -- 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: (MRM-204) Request for Documentation answers
[ http://jira.codehaus.org/browse/MRM-204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MRM-204: - Fix Version/s: (was: 1.0-beta-3) 1.0-beta-4 > Request for Documentation answers > - > > Key: MRM-204 > URL: http://jira.codehaus.org/browse/MRM-204 > Project: Archiva > Issue Type: Wish > Components: documentation >Reporter: Henri Yandell > Fix For: 1.0-beta-4 > > Attachments: MRM-204-wsmoak1.diff > > > Could somebody explain what the following mean and are used for: > Identifiers. > Proxied Repositories. > Observers. -- 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: (MRM-141) update design documentation
[ http://jira.codehaus.org/browse/MRM-141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MRM-141: - Fix Version/s: (was: 1.0-beta-3) 1.0-beta-4 > update design documentation > --- > > Key: MRM-141 > URL: http://jira.codehaus.org/browse/MRM-141 > Project: Archiva > Issue Type: Task > Components: design >Reporter: Brett Porter > Fix For: 1.0-beta-4 > > > - the indexing design docs don't indicate how to use the indexer from an API > perspective > - there needs to be a more general "this is the architecture" design document -- 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: (MRM-490) add xwork exception handling pages for presentable error reporting
[ http://jira.codehaus.org/browse/MRM-490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MRM-490: - Fix Version/s: (was: 1.0-beta-3) 1.0-beta-4 > add xwork exception handling pages for presentable error reporting > -- > > Key: MRM-490 > URL: http://jira.codehaus.org/browse/MRM-490 > Project: Archiva > Issue Type: Bug > Components: web application >Affects Versions: 1.0-beta-2 >Reporter: Brett Porter > Fix For: 1.0-beta-4 > > > if anyone gets a stack trace, they should have an easy way to report it as a > bug (though this should also be configurable since in a production > environment the admin would want to be contacted instead) -- 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: (MRM-552) Download link should be entitled "Plugin", not "Jar" for maven plugins
[ http://jira.codehaus.org/browse/MRM-552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MRM-552: - Fix Version/s: (was: 1.0-beta-3) 1.x > Download link should be entitled "Plugin", not "Jar" for maven plugins > -- > > Key: MRM-552 > URL: http://jira.codehaus.org/browse/MRM-552 > Project: Archiva > Issue Type: Bug > Components: web application >Affects Versions: 1.0-beta-2 >Reporter: Brett Porter > Fix For: 1.x > > -- 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: (MRM-553) removing conf/shared.xml from plexus runtime causes save appearance to fail
[ http://jira.codehaus.org/browse/MRM-553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MRM-553: - Fix Version/s: (was: 1.0-beta-3) 1.x > removing conf/shared.xml from plexus runtime causes save appearance to fail > --- > > Key: MRM-553 > URL: http://jira.codehaus.org/browse/MRM-553 > Project: Archiva > Issue Type: Bug > Components: system >Affects Versions: 1.0-beta-2 >Reporter: Brett Porter > Fix For: 1.x > > -- 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: (MRM-526) cache-failure policy timeout should be easily configurable
[ http://jira.codehaus.org/browse/MRM-526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MRM-526: - Fix Version/s: (was: 1.0-beta-3) 1.x > cache-failure policy timeout should be easily configurable > -- > > Key: MRM-526 > URL: http://jira.codehaus.org/browse/MRM-526 > Project: Archiva > Issue Type: Improvement > Components: remote proxy >Affects Versions: 1.0-beta-2 >Reporter: JR Boyens > Fix For: 1.x > > > set in a plexus.xml deep in archiva-policy.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] Updated: (MRM-550) proxy connectors - move up/down should not show when it's not possible
[ http://jira.codehaus.org/browse/MRM-550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MRM-550: - Fix Version/s: (was: 1.0-beta-3) 1.x > proxy connectors - move up/down should not show when it's not possible > -- > > Key: MRM-550 > URL: http://jira.codehaus.org/browse/MRM-550 > Project: Archiva > Issue Type: Bug > Components: web application >Affects Versions: 1.0-beta-3 >Reporter: Brett Porter > Fix For: 1.x > > > it seems in beta-3 that there was a change to the layout of the proxy > connector pages, and it has ordering now. However, "up" still appears on the > first one, as does "down" on the last, even though they aren't relevant. -- 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: (MRM-448) validation for reports form
[ http://jira.codehaus.org/browse/MRM-448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MRM-448: - Fix Version/s: (was: 1.0-beta-3) 1.x > validation for reports form > --- > > Key: MRM-448 > URL: http://jira.codehaus.org/browse/MRM-448 > Project: Archiva > Issue Type: Bug > Components: web application >Affects Versions: 1.0-beta-1 >Reporter: Brett Porter > Fix For: 1.x > > > validation is missing - see MRM-329 -- 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-549) proxy connectors: no "always" option for releases and snapshots policies
[ http://jira.codehaus.org/browse/MRM-549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110384 ] Brett Porter commented on MRM-549: -- I think the policy settings are misleading. Every option applies to the artifact, while "ignored" applies to the policy. I think these should be changed. > proxy connectors: no "always" option for releases and snapshots policies > > > Key: MRM-549 > URL: http://jira.codehaus.org/browse/MRM-549 > Project: Archiva > Issue Type: Bug > Components: web application >Affects Versions: 1.0-beta-2 >Reporter: Brett Porter > Fix For: 1.0-beta-3 > > -- 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-548) proxy connectors: default policies are not correct on add
[ http://jira.codehaus.org/browse/MRM-548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110383 ] Brett Porter commented on MRM-548: -- so every request for metadata hits the proxies by default? That doesn't sound right either. I'll address the confusing options in the other issue. > proxy connectors: default policies are not correct on add > - > > Key: MRM-548 > URL: http://jira.codehaus.org/browse/MRM-548 > Project: Archiva > Issue Type: Bug > Components: web application >Affects Versions: 1.0-beta-2 >Reporter: Brett Porter > Fix For: 1.0-beta-3 > > > the default for snapshots and releases is "ignored" for updates. This is > inconsistent with Maven default behaviour - should it be daily? -- 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-3245) Maven Reporting API is binary incompatible in 2.0.8-SNAPSHOT by r579987
[ http://jira.codehaus.org/browse/MNG-3245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110381 ] Vincent Siveton commented on MNG-3245: -- Brett, I try these steps: Clean my repo Install maven 2.0.8-SNAPSHOT (r586191) Call mvn checkstyle:checkstyle (so using maven-checkstyle-plugin:2.1) no error here... > Maven Reporting API is binary incompatible in 2.0.8-SNAPSHOT by r579987 > --- > > Key: MNG-3245 > URL: http://jira.codehaus.org/browse/MNG-3245 > Project: Maven 2 > Issue Type: Bug > Components: Sites & Reporting >Affects Versions: 2.0.8 >Reporter: James William Dumay >Assignee: Vincent Siveton >Priority: Blocker > Fix For: 2.0.8 > > Attachments: maven-doxia-rollback.patch, sample-exception-report.txt > > > See example exception file attached. > I tracked the problem down to this change: > r579987 | vsiveton | 2007-09-27 22:31:07 +1000 (Thu, 27 Sep 2007) | 2 lines > o bumped to the release doxia-sink-api > o used org.apache.maven.doxia.sink.Sink instead of the deprecated > org.codehaus.doxia.sink.Sink > Ill attempt a rollback locally of the change and report back. -- 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-552) Download link should be entitled "Plugin", not "Jar" for maven plugins
[ http://jira.codehaus.org/browse/MRM-552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110372 ] Brett Porter commented on MRM-552: -- we have enough info on that page to display the type - we render a plugin icon after all > Download link should be entitled "Plugin", not "Jar" for maven plugins > -- > > Key: MRM-552 > URL: http://jira.codehaus.org/browse/MRM-552 > Project: Archiva > Issue Type: Bug > Components: web application >Affects Versions: 1.0-beta-2 >Reporter: Brett Porter > Fix For: 1.0-beta-3 > > -- 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: (MRM-542) Publish code coverage statistics on the project website
[ http://jira.codehaus.org/browse/MRM-542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MRM-542: - Fix Version/s: (was: 1.0-beta-3) 1.x > Publish code coverage statistics on the project website > --- > > Key: MRM-542 > URL: http://jira.codehaus.org/browse/MRM-542 > Project: Archiva > Issue Type: Improvement > Components: documentation >Affects Versions: 1.0-beta-3 >Reporter: Wendy Smoak > Fix For: 1.x > > > I had to comment out the Cobertura plugin in the reporting section of the > parent pom in order to get the site to build. > It was complaining about a missing cobertura.ser file in > archiva-signature-consumers and archiva-applet. > Needs to be investigated and re-enabled, preferably with results aggregated > at the top level. > See http://maven.apache.org/archiva/ref/1.0-beta-3-SNAPSHOT/ for the latest > docs and archiva/trunk/pom.xml for 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: (MNG-3247) specifying the dependency order
specifying the dependency order Key: MNG-3247 URL: http://jira.codehaus.org/browse/MNG-3247 Project: Maven 2 Issue Type: Bug Components: Dependencies Reporter: madan bysani In our project we have two dependency jar files 1. Product.jar -- that is related to the product release 2. customization_product.jar -- has selected class files from Product.jar that has been modified to be override the original class files and in addition has new class files as part of the customization. Is there any way to specify the order of the jar files for compilation in the pom.xml The classpath should look like this for correct compilation. classpath=customization_product.jar;Product.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] Created: (MJAR-86) Jarsigner option 'storetype' not supported by the plugin
Jarsigner option 'storetype' not supported by the plugin Key: MJAR-86 URL: http://jira.codehaus.org/browse/MJAR-86 Project: Maven 2.x Jar Plugin Issue Type: New Feature Components: sign Affects Versions: 2.1 Environment: winxp Reporter: sijo cherian We use storetype=pkcs12 . The Plugin donot seem to support that configuration parameter -- 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-3245) Maven Reporting API is binary incompatible in 2.0.8-SNAPSHOT by r579987
[ http://jira.codehaus.org/browse/MNG-3245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110379 ] Brett Porter commented on MNG-3245: --- Vincent, the problem is that it won't work with non-snapshot versions of everything (which is what most people are using :). If you use maven 2.0.8-SNAPSHOT with a released version of the checkstyle plugin, can you reproduce the problem? > Maven Reporting API is binary incompatible in 2.0.8-SNAPSHOT by r579987 > --- > > Key: MNG-3245 > URL: http://jira.codehaus.org/browse/MNG-3245 > Project: Maven 2 > Issue Type: Bug > Components: Sites & Reporting >Affects Versions: 2.0.8 >Reporter: James William Dumay >Assignee: Vincent Siveton >Priority: Blocker > Fix For: 2.0.8 > > Attachments: maven-doxia-rollback.patch, sample-exception-report.txt > > > See example exception file attached. > I tracked the problem down to this change: > r579987 | vsiveton | 2007-09-27 22:31:07 +1000 (Thu, 27 Sep 2007) | 2 lines > o bumped to the release doxia-sink-api > o used org.apache.maven.doxia.sink.Sink instead of the deprecated > org.codehaus.doxia.sink.Sink > Ill attempt a rollback locally of the change and report back. -- 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: (MRM-185) revise logging granularity
[ http://jira.codehaus.org/browse/MRM-185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MRM-185: - Fix Version/s: (was: 1.0-beta-3) 1.0-beta-4 > revise logging granularity > -- > > Key: MRM-185 > URL: http://jira.codehaus.org/browse/MRM-185 > Project: Archiva > Issue Type: Improvement > Components: system >Reporter: Brett Porter > Fix For: 1.0-beta-4 > > > in particular, check that JPOX logging is at the correct level, but generally > turn the noise down. -- 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
