Stefane Fermigier wrote: > Some people have some trouble with the m2eclipse plugin. I have > experimented with another method: > > Here is the basic workflow: > > - checkout nuxeo-ep from SVN (using command-line or TortoiseSVN). > - run 'mvn install' > - run 'mvn eclipse:eclipse' > - start Eclipse > > It has one drawback that I can think of of: you will have to re-run 'mvn > install' and 'mvn eclipse:eclipse' each time there are changes in the > dependencies (i.e. when one POM is updated). > > Feel free to try this approach and see if it better suits you. Your > feedback is welcomed.
A little side note about this. I believe NXP contributors should master maven, at least the sub-set of maven functionalities needed to be able to contribute to NXP, and consider this as a major target to reach as quickly as possible. As well, later on, when we will provide NXP components snapshots available from the Nuxeo maven repository, it won't be mandatory to import NXP source code in Eclipse to be able to do some third party components and thus the complexity of setting a Eclipse devel box will decrease. Thus, I'm not sure this method should be any useful in the future and should definitely be avoided by contributors. I encourage everyone to report bugs to the m2eclipse plugin team : http://jira.codehaus.org/browse/MNGECLIPSE At the moment this is not as well integrated to Eclipse compared to ant but that's part of the game. I'm sure the m2eclipse team will be glad to hear about the issues we are facing. I strongly believe choosing maven was a really smart move for the future of NXP. Any feedbacks welcome. Cheers, J. -- Julien Anguenot | Nuxeo R&D (Paris, France) Open Source ECM - http://www.nuxeo.com Nuxeo 5 : http://www.nuxeo.org Mobile: +33 (0) 6 72 57 57 66
signature.asc
Description: OpenPGP digital signature
_______________________________________________ ECM mailing list [email protected] http://lists.nuxeo.com/mailman/listinfo/ecm
