[Building Sakai] Stupid Maven 3 question

Steve Swinsburg steve.swinsburg at gmail.com
Tue Jan 22 15:44:40 PST 2013


I've had a similar issue recently. Maven 3.0.4 is much stricter than Maven 3.0.3 and has an issue with repository inheritance (feature/bug). That is, if you specify some repositories in a pom it will use only those, not inherit all repos from back up up the hierarchy. So you are likely not getting the correct repository set in the reactor. At least that was my observation.

I haven't checked if that is a reported issue or expected behaviour. If expected we need to fix our poms.

Maven 3.0.3 works fine if you can use that for the time being.

cheers,
Steve


On 23/01/2013, at 7:23 AM, Beth Kirschner <bkirschn at umich.edu> wrote:

> I just tried compiling sakai-trunk-all with Maven 3.0.4 ("mvn install sakai:deploy") - changing nothing excepting the MAVEN_HOME variable, and I get the following error:
> 
> [ERROR] No plugin found for prefix 'sakai' in the current project and in the plugin groups [org.apache.maven.plugins, org.codehaus.mojo] available from the repositories [local (/Users/bkirschn/.m2/repository), apache.incubating.plugins (http://people.apache.org/repo/m2-incubating-repository), central (http://repo.maven.apache.org/maven2)] -> [Help 1]
> 
> Would anyone like to point me to the error in my ways?
> 
> Thanks!
> - Beth
> 
> _______________________________________________
> 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"



More information about the sakai-dev mailing list