Re: Site plugin
Hi Jason, Looking at the stack trace it seems to be the remote resources plugin that is throwing an NPE. Didn't you release 1.5 of that plugin because of issues with core? Your build is using 1.4... -- Dennis Lundberg Den 22 feb 2014 05:30 skrev Jason van Zyl ja...@takari.io: Not sure who looks after the site plugin these days but I can't run the staging part to copy it over to the production site: In the release checkout I ran: mvn -Preporting site site:stage and got: https://gist.github.com/jvanzyl/9148731 I'll continue on with the rest of the work but I will release tomorrow regardless. I don't have time to debug the site plugin. Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl http://twitter.com/takari_io - Simplex sigillum veri. (Simplicity is the seal of truth.)
Re: Releasing the release plugin
Caused by: org.codehaus.plexus.component.repository.exception.ComponentRepositoryException: Component descriptor role: 'org.apache.maven.scm.manager.ScmManager', implementation: 'org.apache.maven.scm.manager.plexus.DefaultScmManager', role hint: 'default' has a hint, but there are other implementations that don't Indeed I can find several implementations of ScmManager: org.apache.maven.scm.manager.plexus.DefaultScmManager org.apache.maven.scm.manager.BasicScmManager org.apache.maven.scm.manager.ScmManagerStub org.apache.maven.shared.release.stubs.ScmManagerStub but only the DefaultScmManager is a Plexus Component. It seems like the xml-files under /maven-release-manager/src/test/resources/org/apache/maven/shared/release/phase cause the problem. These specify the Stubs as implementation for the ScmManager, which clarifies the Exception. But how can the upgrade of SCM have effect on this? It looks like there is an invalid dependency kicking in... Robert Op Fri, 21 Feb 2014 16:56:06 +0100 schreef Benson Margulies bimargul...@gmail.com: I checked out the trunk and tried a simple 'mvn test', and I'm drowning in test failures. Anyone have a hint? --- Test set: org.apache.maven.shared.release.DefaultReleaseManagerTest --- Tests run: 30, Failures: 0, Errors: 30, Skipped: 0, Time elapsed: 0.875 sec FAILURE! - in org.apache.maven.shared.release.DefaultReleaseManagerTest testPrepareNoCompletedPhase(org.apache.maven.shared.release.DefaultReleaseManagerTest) Time elapsed: 0.062 sec ERROR! org.codehaus.plexus.PlexusContainerException: Error starting container at org.codehaus.plexus.component.repository.DefaultComponentRepository.addComponentDescriptor(DefaultComponentRepository.java:184) at org.codehaus.plexus.DefaultPlexusContainer.addComponentDescriptor(DefaultPlexusContainer.java:515) at org.codehaus.plexus.DefaultPlexusContainer.discoverComponents(DefaultPlexusContainer.java:738) at org.codehaus.plexus.DefaultPlexusContainer.start(DefaultPlexusContainer.java:779) at org.codehaus.plexus.PlexusTestCase.setUp(PlexusTestCase.java:121) at org.apache.maven.shared.release.DefaultReleaseManagerTest.setUp(DefaultReleaseManagerTest.java:75) - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven 3.2.1
Artifacts have been pushed to Maven Central. I'll wait for them to arrive before announcing and publishing the main site. On Feb 20, 2014, at 3:22 AM, Olivier Lamy ol...@apache.org wrote: +1 finally it's agile @apache :P On 20 February 2014 13:30, Igor Fedorenko i...@ifedorenko.com wrote: Jason, Stephen, other PMC members, I can't really know if there is behind-the-scenes pmc-only discussion going on, but is there any chance to get 3.2.1 released this week? I need to do legal/IP paperwork for upcoming m2e 1.5 release by this coming Friday, and I would really like to list Maven 3.2.1 as the included runtime. I am already past submission deadline and m2e will be stuck with 3.1.1 until at least September unless 3.2.1 is declared next day or two. -- Regards, Igor On 2/17/2014, 6:31, Stephen Connolly wrote: +1 (binding) -Stephen On 17 February 2014 01:13, Jason van Zyl ja...@takari.io wrote: Cool. No dire rush. On Feb 16, 2014, at 2:31 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: Jason, FYI I intend testing tomorrow AM (GMT). Expect my vote by noon/1pm GMT On Sunday, 16 February 2014, Mirko Friedenhagen mfriedenha...@gmail.com wrote: +1 (non-binding) Regards Mirko -- http://illegalstateexception.blogspot.com/ https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen) https://bitbucket.org/mfriedenhagen/ On Sun, Feb 16, 2014 at 10:14 PM, Baptiste Mathus bmat...@batmat.net javascript:; wrote: +1 (non-binding). 2014-02-16 4:59 GMT+01:00 Mark Derricutt m...@talios.comjavascript:; : +1 here, seems to be working for all my projects. Don't seem to be getting the aether lock up either now, now I'm just suffering version-range hell of mixed feature branches there ( a hell of my own making ;p ) Mark On 15 Feb 2014, at 6:58, Jason van Zyl wrote: Specifically the zip, tarball, and source archives can be found here: https://repository.apache.org/content/repositories/maven- 1006/org/apache/maven/apache-maven/3.2.1/apache-maven-3.2.1-bin.zip - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.orgjavascript:; For additional commands, e-mail: dev-h...@maven.apache.org javascript:; -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor ! - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org javascript:; For additional commands, e-mail: dev-h...@maven.apache.orgjavascript:; -- Sent from my phone Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl http://twitter.com/takari_io - You are never dedicated to something you have complete confidence in. No one is fanatically shouting that the sun is going to rise tomorrow. They know it is going to rise tomorrow. When people are fanatically dedicated to political or religious faiths or any other kind of dogmas or goals, it's always because these dogmas or goals are in doubt. -- Robert Pirzig, Zen and the Art of Motorcycle Maintenance - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Olivier Lamy Ecetera: http://ecetera.com.au http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl http://twitter.com/takari_io - People develop abstractions by generalizing from concrete examples. Every attempt to determine the correct abstraction on paper without actually developing a running system is doomed to failure. No one is that smart. A framework is a resuable design, so you develop it by looking at the things it is supposed to be a design of. The more examples you look at, the more general your framework will be. -- Ralph Johnson Don Roberts, Patterns for Evolving Frameworks
Re: Releasing the release plugin
On Sat, Feb 22, 2014 at 7:38 AM, Robert Scholte rfscho...@apache.org wrote: src/test/resources/org/apache/maven/shared/release/phase I'm trying to use a less ancient version of plexus-container-default, it requires some test changes, I'll let you know what happens. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Releasing the release plugin
Plexus-container-default 1.5.5 changes some issues. This seems to make some things better. The first failure is: testNoSnapshotDependencies(org.apache.maven.shared.release.phase.CheckDependencySnapshotsPhaseTest) Time elapsed: 0.07 sec ERROR! org.codehaus.plexus.component.repository.exception.ComponentLookupException: Unable to lookup component 'org.apache.maven.project.MavenProjectBuilder', it could not be started. role: org.apache.maven.project.MavenProjectBuilder roleHint: default classRealm: plexus.core - realm =plexus.core strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy Number of foreign imports: 0 - at org.codehaus.plexus.component.collections.ComponentList.remove(ComponentList.java:91) And this happens over and over. I am checking if I can make it go away. the scm component error is gone, or at least hiding. On Sat, Feb 22, 2014 at 11:44 AM, Benson Margulies bimargul...@gmail.com wrote: On Sat, Feb 22, 2014 at 7:38 AM, Robert Scholte rfscho...@apache.org wrote: src/test/resources/org/apache/maven/shared/release/phase I'm trying to use a less ancient version of plexus-container-default, it requires some test changes, I'll let you know what happens. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Releasing the release plugin
Further down the message, this boils down to a failure to find an ArtifactResolver. On Sat, Feb 22, 2014 at 12:04 PM, Benson Margulies bimargul...@gmail.com wrote: Plexus-container-default 1.5.5 changes some issues. This seems to make some things better. The first failure is: testNoSnapshotDependencies(org.apache.maven.shared.release.phase.CheckDependencySnapshotsPhaseTest) Time elapsed: 0.07 sec ERROR! org.codehaus.plexus.component.repository.exception.ComponentLookupException: Unable to lookup component 'org.apache.maven.project.MavenProjectBuilder', it could not be started. role: org.apache.maven.project.MavenProjectBuilder roleHint: default classRealm: plexus.core - realm =plexus.core strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy Number of foreign imports: 0 - at org.codehaus.plexus.component.collections.ComponentList.remove(ComponentList.java:91) And this happens over and over. I am checking if I can make it go away. the scm component error is gone, or at least hiding. On Sat, Feb 22, 2014 at 11:44 AM, Benson Margulies bimargul...@gmail.com wrote: On Sat, Feb 22, 2014 at 7:38 AM, Robert Scholte rfscho...@apache.org wrote: src/test/resources/org/apache/maven/shared/release/phase I'm trying to use a less ancient version of plexus-container-default, it requires some test changes, I'll let you know what happens. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Releasing the release plugin
You need to add maven-compat as a dependency. -- Regards, Igor On 2/22/2014, 12:27, Benson Margulies wrote: Further down the message, this boils down to a failure to find an ArtifactResolver. On Sat, Feb 22, 2014 at 12:04 PM, Benson Margulies bimargul...@gmail.com wrote: Plexus-container-default 1.5.5 changes some issues. This seems to make some things better. The first failure is: testNoSnapshotDependencies(org.apache.maven.shared.release.phase.CheckDependencySnapshotsPhaseTest) Time elapsed: 0.07 sec ERROR! org.codehaus.plexus.component.repository.exception.ComponentLookupException: Unable to lookup component 'org.apache.maven.project.MavenProjectBuilder', it could not be started. role: org.apache.maven.project.MavenProjectBuilder roleHint: default classRealm: plexus.core - realm =plexus.core strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy Number of foreign imports: 0 - at org.codehaus.plexus.component.collections.ComponentList.remove(ComponentList.java:91) And this happens over and over. I am checking if I can make it go away. the scm component error is gone, or at least hiding. On Sat, Feb 22, 2014 at 11:44 AM, Benson Margulies bimargul...@gmail.com wrote: On Sat, Feb 22, 2014 at 7:38 AM, Robert Scholte rfscho...@apache.org wrote: src/test/resources/org/apache/maven/shared/release/phase I'm trying to use a less ancient version of plexus-container-default, it requires some test changes, I'll let you know what happens. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Releasing the release plugin
I may have misled you, but I'll try it. Caused by: org.codehaus.plexus.component.repository.exception.ComponentLifecycleException: Error constructing component role: 'org.apache.maven.artifact.resolver.ArtifactResolver', implementation: 'org.apache.maven.artifact.resolver.DefaultArtifactResolver', role hint: 'default' at org.codehaus.plexus.component.builder.XBeanComponentBuilder.createComponentInstance(XBeanComponentBuilder.java:176) at org.codehaus.plexus.component.builder.XBeanComponentBuilder.build(XBeanComponentBuilder.java:123) at org.codehaus.plexus.component.manager.AbstractComponentManager.createComponentInstance(AbstractComponentManager.java:181) at org.codehaus.plexus.component.manager.SingletonComponentManager.getComponent(SingletonComponentManager.java:67) at org.codehaus.plexus.DefaultComponentRegistry.getComponent(DefaultComponentRegistry.java:358) ... 33 more Caused by: org.apache.xbean.recipe.ConstructionException: Unable to convert property value from org.codehaus.plexus.component.builder.XBeanComponentBuilder$RequirementRecipe to org.apache.maven.artifact.transform.ArtifactTransformationManager for injection private org.apache.maven.artifact.transform.ArtifactTransformationManager org.apache.maven.artifact.resolver.DefaultArtifactResolver.transformationManager at org.apache.xbean.recipe.ObjectRecipe.setProperty(ObjectRecipe.java:472) at org.apache.xbean.recipe.ObjectRecipe.setProperties(ObjectRecipe.java:367) at org.apache.xbean.recipe.ObjectRecipe.internalCreate(ObjectRecipe.java:282) at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:96) at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:61) at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:49) at org.codehaus.plexus.component.builder.XBeanComponentBuilder.createComponentInstance(XBeanComponentBuilder.java:159) ... 37 more Caused by: java.lang.UnsupportedOperationException: You cannot modify this list. This list is a requirement of role: 'org.apache.maven.artifact.transform.ArtifactTransformationManager', implementation: 'org.apache.maven.artifact.transform.DefaultArtifactTransformationManager', role hint: 'default' and managed by the container. at org.codehaus.plexus.component.collections.ComponentList.remove(ComponentList.java:91) at org.apache.maven.artifact.transform.DefaultArtifactTransformationManager.initialize(DefaultArtifactTransformationManager.java:44) at org.codehaus.plexus.personality.plexus.lifecycle.phase.InitializePhase.execute(InitializePhase.java:33) at org.codehaus.plexus.lifecycle.AbstractLifecycleHandler.start(AbstractLifecycleHandler.java:97) at org.codehaus.plexus.component.manager.AbstractComponentManager.start(AbstractComponentManager.java:167) at org.codehaus.plexus.component.builder.XBeanComponentBuilder.startComponentLifecycle(XBeanComponentBuilder.java:283) at org.codehaus.plexus.component.builder.XBeanComponentBuilder.build(XBeanComponentBuilder.java:129) at org.codehaus.plexus.component.manager.AbstractComponentManager.createComponentInstance(AbstractComponentManager.java:181) at org.codehaus.plexus.component.manager.SingletonComponentManager.getComponent(SingletonComponentManager.java:67) at org.codehaus.plexus.DefaultComponentRegistry.getComponent(DefaultComponentRegistry.java:358) at org.codehaus.plexus.DefaultComponentRegistry.lookup(DefaultComponentRegistry.java:178) at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:393) at org.codehaus.plexus.component.builder.XBeanComponentBuilder$RequirementRecipe.internalCreate(XBeanComponentBuilder.java:402) at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:96) at org.apache.xbean.recipe.RecipeHelper.convert(RecipeHelper.java:167) at org.apache.xbean.recipe.ObjectRecipe.setProperty(ObjectRecipe.java:466) ... 43 more On Sat, Feb 22, 2014 at 12:29 PM, Igor Fedorenko i...@ifedorenko.com wrote: You need to add maven-compat as a dependency. -- Regards, Igor On 2/22/2014, 12:27, Benson Margulies wrote: Further down the message, this boils down to a failure to find an ArtifactResolver. On Sat, Feb 22, 2014 at 12:04 PM, Benson Margulies bimargul...@gmail.com wrote: Plexus-container-default 1.5.5 changes some issues. This seems to make some things better. The first failure is: testNoSnapshotDependencies(org.apache.maven.shared.release.phase.CheckDependencySnapshotsPhaseTest) Time elapsed: 0.07 sec ERROR! org.codehaus.plexus.component.repository.exception.ComponentLookupException: Unable to lookup component 'org.apache.maven.project.MavenProjectBuilder', it could not be started. role: org.apache.maven.project.MavenProjectBuilder roleHint: default classRealm: plexus.core - realm =plexus.core strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy Number of foreign imports: 0 -
Re: Releasing the release plugin
I'm sorry, I did mislead you. Not surprisingly, adding maven-compat did not fix the problem with the apparently unmodifiable list. On Sat, Feb 22, 2014 at 12:33 PM, Benson Margulies bimargul...@gmail.com wrote: I may have misled you, but I'll try it. Caused by: org.codehaus.plexus.component.repository.exception.ComponentLifecycleException: Error constructing component role: 'org.apache.maven.artifact.resolver.ArtifactResolver', implementation: 'org.apache.maven.artifact.resolver.DefaultArtifactResolver', role hint: 'default' at org.codehaus.plexus.component.builder.XBeanComponentBuilder.createComponentInstance(XBeanComponentBuilder.java:176) at org.codehaus.plexus.component.builder.XBeanComponentBuilder.build(XBeanComponentBuilder.java:123) at org.codehaus.plexus.component.manager.AbstractComponentManager.createComponentInstance(AbstractComponentManager.java:181) at org.codehaus.plexus.component.manager.SingletonComponentManager.getComponent(SingletonComponentManager.java:67) at org.codehaus.plexus.DefaultComponentRegistry.getComponent(DefaultComponentRegistry.java:358) ... 33 more Caused by: org.apache.xbean.recipe.ConstructionException: Unable to convert property value from org.codehaus.plexus.component.builder.XBeanComponentBuilder$RequirementRecipe to org.apache.maven.artifact.transform.ArtifactTransformationManager for injection private org.apache.maven.artifact.transform.ArtifactTransformationManager org.apache.maven.artifact.resolver.DefaultArtifactResolver.transformationManager at org.apache.xbean.recipe.ObjectRecipe.setProperty(ObjectRecipe.java:472) at org.apache.xbean.recipe.ObjectRecipe.setProperties(ObjectRecipe.java:367) at org.apache.xbean.recipe.ObjectRecipe.internalCreate(ObjectRecipe.java:282) at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:96) at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:61) at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:49) at org.codehaus.plexus.component.builder.XBeanComponentBuilder.createComponentInstance(XBeanComponentBuilder.java:159) ... 37 more Caused by: java.lang.UnsupportedOperationException: You cannot modify this list. This list is a requirement of role: 'org.apache.maven.artifact.transform.ArtifactTransformationManager', implementation: 'org.apache.maven.artifact.transform.DefaultArtifactTransformationManager', role hint: 'default' and managed by the container. at org.codehaus.plexus.component.collections.ComponentList.remove(ComponentList.java:91) at org.apache.maven.artifact.transform.DefaultArtifactTransformationManager.initialize(DefaultArtifactTransformationManager.java:44) at org.codehaus.plexus.personality.plexus.lifecycle.phase.InitializePhase.execute(InitializePhase.java:33) at org.codehaus.plexus.lifecycle.AbstractLifecycleHandler.start(AbstractLifecycleHandler.java:97) at org.codehaus.plexus.component.manager.AbstractComponentManager.start(AbstractComponentManager.java:167) at org.codehaus.plexus.component.builder.XBeanComponentBuilder.startComponentLifecycle(XBeanComponentBuilder.java:283) at org.codehaus.plexus.component.builder.XBeanComponentBuilder.build(XBeanComponentBuilder.java:129) at org.codehaus.plexus.component.manager.AbstractComponentManager.createComponentInstance(AbstractComponentManager.java:181) at org.codehaus.plexus.component.manager.SingletonComponentManager.getComponent(SingletonComponentManager.java:67) at org.codehaus.plexus.DefaultComponentRegistry.getComponent(DefaultComponentRegistry.java:358) at org.codehaus.plexus.DefaultComponentRegistry.lookup(DefaultComponentRegistry.java:178) at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:393) at org.codehaus.plexus.component.builder.XBeanComponentBuilder$RequirementRecipe.internalCreate(XBeanComponentBuilder.java:402) at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:96) at org.apache.xbean.recipe.RecipeHelper.convert(RecipeHelper.java:167) at org.apache.xbean.recipe.ObjectRecipe.setProperty(ObjectRecipe.java:466) ... 43 more On Sat, Feb 22, 2014 at 12:29 PM, Igor Fedorenko i...@ifedorenko.com wrote: You need to add maven-compat as a dependency. -- Regards, Igor On 2/22/2014, 12:27, Benson Margulies wrote: Further down the message, this boils down to a failure to find an ArtifactResolver. On Sat, Feb 22, 2014 at 12:04 PM, Benson Margulies bimargul...@gmail.com wrote: Plexus-container-default 1.5.5 changes some issues. This seems to make some things better. The first failure is: testNoSnapshotDependencies(org.apache.maven.shared.release.phase.CheckDependencySnapshotsPhaseTest) Time elapsed: 0.07 sec ERROR! org.codehaus.plexus.component.repository.exception.ComponentLookupException: Unable to lookup component 'org.apache.maven.project.MavenProjectBuilder', it could not be started. role: org.apache.maven.project.MavenProjectBuilder
Re: Releasing the release plugin
What version of Maven does release plugin depend on? I think DefaultArtifactTransformationManager.initialize was removed in 3.x, at least it's not present in 3.2.1 and 3.1.1. -- Regards, Igor On 2/22/2014, 12:35, Benson Margulies wrote: I'm sorry, I did mislead you. Not surprisingly, adding maven-compat did not fix the problem with the apparently unmodifiable list. On Sat, Feb 22, 2014 at 12:33 PM, Benson Margulies bimargul...@gmail.com wrote: I may have misled you, but I'll try it. Caused by: org.codehaus.plexus.component.repository.exception.ComponentLifecycleException: Error constructing component role: 'org.apache.maven.artifact.resolver.ArtifactResolver', implementation: 'org.apache.maven.artifact.resolver.DefaultArtifactResolver', role hint: 'default' at org.codehaus.plexus.component.builder.XBeanComponentBuilder.createComponentInstance(XBeanComponentBuilder.java:176) at org.codehaus.plexus.component.builder.XBeanComponentBuilder.build(XBeanComponentBuilder.java:123) at org.codehaus.plexus.component.manager.AbstractComponentManager.createComponentInstance(AbstractComponentManager.java:181) at org.codehaus.plexus.component.manager.SingletonComponentManager.getComponent(SingletonComponentManager.java:67) at org.codehaus.plexus.DefaultComponentRegistry.getComponent(DefaultComponentRegistry.java:358) ... 33 more Caused by: org.apache.xbean.recipe.ConstructionException: Unable to convert property value from org.codehaus.plexus.component.builder.XBeanComponentBuilder$RequirementRecipe to org.apache.maven.artifact.transform.ArtifactTransformationManager for injection private org.apache.maven.artifact.transform.ArtifactTransformationManager org.apache.maven.artifact.resolver.DefaultArtifactResolver.transformationManager at org.apache.xbean.recipe.ObjectRecipe.setProperty(ObjectRecipe.java:472) at org.apache.xbean.recipe.ObjectRecipe.setProperties(ObjectRecipe.java:367) at org.apache.xbean.recipe.ObjectRecipe.internalCreate(ObjectRecipe.java:282) at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:96) at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:61) at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:49) at org.codehaus.plexus.component.builder.XBeanComponentBuilder.createComponentInstance(XBeanComponentBuilder.java:159) ... 37 more Caused by: java.lang.UnsupportedOperationException: You cannot modify this list. This list is a requirement of role: 'org.apache.maven.artifact.transform.ArtifactTransformationManager', implementation: 'org.apache.maven.artifact.transform.DefaultArtifactTransformationManager', role hint: 'default' and managed by the container. at org.codehaus.plexus.component.collections.ComponentList.remove(ComponentList.java:91) at org.apache.maven.artifact.transform.DefaultArtifactTransformationManager.initialize(DefaultArtifactTransformationManager.java:44) at org.codehaus.plexus.personality.plexus.lifecycle.phase.InitializePhase.execute(InitializePhase.java:33) at org.codehaus.plexus.lifecycle.AbstractLifecycleHandler.start(AbstractLifecycleHandler.java:97) at org.codehaus.plexus.component.manager.AbstractComponentManager.start(AbstractComponentManager.java:167) at org.codehaus.plexus.component.builder.XBeanComponentBuilder.startComponentLifecycle(XBeanComponentBuilder.java:283) at org.codehaus.plexus.component.builder.XBeanComponentBuilder.build(XBeanComponentBuilder.java:129) at org.codehaus.plexus.component.manager.AbstractComponentManager.createComponentInstance(AbstractComponentManager.java:181) at org.codehaus.plexus.component.manager.SingletonComponentManager.getComponent(SingletonComponentManager.java:67) at org.codehaus.plexus.DefaultComponentRegistry.getComponent(DefaultComponentRegistry.java:358) at org.codehaus.plexus.DefaultComponentRegistry.lookup(DefaultComponentRegistry.java:178) at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:393) at org.codehaus.plexus.component.builder.XBeanComponentBuilder$RequirementRecipe.internalCreate(XBeanComponentBuilder.java:402) at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:96) at org.apache.xbean.recipe.RecipeHelper.convert(RecipeHelper.java:167) at org.apache.xbean.recipe.ObjectRecipe.setProperty(ObjectRecipe.java:466) ... 43 more On Sat, Feb 22, 2014 at 12:29 PM, Igor Fedorenko i...@ifedorenko.com wrote: You need to add maven-compat as a dependency. -- Regards, Igor On 2/22/2014, 12:27, Benson Margulies wrote: Further down the message, this boils down to a failure to find an ArtifactResolver. On Sat, Feb 22, 2014 at 12:04 PM, Benson Margulies bimargul...@gmail.com wrote: Plexus-container-default 1.5.5 changes some issues. This seems to make some things better. The first failure is: testNoSnapshotDependencies(org.apache.maven.shared.release.phase.CheckDependencySnapshotsPhaseTest) Time elapsed: 0.07 sec ERROR! org.codehaus.plexus.component.repository.exception.ComponentLookupException:
Re: Releasing the release plugin
Still 2.2.1. So, in version 2.2.1, org.apache.maven.artifact.transform.DefaultArtifactTransformationManager tries to patch a list that is injected, and gets into trouble because Plexus has made the list unmodifiable. Presumably, that unmodifiability was some improvement to plexus. I guess that taking 1.5.5 of the container doesn't work with 2.2.1, and the question is how far back one needs to go (give or take making a new release of maven-artifact-manager). Or even if any of this is the solution to Robert's original problem. On Sat, Feb 22, 2014 at 12:46 PM, Igor Fedorenko i...@ifedorenko.com wrote: What version of Maven does release plugin depend on? I think DefaultArtifactTransformationManager.initialize was removed in 3.x, at least it's not present in 3.2.1 and 3.1.1. -- Regards, Igor On 2/22/2014, 12:35, Benson Margulies wrote: I'm sorry, I did mislead you. Not surprisingly, adding maven-compat did not fix the problem with the apparently unmodifiable list. On Sat, Feb 22, 2014 at 12:33 PM, Benson Margulies bimargul...@gmail.com wrote: I may have misled you, but I'll try it. Caused by: org.codehaus.plexus.component.repository.exception.ComponentLifecycleException: Error constructing component role: 'org.apache.maven.artifact.resolver.ArtifactResolver', implementation: 'org.apache.maven.artifact.resolver.DefaultArtifactResolver', role hint: 'default' at org.codehaus.plexus.component.builder.XBeanComponentBuilder.createComponentInstance(XBeanComponentBuilder.java:176) at org.codehaus.plexus.component.builder.XBeanComponentBuilder.build(XBeanComponentBuilder.java:123) at org.codehaus.plexus.component.manager.AbstractComponentManager.createComponentInstance(AbstractComponentManager.java:181) at org.codehaus.plexus.component.manager.SingletonComponentManager.getComponent(SingletonComponentManager.java:67) at org.codehaus.plexus.DefaultComponentRegistry.getComponent(DefaultComponentRegistry.java:358) ... 33 more Caused by: org.apache.xbean.recipe.ConstructionException: Unable to convert property value from org.codehaus.plexus.component.builder.XBeanComponentBuilder$RequirementRecipe to org.apache.maven.artifact.transform.ArtifactTransformationManager for injection private org.apache.maven.artifact.transform.ArtifactTransformationManager org.apache.maven.artifact.resolver.DefaultArtifactResolver.transformationManager at org.apache.xbean.recipe.ObjectRecipe.setProperty(ObjectRecipe.java:472) at org.apache.xbean.recipe.ObjectRecipe.setProperties(ObjectRecipe.java:367) at org.apache.xbean.recipe.ObjectRecipe.internalCreate(ObjectRecipe.java:282) at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:96) at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:61) at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:49) at org.codehaus.plexus.component.builder.XBeanComponentBuilder.createComponentInstance(XBeanComponentBuilder.java:159) ... 37 more Caused by: java.lang.UnsupportedOperationException: You cannot modify this list. This list is a requirement of role: 'org.apache.maven.artifact.transform.ArtifactTransformationManager', implementation: 'org.apache.maven.artifact.transform.DefaultArtifactTransformationManager', role hint: 'default' and managed by the container. at org.codehaus.plexus.component.collections.ComponentList.remove(ComponentList.java:91) at org.apache.maven.artifact.transform.DefaultArtifactTransformationManager.initialize(DefaultArtifactTransformationManager.java:44) at org.codehaus.plexus.personality.plexus.lifecycle.phase.InitializePhase.execute(InitializePhase.java:33) at org.codehaus.plexus.lifecycle.AbstractLifecycleHandler.start(AbstractLifecycleHandler.java:97) at org.codehaus.plexus.component.manager.AbstractComponentManager.start(AbstractComponentManager.java:167) at org.codehaus.plexus.component.builder.XBeanComponentBuilder.startComponentLifecycle(XBeanComponentBuilder.java:283) at org.codehaus.plexus.component.builder.XBeanComponentBuilder.build(XBeanComponentBuilder.java:129) at org.codehaus.plexus.component.manager.AbstractComponentManager.createComponentInstance(AbstractComponentManager.java:181) at org.codehaus.plexus.component.manager.SingletonComponentManager.getComponent(SingletonComponentManager.java:67) at org.codehaus.plexus.DefaultComponentRegistry.getComponent(DefaultComponentRegistry.java:358) at org.codehaus.plexus.DefaultComponentRegistry.lookup(DefaultComponentRegistry.java:178) at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:393) at org.codehaus.plexus.component.builder.XBeanComponentBuilder$RequirementRecipe.internalCreate(XBeanComponentBuilder.java:402) at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:96) at org.apache.xbean.recipe.RecipeHelper.convert(RecipeHelper.java:167) at org.apache.xbean.recipe.ObjectRecipe.setProperty(ObjectRecipe.java:466) ... 43 more On Sat,
Re: Site plugin
That version of the site plugin we have configured just doesn't work with newer versions of Maven. I ran the command with Maven 3.0.4 and it works. We are a long, long, long way from push button releases. On Feb 22, 2014, at 1:54 AM, Dennis Lundberg denn...@apache.org wrote: Hi Jason, Looking at the stack trace it seems to be the remote resources plugin that is throwing an NPE. Didn't you release 1.5 of that plugin because of issues with core? Your build is using 1.4... -- Dennis Lundberg Den 22 feb 2014 05:30 skrev Jason van Zyl ja...@takari.io: Not sure who looks after the site plugin these days but I can't run the staging part to copy it over to the production site: In the release checkout I ran: mvn -Preporting site site:stage and got: https://gist.github.com/jvanzyl/9148731 I'll continue on with the rest of the work but I will release tomorrow regardless. I don't have time to debug the site plugin. Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl http://twitter.com/takari_io - Simplex sigillum veri. (Simplicity is the seal of truth.) Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl http://twitter.com/takari_io - We know what we are, but know not what we may be. -- Shakespeare
Re: Releasing the release plugin
http://svn.apache.org/r1570870 fixes the unittests on my machine. I'll have to check was has changed between SCM 1.8 and 1.8.1, but there's a serious issue here. Robert Op Sat, 22 Feb 2014 18:48:53 +0100 schreef Benson Margulies bimargul...@gmail.com: Still 2.2.1. So, in version 2.2.1, org.apache.maven.artifact.transform.DefaultArtifactTransformationManager tries to patch a list that is injected, and gets into trouble because Plexus has made the list unmodifiable. Presumably, that unmodifiability was some improvement to plexus. I guess that taking 1.5.5 of the container doesn't work with 2.2.1, and the question is how far back one needs to go (give or take making a new release of maven-artifact-manager). Or even if any of this is the solution to Robert's original problem. On Sat, Feb 22, 2014 at 12:46 PM, Igor Fedorenko i...@ifedorenko.com wrote: What version of Maven does release plugin depend on? I think DefaultArtifactTransformationManager.initialize was removed in 3.x, at least it's not present in 3.2.1 and 3.1.1. -- Regards, Igor On 2/22/2014, 12:35, Benson Margulies wrote: I'm sorry, I did mislead you. Not surprisingly, adding maven-compat did not fix the problem with the apparently unmodifiable list. On Sat, Feb 22, 2014 at 12:33 PM, Benson Margulies bimargul...@gmail.com wrote: I may have misled you, but I'll try it. Caused by: org.codehaus.plexus.component.repository.exception.ComponentLifecycleException: Error constructing component role: 'org.apache.maven.artifact.resolver.ArtifactResolver', implementation: 'org.apache.maven.artifact.resolver.DefaultArtifactResolver', role hint: 'default' at org.codehaus.plexus.component.builder.XBeanComponentBuilder.createComponentInstance(XBeanComponentBuilder.java:176) at org.codehaus.plexus.component.builder.XBeanComponentBuilder.build(XBeanComponentBuilder.java:123) at org.codehaus.plexus.component.manager.AbstractComponentManager.createComponentInstance(AbstractComponentManager.java:181) at org.codehaus.plexus.component.manager.SingletonComponentManager.getComponent(SingletonComponentManager.java:67) at org.codehaus.plexus.DefaultComponentRegistry.getComponent(DefaultComponentRegistry.java:358) ... 33 more Caused by: org.apache.xbean.recipe.ConstructionException: Unable to convert property value from org.codehaus.plexus.component.builder.XBeanComponentBuilder$RequirementRecipe to org.apache.maven.artifact.transform.ArtifactTransformationManager for injection private org.apache.maven.artifact.transform.ArtifactTransformationManager org.apache.maven.artifact.resolver.DefaultArtifactResolver.transformationManager at org.apache.xbean.recipe.ObjectRecipe.setProperty(ObjectRecipe.java:472) at org.apache.xbean.recipe.ObjectRecipe.setProperties(ObjectRecipe.java:367) at org.apache.xbean.recipe.ObjectRecipe.internalCreate(ObjectRecipe.java:282) at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:96) at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:61) at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:49) at org.codehaus.plexus.component.builder.XBeanComponentBuilder.createComponentInstance(XBeanComponentBuilder.java:159) ... 37 more Caused by: java.lang.UnsupportedOperationException: You cannot modify this list. This list is a requirement of role: 'org.apache.maven.artifact.transform.ArtifactTransformationManager', implementation: 'org.apache.maven.artifact.transform.DefaultArtifactTransformationManager', role hint: 'default' and managed by the container. at org.codehaus.plexus.component.collections.ComponentList.remove(ComponentList.java:91) at org.apache.maven.artifact.transform.DefaultArtifactTransformationManager.initialize(DefaultArtifactTransformationManager.java:44) at org.codehaus.plexus.personality.plexus.lifecycle.phase.InitializePhase.execute(InitializePhase.java:33) at org.codehaus.plexus.lifecycle.AbstractLifecycleHandler.start(AbstractLifecycleHandler.java:97) at org.codehaus.plexus.component.manager.AbstractComponentManager.start(AbstractComponentManager.java:167) at org.codehaus.plexus.component.builder.XBeanComponentBuilder.startComponentLifecycle(XBeanComponentBuilder.java:283) at org.codehaus.plexus.component.builder.XBeanComponentBuilder.build(XBeanComponentBuilder.java:129) at org.codehaus.plexus.component.manager.AbstractComponentManager.createComponentInstance(AbstractComponentManager.java:181) at org.codehaus.plexus.component.manager.SingletonComponentManager.getComponent(SingletonComponentManager.java:67) at org.codehaus.plexus.DefaultComponentRegistry.getComponent(DefaultComponentRegistry.java:358) at org.codehaus.plexus.DefaultComponentRegistry.lookup(DefaultComponentRegistry.java:178) at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:393) at org.codehaus.plexus.component.builder.XBeanComponentBuilder$RequirementRecipe.internalCreate(XBeanComponentBuilder.java:402) at
Re: Releasing the release plugin
https://jira.codehaus.org/browse/SCM-698 seems to be the cause Op Sat, 22 Feb 2014 19:10:06 +0100 schreef Robert Scholte rfscho...@apache.org: http://svn.apache.org/r1570870 fixes the unittests on my machine. I'll have to check was has changed between SCM 1.8 and 1.8.1, but there's a serious issue here. Robert Op Sat, 22 Feb 2014 18:48:53 +0100 schreef Benson Margulies bimargul...@gmail.com: Still 2.2.1. So, in version 2.2.1, org.apache.maven.artifact.transform.DefaultArtifactTransformationManager tries to patch a list that is injected, and gets into trouble because Plexus has made the list unmodifiable. Presumably, that unmodifiability was some improvement to plexus. I guess that taking 1.5.5 of the container doesn't work with 2.2.1, and the question is how far back one needs to go (give or take making a new release of maven-artifact-manager). Or even if any of this is the solution to Robert's original problem. On Sat, Feb 22, 2014 at 12:46 PM, Igor Fedorenko i...@ifedorenko.com wrote: What version of Maven does release plugin depend on? I think DefaultArtifactTransformationManager.initialize was removed in 3.x, at least it's not present in 3.2.1 and 3.1.1. -- Regards, Igor On 2/22/2014, 12:35, Benson Margulies wrote: I'm sorry, I did mislead you. Not surprisingly, adding maven-compat did not fix the problem with the apparently unmodifiable list. On Sat, Feb 22, 2014 at 12:33 PM, Benson Margulies bimargul...@gmail.com wrote: I may have misled you, but I'll try it. Caused by: org.codehaus.plexus.component.repository.exception.ComponentLifecycleException: Error constructing component role: 'org.apache.maven.artifact.resolver.ArtifactResolver', implementation: 'org.apache.maven.artifact.resolver.DefaultArtifactResolver', role hint: 'default' at org.codehaus.plexus.component.builder.XBeanComponentBuilder.createComponentInstance(XBeanComponentBuilder.java:176) at org.codehaus.plexus.component.builder.XBeanComponentBuilder.build(XBeanComponentBuilder.java:123) at org.codehaus.plexus.component.manager.AbstractComponentManager.createComponentInstance(AbstractComponentManager.java:181) at org.codehaus.plexus.component.manager.SingletonComponentManager.getComponent(SingletonComponentManager.java:67) at org.codehaus.plexus.DefaultComponentRegistry.getComponent(DefaultComponentRegistry.java:358) ... 33 more Caused by: org.apache.xbean.recipe.ConstructionException: Unable to convert property value from org.codehaus.plexus.component.builder.XBeanComponentBuilder$RequirementRecipe to org.apache.maven.artifact.transform.ArtifactTransformationManager for injection private org.apache.maven.artifact.transform.ArtifactTransformationManager org.apache.maven.artifact.resolver.DefaultArtifactResolver.transformationManager at org.apache.xbean.recipe.ObjectRecipe.setProperty(ObjectRecipe.java:472) at org.apache.xbean.recipe.ObjectRecipe.setProperties(ObjectRecipe.java:367) at org.apache.xbean.recipe.ObjectRecipe.internalCreate(ObjectRecipe.java:282) at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:96) at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:61) at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:49) at org.codehaus.plexus.component.builder.XBeanComponentBuilder.createComponentInstance(XBeanComponentBuilder.java:159) ... 37 more Caused by: java.lang.UnsupportedOperationException: You cannot modify this list. This list is a requirement of role: 'org.apache.maven.artifact.transform.ArtifactTransformationManager', implementation: 'org.apache.maven.artifact.transform.DefaultArtifactTransformationManager', role hint: 'default' and managed by the container. at org.codehaus.plexus.component.collections.ComponentList.remove(ComponentList.java:91) at org.apache.maven.artifact.transform.DefaultArtifactTransformationManager.initialize(DefaultArtifactTransformationManager.java:44) at org.codehaus.plexus.personality.plexus.lifecycle.phase.InitializePhase.execute(InitializePhase.java:33) at org.codehaus.plexus.lifecycle.AbstractLifecycleHandler.start(AbstractLifecycleHandler.java:97) at org.codehaus.plexus.component.manager.AbstractComponentManager.start(AbstractComponentManager.java:167) at org.codehaus.plexus.component.builder.XBeanComponentBuilder.startComponentLifecycle(XBeanComponentBuilder.java:283) at org.codehaus.plexus.component.builder.XBeanComponentBuilder.build(XBeanComponentBuilder.java:129) at org.codehaus.plexus.component.manager.AbstractComponentManager.createComponentInstance(AbstractComponentManager.java:181) at org.codehaus.plexus.component.manager.SingletonComponentManager.getComponent(SingletonComponentManager.java:67) at org.codehaus.plexus.DefaultComponentRegistry.getComponent(DefaultComponentRegistry.java:358) at org.codehaus.plexus.DefaultComponentRegistry.lookup(DefaultComponentRegistry.java:178) at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:393) at
Re: Releasing the release plugin
This, of course, does not help the people pining for the git support in 1.9. On Sat, Feb 22, 2014 at 1:10 PM, Robert Scholte rfscho...@apache.org wrote: http://svn.apache.org/r1570870 fixes the unittests on my machine. I'll have to check was has changed between SCM 1.8 and 1.8.1, but there's a serious issue here. Robert Op Sat, 22 Feb 2014 18:48:53 +0100 schreef Benson Margulies bimargul...@gmail.com: Still 2.2.1. So, in version 2.2.1, org.apache.maven.artifact.transform.DefaultArtifactTransformationManager tries to patch a list that is injected, and gets into trouble because Plexus has made the list unmodifiable. Presumably, that unmodifiability was some improvement to plexus. I guess that taking 1.5.5 of the container doesn't work with 2.2.1, and the question is how far back one needs to go (give or take making a new release of maven-artifact-manager). Or even if any of this is the solution to Robert's original problem. On Sat, Feb 22, 2014 at 12:46 PM, Igor Fedorenko i...@ifedorenko.com wrote: What version of Maven does release plugin depend on? I think DefaultArtifactTransformationManager.initialize was removed in 3.x, at least it's not present in 3.2.1 and 3.1.1. -- Regards, Igor On 2/22/2014, 12:35, Benson Margulies wrote: I'm sorry, I did mislead you. Not surprisingly, adding maven-compat did not fix the problem with the apparently unmodifiable list. On Sat, Feb 22, 2014 at 12:33 PM, Benson Margulies bimargul...@gmail.com wrote: I may have misled you, but I'll try it. Caused by: org.codehaus.plexus.component.repository.exception.ComponentLifecycleException: Error constructing component role: 'org.apache.maven.artifact.resolver.ArtifactResolver', implementation: 'org.apache.maven.artifact.resolver.DefaultArtifactResolver', role hint: 'default' at org.codehaus.plexus.component.builder.XBeanComponentBuilder.createComponentInstance(XBeanComponentBuilder.java:176) at org.codehaus.plexus.component.builder.XBeanComponentBuilder.build(XBeanComponentBuilder.java:123) at org.codehaus.plexus.component.manager.AbstractComponentManager.createComponentInstance(AbstractComponentManager.java:181) at org.codehaus.plexus.component.manager.SingletonComponentManager.getComponent(SingletonComponentManager.java:67) at org.codehaus.plexus.DefaultComponentRegistry.getComponent(DefaultComponentRegistry.java:358) ... 33 more Caused by: org.apache.xbean.recipe.ConstructionException: Unable to convert property value from org.codehaus.plexus.component.builder.XBeanComponentBuilder$RequirementRecipe to org.apache.maven.artifact.transform.ArtifactTransformationManager for injection private org.apache.maven.artifact.transform.ArtifactTransformationManager org.apache.maven.artifact.resolver.DefaultArtifactResolver.transformationManager at org.apache.xbean.recipe.ObjectRecipe.setProperty(ObjectRecipe.java:472) at org.apache.xbean.recipe.ObjectRecipe.setProperties(ObjectRecipe.java:367) at org.apache.xbean.recipe.ObjectRecipe.internalCreate(ObjectRecipe.java:282) at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:96) at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:61) at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:49) at org.codehaus.plexus.component.builder.XBeanComponentBuilder.createComponentInstance(XBeanComponentBuilder.java:159) ... 37 more Caused by: java.lang.UnsupportedOperationException: You cannot modify this list. This list is a requirement of role: 'org.apache.maven.artifact.transform.ArtifactTransformationManager', implementation: 'org.apache.maven.artifact.transform.DefaultArtifactTransformationManager', role hint: 'default' and managed by the container. at org.codehaus.plexus.component.collections.ComponentList.remove(ComponentList.java:91) at org.apache.maven.artifact.transform.DefaultArtifactTransformationManager.initialize(DefaultArtifactTransformationManager.java:44) at org.codehaus.plexus.personality.plexus.lifecycle.phase.InitializePhase.execute(InitializePhase.java:33) at org.codehaus.plexus.lifecycle.AbstractLifecycleHandler.start(AbstractLifecycleHandler.java:97) at org.codehaus.plexus.component.manager.AbstractComponentManager.start(AbstractComponentManager.java:167) at org.codehaus.plexus.component.builder.XBeanComponentBuilder.startComponentLifecycle(XBeanComponentBuilder.java:283) at org.codehaus.plexus.component.builder.XBeanComponentBuilder.build(XBeanComponentBuilder.java:129) at org.codehaus.plexus.component.manager.AbstractComponentManager.createComponentInstance(AbstractComponentManager.java:181) at org.codehaus.plexus.component.manager.SingletonComponentManager.getComponent(SingletonComponentManager.java:67) at org.codehaus.plexus.DefaultComponentRegistry.getComponent(DefaultComponentRegistry.java:358) at org.codehaus.plexus.DefaultComponentRegistry.lookup(DefaultComponentRegistry.java:178) at
Re: Releasing the release plugin
I've only changed maven-scm-manager-plexus to 1.8, and kept the rest on 1.9, such as the maven-scm-providers-standard. This brings me to the next question: Are you convinced that 1.9 will solve all the problems of the GIT users? I'm not, and I wouldn't prepare a git special-release without knowing it'll take away the GIT critical issues. I've tried to get feedback after some fixes, but didn't get the feedback I was searching for. Robert Op Sat, 22 Feb 2014 19:12:05 +0100 schreef Benson Margulies bimargul...@gmail.com: This, of course, does not help the people pining for the git support in 1.9. On Sat, Feb 22, 2014 at 1:10 PM, Robert Scholte rfscho...@apache.org wrote: http://svn.apache.org/r1570870 fixes the unittests on my machine. I'll have to check was has changed between SCM 1.8 and 1.8.1, but there's a serious issue here. Robert Op Sat, 22 Feb 2014 18:48:53 +0100 schreef Benson Margulies bimargul...@gmail.com: Still 2.2.1. So, in version 2.2.1, org.apache.maven.artifact.transform.DefaultArtifactTransformationManager tries to patch a list that is injected, and gets into trouble because Plexus has made the list unmodifiable. Presumably, that unmodifiability was some improvement to plexus. I guess that taking 1.5.5 of the container doesn't work with 2.2.1, and the question is how far back one needs to go (give or take making a new release of maven-artifact-manager). Or even if any of this is the solution to Robert's original problem. On Sat, Feb 22, 2014 at 12:46 PM, Igor Fedorenko i...@ifedorenko.com wrote: What version of Maven does release plugin depend on? I think DefaultArtifactTransformationManager.initialize was removed in 3.x, at least it's not present in 3.2.1 and 3.1.1. -- Regards, Igor On 2/22/2014, 12:35, Benson Margulies wrote: I'm sorry, I did mislead you. Not surprisingly, adding maven-compat did not fix the problem with the apparently unmodifiable list. On Sat, Feb 22, 2014 at 12:33 PM, Benson Margulies bimargul...@gmail.com wrote: I may have misled you, but I'll try it. Caused by: org.codehaus.plexus.component.repository.exception.ComponentLifecycleException: Error constructing component role: 'org.apache.maven.artifact.resolver.ArtifactResolver', implementation: 'org.apache.maven.artifact.resolver.DefaultArtifactResolver', role hint: 'default' at org.codehaus.plexus.component.builder.XBeanComponentBuilder.createComponentInstance(XBeanComponentBuilder.java:176) at org.codehaus.plexus.component.builder.XBeanComponentBuilder.build(XBeanComponentBuilder.java:123) at org.codehaus.plexus.component.manager.AbstractComponentManager.createComponentInstance(AbstractComponentManager.java:181) at org.codehaus.plexus.component.manager.SingletonComponentManager.getComponent(SingletonComponentManager.java:67) at org.codehaus.plexus.DefaultComponentRegistry.getComponent(DefaultComponentRegistry.java:358) ... 33 more Caused by: org.apache.xbean.recipe.ConstructionException: Unable to convert property value from org.codehaus.plexus.component.builder.XBeanComponentBuilder$RequirementRecipe to org.apache.maven.artifact.transform.ArtifactTransformationManager for injection private org.apache.maven.artifact.transform.ArtifactTransformationManager org.apache.maven.artifact.resolver.DefaultArtifactResolver.transformationManager at org.apache.xbean.recipe.ObjectRecipe.setProperty(ObjectRecipe.java:472) at org.apache.xbean.recipe.ObjectRecipe.setProperties(ObjectRecipe.java:367) at org.apache.xbean.recipe.ObjectRecipe.internalCreate(ObjectRecipe.java:282) at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:96) at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:61) at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:49) at org.codehaus.plexus.component.builder.XBeanComponentBuilder.createComponentInstance(XBeanComponentBuilder.java:159) ... 37 more Caused by: java.lang.UnsupportedOperationException: You cannot modify this list. This list is a requirement of role: 'org.apache.maven.artifact.transform.ArtifactTransformationManager', implementation: 'org.apache.maven.artifact.transform.DefaultArtifactTransformationManager', role hint: 'default' and managed by the container. at org.codehaus.plexus.component.collections.ComponentList.remove(ComponentList.java:91) at org.apache.maven.artifact.transform.DefaultArtifactTransformationManager.initialize(DefaultArtifactTransformationManager.java:44) at org.codehaus.plexus.personality.plexus.lifecycle.phase.InitializePhase.execute(InitializePhase.java:33) at org.codehaus.plexus.lifecycle.AbstractLifecycleHandler.start(AbstractLifecycleHandler.java:97) at org.codehaus.plexus.component.manager.AbstractComponentManager.start(AbstractComponentManager.java:167) at org.codehaus.plexus.component.builder.XBeanComponentBuilder.startComponentLifecycle(XBeanComponentBuilder.java:283) at
Re: Releasing the release plugin
On Sat, Feb 22, 2014 at 1:23 PM, Robert Scholte rfscho...@apache.org wrote: I've only changed maven-scm-manager-plexus to 1.8, and kept the rest on 1.9, such as the maven-scm-providers-standard. This brings me to the next question: Are you convinced that 1.9 will solve all the problems of the GIT users? I'm not, and I wouldn't prepare a git special-release without knowing it'll take away the GIT critical issues. I've tried to get feedback after some fixes, but didn't get the feedback I was searching for. Not I, I'm just reflecting the claims of others. Robert Op Sat, 22 Feb 2014 19:12:05 +0100 schreef Benson Margulies bimargul...@gmail.com: This, of course, does not help the people pining for the git support in 1.9. On Sat, Feb 22, 2014 at 1:10 PM, Robert Scholte rfscho...@apache.org wrote: http://svn.apache.org/r1570870 fixes the unittests on my machine. I'll have to check was has changed between SCM 1.8 and 1.8.1, but there's a serious issue here. Robert Op Sat, 22 Feb 2014 18:48:53 +0100 schreef Benson Margulies bimargul...@gmail.com: Still 2.2.1. So, in version 2.2.1, org.apache.maven.artifact.transform.DefaultArtifactTransformationManager tries to patch a list that is injected, and gets into trouble because Plexus has made the list unmodifiable. Presumably, that unmodifiability was some improvement to plexus. I guess that taking 1.5.5 of the container doesn't work with 2.2.1, and the question is how far back one needs to go (give or take making a new release of maven-artifact-manager). Or even if any of this is the solution to Robert's original problem. On Sat, Feb 22, 2014 at 12:46 PM, Igor Fedorenko i...@ifedorenko.com wrote: What version of Maven does release plugin depend on? I think DefaultArtifactTransformationManager.initialize was removed in 3.x, at least it's not present in 3.2.1 and 3.1.1. -- Regards, Igor On 2/22/2014, 12:35, Benson Margulies wrote: I'm sorry, I did mislead you. Not surprisingly, adding maven-compat did not fix the problem with the apparently unmodifiable list. On Sat, Feb 22, 2014 at 12:33 PM, Benson Margulies bimargul...@gmail.com wrote: I may have misled you, but I'll try it. Caused by: org.codehaus.plexus.component.repository.exception.ComponentLifecycleException: Error constructing component role: 'org.apache.maven.artifact.resolver.ArtifactResolver', implementation: 'org.apache.maven.artifact.resolver.DefaultArtifactResolver', role hint: 'default' at org.codehaus.plexus.component.builder.XBeanComponentBuilder.createComponentInstance(XBeanComponentBuilder.java:176) at org.codehaus.plexus.component.builder.XBeanComponentBuilder.build(XBeanComponentBuilder.java:123) at org.codehaus.plexus.component.manager.AbstractComponentManager.createComponentInstance(AbstractComponentManager.java:181) at org.codehaus.plexus.component.manager.SingletonComponentManager.getComponent(SingletonComponentManager.java:67) at org.codehaus.plexus.DefaultComponentRegistry.getComponent(DefaultComponentRegistry.java:358) ... 33 more Caused by: org.apache.xbean.recipe.ConstructionException: Unable to convert property value from org.codehaus.plexus.component.builder.XBeanComponentBuilder$RequirementRecipe to org.apache.maven.artifact.transform.ArtifactTransformationManager for injection private org.apache.maven.artifact.transform.ArtifactTransformationManager org.apache.maven.artifact.resolver.DefaultArtifactResolver.transformationManager at org.apache.xbean.recipe.ObjectRecipe.setProperty(ObjectRecipe.java:472) at org.apache.xbean.recipe.ObjectRecipe.setProperties(ObjectRecipe.java:367) at org.apache.xbean.recipe.ObjectRecipe.internalCreate(ObjectRecipe.java:282) at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:96) at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:61) at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:49) at org.codehaus.plexus.component.builder.XBeanComponentBuilder.createComponentInstance(XBeanComponentBuilder.java:159) ... 37 more Caused by: java.lang.UnsupportedOperationException: You cannot modify this list. This list is a requirement of role: 'org.apache.maven.artifact.transform.ArtifactTransformationManager', implementation: 'org.apache.maven.artifact.transform.DefaultArtifactTransformationManager', role hint: 'default' and managed by the container. at org.codehaus.plexus.component.collections.ComponentList.remove(ComponentList.java:91) at org.apache.maven.artifact.transform.DefaultArtifactTransformationManager.initialize(DefaultArtifactTransformationManager.java:44) at org.codehaus.plexus.personality.plexus.lifecycle.phase.InitializePhase.execute(InitializePhase.java:33) at org.codehaus.plexus.lifecycle.AbstractLifecycleHandler.start(AbstractLifecycleHandler.java:97) at
Re: Releasing the release plugin
I am willing to do the work of RM'ing what we have here, since no one out there will test anything before it's released. On Sat, Feb 22, 2014 at 1:34 PM, Benson Margulies bimargul...@gmail.com wrote: On Sat, Feb 22, 2014 at 1:23 PM, Robert Scholte rfscho...@apache.org wrote: I've only changed maven-scm-manager-plexus to 1.8, and kept the rest on 1.9, such as the maven-scm-providers-standard. This brings me to the next question: Are you convinced that 1.9 will solve all the problems of the GIT users? I'm not, and I wouldn't prepare a git special-release without knowing it'll take away the GIT critical issues. I've tried to get feedback after some fixes, but didn't get the feedback I was searching for. Not I, I'm just reflecting the claims of others. Robert Op Sat, 22 Feb 2014 19:12:05 +0100 schreef Benson Margulies bimargul...@gmail.com: This, of course, does not help the people pining for the git support in 1.9. On Sat, Feb 22, 2014 at 1:10 PM, Robert Scholte rfscho...@apache.org wrote: http://svn.apache.org/r1570870 fixes the unittests on my machine. I'll have to check was has changed between SCM 1.8 and 1.8.1, but there's a serious issue here. Robert Op Sat, 22 Feb 2014 18:48:53 +0100 schreef Benson Margulies bimargul...@gmail.com: Still 2.2.1. So, in version 2.2.1, org.apache.maven.artifact.transform.DefaultArtifactTransformationManager tries to patch a list that is injected, and gets into trouble because Plexus has made the list unmodifiable. Presumably, that unmodifiability was some improvement to plexus. I guess that taking 1.5.5 of the container doesn't work with 2.2.1, and the question is how far back one needs to go (give or take making a new release of maven-artifact-manager). Or even if any of this is the solution to Robert's original problem. On Sat, Feb 22, 2014 at 12:46 PM, Igor Fedorenko i...@ifedorenko.com wrote: What version of Maven does release plugin depend on? I think DefaultArtifactTransformationManager.initialize was removed in 3.x, at least it's not present in 3.2.1 and 3.1.1. -- Regards, Igor On 2/22/2014, 12:35, Benson Margulies wrote: I'm sorry, I did mislead you. Not surprisingly, adding maven-compat did not fix the problem with the apparently unmodifiable list. On Sat, Feb 22, 2014 at 12:33 PM, Benson Margulies bimargul...@gmail.com wrote: I may have misled you, but I'll try it. Caused by: org.codehaus.plexus.component.repository.exception.ComponentLifecycleException: Error constructing component role: 'org.apache.maven.artifact.resolver.ArtifactResolver', implementation: 'org.apache.maven.artifact.resolver.DefaultArtifactResolver', role hint: 'default' at org.codehaus.plexus.component.builder.XBeanComponentBuilder.createComponentInstance(XBeanComponentBuilder.java:176) at org.codehaus.plexus.component.builder.XBeanComponentBuilder.build(XBeanComponentBuilder.java:123) at org.codehaus.plexus.component.manager.AbstractComponentManager.createComponentInstance(AbstractComponentManager.java:181) at org.codehaus.plexus.component.manager.SingletonComponentManager.getComponent(SingletonComponentManager.java:67) at org.codehaus.plexus.DefaultComponentRegistry.getComponent(DefaultComponentRegistry.java:358) ... 33 more Caused by: org.apache.xbean.recipe.ConstructionException: Unable to convert property value from org.codehaus.plexus.component.builder.XBeanComponentBuilder$RequirementRecipe to org.apache.maven.artifact.transform.ArtifactTransformationManager for injection private org.apache.maven.artifact.transform.ArtifactTransformationManager org.apache.maven.artifact.resolver.DefaultArtifactResolver.transformationManager at org.apache.xbean.recipe.ObjectRecipe.setProperty(ObjectRecipe.java:472) at org.apache.xbean.recipe.ObjectRecipe.setProperties(ObjectRecipe.java:367) at org.apache.xbean.recipe.ObjectRecipe.internalCreate(ObjectRecipe.java:282) at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:96) at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:61) at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:49) at org.codehaus.plexus.component.builder.XBeanComponentBuilder.createComponentInstance(XBeanComponentBuilder.java:159) ... 37 more Caused by: java.lang.UnsupportedOperationException: You cannot modify this list. This list is a requirement of role: 'org.apache.maven.artifact.transform.ArtifactTransformationManager', implementation: 'org.apache.maven.artifact.transform.DefaultArtifactTransformationManager', role hint: 'default' and managed by the container. at org.codehaus.plexus.component.collections.ComponentList.remove(ComponentList.java:91) at org.apache.maven.artifact.transform.DefaultArtifactTransformationManager.initialize(DefaultArtifactTransformationManager.java:44) at
Re: Releasing the release plugin
I'l try it before you release it. But I suggest you modernize it and by that I mean forget Maven 2.x and update it to the sisu-plexus, remove all the old crap. If you want to use the new stuff then move to a relatively modern version of Maven. If users need new capabilities then they move forward with Maven as well. We're EOL'ing Maven 2.x so I would just move forward. On Feb 22, 2014, at 10:34 AM, Benson Margulies bimargul...@gmail.com wrote: I am willing to do the work of RM'ing what we have here, since no one out there will test anything before it's released. On Sat, Feb 22, 2014 at 1:34 PM, Benson Margulies bimargul...@gmail.com wrote: On Sat, Feb 22, 2014 at 1:23 PM, Robert Scholte rfscho...@apache.org wrote: I've only changed maven-scm-manager-plexus to 1.8, and kept the rest on 1.9, such as the maven-scm-providers-standard. This brings me to the next question: Are you convinced that 1.9 will solve all the problems of the GIT users? I'm not, and I wouldn't prepare a git special-release without knowing it'll take away the GIT critical issues. I've tried to get feedback after some fixes, but didn't get the feedback I was searching for. Not I, I'm just reflecting the claims of others. Robert Op Sat, 22 Feb 2014 19:12:05 +0100 schreef Benson Margulies bimargul...@gmail.com: This, of course, does not help the people pining for the git support in 1.9. On Sat, Feb 22, 2014 at 1:10 PM, Robert Scholte rfscho...@apache.org wrote: http://svn.apache.org/r1570870 fixes the unittests on my machine. I'll have to check was has changed between SCM 1.8 and 1.8.1, but there's a serious issue here. Robert Op Sat, 22 Feb 2014 18:48:53 +0100 schreef Benson Margulies bimargul...@gmail.com: Still 2.2.1. So, in version 2.2.1, org.apache.maven.artifact.transform.DefaultArtifactTransformationManager tries to patch a list that is injected, and gets into trouble because Plexus has made the list unmodifiable. Presumably, that unmodifiability was some improvement to plexus. I guess that taking 1.5.5 of the container doesn't work with 2.2.1, and the question is how far back one needs to go (give or take making a new release of maven-artifact-manager). Or even if any of this is the solution to Robert's original problem. On Sat, Feb 22, 2014 at 12:46 PM, Igor Fedorenko i...@ifedorenko.com wrote: What version of Maven does release plugin depend on? I think DefaultArtifactTransformationManager.initialize was removed in 3.x, at least it's not present in 3.2.1 and 3.1.1. -- Regards, Igor On 2/22/2014, 12:35, Benson Margulies wrote: I'm sorry, I did mislead you. Not surprisingly, adding maven-compat did not fix the problem with the apparently unmodifiable list. On Sat, Feb 22, 2014 at 12:33 PM, Benson Margulies bimargul...@gmail.com wrote: I may have misled you, but I'll try it. Caused by: org.codehaus.plexus.component.repository.exception.ComponentLifecycleException: Error constructing component role: 'org.apache.maven.artifact.resolver.ArtifactResolver', implementation: 'org.apache.maven.artifact.resolver.DefaultArtifactResolver', role hint: 'default' at org.codehaus.plexus.component.builder.XBeanComponentBuilder.createComponentInstance(XBeanComponentBuilder.java:176) at org.codehaus.plexus.component.builder.XBeanComponentBuilder.build(XBeanComponentBuilder.java:123) at org.codehaus.plexus.component.manager.AbstractComponentManager.createComponentInstance(AbstractComponentManager.java:181) at org.codehaus.plexus.component.manager.SingletonComponentManager.getComponent(SingletonComponentManager.java:67) at org.codehaus.plexus.DefaultComponentRegistry.getComponent(DefaultComponentRegistry.java:358) ... 33 more Caused by: org.apache.xbean.recipe.ConstructionException: Unable to convert property value from org.codehaus.plexus.component.builder.XBeanComponentBuilder$RequirementRecipe to org.apache.maven.artifact.transform.ArtifactTransformationManager for injection private org.apache.maven.artifact.transform.ArtifactTransformationManager org.apache.maven.artifact.resolver.DefaultArtifactResolver.transformationManager at org.apache.xbean.recipe.ObjectRecipe.setProperty(ObjectRecipe.java:472) at org.apache.xbean.recipe.ObjectRecipe.setProperties(ObjectRecipe.java:367) at org.apache.xbean.recipe.ObjectRecipe.internalCreate(ObjectRecipe.java:282) at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:96) at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:61) at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:49) at org.codehaus.plexus.component.builder.XBeanComponentBuilder.createComponentInstance(XBeanComponentBuilder.java:159) ... 37 more Caused by: java.lang.UnsupportedOperationException: You cannot modify this list. This list is a requirement of role:
Re: Releasing the release plugin
Seems to me we might as well make one last release with what's there now, just in case it helps someone. Then clean the closet. On Sat, Feb 22, 2014 at 1:47 PM, Jason van Zyl ja...@takari.io wrote: I'l try it before you release it. But I suggest you modernize it and by that I mean forget Maven 2.x and update it to the sisu-plexus, remove all the old crap. If you want to use the new stuff then move to a relatively modern version of Maven. If users need new capabilities then they move forward with Maven as well. We're EOL'ing Maven 2.x so I would just move forward. On Feb 22, 2014, at 10:34 AM, Benson Margulies bimargul...@gmail.com wrote: I am willing to do the work of RM'ing what we have here, since no one out there will test anything before it's released. On Sat, Feb 22, 2014 at 1:34 PM, Benson Margulies bimargul...@gmail.com wrote: On Sat, Feb 22, 2014 at 1:23 PM, Robert Scholte rfscho...@apache.org wrote: I've only changed maven-scm-manager-plexus to 1.8, and kept the rest on 1.9, such as the maven-scm-providers-standard. This brings me to the next question: Are you convinced that 1.9 will solve all the problems of the GIT users? I'm not, and I wouldn't prepare a git special-release without knowing it'll take away the GIT critical issues. I've tried to get feedback after some fixes, but didn't get the feedback I was searching for. Not I, I'm just reflecting the claims of others. Robert Op Sat, 22 Feb 2014 19:12:05 +0100 schreef Benson Margulies bimargul...@gmail.com: This, of course, does not help the people pining for the git support in 1.9. On Sat, Feb 22, 2014 at 1:10 PM, Robert Scholte rfscho...@apache.org wrote: http://svn.apache.org/r1570870 fixes the unittests on my machine. I'll have to check was has changed between SCM 1.8 and 1.8.1, but there's a serious issue here. Robert Op Sat, 22 Feb 2014 18:48:53 +0100 schreef Benson Margulies bimargul...@gmail.com: Still 2.2.1. So, in version 2.2.1, org.apache.maven.artifact.transform.DefaultArtifactTransformationManager tries to patch a list that is injected, and gets into trouble because Plexus has made the list unmodifiable. Presumably, that unmodifiability was some improvement to plexus. I guess that taking 1.5.5 of the container doesn't work with 2.2.1, and the question is how far back one needs to go (give or take making a new release of maven-artifact-manager). Or even if any of this is the solution to Robert's original problem. On Sat, Feb 22, 2014 at 12:46 PM, Igor Fedorenko i...@ifedorenko.com wrote: What version of Maven does release plugin depend on? I think DefaultArtifactTransformationManager.initialize was removed in 3.x, at least it's not present in 3.2.1 and 3.1.1. -- Regards, Igor On 2/22/2014, 12:35, Benson Margulies wrote: I'm sorry, I did mislead you. Not surprisingly, adding maven-compat did not fix the problem with the apparently unmodifiable list. On Sat, Feb 22, 2014 at 12:33 PM, Benson Margulies bimargul...@gmail.com wrote: I may have misled you, but I'll try it. Caused by: org.codehaus.plexus.component.repository.exception.ComponentLifecycleException: Error constructing component role: 'org.apache.maven.artifact.resolver.ArtifactResolver', implementation: 'org.apache.maven.artifact.resolver.DefaultArtifactResolver', role hint: 'default' at org.codehaus.plexus.component.builder.XBeanComponentBuilder.createComponentInstance(XBeanComponentBuilder.java:176) at org.codehaus.plexus.component.builder.XBeanComponentBuilder.build(XBeanComponentBuilder.java:123) at org.codehaus.plexus.component.manager.AbstractComponentManager.createComponentInstance(AbstractComponentManager.java:181) at org.codehaus.plexus.component.manager.SingletonComponentManager.getComponent(SingletonComponentManager.java:67) at org.codehaus.plexus.DefaultComponentRegistry.getComponent(DefaultComponentRegistry.java:358) ... 33 more Caused by: org.apache.xbean.recipe.ConstructionException: Unable to convert property value from org.codehaus.plexus.component.builder.XBeanComponentBuilder$RequirementRecipe to org.apache.maven.artifact.transform.ArtifactTransformationManager for injection private org.apache.maven.artifact.transform.ArtifactTransformationManager org.apache.maven.artifact.resolver.DefaultArtifactResolver.transformationManager at org.apache.xbean.recipe.ObjectRecipe.setProperty(ObjectRecipe.java:472) at org.apache.xbean.recipe.ObjectRecipe.setProperties(ObjectRecipe.java:367) at org.apache.xbean.recipe.ObjectRecipe.internalCreate(ObjectRecipe.java:282) at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:96) at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:61) at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:49) at org.codehaus.plexus.component.builder.XBeanComponentBuilder.createComponentInstance(XBeanComponentBuilder.java:159) ...
Re: Releasing the release plugin
Jason, I can't help suspecting that the first step in housecleaning here will be a new-tech SCM release, do you think so? On Sat, Feb 22, 2014 at 1:56 PM, Benson Margulies bimargul...@gmail.com wrote: Seems to me we might as well make one last release with what's there now, just in case it helps someone. Then clean the closet. On Sat, Feb 22, 2014 at 1:47 PM, Jason van Zyl ja...@takari.io wrote: I'l try it before you release it. But I suggest you modernize it and by that I mean forget Maven 2.x and update it to the sisu-plexus, remove all the old crap. If you want to use the new stuff then move to a relatively modern version of Maven. If users need new capabilities then they move forward with Maven as well. We're EOL'ing Maven 2.x so I would just move forward. On Feb 22, 2014, at 10:34 AM, Benson Margulies bimargul...@gmail.com wrote: I am willing to do the work of RM'ing what we have here, since no one out there will test anything before it's released. On Sat, Feb 22, 2014 at 1:34 PM, Benson Margulies bimargul...@gmail.com wrote: On Sat, Feb 22, 2014 at 1:23 PM, Robert Scholte rfscho...@apache.org wrote: I've only changed maven-scm-manager-plexus to 1.8, and kept the rest on 1.9, such as the maven-scm-providers-standard. This brings me to the next question: Are you convinced that 1.9 will solve all the problems of the GIT users? I'm not, and I wouldn't prepare a git special-release without knowing it'll take away the GIT critical issues. I've tried to get feedback after some fixes, but didn't get the feedback I was searching for. Not I, I'm just reflecting the claims of others. Robert Op Sat, 22 Feb 2014 19:12:05 +0100 schreef Benson Margulies bimargul...@gmail.com: This, of course, does not help the people pining for the git support in 1.9. On Sat, Feb 22, 2014 at 1:10 PM, Robert Scholte rfscho...@apache.org wrote: http://svn.apache.org/r1570870 fixes the unittests on my machine. I'll have to check was has changed between SCM 1.8 and 1.8.1, but there's a serious issue here. Robert Op Sat, 22 Feb 2014 18:48:53 +0100 schreef Benson Margulies bimargul...@gmail.com: Still 2.2.1. So, in version 2.2.1, org.apache.maven.artifact.transform.DefaultArtifactTransformationManager tries to patch a list that is injected, and gets into trouble because Plexus has made the list unmodifiable. Presumably, that unmodifiability was some improvement to plexus. I guess that taking 1.5.5 of the container doesn't work with 2.2.1, and the question is how far back one needs to go (give or take making a new release of maven-artifact-manager). Or even if any of this is the solution to Robert's original problem. On Sat, Feb 22, 2014 at 12:46 PM, Igor Fedorenko i...@ifedorenko.com wrote: What version of Maven does release plugin depend on? I think DefaultArtifactTransformationManager.initialize was removed in 3.x, at least it's not present in 3.2.1 and 3.1.1. -- Regards, Igor On 2/22/2014, 12:35, Benson Margulies wrote: I'm sorry, I did mislead you. Not surprisingly, adding maven-compat did not fix the problem with the apparently unmodifiable list. On Sat, Feb 22, 2014 at 12:33 PM, Benson Margulies bimargul...@gmail.com wrote: I may have misled you, but I'll try it. Caused by: org.codehaus.plexus.component.repository.exception.ComponentLifecycleException: Error constructing component role: 'org.apache.maven.artifact.resolver.ArtifactResolver', implementation: 'org.apache.maven.artifact.resolver.DefaultArtifactResolver', role hint: 'default' at org.codehaus.plexus.component.builder.XBeanComponentBuilder.createComponentInstance(XBeanComponentBuilder.java:176) at org.codehaus.plexus.component.builder.XBeanComponentBuilder.build(XBeanComponentBuilder.java:123) at org.codehaus.plexus.component.manager.AbstractComponentManager.createComponentInstance(AbstractComponentManager.java:181) at org.codehaus.plexus.component.manager.SingletonComponentManager.getComponent(SingletonComponentManager.java:67) at org.codehaus.plexus.DefaultComponentRegistry.getComponent(DefaultComponentRegistry.java:358) ... 33 more Caused by: org.apache.xbean.recipe.ConstructionException: Unable to convert property value from org.codehaus.plexus.component.builder.XBeanComponentBuilder$RequirementRecipe to org.apache.maven.artifact.transform.ArtifactTransformationManager for injection private org.apache.maven.artifact.transform.ArtifactTransformationManager org.apache.maven.artifact.resolver.DefaultArtifactResolver.transformationManager at org.apache.xbean.recipe.ObjectRecipe.setProperty(ObjectRecipe.java:472) at org.apache.xbean.recipe.ObjectRecipe.setProperties(ObjectRecipe.java:367) at org.apache.xbean.recipe.ObjectRecipe.internalCreate(ObjectRecipe.java:282) at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:96) at
Java 1.5
How much longer with this Java 1.5 business? It' a giant pain. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Site plugin
Which versions of Maven failed for you? On Sat, Feb 22, 2014 at 7:03 PM, Jason van Zyl ja...@takari.io wrote: That version of the site plugin we have configured just doesn't work with newer versions of Maven. I ran the command with Maven 3.0.4 and it works. We are a long, long, long way from push button releases. On Feb 22, 2014, at 1:54 AM, Dennis Lundberg denn...@apache.org wrote: Hi Jason, Looking at the stack trace it seems to be the remote resources plugin that is throwing an NPE. Didn't you release 1.5 of that plugin because of issues with core? Your build is using 1.4... -- Dennis Lundberg Den 22 feb 2014 05:30 skrev Jason van Zyl ja...@takari.io: Not sure who looks after the site plugin these days but I can't run the staging part to copy it over to the production site: In the release checkout I ran: mvn -Preporting site site:stage and got: https://gist.github.com/jvanzyl/9148731 I'll continue on with the rest of the work but I will release tomorrow regardless. I don't have time to debug the site plugin. Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl http://twitter.com/takari_io - Simplex sigillum veri. (Simplicity is the seal of truth.) Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl http://twitter.com/takari_io - We know what we are, but know not what we may be. -- Shakespeare -- Dennis Lundberg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Java 1.5
Which business are you referring to? On Sat, Feb 22, 2014 at 8:02 PM, Benson Margulies bimargul...@gmail.com wrote: How much longer with this Java 1.5 business? It' a giant pain. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Dennis Lundberg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Java 1.5
The business of being required to use it in all Maven releases, which adds a layer of VM complexity to my process. On Sat, Feb 22, 2014 at 2:31 PM, Dennis Lundberg denn...@apache.org wrote: Which business are you referring to? On Sat, Feb 22, 2014 at 8:02 PM, Benson Margulies bimargul...@gmail.com wrote: How much longer with this Java 1.5 business? It' a giant pain. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Dennis Lundberg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Java 1.5
I think we might just use animal sniffer to check such compatibility if we want to keep it. Not 100% safe but enought to cover a respectable compatibility My 2 cents — Sent from Mailbox for iPhone On Sat, Feb 22, 2014 at 8:44 PM, Benson Margulies bimargul...@gmail.com wrote: The business of being required to use it in all Maven releases, which adds a layer of VM complexity to my process. On Sat, Feb 22, 2014 at 2:31 PM, Dennis Lundberg denn...@apache.org wrote: Which business are you referring to? On Sat, Feb 22, 2014 at 8:02 PM, Benson Margulies bimargul...@gmail.com wrote: How much longer with this Java 1.5 business? It' a giant pain. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Dennis Lundberg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Releasing the release plugin
If you're going to try and cut a release that works with 2.x then I wouldn't worry about updating scm. I think users on Git are also more likely to be on m3 which is where the scm issues are yes? If you want to cut a quick release for 2.x users I would try and leave as many of the existing deps alone. jvz On Feb 22, 2014, at 10:58 AM, Benson Margulies bimargul...@gmail.com wrote: Jason, I can't help suspecting that the first step in housecleaning here will be a new-tech SCM release, do you think so? On Sat, Feb 22, 2014 at 1:56 PM, Benson Margulies bimargul...@gmail.com wrote: Seems to me we might as well make one last release with what's there now, just in case it helps someone. Then clean the closet. On Sat, Feb 22, 2014 at 1:47 PM, Jason van Zyl ja...@takari.io wrote: I'l try it before you release it. But I suggest you modernize it and by that I mean forget Maven 2.x and update it to the sisu-plexus, remove all the old crap. If you want to use the new stuff then move to a relatively modern version of Maven. If users need new capabilities then they move forward with Maven as well. We're EOL'ing Maven 2.x so I would just move forward. On Feb 22, 2014, at 10:34 AM, Benson Margulies bimargul...@gmail.com wrote: I am willing to do the work of RM'ing what we have here, since no one out there will test anything before it's released. On Sat, Feb 22, 2014 at 1:34 PM, Benson Margulies bimargul...@gmail.com wrote: On Sat, Feb 22, 2014 at 1:23 PM, Robert Scholte rfscho...@apache.org wrote: I've only changed maven-scm-manager-plexus to 1.8, and kept the rest on 1.9, such as the maven-scm-providers-standard. This brings me to the next question: Are you convinced that 1.9 will solve all the problems of the GIT users? I'm not, and I wouldn't prepare a git special-release without knowing it'll take away the GIT critical issues. I've tried to get feedback after some fixes, but didn't get the feedback I was searching for. Not I, I'm just reflecting the claims of others. Robert Op Sat, 22 Feb 2014 19:12:05 +0100 schreef Benson Margulies bimargul...@gmail.com: This, of course, does not help the people pining for the git support in 1.9. On Sat, Feb 22, 2014 at 1:10 PM, Robert Scholte rfscho...@apache.org wrote: http://svn.apache.org/r1570870 fixes the unittests on my machine. I'll have to check was has changed between SCM 1.8 and 1.8.1, but there's a serious issue here. Robert Op Sat, 22 Feb 2014 18:48:53 +0100 schreef Benson Margulies bimargul...@gmail.com: Still 2.2.1. So, in version 2.2.1, org.apache.maven.artifact.transform.DefaultArtifactTransformationManager tries to patch a list that is injected, and gets into trouble because Plexus has made the list unmodifiable. Presumably, that unmodifiability was some improvement to plexus. I guess that taking 1.5.5 of the container doesn't work with 2.2.1, and the question is how far back one needs to go (give or take making a new release of maven-artifact-manager). Or even if any of this is the solution to Robert's original problem. On Sat, Feb 22, 2014 at 12:46 PM, Igor Fedorenko i...@ifedorenko.com wrote: What version of Maven does release plugin depend on? I think DefaultArtifactTransformationManager.initialize was removed in 3.x, at least it's not present in 3.2.1 and 3.1.1. -- Regards, Igor On 2/22/2014, 12:35, Benson Margulies wrote: I'm sorry, I did mislead you. Not surprisingly, adding maven-compat did not fix the problem with the apparently unmodifiable list. On Sat, Feb 22, 2014 at 12:33 PM, Benson Margulies bimargul...@gmail.com wrote: I may have misled you, but I'll try it. Caused by: org.codehaus.plexus.component.repository.exception.ComponentLifecycleException: Error constructing component role: 'org.apache.maven.artifact.resolver.ArtifactResolver', implementation: 'org.apache.maven.artifact.resolver.DefaultArtifactResolver', role hint: 'default' at org.codehaus.plexus.component.builder.XBeanComponentBuilder.createComponentInstance(XBeanComponentBuilder.java:176) at org.codehaus.plexus.component.builder.XBeanComponentBuilder.build(XBeanComponentBuilder.java:123) at org.codehaus.plexus.component.manager.AbstractComponentManager.createComponentInstance(AbstractComponentManager.java:181) at org.codehaus.plexus.component.manager.SingletonComponentManager.getComponent(SingletonComponentManager.java:67) at org.codehaus.plexus.DefaultComponentRegistry.getComponent(DefaultComponentRegistry.java:358) ... 33 more Caused by: org.apache.xbean.recipe.ConstructionException: Unable to convert property value from org.codehaus.plexus.component.builder.XBeanComponentBuilder$RequirementRecipe to org.apache.maven.artifact.transform.ArtifactTransformationManager for injection private org.apache.maven.artifact.transform.ArtifactTransformationManager
Re: Site plugin
I had build of master I was using. jvz On Feb 22, 2014, at 11:25 AM, Dennis Lundberg dennisl.apa...@gmail.com wrote: Which versions of Maven failed for you? On Sat, Feb 22, 2014 at 7:03 PM, Jason van Zyl ja...@takari.io wrote: That version of the site plugin we have configured just doesn't work with newer versions of Maven. I ran the command with Maven 3.0.4 and it works. We are a long, long, long way from push button releases. On Feb 22, 2014, at 1:54 AM, Dennis Lundberg denn...@apache.org wrote: Hi Jason, Looking at the stack trace it seems to be the remote resources plugin that is throwing an NPE. Didn't you release 1.5 of that plugin because of issues with core? Your build is using 1.4... -- Dennis Lundberg Den 22 feb 2014 05:30 skrev Jason van Zyl ja...@takari.io: Not sure who looks after the site plugin these days but I can't run the staging part to copy it over to the production site: In the release checkout I ran: mvn -Preporting site site:stage and got: https://gist.github.com/jvanzyl/9148731 I'll continue on with the rest of the work but I will release tomorrow regardless. I don't have time to debug the site plugin. Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl http://twitter.com/takari_io - Simplex sigillum veri. (Simplicity is the seal of truth.) Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl http://twitter.com/takari_io - We know what we are, but know not what we may be. -- Shakespeare -- Dennis Lundberg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Java 1.5
Didn't we decide that everything can be 1.6? I remember because it was one of Stephen's overly long emails :-) jvz On Feb 22, 2014, at 11:02 AM, Benson Margulies bimargul...@gmail.com wrote: How much longer with this Java 1.5 business? It' a giant pain. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Java 1.5
;) AFAIR for core yes. New releases (thus 3.2) should be certified 1.6+ For plugins it's another story I suppose depending of the version of maven core they are supposed to support.. — Sent from Mailbox for iPhone On Sat, Feb 22, 2014 at 9:04 PM, Jason van Zyl ja...@tesla.io wrote: Didn't we decide that everything can be 1.6? I remember because it was one of Stephen's overly long emails :-) jvz On Feb 22, 2014, at 11:02 AM, Benson Margulies bimargul...@gmail.com wrote: How much longer with this Java 1.5 business? It' a giant pain. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Site plugin
Yeah need to update site plugin to 3.3 and it should work on mvn 2.x and 3.x (yes 2.x is EOL already but anyways) On Saturday, 22 February 2014, Jason van Zyl ja...@tesla.io wrote: I had build of master I was using. jvz On Feb 22, 2014, at 11:25 AM, Dennis Lundberg dennisl.apa...@gmail.comjavascript:; wrote: Which versions of Maven failed for you? On Sat, Feb 22, 2014 at 7:03 PM, Jason van Zyl ja...@takari.iojavascript:; wrote: That version of the site plugin we have configured just doesn't work with newer versions of Maven. I ran the command with Maven 3.0.4 and it works. We are a long, long, long way from push button releases. On Feb 22, 2014, at 1:54 AM, Dennis Lundberg denn...@apache.orgjavascript:; wrote: Hi Jason, Looking at the stack trace it seems to be the remote resources plugin that is throwing an NPE. Didn't you release 1.5 of that plugin because of issues with core? Your build is using 1.4... -- Dennis Lundberg Den 22 feb 2014 05:30 skrev Jason van Zyl ja...@takari.iojavascript:; : Not sure who looks after the site plugin these days but I can't run the staging part to copy it over to the production site: In the release checkout I ran: mvn -Preporting site site:stage and got: https://gist.github.com/jvanzyl/9148731 I'll continue on with the rest of the work but I will release tomorrow regardless. I don't have time to debug the site plugin. Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl http://twitter.com/takari_io - Simplex sigillum veri. (Simplicity is the seal of truth.) Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl http://twitter.com/takari_io - We know what we are, but know not what we may be. -- Shakespeare -- Dennis Lundberg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org javascript:; For additional commands, e-mail: dev-h...@maven.apache.orgjavascript:; - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org javascript:; For additional commands, e-mail: dev-h...@maven.apache.org javascript:; -- Sent from my phone
Re: Java 1.5
Somehow with my brief emails you find some misinterpretation to take a hump at! Verbose or misunderstood... You decide ;-) Sent from my iPhone On 22 Feb 2014, at 20:03, Jason van Zyl ja...@tesla.io wrote: Didn't we decide that everything can be 1.6? I remember because it was one of Stephen's overly long emails :-) jvz On Feb 22, 2014, at 11:02 AM, Benson Margulies bimargul...@gmail.com wrote: How much longer with this Java 1.5 business? It' a giant pain. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Java 1.5
If a plugin depends on Maven 2.2.1 through 3.1.1 then we are stuck with Java 1.5 Hence my version policy that you lot are all ignoring commenting on... No comments means I'll just put it up for a vote ;-) Sent from my iPhone On 22 Feb 2014, at 20:10, Arnaud Héritier aherit...@gmail.com wrote: ;) AFAIR for core yes. New releases (thus 3.2) should be certified 1.6+ For plugins it's another story I suppose depending of the version of maven core they are supposed to support.. — Sent from Mailbox for iPhone On Sat, Feb 22, 2014 at 9:04 PM, Jason van Zyl ja...@tesla.io wrote: Didn't we decide that everything can be 1.6? I remember because it was one of Stephen's overly long emails :-) jvz On Feb 22, 2014, at 11:02 AM, Benson Margulies bimargul...@gmail.com wrote: How much longer with this Java 1.5 business? It' a giant pain. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Releasing the release plugin
Found the cause: SCM 1.8 has the following components.xml component-set components component roleorg.apache.maven.scm.manager.ScmManager/role implementationorg.apache.maven.scm.manager.plexus.DefaultScmManager/implementation description/description isolated-realmfalse/isolated-realm requirements requirement roleorg.apache.maven.scm.provider.ScmProvider/role field-namescmProviders/field-name /requirement /requirements /component /components /component-set while newer SCM version have the following: ?xml version=1.0 encoding=UTF-8? component-set components component roleorg.apache.maven.scm.manager.ScmManager/role role-hintdefault/role-hint implementationorg.apache.maven.scm.manager.plexus.DefaultScmManager/implementation description / isolated-realmfalse/isolated-realm requirements requirement roleorg.apache.maven.scm.provider.ScmProvider/role field-namescmProviders/field-name /requirement /requirements /component /components /component-set Notice the additional role-hintdefault/role-hint line. The DefaultScmManager didn't specify the hint. So the result of generate-metadata has changed with plexus-component-metadata. Robert Op Sat, 22 Feb 2014 19:10:06 +0100 schreef Robert Scholte rfscho...@apache.org: http://svn.apache.org/r1570870 fixes the unittests on my machine. I'll have to check was has changed between SCM 1.8 and 1.8.1, but there's a serious issue here. Robert Op Sat, 22 Feb 2014 18:48:53 +0100 schreef Benson Margulies bimargul...@gmail.com: Still 2.2.1. So, in version 2.2.1, org.apache.maven.artifact.transform.DefaultArtifactTransformationManager tries to patch a list that is injected, and gets into trouble because Plexus has made the list unmodifiable. Presumably, that unmodifiability was some improvement to plexus. I guess that taking 1.5.5 of the container doesn't work with 2.2.1, and the question is how far back one needs to go (give or take making a new release of maven-artifact-manager). Or even if any of this is the solution to Robert's original problem. On Sat, Feb 22, 2014 at 12:46 PM, Igor Fedorenko i...@ifedorenko.com wrote: What version of Maven does release plugin depend on? I think DefaultArtifactTransformationManager.initialize was removed in 3.x, at least it's not present in 3.2.1 and 3.1.1. -- Regards, Igor On 2/22/2014, 12:35, Benson Margulies wrote: I'm sorry, I did mislead you. Not surprisingly, adding maven-compat did not fix the problem with the apparently unmodifiable list. On Sat, Feb 22, 2014 at 12:33 PM, Benson Margulies bimargul...@gmail.com wrote: I may have misled you, but I'll try it. Caused by: org.codehaus.plexus.component.repository.exception.ComponentLifecycleException: Error constructing component role: 'org.apache.maven.artifact.resolver.ArtifactResolver', implementation: 'org.apache.maven.artifact.resolver.DefaultArtifactResolver', role hint: 'default' at org.codehaus.plexus.component.builder.XBeanComponentBuilder.createComponentInstance(XBeanComponentBuilder.java:176) at org.codehaus.plexus.component.builder.XBeanComponentBuilder.build(XBeanComponentBuilder.java:123) at org.codehaus.plexus.component.manager.AbstractComponentManager.createComponentInstance(AbstractComponentManager.java:181) at org.codehaus.plexus.component.manager.SingletonComponentManager.getComponent(SingletonComponentManager.java:67) at org.codehaus.plexus.DefaultComponentRegistry.getComponent(DefaultComponentRegistry.java:358) ... 33 more Caused by: org.apache.xbean.recipe.ConstructionException: Unable to convert property value from org.codehaus.plexus.component.builder.XBeanComponentBuilder$RequirementRecipe to org.apache.maven.artifact.transform.ArtifactTransformationManager for injection private org.apache.maven.artifact.transform.ArtifactTransformationManager org.apache.maven.artifact.resolver.DefaultArtifactResolver.transformationManager at org.apache.xbean.recipe.ObjectRecipe.setProperty(ObjectRecipe.java:472) at org.apache.xbean.recipe.ObjectRecipe.setProperties(ObjectRecipe.java:367) at org.apache.xbean.recipe.ObjectRecipe.internalCreate(ObjectRecipe.java:282) at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:96) at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:61) at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:49) at org.codehaus.plexus.component.builder.XBeanComponentBuilder.createComponentInstance(XBeanComponentBuilder.java:159) ... 37 more Caused by: java.lang.UnsupportedOperationException: You cannot modify this list. This list is a requirement of role: 'org.apache.maven.artifact.transform.ArtifactTransformationManager', implementation: 'org.apache.maven.artifact.transform.DefaultArtifactTransformationManager', role hint: 'default' and managed by the container. at
Re: [VOTE] Release Apache Maven GPG Plugin version 1.5
+1 - can be built and tested from source-release.zip - rat: only approved licenses - sha11: correct - site: ok Robert Op Fri, 21 Feb 2014 15:13:14 +0100 schreef Stephen Connolly stephen.alan.conno...@gmail.com: Hi, We solved 4 issues:http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11431styleName=Htmlversion=17635 There are still a couple of issues left in JIRA:http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11431status=1 Staging repo: http://repository.apache.org/content/repositories/maven-1007/ Source release: http://repository.apache.org/content/repositories/maven-1007/org/apache/maven/plugins/maven-gpg-plugin/1.5/maven-gpg-plugin-1.5-source-release.zip Source release checksum(s): maven-gpg-plugin-1.5-source-release.zip sha1: 5837a389a793d08ab5673b319e6a84e992b3872d Staging site:http://maven.apache.org/plugins-archives/maven-gpg-plugin-LATEST/ Guide to testing staged releases:http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Java 1.5
+1 to dump Java5 compat. In about 2 months, even Java 6 will rapidly become old. We're already using Java 1.7 at our shop, and plan to migrate to 1.8 asap. And we're really not a startup kind of company ;-). And I'm sure the features in 1.8 (compared to the ones in the previous version) is gonna accelerate the move. Sure you'll always companies where migration is said to be hard, but any move being made would be considered hard to absorb by those anyway... :) Stephen, when talking about version policy in the current context, do you mean something like any plugin could from now on be released with 1.6+ requirement, you would just have to make sure to bump the MAJOR (or only minor?) version number to acknowledge the change ? 2014-02-22 21:26 GMT+01:00 Stephen Connolly stephen.alan.conno...@gmail.com : If a plugin depends on Maven 2.2.1 through 3.1.1 then we are stuck with Java 1.5 Hence my version policy that you lot are all ignoring commenting on... No comments means I'll just put it up for a vote ;-) Sent from my iPhone On 22 Feb 2014, at 20:10, Arnaud Héritier aherit...@gmail.com wrote: ;) AFAIR for core yes. New releases (thus 3.2) should be certified 1.6+ For plugins it's another story I suppose depending of the version of maven core they are supposed to support.. — Sent from Mailbox for iPhone On Sat, Feb 22, 2014 at 9:04 PM, Jason van Zyl ja...@tesla.io wrote: Didn't we decide that everything can be 1.6? I remember because it was one of Stephen's overly long emails :-) jvz On Feb 22, 2014, at 11:02 AM, Benson Margulies bimargul...@gmail.com wrote: How much longer with this Java 1.5 business? It' a giant pain. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor ! nbsp;! dev-h...@maven.apache.org
Re: Releasing the release plugin
That's my plan. Cut a release with things as they are today, though Robert's discovery suggests at least a brief delay. On Sat, Feb 22, 2014 at 3:00 PM, Jason van Zyl ja...@tesla.io wrote: If you're going to try and cut a release that works with 2.x then I wouldn't worry about updating scm. I think users on Git are also more likely to be on m3 which is where the scm issues are yes? If you want to cut a quick release for 2.x users I would try and leave as many of the existing deps alone. jvz On Feb 22, 2014, at 10:58 AM, Benson Margulies bimargul...@gmail.com wrote: Jason, I can't help suspecting that the first step in housecleaning here will be a new-tech SCM release, do you think so? On Sat, Feb 22, 2014 at 1:56 PM, Benson Margulies bimargul...@gmail.com wrote: Seems to me we might as well make one last release with what's there now, just in case it helps someone. Then clean the closet. On Sat, Feb 22, 2014 at 1:47 PM, Jason van Zyl ja...@takari.io wrote: I'l try it before you release it. But I suggest you modernize it and by that I mean forget Maven 2.x and update it to the sisu-plexus, remove all the old crap. If you want to use the new stuff then move to a relatively modern version of Maven. If users need new capabilities then they move forward with Maven as well. We're EOL'ing Maven 2.x so I would just move forward. On Feb 22, 2014, at 10:34 AM, Benson Margulies bimargul...@gmail.com wrote: I am willing to do the work of RM'ing what we have here, since no one out there will test anything before it's released. On Sat, Feb 22, 2014 at 1:34 PM, Benson Margulies bimargul...@gmail.com wrote: On Sat, Feb 22, 2014 at 1:23 PM, Robert Scholte rfscho...@apache.org wrote: I've only changed maven-scm-manager-plexus to 1.8, and kept the rest on 1.9, such as the maven-scm-providers-standard. This brings me to the next question: Are you convinced that 1.9 will solve all the problems of the GIT users? I'm not, and I wouldn't prepare a git special-release without knowing it'll take away the GIT critical issues. I've tried to get feedback after some fixes, but didn't get the feedback I was searching for. Not I, I'm just reflecting the claims of others. Robert Op Sat, 22 Feb 2014 19:12:05 +0100 schreef Benson Margulies bimargul...@gmail.com: This, of course, does not help the people pining for the git support in 1.9. On Sat, Feb 22, 2014 at 1:10 PM, Robert Scholte rfscho...@apache.org wrote: http://svn.apache.org/r1570870 fixes the unittests on my machine. I'll have to check was has changed between SCM 1.8 and 1.8.1, but there's a serious issue here. Robert Op Sat, 22 Feb 2014 18:48:53 +0100 schreef Benson Margulies bimargul...@gmail.com: Still 2.2.1. So, in version 2.2.1, org.apache.maven.artifact.transform.DefaultArtifactTransformationManager tries to patch a list that is injected, and gets into trouble because Plexus has made the list unmodifiable. Presumably, that unmodifiability was some improvement to plexus. I guess that taking 1.5.5 of the container doesn't work with 2.2.1, and the question is how far back one needs to go (give or take making a new release of maven-artifact-manager). Or even if any of this is the solution to Robert's original problem. On Sat, Feb 22, 2014 at 12:46 PM, Igor Fedorenko i...@ifedorenko.com wrote: What version of Maven does release plugin depend on? I think DefaultArtifactTransformationManager.initialize was removed in 3.x, at least it's not present in 3.2.1 and 3.1.1. -- Regards, Igor On 2/22/2014, 12:35, Benson Margulies wrote: I'm sorry, I did mislead you. Not surprisingly, adding maven-compat did not fix the problem with the apparently unmodifiable list. On Sat, Feb 22, 2014 at 12:33 PM, Benson Margulies bimargul...@gmail.com wrote: I may have misled you, but I'll try it. Caused by: org.codehaus.plexus.component.repository.exception.ComponentLifecycleException: Error constructing component role: 'org.apache.maven.artifact.resolver.ArtifactResolver', implementation: 'org.apache.maven.artifact.resolver.DefaultArtifactResolver', role hint: 'default' at org.codehaus.plexus.component.builder.XBeanComponentBuilder.createComponentInstance(XBeanComponentBuilder.java:176) at org.codehaus.plexus.component.builder.XBeanComponentBuilder.build(XBeanComponentBuilder.java:123) at org.codehaus.plexus.component.manager.AbstractComponentManager.createComponentInstance(AbstractComponentManager.java:181) at org.codehaus.plexus.component.manager.SingletonComponentManager.getComponent(SingletonComponentManager.java:67) at org.codehaus.plexus.DefaultComponentRegistry.getComponent(DefaultComponentRegistry.java:358) ... 33 more Caused by: org.apache.xbean.recipe.ConstructionException: Unable to convert property value from org.codehaus.plexus.component.builder.XBeanComponentBuilder$RequirementRecipe to
Re: Releasing the release plugin
I can't built the m-r-p with Java 1.5. The compiler plugin fails. Don't we have source and target set so that I can leave JAVA_HOME at 1.6 and still cut a release? On Sat, Feb 22, 2014 at 5:13 PM, Benson Margulies bimargul...@gmail.com wrote: That's my plan. Cut a release with things as they are today, though Robert's discovery suggests at least a brief delay. On Sat, Feb 22, 2014 at 3:00 PM, Jason van Zyl ja...@tesla.io wrote: If you're going to try and cut a release that works with 2.x then I wouldn't worry about updating scm. I think users on Git are also more likely to be on m3 which is where the scm issues are yes? If you want to cut a quick release for 2.x users I would try and leave as many of the existing deps alone. jvz On Feb 22, 2014, at 10:58 AM, Benson Margulies bimargul...@gmail.com wrote: Jason, I can't help suspecting that the first step in housecleaning here will be a new-tech SCM release, do you think so? On Sat, Feb 22, 2014 at 1:56 PM, Benson Margulies bimargul...@gmail.com wrote: Seems to me we might as well make one last release with what's there now, just in case it helps someone. Then clean the closet. On Sat, Feb 22, 2014 at 1:47 PM, Jason van Zyl ja...@takari.io wrote: I'l try it before you release it. But I suggest you modernize it and by that I mean forget Maven 2.x and update it to the sisu-plexus, remove all the old crap. If you want to use the new stuff then move to a relatively modern version of Maven. If users need new capabilities then they move forward with Maven as well. We're EOL'ing Maven 2.x so I would just move forward. On Feb 22, 2014, at 10:34 AM, Benson Margulies bimargul...@gmail.com wrote: I am willing to do the work of RM'ing what we have here, since no one out there will test anything before it's released. On Sat, Feb 22, 2014 at 1:34 PM, Benson Margulies bimargul...@gmail.com wrote: On Sat, Feb 22, 2014 at 1:23 PM, Robert Scholte rfscho...@apache.org wrote: I've only changed maven-scm-manager-plexus to 1.8, and kept the rest on 1.9, such as the maven-scm-providers-standard. This brings me to the next question: Are you convinced that 1.9 will solve all the problems of the GIT users? I'm not, and I wouldn't prepare a git special-release without knowing it'll take away the GIT critical issues. I've tried to get feedback after some fixes, but didn't get the feedback I was searching for. Not I, I'm just reflecting the claims of others. Robert Op Sat, 22 Feb 2014 19:12:05 +0100 schreef Benson Margulies bimargul...@gmail.com: This, of course, does not help the people pining for the git support in 1.9. On Sat, Feb 22, 2014 at 1:10 PM, Robert Scholte rfscho...@apache.org wrote: http://svn.apache.org/r1570870 fixes the unittests on my machine. I'll have to check was has changed between SCM 1.8 and 1.8.1, but there's a serious issue here. Robert Op Sat, 22 Feb 2014 18:48:53 +0100 schreef Benson Margulies bimargul...@gmail.com: Still 2.2.1. So, in version 2.2.1, org.apache.maven.artifact.transform.DefaultArtifactTransformationManager tries to patch a list that is injected, and gets into trouble because Plexus has made the list unmodifiable. Presumably, that unmodifiability was some improvement to plexus. I guess that taking 1.5.5 of the container doesn't work with 2.2.1, and the question is how far back one needs to go (give or take making a new release of maven-artifact-manager). Or even if any of this is the solution to Robert's original problem. On Sat, Feb 22, 2014 at 12:46 PM, Igor Fedorenko i...@ifedorenko.com wrote: What version of Maven does release plugin depend on? I think DefaultArtifactTransformationManager.initialize was removed in 3.x, at least it's not present in 3.2.1 and 3.1.1. -- Regards, Igor On 2/22/2014, 12:35, Benson Margulies wrote: I'm sorry, I did mislead you. Not surprisingly, adding maven-compat did not fix the problem with the apparently unmodifiable list. On Sat, Feb 22, 2014 at 12:33 PM, Benson Margulies bimargul...@gmail.com wrote: I may have misled you, but I'll try it. Caused by: org.codehaus.plexus.component.repository.exception.ComponentLifecycleException: Error constructing component role: 'org.apache.maven.artifact.resolver.ArtifactResolver', implementation: 'org.apache.maven.artifact.resolver.DefaultArtifactResolver', role hint: 'default' at org.codehaus.plexus.component.builder.XBeanComponentBuilder.createComponentInstance(XBeanComponentBuilder.java:176) at org.codehaus.plexus.component.builder.XBeanComponentBuilder.build(XBeanComponentBuilder.java:123) at org.codehaus.plexus.component.manager.AbstractComponentManager.createComponentInstance(AbstractComponentManager.java:181) at org.codehaus.plexus.component.manager.SingletonComponentManager.getComponent(SingletonComponentManager.java:67) at
Re: Java 1.5
+1 to dump Java 5. Gary Original message From: Baptiste Mathus m...@batmat.net Date:02/22/2014 17:00 (GMT-05:00) To: Maven Developers List dev@maven.apache.org Subject: Re: Java 1.5 +1 to dump Java5 compat. In about 2 months, even Java 6 will rapidly become old. We're already using Java 1.7 at our shop, and plan to migrate to 1.8 asap. And we're really not a startup kind of company ;-). And I'm sure the features in 1.8 (compared to the ones in the previous version) is gonna accelerate the move. Sure you'll always companies where migration is said to be hard, but any move being made would be considered hard to absorb by those anyway... :) Stephen, when talking about version policy in the current context, do you mean something like any plugin could from now on be released with 1.6+ requirement, you would just have to make sure to bump the MAJOR (or only minor?) version number to acknowledge the change ? 2014-02-22 21:26 GMT+01:00 Stephen Connolly stephen.alan.conno...@gmail.com : If a plugin depends on Maven 2.2.1 through 3.1.1 then we are stuck with Java 1.5 Hence my version policy that you lot are all ignoring commenting on... No comments means I'll just put it up for a vote ;-) Sent from my iPhone On 22 Feb 2014, at 20:10, Arnaud Héritier aherit...@gmail.com wrote: ;) AFAIR for core yes. New releases (thus 3.2) should be certified 1.6+ For plugins it's another story I suppose depending of the version of maven core they are supposed to support.. — Sent from Mailbox for iPhone On Sat, Feb 22, 2014 at 9:04 PM, Jason van Zyl ja...@tesla.io wrote: Didn't we decide that everything can be 1.6? I remember because it was one of Stephen's overly long emails :-) jvz On Feb 22, 2014, at 11:02 AM, Benson Margulies bimargul...@gmail.com wrote: How much longer with this Java 1.5 business? It' a giant pain. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor ! nbsp;! dev-h...@maven.apache.org
Re: Java 1.5
On 22 February 2014 22:00, Baptiste Mathus m...@batmat.net wrote: +1 to dump Java5 compat. In about 2 months, even Java 6 will rapidly become old. We're already using Java 1.7 at our shop, and plan to migrate to 1.8 asap. And we're really not a startup kind of company ;-). And I'm sure the features in 1.8 (compared to the ones in the previous version) is gonna accelerate the move. Sure you'll always companies where migration is said to be hard, but any move being made would be considered hard to absorb by those anyway... :) Stephen, when talking about version policy in the current context, do you mean something like any plugin could from now on be released with 1.6+ requirement, you would just have to make sure to bump the MAJOR (or only minor?) version number to acknowledge the change ? Well I think that a MINOR bump suffices... but perhaps we should doc it. FWIW I would be happy to say that any JVM which is more than 12 months since being declared EOL by Oracle is one that we don't bother with... has the side effect that our next minor version can require Java 7 as a minimum... but we are now OT 2014-02-22 21:26 GMT+01:00 Stephen Connolly stephen.alan.conno...@gmail.com : If a plugin depends on Maven 2.2.1 through 3.1.1 then we are stuck with Java 1.5 Hence my version policy that you lot are all ignoring commenting on... No comments means I'll just put it up for a vote ;-) Sent from my iPhone On 22 Feb 2014, at 20:10, Arnaud Héritier aherit...@gmail.com wrote: ;) AFAIR for core yes. New releases (thus 3.2) should be certified 1.6+ For plugins it's another story I suppose depending of the version of maven core they are supposed to support.. -- Sent from Mailbox for iPhone On Sat, Feb 22, 2014 at 9:04 PM, Jason van Zyl ja...@tesla.io wrote: Didn't we decide that everything can be 1.6? I remember because it was one of Stephen's overly long emails :-) jvz On Feb 22, 2014, at 11:02 AM, Benson Margulies bimargul...@gmail.com wrote: How much longer with this Java 1.5 business? It' a giant pain. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor ! nbsp;! dev-h...@maven.apache.org
Re: A release of maven-checkstyle-plugin is coming shortly
Am 2014-02-22 00:58, schrieb Dennis Lundberg: Hi, If anyone wants to add something to the next release of the Checkstyle plugin, now would be a good time to do it, as I intend to make a release next week. If you need more time to squeeze something in, just let me know. Thanks for that notification. I have fixed several issues recently and have tested the code again -- it seems I have missed some issues which I will address shortly. Some are translation-related and some xref linking. I will update as soon as the issues have been addressed. Michael - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Releasing the release plugin
AFAIK yes we do... but if we don't then I'll need to cancel gpg 1.5 On 22 February 2014 22:40, Benson Margulies bimargul...@gmail.com wrote: I can't built the m-r-p with Java 1.5. The compiler plugin fails. Don't we have source and target set so that I can leave JAVA_HOME at 1.6 and still cut a release? On Sat, Feb 22, 2014 at 5:13 PM, Benson Margulies bimargul...@gmail.com wrote: That's my plan. Cut a release with things as they are today, though Robert's discovery suggests at least a brief delay. On Sat, Feb 22, 2014 at 3:00 PM, Jason van Zyl ja...@tesla.io wrote: If you're going to try and cut a release that works with 2.x then I wouldn't worry about updating scm. I think users on Git are also more likely to be on m3 which is where the scm issues are yes? If you want to cut a quick release for 2.x users I would try and leave as many of the existing deps alone. jvz On Feb 22, 2014, at 10:58 AM, Benson Margulies bimargul...@gmail.com wrote: Jason, I can't help suspecting that the first step in housecleaning here will be a new-tech SCM release, do you think so? On Sat, Feb 22, 2014 at 1:56 PM, Benson Margulies bimargul...@gmail.com wrote: Seems to me we might as well make one last release with what's there now, just in case it helps someone. Then clean the closet. On Sat, Feb 22, 2014 at 1:47 PM, Jason van Zyl ja...@takari.io wrote: I'l try it before you release it. But I suggest you modernize it and by that I mean forget Maven 2.x and update it to the sisu-plexus, remove all the old crap. If you want to use the new stuff then move to a relatively modern version of Maven. If users need new capabilities then they move forward with Maven as well. We're EOL'ing Maven 2.x so I would just move forward. On Feb 22, 2014, at 10:34 AM, Benson Margulies bimargul...@gmail.com wrote: I am willing to do the work of RM'ing what we have here, since no one out there will test anything before it's released. On Sat, Feb 22, 2014 at 1:34 PM, Benson Margulies bimargul...@gmail.com wrote: On Sat, Feb 22, 2014 at 1:23 PM, Robert Scholte rfscho...@apache.org wrote: I've only changed maven-scm-manager-plexus to 1.8, and kept the rest on 1.9, such as the maven-scm-providers-standard. This brings me to the next question: Are you convinced that 1.9 will solve all the problems of the GIT users? I'm not, and I wouldn't prepare a git special-release without knowing it'll take away the GIT critical issues. I've tried to get feedback after some fixes, but didn't get the feedback I was searching for. Not I, I'm just reflecting the claims of others. Robert Op Sat, 22 Feb 2014 19:12:05 +0100 schreef Benson Margulies bimargul...@gmail.com: This, of course, does not help the people pining for the git support in 1.9. On Sat, Feb 22, 2014 at 1:10 PM, Robert Scholte rfscho...@apache.org wrote: http://svn.apache.org/r1570870 fixes the unittests on my machine. I'll have to check was has changed between SCM 1.8 and 1.8.1, but there's a serious issue here. Robert Op Sat, 22 Feb 2014 18:48:53 +0100 schreef Benson Margulies bimargul...@gmail.com: Still 2.2.1. So, in version 2.2.1, org.apache.maven.artifact.transform.DefaultArtifactTransformationManager tries to patch a list that is injected, and gets into trouble because Plexus has made the list unmodifiable. Presumably, that unmodifiability was some improvement to plexus. I guess that taking 1.5.5 of the container doesn't work with 2.2.1, and the question is how far back one needs to go (give or take making a new release of maven-artifact-manager). Or even if any of this is the solution to Robert's original problem. On Sat, Feb 22, 2014 at 12:46 PM, Igor Fedorenko i...@ifedorenko.com wrote: What version of Maven does release plugin depend on? I think DefaultArtifactTransformationManager.initialize was removed in 3.x, at least it's not present in 3.2.1 and 3.1.1. -- Regards, Igor On 2/22/2014, 12:35, Benson Margulies wrote: I'm sorry, I did mislead you. Not surprisingly, adding maven-compat did not fix the problem with the apparently unmodifiable list. On Sat, Feb 22, 2014 at 12:33 PM, Benson Margulies bimargul...@gmail.com wrote: I may have misled you, but I'll try it. Caused by: org.codehaus.plexus.component.repository.exception.ComponentLifecycleException: Error constructing component role: 'org.apache.maven.artifact.resolver.ArtifactResolver', implementation: 'org.apache.maven.artifact.resolver.DefaultArtifactResolver', role hint: 'default' at org.codehaus.plexus.component.builder.XBeanComponentBuilder.createComponentInstance(XBeanComponentBuilder.java:176) at org.codehaus.plexus.component.builder.XBeanComponentBuilder.build(XBeanComponentBuilder.java:123) at
Re: Releasing the release plugin
cool! I'm grand. I cut m-gpg-p 1.5 using Java 1.7.0_51 and look at my class versions! java -jar ~/codehaus/animal-sniffer/animal-sniffer/target/animal-sniffer-1.10.jar ~/apache/maven-gpg-plugin/target/checkout/target/maven-gpg-plugin-1.5.jar 49.0 /Users/stephenc/apache/maven-gpg-plugin/target/checkout/target/maven-gpg-plugin-1.5.jar:org/apache/maven/plugin/gpg/HelpMojo.class 49.0 /Users/stephenc/apache/maven-gpg-plugin/target/checkout/target/maven-gpg-plugin-1.5.jar:org/apache/maven/plugin/gpg/GpgSigner.class 49.0 /Users/stephenc/apache/maven-gpg-plugin/target/checkout/target/maven-gpg-plugin-1.5.jar:org/apache/maven/plugin/gpg/SigningBundle.class 49.0 /Users/stephenc/apache/maven-gpg-plugin/target/checkout/target/maven-gpg-plugin-1.5.jar:org/apache/maven/plugin/gpg/AbstractGpgMojo.class 49.0 /Users/stephenc/apache/maven-gpg-plugin/target/checkout/target/maven-gpg-plugin-1.5.jar:org/apache/maven/plugin/gpg/AbstractGpgSigner.class 49.0 /Users/stephenc/apache/maven-gpg-plugin/target/checkout/target/maven-gpg-plugin-1.5.jar:org/apache/maven/plugin/gpg/AscArtifactMetadata.class 49.0 /Users/stephenc/apache/maven-gpg-plugin/target/checkout/target/maven-gpg-plugin-1.5.jar:org/apache/maven/plugin/gpg/GpgSignAttachedMojo.class 49.0 /Users/stephenc/apache/maven-gpg-plugin/target/checkout/target/maven-gpg-plugin-1.5.jar:org/apache/maven/plugin/gpg/SignAndDeployFileMojo.class 49.0 /Users/stephenc/apache/maven-gpg-plugin/target/checkout/target/maven-gpg-plugin-1.5.jar:org/apache/maven/plugin/gpg/AttachedSignedArtifact.class 49.0 /Users/stephenc/apache/maven-gpg-plugin/target/checkout/target/maven-gpg-plugin-1.5.jar:org/apache/maven/plugin/gpg/AbstractGpgSigner$MaskingThread.class On 22 February 2014 23:19, Stephen Connolly stephen.alan.conno...@gmail.com wrote: AFAIK yes we do... but if we don't then I'll need to cancel gpg 1.5 On 22 February 2014 22:40, Benson Margulies bimargul...@gmail.com wrote: I can't built the m-r-p with Java 1.5. The compiler plugin fails. Don't we have source and target set so that I can leave JAVA_HOME at 1.6 and still cut a release? On Sat, Feb 22, 2014 at 5:13 PM, Benson Margulies bimargul...@gmail.com wrote: That's my plan. Cut a release with things as they are today, though Robert's discovery suggests at least a brief delay. On Sat, Feb 22, 2014 at 3:00 PM, Jason van Zyl ja...@tesla.io wrote: If you're going to try and cut a release that works with 2.x then I wouldn't worry about updating scm. I think users on Git are also more likely to be on m3 which is where the scm issues are yes? If you want to cut a quick release for 2.x users I would try and leave as many of the existing deps alone. jvz On Feb 22, 2014, at 10:58 AM, Benson Margulies bimargul...@gmail.com wrote: Jason, I can't help suspecting that the first step in housecleaning here will be a new-tech SCM release, do you think so? On Sat, Feb 22, 2014 at 1:56 PM, Benson Margulies bimargul...@gmail.com wrote: Seems to me we might as well make one last release with what's there now, just in case it helps someone. Then clean the closet. On Sat, Feb 22, 2014 at 1:47 PM, Jason van Zyl ja...@takari.io wrote: I'l try it before you release it. But I suggest you modernize it and by that I mean forget Maven 2.x and update it to the sisu-plexus, remove all the old crap. If you want to use the new stuff then move to a relatively modern version of Maven. If users need new capabilities then they move forward with Maven as well. We're EOL'ing Maven 2.x so I would just move forward. On Feb 22, 2014, at 10:34 AM, Benson Margulies bimargul...@gmail.com wrote: I am willing to do the work of RM'ing what we have here, since no one out there will test anything before it's released. On Sat, Feb 22, 2014 at 1:34 PM, Benson Margulies bimargul...@gmail.com wrote: On Sat, Feb 22, 2014 at 1:23 PM, Robert Scholte rfscho...@apache.org wrote: I've only changed maven-scm-manager-plexus to 1.8, and kept the rest on 1.9, such as the maven-scm-providers-standard. This brings me to the next question: Are you convinced that 1.9 will solve all the problems of the GIT users? I'm not, and I wouldn't prepare a git special-release without knowing it'll take away the GIT critical issues. I've tried to get feedback after some fixes, but didn't get the feedback I was searching for. Not I, I'm just reflecting the claims of others. Robert Op Sat, 22 Feb 2014 19:12:05 +0100 schreef Benson Margulies bimargul...@gmail.com: This, of course, does not help the people pining for the git support in 1.9. On Sat, Feb 22, 2014 at 1:10 PM, Robert Scholte rfscho...@apache.org wrote: http://svn.apache.org/r1570870 fixes the unittests on my machine. I'll have to check was has changed between SCM 1.8 and 1.8.1, but there's a serious issue here. Robert Op Sat, 22 Feb 2014 18:48:53 +0100 schreef Benson Margulies
Re: Java 1.5
Ok, I promise never to poke fun if you promise never to never again use the word hump in an email to this list. On Feb 22, 2014, at 12:24 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: Somehow with my brief emails you find some misinterpretation to take a hump at! Verbose or misunderstood... You decide ;-) Sent from my iPhone On 22 Feb 2014, at 20:03, Jason van Zyl ja...@tesla.io wrote: Didn't we decide that everything can be 1.6? I remember because it was one of Stephen's overly long emails :-) jvz On Feb 22, 2014, at 11:02 AM, Benson Margulies bimargul...@gmail.com wrote: How much longer with this Java 1.5 business? It' a giant pain. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl http://twitter.com/takari_io - The modern conservative is engaged in one of man's oldest exercises in moral philosophy; that is, the search for a superior moral justification for selfishness. -- John Kenneth Galbraith
Re: Java 1.5
You are overly politically correct. I should take offence! On 22 February 2014 23:31, Jason van Zyl ja...@takari.io wrote: Ok, I promise never to poke fun if you promise never to never again use the word hump in an email to this list. On Feb 22, 2014, at 12:24 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: Somehow with my brief emails you find some misinterpretation to take a hump at! Verbose or misunderstood... You decide ;-) Sent from my iPhone On 22 Feb 2014, at 20:03, Jason van Zyl ja...@tesla.io wrote: Didn't we decide that everything can be 1.6? I remember because it was one of Stephen's overly long emails :-) jvz On Feb 22, 2014, at 11:02 AM, Benson Margulies bimargul...@gmail.com wrote: How much longer with this Java 1.5 business? It' a giant pain. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl http://twitter.com/takari_io - The modern conservative is engaged in one of man's oldest exercises in moral philosophy; that is, the search for a superior moral justification for selfishness. -- John Kenneth Galbraith
Re: Releasing the release plugin
Right, see one of my earlier posts on this. m-r-p seems to trigger a bug in Java 5, making it impossible to build it using Java 5. Having the correct source/target versions set and checking it with animal sniffer should be enough. On Sat, Feb 22, 2014 at 11:40 PM, Benson Margulies bimargul...@gmail.com wrote: I can't built the m-r-p with Java 1.5. The compiler plugin fails. Don't we have source and target set so that I can leave JAVA_HOME at 1.6 and still cut a release? On Sat, Feb 22, 2014 at 5:13 PM, Benson Margulies bimargul...@gmail.com wrote: That's my plan. Cut a release with things as they are today, though Robert's discovery suggests at least a brief delay. On Sat, Feb 22, 2014 at 3:00 PM, Jason van Zyl ja...@tesla.io wrote: If you're going to try and cut a release that works with 2.x then I wouldn't worry about updating scm. I think users on Git are also more likely to be on m3 which is where the scm issues are yes? If you want to cut a quick release for 2.x users I would try and leave as many of the existing deps alone. jvz On Feb 22, 2014, at 10:58 AM, Benson Margulies bimargul...@gmail.com wrote: Jason, I can't help suspecting that the first step in housecleaning here will be a new-tech SCM release, do you think so? On Sat, Feb 22, 2014 at 1:56 PM, Benson Margulies bimargul...@gmail.com wrote: Seems to me we might as well make one last release with what's there now, just in case it helps someone. Then clean the closet. On Sat, Feb 22, 2014 at 1:47 PM, Jason van Zyl ja...@takari.io wrote: I'l try it before you release it. But I suggest you modernize it and by that I mean forget Maven 2.x and update it to the sisu-plexus, remove all the old crap. If you want to use the new stuff then move to a relatively modern version of Maven. If users need new capabilities then they move forward with Maven as well. We're EOL'ing Maven 2.x so I would just move forward. On Feb 22, 2014, at 10:34 AM, Benson Margulies bimargul...@gmail.com wrote: I am willing to do the work of RM'ing what we have here, since no one out there will test anything before it's released. On Sat, Feb 22, 2014 at 1:34 PM, Benson Margulies bimargul...@gmail.com wrote: On Sat, Feb 22, 2014 at 1:23 PM, Robert Scholte rfscho...@apache.org wrote: I've only changed maven-scm-manager-plexus to 1.8, and kept the rest on 1.9, such as the maven-scm-providers-standard. This brings me to the next question: Are you convinced that 1.9 will solve all the problems of the GIT users? I'm not, and I wouldn't prepare a git special-release without knowing it'll take away the GIT critical issues. I've tried to get feedback after some fixes, but didn't get the feedback I was searching for. Not I, I'm just reflecting the claims of others. Robert Op Sat, 22 Feb 2014 19:12:05 +0100 schreef Benson Margulies bimargul...@gmail.com: This, of course, does not help the people pining for the git support in 1.9. On Sat, Feb 22, 2014 at 1:10 PM, Robert Scholte rfscho...@apache.org wrote: http://svn.apache.org/r1570870 fixes the unittests on my machine. I'll have to check was has changed between SCM 1.8 and 1.8.1, but there's a serious issue here. Robert Op Sat, 22 Feb 2014 18:48:53 +0100 schreef Benson Margulies bimargul...@gmail.com: Still 2.2.1. So, in version 2.2.1, org.apache.maven.artifact.transform.DefaultArtifactTransformationManager tries to patch a list that is injected, and gets into trouble because Plexus has made the list unmodifiable. Presumably, that unmodifiability was some improvement to plexus. I guess that taking 1.5.5 of the container doesn't work with 2.2.1, and the question is how far back one needs to go (give or take making a new release of maven-artifact-manager). Or even if any of this is the solution to Robert's original problem. On Sat, Feb 22, 2014 at 12:46 PM, Igor Fedorenko i...@ifedorenko.com wrote: What version of Maven does release plugin depend on? I think DefaultArtifactTransformationManager.initialize was removed in 3.x, at least it's not present in 3.2.1 and 3.1.1. -- Regards, Igor On 2/22/2014, 12:35, Benson Margulies wrote: I'm sorry, I did mislead you. Not surprisingly, adding maven-compat did not fix the problem with the apparently unmodifiable list. On Sat, Feb 22, 2014 at 12:33 PM, Benson Margulies bimargul...@gmail.com wrote: I may have misled you, but I'll try it. Caused by: org.codehaus.plexus.component.repository.exception.ComponentLifecycleException: Error constructing component role: 'org.apache.maven.artifact.resolver.ArtifactResolver', implementation: 'org.apache.maven.artifact.resolver.DefaultArtifactResolver', role hint: 'default' at org.codehaus.plexus.component.builder.XBeanComponentBuilder.createComponentInstance(XBeanComponentBuilder.java:176) at
Sonatype plugin question?
I *think* the sonatype folk went home for weekend so I'll ask maven gurus Close to getting a plugin working but when i start wrapper.exe the wrapper.log displays this error: The following plugins were processed: jvm 1| ... org.sonatype.nexus.plugins:stagingrules-nexus-plugin:1.0-SNAPSHOT :: action=ACTIVATE result=BROKEN jvm 1|Reason: Plugin artifact com.sonatype.nexus:nexus-core:2.7.0::jar not found! Ideas on where com.sonatype.nexus:nexus-core:2.7.0::jar should be located? local repo? some undisclosed maven repo? classpath? HELP! Martin
Re: Java 1.5
It's not political correctness (I've never been accused of that before), it's just self interest in protecting myself against unintended imagery... On Feb 22, 2014, at 3:31 PM, Jason van Zyl ja...@takari.io wrote: Ok, I promise never to poke fun if you promise never to never again use the word hump in an email to this list. On Feb 22, 2014, at 12:24 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: Somehow with my brief emails you find some misinterpretation to take a hump at! Verbose or misunderstood... You decide ;-) Sent from my iPhone On 22 Feb 2014, at 20:03, Jason van Zyl ja...@tesla.io wrote: Didn't we decide that everything can be 1.6? I remember because it was one of Stephen's overly long emails :-) jvz On Feb 22, 2014, at 11:02 AM, Benson Margulies bimargul...@gmail.com wrote: How much longer with this Java 1.5 business? It' a giant pain. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl http://twitter.com/takari_io - The modern conservative is engaged in one of man's oldest exercises in moral philosophy; that is, the search for a superior moral justification for selfishness. -- John Kenneth Galbraith Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl http://twitter.com/takari_io - Be not afraid of growing slowly, be only afraid of standing still. -- Chinese Proverb
Re: Sonatype plugin question?
I think this message comes from a Nexus server, and the plugin refers to Nexus plugin running on the server. Almost looks like a broken Nexus installation, but it's been some time since I last looked at Nexus. -- Regards, Igor On 2/22/2014, 19:08, Martin Gainty wrote: I *think* the sonatype folk went home for weekend so I'll ask maven gurus Close to getting a plugin working but when i start wrapper.exe the wrapper.log displays this error: The following plugins were processed: jvm 1| ... org.sonatype.nexus.plugins:stagingrules-nexus-plugin:1.0-SNAPSHOT :: action=ACTIVATE result=BROKEN jvm 1|Reason: Plugin artifact com.sonatype.nexus:nexus-core:2.7.0::jar not found! Ideas on where com.sonatype.nexus:nexus-core:2.7.0::jar should be located? local repo? some undisclosed maven repo? classpath? HELP! Martin - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
RE: Sonatype plugin question?
I wrote and installed a quick and dirty sonatype plugin My Nexus OpenSource distro that Im testing against is 2.8.0-SNAPSHOT my plugin examples came from 2.7.0 If Monday am comes and Im calling no joy... i'll revert nexus back to 2.7.0 and test on that I guess Sonatype folk are is in Russia or watching the Olympics Thanks Igor! Martin- Date: Sat, 22 Feb 2014 19:23:08 -0500 From: i...@ifedorenko.com To: dev@maven.apache.org Subject: Re: Sonatype plugin question? I think this message comes from a Nexus server, and the plugin refers to Nexus plugin running on the server. Almost looks like a broken Nexus installation, but it's been some time since I last looked at Nexus. -- Regards, Igor On 2/22/2014, 19:08, Martin Gainty wrote: I *think* the sonatype folk went home for weekend so I'll ask maven gurus Close to getting a plugin working but when i start wrapper.exe the wrapper.log displays this error: The following plugins were processed: jvm 1 | ... org.sonatype.nexus.plugins:stagingrules-nexus-plugin:1.0-SNAPSHOT :: action=ACTIVATE result=BROKEN jvm 1 | Reason: Plugin artifact com.sonatype.nexus:nexus-core:2.7.0::jar not found! Ideas on where com.sonatype.nexus:nexus-core:2.7.0::jar should be located? local repo? some undisclosed maven repo? classpath? HELP! Martin - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Sonatype plugin question?
On 23 Feb 2014, at 00:08, Martin Gainty mgai...@hotmail.com wrote: I *think* the sonatype folk went home for weekend so I'll ask maven gurus Odd assumption, why didn’t you at least try asking this question on nexus-user or nexus-dev? Close to getting a plugin working but when i start wrapper.exe the wrapper.log displays this error: The following plugins were processed: jvm 1| ... org.sonatype.nexus.plugins:stagingrules-nexus-plugin:1.0-SNAPSHOT :: action=ACTIVATE result=BROKEN Is this your own plugin? You should ideally choose a groupId that matches your organization/company jvm 1|Reason: Plugin artifact com.sonatype.nexus:nexus-core:2.7.0::jar not found! Looks like your pom.xml has a bad dependency - nexus-core has a groupId of org.sonatype.nexus and should be a provided dependency In fact you should really just depend on nexus-plugin-api as explained in http://books.sonatype.com/nexus-book/reference/plugdev.html Ideas on where com.sonatype.nexus:nexus-core:2.7.0::jar should be located? local repo? some undisclosed maven repo? classpath? HELP! Best way to get help is to ask this on either of the nexus mailing lists (http://www.sonatype.org/nexus/participate) - paste a copy of your plugin pom.xml Martin - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: maven-acr-plugin - plugins list page
Hi, it does appear, but is listed as app-client instead of acr perhaps name in the list should be updated because it's not easy to figure out that app-client == acr Regards, Hervé Le jeudi 20 février 2014 00:01:39 Karl Heinz Marbaise a écrit : Hi, so after taken a look into SVN it looks a little bit strange to me. The entry for the maven-acr-plugin has been added in r1087343 which is long time a go but the question is why does not appear on the sites ? Kind regards Karl Heinz Marbaise - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
RE: Sonatype plugin question?
wondering where nexus is looking to resolve dependencies? I'll try scopeprovided/scope for nexus-core (re)posted to nexus-...@sonatype.org Thanks Stewart Martin Subject: Re: Sonatype plugin question? From: mccu...@gmail.com Date: Sun, 23 Feb 2014 00:37:17 + To: dev@maven.apache.org On 23 Feb 2014, at 00:08, Martin Gainty mgai...@hotmail.com wrote: I *think* the sonatype folk went home for weekend so I'll ask maven gurus Odd assumption, why didn’t you at least try asking this question on nexus-user or nexus-dev? Close to getting a plugin working but when i start wrapper.exe the wrapper.log displays this error: The following plugins were processed: jvm 1 | ... org.sonatype.nexus.plugins:stagingrules-nexus-plugin:1.0-SNAPSHOT :: action=ACTIVATE result=BROKEN Is this your own plugin? You should ideally choose a groupId that matches your organization/company jvm 1 | Reason: Plugin artifact com.sonatype.nexus:nexus-core:2.7.0::jar not found! Looks like your pom.xml has a bad dependency - nexus-core has a groupId of org.sonatype.nexus and should be a provided dependency In fact you should really just depend on nexus-plugin-api as explained in http://books.sonatype.com/nexus-book/reference/plugdev.html Ideas on where com.sonatype.nexus:nexus-core:2.7.0::jar should be located? local repo? some undisclosed maven repo? classpath? HELP! Best way to get help is to ask this on either of the nexus mailing lists (http://www.sonatype.org/nexus/participate) - paste a copy of your plugin pom.xml Martin - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Site plugin
the site plugin itself works but the site plugin launches a lot of other plugins, like remote resources plugin which is apparently failing here did you try to update remote resources to 1.5, like Dennis proposed? Regards, Hervé Le samedi 22 février 2014 10:03:14 Jason van Zyl a écrit : That version of the site plugin we have configured just doesn't work with newer versions of Maven. I ran the command with Maven 3.0.4 and it works. We are a long, long, long way from push button releases. On Feb 22, 2014, at 1:54 AM, Dennis Lundberg denn...@apache.org wrote: Hi Jason, Looking at the stack trace it seems to be the remote resources plugin that is throwing an NPE. Didn't you release 1.5 of that plugin because of issues with core? Your build is using 1.4... -- Dennis Lundberg Den 22 feb 2014 05:30 skrev Jason van Zyl ja...@takari.io: Not sure who looks after the site plugin these days but I can't run the staging part to copy it over to the production site: In the release checkout I ran: mvn -Preporting site site:stage and got: https://gist.github.com/jvanzyl/9148731 I'll continue on with the rest of the work but I will release tomorrow regardless. I don't have time to debug the site plugin. Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl http://twitter.com/takari_io - Simplex sigillum veri. (Simplicity is the seal of truth.) Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl http://twitter.com/takari_io - We know what we are, but know not what we may be. -- Shakespeare
