[cle-release-team] Merging pom.xml and master/pom.xml

[Steve Swinsburg]

> It looks like in the pom you linked you still have the parent as master. I suppose removing base/master would also break some parent dependencies and require cleanup. 


That's a typo ;) The goal was to merge the two poms so there was no parent.

I just think it would be much easier overall to just have one pom. To change a version you go to master to change something else you go to the base pom. Seems overly complicated IMO.

cheers,
Steve


On 01/10/2011, at 4:33 AM, Matthew Jones wrote:

> We still have the two at Michigan, mostly because the master contains dependencies/versions and other junk while the main pom contains the profiles and modules. We don't even use the main pom, completely replacing it, but we do change versions in the master (custom kernel, local msgcntr, etc). 
> 
> I'd really like it if master used something like maven-properties-plugin [1] so then I wouldn't need to touch the master at all, just the file with the properties in it, and then we'd have 3 files.
> 
> It looks like in the pom you linked you still have the parent as master. I suppose removing base/master would also break some parent dependencies and require cleanup. 
> 
> The most annoying things for me as a deployer are bugs that we don't control: 
> http://jira.codehaus.org/browse/MRELEASE-707
> http://jira.codehaus.org/browse/MNG-624
> http://jira.codehaus.org/browse/MNG-3328
> 
> Hate all of those! ;)
> 
> [1] http://mojo.codehaus.org/properties-maven-plugin/plugin-info.html
> 
> On Fri, Sep 30, 2011 at 2:22 AM, David Horwitz <david.horwitz at uct.ac.za> wrote:
> +1
> 
> On 09/30/2011 07:47 AM, Steve Swinsburg wrote:
> > Hi all,
> >
> > Now are are moving towards more indie releases, what is the benefit of having two poms - the main pom.xml and master/pom.xml? I know that historically all tools used to use it as the parent, but that is no longer the case. In fact most tools now declare a pom from purepoms as their master.
> >
> > What do people think about cleaning this up and combining them? It should make things easier for pushing a button to deploy a release of the CLE.
> >
> > In one of our instances of Sakai, we have done exactly this. One pom.xml, no master. Combined.
> >
> > https://source.sakaiproject.org/svn//msub/anu.edu.au/services/2.8.x/
> >
> > cheers,
> > Steve
> >
> >
> >
> > _______________________________________________
> > cle-release-team mailing list
> > cle-release-team at collab.sakaiproject.org
> > http://collab.sakaiproject.org/mailman/listinfo/cle-release-team
> _______________________________________________
> cle-release-team mailing list
> cle-release-team at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/cle-release-team
> 
> _______________________________________________
> cle-release-team mailing list
> cle-release-team at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/cle-release-team

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/cle-release-team/attachments/20111001/082fb5a2/attachment-0006.html