[cle-release-team] pom review request

Wed Dec 21 20:57:47 PST 2011

If projects specify a parent pom that available in the sakai repository, then the only repository you need in projects is the sakai repo. Even the plugin repo could go in the parent (IIRC).

Something we might consider is getting only the parent pom into maven central. Then you don't need to specify any repo in any project. The sakai repo can be defined in the upstream parent and projects never need to worry about any of those specifics.

cheers,
Steve

On 22/12/2011, at 3:51 PM, Matthew Jones wrote:

> I agree, without having master in maven central, we cannot remove repositories section from indies. 
> 
> I think a possible plan was to look into getting all of our deployed artifacts into maven central rather than scp'ing them to source.sakaiproject.
> 
> I'm on vacation though for another week and only occasionally reading emails and didn't look into that, but can as soon as I'm back working again.
> 
> If we did this, then for sure we could remove many more sections from poms.
> 
> -Matthew
> 
> On Wed, Dec 21, 2011 at 11:48 PM, Noah Botimer <botimer at umich.edu> wrote:
> I can get with this. I also think we might consider getting our organizational/master POM into central at some point. But I'm mostly in favor of simplifying the average case quickly. If that means putting repo definitions back in, so be it.
> 
> Thanks,
> -Noah
> 
> On Dec 21, 2011, at 11:18 PM, Anthony Whyte <arwhyte at umich.edu> wrote:
> 
> > Removing the <repositories> and <pluginRepositories> elements from the search base pom (and perhaps all indie base poms--I'm assuming this was done universally, though I've not checked) is a mistake in my view, though a well-intentioned one.
> >
> > For example, I can download and install search-1.4.0-a01 on it's own against an absolutely empty .m2 repo (the same behavior applies for all earlier indie search versions).  External repos are specified.  I've told it where to look to find stuff.  I don't need to check it out into the sakai src folder.  I don't need to check out master first or anything else.
> >
> > search-1.4.0-b01 is crippled.  Try building it against an empty .m2 (I just tried to build it against my .m2 repo which does not include master-2.9.0-b01).  Since no repos are specified Maven defaults to the super pom (lurking above master) in its attempt to find the <parent> pom.  The super pom defaults to the Maven central repo [1].  Ain't gonna find CLE dependencies there.
> >
> > search r101783 over-reached in my view.  Not all pom overrides (e.g., described as "cleaning up most duplication") are bad.  <repositories> and <pluginRespositories> were defined in the search base pom for a good reason.  I highly recommend restoring them to all indie poms from which they were removed.
> >
> > Being able to check out a CLE project such as Search or BasicLTI into any folder on your machine and then build it against an empty .m2 repo is a highly useful trait.
> >
> > Anth
> >
> >
> > 1.4.0-a01
> > https://source.sakaiproject.org/svn/search/tags/search-1.4.0-a01/pom.xml
> >
> >
> > [1] with no repos specified other than maven central the build fails
> >
> > Luthuli:search-1.4.x arwhyte$ mvn -X clean install
> > + Error stacktraces are turned on.
> > Apache Maven 2.2.1 (r801777; 2009-08-06 15:16:01-0400)
> > Java version: 1.6.0_29
> > Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
> > Default locale: en_US, platform encoding: MacRoman
> > OS name: "mac os x" version: "10.6.8" arch: "x86_64" Family: "mac"
> > [DEBUG] Building Maven user-level plugin registry from: '/Users/arwhyte/.m2/plugin-registry.xml'
> > [DEBUG] Building Maven global-level plugin registry from: '/opt/maven/apache-maven-2.2.1/conf/plugin-registry.xml'
> > [INFO] Scanning for projects...
> > [DEBUG] Searching for parent-POM: org.sakaiproject:master:pom:2.9.0-b01 of project: org.sakaiproject.search:search:pom:1.4-SNAPSHOT in relative path: ../pom.xml
> > [DEBUG] Parent-POM: org.sakaiproject:master:pom:2.9.0-b01 not found in relative path: ../pom.xml
> > [DEBUG] Retrieving parent-POM: org.sakaiproject:master:pom:2.9.0-b01 for project: org.sakaiproject.search:search:pom:1.4-SNAPSHOT from the repository.
> > [DEBUG] Trying repository central
> > [DEBUG] Using Wagon implementation lightweight from default mapping for protocol http
> > [DEBUG] Checking for pre-existing User-Agent configuration.
> > [DEBUG] Adding User-Agent configuration.
> > [DEBUG] Connecting to repository: 'central' with url: 'http://repo1.maven.org/maven2'.
> > Downloading: http://repo1.maven.org/maven2/org/sakaiproject/master/2.9.0-b01/master-2.9.0-b01.pom
> > [DEBUG] Unable to locate resource in repository
> >
> >
> >
> >
> >
> >
> >
> > On Dec 21, 2011, at 8:55 AM, Maurer, Christopher Wayne wrote:
> >
> >> No worries.  We worked through (around) some of those issues and are
> >> making progress.  The one that I haven't been able to get around yet is
> >> search.
> >> A regular build seems to work just fine, but when I get to the
> >> release:prepare part, it fails with this:
> >>
> >> Missing:
> >> ----------
> >> 1) org.sakaiproject.search:search-util:jar:1.4.0-b01
> >>
> >> Try downloading the file manually from the project website.
> >>
> >> Then, install it using the command:
> >>     mvn install:install-file -DgroupId=org.sakaiproject.search
> >> -DartifactId=search-util -Dversion=1.4.0-b01 -Dpackaging=jar
> >> -Dfile=/path/to/file
> >>
> >> Alternatively, if you host your own repository you can deploy the file
> >> there:
> >>     mvn deploy:deploy-file -DgroupId=org.sakaiproject.search
> >> -DartifactId=search-util -Dversion=1.4.0-b01 -Dpackaging=jar
> >> -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
> >>
> >> Path to dependency:
> >>    1) org.sakaiproject.search:search-pack:sakai-component:1.4-SNAPSHOT
> >>    2) org.sakaiproject.search:search-impl:jar:1.4-SNAPSHOT
> >>    3) org.sakaiproject.search:search-util:jar:1.4.0-b01
> >>
> >> ----------
> >> 1 required artifact is missing.
> >>
> >> for artifact:
> >> org.sakaiproject.search:search-pack:sakai-component:1.4-SNAPSHOT
> >>
> >> from the specified remote repositories:
> >> default (http://repo1.maven.org/maven2),
> >> sakai-maven2-snapshots (http://source.sakaiproject.org/maven2-snapshots),
> >> central (http://repo1.maven.org/maven2),
> >> sakai-maven (http://source.sakaiproject.org/maven2)
> >>
> >>
> >>
> >> Chris
> >>
> >>
> >>
> >> On 12/21/11 7:30 AM, "Anthony Whyte" <arwhyte at umich.edu> wrote:
> >>
> >>> Chris--the time that I could allocate to looking at the poms you
> >>> requested of me was soaked up by tweeking Aaron's reflectutils and
> >>> getting 0.9.16 released.  I'll find some time to look at the other poms
> >>> today.
> >>>
> >>> Anth
> >>
> >>
> >>
> >
> >
> >
> _______________________________________________
> 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/20111222/446963f0/attachment-0006.html 