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
