I took a quick look on the Genesis's root pom. As it seems to me the most of its configuration is irrelevant to Wink. Thus, I suggest coping the relevant configuration from Genesis to Wink and extend directly the Apache's pom.
On Thu, Jun 25, 2009 at 3:29 PM, 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 >> > >
