One being work to duplicate and maintain. Any reason you see to
object to just extending from it?
If you are worried about maintenance, I am also responsible for
Geronimo Genesis... the whole point of the project is to configure
well know working Maven2 configurations so that sub-projects can
consume them w/o needing all that xml muck to get things working
*always*.
--jason
On Jun 25, 2009, at 7:47 PM, Luciano Resende wrote:
How about copying that pom as the bases for the one used in Wink's
project and use the Apache one as Parent ?
On Thu, Jun 25, 2009 at 5:29 AM, Jason Dillon<[email protected]>
wrote:
Yes, that was what I was saying. Would save a lot of mvn
configuration
muck.
--jason
On Jun 25, 2009, at 6:33 PM, Michael Elman wrote:
Hi Jason,
By saying "using Geronimo's Genesis project for the projects root
poms"
do you mean that Wink should set the Geronimo's Genesis as Wink's
parent
pom?
Michael Elman
-----Original Message-----
From: Jason Dillon [mailto:[email protected]] On Behalf Of
Jason
Dillon
Sent: Wednesday, June 24, 2009 6:45 PM
To: [email protected]
Subject: Using Geronimo's Genesis
I would recommend using Geronimo's Genesis project for the projects
root poms. Genesis provides a lot of boilerplate Maven2
configuration
muck, greatly simplifying a projects poms while inheriting well
known
pluginn versions and configuration. There is already a published
release of Genesis 2.0 which can be easily consumed. I recommend
having the wink root pom extend from the appropriate Genesis Java
Flava to pick up the basic platform configuration.
--jason
--
Luciano Resende
Apache Tuscany, Apache PhotArk
http://people.apache.org/~lresende
http://lresende.blogspot.com/
