[Building Sakai] Issue? during maven build

[Steve Swinsburg]

Hi Gerwood,

Those build times are extremely long. Is your repository on your local  
machine or networked? Also, is your Tomcat local or remote? What are  
your MAVEN_OPTS and settings.xml?

Normal build (mvn clean install sakai:deploy)
[INFO] Total time: 10 minutes 15 seconds
[INFO] Finished at: Tue Jun 16 11:33:26 BST 2009
[INFO] Final Memory: 135M/254M

Offline and without tests (mvn clean install sakai:deploy -o - 
Dmaven.test.skip=true) I get:
[INFO] Total time: 4 minutes 5 seconds
[INFO] Finished at: Tue Jun 16 11:40:20 BST 2009
[INFO] Final Memory: 135M/254M

 From Australia I was getting similar build times to above. There's  
definitely some tweaking that can be done, an hour to build is absurd.


cheers,
Steve

---
Steve Swinsburg
Portal Systems Developer
Centre for e-Science
Lancaster University
Lancaster
LA1 4YT

email: s.swinsburg at lancaster.ac.uk
phone: +44 (0) 1524 594870







On 16 Jun 2009, at 02:37, Gerwood Stewart wrote:

> 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
>
> _______________________________________________
> 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/20090616/1d580f0f/attachment.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2437 bytes
Desc: not available
Url : http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20090616/1d580f0f/attachment.bin