Re: Releasing maven-eclipse-plugin
Arnaud is the one with all the outstanding issues - he should comment if they can get bumped to the next version. All those unassigned look suitable for bumping. I'm not working on it and I won't be able soon I unassign all my issues. You can postpone issues you don't want to fix. You can try to deploy a SNAPSHOT and ask feedback from users before releasing it because our ITs doesn't validate many things (just that we always generate the same files, but it doesn't validate that you can use them in new/current eclipse versions). This plugin is widely used and the major part of users didn't upgrade to last releases because w have regressions in them. Thus if you want to have a wide usage of this new version you should take care to regressions found in 2 previous releases. cheers Arnaud
Re: Releasing maven-eclipse-plugin
I'm not in any dire rush to release the plugin, so I'll defer to you. If I can release it I will, otherwise I'll wait. On 2010-01-15, at 11:30 AM, Arnaud HERITIER wrote: Arnaud is the one with all the outstanding issues - he should comment if they can get bumped to the next version. All those unassigned look suitable for bumping. I'm not working on it and I won't be able soon I unassign all my issues. You can postpone issues you don't want to fix. You can try to deploy a SNAPSHOT and ask feedback from users before releasing it because our ITs doesn't validate many things (just that we always generate the same files, but it doesn't validate that you can use them in new/current eclipse versions). This plugin is widely used and the major part of users didn't upgrade to last releases because w have regressions in them. Thus if you want to have a wide usage of this new version you should take care to regressions found in 2 previous releases. cheers Arnaud Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl -- - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Releasing maven-eclipse-plugin
Hi, There are some issues left in the 2.8 for the maven-eclipse-plugin but if no one is going work on it then I'll just release it. I specifically want to release the addition I've made to the maven-eclipse-plugin which will stop the confusion among users where they think stuff generated by maven-eclipse-plugin is supported in M2Eclipse. There are projects like CXF that specifically tell users not to use M2Eclipse, which is fine, but I want support issues to fall back to those projects who want to support the maven-eclipse-plugin. More often then not they become the problem of the M2Eclipse developers. So this is really to partition the support where it belongs. It's a simple change, I just added a comment which we will detect in M2Eclipse and tell users what they are attempting are not supported. Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl -- - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Releasing maven-eclipse-plugin
Can we at least get a snapshot staged with your changes so I can double check that it doesn't break the CXF instructions? Specifically, we tell people not to use m2eclipse as it generally takes a couple HOURS to import CXF into m2eclipse and then the normal edit/save/run unit test cycle in m2eclipse takes minutes, not seconds.With the normal maven-eclipse-plugin setup and such, it's all MUCH MUCH faster.If the m2eclipse experience could match, I'd have no problems recommending it. But it's too painful right now. Dan On Thu January 14 2010 10:43:45 am Jason van Zyl wrote: Hi, There are some issues left in the 2.8 for the maven-eclipse-plugin but if no one is going work on it then I'll just release it. I specifically want to release the addition I've made to the maven-eclipse-plugin which will stop the confusion among users where they think stuff generated by maven-eclipse-plugin is supported in M2Eclipse. There are projects like CXF that specifically tell users not to use M2Eclipse, which is fine, but I want support issues to fall back to those projects who want to support the maven-eclipse-plugin. More often then not they become the problem of the M2Eclipse developers. So this is really to partition the support where it belongs. It's a simple change, I just added a comment which we will detect in M2Eclipse and tell users what they are attempting are not supported. Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl -- - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Daniel Kulp dk...@apache.org http://www.dankulp.com/blog - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Releasing maven-eclipse-plugin
On 2010-01-14, at 11:04 AM, Daniel Kulp wrote: Can we at least get a snapshot staged with your changes so I can double check that it doesn't break the CXF instructions? It's always staged. But my change in sum total is this: commentNO_M2ECLIPSE_SUPPORT: Project files created with the maven-eclipse-plugin are not supported in M2Eclipse./comment That's enough for us to do the detection we need. Specifically, we tell people not to use m2eclipse as it generally takes a couple HOURS to import CXF into m2eclipse and then the normal edit/save/run unit test cycle in m2eclipse takes minutes, not seconds.With the normal maven-eclipse-plugin setup and such, it's all MUCH MUCH faster.If the m2eclipse experience could match, I'd have no problems recommending it. But it's too painful right now. Dan On Thu January 14 2010 10:43:45 am Jason van Zyl wrote: Hi, There are some issues left in the 2.8 for the maven-eclipse-plugin but if no one is going work on it then I'll just release it. I specifically want to release the addition I've made to the maven-eclipse-plugin which will stop the confusion among users where they think stuff generated by maven-eclipse-plugin is supported in M2Eclipse. There are projects like CXF that specifically tell users not to use M2Eclipse, which is fine, but I want support issues to fall back to those projects who want to support the maven-eclipse-plugin. More often then not they become the problem of the M2Eclipse developers. So this is really to partition the support where it belongs. It's a simple change, I just added a comment which we will detect in M2Eclipse and tell users what they are attempting are not supported. Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl -- - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Daniel Kulp dk...@apache.org http://www.dankulp.com/blog Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl -- - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Releasing maven-eclipse-plugin
Same issue on my project using m2eclipse = 0.9.8 0.9.9 introduce many improvements that makes m2eclipse compliant with large multi-modules projets Nicolas 2010/1/14 Daniel Kulp dk...@apache.org Can we at least get a snapshot staged with your changes so I can double check that it doesn't break the CXF instructions? Specifically, we tell people not to use m2eclipse as it generally takes a couple HOURS to import CXF into m2eclipse and then the normal edit/save/run unit test cycle in m2eclipse takes minutes, not seconds.With the normal maven-eclipse-plugin setup and such, it's all MUCH MUCH faster.If the m2eclipse experience could match, I'd have no problems recommending it. But it's too painful right now. Dan On Thu January 14 2010 10:43:45 am Jason van Zyl wrote: Hi, There are some issues left in the 2.8 for the maven-eclipse-plugin but if no one is going work on it then I'll just release it. I specifically want to release the addition I've made to the maven-eclipse-plugin which will stop the confusion among users where they think stuff generated by maven-eclipse-plugin is supported in M2Eclipse. There are projects like CXF that specifically tell users not to use M2Eclipse, which is fine, but I want support issues to fall back to those projects who want to support the maven-eclipse-plugin. More often then not they become the problem of the M2Eclipse developers. So this is really to partition the support where it belongs. It's a simple change, I just added a comment which we will detect in M2Eclipse and tell users what they are attempting are not supported. Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl -- - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Daniel Kulp dk...@apache.org http://www.dankulp.com/blog - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Releasing maven-eclipse-plugin
On 2010-01-14, at 11:09 AM, nicolas de loof wrote: Same issue on my project using m2eclipse = 0.9.8 0.9.9 introduce many improvements that makes m2eclipse compliant with large multi-modules projets Folks can do whatever they want for their projects. I just want to stop the confusion. Use one method or the other and then users understand clearly where to go for support. Nicolas 2010/1/14 Daniel Kulp dk...@apache.org Can we at least get a snapshot staged with your changes so I can double check that it doesn't break the CXF instructions? Specifically, we tell people not to use m2eclipse as it generally takes a couple HOURS to import CXF into m2eclipse and then the normal edit/save/run unit test cycle in m2eclipse takes minutes, not seconds.With the normal maven-eclipse-plugin setup and such, it's all MUCH MUCH faster.If the m2eclipse experience could match, I'd have no problems recommending it. But it's too painful right now. Dan On Thu January 14 2010 10:43:45 am Jason van Zyl wrote: Hi, There are some issues left in the 2.8 for the maven-eclipse-plugin but if no one is going work on it then I'll just release it. I specifically want to release the addition I've made to the maven-eclipse-plugin which will stop the confusion among users where they think stuff generated by maven-eclipse-plugin is supported in M2Eclipse. There are projects like CXF that specifically tell users not to use M2Eclipse, which is fine, but I want support issues to fall back to those projects who want to support the maven-eclipse-plugin. More often then not they become the problem of the M2Eclipse developers. So this is really to partition the support where it belongs. It's a simple change, I just added a comment which we will detect in M2Eclipse and tell users what they are attempting are not supported. Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl -- - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Daniel Kulp dk...@apache.org http://www.dankulp.com/blog - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl --
Re: Releasing maven-eclipse-plugin
On Fri, Jan 15, 2010 at 2:38 AM, Jason van Zyl ja...@sonatype.com wrote: commentNO_M2ECLIPSE_SUPPORT: Project files created with the maven-eclipse-plugin are not supported in M2Eclipse./comment That's enough for us to do the detection we need. Are you saying that M2Eclipse will search for this comment and provide a warning as well? Can we also update the front page to indicate the M2Eclipse is no longer supported (and duplicate that in the FAQ) please? Arnaud is the one with all the outstanding issues - he should comment if they can get bumped to the next version. All those unassigned look suitable for bumping. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Releasing maven-eclipse-plugin
On 2010-01-14, at 6:41 PM, Barrie Treloar wrote: On Fri, Jan 15, 2010 at 2:38 AM, Jason van Zyl ja...@sonatype.com wrote: commentNO_M2ECLIPSE_SUPPORT: Project files created with the maven-eclipse-plugin are not supported in M2Eclipse./comment That's enough for us to do the detection we need. Are you saying that M2Eclipse will search for this comment and provide a warning as well? Yes, we'll tell the user we're not importing the project and why. Provide a pointer back to the maven-eclipse-plugin and where to get help. Can we also update the front page to indicate the M2Eclipse is no longer supported (and duplicate that in the FAQ) please? Sure you can. Arnaud is the one with all the outstanding issues - he should comment if they can get bumped to the next version. All those unassigned look suitable for bumping. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl -- - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Releasing maven-eclipse-plugin
On Thu, Jan 14, 2010 at 10:43 AM, Jason van Zyl ja...@sonatype.com wrote: Hi, There are some issues left in the 2.8 for the maven-eclipse-plugin but if no one is going work on it then I'll just release it. I have been trying to resolve issues using Maven 3 to build the plugin. I provided a patch for MECLIPSE-631, no one has applied it and I don't have karma. It would be nice if someone could apply that one at least before you release. Issue MECLIPSE-633 is the other one, which seems like it will take more time to sort out due to MNG-4523. -Peter
Re: Releasing maven-eclipse-plugin
On Fri, Jan 15, 2010 at 2:54 PM, Peter Lynch pe...@peterlynch.ca wrote: On Thu, Jan 14, 2010 at 10:43 AM, Jason van Zyl ja...@sonatype.com wrote: Hi, There are some issues left in the 2.8 for the maven-eclipse-plugin but if no one is going work on it then I'll just release it. I have been trying to resolve issues using Maven 3 to build the plugin. I provided a patch for MECLIPSE-631, no one has applied it and I don't have karma. It would be nice if someone could apply that one at least before you release. Issue MECLIPSE-633 is the other one, which seems like it will take more time to sort out due to MNG-4523. Can these wait for the next release cycle? I dont believe there is anyone actively watching new issues for the plugin. Your best bet is to ping the dev list with your issue and gather support for the bug and find someone willing to commit your patches. I have only been watching the list for Maven 3 and am not actively involved so I haven't attempted to use it to build m-e-p. I may have a few spare cycles shortly - is setting up my environment simple enough and documented somewhere? - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
