[gradebook2-dev] [Building Sakai] Problem with pom.xml at root of edu-services

[Maurer, Christopher Wayne]

Jim,
I think this is the same sort of issue that we just ran into at IU.  There are version ranges specified in the poms and apparently maven isn't dealing with them properly.  What we were seeing was a dependency that had a range like this:

<version>[2.7.0,2.8.0)</version>

…was pulling in the 2.8.0-alpha02 artifacts.
This caught us a bit off guard!  So, I expect that's the same thing you're seeing.  It's pulling in those alpha artifacts related to the 2.8 release instead of the highest 2.7 artifact.

Chris


From: Jim Eng <jimeng at umich.edu<mailto:jimeng at umich.edu>>
Date: Thu, 21 Oct 2010 14:46:24 -0400
To: Jim Eng <jimeng at umich.edu<mailto:jimeng at umich.edu>>
Cc: <gradebook2-dev at collab.sakaiproject.org<mailto:gradebook2-dev at collab.sakaiproject.org>>, David Pang <dxp at umich.edu<mailto:dxp at umich.edu>>, Sakai-Dev Developers <sakai-dev at collab.sakaiproject.org<mailto:sakai-dev at collab.sakaiproject.org>>
Subject: Re: [Building Sakai] Problem with pom.xml at root of edu-services

master/pom.xml defines this property:

<sakai.edu-services.version>1.0.6</sakai.edu-services.version>

I am not seeing any hardcoded versions in master, core-deploy, sections or gradebook2.



On Oct 21, 2010, at 2:39 PM, Jim Eng wrote:

Turns out there's another problem. Sakai 2.7.1 and 2.7.x seem to have a mix of versions for edu-services.  After cleaning out everything from ~/.m2/repository/org/sakaiproject and starting to build full sakai version 2.7.1, I find that sections-integrationsupport-1.0.6.jar has been put into my m2 repo.  But when gradebook2 tries to find the sections-api jar, it ends up using ${sakai.edu-services.version} when looking for that jar, and ${sakai.edu-services.version} seems to have a value of 1.1.0-a02 instead of 1.0.6.

I have been trying to unwind this to see why core-deply gets the 1.0.6 versions of various edu-services jars, but then the sections project seems to want the 1.1.0-a02 versions.

Jim



On Oct 20, 2010, at 2:08 PM, Anthony Whyte wrote:

I'll handle this.

Anth


On Oct 20, 2010, at 1:32 PM, Matthew Jones wrote:

Looks like Anthony removed this from master in November 2009? Searching email it's given people a lot of problems in various messages.

http://collab.sakaiproject.org/pipermail/sakai-dev/2010-January/005521.html

On Wed, Oct 20, 2010 at 1:29 PM, Jim Eng <jimeng at umich.edu<mailto:jimeng at umich.edu>> wrote:
What I meant was:  Could someone remove or update **the apache-repo repository element in** the edu-services pom.xml file?

:-)

On Oct 20, 2010, at 1:26 PM, Jim Eng wrote:

> The "repositories" tag in the root pom.xml file for edu-services includes the following repository element:
>
>        <repository>
>            <id>apache-repo</id>
>            <name>apache-repo</name>
>            <layout>default</layout>
>            <url>http://myfaces.zones.apache.org/dist/maven-repository</url>
>            <releases>
>                <enabled>true</enabled>
>            </releases>
>            <snapshots>
>                <enabled>false</enabled>
>            </snapshots>
>        </repository>
>
> This seems to be an invalid URL, and it causes problems when doing a full build of sakai with gradebook2.  The build hangs at this point for several minutes before timing out:
>
> [INFO] artifact org.sakaiproject.edu-services.sections:sections-integrationsupport: checking for updates from apache-repo
>
> After that long delay, the following messages are displayed:
>
> [WARNING] repository metadata for: 'artifact org.sakaiproject.edu-services.sections:sections-integrationsupport' could not be retrieved from repository: apache-repo due to an error: Operation timed out
> [INFO] Repository 'apache-repo' will be blacklisted
>
> A similar repository element has been commented out in the master/pom.xml file.  Could someone remove or update the edu-services pom.xml file?
>
> Thanks.
>
> Jim
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org<mailto:sakai-dev at collab.sakaiproject.org>
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>
> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org<mailto:sakai-dev-unsubscribe at collab.sakaiproject.org> with a subject of "unsubscribe"
>
>

_______________________________________________
sakai-dev mailing list
sakai-dev at collab.sakaiproject.org<mailto:sakai-dev at collab.sakaiproject.org>
http://collab.sakaiproject.org/mailman/listinfo/sakai-dev

TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org<mailto:sakai-dev-unsubscribe at collab.sakaiproject.org> with a subject of "unsubscribe"

_______________________________________________
sakai-dev mailing list
sakai-dev at collab.sakaiproject.org<mailto:sakai-dev at collab.sakaiproject.org>
http://collab.sakaiproject.org/mailman/listinfo/sakai-dev

TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org<mailto:sakai-dev-unsubscribe at collab.sakaiproject.org> with a subject of "unsubscribe"


_______________________________________________
sakai-dev mailing list
sakai-dev at collab.sakaiproject.org<mailto:sakai-dev at collab.sakaiproject.org>
http://collab.sakaiproject.org/mailman/listinfo/sakai-dev

TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org<mailto:sakai-dev-unsubscribe at collab.sakaiproject.org> with a subject of "unsubscribe"

_______________________________________________ sakai-dev mailing list sakai-dev at collab.sakaiproject.org<mailto:sakai-dev at collab.sakaiproject.org> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org<mailto:sakai-dev-unsubscribe at collab.sakaiproject.org> with a subject of "unsubscribe"
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/gradebook2-dev/attachments/20101021/6154f0c9/attachment-0001.html