On 05/15/2012 12:41 PM, Hervé Esteguet wrote:
- We avoid polluting source with maven metadata.
You do not pollute: you add the necessary stuff to let anyone
perform a build locally in an equivalent way as your production
build. IMO XSLT is more pollution in a build process than a pom is.
Pom is straightforward, XSLT is workaround.
Tycho is not yet the native method used by eclipse to build bundles from the workbench. When it will be so, the presence of the pom.xml into a plugin source will be justified.
It is your native method to build. Giving your developers an
opportunity to see how the build will behave by typing "mvn install"
in a console is priceless.
- The releng engineer is not always allowed to modify the source repository which can be of different sources and natures. In fact the project could depends on others projects in which you just have a readonly access.
Too bad.
- Tycho make this approach easier, in most case the
modification of the pom parent generated by tycho will suffice to
configure the whole build process (an XSLT transformation do the
trick). There are small cases like the original subject of this
thread which complicated things.
You should really try a less constrained approach and generate your
pom once, commit them, and make release engineers committers on the
project they are working one. You'll quickly see a lot of
difficulties disappear.
My 2c.
|
