Re: Maven 2.1.0 Plans (a proposal of sorts)
Question about 2.1.0 / 3.0.0. In 3.0 alpha2 Jason fix a problem with jaxws-maven. Could it be backported to 2.1.0 ? Also did this new 'mileston' will be used in m2eclipse. I know Maven 3.0 is the target for m2eclipse but during the intermin, having a stable and known 2.1 would be nice. Regards 2009/2/18 John Casey jdca...@commonjava.org: Brett Porter wrote: On 18/02/2009, at 7:23 AM, John Casey wrote: It will take less effort for me to just keep working on issues until they are done, so that's what I'll do. So, agreed, next version is 2.1.0, standard RC cycle applies. I'm fine whittling away some of what's left out there. I don't think it all has to happen in 2.1.0. IMO, we should take care of the four top-voted issues if we can - and if we can be relatively sure we're not angering the gods with our hubris - then do the rest in 2.1.1. The fourth top issue seems on the face of it to be based on a common misunderstanding about how profiles are triggered and applied...probably more of a documentation/education task than anything else. I'm not sure which one you are referring to. If you look at the 2.1.0 version bucket, enable the display of vote counts, and sort on that column, you'll see one pop out related to profiles in the parent not being applied to the child. I'm guessing it's just some explaining we need to do around that in terms of doco/education, and we're done. Beyond that, I'm alright releasing 2.1.0 final provided we can be sure that the wagon version we're using is stable. I seem to remember an issue coming up shortly after the release of 2.1.0-M1 related to one of the new Wagon implementations - WebDAV, maybe? I'm having some trouble remembering/finding that issue in my gmail, but we need to make sure that doesn't get left out of this release. If it means rolling back to an older wagon version, then let's do that. It's a regression in the SSH wagon, which I've not been able to reproduce and I never saw an issue filed for. We can wait and see what happens in the RC cycle. Do you happen to have a Nabble link for that thread? I'll keep searching, but it'd be really nice to push that to resolution, as it's probably the biggest wart on 2.1.0-M1. -john - 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: Maven 2.1.0 Plans (a proposal of sorts)
On 18/02/2009, at 7:43 PM, Henri Gomez wrote: Question about 2.1.0 / 3.0.0. In 3.0 alpha2 Jason fix a problem with jaxws-maven. Could it be backported to 2.1.0 ? I believe that problem doesn't affect 2.1.0. Also did this new 'mileston' will be used in m2eclipse. I know Maven 3.0 is the target for m2eclipse but during the intermin, having a stable and known 2.1 would be nice. We're not planning to backport the embedder at this stage, but of course 2.1.0 will be available as an external installation should you want to use it that way. HTH, Brett -- Brett Porter br...@apache.org http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Maven 2.1.0 Plans (a proposal of sorts)
2009/2/18 Brett Porter br...@apache.org: On 18/02/2009, at 7:43 PM, Henri Gomez wrote: Question about 2.1.0 / 3.0.0. In 3.0 alpha2 Jason fix a problem with jaxws-maven. Could it be backported to 2.1.0 ? I believe that problem doesn't affect 2.1.0. Nope, the jaxws maven plugin didn't works with maven 2.1.0 (at least the version in m2eclipse 0.9.7) :( The following mojo encountered an error while executing: Group-Id: org.codehaus.mojo Artifact-Id: jaxws-maven-plugin Version: 1.11 Mojo: wsgen brought in via: POM While building project: Group-Id: mycorp.can Artifact-Id: mycorp-framework Version: 2.0.0-19-SNAPSHOT From file: C:\workspace-34\mycorp-framework\pom.xml Reason: Failed to execute wsgen java.lang.NoClassDefFoundError: com/sun/mirror/apt/AnnotationProcessorFactory at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:620) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124) at java.net.URLClassLoader.defineClass(URLClassLoader.java:260) at java.net.URLClassLoader.access$100(URLClassLoader.java:56) at java.net.URLClassLoader$1.run(URLClassLoader.java:195) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:188) at java.lang.ClassLoader.loadClass(ClassLoader.java:306) at java.lang.ClassLoader.loadClass(ClassLoader.java:251) at org.codehaus.plexus.classworlds.realm.ClassRealm.loadRealmClass(ClassRealm.java:174) at org.codehaus.plexus.classworlds.strategy.DefaultStrategy.loadClass(DefaultStrategy.java:67) at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:201) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) at com.sun.tools.ws.WsGen.doMain(WsGen.java:69) at org.codehaus.mojo.jaxws.AbstractWsGenMojo.execute(AbstractWsGenMojo.java:97) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:579) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:498) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmentForProject(DefaultLifecycleExecutor.java:265) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:191) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:149) at org.apache.maven.DefaultMaven.execute_aroundBody0(DefaultMaven.java:223) at org.apache.maven.DefaultMaven.execute_aroundBody1$advice(DefaultMaven.java:304) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:1) at org.apache.maven.embedder.MavenEmbedder.execute_aroundBody2(MavenEmbedder.java:904) at org.apache.maven.embedder.MavenEmbedder.execute_aroundBody3$advice(MavenEmbedder.java:304) at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:1) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:176) at org.apache.maven.cli.MavenCli.main(MavenCli.java:63) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:408) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:351) at org.codehaus.classworlds.Launcher.main(Launcher.java:31) Error stacktrace: org.apache.maven.lifecycle.LifecycleExecutionException: Internal error in the plugin manager executing goal 'org.codehaus.mojo:jaxws-maven-plugin:1.11:wsgen': Mojo execution failed. at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:505) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmentForProject(DefaultLifecycleExecutor.java:265) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:191) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:149) at org.apache.maven.DefaultMaven.execute_aroundBody0(DefaultMaven.java:223) at org.apache.maven.DefaultMaven.execute_aroundBody1$advice(DefaultMaven.java:304) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:1) at
Re: Maven 2.1.0 Plans (a proposal of sorts)
As was highlighted before in these threads, this is a completely different 2.1.0 to the one previously included in m2eclipse (it never has been included): http://www.sonatype.com/people/2008/11/a-visual-history-of-maven-2/ - Brett On 18/02/2009, at 10:32 PM, Henri Gomez wrote: 2009/2/18 Brett Porter br...@apache.org: On 18/02/2009, at 7:43 PM, Henri Gomez wrote: Question about 2.1.0 / 3.0.0. In 3.0 alpha2 Jason fix a problem with jaxws-maven. Could it be backported to 2.1.0 ? I believe that problem doesn't affect 2.1.0. Nope, the jaxws maven plugin didn't works with maven 2.1.0 (at least the version in m2eclipse 0.9.7) :( The following mojo encountered an error while executing: Group-Id: org.codehaus.mojo Artifact-Id: jaxws-maven-plugin Version: 1.11 Mojo: wsgen brought in via: POM While building project: Group-Id: mycorp.can Artifact-Id: mycorp-framework Version: 2.0.0-19-SNAPSHOT From file: C:\workspace-34\mycorp-framework\pom.xml Reason: Failed to execute wsgen java.lang.NoClassDefFoundError: com/sun/mirror/apt/ AnnotationProcessorFactory at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:620) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java: 124) at java.net.URLClassLoader.defineClass(URLClassLoader.java:260) at java.net.URLClassLoader.access$100(URLClassLoader.java:56) at java.net.URLClassLoader$1.run(URLClassLoader.java:195) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:188) at java.lang.ClassLoader.loadClass(ClassLoader.java:306) at java.lang.ClassLoader.loadClass(ClassLoader.java:251) at org .codehaus .plexus.classworlds.realm.ClassRealm.loadRealmClass(ClassRealm.java: 174) at org .codehaus .plexus .classworlds.strategy.DefaultStrategy.loadClass(DefaultStrategy.java: 67) at org .codehaus .plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:201) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) at com.sun.tools.ws.WsGen.doMain(WsGen.java:69) at org .codehaus .mojo.jaxws.AbstractWsGenMojo.execute(AbstractWsGenMojo.java:97) at org .apache .maven .plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java: 579) at org .apache .maven .lifecycle .DefaultLifecycleExecutor .executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:498) at org .apache .maven .lifecycle .DefaultLifecycleExecutor .executeTaskSegmentForProject(DefaultLifecycleExecutor.java:265) at org .apache .maven .lifecycle .DefaultLifecycleExecutor .executeTaskSegments(DefaultLifecycleExecutor.java:191) at org .apache .maven .lifecycle .DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:149) at org.apache.maven.DefaultMaven.execute_aroundBody0(DefaultMaven.java: 223) at org .apache .maven.DefaultMaven.execute_aroundBody1$advice(DefaultMaven.java:304) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:1) at org .apache .maven.embedder.MavenEmbedder.execute_aroundBody2(MavenEmbedder.java: 904) at org .apache .maven .embedder .MavenEmbedder.execute_aroundBody3$advice(MavenEmbedder.java:304) at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:1) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:176) at org.apache.maven.cli.MavenCli.main(MavenCli.java:63) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun .reflect .NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun .reflect .DelegatingMethodAccessorImpl .invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org .codehaus .plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java: 289) at org .codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java: 229) at org .codehaus .plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java: 408) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java: 351) at org.codehaus.classworlds.Launcher.main(Launcher.java:31) Error stacktrace: org.apache.maven.lifecycle.LifecycleExecutionException: Internal error in the plugin manager executing goal 'org.codehaus.mojo:jaxws-maven-plugin:1.11:wsgen': Mojo execution failed. at org .apache .maven .lifecycle .DefaultLifecycleExecutor .executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:505) at org .apache .maven .lifecycle .DefaultLifecycleExecutor .executeTaskSegmentForProject(DefaultLifecycleExecutor.java:265) at org .apache .maven .lifecycle .DefaultLifecycleExecutor .executeTaskSegments(DefaultLifecycleExecutor.java:191) at org .apache .maven .lifecycle .DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:149) at
Re: Maven 2.1.0 Plans (a proposal of sorts)
I build my JAX-WS project with maven 2.1.0-M1 and it works :) Good news, but could it be used in m2eclipse ? 2009/2/18 Brett Porter br...@apache.org: As was highlighted before in these threads, this is a completely different 2.1.0 to the one previously included in m2eclipse (it never has been included): http://www.sonatype.com/people/2008/11/a-visual-history-of-maven-2/ - Brett On 18/02/2009, at 10:32 PM, Henri Gomez wrote: 2009/2/18 Brett Porter br...@apache.org: On 18/02/2009, at 7:43 PM, Henri Gomez wrote: Question about 2.1.0 / 3.0.0. In 3.0 alpha2 Jason fix a problem with jaxws-maven. Could it be backported to 2.1.0 ? I believe that problem doesn't affect 2.1.0. Nope, the jaxws maven plugin didn't works with maven 2.1.0 (at least the version in m2eclipse 0.9.7) :( The following mojo encountered an error while executing: Group-Id: org.codehaus.mojo Artifact-Id: jaxws-maven-plugin Version: 1.11 Mojo: wsgen brought in via: POM While building project: Group-Id: mycorp.can Artifact-Id: mycorp-framework Version: 2.0.0-19-SNAPSHOT From file: C:\workspace-34\mycorp-framework\pom.xml Reason: Failed to execute wsgen java.lang.NoClassDefFoundError: com/sun/mirror/apt/AnnotationProcessorFactory at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:620) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124) at java.net.URLClassLoader.defineClass(URLClassLoader.java:260) at java.net.URLClassLoader.access$100(URLClassLoader.java:56) at java.net.URLClassLoader$1.run(URLClassLoader.java:195) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:188) at java.lang.ClassLoader.loadClass(ClassLoader.java:306) at java.lang.ClassLoader.loadClass(ClassLoader.java:251) at org.codehaus.plexus.classworlds.realm.ClassRealm.loadRealmClass(ClassRealm.java:174) at org.codehaus.plexus.classworlds.strategy.DefaultStrategy.loadClass(DefaultStrategy.java:67) at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:201) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) at com.sun.tools.ws.WsGen.doMain(WsGen.java:69) at org.codehaus.mojo.jaxws.AbstractWsGenMojo.execute(AbstractWsGenMojo.java:97) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:579) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:498) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmentForProject(DefaultLifecycleExecutor.java:265) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:191) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:149) at org.apache.maven.DefaultMaven.execute_aroundBody0(DefaultMaven.java:223) at org.apache.maven.DefaultMaven.execute_aroundBody1$advice(DefaultMaven.java:304) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:1) at org.apache.maven.embedder.MavenEmbedder.execute_aroundBody2(MavenEmbedder.java:904) at org.apache.maven.embedder.MavenEmbedder.execute_aroundBody3$advice(MavenEmbedder.java:304) at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:1) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:176) at org.apache.maven.cli.MavenCli.main(MavenCli.java:63) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:408) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:351) at org.codehaus.classworlds.Launcher.main(Launcher.java:31) Error stacktrace: org.apache.maven.lifecycle.LifecycleExecutionException: Internal error in the plugin manager executing goal 'org.codehaus.mojo:jaxws-maven-plugin:1.11:wsgen': Mojo execution failed. at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:505) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmentForProject(DefaultLifecycleExecutor.java:265) at
Re: Maven 2.1.0 Plans (a proposal of sorts)
On 18/02/2009, at 11:59 PM, Henri Gomez wrote: I build my JAX-WS project with maven 2.1.0-M1 and it works :) Good news, but could it be used in m2eclipse ? It's really something to take up with m2eclipse... but I don't see it happening for the reason I outlined earlier regarding the embedder. - Brett -- Brett Porter br...@apache.org http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven Doxia version 1.0
Hi Dennis/Brian, Does the vote could continue with this new staging or do we need a new thread? Cheers, Vincent 2009/2/17, Brian E. Fox bri...@reply.infinity.nu: The new staging repo location is: https://repository.apache.org/content/repositories/maven-staging-4847e34 062fc70/ Just double check that everything looks ok to you. -Original Message- From: Dennis Lundberg [mailto:denn...@apache.org] Sent: Tuesday, February 17, 2009 2:26 PM To: Maven Developers List Subject: Re: [VOTE] Release Maven Doxia version 1.0 Thanks Brian. I'm reading up on the new repo as we speak. Brian E. Fox wrote: I'll copy the artifacts to a staging repo for you tonight and then you can promote it when the vote is closed. On 2/17/09 1:25 PM, Dennis Lundberg denn...@apache.org wrote: +1 from me Dennis Lundberg wrote: Hi, (resending due to SMTP-server problems) The time has finally come to release Doxia 1.0. For more info on the relationship to plugins and other components, see the Doxia Release Plan at http://docs.codehaus.org/display/MAVEN/Doxia+Release+Plan We've solved 1 issue: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10780styleNa me=Ht mlversion=14834 There are still lots of issues left in JIRA, but they will go into later versions: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=10780 stat us=1 Staging repo: http://people.apache.org/~dennisl/staging-repo/doxia/ Staging site: http://maven.apache.org/doxia/doxia-1.0.x/staging/ Well, at least it should be there, but I'm bitten by http://jira.codehaus.org/browse/MSITE-384 so I can't deploy the full staging site from my Windows box. I tried to deploy it using Ubuntu running in Virtual Box, but that hasn't worked out completely either. If someone with a non-Windows box could check out https://svn.apache.org/repos/asf/maven/doxia/doxia/tags/doxia-1.0/ and the run 'mvn package site:stage-deploy' on it I'd sure appreciate it. 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 -- 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 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Maven 2.1.0 Plans (a proposal of sorts)
2009/2/18 Brett Porter br...@apache.org: On 18/02/2009, at 11:59 PM, Henri Gomez wrote: I build my JAX-WS project with maven 2.1.0-M1 and it works :) Good news, but could it be used in m2eclipse ? It's really something to take up with m2eclipse... but I don't see it happening for the reason I outlined earlier regarding the embedder. Sniff ;( I'll ask on m2eclipse. Thanks Brett - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven Doxia version 1.0
IMO it should continue, I merely copied the artifacts from one location to another. Inspecting the signatures should validate the artifacts. --Brian (mobile) On Feb 18, 2009, at 8:16 AM, Vincent Siveton vincent.sive...@gmail.com wrote: Hi Dennis/Brian, Does the vote could continue with this new staging or do we need a new thread? Cheers, Vincent 2009/2/17, Brian E. Fox bri...@reply.infinity.nu: The new staging repo location is: https://repository.apache.org/content/repositories/maven-staging-4847e34 062fc70/ Just double check that everything looks ok to you. -Original Message- From: Dennis Lundberg [mailto:denn...@apache.org] Sent: Tuesday, February 17, 2009 2:26 PM To: Maven Developers List Subject: Re: [VOTE] Release Maven Doxia version 1.0 Thanks Brian. I'm reading up on the new repo as we speak. Brian E. Fox wrote: I'll copy the artifacts to a staging repo for you tonight and then you can promote it when the vote is closed. On 2/17/09 1:25 PM, Dennis Lundberg denn...@apache.org wrote: +1 from me Dennis Lundberg wrote: Hi, (resending due to SMTP-server problems) The time has finally come to release Doxia 1.0. For more info on the relationship to plugins and other components, see the Doxia Release Plan at http://docs.codehaus.org/display/MAVEN/Doxia+Release+Plan We've solved 1 issue: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10780styleNa me=Ht mlversion=14834 There are still lots of issues left in JIRA, but they will go into later versions: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=10780 stat us=1 Staging repo: http://people.apache.org/~dennisl/staging-repo/doxia/ Staging site: http://maven.apache.org/doxia/doxia-1.0.x/staging/ Well, at least it should be there, but I'm bitten by http://jira.codehaus.org/browse/MSITE-384 so I can't deploy the full staging site from my Windows box. I tried to deploy it using Ubuntu running in Virtual Box, but that hasn't worked out completely either. If someone with a non-Windows box could check out https://svn.apache.org/repos/asf/maven/doxia/doxia/tags/doxia-1.0/ and the run 'mvn package site:stage-deploy' on it I'd sure appreciate it. 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 -- 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 - 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 mercury-1.0-alpha-5
I know the vote is closed, but +1 Emmanuel On Wed, Feb 11, 2009 at 6:58 AM, Oleg Gusakov oleg.subscripti...@gmail.comwrote: Hi, Main reason for this release - bug fixes. A lot of testing done on the repository side, IT coverage on repository components is 60-70 % We solved 11 issues: http://jira.codehaus.org/browse/MERCURY/fixforversion/14955 Staging repo: https://repository.apache.org/content/repositories/maven-staging-4630e65601be12/ Staging site: published and will be synced to: http://maven.apache.org/mercury/staging/ 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
[ANN] Maven 2.0.10 Release
The Maven team is pleased to announce the release of the Maven 2.0.10 This is a stable bug fix release and you can see the full list of issues fixed at http://maven.apache.org/release-notes.html Enjoy, -The Maven team - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Maven 2.1.0 Plans (a proposal of sorts)
On 18/02/2009, at 4:58 PM, John Casey wrote: Brett Porter wrote: On 18/02/2009, at 7:23 AM, John Casey wrote: It will take less effort for me to just keep working on issues until they are done, so that's what I'll do. So, agreed, next version is 2.1.0, standard RC cycle applies. I'm fine whittling away some of what's left out there. I don't think it all has to happen in 2.1.0. IMO, we should take care of the four top-voted issues if we can - and if we can be relatively sure we're not angering the gods with our hubris - then do the rest in 2.1.1. Ok, I dropped a couple of non-controversial ones and assigned some to self. Some of them have patches so should be quick enough to get in there. Beyond that, I'm alright releasing 2.1.0 final provided we can be sure that the wagon version we're using is stable. I seem to remember an issue coming up shortly after the release of 2.1.0-M1 related to one of the new Wagon implementations - WebDAV, maybe? I'm having some trouble remembering/finding that issue in my gmail, but we need to make sure that doesn't get left out of this release. If it means rolling back to an older wagon version, then let's do that. It's a regression in the SSH wagon, which I've not been able to reproduce and I never saw an issue filed for. We can wait and see what happens in the RC cycle. Do you happen to have a Nabble link for that thread? I'll keep searching, but it'd be really nice to push that to resolution, as it's probably the biggest wart on 2.1.0-M1. I think it's the one from Henrique here: http://markmail.org/thread/2goikjq2x3nqrx5z I can fiddle around with it again to see if I can reproduce. - Brett -- Brett Porter br...@apache.org http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven Doxia version 1.0
+1 FYI I already staged the site early this month: http://people.apache.org/~vsiveton/doxia-1.0.x/ Cheers, Vincent 2009/2/11 Dennis Lundberg denn...@apache.org: Hi, (resending due to SMTP-server problems) The time has finally come to release Doxia 1.0. For more info on the relationship to plugins and other components, see the Doxia Release Plan at http://docs.codehaus.org/display/MAVEN/Doxia+Release+Plan We've solved 1 issue: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10780styleName=Htmlversion=14834 There are still lots of issues left in JIRA, but they will go into later versions: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=10780status=1 Staging repo: http://people.apache.org/~dennisl/staging-repo/doxia/ Staging site: http://maven.apache.org/doxia/doxia-1.0.x/staging/ Well, at least it should be there, but I'm bitten by http://jira.codehaus.org/browse/MSITE-384 so I can't deploy the full staging site from my Windows box. I tried to deploy it using Ubuntu running in Virtual Box, but that hasn't worked out completely either. If someone with a non-Windows box could check out https://svn.apache.org/repos/asf/maven/doxia/doxia/tags/doxia-1.0/ and the run 'mvn package site:stage-deploy' on it I'd sure appreciate it. Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 -- 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: svn commit: r744288 - in /maven/pom/trunk: asf/pom.xml maven/pom.xml
On 15/02/2009, at 2:05 AM, Brian E. Fox wrote: This is probably moreso for the repositories elements - there's a chance some projects will be referring to snapshots in both places. The current one is a group that is logically combining the old and new repos, there's no reason not to use the r.a.o group for any project instead of p.a.o since it is the only place that will have all snapshots. Is this working? I only see a few projects in there. I also see metadata from external stuff (opensymphony) which seems wrong. Thanks, Brett -- Brett Porter br...@apache.org http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [vote] release asf/maven/maven-plugins/maven-shared poms
+1 (note possible problems with the remote configuration that I've replied to on a separate mail, but the POMs themselves are fine). - Brett On 18/02/2009, at 12:42 PM, Brian E. Fox wrote: New parents need to be released with the new distributionManagement sections pointed at repository.apache.org: Apache Pom Diffs: http://svn.apache.org/viewvc/maven/pom/tags/apache-5/pom.xml?r1=639584r 2=745325diff_format=h Staged at: https://repository.apache.org/content/repositories/staging-484a2aeeabd6a 7/ Diffs: http://svn.apache.org/viewvc/maven/pom/tags/maven-parent-11/pom.xml?r1=7 39516r2=745330diff_format=h http://svn.apache.org/viewvc/maven/plugins/tags/maven-plugins-13/pom.xml ?r1=728991r2=745340diff_format=h http://svn.apache.org/viewvc/maven/shared/tags/maven-shared-components-1 1/pom.xml?r1=739774r2=745352diff_format=h Maven Parent and Maven-Plugins Parent Staged at: https://repository.apache.org/content/repositories/maven-staging-484a998 2bc6221/ 72hrs, +1 -- Brian Fox Apache Maven PMC http://www.sonatype.com/people/author/brian - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Brett Porter br...@apache.org http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [vote] release asf/maven/maven-plugins/maven-shared poms
+1 Vincent 2009/2/17 Brian E. Fox bri...@reply.infinity.nu: New parents need to be released with the new distributionManagement sections pointed at repository.apache.org: Apache Pom Diffs: http://svn.apache.org/viewvc/maven/pom/tags/apache-5/pom.xml?r1=639584r 2=745325diff_format=h Staged at: https://repository.apache.org/content/repositories/staging-484a2aeeabd6a 7/ Diffs: http://svn.apache.org/viewvc/maven/pom/tags/maven-parent-11/pom.xml?r1=7 39516r2=745330diff_format=h http://svn.apache.org/viewvc/maven/plugins/tags/maven-plugins-13/pom.xml ?r1=728991r2=745340diff_format=h http://svn.apache.org/viewvc/maven/shared/tags/maven-shared-components-1 1/pom.xml?r1=739774r2=745352diff_format=h Maven Parent and Maven-Plugins Parent Staged at: https://repository.apache.org/content/repositories/maven-staging-484a998 2bc6221/ 72hrs, +1 -- Brian Fox Apache Maven PMC http://www.sonatype.com/people/author/brian - 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: Maven 2.1.0 Plans (a proposal of sorts)
2.1 has actually served the purpose it was intended for and should be released. Obviously, the other items that were intended for 2.1 haven't been completed and shouldn't hold things up. So +1 on releasing 2.1.0 now. As for the other items that weren't completed, at this point it is unclear to me whether the items that were on the roadmap are being fixed in 3.0 or not. I'm still not quite sure how far off the 3.0 release is, but it is looking closer all the time. So I really don't know if it makes sense to work on those items and target a 2.2 release or not. Ralph On Feb 17, 2009, at 5:35 PM, Brett Porter wrote: On 18/02/2009, at 7:23 AM, John Casey wrote: I fully agree with Brian about the version naming for the next release. I couldn't possibly care less what version we use at this point, only that we start doing releases again. I want to see 2.1 out as much as anyone. However, it was frustrating to work the list of issues down to 0 and have that pulled away at the last minute. We should have stuck with the scheme we had in place already. It will take less effort for me to just keep working on issues until they are done, so that's what I'll do. So, agreed, next version is 2.1.0, standard RC cycle applies. I thought Oleg was working on MNG-553 still... It's been closed today, but there is still a snapshot dependency on trunk. Oleg, can you release plexus-sec-dispatcher? Brett, are you still working on MNG-3379, and did you plan to finish that before we release 2.1.0? I was waiting for the milestone release before disrupting anything. If that's not happening, I'll push that down as soon as I have some free time this week. The fourth top issue seems on the face of it to be based on a common misunderstanding about how profiles are triggered and applied...probably more of a documentation/education task than anything else. I'm not sure which one you are referring to. Beyond that, I'm alright releasing 2.1.0 final provided we can be sure that the wagon version we're using is stable. I seem to remember an issue coming up shortly after the release of 2.1.0-M1 related to one of the new Wagon implementations - WebDAV, maybe? I'm having some trouble remembering/finding that issue in my gmail, but we need to make sure that doesn't get left out of this release. If it means rolling back to an older wagon version, then let's do that. It's a regression in the SSH wagon, which I've not been able to reproduce and I never saw an issue filed for. We can wait and see what happens in the RC cycle. Thanks, Brett -- Brett Porter br...@apache.org http://blogs.exist.com/bporter/ - 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: svn commit: r744288 - in /maven/pom/trunk: asf/pom.xml maven/pom.xml
As far as I know, I've been using it but haven't cleared my repo. If you browse it's only going to show stuff that has been proxied, not the entire contents of p.a.o. On 2/18/09 10:41 AM, Brett Porter br...@apache.org wrote: On 15/02/2009, at 2:05 AM, Brian E. Fox wrote: This is probably moreso for the repositories elements - there's a chance some projects will be referring to snapshots in both places. The current one is a group that is logically combining the old and new repos, there's no reason not to use the r.a.o group for any project instead of p.a.o since it is the only place that will have all snapshots. Is this working? I only see a few projects in there. I also see metadata from external stuff (opensymphony) which seems wrong. Thanks, Brett -- Brett Porter br...@apache.org http://blogs.exist.com/bporter/ - 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
Vote for EclipseLink JavaDoc maven artifacts
Many projects that provide artifacts via maven often include only the binary and source artifacts. If a user is just starting with maven, it can be frustrating not being able to get the JavaDoc artifact in the same manner as the other variants. This is particularly important in GUIs (NetBeans, Eclipse, c.) which offer contextual linkage to documentation. I would like the EclipseLink development team to generate JavaDoc artifacts for their build products. I'm asking other maven users and developers to vote for this issue in the Eclipse issues list... Issue #: 249523 Direct link: https://bugs.eclipse.org/bugs/votes.cgi? action=show_userbug_id=249523#vote_249523 -David - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Maven Meetup In Amsterdam?
Hi guys, I got an email from Arje Cahn with a proposal to make a Maven GetTogether/Meetup during the ApacheCON in Amsterdam. I am very interested in such an event but I do feel that it will only make sense if more of the Maven developers are present at the conference. I know for sure me, Carlos and Wendy are going to be there. Anybody else planning to attend? If we get there more people we can easily setup a wiki page and announce a few sessions there. What do you think? Here is the email from Arje: == Hi all, I'm sending you this email because we've done GetTogethers / Meetups together, or have spoken about them somewhere in the past. If you feel I should be addressing different people, or different projects, I'd be grateful if you could point me to the right project and/or person! :) As you are probably very much aware of, the ApacheCon Europe is in about 7 weeks, in Amsterdam. I got a really nice offer from the ApacheCon producers. The Matterhorn rooms are available in the evenings for Meetup / GetTogether style events. This means we can host up to 3 evening Meetups, from 18:00 - 22:00, with our own program, on Monday evening and Tuesday evening, all within the ApacheCon venue (the Movenpick). Meetups happen after the trainings. This is in my opinion a much better opportunity than we had last year where we were 1) in a different location 2) conflicting with the hackaton 3) conflicting with trainings Grant, I'd love to hear your thoughts from your Lucene perspective. I know last year was unclear and I hope to be able to straighten that out with you this year. We're *not* organizing Lucene meetups without having Lucene people on board :) Potentially, we could have 6 Meetups in total. The rooms can hold up to 100 people each. Wifi, beamers, etc, is all taken care of. The question I have for you all, is whether you think you and / or your project would be interested in filling an evening. Can you organize between 20 and 100 people from your project, and put up an agenda with speakers and talks? Also, we'll have to come up with some sponsors. To give you an idea - last years Meetups were sponsored by 2 to 4 sponsors per project, paying roughly 1000 euro each to cover all costs. These sponsors will then become official ApacheCon Meetup sponsors and get marketed like that on the ApacheCon website. Right now, the planners have asked me to come up with a list of Apache projects that would be interested in the idea. If you're interested, please let me know ASAP, as I need to follow up on Monday to be able to be in time with all the marketing stuff going on around ApacheCon. Hope you like this idea as much as I do! -- Kind regards, Arjé Cahn -- Regards, Petar! Karlovo, Bulgaria. - - - - - - - - | Author @ Manning Publications. | Senior Solution Architect @ Unic | BGJUG-Bulgarian Java User Group Leader. | Apache Maven Developer. | Apache Jakarta PMC member. | Jakarta Cactus Lead Developer. | Codehaus Plexus Developer | Blogger: http://weblogs.java.net/blog/paranoiabla/ - - - - - - - - Public PGP Key at: https://keyserver1.pgp.com/vkd/DownloadKey.event?keyid=0x19658550C3110611 Key Fingerprint: A369 A7EE 61BC 93A3 CDFF 55A5 1965 8550 C311 0611
RE: svn commit: r744288 - in /maven/pom/trunk: asf/pom.xml maven/pom.xml
Seems to be proxying just fine: http://repository.apache.org/snapshots/org/apache/asyncweb/asyncweb-spri ng/maven-metadata.xml http://repository.apache.org/snapshots/org/apache/maven/maven-project-bu ilder/3.0-SNAPSHOT/maven-metadata.xml -Original Message- From: Brian E. Fox [mailto:bri...@reply.infinity.nu] Sent: Wednesday, February 18, 2009 1:52 PM To: Maven Developers List Subject: Re: svn commit: r744288 - in /maven/pom/trunk: asf/pom.xml maven/pom.xml As far as I know, I've been using it but haven't cleared my repo. If you browse it's only going to show stuff that has been proxied, not the entire contents of p.a.o. On 2/18/09 10:41 AM, Brett Porter br...@apache.org wrote: On 15/02/2009, at 2:05 AM, Brian E. Fox wrote: This is probably moreso for the repositories elements - there's a chance some projects will be referring to snapshots in both places. The current one is a group that is logically combining the old and new repos, there's no reason not to use the r.a.o group for any project instead of p.a.o since it is the only place that will have all snapshots. Is this working? I only see a few projects in there. I also see metadata from external stuff (opensymphony) which seems wrong. Thanks, Brett -- Brett Porter br...@apache.org http://blogs.exist.com/bporter/ - 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: Maven Meetup In Amsterdam?
Maria (Deng) is going to be there too It'd be a good idea. On Wed, Feb 18, 2009 at 11:35 AM, Petar Tahchiev paranoia...@gmail.com wrote: Hi guys, I got an email from Arje Cahn with a proposal to make a Maven GetTogether/Meetup during the ApacheCON in Amsterdam. I am very interested in such an event but I do feel that it will only make sense if more of the Maven developers are present at the conference. I know for sure me, Carlos and Wendy are going to be there. Anybody else planning to attend? If we get there more people we can easily setup a wiki page and announce a few sessions there. What do you think? Here is the email from Arje: == Hi all, I'm sending you this email because we've done GetTogethers / Meetups together, or have spoken about them somewhere in the past. If you feel I should be addressing different people, or different projects, I'd be grateful if you could point me to the right project and/or person! :) As you are probably very much aware of, the ApacheCon Europe is in about 7 weeks, in Amsterdam. I got a really nice offer from the ApacheCon producers. The Matterhorn rooms are available in the evenings for Meetup / GetTogether style events. This means we can host up to 3 evening Meetups, from 18:00 - 22:00, with our own program, on Monday evening and Tuesday evening, all within the ApacheCon venue (the Movenpick). Meetups happen after the trainings. This is in my opinion a much better opportunity than we had last year where we were 1) in a different location 2) conflicting with the hackaton 3) conflicting with trainings Grant, I'd love to hear your thoughts from your Lucene perspective. I know last year was unclear and I hope to be able to straighten that out with you this year. We're *not* organizing Lucene meetups without having Lucene people on board :) Potentially, we could have 6 Meetups in total. The rooms can hold up to 100 people each. Wifi, beamers, etc, is all taken care of. The question I have for you all, is whether you think you and / or your project would be interested in filling an evening. Can you organize between 20 and 100 people from your project, and put up an agenda with speakers and talks? Also, we'll have to come up with some sponsors. To give you an idea - last years Meetups were sponsored by 2 to 4 sponsors per project, paying roughly 1000 euro each to cover all costs. These sponsors will then become official ApacheCon Meetup sponsors and get marketed like that on the ApacheCon website. Right now, the planners have asked me to come up with a list of Apache projects that would be interested in the idea. If you're interested, please let me know ASAP, as I need to follow up on Monday to be able to be in time with all the marketing stuff going on around ApacheCon. Hope you like this idea as much as I do! -- Kind regards, Arjé Cahn -- Regards, Petar! Karlovo, Bulgaria. - - - - - - - - | Author @ Manning Publications. | Senior Solution Architect @ Unic | BGJUG-Bulgarian Java User Group Leader. | Apache Maven Developer. | Apache Jakarta PMC member. | Jakarta Cactus Lead Developer. | Codehaus Plexus Developer | Blogger: http://weblogs.java.net/blog/paranoiabla/ - - - - - - - - Public PGP Key at: https://keyserver1.pgp.com/vkd/DownloadKey.event?keyid=0x19658550C3110611 Key Fingerprint: A369 A7EE 61BC 93A3 CDFF 55A5 1965 8550 C311 0611 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [vote] release asf/maven/maven-plugins/maven-shared poms
+1 -- Olivier 2009/2/18 Brian E. Fox bri...@reply.infinity.nu: New parents need to be released with the new distributionManagement sections pointed at repository.apache.org: Apache Pom Diffs: http://svn.apache.org/viewvc/maven/pom/tags/apache-5/pom.xml?r1=639584r 2=745325diff_format=h Staged at: https://repository.apache.org/content/repositories/staging-484a2aeeabd6a 7/ Diffs: http://svn.apache.org/viewvc/maven/pom/tags/maven-parent-11/pom.xml?r1=7 39516r2=745330diff_format=h http://svn.apache.org/viewvc/maven/plugins/tags/maven-plugins-13/pom.xml ?r1=728991r2=745340diff_format=h http://svn.apache.org/viewvc/maven/shared/tags/maven-shared-components-1 1/pom.xml?r1=739774r2=745352diff_format=h Maven Parent and Maven-Plugins Parent Staged at: https://repository.apache.org/content/repositories/maven-staging-484a998 2bc6221/ 72hrs, +1 -- Brian Fox Apache Maven PMC http://www.sonatype.com/people/author/brian - 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 asf/maven/maven-plugins/maven-shared poms
+1 Brian E. Fox wrote: New parents need to be released with the new distributionManagement sections pointed at repository.apache.org: Apache Pom Diffs: http://svn.apache.org/viewvc/maven/pom/tags/apache-5/pom.xml?r1=639584r 2=745325diff_format=h Staged at: https://repository.apache.org/content/repositories/staging-484a2aeeabd6a 7/ Diffs: http://svn.apache.org/viewvc/maven/pom/tags/maven-parent-11/pom.xml?r1=7 39516r2=745330diff_format=h http://svn.apache.org/viewvc/maven/plugins/tags/maven-plugins-13/pom.xml ?r1=728991r2=745340diff_format=h http://svn.apache.org/viewvc/maven/shared/tags/maven-shared-components-1 1/pom.xml?r1=739774r2=745352diff_format=h Maven Parent and Maven-Plugins Parent Staged at: https://repository.apache.org/content/repositories/maven-staging-484a998 2bc6221/ 72hrs, +1 -- Brian Fox Apache Maven PMC http://www.sonatype.com/people/author/brian - 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
modello snapshot problem
I am modifying the bootstrap and am hitting a problem:
Generating sources for maven-model/src/main/mdo/maven.mdo
[java] Usage: modello model outputType output directory
modelVersion packageWithVersionuseJava5 [encoding]
Has modello CLI been changed recently? The bootstrap ant macro calls it
like:
sequential
java fork=fork classname=org.codehaus.modello.ModelloCli ...
arg file=@{file}/
arg value=@{mode}/
arg file=bootstrap/target/generated-sources/
arg value=@{version}/
arg value=false/
/java
/sequential
Problem see to be between modelVersion and packageWithVersion.
How should macro look like - what's the missing param?
The resolved modello snapshot is 1.0.1-20090215.121512-2
Thanks,
Oleg
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
RE: svn commit: r744288 - in /maven/pom/trunk: asf/pom.xml maven/pom.xml
Just testing the wrapping problem I seem to have: http://repository.apache.org/snapshots/org/apache/asyncweb/asyncweb-spri ng/maven-metadata.xml -Original Message- From: Brian E. Fox [mailto:bri...@reply.infinity.nu] Sent: Wednesday, February 18, 2009 2:37 PM To: Maven Developers List Subject: RE: svn commit: r744288 - in /maven/pom/trunk: asf/pom.xml maven/pom.xml Seems to be proxying just fine: http://repository.apache.org/snapshots/org/apache/asyncweb/asyncweb-spri ng/maven-metadata.xml http://repository.apache.org/snapshots/org/apache/maven/maven-project-bu ilder/3.0-SNAPSHOT/maven-metadata.xml -Original Message- From: Brian E. Fox [mailto:bri...@reply.infinity.nu] Sent: Wednesday, February 18, 2009 1:52 PM To: Maven Developers List Subject: Re: svn commit: r744288 - in /maven/pom/trunk: asf/pom.xml maven/pom.xml As far as I know, I've been using it but haven't cleared my repo. If you browse it's only going to show stuff that has been proxied, not the entire contents of p.a.o. On 2/18/09 10:41 AM, Brett Porter br...@apache.org wrote: On 15/02/2009, at 2:05 AM, Brian E. Fox wrote: This is probably moreso for the repositories elements - there's a chance some projects will be referring to snapshots in both places. The current one is a group that is logically combining the old and new repos, there's no reason not to use the r.a.o group for any project instead of p.a.o since it is the only place that will have all snapshots. Is this working? I only see a few projects in there. I also see metadata from external stuff (opensymphony) which seems wrong. Thanks, Brett -- Brett Porter br...@apache.org http://blogs.exist.com/bporter/ - 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 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
RE: [ANN] Maven 2.0.10 Release
The link to the release notes on http://maven.apache.org/release-notes.html still points to the 2.0.9 release notes. Reinhard -Original Message- From: briane...@gmail.com [mailto:briane...@gmail.com] On Behalf Of Brian Fox Sent: Wednesday, February 18, 2009 3:48 PM To: annou...@maven.apache.org; dev@maven.apache.org; Maven Users List; annou...@apache.org Subject: [ANN] Maven 2.0.10 Release The Maven team is pleased to announce the release of the Maven 2.0.10 This is a stable bug fix release and you can see the full list of issues fixed at http://maven.apache.org/release-notes.html Enjoy, -The Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
