|
|
DataNucleus Forum » List all forums » » Forum: General Development » » » Thread: Maven 2 - 1.2.0-beta-5 » » » » Post: Re: Maven 2 - 1.2.0-beta-5 |
Print at Mar 18, 2010 2:48:25 AM |
| Posted by andy at Aug 26, 2008 7:59:23 AM |
|
Re: Maven 2 - 1.2.0-beta-5 When someone finally provides a working M2 setup for DataNucleus they really ought to consider whether having a parent POM is of much use in these two places :- Plugin Development People developing DataNucleus are typically working on one plugin at a time, hence can build that plugin with a single command and no need for parentage. A shell script can provide whatever build automation is required. Use of parentage here complicates things because each plugin has its own lifecycle and hence its own space in SVN. When you branch plugin X then its source resides under pluginX/branches/{version}/ yet trunk for the plugin is at pluginX/trunk/ so the use of relativePath in the parent and plugin POMs don't work. Also dependencies are on a plugin-by-plugin basis, so no benefit from having a parent POM. Conclusion thus far : strip out parentage for plugins Testing People want to run all tests (in general). In this situation parentage can be useful since it would trigger the run of all tests, and the dependencies across the test projects are similar. In terms of SVN, all test scenarios are in the same part of SVN so when they are branched the parent POM is branched in the same area so relativePaths work still. Conclusion : leave parentage as is Comments ? ---------------------------------------- -Andy   |
|
Current timezone is GMT Mar 18, 2010 2:48:25 AM |