[xwiki-dev] Maven/build help

Vincent Massol vincent at massol.net
Tue Jan 2 23:41:29 CET 2007


Hi Marc,

> -----Original Message-----
> From: Marc Lijour [mailto:marc at lijour.net]
> Sent: mardi 2 janvier 2007 23:15
> To: xwiki-dev at objectweb.org
> Subject: [xwiki-dev] Maven/build help
> 
> I try to get into maven to build xwiki but I don't find any doc on
> xwiki.org.

This is voluntary as it's not ready yet. That said it's good to have a
"customer" of the maven2 build so that we can improve it :-)
 
> When I checked out xwiki/trunk as a project in eclipse and I enable the
> maven2 plugin, it starts downloading a bunch of stuff and it complains
> about 2 items (see log below). Is that normal? Did I checked out
> everything I need?

That's because I haven't published these artifacts in the xwiki remote repo,
so you have to build them before they can be used by a module requiring
them.

The full build is available when you check xwiki/trunks-dev but this will
only work for xwiki committers as it required svn+ssh access. I'll create a
trunks-users for you if you want to try it out. 
 
> Is everybody using maven2 or ant or something else?

I am but it's not finished. That said it's building fine. It's just that
tests have not all been moved yet, some modules have no maven2 build and I
haven't fully tested the generated WAR yet so it may be missing some runtime
dependencies.
 
> A few pointers would be nice. Thanks.

Sure. We can start workong on this together if you want and document it as
we progress.

> (I still wonder why it has to download stuff since everything is
> available in the svn repository. 

Well that's how maven works... :-) Each module has binary dependencies and
each module produces artifacts which are depended upon by other modules.
When you build with mvn install generated artifacts are put in your local
repo (mvn deploy deploys them in the remote repo). They are then available
to other modules.

You can of course build everything from sources if you cd to the top level
of the source tree (trunks-dev for now, see above).

To better understand this see
http://blogs.codehaus.org/people/vmassol/archives/think_tank.html#000953_bin
ary_dependency_builds

> Actually it would be a good idea to
> keep the libraries aside, in another folder, if they have to be re-used
> in different places but then why keeping them in the repository as
> well?)

Jars in libs/ will be removed when we remove the Ant build as Maven2 handles
this with the notion of repositories (local and remote).

[snip]

Thanks
-Vincent





	

	
		
___________________________________________________________________________ 
Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions ! 
Profitez des connaissances, des opinions et des expériences des internautes sur Yahoo! Questions/Réponses 
http://fr.answers.yahoo.com




More information about the devs mailing list