I figured something like: org.eclipse.dash/ eclipse/ - for the eclipse tlp (top level pom) coordinates of org.eclipse:eclipse:1,2,3,4 dash-parent/ - for the dash tlp, inherits from eclipse tlp, coordinates of org.eclipse.dash:dash-parent:1,2,3,4 eclipse-signing-maven-plugin/ - inherits dash tlp, typical versioning.. minerva/ - inherits dash tlp etc/ etc/
Dave and I discussed on irc about the tlp for eclipse, that it should be on the scale of the apache tlp under org.apache:apache:9 for setting broad organizational metadata. We could put it under dash as the place that is currently aggregating maven bits and pieces for eclipse infrastructure as it relates to maven. cheers, jesse -- jesse mcconnell [email protected] On Tue, May 10, 2011 at 19:50, Wayne Beaton <[email protected]> wrote: > My vote is for separate repos for separate functional areas. > > Wayne > > Chris Aniszczyk <[email protected]> wrote: > >>On Tue, May 10, 2011 at 5:27 PM, Jesse McConnell >><[email protected]> wrote: >>> my election status appears to be 'waiting for webmaster provisioning' >>> in the portal.. >> >>do we envision the repo do be just one repo? >> >>org.eclipse.dash/ >> m4e/ >> minerva/ >> maven-eclipse-signing-plugin/ >> ... >> pom.xml >> >>? >> >>-- >>Cheers, >> >>Chris Aniszczyk >>http://aniszczyk.org >>+1 512 961 6719 >>_______________________________________________ >>dash-dev mailing list >>[email protected] >>https://dev.eclipse.org/mailman/listinfo/dash-dev > _______________________________________________ > dash-dev mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/dash-dev > _______________________________________________ dash-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/dash-dev
