Issues with getting 1.1-SNAPSHOT started
I hope addressing this to continuum-dev is correct. I've been using 1.0.3 for some time now, but thought I'd check out 1.1-SNAPSHOT just to see what good things I can look forward to, or even to start using it if it's stable. I've build it and got the war file. I'm trying to deploy this on my build server using winstone as the container. First off, is there any reason why winstone isn't a good choice for a basic container into which I can deploy this war? If it's not, what's a good alternative? Are there any notes I can look at re configuration? I'm getting the following. Thanks in advance, Ian [Winstone 2007/04/16 15:30:50] - Beginning extraction from war file [webapp 2007/04/16 15:30:53] - Loading plexus context properties from: '/WEB-INF/plexus.properties' [webapp 2007/04/16 15:30:53] - Could not load plexus context properties from: '/WEB-INF/plexus.properties' log4j:ERROR setFile(null,true) call failed. java.io.FileNotFoundException: /logs/continuum.log (No such file or directory) at java.io.FileOutputStream.openAppend(Native Method) at java.io.FileOutputStream.init(FileOutputStream.java:177) at java.io.FileOutputStream.init(FileOutputStream.java:102) at org.apache.log4j.FileAppender.setFile(FileAppender.java:272) at org.apache.log4j.FileAppender.activateOptions(FileAppender.java:151) at org.apache.log4j.DailyRollingFileAppender.activateOptions(DailyRollingFi leAppender.java:206) at org.apache.log4j.config.PropertySetter.activate(PropertySetter.java:247) at org.apache.log4j.config.PropertySetter.setProperties(PropertySetter.java :123) at org.apache.log4j.config.PropertySetter.setProperties(PropertySetter.java :87) at org.apache.log4j.PropertyConfigurator.parseAppender(PropertyConfigurator .java:645) at org.apache.log4j.PropertyConfigurator.parseCategory(PropertyConfigurator .java:603) at org.apache.log4j.PropertyConfigurator.configureRootCategory(PropertyConf igurator.java:500) at org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.j ava:406) at org.apache.log4j.PropertyConfigurator.configure(PropertyConfigurator.jav a:340) at org.codehaus.plexus.logging.log4j.Log4JLoggerManager.start(Log4JLoggerMa nager.java:299) at org.codehaus.plexus.personality.plexus.lifecycle.phase.StartPhase.execut e(StartPhase.java:33) at org.codehaus.plexus.lifecycle.AbstractLifecycleHandler.start(AbstractLif ecycleHandler.java:128) at org.codehaus.plexus.component.manager.AbstractComponentManager.startComp onentLifecycle(AbstractComponentManager.java:142) at org.codehaus.plexus.component.manager.AbstractComponentManager.createCom ponentInstance(AbstractComponentManager.java:132) at org.codehaus.plexus.component.manager.ClassicSingletonComponentManager.g etComponent(ClassicSingletonComponentManager.java:90) at org.codehaus.plexus.DefaultComponentLookupManager.lookup(DefaultComponen tLookupManager.java:147) at org.codehaus.plexus.DefaultComponentLookupManager.lookupMap(DefaultCompo nentLookupManager.java:199) at org.codehaus.plexus.DefaultPlexusContainer.lookupMap(DefaultPlexusContai ner.java:309) at org.codehaus.plexus.DefaultPlexusContainer.lookupMap(DefaultPlexusContai ner.java:303) at org.codehaus.plexus.container.initialization.InitializeLoggerManagerPhas e.initializeCoreComponent(InitializeLoggerManagerPhase.java:47) at org.codehaus.plexus.container.initialization.AbstractCoreComponentInitia lizationPhase.execute(AbstractCoreComponentInitializationPhase.java:37) at org.codehaus.plexus.DefaultPlexusContainer.initializePhases(DefaultPlexu sContainer.java:886) at org.codehaus.plexus.DefaultPlexusContainer.initialize(DefaultPlexusConta iner.java:834) at org.codehaus.plexus.DefaultPlexusContainer.construct(DefaultPlexusContai ner.java:811) at org.codehaus.plexus.DefaultPlexusContainer.init(DefaultPlexusContainer .java:222) at org.codehaus.plexus.DefaultPlexusContainer.init(DefaultPlexusContainer .java:260) at org.codehaus.plexus.xwork.PlexusLifecycleListener.contextInitialized(Ple xusLifecycleListener.java:76) at winstone.WebAppConfiguration.init(WebAppConfiguration.java:885) at winstone.HostConfiguration.initWebApp(HostConfiguration.java:131) at winstone.HostConfiguration.init(HostConfiguration.java:73) at winstone.HostGroup.initHost(HostGroup.java:85) at winstone.HostGroup.init(HostGroup.java:45) at winstone.Launcher.init(Launcher.java:194) at winstone.Launcher.main(Launcher.java:389) -- This e-mail is confidential and the information contained in it may be privileged. It should not be read, copied or used by anyone other than the intended recipient. If you have received it in error, please contact the sender immediately by telephoning +44 (0)20 7623 8000 or by return email, and
RE: Issues with getting 1.1-SNAPSHOT started
Thanks Emmanuel, I played with jetty and ended up with the same exception there, so no reason to believe that winstone is behaving differently. I tried -Dappserver.base=., but that didn't have any noticable effect. I'm now going to try David Goemans' suggestion. Regards, Ian -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: 16 April 2007 15:55 To: continuum-dev@maven.apache.org Subject: Re: Issues with getting 1.1-SNAPSHOT started winstone isn't tested yet, but if you can run continuum with it, please update the wiki. About the exception, you need to start your container with appserver.base system property, Continuum use it for some paths like the log file. You can use what you want for this property, it's only need to be a valid directory. Emmanuel Orford, Ian a écrit : I hope addressing this to continuum-dev is correct. I've been using 1.0.3 for some time now, but thought I'd check out 1.1-SNAPSHOT just to see what good things I can look forward to, or even to start using it if it's stable. I've build it and got the war file. I'm trying to deploy this on my build server using winstone as the container. First off, is there any reason why winstone isn't a good choice for a basic container into which I can deploy this war? If it's not, what's a good alternative? Are there any notes I can look at re configuration? I'm getting the following. Thanks in advance, Ian [Winstone 2007/04/16 15:30:50] - Beginning extraction from war file [webapp 2007/04/16 15:30:53] - Loading plexus context properties from: '/WEB-INF/plexus.properties' [webapp 2007/04/16 15:30:53] - Could not load plexus context properties from: '/WEB-INF/plexus.properties' log4j:ERROR setFile(null,true) call failed. java.io.FileNotFoundException: /logs/continuum.log (No such file or directory) at java.io.FileOutputStream.openAppend(Native Method) at java.io.FileOutputStream.init(FileOutputStream.java:177) at java.io.FileOutputStream.init(FileOutputStream.java:102) at org.apache.log4j.FileAppender.setFile(FileAppender.java:272) at org.apache.log4j.FileAppender.activateOptions(FileAppender.java:151) at org.apache.log4j.DailyRollingFileAppender.activateOptions(DailyRolling Fi leAppender.java:206) at org.apache.log4j.config.PropertySetter.activate(PropertySetter .java:247) at org.apache.log4j.config.PropertySetter.setProperties(PropertySetter.ja va :123) at org.apache.log4j.config.PropertySetter.setProperties(PropertySetter.ja va :87) at org.apache.log4j.PropertyConfigurator.parseAppender(PropertyConfigurat or .java:645) at org.apache.log4j.PropertyConfigurator.parseCategory(PropertyConfigurat or .java:603) at org.apache.log4j.PropertyConfigurator.configureRootCategory(PropertyCo nf igurator.java:500) at org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator .j ava:406) at org.apache.log4j.PropertyConfigurator.configure(PropertyConfigurator.j av a:340) at org.codehaus.plexus.logging.log4j.Log4JLoggerManager.start(Log4JLogger Ma nager.java:299) at org.codehaus.plexus.personality.plexus.lifecycle.phase.StartPhase.exec ut e(StartPhase.java:33) at org.codehaus.plexus.lifecycle.AbstractLifecycleHandler.start(AbstractL if ecycleHandler.java:128) at org.codehaus.plexus.component.manager.AbstractComponentManager.startCo mp onentLifecycle(AbstractComponentManager.java:142) at org.codehaus.plexus.component.manager.AbstractComponentManager.createC om ponentInstance(AbstractComponentManager.java:132) at org.codehaus.plexus.component.manager.ClassicSingletonComponentManager .g etComponent(ClassicSingletonComponentManager.java:90) at org.codehaus.plexus.DefaultComponentLookupManager.lookup(DefaultCompon en tLookupManager.java:147) at org.codehaus.plexus.DefaultComponentLookupManager.lookupMap(DefaultCom po nentLookupManager.java:199) at org.codehaus.plexus.DefaultPlexusContainer.lookupMap(DefaultPlexusCont ai ner.java:309) at org.codehaus.plexus.DefaultPlexusContainer.lookupMap(DefaultPlexusCont ai ner.java:303) at org.codehaus.plexus.container.initialization.InitializeLoggerManagerPh as e.initializeCoreComponent(InitializeLoggerManagerPhase.java:47) at org.codehaus.plexus.container.initialization.AbstractCoreComponentInit ia lizationPhase.execute(AbstractCoreComponentInitializationPhase .java:37) at org.codehaus.plexus.DefaultPlexusContainer.initializePhases(DefaultPle xu sContainer.java:886) at
Re: Issues with getting 1.1-SNAPSHOT started
I think you need to create the log dir and conf dir in the directory used in appserver.base system property Emmanuel Orford, Ian a écrit : Thanks Emmanuel, I played with jetty and ended up with the same exception there, so no reason to believe that winstone is behaving differently. I tried -Dappserver.base=., but that didn't have any noticable effect. I'm now going to try David Goemans' suggestion. Regards, Ian -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: 16 April 2007 15:55 To: continuum-dev@maven.apache.org Subject: Re: Issues with getting 1.1-SNAPSHOT started winstone isn't tested yet, but if you can run continuum with it, please update the wiki. About the exception, you need to start your container with appserver.base system property, Continuum use it for some paths like the log file. You can use what you want for this property, it's only need to be a valid directory. Emmanuel Orford, Ian a écrit : I hope addressing this to continuum-dev is correct. I've been using 1.0.3 for some time now, but thought I'd check out 1.1-SNAPSHOT just to see what good things I can look forward to, or even to start using it if it's stable. I've build it and got the war file. I'm trying to deploy this on my build server using winstone as the container. First off, is there any reason why winstone isn't a good choice for a basic container into which I can deploy this war? If it's not, what's a good alternative? Are there any notes I can look at re configuration? I'm getting the following. Thanks in advance, Ian [Winstone 2007/04/16 15:30:50] - Beginning extraction from war file [webapp 2007/04/16 15:30:53] - Loading plexus context properties from: '/WEB-INF/plexus.properties' [webapp 2007/04/16 15:30:53] - Could not load plexus context properties from: '/WEB-INF/plexus.properties' log4j:ERROR setFile(null,true) call failed. java.io.FileNotFoundException: /logs/continuum.log (No such file or directory) at java.io.FileOutputStream.openAppend(Native Method) at java.io.FileOutputStream.init(FileOutputStream.java:177) at java.io.FileOutputStream.init(FileOutputStream.java:102) at org.apache.log4j.FileAppender.setFile(FileAppender.java:272) at org.apache.log4j.FileAppender.activateOptions(FileAppender.java:151) at org.apache.log4j.DailyRollingFileAppender.activateOptions(DailyRolling Fi leAppender.java:206) at org.apache.log4j.config.PropertySetter.activate(PropertySetter .java:247) at org.apache.log4j.config.PropertySetter.setProperties(PropertySetter.ja va :123) at org.apache.log4j.config.PropertySetter.setProperties(PropertySetter.ja va :87) at org.apache.log4j.PropertyConfigurator.parseAppender(PropertyConfigurat or .java:645) at org.apache.log4j.PropertyConfigurator.parseCategory(PropertyConfigurat or .java:603) at org.apache.log4j.PropertyConfigurator.configureRootCategory(PropertyCo nf igurator.java:500) at org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator .j ava:406) at org.apache.log4j.PropertyConfigurator.configure(PropertyConfigurator.j av a:340) at org.codehaus.plexus.logging.log4j.Log4JLoggerManager.start(Log4JLogger Ma nager.java:299) at org.codehaus.plexus.personality.plexus.lifecycle.phase.StartPhase.exec ut e(StartPhase.java:33) at org.codehaus.plexus.lifecycle.AbstractLifecycleHandler.start(AbstractL if ecycleHandler.java:128) at org.codehaus.plexus.component.manager.AbstractComponentManager.startCo mp onentLifecycle(AbstractComponentManager.java:142) at org.codehaus.plexus.component.manager.AbstractComponentManager.createC om ponentInstance(AbstractComponentManager.java:132) at org.codehaus.plexus.component.manager.ClassicSingletonComponentManager .g etComponent(ClassicSingletonComponentManager.java:90) at org.codehaus.plexus.DefaultComponentLookupManager.lookup(DefaultCompon en tLookupManager.java:147) at org.codehaus.plexus.DefaultComponentLookupManager.lookupMap(DefaultCom po nentLookupManager.java:199) at org.codehaus.plexus.DefaultPlexusContainer.lookupMap(DefaultPlexusCont ai ner.java:309) at org.codehaus.plexus.DefaultPlexusContainer.lookupMap(DefaultPlexusCont ai ner.java:303) at org.codehaus.plexus.container.initialization.InitializeLoggerManagerPh as e.initializeCoreComponent(InitializeLoggerManagerPhase.java:47) at org.codehaus.plexus.container.initialization.AbstractCoreComponentInit ia lizationPhase.execute(AbstractCoreComponentInitializationPhase .java:37) at org.codehaus.plexus.DefaultPlexusContainer.initializePhases(DefaultPle xu sContainer.java:886) at org.codehaus.plexus.DefaultPlexusContainer.initialize(DefaultPlexusCon ta iner.java:834) at
RE: Issues with getting 1.1-SNAPSHOT started
I guess this should start up out of the box right? I hate to paste long and boring stack traces, but here goes Thanks again for any suggestions. Ian INFO: ** FATAL ERROR STARTING UP PLEXUS-WEBWORK INTEGRATION ** Looks like the Plexus listener was not configured for your web app! You need to add the following to web.xml: listener listener-classorg.codehaus.plexus.xwork.PlexusLifecycleListener/liste ner-class /listener [ERROR] Error while deploying appserver continuum-plexus-application-1.1-SNAPSHOT.jar. org.codehaus.plexus.appserver.ApplicationServerException: Error in the app server lifecycle post-app-container-init-service-call phase. at org.codehaus.plexus.appserver.application.deploy.DefaultApplicationDeplo yer.deployJar(DefaultApplicationDeployer.java:119) at org.codehaus.plexus.appserver.application.deploy.DefaultApplicationDeplo yer.deploy(DefaultApplicationDeployer.java:88) at org.codehaus.plexus.appserver.lifecycle.phase.ApplicationDeploymentPhase $1.onJarDiscovered(ApplicationDeploymentPhase.java:44) at org.codehaus.plexus.appserver.supervisor.DefaultSupervisor.scanDirectory (DefaultSupervisor.java:100) at org.codehaus.plexus.appserver.supervisor.DefaultSupervisor.scan(DefaultS upervisor.java:73) at org.codehaus.plexus.appserver.lifecycle.phase.ApplicationDeploymentPhase .execute(ApplicationDeploymentPhase.java:58) at org.codehaus.plexus.appserver.DefaultApplicationServer.start(DefaultAppl icationServer.java:218) at org.codehaus.plexus.personality.plexus.lifecycle.phase.StartPhase.execut e(StartPhase.java:33) at org.codehaus.plexus.lifecycle.AbstractLifecycleHandler.start(AbstractLif ecycleHandler.java:128) at org.codehaus.plexus.component.manager.AbstractComponentManager.startComp onentLifecycle(AbstractComponentManager.java:142) at org.codehaus.plexus.component.manager.AbstractComponentManager.createCom ponentInstance(AbstractComponentManager.java:132) at org.codehaus.plexus.component.manager.ClassicSingletonComponentManager.g etComponent(ClassicSingletonComponentManager.java:90) at org.codehaus.plexus.DefaultComponentLookupManager.lookup(DefaultComponen tLookupManager.java:147) at org.codehaus.plexus.DefaultComponentLookupManager.lookup(DefaultComponen tLookupManager.java:69) at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer .java:297) at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer .java:291) at org.codehaus.plexus.appserver.PlexusApplicationHost.start(PlexusApplicat ionHost.java:155) at org.codehaus.plexus.appserver.PlexusApplicationHost.start(PlexusApplicat ionHost.java:85) at org.codehaus.plexus.appserver.PlexusApplicationHost.main(PlexusApplicati onHost.java:289) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav a:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Impl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launche r.java:289) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:2 29) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launc her.java:408) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:351 ) Caused by: org.codehaus.plexus.appserver.application.deploy.lifecycle.AppDeployment Exception: Error calling service in pre-app init phase. at org.codehaus.plexus.appserver.application.deploy.lifecycle.phase.AfterAp pStartServiceSetupPhase.execute(AfterAppStartServiceSetupPhase.java:32) at org.codehaus.plexus.appserver.application.deploy.DefaultApplicationDeplo yer.deployJar(DefaultApplicationDeployer.java:107) ... 26 more Caused by: org.codehaus.plexus.appserver.service.PlexusServiceException: Error while starting the context /continuum at org.codehaus.plexus.service.jetty.JettyPlexusService.afterApplicationSta rt(JettyPlexusService.java:252) at org.codehaus.plexus.appserver.application.deploy.lifecycle.phase.AfterAp pStartServiceSetupPhase.execute(AfterAppStartServiceSetupPhase.java:28) ... 27 more Caused by: org.codehaus.plexus.jetty.ServletContainerException: Error while starting the context /continuum at org.codehaus.plexus.jetty.AbstractJettyServletContainer.startApplication (AbstractJettyServletContainer.java:213) at org.codehaus.plexus.service.jetty.JettyPlexusService.afterApplicationSta rt(JettyPlexusService.java:248) ... 28 more Caused by: java.lang.RuntimeException: org.codehaus.plexus.PlexusContainerException: Error initializaing container in org.codehaus.plexus.container.initialization.StartLoadOnStartComponentsP [EMAIL PROTECTED]
Re: Issues with getting 1.1-SNAPSHOT started
What is the version you try? It seems a jar is missing : java.lang.NoClassDefFoundError: org/jdom/Content Emmanuel Orford, Ian a écrit : I guess this should start up out of the box right? I hate to paste long and boring stack traces, but here goes Thanks again for any suggestions. Ian INFO: ** FATAL ERROR STARTING UP PLEXUS-WEBWORK INTEGRATION ** Looks like the Plexus listener was not configured for your web app! You need to add the following to web.xml: listener listener-classorg.codehaus.plexus.xwork.PlexusLifecycleListener/liste ner-class /listener [ERROR] Error while deploying appserver continuum-plexus-application-1.1-SNAPSHOT.jar. org.codehaus.plexus.appserver.ApplicationServerException: Error in the app server lifecycle post-app-container-init-service-call phase. at org.codehaus.plexus.appserver.application.deploy.DefaultApplicationDeplo yer.deployJar(DefaultApplicationDeployer.java:119) at org.codehaus.plexus.appserver.application.deploy.DefaultApplicationDeplo yer.deploy(DefaultApplicationDeployer.java:88) at org.codehaus.plexus.appserver.lifecycle.phase.ApplicationDeploymentPhase $1.onJarDiscovered(ApplicationDeploymentPhase.java:44) at org.codehaus.plexus.appserver.supervisor.DefaultSupervisor.scanDirectory (DefaultSupervisor.java:100) at org.codehaus.plexus.appserver.supervisor.DefaultSupervisor.scan(DefaultS upervisor.java:73) at org.codehaus.plexus.appserver.lifecycle.phase.ApplicationDeploymentPhase .execute(ApplicationDeploymentPhase.java:58) at org.codehaus.plexus.appserver.DefaultApplicationServer.start(DefaultAppl icationServer.java:218) at org.codehaus.plexus.personality.plexus.lifecycle.phase.StartPhase.execut e(StartPhase.java:33) at org.codehaus.plexus.lifecycle.AbstractLifecycleHandler.start(AbstractLif ecycleHandler.java:128) at org.codehaus.plexus.component.manager.AbstractComponentManager.startComp onentLifecycle(AbstractComponentManager.java:142) at org.codehaus.plexus.component.manager.AbstractComponentManager.createCom ponentInstance(AbstractComponentManager.java:132) at org.codehaus.plexus.component.manager.ClassicSingletonComponentManager.g etComponent(ClassicSingletonComponentManager.java:90) at org.codehaus.plexus.DefaultComponentLookupManager.lookup(DefaultComponen tLookupManager.java:147) at org.codehaus.plexus.DefaultComponentLookupManager.lookup(DefaultComponen tLookupManager.java:69) at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer .java:297) at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer .java:291) at org.codehaus.plexus.appserver.PlexusApplicationHost.start(PlexusApplicat ionHost.java:155) at org.codehaus.plexus.appserver.PlexusApplicationHost.start(PlexusApplicat ionHost.java:85) at org.codehaus.plexus.appserver.PlexusApplicationHost.main(PlexusApplicati onHost.java:289) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav a:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Impl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launche r.java:289) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:2 29) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launc her.java:408) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:351 ) Caused by: org.codehaus.plexus.appserver.application.deploy.lifecycle.AppDeployment Exception: Error calling service in pre-app init phase. at org.codehaus.plexus.appserver.application.deploy.lifecycle.phase.AfterAp pStartServiceSetupPhase.execute(AfterAppStartServiceSetupPhase.java:32) at org.codehaus.plexus.appserver.application.deploy.DefaultApplicationDeplo yer.deployJar(DefaultApplicationDeployer.java:107) ... 26 more Caused by: org.codehaus.plexus.appserver.service.PlexusServiceException: Error while starting the context /continuum at org.codehaus.plexus.service.jetty.JettyPlexusService.afterApplicationSta rt(JettyPlexusService.java:252) at org.codehaus.plexus.appserver.application.deploy.lifecycle.phase.AfterAp pStartServiceSetupPhase.execute(AfterAppStartServiceSetupPhase.java:28) ... 27 more Caused by: org.codehaus.plexus.jetty.ServletContainerException: Error while starting the context /continuum at org.codehaus.plexus.jetty.AbstractJettyServletContainer.startApplication (AbstractJettyServletContainer.java:213) at org.codehaus.plexus.service.jetty.JettyPlexusService.afterApplicationSta rt(JettyPlexusService.java:248) ... 28 more Caused by: java.lang.RuntimeException:
Re: [vote] Release maven-developer-activity-plugin and maven-file-activity-plugin 1.6.1 for maven 1.X
+1 On 15 Apr 07, at 8:41 PM 15 Apr 07, Arnaud HERITIER wrote: Hi, Those two plugins have a similar fix and weren't release for several months (more than 1 year in fact). Changes : http://people.apache.org/~aheritier/staging-sites/m1-plugins/ maven-1.x/plugins/developer-activity/changes- report.html#Release1_6_1-SNAPSHOThttp://people.apache.org/% 7Eaheritier/staging-sites/m1-plugins/maven-1.x/plugins/site/changes- report.html#Release1_7_2-SNAPSHOT http://people.apache.org/~aheritier/staging-sites/m1-plugins/ maven-1.x/plugins/file-activity/changes-report.html#Release1_6_1- SNAPSHOThttp://people.apache.org/%7Eaheritier/staging-sites/m1- plugins/maven-1.x/plugins/site/changes-report.html#Release1_7_2- SNAPSHOT http://people.apache.org/%7Eaheritier/staging-sites/m1-plugins/ maven-1.x/plugins/site/changes-report.html#Release1_7_2-SNAPSHOT Staging sites : http://people.apache.org/~aheritier/staging-sites/m1-plugins/ maven-1.x/plugins/developer-activity/http://people.apache.org/% 7Eaheritier/staging-sites/m1-plugins/maven-1.x/plugins/site/ http://people.apache.org/~aheritier/staging-sites/m1-plugins/ maven-1.x/plugins/file-activity/http://people.apache.org/% 7Eaheritier/staging-sites/m1-plugins/maven-1.x/plugins/site/ Download : maven plugin:download -Dmaven.repo.remote=http://people.apache.org/ repo/ m1 -snapshot-repository/,http://repo1.maven.org/maven -DgroupId=maven -DartifactId=maven-developer-activity-plugin -Dversion=1.6.1-SNAPSHOT maven plugin:download -Dmaven.repo.remote=http://people.apache.org/ repo/ m1 -snapshot-repository/,http://repo1.maven.org/maven -DgroupId=maven -DartifactId=maven-file-activity-plugin -Dversion=1.6.1-SNAPSHOT +1 from me, 72h to vote Cheers, - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] Release maven-announcement-plugin 1.4.1 for maven 1.X
+1 On 15 Apr 07, at 8:42 PM 15 Apr 07, Arnaud HERITIER wrote: On 16/04/07, Arnaud HERITIER [EMAIL PROTECTED] wrote: Hi, In the logic to try to release often I propose to release the announcement which has only one minor change. It's to have these one included in the RC1. Changes : http://people.apache.org/~aheritier/staging-sites/m1-plugins/ maven-1.x/plugins/announcement/changes-report.html#Release1_4_1- SNAPSHOThttp://people.apache.org/%7Eaheritier/staging-sites/m1- plugins/maven-1.x/plugins/site/changes-report.html#Release1_7_2- SNAPSHOT http://people.apache.org/%7Eaheritier/staging-sites/m1-plugins/ maven-1.x/plugins/site/changes-report.html#Release1_7_2-SNAPSHOT Staging site : http://people.apache.org/~aheritier/staging-sites/m1-plugins/ maven-1.x/plugins/announcement/http://people.apache.org/% 7Eaheritier/staging-sites/m1-plugins/maven-1.x/plugins/site/ Download : maven plugin:download -Dmaven.repo.remote=http://people.apache.org/ repo/m1 -snapshot-repository/,http://repo1.maven.org/maven -DgroupId=maven -DartifactId=maven-site-plugin -Dversion= 1.4.1-SNAPSHOT Bad cut'n paste maven plugin:download -Dmaven.repo.remote=http://people.apache.org/ repo/m1 -snapshot-repository/,http://repo1.maven.org/maven -DgroupId=maven -DartifactId=maven-announcement-plugin -Dversion= 1.4.1-SNAPSHOT +1 from me, 72h to vote Cheers, - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Clover plugin v2.4 - Take 2
+1 Vincent Massol wrote: Hi, As Mike Perham pointed out the Clover license for the release clover plugin (ie v2.3) has expired. Thus the urgency to release version 2.4. Here's the release notes for 2.4: ** Bug * [MCLOVER-45] - Excluded files should be added to compiled sources * [MCLOVER-53] - Clover plugin installs clover instrumented source in local repository * [MCLOVER-66] - The report goal doesn't support a user-provided Clover license * [MCLOVER-68] - XDoclet plugin executes before the Clover plugin in the lifecycle forked by the latter ** Improvement * [MCLOVER-38] - Allow check Mojo to be overriden by a failOnViolation parameter in the same way PMD and Checkstyle can * [MCLOVER-65] - Clover license has expired ** Task * [MCLOVER-67] - Remove deprecated licenseFile configuration parameter The plugin is staged at http://people.apache.org/~vmassol/maven-staging/ Here's my +1 Thanks -Vincent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] !DSPAM:602,46227532110829182317745! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] Release maven-developer-activity-plugin and maven-file-activity-plugin 1.6.1 for maven 1.X
+1 Stéphane On 4/16/07, Arnaud HERITIER [EMAIL PROTECTED] wrote: Hi, Those two plugins have a similar fix and weren't release for several months (more than 1 year in fact). Changes : http://people.apache.org/~aheritier/staging-sites/m1-plugins/maven-1.x/plugins/developer-activity/changes-report.html#Release1_6_1-SNAPSHOThttp://people.apache.org/%7Eaheritier/staging-sites/m1-plugins/maven-1.x/plugins/site/changes-report.html#Release1_7_2-SNAPSHOT http://people.apache.org/~aheritier/staging-sites/m1-plugins/maven-1.x/plugins/file-activity/changes-report.html#Release1_6_1-SNAPSHOThttp://people.apache.org/%7Eaheritier/staging-sites/m1-plugins/maven-1.x/plugins/site/changes-report.html#Release1_7_2-SNAPSHOT http://people.apache.org/%7Eaheritier/staging-sites/m1-plugins/maven-1.x/plugins/site/changes-report.html#Release1_7_2-SNAPSHOT Staging sites : http://people.apache.org/~aheritier/staging-sites/m1-plugins/maven-1.x/plugins/developer-activity/http://people.apache.org/%7Eaheritier/staging-sites/m1-plugins/maven-1.x/plugins/site/ http://people.apache.org/~aheritier/staging-sites/m1-plugins/maven-1.x/plugins/file-activity/http://people.apache.org/%7Eaheritier/staging-sites/m1-plugins/maven-1.x/plugins/site/ Download : maven plugin:download -Dmaven.repo.remote=http://people.apache.org/repo/ m1 -snapshot-repository/,http://repo1.maven.org/maven -DgroupId=maven -DartifactId=maven-developer-activity-plugin -Dversion=1.6.1-SNAPSHOT maven plugin:download -Dmaven.repo.remote=http://people.apache.org/repo/ m1 -snapshot-repository/,http://repo1.maven.org/maven -DgroupId=maven -DartifactId=maven-file-activity-plugin -Dversion=1.6.1-SNAPSHOT +1 from me, 72h to vote Cheers, - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] Release maven-site-plugin 1.7.2 for maven 1.X
+1 -Lukas Arnaud HERITIER wrote: Hi, I encountered some problems with the site plugin and its rsync deployment feature. I propose to release a new version to fix these problems. Changes : http://people.apache.org/~aheritier/staging-sites/m1-plugins/maven-1.x/plugins/site/changes-report.html#Release1_7_2-SNAPSHOT Staging site : http://people.apache.org/~aheritier/staging-sites/m1-plugins/maven-1.x/plugins/site/ Download : maven plugin:download -Dmaven.repo.remote=http://people.apache.org/repo/m1-snapshot-repository/, http://repo1.maven.org/maven -DgroupId=maven -DartifactId=maven-site-plugin -Dversion=1.7.2-SNAPSHOT +1 from me, 72h to vote Cheers, Arnaud - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] Release maven-announcement-plugin 1.4.1 for maven 1.X
+1 -Lukas Arnaud HERITIER wrote: Hi, In the logic to try to release often I propose to release the announcement which has only one minor change. It's to have these one included in the RC1. Changes : http://people.apache.org/~aheritier/staging-sites/m1-plugins/maven-1.x/plugins/announcement/changes-report.html#Release1_4_1-SNAPSHOThttp://people.apache.org/%7Eaheritier/staging-sites/m1-plugins/maven-1.x/plugins/site/changes-report.html#Release1_7_2-SNAPSHOT http://people.apache.org/%7Eaheritier/staging-sites/m1-plugins/maven-1.x/plugins/site/changes-report.html#Release1_7_2-SNAPSHOT Staging site : http://people.apache.org/~aheritier/staging-sites/m1-plugins/maven-1.x/plugins/announcement/http://people.apache.org/%7Eaheritier/staging-sites/m1-plugins/maven-1.x/plugins/site/ Download : maven plugin:download -Dmaven.repo.remote=http://people.apache.org/repo/ m1 -snapshot-repository/,http://repo1.maven.org/maven -DgroupId=maven -DartifactId=maven-site-plugin -Dversion=1.4.1-SNAPSHOT +1 from me, 72h to vote Cheers, - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] Release maven-developer-activity-plugin and maven-file-activity-plugin 1.6.1 for maven 1.X
+1 -Lukas Arnaud HERITIER wrote: Hi, Those two plugins have a similar fix and weren't release for several months (more than 1 year in fact). Changes : http://people.apache.org/~aheritier/staging-sites/m1-plugins/maven-1.x/plugins/developer-activity/changes-report.html#Release1_6_1-SNAPSHOThttp://people.apache.org/%7Eaheritier/staging-sites/m1-plugins/maven-1.x/plugins/site/changes-report.html#Release1_7_2-SNAPSHOT http://people.apache.org/~aheritier/staging-sites/m1-plugins/maven-1.x/plugins/file-activity/changes-report.html#Release1_6_1-SNAPSHOThttp://people.apache.org/%7Eaheritier/staging-sites/m1-plugins/maven-1.x/plugins/site/changes-report.html#Release1_7_2-SNAPSHOT http://people.apache.org/%7Eaheritier/staging-sites/m1-plugins/maven-1.x/plugins/site/changes-report.html#Release1_7_2-SNAPSHOT Staging sites : http://people.apache.org/~aheritier/staging-sites/m1-plugins/maven-1.x/plugins/developer-activity/http://people.apache.org/%7Eaheritier/staging-sites/m1-plugins/maven-1.x/plugins/site/ http://people.apache.org/~aheritier/staging-sites/m1-plugins/maven-1.x/plugins/file-activity/http://people.apache.org/%7Eaheritier/staging-sites/m1-plugins/maven-1.x/plugins/site/ Download : maven plugin:download -Dmaven.repo.remote=http://people.apache.org/repo/ m1 -snapshot-repository/,http://repo1.maven.org/maven -DgroupId=maven -DartifactId=maven-developer-activity-plugin -Dversion=1.6.1-SNAPSHOT maven plugin:download -Dmaven.repo.remote=http://people.apache.org/repo/ m1 -snapshot-repository/,http://repo1.maven.org/maven -DgroupId=maven -DartifactId=maven-file-activity-plugin -Dversion=1.6.1-SNAPSHOT +1 from me, 72h to vote Cheers, - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] Release maven-announcement-plugin 1.4.1 for maven 1.X
+1 Stéphane On 4/16/07, Arnaud HERITIER [EMAIL PROTECTED] wrote: Hi, In the logic to try to release often I propose to release the announcement which has only one minor change. It's to have these one included in the RC1. Changes : http://people.apache.org/~aheritier/staging-sites/m1-plugins/maven-1.x/plugins/announcement/changes-report.html#Release1_4_1-SNAPSHOThttp://people.apache.org/%7Eaheritier/staging-sites/m1-plugins/maven-1.x/plugins/site/changes-report.html#Release1_7_2-SNAPSHOT http://people.apache.org/%7Eaheritier/staging-sites/m1-plugins/maven-1.x/plugins/site/changes-report.html#Release1_7_2-SNAPSHOT Staging site : http://people.apache.org/~aheritier/staging-sites/m1-plugins/maven-1.x/plugins/announcement/http://people.apache.org/%7Eaheritier/staging-sites/m1-plugins/maven-1.x/plugins/site/ Download : maven plugin:download -Dmaven.repo.remote=http://people.apache.org/repo/ m1 -snapshot-repository/,http://repo1.maven.org/maven -DgroupId=maven -DartifactId=maven-site-plugin -Dversion=1.4.1-SNAPSHOT +1 from me, 72h to vote Cheers, - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] Release maven-site-plugin 1.7.2 for maven 1.X
+1 Stéphane On 4/16/07, Arnaud HERITIER [EMAIL PROTECTED] wrote: Hi, I encountered some problems with the site plugin and its rsync deployment feature. I propose to release a new version to fix these problems. Changes : http://people.apache.org/~aheritier/staging-sites/m1-plugins/maven-1.x/plugins/site/changes-report.html#Release1_7_2-SNAPSHOT Staging site : http://people.apache.org/~aheritier/staging-sites/m1-plugins/maven-1.x/plugins/site/ Download : maven plugin:download -Dmaven.repo.remote=http://people.apache.org/repo/m1-snapshot-repository/, http://repo1.maven.org/maven -DgroupId=maven -DartifactId=maven-site-plugin -Dversion=1.7.2-SNAPSHOT +1 from me, 72h to vote Cheers, Arnaud - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Clover plugin v2.4 - Take 2
+I On 4/16/07, Maria Odea Ching [EMAIL PROTECTED] wrote: +1 Vincent Massol wrote: Hi, As Mike Perham pointed out the Clover license for the release clover plugin (ie v2.3) has expired. Thus the urgency to release version 2.4. Here's the release notes for 2.4: ** Bug * [MCLOVER-45] - Excluded files should be added to compiled sources * [MCLOVER-53] - Clover plugin installs clover instrumented source in local repository * [MCLOVER-66] - The report goal doesn't support a user-provided Clover license * [MCLOVER-68] - XDoclet plugin executes before the Clover plugin in the lifecycle forked by the latter ** Improvement * [MCLOVER-38] - Allow check Mojo to be overriden by a failOnViolation parameter in the same way PMD and Checkstyle can * [MCLOVER-65] - Clover license has expired ** Task * [MCLOVER-67] - Remove deprecated licenseFile configuration parameter The plugin is staged at http://people.apache.org/~vmassol/maven-staging/ Here's my +1 Thanks -Vincent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] !DSPAM:602,46227532110829182317745! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Clover plugin v2.4 - Take 2
+1 On 4/15/07, Vincent Massol [EMAIL PROTECTED] wrote: Hi, As Mike Perham pointed out the Clover license for the release clover plugin (ie v2.3) has expired. Thus the urgency to release version 2.4. Here's the release notes for 2.4: ** Bug * [MCLOVER-45] - Excluded files should be added to compiled sources * [MCLOVER-53] - Clover plugin installs clover instrumented source in local repository * [MCLOVER-66] - The report goal doesn't support a user-provided Clover license * [MCLOVER-68] - XDoclet plugin executes before the Clover plugin in the lifecycle forked by the latter ** Improvement * [MCLOVER-38] - Allow check Mojo to be overriden by a failOnViolation parameter in the same way PMD and Checkstyle can * [MCLOVER-65] - Clover license has expired ** Task * [MCLOVER-67] - Remove deprecated licenseFile configuration parameter The plugin is staged at http://people.apache.org/~vmassol/maven-staging/ Here's my +1 Thanks -Vincent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[RESULT][VOTE] maven-remote-resources-plugin 1.0-alpha-5
5 +1 binding votes (Jason van Zyl, John Casey, Emmanuel Venisse, Joakim Erdfelt, Vincent Siveton) 3 +1 non-binding votes (Jason Dillon, Andrew Williams, Daniel Kulp) No -1 votes or new issues raised. This vote passes. Dan On Thursday 12 April 2007 13:13, Daniel Kulp wrote: I'd like to release version 1.0-alpha-5 of the maven-remote-resources-plugin. This resolves one critical bug, but also adds some new features to make it a bit more usable. Release Notes - Maven 2.x Remote Resources Plugin - Version 1.0-alpha-5 ** Bug * [MRRESOURCES-18] - Error when no 'inceptionYear' is specified in POM ** Improvement * [MRRESOURCES-19] - Bundle mojo only looks for txt and vm files * [MRRESOURCES-20] - Support for binary resources * [MRRESOURCES-21] - Supplement the data model used by Velocity Staging area: http://people.apache.org/~dkulp/stage_remoteresources/ Tag: http://svn.apache.org/repos/asf/maven/plugins/tags/maven-remote-resour ces-plugin-1.0-alpha-5/ -- J. Daniel Kulp Principal Engineer IONA P: 781-902-8727C: 508-380-7194 [EMAIL PROTECTED] http://www.dankulp.com/blog - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Clover plugin v2.4 - Take 2
+1 On 15 Apr 2007, at 19:55, Vincent Massol wrote: Hi, As Mike Perham pointed out the Clover license for the release clover plugin (ie v2.3) has expired. Thus the urgency to release version 2.4. Here's the release notes for 2.4: ** Bug * [MCLOVER-45] - Excluded files should be added to compiled sources * [MCLOVER-53] - Clover plugin installs clover instrumented source in local repository * [MCLOVER-66] - The report goal doesn't support a user- provided Clover license * [MCLOVER-68] - XDoclet plugin executes before the Clover plugin in the lifecycle forked by the latter ** Improvement * [MCLOVER-38] - Allow check Mojo to be overriden by a failOnViolation parameter in the same way PMD and Checkstyle can * [MCLOVER-65] - Clover license has expired ** Task * [MCLOVER-67] - Remove deprecated licenseFile configuration parameter The plugin is staged at http://people.apache.org/~vmassol/maven- staging/ Here's my +1 Thanks -Vincent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] release maven-release-1 parent and maven-release-manager-1.0-alpha-1
Summary: 6 binding +1 (jesse, emmanuel, jdcasey, snicoll, arnaud, vsiveton) I'll get this moved over and synced out today. thanks! next up, continuum 1.1 alpha 1 On 4/15/07, Stephane Nicoll [EMAIL PROTECTED] wrote: On 4/15/07, Max Bowsher [EMAIL PROTECTED] wrote: Stephane Nicoll wrote: On 4/14/07, Max Bowsher [EMAIL PROTECTED] wrote: Too late for this release, but could someone take a look at MRELEASE-137 so it gets into the next one? It's a trivial one-liner fix. The attached patch is for maven-release-plugin, but the relevant class has since moved into maven-release-manager. It's obvious how to forward port the single change to the new code. The change does not seem that trivial to me. A potential IndexOutOfBoundsException might be trhown. Jason is the assignee but i'll try to have a look. The current code calls: list.get( 0 ) the fix is to change that to: list.get( list.size() - 1 ) Surely the only way the second one could cause an IOOBE is if the list is empty, in which case the current code would also IOOBE? I'm missing coffee. Forget it :) Max. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- jesse mcconnell [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Remove auto-resolution of plugin versions from Maven 2.1
Apologies for the delayed response. I must've missed the message. I'd have to check with Andrus Adamchik, since he was the guy that had to keep fixing the POM. I know for certain that we've been bitten numerous times by the Geronimo folk though, both transitively and directly. We also got bit by the whole surefire/classloader issue, which the suggestions in this thread would take care of. For my own stuff, I've had to rely on SNAPSHOT for Selenium and Cargo, because either the released versions were broken in some way or didn't support newer releases of external software. At least in the case of Selenium, the authors know that they're released version is broken and their response is to just use SNAPSHOT. That's the sort of scenario I'd like to see avoided if possible. -- Kevin -Original Message- From: John Casey [mailto:[EMAIL PROTECTED] Sent: Thursday, April 12, 2007 5:24 PM To: Maven Developers List Subject: Re: Remove auto-resolution of plugin versions from Maven 2.1 I'm interested to know which snapshots bit you guys so hard? Was it a [set of] internal snapshots, or were they snapshots from Maven or some other OSS project that you depend on or use? If we start talking seriously about shorter dev cycles and milestone releases with less of a barrier to release (for alpha quality, for instance)...and start shunning snapshots as an acceptable mechanism for distributing pre-release code...would that have helped you all? -john On 4/12/07, Kevin Menard [EMAIL PROTECTED] wrote: I agree. I am suggesting that it's a little too easy to use SNAPSHOTs and that all that wonderful time maven was supposed to save you in preparing releases is trumped by the time it takes to just append -SNAPSHOT to a version number. Sure, it's people abusing it, but it's easy to abuse and looks like it's officially condoned as proper behavior. Things get even murkier when transitive dependencies are considered. So, I'm not suggesting dumping SNAPSHOT wholesale, but making it more difficult to distribute an artifact via SNAPSHOT (maybe require the end user to have to agree to use a new SNAPSHOT each time one is available or something). Maybe we'll just have to agree to disagree. I will say that this matter has bitten the Cayenne team a few times now, and we've come close to dumping maven altogether. It got to the point where we had to start pinning SNAPSHOTs by timestamp via a guess and check method. Perhaps the plugin Nigel suggested would help matters, though. -- Kevin -Original Message- From: Brian E. Fox [mailto:[EMAIL PROTECTED] Sent: Thursday, April 12, 2007 3:10 PM To: Maven Developers List Subject: RE: Remove auto-resolution of plugin versions from Maven 2.1 Snapshots are a very good thing for internal development. It would be impossible to manage my builds without them. I think that people using snapshots of plugins are a symptom of another problem -- long release cycles. Just because people do bad things with snapshots doesn't mean snapshots should go away. It already takes a little effort to get at them, the snapshot repo isn't part of the super-pom, so if you go out of your way to get them, you should understand the consequences. It's like me picking up an unstable version of some jar and then complaining that it broke later and asking the creators to stop releasing unstable versions at all(that are clearly marked as such). People would then just go get the code anyway. -Original Message- From: Kevin Menard [mailto:[EMAIL PROTECTED] Sent: Thursday, April 12, 2007 1:09 PM To: Maven Developers List Subject: RE: Remove auto-resolution of plugin versions from Maven 2.1 Right. My point is that regardless of what the original intention may have been, the current process facilitates laziness via SNAPSHOTs. Without them, incremental builds would be necessary, which would give fixed version numbers with known binaries. If the plan is to take actions to help prevent users from having things break on them, this may be easier than the path you outlined. -- Kevin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] Release maven-developer-activity-plugin and maven-file-activity-plugin 1.6.1 for maven 1.X
+1 Arnaud HERITIER wrote: Hi, Those two plugins have a similar fix and weren't release for several months (more than 1 year in fact). Changes : http://people.apache.org/~aheritier/staging-sites/m1-plugins/maven-1.x/plugins/developer-activity/changes-report.html#Release1_6_1-SNAPSHOThttp://people.apache.org/%7Eaheritier/staging-sites/m1-plugins/maven-1.x/plugins/site/changes-report.html#Release1_7_2-SNAPSHOT http://people.apache.org/~aheritier/staging-sites/m1-plugins/maven-1.x/plugins/file-activity/changes-report.html#Release1_6_1-SNAPSHOThttp://people.apache.org/%7Eaheritier/staging-sites/m1-plugins/maven-1.x/plugins/site/changes-report.html#Release1_7_2-SNAPSHOT http://people.apache.org/%7Eaheritier/staging-sites/m1-plugins/maven-1.x/plugins/site/changes-report.html#Release1_7_2-SNAPSHOT Staging sites : http://people.apache.org/~aheritier/staging-sites/m1-plugins/maven-1.x/plugins/developer-activity/http://people.apache.org/%7Eaheritier/staging-sites/m1-plugins/maven-1.x/plugins/site/ http://people.apache.org/~aheritier/staging-sites/m1-plugins/maven-1.x/plugins/file-activity/http://people.apache.org/%7Eaheritier/staging-sites/m1-plugins/maven-1.x/plugins/site/ Download : maven plugin:download -Dmaven.repo.remote=http://people.apache.org/repo/ m1 -snapshot-repository/,http://repo1.maven.org/maven -DgroupId=maven -DartifactId=maven-developer-activity-plugin -Dversion=1.6.1-SNAPSHOT maven plugin:download -Dmaven.repo.remote=http://people.apache.org/repo/ m1 -snapshot-repository/,http://repo1.maven.org/maven -DgroupId=maven -DartifactId=maven-file-activity-plugin -Dversion=1.6.1-SNAPSHOT +1 from me, 72h to vote Cheers, -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Integration Testing
Jerome, that link contains information on the strategy I've been using in the assembly plugin, and it seems to work well (although it's a bit slower, since it's spawning so many Maven builds). I'm hoping to converge the tools we're using in the core ITs with those in the maven-component-test-plugin (used to be maven-plugin-test-plugin), and the maven-invoker-plugin, and arrive at some single solution (a plugin) that we can use everywhere...but I haven't even been able to come up with a unified feature list yet. -john On 4/15/07, Jerome Lacoste [EMAIL PROTECTED] wrote: On 2/24/07, Brett Porter [EMAIL PROTECTED] wrote: On 04/01/2007, at 4:32 PM, Brett Porter wrote: Jason - any further thoughts on this? Ping... No is a valid answer :) I'd like to get your summary put somewhere individuals can pick things off to work on - probably a jira project for shared. WDYT? I'm overcommitted for working on things right now, but I know a couple of people are confused about the IT testing, and we've got all those chronically broken plugins. Volunteers? I want to improve the state of IT for the mojos I work with (in particular in the mojo project). I am particularly interested in doing it in an sort of official/standard way. - [ ] We need to standardize on integration testing in general. We have people going all over the place and it's a disaster. - [ ] We have too many IT plugins (3) - [ ] We have too many invokers (5) - [ ] We have too many verifiers (3) I've found this: http://maven.apache.org/developers/committer-testing-plugins.html Does that represent the current IT strategy 'standard' ? Was that written after the point above was resolved ? Cheers, Jerome - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Integration Testing
On 4/17/07, John Casey [EMAIL PROTECTED] wrote: Jerome, that link contains information on the strategy I've been using in the assembly plugin, and it seems to work well (although it's a bit slower, since it's spawning so many Maven builds). I'm hoping to converge the tools we're using in the core ITs with those in the maven-component-test-plugin (used to be maven-plugin-test-plugin), and the maven-invoker-plugin, and arrive at some single solution (a plugin) that we can use everywhere...but I haven't even been able to come up with a unified feature list yet. So, does anyone have a recommended approach so I can move forward in the mean time? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Remove auto-resolution of plugin versions from Maven 2.1
On 4/17/07, Kevin Menard [EMAIL PROTECTED] wrote: support newer releases of external software. At least in the case of Selenium, the authors know that they're released version is broken and their response is to just use SNAPSHOT. That's the sort of scenario I'd like to see avoided if possible. That's not terribly helpful of the Selenium folks. You should get more of their users to whinge. Broken releases should get fixed ASAP, or else dump Selenium and use something else. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Integration Testing
my only recommendation would be to take a look at the maven-assembly-plugin (SVN: http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-assembly-plugin) and go for something like that... On 4/16/07, Barrie Treloar [EMAIL PROTECTED] wrote: On 4/17/07, John Casey [EMAIL PROTECTED] wrote: Jerome, that link contains information on the strategy I've been using in the assembly plugin, and it seems to work well (although it's a bit slower, since it's spawning so many Maven builds). I'm hoping to converge the tools we're using in the core ITs with those in the maven-component-test-plugin (used to be maven-plugin-test-plugin), and the maven-invoker-plugin, and arrive at some single solution (a plugin) that we can use everywhere...but I haven't even been able to come up with a unified feature list yet. So, does anyone have a recommended approach so I can move forward in the mean time? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
