[Building Sakai] Sitestats 2.1.0 in Sakai 2.6.x

[Nuno Fernandes]

Hi Matthew,


Yes - you just need to change the pom's in order to run 2.1.0 with Sakai
2.6.x. We did that with 2.1 and are doing the same using 2.2-SNAPSHOT with
Sakai 2.7.1...

Thanks,
Nuno

On Fri, Oct 22, 2010 at 8:00 PM,
<sakai-dev-request at collab.sakaiproject.org>wrote:

> Send sakai-dev mailing list submissions to
>        sakai-dev at collab.sakaiproject.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>        http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
> or, via email, send a message with subject or body 'help' to
>        sakai-dev-request at collab.sakaiproject.org
>
> You can reach the person managing the list at
>        sakai-dev-owner at collab.sakaiproject.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of sakai-dev digest..."
>
>
> Today's Topics:
>
>   1. Re: InnoDB Question (Bryan Bakotich)
>   2. Re: Problem with pom.xml at root of edu-services
>      (Maurer, Christopher Wayne)
>   3. Re: Problem with pom.xml at root of edu-services (Jim Eng)
>   4. Re: Problem with pom.xml at root of edu-services (Jim Eng)
>   5. Re: Problem with pom.xml at root of edu-services (Noah Botimer)
>   6. Re: Problem with pom.xml at root of edu-services (Jim Eng)
>   7. Re: Problem with pom.xml at root of edu-services (Steve Swinsburg)
>   8. Re: Problem with pom.xml at root of edu-services (Jim Eng)
>   9. Re: Problem with pom.xml at root of edu-services (Anthony Whyte)
>  10. Re: Problem with pom.xml at root of edu-services (Anthony Whyte)
>  11. Re: Problem with pom.xml at root of edu-services (Jim Eng)
>  12. Re: Problem with pom.xml at root of edu-services (Anthony Whyte)
>  13. Re: Problem with pom.xml at root of edu-services (Anthony Whyte)
>  14. PostgreSQL support (Jacek Bilski)
>  15. How to fix this problem with Tests&Quizzes and    Chat tools
>      (Tin Nguyen)
>  16. Re: Displaying details in Resources' table view (Adam Marshall)
>  17. Sitestats 2.1.0 in Sakai 2.6.x (Matthew Buckett)
>  18. math editor for fckeditor (John Bush)
>  19. Re: math editor for fckeditor (Qian, Zhen)
>  20. Re: How to fix this problem with Tests&Quizzes and Chat tools
>      (Karen Tsao)
>  21. Re: math editor for fckeditor (Richwine, Brian L)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 21 Oct 2010 12:01:25 -0700
> From: Bryan Bakotich <bakotibj at plu.edu>
> Subject: Re: [Building Sakai] InnoDB Question
> To: Sam Ottenhoff <ottenhoff at longsight.com>
> Cc: sakai-dev at collab.sakaiproject.org
> Message-ID:
>        <AANLkTim2DL0bvFyxLuLuShiZBOw=iV2KzE5gF45486wf at mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> I think the change in that JIRA makes it so tables that say ENGINE=INNODB
> in
> the create statement actually get created as InnoDB tables. I just checked
> a
> fresh 2.7.x install with no add-on tools and 199 out of 312 tables are
> InnoDB. The rest are MyISAM.
>
> -Bryan
>
> On Thu, Oct 21, 2010 at 11:53 AM, Sam Ottenhoff <ottenhoff at longsight.com
> >wrote:
>
> >  I thought there was a change to the default Hibernate dialect in this
> > JIRA:
> >
> >   http://jira.sakaiproject.org/browse/SAK-10699
> >
> > But yes, I support documentation changes also.  I have seen this happen
> to
> > multiple institutions.  I agree that installation instructions should
> offer
> > more explicit warnings about the MySQL engine.
> >
> > --Sam
> >
> >
> > On 10/21/2010 2:48 PM, Bryan Bakotich wrote:
> >
> > Sam,
> >
> > Thanks for the info, I will give that a shot on our dev server.
> >
> > If all tables should be InnoDB I think we should modify the documentation
> > to explicitly say that. It seems a little ambiguous how it's worded now
> > especially since a good portion of the tables are created as InnoDB even
> if
> > it isn't the default storage engine.
> >
> > Maybe we could add something like this (which is a little info note in
> > atlassian's confluence setup guide):
> > *It is* *highly recommended* *that you only use the InnoDB storage engine
> > with Confluence. Avoid using the MyISAM storage engine as this can lead
> to
> > data corruption.*
> >
> > Or we could append something like &sessionVariables=storage_engine=InnoDB
> > to the jdbc url in the default sakai.properties file so that people don't
> > have to modify the default storage engine.
> >
> > Any thoughts?
> >
> > -Bryan
> >
> > On Wed, Oct 20, 2010 at 5:48 PM, Sam Ottenhoff <ottenhoff at longsight.com
> >wrote:
> >
> >>  I strongly recommend using only InnoDB.  All tables should be InnoDB.
> >> Using only InnoDB will provide transaction support, foreign key support,
> and
> >> will make sure you are running on the same database engine as other
> Sakai
> >> MySQL users.
> >>
> >> I recommend stopping Sakai, doing a MySQL database dump, changing all
> >> table creation stanzas to use InnoDB, and re-importing the database.
> >> Finally, I recommend starting a clean instance of Sakai 2.7 to compare
> it
> >> your newly-converted InnoDB database.  If you have any missing foreign
> keys
> >> in your converted database, you will have to resolve duplicate data
> manually
> >> and apply the foreign-key constraints manually.
> >>
> >> --Sam
> >>
> >>
> >> On 10/20/2010 8:31 PM, Bryan Bakotich wrote:
> >>
> >>  Hi,
> >>
> >> On the Sakai 2.7 install guide it says this about MySQL and InnoDB:
> Sakai
> >> requires transaction support. In the case of MySQL you must implement
> the
> >> InnoDB storage engine to ensure proper transaction handling.
> >>
> >> Does this mean that InnoDB just needs to be an available storage engine
> or
> >> should this be the default storage engine so that all tables are InnoDB?
> I
> >> am asking this because our current 2.6.x database is a mix of MyISAM and
> >> InnoDB and I just ran into an error while running the
> >> sakai_2_7_0_mysql_conversion.sql script because one of our existing
> tables
> >> was MyISAM and it needed to be InnoDB.
> >> I also recently did a fresh 2.7 install for a non-profit and their
> >> database has a lot more InnoDB tables than ours (Our current
> installation
> >> has 118, fresh install has 199).
> >>
> >> So should all tables be InnoDB or just a few? Is it documented anywhere
> >> what tables should be what storage engine so I can make sure our
> database is
> >> correct? Thanks for the help!
> >>
> >> -Bryan
> >>
> >> --
> >> Bryan Bakotich
> >> Open Source Implementation Specialist
> >> Digital Media Center, Information & Technology Services
> >> Pacific Lutheran University
> >> Tacoma, WA 98447-0013
> >> Phone: 253-536-5021
> >>
> >>
> >> _______________________________________________
> >> sakai-dev mailing listsakai-dev at collab.sakaiproject.orghttp://
> collab.sakaiproject.org/mailman/listinfo/sakai-dev
> >>
> >> TO UNSUBSCRIBE: send email to
> sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of
> "unsubscribe"
> >>
> >>
> >> _______________________________________________
> >> sakai-dev mailing list
> >> 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 with a subject of
> >> "unsubscribe"
> >>
> >
> >
> >
> > --
> > Bryan Bakotich
> > Open Source Implementation Specialist
> > Digital Media Center, Information & Technology Services
> > Pacific Lutheran University
> > Tacoma, WA 98447-0013
> > Phone: 253-536-5021
> >
> >
>
>
> --
> Bryan Bakotich
> Open Source Implementation Specialist
> Digital Media Center, Information & Technology Services
> Pacific Lutheran University
> Tacoma, WA 98447-0013
> Phone: 253-536-5021
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20101021/f1b96c7c/attachment-0001.html
>
> ------------------------------
>
> Message: 2
> Date: Thu, 21 Oct 2010 19:02:29 +0000
> From: "Maurer, Christopher Wayne" <chmaurer at iupui.edu>
> Subject: Re: [Building Sakai] Problem with pom.xml at root of
>        edu-services
> To: Jim Eng <jimeng at umich.edu>
> Cc: "gradebook2-dev at collab.sakaiproject.org"
>        <gradebook2-dev at collab.sakaiproject.org>, David Pang <dxp at umich.edu
> >,
>        Sakai-Dev Developers <sakai-dev at collab.sakaiproject.org>
> Message-ID: <C8E605C5.3050%chmaurer at iupui.edu<C8E605C5.3050%25chmaurer at iupui.edu>
> >
> Content-Type: text/plain; charset="windows-1252"
>
> 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/sakai-dev/attachments/20101021/6154f0c9/attachment-0001.html
>
> ------------------------------
>
> Message: 3
> Date: Thu, 21 Oct 2010 15:05:24 -0400
> From: Jim Eng <jimeng at umich.edu>
> Subject: Re: [Building Sakai] Problem with pom.xml at root of
>        edu-services
> To: Jim Eng <jimeng at umich.edu>
> Cc: gradebook2-dev at collab.sakaiproject.org, David Pang
>        <dxp at umich.edu>,        Sakai-Dev Developers
>        <sakai-dev at collab.sakaiproject.org>
> Message-ID: <0672DB75-BD7F-43C5-ABDC-60927951ABFF at umich.edu>
> Content-Type: text/plain; charset="us-ascii"
>
> Is it possible that we are downloading
> org.sakaiproject.edu-services.gradebook:gradebook-service-impl:jar:1.0.6 and
> that somehow depends on
> org.sakaiproject.edu-services.sections:sections-integrationsupport:jar:1.1.0-a02?
>
> The relevant part of the error message is shown below.  This occurs while
> trying to build gradebook2 in a fresh checkout of sakai 2.7.1 (also in sakai
> 2.7.x):
>
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Failed to resolve artifact.
>
> Missing:
> ----------
> 1)
> org.sakaiproject.edu-services.sections:sections-integrationsupport:jar:1.1.0-a02
>
>  Try downloading the file manually from:
>      http://source.sakaiproject.org/maven2/
>
>  Then, install it using the command:
>      mvn install:install-file
> -DgroupId=org.sakaiproject.edu-services.sections
> -DartifactId=sections-integrationsupport -Dversion=1.1.0-a02 -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.edu-services.sections
> -DartifactId=sections-integrationsupport -Dversion=1.1.0-a02 -Dpackaging=jar
> -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
>
>  Path to dependency:
>        1) org.sakaiproject.gradebook2:gradebook2-model:jar:1.3.0-SNAPSHOT
>        2)
> org.sakaiproject.edu-services.gradebook:gradebook-service-impl:jar:1.0.6
>        3)
> org.sakaiproject.edu-services.sections:sections-integrationsupport:jar:1.1.0-a02
>
> ----------
> 1 required artifact is missing.
>
>
>
>
> On Oct 21, 2010, at 2:46 PM, Jim Eng wrote:
>
> > 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> 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
> >>>> > http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
> >>>> >
> >>>> > TO UNSUBSCRIBE: send email to
> sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of
> "unsubscribe"
> >>>> >
> >>>> >
> >>>>
> >>>> _______________________________________________
> >>>> sakai-dev mailing list
> >>>> 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 with a subject of
> "unsubscribe"
> >>>>
> >>>> _______________________________________________
> >>>> sakai-dev mailing list
> >>>> 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 with a subject of
> "unsubscribe"
> >>>
> >>
> >> _______________________________________________
> >> sakai-dev mailing list
> >> 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 with a subject of
> "unsubscribe"
> >
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20101021/c196606a/attachment-0001.html
>
> ------------------------------
>
> Message: 4
> Date: Thu, 21 Oct 2010 15:23:41 -0400
> From: Jim Eng <jimeng at umich.edu>
> Subject: Re: [Building Sakai] Problem with pom.xml at root of
>        edu-services
> To: "Maurer, Christopher Wayne" <chmaurer at iupui.edu>
> Cc: "gradebook2-dev at collab.sakaiproject.org"
>        <gradebook2-dev at collab.sakaiproject.org>, David Pang <dxp at umich.edu
> >,
>        Sakai-Dev Developers <sakai-dev at collab.sakaiproject.org>
> Message-ID: <C9783BC1-23D3-483D-AAFE-570B572D27ED at umich.edu>
> Content-Type: text/plain; charset="windows-1252"
>
> Thanks, Chris. It looks like you are correct.  The last element in the
> dependencyManagement section of this pom.xml uses a range:
>
>
> https://source.sakaiproject.org/svn//edu-services/tags/edu-services-1.0.6/pom.xml
>
> The gradebook2 build process depends on the jar, which is downloaded rather
> than built locally.  That pom.xml file also includes a repository element
> for apache-repo with a bogus URL.  I don't think we'll be able to build
> gradebook2 locally until that 1.0.6 jar is rebuilt without that range of
> versions and without the apache-repo element.
>
> Jim
>
>
> On Oct 21, 2010, at 3:02 PM, Maurer, Christopher Wayne wrote:
>
> > 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>
> > Date: Thu, 21 Oct 2010 14:46:24 -0400
> > To: Jim Eng <jimeng at umich.edu>
> > Cc: <gradebook2-dev at collab.sakaiproject.org>, David Pang <dxp at umich.edu>,
> Sakai-Dev Developers <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> 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
> >>>>> > http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
> >>>>> >
> >>>>> > TO UNSUBSCRIBE: send email to
> sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of
> "unsubscribe"
> >>>>> >
> >>>>> >
> >>>>>
> >>>>> _______________________________________________
> >>>>> sakai-dev mailing list
> >>>>> 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 with a subject of
> "unsubscribe"
> >>>>
> >>>> _______________________________________________
> >>>> sakai-dev mailing list
> >>>> 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 with a subject of
> "unsubscribe"
> >>>
> >>
> >> _______________________________________________
> >> sakai-dev mailing list
> >> 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 with a subject of
> "unsubscribe"
> >
> > _______________________________________________ sakai-dev mailing list
> 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 with a subject
> of "unsubscribe"
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20101021/5ae5f170/attachment-0001.html
>
> ------------------------------
>
> Message: 5
> Date: Thu, 21 Oct 2010 15:24:59 -0400
> From: Noah Botimer <botimer at umich.edu>
> Subject: Re: [Building Sakai] Problem with pom.xml at root of
>        edu-services
> To: sakai-dev <sakai-dev at collab.sakaiproject.org>
> Message-ID: <9E57460B-1F19-4F91-A89E-BA00CF45B0F7 at umich.edu>
> Content-Type: text/plain; charset="us-ascii"
>
> Maybe we can start up a FAQ / Troubleshooting Guide?
>
> We've been seeing a lot of these build / deployment / pom problems tripping
> up some of our most experienced people, as well as newcomers.
>
> There's a lot of complexity in our packaging and it's hard to find good
> answers, check for (ill-)advised patterns, or debug problems quickly.
> Burning a half day of senior developer time at a crack on getting a build
> going isn't really a best practice.
>
> Thanks,
> -Noah
>
> On Oct 21, 2010, at 3:05 PM, Jim Eng wrote:
>
> > Is it possible that we are downloading
> org.sakaiproject.edu-services.gradebook:gradebook-service-impl:jar:1.0.6 and
> that somehow depends on
> org.sakaiproject.edu-services.sections:sections-integrationsupport:jar:1.1.0-a02?
> >
> > The relevant part of the error message is shown below.  This occurs while
> trying to build gradebook2 in a fresh checkout of sakai 2.7.1 (also in sakai
> 2.7.x):
> >
> > [INFO]
> ------------------------------------------------------------------------
> > [ERROR] BUILD ERROR
> > [INFO]
> ------------------------------------------------------------------------
> > [INFO] Failed to resolve artifact.
> >
> > Missing:
> > ----------
> > 1)
> org.sakaiproject.edu-services.sections:sections-integrationsupport:jar:1.1.0-a02
> >
> >   Try downloading the file manually from:
> >       http://source.sakaiproject.org/maven2/
> >
> >   Then, install it using the command:
> >       mvn install:install-file
> -DgroupId=org.sakaiproject.edu-services.sections
> -DartifactId=sections-integrationsupport -Dversion=1.1.0-a02 -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.edu-services.sections
> -DartifactId=sections-integrationsupport -Dversion=1.1.0-a02 -Dpackaging=jar
> -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
> >
> >   Path to dependency:
> >       1) org.sakaiproject.gradebook2:gradebook2-model:jar:1.3.0-SNAPSHOT
> >       2)
> org.sakaiproject.edu-services.gradebook:gradebook-service-impl:jar:1.0.6
> >       3)
> org.sakaiproject.edu-services.sections:sections-integrationsupport:jar:1.1.0-a02
> >
> > ----------
> > 1 required artifact is missing.
> >
> >
> >
> >
> > On Oct 21, 2010, at 2:46 PM, Jim Eng wrote:
> >
> >> 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> 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
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20101021/d5f1baa1/attachment-0001.html
>
> ------------------------------
>
> Message: 6
> Date: Thu, 21 Oct 2010 16:21:19 -0400
> From: Jim Eng <jimeng at umich.edu>
> Subject: Re: [Building Sakai] Problem with pom.xml at root of
>        edu-services
> To: Jim Eng <jimeng at umich.edu>
> Cc: "gradebook2-dev at collab.sakaiproject.org"
>        <gradebook2-dev at collab.sakaiproject.org>,       Sakai-Dev
> Developers
>        <sakai-dev at collab.sakaiproject.org>,    David Pang <dxp at umich.edu>
> Message-ID: <CE6071AA-5FA6-4B0D-B0C5-2A21192CAF47 at umich.edu>
> Content-Type: text/plain; charset="windows-1252"
>
> We need to eliminate the apache-repo references in all pom.xml files, but
> that is really just an annoyance that mostly slows down the build process
> for developers.
>
> On the other hand, the use of ranges for versions in poms for "released"
> versions of a project should be considered a blocker.  In this case, it
> looks like the correct version would have been "${project.version}" rather
> than "[1.0.0-1.1.0)".
>
> What is needed to get this fixed?  Does it require building edu-services
> 1.0.7 and replacing all references to edu-services 1.0.6 with edu-services
> 1.0.7?
>
> Jim
>
>
> On Oct 21, 2010, at 3:23 PM, Jim Eng wrote:
>
> > Thanks, Chris. It looks like you are correct.  The last element in the
> dependencyManagement section of this pom.xml uses a range:
> >
> >
> https://source.sakaiproject.org/svn//edu-services/tags/edu-services-1.0.6/pom.xml
> >
> > The gradebook2 build process depends on the jar, which is downloaded
> rather than built locally.  That pom.xml file also includes a repository
> element for apache-repo with a bogus URL.  I don't think we'll be able to
> build gradebook2 locally until that 1.0.6 jar is rebuilt without that range
> of versions and without the apache-repo element.
> >
> > Jim
> >
> >
> > On Oct 21, 2010, at 3:02 PM, Maurer, Christopher Wayne wrote:
> >
> >> 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>
> >> Date: Thu, 21 Oct 2010 14:46:24 -0400
> >> To: Jim Eng <jimeng at umich.edu>
> >> Cc: <gradebook2-dev at collab.sakaiproject.org>, David Pang <dxp at umich.edu>,
> Sakai-Dev Developers <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> 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
> >>>>>> > http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
> >>>>>> >
> >>>>>> > TO UNSUBSCRIBE: send email to
> sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of
> "unsubscribe"
> >>>>>> >
> >>>>>> >
> >>>>>>
> >>>>>> _______________________________________________
> >>>>>> sakai-dev mailing list
> >>>>>> 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 with a subject of
> "unsubscribe"
> >>>>>
> >>>>> _______________________________________________
> >>>>> sakai-dev mailing list
> >>>>> 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 with a subject of
> "unsubscribe"
> >>>>
> >>>
> >>> _______________________________________________
> >>> sakai-dev mailing list
> >>> 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 with a subject of
> "unsubscribe"
> >>
> >> _______________________________________________ sakai-dev mailing list
> 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 with a subject
> of "unsubscribe"
> >
> > _______________________________________________
> > sakai-dev mailing list
> > 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 with a subject of
> "unsubscribe"
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20101021/55ace428/attachment-0001.html
>
> ------------------------------
>
> Message: 7
> Date: Fri, 22 Oct 2010 07:51:42 +1100
> From: Steve Swinsburg <steve.swinsburg at gmail.com>
> Subject: Re: [Building Sakai] Problem with pom.xml at root of
>        edu-services
> To: Jim Eng <jimeng at umich.edu>
> Cc: "gradebook2-dev at collab.sakaiproject.org"
>        <gradebook2-dev at collab.sakaiproject.org>,       Sakai-Dev
> Developers
>        <sakai-dev at collab.sakaiproject.org>,    David Pang <dxp at umich.edu>
> Message-ID: <047DCBE0-90BD-46A3-BA99-8ABBA74A1724 at gmail.com>
> Content-Type: text/plain; charset="windows-1252"
>
> When building 2.7, you need to blow away that portion of your local Maven
> repo so that it doesn't have the newer 2.8 artifacts in there.
>
> But I agree that a specific version should be used so as to eliminate this
> issue.
>
> cheers,
> Steve
>
>
>
> On 22/10/2010, at 7:21 AM, Jim Eng wrote:
>
> > We need to eliminate the apache-repo references in all pom.xml files, but
> that is really just an annoyance that mostly slows down the build process
> for developers.
> >
> > On the other hand, the use of ranges for versions in poms for "released"
> versions of a project should be considered a blocker.  In this case, it
> looks like the correct version would have been "${project.version}" rather
> than "[1.0.0-1.1.0)".
> >
> > What is needed to get this fixed?  Does it require building edu-services
> 1.0.7 and replacing all references to edu-services 1.0.6 with edu-services
> 1.0.7?
> >
> > Jim
> >
> >
> > On Oct 21, 2010, at 3:23 PM, Jim Eng wrote:
> >
> >> Thanks, Chris. It looks like you are correct.  The last element in the
> dependencyManagement section of this pom.xml uses a range:
> >>
> >>
> https://source.sakaiproject.org/svn//edu-services/tags/edu-services-1.0.6/pom.xml
> >>
> >> The gradebook2 build process depends on the jar, which is downloaded
> rather than built locally.  That pom.xml file also includes a repository
> element for apache-repo with a bogus URL.  I don't think we'll be able to
> build gradebook2 locally until that 1.0.6 jar is rebuilt without that range
> of versions and without the apache-repo element.
> >>
> >> Jim
> >>
> >>
> >> On Oct 21, 2010, at 3:02 PM, Maurer, Christopher Wayne wrote:
> >>
> >>> 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>
> >>> Date: Thu, 21 Oct 2010 14:46:24 -0400
> >>> To: Jim Eng <jimeng at umich.edu>
> >>> Cc: <gradebook2-dev at collab.sakaiproject.org>, David Pang <
> dxp at umich.edu>, Sakai-Dev Developers <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> 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
> >>>>>>> > http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
> >>>>>>> >
> >>>>>>> > TO UNSUBSCRIBE: send email to
> sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of
> "unsubscribe"
> >>>>>>> >
> >>>>>>> >
> >>>>>>>
> >>>>>>> _______________________________________________
> >>>>>>> sakai-dev mailing list
> >>>>>>> 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 with a subject of
> "unsubscribe"
> >>>>>>
> >>>>>> _______________________________________________
> >>>>>> sakai-dev mailing list
> >>>>>> 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 with a subject of
> "unsubscribe"
> >>>>>
> >>>>
> >>>> _______________________________________________
> >>>> sakai-dev mailing list
> >>>> 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 with a subject of
> "unsubscribe"
> >>>
> >>> _______________________________________________ sakai-dev mailing list
> 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 with a subject
> of "unsubscribe"
> >>
> >> _______________________________________________
> >> sakai-dev mailing list
> >> 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 with a subject of
> "unsubscribe"
> >
> > _______________________________________________
> > sakai-dev mailing list
> > 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 with a subject of
> "unsubscribe"
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20101022/d5848933/attachment-0001.html
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: smime.p7s
> Type: application/pkcs7-signature
> Size: 3689 bytes
> Desc: not available
> Url :
> http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20101022/d5848933/attachment-0001.bin
>
> ------------------------------
>
> Message: 8
> Date: Thu, 21 Oct 2010 17:50:55 -0400
> From: Jim Eng <jimeng at umich.edu>
> Subject: Re: [Building Sakai] Problem with pom.xml at root of
>        edu-services
> To: Steve Swinsburg <steve.swinsburg at gmail.com>
> Cc: "gradebook2-dev at collab.sakaiproject.org"
>        <gradebook2-dev at collab.sakaiproject.org>,       Sakai-Dev
> Developers
>        <sakai-dev at collab.sakaiproject.org>,    David Pang <dxp at umich.edu>
> Message-ID: <901FBEB5-F01D-4A8B-8BE2-14172349B62C at umich.edu>
> Content-Type: text/plain; charset="windows-1252"
>
> Actually, this does not cause as much of a problem (at least at build time)
> if you have old 2.8 artifacts in your repo.  It's a problem when you don't
> have them because some of them are no longer available from remote repos.
>  If maven decides it needs version 1.1.0-a02 of a particular jar and it is
> no longer in the local repo or any remote repo, and it can't be built
> locally, that causes the build to fail.  And short of checking out source
> for edu-services, fixing the errors in the pom files, and building it
> locally, there is no way to get gradebook2 to build with 2.7.
>
> This is not just a problem for gradebook2.  Any other project that depends
> on sections (and probably other edu-services jars) will have similar
> problems until this is fixed.
>
> Jim
>
>
> On Oct 21, 2010, at 4:51 PM, Steve Swinsburg wrote:
>
> > When building 2.7, you need to blow away that portion of your local Maven
> repo so that it doesn't have the newer 2.8 artifacts in there.
> >
> > But I agree that a specific version should be used so as to eliminate
> this issue.
> >
> > cheers,
> > Steve
> >
> >
> >
> > On 22/10/2010, at 7:21 AM, Jim Eng wrote:
> >
> >> We need to eliminate the apache-repo references in all pom.xml files,
> but that is really just an annoyance that mostly slows down the build
> process for developers.
> >>
> >> On the other hand, the use of ranges for versions in poms for "released"
> versions of a project should be considered a blocker.  In this case, it
> looks like the correct version would have been "${project.version}" rather
> than "[1.0.0-1.1.0)".
> >>
> >> What is needed to get this fixed?  Does it require building edu-services
> 1.0.7 and replacing all references to edu-services 1.0.6 with edu-services
> 1.0.7?
> >>
> >> Jim
> >>
> >>
> >> On Oct 21, 2010, at 3:23 PM, Jim Eng wrote:
> >>
> >>> Thanks, Chris. It looks like you are correct.  The last element in the
> dependencyManagement section of this pom.xml uses a range:
> >>>
> >>>
> https://source.sakaiproject.org/svn//edu-services/tags/edu-services-1.0.6/pom.xml
> >>>
> >>> The gradebook2 build process depends on the jar, which is downloaded
> rather than built locally.  That pom.xml file also includes a repository
> element for apache-repo with a bogus URL.  I don't think we'll be able to
> build gradebook2 locally until that 1.0.6 jar is rebuilt without that range
> of versions and without the apache-repo element.
> >>>
> >>> Jim
> >>>
> >>>
> >>> On Oct 21, 2010, at 3:02 PM, Maurer, Christopher Wayne wrote:
> >>>
> >>>> 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>
> >>>> Date: Thu, 21 Oct 2010 14:46:24 -0400
> >>>> To: Jim Eng <jimeng at umich.edu>
> >>>> Cc: <gradebook2-dev at collab.sakaiproject.org>, David Pang <
> dxp at umich.edu>, Sakai-Dev Developers <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> 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
> >>>>>>>> > http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
> >>>>>>>> >
> >>>>>>>> > TO UNSUBSCRIBE: send email to
> sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of
> "unsubscribe"
> >>>>>>>> >
> >>>>>>>> >
> >>>>>>>>
> >>>>>>>> _______________________________________________
> >>>>>>>> sakai-dev mailing list
> >>>>>>>> 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 with a subject of
> "unsubscribe"
> >>>>>>>
> >>>>>>> _______________________________________________
> >>>>>>> sakai-dev mailing list
> >>>>>>> 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 with a subject of
> "unsubscribe"
> >>>>>>
> >>>>>
> >>>>> _______________________________________________
> >>>>> sakai-dev mailing list
> >>>>> 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 with a subject of
> "unsubscribe"
> >>>>
> >>>> _______________________________________________ sakai-dev mailing list
> 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 with a subject
> of "unsubscribe"
> >>>
> >>> _______________________________________________
> >>> sakai-dev mailing list
> >>> 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 with a subject of
> "unsubscribe"
> >>
> >> _______________________________________________
> >> sakai-dev mailing list
> >> 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 with a subject of
> "unsubscribe"
> >
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20101021/97be9792/attachment-0001.html
>
> ------------------------------
>
> Message: 9
> Date: Thu, 21 Oct 2010 17:59:06 -0400
> From: Anthony Whyte <arwhyte at umich.edu>
> Subject: Re: [Building Sakai] Problem with pom.xml at root of
>        edu-services
> To: Noah Botimer <botimer at umich.edu>
> Cc: sakai-dev <sakai-dev at collab.sakaiproject.org>
> Message-ID: <7C2F608F-213E-421E-8D4F-73CBE814289B at umich.edu>
> Content-Type: text/plain; charset="us-ascii"
>
> The 2.8.0-a01 / a02 tags are considered by Maven as inside the Maven
> version range [2.7.0, 2.8.0) if I am interpreting the following rule
> correctly:
>
> "if qualifier does not exist, it is newer than if it does"
>
>
> http://docs.codehaus.org/display/MAVEN/Dependency+Mediation+and+Conflict+Resolution
> "For ordering, the following is done in order until an element is found
> that are not equal:
>
> numerical comparison of major version
> numerical comparison of minor version
> if revision does not exist, add ".0" for comparison purposes
> numerical comparison of revision
> if qualifier does not exist, it is newer than if it does
> case-insensitive string comparison of qualifier
> this ensures timestamps are correctly ordered, and SNAPSHOT is newer than
> an equivalent timestamp
> this also ensures that beta comes after alpha, as does rc
> if no qualifier, and build does not exist, add "-0" for comparison purposes
> numerical comparison of build"
> Starting tomorrow I'll yank the version ranges out of 2.7.x-related
> projects (including indies) and in the case of the latter, generate new
> releases as required that will be deployed by 2.7.x.  If necessary we can
> also roll a sakai-2.7.2 maintenance release.
>
> There are no version ranges used in trunk, 2.8.x or 2.8-related indies.
>
> ~Anth
>
>
>
>
>
> On Oct 21, 2010, at 3:24 PM, Noah Botimer wrote:
>
> > Maybe we can start up a FAQ / Troubleshooting Guide?
> >
> > We've been seeing a lot of these build / deployment / pom problems
> tripping up some of our most experienced people, as well as newcomers.
> >
> > There's a lot of complexity in our packaging and it's hard to find good
> answers, check for (ill-)advised patterns, or debug problems quickly.
> Burning a half day of senior developer time at a crack on getting a build
> going isn't really a best practice.
> >
> > Thanks,
> > -Noah
> >
> > On Oct 21, 2010, at 3:05 PM, Jim Eng wrote:
> >
> >> Is it possible that we are downloading
> org.sakaiproject.edu-services.gradebook:gradebook-service-impl:jar:1.0.6 and
> that somehow depends on
> org.sakaiproject.edu-services.sections:sections-integrationsupport:jar:1.1.0-a02?
> >>
> >> The relevant part of the error message is shown below.  This occurs
> while trying to build gradebook2 in a fresh checkout of sakai 2.7.1 (also in
> sakai 2.7.x):
> >>
> >> [INFO]
> ------------------------------------------------------------------------
> >> [ERROR] BUILD ERROR
> >> [INFO]
> ------------------------------------------------------------------------
> >> [INFO] Failed to resolve artifact.
> >>
> >> Missing:
> >> ----------
> >> 1)
> org.sakaiproject.edu-services.sections:sections-integrationsupport:jar:1.1.0-a02
> >>
> >>   Try downloading the file manually from:
> >>       http://source.sakaiproject.org/maven2/
> >>
> >>   Then, install it using the command:
> >>       mvn install:install-file
> -DgroupId=org.sakaiproject.edu-services.sections
> -DartifactId=sections-integrationsupport -Dversion=1.1.0-a02 -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.edu-services.sections
> -DartifactId=sections-integrationsupport -Dversion=1.1.0-a02 -Dpackaging=jar
> -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
> >>
> >>   Path to dependency:
> >>      1) org.sakaiproject.gradebook2:gradebook2-model:jar:1.3.0-SNAPSHOT
> >>      2)
> org.sakaiproject.edu-services.gradebook:gradebook-service-impl:jar:1.0.6
> >>      3)
> org.sakaiproject.edu-services.sections:sections-integrationsupport:jar:1.1.0-a02
> >>
> >> ----------
> >> 1 required artifact is missing.
> >>
> >>
> >>
> >>
> >> On Oct 21, 2010, at 2:46 PM, Jim Eng wrote:
> >>
> >>> 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> 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
> > http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
> >
> > TO UNSUBSCRIBE: send email to
> 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/sakai-dev/attachments/20101021/fd3be834/attachment-0001.html
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: smime.p7s
> Type: application/pkcs7-signature
> Size: 3829 bytes
> Desc: not available
> Url :
> http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20101021/fd3be834/attachment-0001.bin
>
> ------------------------------
>
> Message: 10
> Date: Thu, 21 Oct 2010 18:25:51 -0400
> From: Anthony Whyte <arwhyte at umich.edu>
> Subject: Re: [Building Sakai] Problem with pom.xml at root of
>        edu-services
> To: Jim Eng <jimeng at umich.edu>
> Cc: David Pang <dxp at umich.edu>,
>        "gradebook2-dev at collab.sakaiproject.org"
>        <gradebook2-dev at collab.sakaiproject.org>,       Sakai-Dev
> Developers
>        <sakai-dev at collab.sakaiproject.org>
> Message-ID: <6F0EDBAF-4060-4DE4-8263-78171E806140 at umich.edu>
> Content-Type: text/plain; charset="windows-1252"
>
> We don't delete stable binaries from our Sakai Mavn2 repo so the scenario
> described in the sentence below insofar as it pertains to Sakai artifacts
> ("1.1.0-a02 . . . is no longer in  . . . any remote repo") should rank
> pretty low when one is seeking to account for a build failure.
>
> > If maven decides it needs version 1.1.0-a02 of a particular jar and it is
> no longer in the local repo or any remote repo, and it can't be built
> locally, that causes the build to fail.
>
>
> Recall, however that we generate no binaries for "monolithic" Sakai (e.g.,
> non-indies) during the alpha, beta, rc phases prior to a release.  If for
> some reason you decide to declare a dependency on
> assignments-api-2.8-SNAPSHOT, you better have the jar in your local .m2 repo
> because you'll never retrieve it remotely (until such a time as we choose to
> repackage assignments).
>
> ~Anth
>
>
>
>
> On Oct 21, 2010, at 5:50 PM, Jim Eng wrote:
>
> > Actually, this does not cause as much of a problem (at least at build
> time) if you have old 2.8 artifacts in your repo.  It's a problem when you
> don't have them because some of them are no longer available from remote
> repos.  If maven decides it needs version 1.1.0-a02 of a particular jar and
> it is no longer in the local repo or any remote repo, and it can't be built
> locally, that causes the build to fail.  And short of checking out source
> for edu-services, fixing the errors in the pom files, and building it
> locally, there is no way to get gradebook2 to build with 2.7.
> >
> > This is not just a problem for gradebook2.  Any other project that
> depends on sections (and probably other edu-services jars) will have similar
> problems until this is fixed.
> >
> > Jim
> >
> >
> > On Oct 21, 2010, at 4:51 PM, Steve Swinsburg wrote:
> >
> >> When building 2.7, you need to blow away that portion of your local
> Maven repo so that it doesn't have the newer 2.8 artifacts in there.
> >>
> >> But I agree that a specific version should be used so as to eliminate
> this issue.
> >>
> >> cheers,
> >> Steve
> >>
> >>
> >>
> >> On 22/10/2010, at 7:21 AM, Jim Eng wrote:
> >>
> >>> We need to eliminate the apache-repo references in all pom.xml files,
> but that is really just an annoyance that mostly slows down the build
> process for developers.
> >>>
> >>> On the other hand, the use of ranges for versions in poms for
> "released" versions of a project should be considered a blocker.  In this
> case, it looks like the correct version would have been "${project.version}"
> rather than "[1.0.0-1.1.0)".
> >>>
> >>> What is needed to get this fixed?  Does it require building
> edu-services 1.0.7 and replacing all references to edu-services 1.0.6 with
> edu-services 1.0.7?
> >>>
> >>> Jim
> >>>
> >>>
> >>> On Oct 21, 2010, at 3:23 PM, Jim Eng wrote:
> >>>
> >>>> Thanks, Chris. It looks like you are correct.  The last element in the
> dependencyManagement section of this pom.xml uses a range:
> >>>>
> >>>>
> https://source.sakaiproject.org/svn//edu-services/tags/edu-services-1.0.6/pom.xml
> >>>>
> >>>> The gradebook2 build process depends on the jar, which is downloaded
> rather than built locally.  That pom.xml file also includes a repository
> element for apache-repo with a bogus URL.  I don't think we'll be able to
> build gradebook2 locally until that 1.0.6 jar is rebuilt without that range
> of versions and without the apache-repo element.
> >>>>
> >>>> Jim
> >>>>
> >>>>
> >>>> On Oct 21, 2010, at 3:02 PM, Maurer, Christopher Wayne wrote:
> >>>>
> >>>>> 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>
> >>>>> Date: Thu, 21 Oct 2010 14:46:24 -0400
> >>>>> To: Jim Eng <jimeng at umich.edu>
> >>>>> Cc: <gradebook2-dev at collab.sakaiproject.org>, David Pang <
> dxp at umich.edu>, Sakai-Dev Developers <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>
> 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
> >>>>>>>>> > http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
> >>>>>>>>> >
> >>>>>>>>> > TO UNSUBSCRIBE: send email to
> sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of
> "unsubscribe"
> >>>>>>>>> >
> >>>>>>>>> >
> >>>>>>>>>
> >>>>>>>>> _______________________________________________
> >>>>>>>>> sakai-dev mailing list
> >>>>>>>>> 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 with a subject of
> "unsubscribe"
> >>>>>>>>
> >>>>>>>> _______________________________________________
> >>>>>>>> sakai-dev mailing list
> >>>>>>>> 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 with a subject of
> "unsubscribe"
> >>>>>>>
> >>>>>>
> >>>>>> _______________________________________________
> >>>>>> sakai-dev mailing list
> >>>>>> 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 with a subject of
> "unsubscribe"
> >>>>>
> >>>>> _______________________________________________ sakai-dev mailing
> list 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 with a subject
> of "unsubscribe"
> >>>>
> >>>> _______________________________________________
> >>>> sakai-dev mailing list
> >>>> 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 with a subject of
> "unsubscribe"
> >>>
> >>> _______________________________________________
> >>> sakai-dev mailing list
> >>> 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 with a subject of
> "unsubscribe"
> >>
> >
> > _______________________________________________
> > sakai-dev mailing list
> > 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 with a subject of
> "unsubscribe"
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20101021/1be1b633/attachment-0001.html
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: smime.p7s
> Type: application/pkcs7-signature
> Size: 3829 bytes
> Desc: not available
> Url :
> http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20101021/1be1b633/attachment-0001.bin
>
> ------------------------------
>
> Message: 11
> Date: Thu, 21 Oct 2010 18:45:10 -0400
> From: Jim Eng <jimeng at umich.edu>
> Subject: Re: [Building Sakai] Problem with pom.xml at root of
>        edu-services
> To: Anthony Whyte <arwhyte at umich.edu>
> Cc: David Pang <dxp at umich.edu>,
>        "gradebook2-dev at collab.sakaiproject.org"
>        <gradebook2-dev at collab.sakaiproject.org>,       Sakai-Dev
> Developers
>        <sakai-dev at collab.sakaiproject.org>
> Message-ID: <26CA389A-96ED-45E5-A6BC-E1140077F2C2 at umich.edu>
> Content-Type: text/plain; charset="windows-1252"
>
> I may be saying it wrong, but edu-services' base pom declares that it needs
> version [1.0.0-1.1.0) of a couple jars.  For some reason for the past couple
> weeks, maven has decided that the version it needs based on that declaration
> was 1.1.0-a02. I'm guessing that maven was finding that jar in my local repo
> and then it looked in remote repositories to see if there was a newer
> version.  Because edu-services also contained a reference to a bogus repo
> (apache-repo), that took a lot of time.  Once I cleaned out my local repo,
> for some reason, maven still decides it needs version 1.1.0-a02 of that jar,
> but now it is no longer in my local repo and it's not in any remote repo, so
> the build fails.
>
> Maybe I am doing something wrong that is aggravating this situation, but if
> the pom said it wanted version 1.0.6 of that jar (which *IS* in the remote
> repos *AND* in my local repo) I would not be having this problem.  To me
> that is a bug in the pre-built edu-services jars.
>
> Jim
>
>
> On Oct 21, 2010, at 6:25 PM, Anthony Whyte wrote:
>
> > We don't delete stable binaries from our Sakai Mavn2 repo so the scenario
> described in the sentence below insofar as it pertains to Sakai artifacts
> ("1.1.0-a02 . . . is no longer in  . . . any remote repo") should rank
> pretty low when one is seeking to account for a build failure.
> >
> >> If maven decides it needs version 1.1.0-a02 of a particular jar and it
> is no longer in the local repo or any remote repo, and it can't be built
> locally, that causes the build to fail.
> >
> >
> > Recall, however that we generate no binaries for "monolithic" Sakai
> (e.g., non-indies) during the alpha, beta, rc phases prior to a release.  If
> for some reason you decide to declare a dependency on
> assignments-api-2.8-SNAPSHOT, you better have the jar in your local .m2 repo
> because you'll never retrieve it remotely (until such a time as we choose to
> repackage assignments).
> >
> > ~Anth
> >
> >
> >
> >
> > On Oct 21, 2010, at 5:50 PM, Jim Eng wrote:
> >
> >> Actually, this does not cause as much of a problem (at least at build
> time) if you have old 2.8 artifacts in your repo.  It's a problem when you
> don't have them because some of them are no longer available from remote
> repos.  If maven decides it needs version 1.1.0-a02 of a particular jar and
> it is no longer in the local repo or any remote repo, and it can't be built
> locally, that causes the build to fail.  And short of checking out source
> for edu-services, fixing the errors in the pom files, and building it
> locally, there is no way to get gradebook2 to build with 2.7.
> >>
> >> This is not just a problem for gradebook2.  Any other project that
> depends on sections (and probably other edu-services jars) will have similar
> problems until this is fixed.
> >>
> >> Jim
> >>
> >>
> >> On Oct 21, 2010, at 4:51 PM, Steve Swinsburg wrote:
> >>
> >>> When building 2.7, you need to blow away that portion of your local
> Maven repo so that it doesn't have the newer 2.8 artifacts in there.
> >>>
> >>> But I agree that a specific version should be used so as to eliminate
> this issue.
> >>>
> >>> cheers,
> >>> Steve
> >>>
> >>>
> >>>
> >>> On 22/10/2010, at 7:21 AM, Jim Eng wrote:
> >>>
> >>>> We need to eliminate the apache-repo references in all pom.xml files,
> but that is really just an annoyance that mostly slows down the build
> process for developers.
> >>>>
> >>>> On the other hand, the use of ranges for versions in poms for
> "released" versions of a project should be considered a blocker.  In this
> case, it looks like the correct version would have been "${project.version}"
> rather than "[1.0.0-1.1.0)".
> >>>>
> >>>> What is needed to get this fixed?  Does it require building
> edu-services 1.0.7 and replacing all references to edu-services 1.0.6 with
> edu-services 1.0.7?
> >>>>
> >>>> Jim
> >>>>
> >>>>
> >>>> On Oct 21, 2010, at 3:23 PM, Jim Eng wrote:
> >>>>
> >>>>> Thanks, Chris. It looks like you are correct.  The last element in
> the dependencyManagement section of this pom.xml uses a range:
> >>>>>
> >>>>>
> https://source.sakaiproject.org/svn//edu-services/tags/edu-services-1.0.6/pom.xml
> >>>>>
> >>>>> The gradebook2 build process depends on the jar, which is downloaded
> rather than built locally.  That pom.xml file also includes a repository
> element for apache-repo with a bogus URL.  I don't think we'll be able to
> build gradebook2 locally until that 1.0.6 jar is rebuilt without that range
> of versions and without the apache-repo element.
> >>>>>
> >>>>> Jim
> >>>>>
> >>>>>
> >>>>> On Oct 21, 2010, at 3:02 PM, Maurer, Christopher Wayne wrote:
> >>>>>
> >>>>>> 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>
> >>>>>> Date: Thu, 21 Oct 2010 14:46:24 -0400
> >>>>>> To: Jim Eng <jimeng at umich.edu>
> >>>>>> Cc: <gradebook2-dev at collab.sakaiproject.org>, David Pang <
> dxp at umich.edu>, Sakai-Dev Developers <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>
> 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
> >>>>>>>>>> > http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
> >>>>>>>>>> >
> >>>>>>>>>> > TO UNSUBSCRIBE: send email to
> sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of
> "unsubscribe"
> >>>>>>>>>> >
> >>>>>>>>>> >
> >>>>>>>>>>
> >>>>>>>>>> _______________________________________________
> >>>>>>>>>> sakai-dev mailing list
> >>>>>>>>>> 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 with a subject of
> "unsubscribe"
> >>>>>>>>>
> >>>>>>>>> _______________________________________________
> >>>>>>>>> sakai-dev mailing list
> >>>>>>>>> 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 with a subject of
> "unsubscribe"
> >>>>>>>>
> >>>>>>>
> >>>>>>> _______________________________________________
> >>>>>>> sakai-dev mailing list
> >>>>>>> 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 with a subject of
> "unsubscribe"
> >>>>>>
> >>>>>> _______________________________________________ sakai-dev mailing
> list 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 with a subject
> of "unsubscribe"
> >>>>>
> >>>>> _______________________________________________
> >>>>> sakai-dev mailing list
> >>>>> 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 with a subject of
> "unsubscribe"
> >>>>
> >>>> _______________________________________________
> >>>> sakai-dev mailing list
> >>>> 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 with a subject of
> "unsubscribe"
> >>>
> >>
> >> _______________________________________________
> >> sakai-dev mailing list
> >> 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 with a subject of
> "unsubscribe"
> >
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20101021/2a93f0b4/attachment-0001.html
>
> ------------------------------
>
> Message: 12
> Date: Thu, 21 Oct 2010 19:08:20 -0400
> From: Anthony Whyte <arwhyte at umich.edu>
> Subject: Re: [Building Sakai] Problem with pom.xml at root of
>        edu-services
> To: Jim Eng <jimeng at umich.edu>
> Cc: David Pang <dxp at umich.edu>,
>        "gradebook2-dev at collab.sakaiproject.org"
>        <gradebook2-dev at collab.sakaiproject.org>,       Sakai-Dev
> Developers
>        <sakai-dev at collab.sakaiproject.org>
> Message-ID: <C35D06EA-981E-48FC-861B-5DF4792E2CB6 at umich.edu>
> Content-Type: text/plain; charset="windows-1252"
>
> edu-services-1.1.0-a02 was generated on 19 October 2010 for
> sakai-2.8.0-a02; you can find it along with 1.1.0-a01 (generated 22 Sept
> 2010) and earlier binaries here:
>
> http://source.sakaiproject.org/maven2/org/sakaiproject/edu-services/
>
> What you've been experiencing of late is Maven opting for the new jars
> (1.1.0-a01 then as of Tuesday evening, 1.1.0-a02) as you deduced earlier  In
> either case, whether or not you can retrieve these binaries, whether or not
> they are in your local repo or elsewhere--you don't want them.  You need
> edu-services-1.0.6.
>
> As I noted in my earlier email, I am going to remove the version range from
> edu-services-1.0.x and generate a new release (1.0.7).  I will then do the
> same for the rest of the 2.7-related indies.  I'll update 2.7.x so that it
> deploys the new binaries, sans version ranges.
>
> Once I am done, this leakage of 2.8-related artifacts into 2.7 builds will
> cease.
>
> Anth
>
>
>
>
>
>
>
>
> On Oct 21, 2010, at 6:45 PM, Jim Eng wrote:
>
> > I may be saying it wrong, but edu-services' base pom declares that it
> needs version [1.0.0-1.1.0) of a couple jars.  For some reason for the past
> couple weeks, maven has decided that the version it needs based on that
> declaration was 1.1.0-a02. I'm guessing that maven was finding that jar in
> my local repo and then it looked in remote repositories to see if there was
> a newer version.  Because edu-services also contained a reference to a bogus
> repo (apache-repo), that took a lot of time.  Once I cleaned out my local
> repo, for some reason, maven still decides it needs version 1.1.0-a02 of
> that jar, but now it is no longer in my local repo and it's not in any
> remote repo, so the build fails.
> >
> > Maybe I am doing something wrong that is aggravating this situation, but
> if the pom said it wanted version 1.0.6 of that jar (which *IS* in the
> remote repos *AND* in my local repo) I would not be having this problem.  To
> me that is a bug in the pre-built edu-services jars.
> >
> > Jim
> >
> >
> > On Oct 21, 2010, at 6:25 PM, Anthony Whyte wrote:
> >
> >> We don't delete stable binaries from our Sakai Mavn2 repo so the
> scenario described in the sentence below insofar as it pertains to Sakai
> artifacts ("1.1.0-a02 . . . is no longer in  . . . any remote repo") should
> rank pretty low when one is seeking to account for a build failure.
> >>
> >>> If maven decides it needs version 1.1.0-a02 of a particular jar and it
> is no longer in the local repo or any remote repo, and it can't be built
> locally, that causes the build to fail.
> >>
> >>
> >> Recall, however that we generate no binaries for "monolithic" Sakai
> (e.g., non-indies) during the alpha, beta, rc phases prior to a release.  If
> for some reason you decide to declare a dependency on
> assignments-api-2.8-SNAPSHOT, you better have the jar in your local .m2 repo
> because you'll never retrieve it remotely (until such a time as we choose to
> repackage assignments).
> >>
> >> ~Anth
> >>
> >>
> >>
> >>
> >> On Oct 21, 2010, at 5:50 PM, Jim Eng wrote:
> >>
> >>> Actually, this does not cause as much of a problem (at least at build
> time) if you have old 2.8 artifacts in your repo.  It's a problem when you
> don't have them because some of them are no longer available from remote
> repos.  If maven decides it needs version 1.1.0-a02 of a particular jar and
> it is no longer in the local repo or any remote repo, and it can't be built
> locally, that causes the build to fail.  And short of checking out source
> for edu-services, fixing the errors in the pom files, and building it
> locally, there is no way to get gradebook2 to build with 2.7.
> >>>
> >>> This is not just a problem for gradebook2.  Any other project that
> depends on sections (and probably other edu-services jars) will have similar
> problems until this is fixed.
> >>>
> >>> Jim
> >>>
> >>>
> >>> On Oct 21, 2010, at 4:51 PM, Steve Swinsburg wrote:
> >>>
> >>>> When building 2.7, you need to blow away that portion of your local
> Maven repo so that it doesn't have the newer 2.8 artifacts in there.
> >>>>
> >>>> But I agree that a specific version should be used so as to eliminate
> this issue.
> >>>>
> >>>> cheers,
> >>>> Steve
> >>>>
> >>>>
> >>>>
> >>>> On 22/10/2010, at 7:21 AM, Jim Eng wrote:
> >>>>
> >>>>> We need to eliminate the apache-repo references in all pom.xml files,
> but that is really just an annoyance that mostly slows down the build
> process for developers.
> >>>>>
> >>>>> On the other hand, the use of ranges for versions in poms for
> "released" versions of a project should be considered a blocker.  In this
> case, it looks like the correct version would have been "${project.version}"
> rather than "[1.0.0-1.1.0)".
> >>>>>
> >>>>> What is needed to get this fixed?  Does it require building
> edu-services 1.0.7 and replacing all references to edu-services 1.0.6 with
> edu-services 1.0.7?
> >>>>>
> >>>>> Jim
> >>>>>
> >>>>>
> >>>>> On Oct 21, 2010, at 3:23 PM, Jim Eng wrote:
> >>>>>
> >>>>>> Thanks, Chris. It looks like you are correct.  The last element in
> the dependencyManagement section of this pom.xml uses a range:
> >>>>>>
> >>>>>>
> https://source.sakaiproject.org/svn//edu-services/tags/edu-services-1.0.6/pom.xml
> >>>>>>
> >>>>>> The gradebook2 build process depends on the jar, which is downloaded
> rather than built locally.  That pom.xml file also includes a repository
> element for apache-repo with a bogus URL.  I don't think we'll be able to
> build gradebook2 locally until that 1.0.6 jar is rebuilt without that range
> of versions and without the apache-repo element.
> >>>>>>
> >>>>>> Jim
> >>>>>>
> >>>>>>
> >>>>>> On Oct 21, 2010, at 3:02 PM, Maurer, Christopher Wayne wrote:
> >>>>>>
> >>>>>>> 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>
> >>>>>>> Date: Thu, 21 Oct 2010 14:46:24 -0400
> >>>>>>> To: Jim Eng <jimeng at umich.edu>
> >>>>>>> Cc: <gradebook2-dev at collab.sakaiproject.org>, David Pang <
> dxp at umich.edu>, Sakai-Dev Developers <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>
> 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
> >>>>>>>>>>> > http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
> >>>>>>>>>>> >
> >>>>>>>>>>> > TO UNSUBSCRIBE: send email to
> sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of
> "unsubscribe"
> >>>>>>>>>>> >
> >>>>>>>>>>> >
> >>>>>>>>>>>
> >>>>>>>>>>> _______________________________________________
> >>>>>>>>>>> sakai-dev mailing list
> >>>>>>>>>>> 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 with a subject of
> "unsubscribe"
> >>>>>>>>>>
> >>>>>>>>>> _______________________________________________
> >>>>>>>>>> sakai-dev mailing list
> >>>>>>>>>> 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 with a subject of
> "unsubscribe"
> >>>>>>>>>
> >>>>>>>>
> >>>>>>>> _______________________________________________
> >>>>>>>> sakai-dev mailing list
> >>>>>>>> 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 with a subject of
> "unsubscribe"
> >>>>>>>
> >>>>>>> _______________________________________________ sakai-dev mailing
> list 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 with a subject
> of "unsubscribe"
> >>>>>>
> >>>>>> _______________________________________________
> >>>>>> sakai-dev mailing list
> >>>>>> 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 with a subject of
> "unsubscribe"
> >>>>>
> >>>>> _______________________________________________
> >>>>> sakai-dev mailing list
> >>>>> 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 with a subject of
> "unsubscribe"
> >>>>
> >>>
> >>> _______________________________________________
> >>> sakai-dev mailing list
> >>> 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 with a subject of
> "unsubscribe"
> >>
> >
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20101021/71b21c97/attachment-0001.html
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: smime.p7s
> Type: application/pkcs7-signature
> Size: 3829 bytes
> Desc: not available
> Url :
> http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20101021/71b21c97/attachment-0001.bin
>
> ------------------------------
>
> Message: 13
> Date: Thu, 21 Oct 2010 19:27:30 -0400
> From: Anthony Whyte <arwhyte at umich.edu>
> Subject: Re: [Building Sakai] Problem with pom.xml at root of
>        edu-services
> To: Eng Jim <jimeng at umich.edu>, David Pang <dxp at umich.edu>
> Cc: gradebook2-dev at collab.sakaiproject.org,     Developers Sakai-Dev
>        <sakai-dev at collab.sakaiproject.org>
> Message-ID: <7CC153FE-D137-4961-BDF5-C1E7C2DC2FF4 at umich.edu>
> Content-Type: text/plain; charset="windows-1252"
>
> I should note that I misread your email slightly -- the jars I belive you
> are referring to are: archive-api and sections-integrationsupport
>
> edu-services-1.0.6 base pom:
>
> <dependency>
> <groupId>org.sakaiproject.common</groupId>
> <artifactId>archive-api</artifactId>
> <version>[1.0.0,1.1.0)</version>
> </dependency>
>
> Binaries exist here: (1.0.4, 1.1.0-a01, 1.1.0-a02)
>
> http://source.sakaiproject.org/maven2/org/sakaiproject/common/archive-api
>
> <dependency>
> <groupId>org.sakaiproject.edu-services.sections</groupId>
> <artifactId>sections-integrationsupport</artifactId>
> <version>[1.0.0,1.1.0)</version>
> </dependency>
>
> Binaries exist here (1.0.6, 1.1.0-a01, 1.1.0-a02)
>
>
> http://source.sakaiproject.org/maven2/org/sakaiproject/edu-services/sections/sections-integrationsupport/
>
> Anyways, the issue is not about missing jars, it's about a version range
> pulling in the wrong binaries for you.
>
> You'll start seeing fixes in the morning.
>
> Anth
>
>
>
> On Oct 21, 2010, at 7:08 PM, Anthony Whyte wrote:
>
> > edu-services-1.1.0-a02 was generated on 19 October 2010 for
> sakai-2.8.0-a02; you can find it along with 1.1.0-a01 (generated 22 Sept
> 2010) and earlier binaries here:
> >
> > http://source.sakaiproject.org/maven2/org/sakaiproject/edu-services/
> >
> > What you've been experiencing of late is Maven opting for the new jars
> (1.1.0-a01 then as of Tuesday evening, 1.1.0-a02) as you deduced earlier  In
> either case, whether or not you can retrieve these binaries, whether or not
> they are in your local repo or elsewhere--you don't want them.  You need
> edu-services-1.0.6.
> >
> > As I noted in my earlier email, I am going to remove the version range
> from edu-services-1.0.x and generate a new release (1.0.7).  I will then do
> the same for the rest of the 2.7-related indies.  I'll update 2.7.x so that
> it deploys the new binaries, sans version ranges.
> >
> > Once I am done, this leakage of 2.8-related artifacts into 2.7 builds
> will cease.
> >
> > Anth
> >
> >
> >
> >
> >
> >
> >
> >
> > On Oct 21, 2010, at 6:45 PM, Jim Eng wrote:
> >
> >> I may be saying it wrong, but edu-services' base pom declares that it
> needs version [1.0.0-1.1.0) of a couple jars.  For some reason for the past
> couple weeks, maven has decided that the version it needs based on that
> declaration was 1.1.0-a02. I'm guessing that maven was finding that jar in
> my local repo and then it looked in remote repositories to see if there was
> a newer version.  Because edu-services also contained a reference to a bogus
> repo (apache-repo), that took a lot of time.  Once I cleaned out my local
> repo, for some reason, maven still decides it needs version 1.1.0-a02 of
> that jar, but now it is no longer in my local repo and it's not in any
> remote repo, so the build fails.
> >>
> >> Maybe I am doing something wrong that is aggravating this situation, but
> if the pom said it wanted version 1.0.6 of that jar (which *IS* in the
> remote repos *AND* in my local repo) I would not be having this problem.  To
> me that is a bug in the pre-built edu-services jars.
> >>
> >> Jim
> >>
> >>
> >> On Oct 21, 2010, at 6:25 PM, Anthony Whyte wrote:
> >>
> >>> We don't delete stable binaries from our Sakai Mavn2 repo so the
> scenario described in the sentence below insofar as it pertains to Sakai
> artifacts ("1.1.0-a02 . . . is no longer in  . . . any remote repo") should
> rank pretty low when one is seeking to account for a build failure.
> >>>
> >>>> If maven decides it needs version 1.1.0-a02 of a particular jar and it
> is no longer in the local repo or any remote repo, and it can't be built
> locally, that causes the build to fail.
> >>>
> >>>
> >>> Recall, however that we generate no binaries for "monolithic" Sakai
> (e.g., non-indies) during the alpha, beta, rc phases prior to a release.  If
> for some reason you decide to declare a dependency on
> assignments-api-2.8-SNAPSHOT, you better have the jar in your local .m2 repo
> because you'll never retrieve it remotely (until such a time as we choose to
> repackage assignments).
> >>>
> >>> ~Anth
> >>>
> >>>
> >>>
> >>>
> >>> On Oct 21, 2010, at 5:50 PM, Jim Eng wrote:
> >>>
> >>>> Actually, this does not cause as much of a problem (at least at build
> time) if you have old 2.8 artifacts in your repo.  It's a problem when you
> don't have them because some of them are no longer available from remote
> repos.  If maven decides it needs version 1.1.0-a02 of a particular jar and
> it is no longer in the local repo or any remote repo, and it can't be built
> locally, that causes the build to fail.  And short of checking out source
> for edu-services, fixing the errors in the pom files, and building it
> locally, there is no way to get gradebook2 to build with 2.7.
> >>>>
> >>>> This is not just a problem for gradebook2.  Any other project that
> depends on sections (and probably other edu-services jars) will have similar
> problems until this is fixed.
> >>>>
> >>>> Jim
> >>>>
> >>>>
> >>>> On Oct 21, 2010, at 4:51 PM, Steve Swinsburg wrote:
> >>>>
> >>>>> When building 2.7, you need to blow away that portion of your local
> Maven repo so that it doesn't have the newer 2.8 artifacts in there.
> >>>>>
> >>>>> But I agree that a specific version should be used so as to eliminate
> this issue.
> >>>>>
> >>>>> cheers,
> >>>>> Steve
> >>>>>
> >>>>>
> >>>>>
> >>>>> On 22/10/2010, at 7:21 AM, Jim Eng wrote:
> >>>>>
> >>>>>> We need to eliminate the apache-repo references in all pom.xml
> files, but that is really just an annoyance that mostly slows down the build
> process for developers.
> >>>>>>
> >>>>>> On the other hand, the use of ranges for versions in poms for
> "released" versions of a project should be considered a blocker.  In this
> case, it looks like the correct version would have been "${project.version}"
> rather than "[1.0.0-1.1.0)".
> >>>>>>
> >>>>>> What is needed to get this fixed?  Does it require building
> edu-services 1.0.7 and replacing all references to edu-services 1.0.6 with
> edu-services 1.0.7?
> >>>>>>
> >>>>>> Jim
> >>>>>>
> >>>>>>
> >>>>>> On Oct 21, 2010, at 3:23 PM, Jim Eng wrote:
> >>>>>>
> >>>>>>> Thanks, Chris. It looks like you are correct.  The last element in
> the dependencyManagement section of this pom.xml uses a range:
> >>>>>>>
> >>>>>>>
> https://source.sakaiproject.org/svn//edu-services/tags/edu-services-1.0.6/pom.xml
> >>>>>>>
> >>>>>>> The gradebook2 build process depends on the jar, which is
> downloaded rather than built locally.  That pom.xml file also includes a
> repository element for apache-repo with a bogus URL.  I don't think we'll be
> able to build gradebook2 locally until that 1.0.6 jar is rebuilt without
> that range of versions and without the apache-repo element.
> >>>>>>>
> >>>>>>> Jim
> >>>>>>>
> >>>>>>>
> >>>>>>> On Oct 21, 2010, at 3:02 PM, Maurer, Christopher Wayne wrote:
> >>>>>>>
> >>>>>>>> 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>
> >>>>>>>> Date: Thu, 21 Oct 2010 14:46:24 -0400
> >>>>>>>> To: Jim Eng <jimeng at umich.edu>
> >>>>>>>> Cc: <gradebook2-dev at collab.sakaiproject.org>, David Pang <
> dxp at umich.edu>, Sakai-Dev Developers <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>
> 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
> >>>>>>>>>>>> > http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
> >>>>>>>>>>>> >
> >>>>>>>>>>>> > TO UNSUBSCRIBE: send email to
> sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of
> "unsubscribe"
> >>>>>>>>>>>> >
> >>>>>>>>>>>> >
> >>>>>>>>>>>>
> >>>>>>>>>>>> _______________________________________________
> >>>>>>>>>>>> sakai-dev mailing list
> >>>>>>>>>>>> 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 with a subject of
> "unsubscribe"
> >>>>>>>>>>>
> >>>>>>>>>>> _______________________________________________
> >>>>>>>>>>> sakai-dev mailing list
> >>>>>>>>>>> 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 with a subject of
> "unsubscribe"
> >>>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> _______________________________________________
> >>>>>>>>> sakai-dev mailing list
> >>>>>>>>> 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 with a subject of
> "unsubscribe"
> >>>>>>>>
> >>>>>>>> _______________________________________________ sakai-dev mailing
> list 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 with a subject
> of "unsubscribe"
> >>>>>>>
> >>>>>>> _______________________________________________
> >>>>>>> sakai-dev mailing list
> >>>>>>> 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 with a subject of
> "unsubscribe"
> >>>>>>
> >>>>>> _______________________________________________
> >>>>>> sakai-dev mailing list
> >>>>>> 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 with a subject of
> "unsubscribe"
> >>>>>
> >>>>
> >>>> _______________________________________________
> >>>> sakai-dev mailing list
> >>>> 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 with a subject of
> "unsubscribe"
> >>>
> >>
> >
> > _______________________________________________
> > sakai-dev mailing list
> > 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 with a subject of
> "unsubscribe"
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20101021/c312e7f7/attachment-0001.html
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: smime.p7s
> Type: application/pkcs7-signature
> Size: 3829 bytes
> Desc: not available
> Url :
> http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20101021/c312e7f7/attachment-0001.bin
>
> ------------------------------
>
> Message: 14
> Date: Fri, 22 Oct 2010 09:10:58 +0200
> From: Jacek Bilski <jacek.bilski at avalcom.pl>
> Subject: [Building Sakai] PostgreSQL support
> To: Sakai-dev <sakai-dev at collab.sakaiproject.org>
> Message-ID: <4CC13902.2090906 at avalcom.pl>
> Content-Type: text/plain; charset=UTF-8; format=flowed
>
> Hello,
>
> As I already wrote in http://jira.sakaiproject.org/browse/SAK-10826 me
> and my company are willing to add support for PostgreSQL to Sakai. We're
> beginning a new project involving Sakai, but as it will take some time
> to start it, we're targeting version 3.0.
>
> Could anyone give us some hints as to where to look and what to look
> for, any possible pitfalls, and the like? We're now looking into what
> needs to be done. If anyone could help it would be much easier. We would
> probably also need rw access to svn repository.
>
> Best regards
>
> --
> Jacek Bilski
> Dyrektor ds. Technologii
> jacek.bilski at avalcom.pl
> tel.: +48 609 572 036
>
> Avalcom Sp. z o.o. z siedzib? w Rokietnicy, ul. Modrzewiowa 12, 62-090
> Rokietnica. S?d Rejonowy w Poznaniu, VIII Wydzia? Gospodarczy Krajowego
> Rejestru S?dowego, numer KRS 00000349521, NIP 777-31-50-030, REGON
> 301371500, kapita? zak?adowy 6.000,00 PLN
> tel. +48 71 3495219, e-mail: biuro at avalcom.pl,
> http://www.avalcom.pl
>
>
> ------------------------------
>
> Message: 15
> Date: Fri, 22 Oct 2010 14:27:54 +0700
> From: Tin Nguyen <nguyentrongtin89 at gmail.com>
> Subject: [Building Sakai] How to fix this problem with Tests&Quizzes
>        and     Chat tools
> To: sakai-dev at collab.sakaiproject.org
> Message-ID:
>        <AANLkTi=ruS4wQNVG=X-=zaajEK6Q+gRU1HChgxvKOsiG at mail.gmail.com<zaajEK6Q%2BgRU1HChgxvKOsiG at mail.gmail.com>
> >
> Content-Type: text/plain; charset="iso-8859-1"
>
> Dear all,
> When I clicked the Tests&Quizzes or Chat link, sakai showed the exception:
>
> org.sakaiproject.portal.api.PortalHandlerException:
> java.lang.IllegalArgumentException: Unable to find registered context
> for tool with ID sakai.samigo
>    at
> org.sakaiproject.portal.charon.SkinnableCharonPortal.doGet(SkinnableCharonPortal.java:768)
> caused by: java.lang.IllegalArgumentException: Unable to find
> registered context for tool with ID sakai.samigo
>    at
> org.sakaiproject.tool.impl.ActiveToolComponent$MyActiveTool.forward(ActiveToolComponent.java:497)
>    at
> org.sakaiproject.portal.charon.SkinnableCharonPortal.forwardTool(SkinnableCharonPortal.java:1221)
>    at
> org.sakaiproject.portal.charon.handlers.ToolHandler.doTool(ToolHandler.java:204)
>    at
> org.sakaiproject.portal.charon.handlers.ToolHandler.doGet(ToolHandler.java:96)
>    at
> org.sakaiproject.portal.charon.SkinnableCharonPortal.doGet(SkinnableCharonPortal.java:768)
>    at javax.servlet.http.HttpServlet.service(HttpServlet.java:627)
>    at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
>    at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)
>    at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
>    at org.sakaiproject.util.RequestFilter.doFilter(RequestFilter.java:646)
>    at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215)
>    at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
>    at
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
>    at
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:172)
>    at
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
>    at
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
>    at
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108)
>    at
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:174)
>    at
> org.apache.coyote.http11.Http11AprProcessor.process(Http11AprProcessor.java:843)
>    at
> org.apache.coyote.http11.Http11AprProtocol$Http11ConnectionHandler.process(Http11AprProtocol.java:679)
>    at
> org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:1293)
>    at java.lang.Thread.run(Thread.java:619)
>
> I tried to clean all (database, tomcat, sakai source). After that I
> installed and deployed again, but not effect.
> My system is:
>
>   - Tomcat 5.5.31
>   - Sakai-src 2.7.1
>   - MySQL database 5.1
>   - Win 7 Home 64bit
>   - JDK 1.6.0_21
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20101022/3f2f925c/attachment-0001.html
>
> ------------------------------
>
> Message: 16
> Date: Fri, 22 Oct 2010 10:11:58 +0100
> From: Adam Marshall <adam.marshall at oucs.ox.ac.uk>
> Subject: Re: [Building Sakai] Displaying details in Resources' table
>        view
> To: Matt Clare <Matt.Clare at BrockU.CA>
> Cc: "sakai-dev at collab.sakaiproject.org"
>        <sakai-dev at collab.sakaiproject.org>
> Message-ID:
>        <E3F632CF621AB2488269800D3F05D54C56FE7BA69B at EXMBX03.ad.oak.ox.ac.uk
> >
> Content-Type: text/plain; charset="us-ascii"
>
> I suggest what you need to use is the "Access view" of resources!
>
> We've been running an improved version of the access view of resources for
> about 3 years now. This was done by Gonzalo Silvero to whom we will be
> eternally grateful. See: http://jira.sakaiproject.org/browse/SAK-13694 .
>
> It doesnt render copyright status though - adding this would be an
> excellent improvement. Perhaps a BG image of a (c) could be added somewhere
> to an item?
>
> We made the decision to allow HTML in a resource description but don't
> intend to offer a WYSIWYG editor as this often prompts people to get a bit
> carried away!
>
> It looks like this fix may be in 2.7.
>
> Here's a made-up example:
> https://weblearn.ox.ac.uk/access/content/group/cc2c88fe-a0fe-44d6-0046-89493362b2aa/sub%20f/
>
> I'm not sure what we did to enable HTML in the descriptions but we're happy
> to kake it available.
>
> As a side note we neededn this as we added IMS CP import to Site Info >
> Import from file and our IMS CPs contain HTML descriptions. This may also
> apply to IMS CCtoo?
>
> adam
>
> | -----Original Message-----
> | From: Matt Clare [mailto:Matt.Clare at BrockU.CA]
> | Sent: 21 October 2010 18:04
> | To: Adam Marshall
> | Cc: sakai-dev at collab.sakaiproject.org
> | Subject: Re: Displaying details in Resources' table view
> |
> | Thanks for the follow up,
> |
> |       The main "details" are the Description and Copyright Status.
> | There are also a number of Optional properties.
> |
> |       If these items had some indicator in the same way that "Copyright
> | Alert" does students would be more likely to click through to them.  As
> | it stands a student that does go to Actions > View Details for each
> | item is quickly condition not to do that anymore because there is
> | rarely any results and its a number of steps each time, in turn,
> | instructors tend not make use of Description and Copyright Status
> | because student don't review them
> |
> |       Should I be filing a feature request then?
> |
> |       .\.\att
> |
> | On 2010-10-21, at 12:18 PM, Adam Marshall wrote:
> |
> | > what else did you want to display?
> | >
> | > adam
> | >
> | > | -----Original Message-----
> | > | From: sakai-dev-bounces at collab.sakaiproject.org [mailto:sakai-dev-
> | > | bounces at collab.sakaiproject.org] On Behalf Of Matt Clare
> | > | Sent: 20 October 2010 20:52
> | > | To: sakai-dev at collab.sakaiproject.org
> | > | Subject: [Building Sakai] Displaying details in Resources' table
> | view
> | > |
> | > | Hello Sakai-dev community.
> | > |
> | > |   I was curious if there was a way to display the details
> | > | instructor add to items in the Resources tool in the table view?
> | > |
> | > |   When an item is marked as "Display copyright alert and require
> | > | a...." there is a (c) placed beside the item title, but the other
> | > | details are still two-clicks and a page-load away for students to
> | > | discover under Actions > View Details.
> | > |
> | > |   Is there any way to indicate to students which Resource items
> | > | they should be investigating the details of?  Is this a
> | configuration
> | > | item somewhere?
> | > |
> | > | Thanks,
> | > |
> | > | .\.\att
> | > |
> | > | Brock University
> | > | _______________________________________________
> | > | sakai-dev mailing list
> | > | 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 with a subject of "unsubscribe"
> |
> |   ::  Matt Clare
> | Educational Technology Support Specialist,
> | Centre for Teaching Learning and Educational Technologies (CTLET)
> | Part-time Instructor, Interactive Arts and Sciences
> | Brock University, Niagara Region, Ontario, Canada
> | www.brocku.ca/ctlet  905 688 5550 xt 4734   Office: SBH315
> |
> | Isaak/Sakai Question?  http://kumu.brocku.ca/sakai/FAQ
>
>
>
> ------------------------------
>
> Message: 17
> Date: Fri, 22 Oct 2010 11:52:16 +0100
> From: Matthew Buckett <matthew.buckett at oucs.ox.ac.uk>
> Subject: [Building Sakai] Sitestats 2.1.0 in Sakai 2.6.x
> To: Sakai Developers <sakai-dev at collab.sakaiproject.org>
> Cc: Nuno Fernandes <nuno at ufp.pt>
> Message-ID:
>        <AANLkTi=hfTY4GQ0EHLwd9n5zaKxH-oeFbu5uayk9T9Wq at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Should it easy to run Sitestats 2.1.0 on Sakai 2.6.x by just changing
> the references in the POMs?
>
> The reason is we're interested in 2.1.0 is that some of our users are
> seeing negative resources counts
> (http://jira.sakaiproject.org/browse/STAT-203)  and this isn't fixed
> in the 2.6.x branch of Sitestats 2.0.
>
> So one possible way to fix it is to upgrade to 2.1.0.
>
> --
> ? Matthew Buckett
> ? VLE Developer, LTG, Oxford University Computing Services
>
>
> ------------------------------
>
> Message: 18
> Date: Fri, 22 Oct 2010 08:33:33 -0700
> From: John Bush <john.bush at rsmart.com>
> Subject: [Building Sakai] math editor for fckeditor
> To: sakai-user <sakai-user at collab.sakaiproject.org>,    Sakai-Dev
>        <sakai-dev at collab.sakaiproject.org>
> Message-ID:
>        <AANLkTinJ28bX0pHt1_jncbBbBjKu5nocCJFNjJDfxRoL at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Is anyone doing anything to bring a math editor into sakai?  I know
> about jsmath for rwiki and sferyx for melete, but something that plugs
> into the fckeditor is the ideal, since that give the most widespread
> use.  I stumbled across I decent blog that talks about some of the
> options for moodle, but seems relevant to us as well.
>
> http://www.stattler.com/blog/latex-equation-drupal-blog
>
> This look like the best contender, as there is already a fckeditor
> plugin for this tool, check it out:
>
> check this out, http://www.codecogs.com/pages/forums/pagegen.php?id=1639
>
> Is anyone using this or an alternative, care to share experiences ?
>
> --
> John Bush
> 602-490-0470
>
>
> ------------------------------
>
> Message: 19
> Date: Fri, 22 Oct 2010 12:49:49 -0400
> From: "Qian, Zhen" <zqian at umich.edu>
> Subject: Re: [Building Sakai] math editor for fckeditor
> To: John Bush <john.bush at rsmart.com>, sakai-user
>        <sakai-user at collab.sakaiproject.org>, Sakai-Dev
>        <sakai-dev at collab.sakaiproject.org>
> Message-ID:
>        <
> CBA500AB728544458AAED0758F72F6C5032E06680A at ITS-ECLS-2-VS4.adsroot.itcs.umich.edu
> >
>
> Content-Type: text/plain; charset="us-ascii"
>
> John,
>
> I think equation support can be divided into two parts: (1) the ability to
> render good quality image for equation in browsers and (2) the ability to
> support creating/editing LaTex/MathML equation.
>
> As for part (1), I think the trend now is to use MathJax display engine(
> http://www.mathjax.org/), which support all browsers and both LaTex and
> MathML. Here is a previous discussion thread for replacing jsMath with
> MathJax:
> http://old.nabble.com/-Building-Sakai--MathJax-to-replace-jsMath-in-rWiki--td29464530.html
>
> For part (2), I haven't checked their licences or prices yet. Some plugins
> render equation images and embed into FCKEditor. DragMath (
> http://www.dragmath.bham.ac.uk/integrations.html) can output LaTex
> formatted string, which can be displayed by MathJax afterwards.
>
> Part 1 seems to be a low-hanging fruit, and I hope that can solve at least
> 50% of user needs. Equation support is on our top to-do list here. We'd love
> to hear suggestions from other teams.
>
> Thanks,
>
> - Zhen
> ________________________________________
> From: sakai-dev-bounces at collab.sakaiproject.org [
> sakai-dev-bounces at collab.sakaiproject.org] On Behalf Of John Bush [
> john.bush at rsmart.com]
> Sent: Friday, October 22, 2010 11:33 AM
> To: sakai-user; Sakai-Dev
> Subject: [Building Sakai] math editor for fckeditor
>
> Is anyone doing anything to bring a math editor into sakai?  I know
> about jsmath for rwiki and sferyx for melete, but something that plugs
> into the fckeditor is the ideal, since that give the most widespread
> use.  I stumbled across I decent blog that talks about some of the
> options for moodle, but seems relevant to us as well.
>
> http://www.stattler.com/blog/latex-equation-drupal-blog
>
> This look like the best contender, as there is already a fckeditor
> plugin for this tool, check it out:
>
> check this out, http://www.codecogs.com/pages/forums/pagegen.php?id=1639
>
> Is anyone using this or an alternative, care to share experiences ?
>
> --
> John Bush
> 602-490-0470
> _______________________________________________
> sakai-dev mailing list
> 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 with a subject of
> "unsubscribe"
>
>
> ------------------------------
>
> Message: 20
> Date: Fri, 22 Oct 2010 10:37:22 -0700
> From: Karen Tsao <ktsao at stanford.edu>
> Subject: Re: [Building Sakai] How to fix this problem with
>        Tests&Quizzes and Chat tools
> To: Tin Nguyen <nguyentrongtin89 at gmail.com>
> Cc: sakai-dev at collab.sakaiproject.org
> Message-ID:
>        <AANLkTi=aa-tDp_Wew9rC8J9jNkuJndXTmCQ0W1qu_SML at mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hi Tin,
>
> I am not sure what causes the error. However, I notice you use JDK 1.6, can
> you please check if you have the following line added in the tomcat startup
> script?
>
> *-Dsun.lang.ClassLoader.allowArraySyntax=true *
>
> If you don't have it, please add it in and let me know if it can fix your
> problem.
>
> Thanks,
> Karen
>
> On Fri, Oct 22, 2010 at 12:27 AM, Tin Nguyen <nguyentrongtin89 at gmail.com
> >wrote:
>
> > Dear all,
> > When I clicked the Tests&Quizzes or Chat link, sakai showed the
> exception:
> >
> > org.sakaiproject.portal.api.PortalHandlerException:
> java.lang.IllegalArgumentException: Unable to find registered context for
> tool with ID sakai.samigo
> >
> >     at
> org.sakaiproject.portal.charon.SkinnableCharonPortal.doGet(SkinnableCharonPortal.java:768)
> > caused by: java.lang.IllegalArgumentException: Unable to find registered
> context for tool with ID sakai.samigo
> >     at
> org.sakaiproject.tool.impl.ActiveToolComponent$MyActiveTool.forward(ActiveToolComponent.java:497)
> >
> >     at
> org.sakaiproject.portal.charon.SkinnableCharonPortal.forwardTool(SkinnableCharonPortal.java:1221)
> >     at
> org.sakaiproject.portal.charon.handlers.ToolHandler.doTool(ToolHandler.java:204)
> >     at
> org.sakaiproject.portal.charon.handlers.ToolHandler.doGet(ToolHandler.java:96)
> >
> >     at
> org.sakaiproject.portal.charon.SkinnableCharonPortal.doGet(SkinnableCharonPortal.java:768)
> >     at javax.servlet.http.HttpServlet.service(HttpServlet.java:627)
> >     at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
> >
> >     at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)
> >     at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
> >     at
> org.sakaiproject.util.RequestFilter.doFilter(RequestFilter.java:646)
> >
> >     at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215)
> >     at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
> >     at
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
> >
> >     at
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:172)
> >     at
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
> >     at
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
> >
> >     at
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108)
> >     at
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:174)
> >     at
> org.apache.coyote.http11.Http11AprProcessor.process(Http11AprProcessor.java:843)
> >
> >     at
> org.apache.coyote.http11.Http11AprProtocol$Http11ConnectionHandler.process(Http11AprProtocol.java:679)
> >     at
> org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:1293)
> >     at java.lang.Thread.run(Thread.java:619)
> >
> > I tried to clean all (database, tomcat, sakai source). After that I
> > installed and deployed again, but not effect.
> > My system is:
> >
> >    - Tomcat 5.5.31
> >    - Sakai-src 2.7.1
> >    - MySQL database 5.1
> >    - Win 7 Home 64bit
> >    - JDK 1.6.0_21
> >
> >
> > _______________________________________________
> > sakai-dev mailing list
> > 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 with a subject of
> > "unsubscribe"
> >
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20101022/f34b720d/attachment-0001.html
>
> ------------------------------
>
> Message: 21
> Date: Fri, 22 Oct 2010 17:54:47 +0000
> From: "Richwine, Brian L" <brichwin at indiana.edu>
> Subject: Re: [Building Sakai] math editor for fckeditor
> To: "Qian, Zhen" <zqian at umich.edu>, John Bush <john.bush at rsmart.com>,
>        sakai-user <sakai-user at collab.sakaiproject.org>, Sakai-Dev
>        <sakai-dev at collab.sakaiproject.org>
> Cc: "accessibility at collab.sakaiproject.org WG
>        \(accessibility at collab.sakaiproject.org\)"
>        <accessibility at collab.sakaiproject.org>
> Message-ID:
>        <D0FD37EC6A2B874984F5EEC59677E4C4E9102B at IU-MSSG-MBX104.ads.iu.edu>
> Content-Type: text/plain; charset="us-ascii"
>
> If work towards bringing math to Sakai is taking place, it would be great
> if the results were accessible.
>
> Accessible math (for screen-reader users for instance) still has a little
> ways to go. The only accessible paths I've seen supported involve using
> MathML. Browser plug-ins (like MathPlayer for IE) let users navigate and
> explore the equation audibly, can highlight math as it is spoken, and allow
> for in browser magnification of the equation. There are MathML-to-Braille
> translators which would make the work of folks who have to convert course
> materials for blink students into Braille much easier if the math was
> already in MathML.
>
> LaTeX is really a printer markup language, and as a result, is not as
> purely semantic as MathML is. LaTeX codes for equations are frequently
> chosen from a standpoint of achieving a specific visual result, and often
> don't supply enough information semantically and hierarchically to make the
> relationships between terms clear.  Equations coded in MathML are
> semantically and hierarchically correct and machine readable and as such can
> be computed -- equations coded in LaTeX are predictable in their appearance
> but often are semantically and hierarchically ambiguous and thus are not
> machine readable for the purpose of computation.  Since equations coded as
> LaTeX aren't always machine readable, they also aren't in a format that
> adaptive technologies such as screen-readers can announce clearly and
> accurately to their users. It is our experience that LaTeX to MathML
> convertors (such as using MathJax with MathPlayer) fail to do an accurate
> job for this reason.
>
> Brian Richwine
>
> Brian Richwine
> Sakai Accessibility Working Group
> Adaptive Technology Support Specialist
> Adaptive Technology and Accessibility Centers
> Indiana University - Bloomington/Indianapolis
> http://iuadapts.indiana.edu
> (812) 856-4112
>
>
>
> -----Original Message-----
> From: sakai-dev-bounces at collab.sakaiproject.org [mailto:
> sakai-dev-bounces at collab.sakaiproject.org] On Behalf Of Qian, Zhen
> Sent: Friday, October 22, 2010 12:50 PM
> To: John Bush; sakai-user; Sakai-Dev
> Subject: Re: [Building Sakai] math editor for fckeditor
>
> John,
>
> I think equation support can be divided into two parts: (1) the ability to
> render good quality image for equation in browsers and (2) the ability to
> support creating/editing LaTex/MathML equation.
>
> As for part (1), I think the trend now is to use MathJax display engine(
> http://www.mathjax.org/), which support all browsers and both LaTex and
> MathML. Here is a previous discussion thread for replacing jsMath with
> MathJax:
> http://old.nabble.com/-Building-Sakai--MathJax-to-replace-jsMath-in-rWiki--td29464530.html
>
> For part (2), I haven't checked their licences or prices yet. Some plugins
> render equation images and embed into FCKEditor. DragMath (
> http://www.dragmath.bham.ac.uk/integrations.html) can output LaTex
> formatted string, which can be displayed by MathJax afterwards.
>
> Part 1 seems to be a low-hanging fruit, and I hope that can solve at least
> 50% of user needs. Equation support is on our top to-do list here. We'd love
> to hear suggestions from other teams.
>
> Thanks,
>
> - Zhen
> ________________________________________
> From: sakai-dev-bounces at collab.sakaiproject.org [
> sakai-dev-bounces at collab.sakaiproject.org] On Behalf Of John Bush [
> john.bush at rsmart.com]
> Sent: Friday, October 22, 2010 11:33 AM
> To: sakai-user; Sakai-Dev
> Subject: [Building Sakai] math editor for fckeditor
>
> Is anyone doing anything to bring a math editor into sakai?  I know about
> jsmath for rwiki and sferyx for melete, but something that plugs into the
> fckeditor is the ideal, since that give the most widespread use.  I stumbled
> across I decent blog that talks about some of the options for moodle, but
> seems relevant to us as well.
>
> http://www.stattler.com/blog/latex-equation-drupal-blog
>
> This look like the best contender, as there is already a fckeditor plugin
> for this tool, check it out:
>
> check this out, http://www.codecogs.com/pages/forums/pagegen.php?id=1639
>
> Is anyone using this or an alternative, care to share experiences ?
>
> --
> John Bush
> 602-490-0470
> _______________________________________________
> sakai-dev mailing list
> 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 with a subject of
> "unsubscribe"
> _______________________________________________
> sakai-dev mailing list
> 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 with a subject of
> "unsubscribe"
>
>
> ------------------------------
>
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>
>
> End of sakai-dev Digest, Vol 20, Issue 21
> *****************************************
>



-- 
Nuno Fernandes  .  { Analyst/Programmer }

|| web  . { http://tinyurl.com/nfgrilo  |  http://interacto.net  |
follow_me @ nfgrilo }
|| work . { interacto.net  |  Sakai Project  |  Universidade Fernando Pessoa
}
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20101024/72a8f85b/attachment.html