I didn't know about the option to disable the m2e builder. I will give it a try and get back. It might take a while, but I will get back with my findings. Thanks much,
Sahoo On Wed, Aug 10, 2011 at 8:58 AM, Jason van Zyl <[email protected]> wrote: > If you want all of m2eclipse with no build support you can already disable > the m2e builder in the project properties. You will lose most of 3) as thats > a huge part of the lifecycle integration. Decoupling the configuration of > the project for initial setup from the incremental support would not be a > small amount of work and likely wouldn't work very well. It's not something > we're likely to do. But you're free to implement it and see if people like > it. We see only one way working well, and we really only have time to pursue > that. > > On Aug 9, 2011, at 10:38 PM, Sanjeeb Sahoo wrote: > > > > On Wed, Aug 10, 2011 at 2:05 AM, Jason van Zyl <[email protected]> wrote: > >> >> On Aug 9, 2011, at 4:21 PM, Sanjeeb Sahoo wrote: >> >> Let's say there are two kinds of users: >> a) Some who would like maven/ide plugin to be aware of the IDE build >> process and project output locations so that they can experience really fast >> edit/build/test cycle. >> >> b) Others who would like maven/ide plugin to delegate the build to maven >> completely. These users either don't face or don't care for the performance >> problem because of various reasons which are not important for this >> discussion. >> >> If m2e can provide an option to be configured to operate in mode #b, then >> neither group has to sacrifice. I will let m2e developers tell us how >> difficult it is to support this additional mode. >> >> >> If you want option b) then your use case is already supported. Use the >> maven-eclipse-plugin to generate your eclipse files and then just do your >> build with Maven configured as an external tool. Every time you make changes >> to your POMs you just generate the Eclipse files again. >> > > Pl help me understand what features won't be available if I chose to go > down this path. > 1) Will I be able to create maven projects/modules using easy to use > wizards available today with m2e or m2eclipse? I guess not. Then it becomes > a real stopper. > 2) Will I be able to use the POM editor? > 3) Will my eclipse project be correctly configured with maven folder > structure such as src/main/webapp instead of WebContent for web artifacts. > 4) Will the IDE prompt to update the POM with new dependencies when I add > new import in my .java file? > > If answer to these are YES, then I think it's a viable option for #b. > > Thank you, > Sahoo > _______________________________________________ > m2e-users mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/m2e-users > > > Thanks, > > Jason > > ---------------------------------------------------------- > Jason van Zyl > Founder, Apache Maven > http://twitter.com/jvanzyl > --------------------------------------------------------- > > To do two things at once is to do neither. > > -—Publilius Syrus, Roman slave, first century B.C. > > > > > _______________________________________________ > m2e-users mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/m2e-users > >
_______________________________________________ m2e-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/m2e-users
