On 03/06/2009 09:06 AM, Felix Meschberger wrote:
Hi,
Richard S. Hall schrieb:
Well, I am not against releasing this POM, but I had hoped we would
include File Install in our next pom release so it would get built with
everything else.
This is what I feared ;-)
Maybe we should split the parent pom part (shared plugin versions and
other setup) and the reactor part (<modules> tags) into two separate poms.
This way we do not have to release the parent pom everytime we add a
module. In fact the reactor POM need not be release at all.
Well, we don't actually have to release it, but we would have to have a
modified one in our trunk.
But, fine by me. I certainly don't know what Maven best practices are in
this area, so I am happy with whatever works.
-> richard
Regards
Felix
So, +1, but then let's add File Install...
-> richard
On 03/06/2009 05:28 AM, Carsten Ziegeler wrote:
Hi,
I've assembled a release candidate for the new parent pom here:
http://people.apache.org/~cziegeler/releases/felix/
The differences to the old parent pom are:
- Reverted the version of the assembly plugin to the version we used
before our parent pom 1.0.3 - as the latest version seems to have
problems.
Please cast your votes.
Thanks
Carsten
