[Building Sakai] Issue? during maven build

[Gerwood Stewart]

Matthew

Thanks for the reply. It is more or less what I thought was the case.

It does raise one issue for me at least, which is:
The Sakai build as a result of this has "errors that aren't errors". As you say this can be ignored but I would think it's something not overly onerous to fix which would clean up (and make clearer) the build process, and certainly make doing things like running -o or constantly checking with the 'net less necessary.

Gerwood


On 15/06/09 6:36 PM, "Matthew Buckett" <matthew.buckett at oucs.ox.ac.uk> wrote:

2009/6/15 Gerwood Stewart <gstewar8 at une.edu.au>:
> We are seeing this a lot in our 2.5.4 build.
>
> Is this actually a problem.

Not a big one. Your builds will work fine.

> In post (possibly all) cases it seems to only
> have an issue retrieving the POM file
> See the bold line. I believe this is the repository most of this is meant to
> come from...

Yep, basically the issue is that the artifact (eg
jaxen-1.1-beta-10.jar file)  exists in the Sakai repository but
doesn't have a .pom file to describe it (it's dependencies, copyright,
author, etc). Your maven build will work fine without a .pom file for
this artifact but maven will attempt to download one every time you
perform a build.

To get rid of this warning either:
-  build in offline mode: mvn -o install
or
- Create a fake jaxen-1.1-beta-10.pom file in your local repository
with the basic information (groupId, artifactId, version, etc),
however there are quite a few artifacts that don't have .pom files
used in the Sakai build.

--
  Matthew Buckett

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20090616/1c76d6d5/attachment.html