Jason, I believe that there are good concepts there that should be adopted. I rather we work on a copy of the poms, clean them from Geronimo propriety data and also have the ability to modify them if we like. In any case I believe we should first work toward creating the first build and then work on improving the existing poms.
--Eli -----Original Message----- From: Jason Dillon [mailto:[email protected]] On Behalf Of Jason Dillon Sent: Thursday, June 25, 2009 5:06 PM To: [email protected] Subject: Re: Using Geronimo's Genesis Yes, I know, those would have to be overridden of course. This pom is more about the plugin version configurations. The *-flava poms are more about what plugin configuration for a java version. So if Wink is going to be Java-5 then it should extend from genesis-java5-flava, or for Java 6, genesis-java6-flava. Then all that is needed past that is to redefine the mailings lists and scm much, which is expected. Its okay if you don't want to use Genesis... but using it could save a lot of xml configuration to maintain. --jason On Jun 25, 2009, at 8:43 PM, Baram, Eliezer wrote: > Jason > Do you relate to the pom that located in > https://svn.apache.org/repos/asf/geronimo/genesis/tags/genesis-2.0/pom.xml > ? > > This pom includes a lot of Geronimo propriety configuration like > Jira, mailing list, properties and modules. > > --Eli > > -----Original Message----- > From: Jason Dillon [mailto:[email protected]] On Behalf Of > Jason Dillon > Sent: Thursday, June 25, 2009 4:38 PM > To: [email protected] > Subject: Re: Using Geronimo's Genesis > > I actually think that Genesis is generally useful to any project at > the ASF using Maven2 or really any project using Maven2. Almost to > the point that it should be separate from Geronimo. > > Anyways, I just think it makes life easier for build folks, if you > want to duplicate and maintain, well that is your decision to make. > > /me just here to help out na. > > --jason > > > On Jun 25, 2009, at 8:18 PM, Michael Elman wrote: > >> 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 >>>> >>> >>> >
