[Building Sakai] Issue? during maven build

[Gerwood Stewart]

Matthew

Sorry if I sound like I'm carrying on a little, I realise this isn't necessarily a huge problem. I tried a compile with -o vs normal. The time difference (probably as a result of network wait) was:

Normal Build:
[INFO] BUILD SUCCESSFUL
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 63 minutes 4 seconds
[INFO] Finished at: Tue Jun 16 10:52:16 EST 2009
[INFO] Final Memory: 185M/879M
[INFO] ------------------------------------------------------------------------

Offline mode:
[INFO] BUILD SUCCESSFUL
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 38 minutes 56 seconds
[INFO] Finished at: Tue Jun 16 11:32:04 EST 2009
[INFO] Final Memory: 195M/894M
[INFO] ------------------------------------------------------------------------


The poms not being there do represent a fair amount of time even if not a technical problem. I'll will probably be using -o most of the time now but I wouldn't consider this the best of habit to get into.

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/680c09ad/attachment.html