On Thu, 2005-08-25 at 09:51 +0200, Nacho G. Mac Dowell wrote:
> > robert burrell donkin wrote:
> >
> >> ran
> >> $ maven clean
> >> $ maven build
> >
> maven build does also a maven clean
> 
> >> is it necessary to build the projects individually first? or do any
> >> properties need tuning?
> >
> now it is fixed. the thing is that jar:install should have been called 
> on goal build for each subproject
> could you please try to delete the jaxme group directory in the local 
> repository and try again?

this works well for me now. thanks :)

> > I have just tried the same. Funnily, for me it breaks earlier: I have 
> > the same problem with jaxmeapi as a dependency of jaxmexs.
> 
> I hope this is that Robert had built jaxmeapi some other time and it 
> installed jaxmeapi-0.6-dev.jar on the local repository. Could it be this 
> Robert? If not, then we might be in trouble...

nope: everything's cool. good work :)

> I'll explain the maven build process currently in use starting with the 
> subprojects:
> 
> - There is a goal defined build on common-build/maven.xml which (at the 
> moment - it could be anything) calls goals clean jar:install and site. 
> This way when we build a subproject individually we always now it is 
> going to be built as it would be from the top level project (you'll see 
> why below)
> 
> - On the top level project there is a goal called build which does the 
> following:
> 
> 1. Delete the maven.build.dir (target directory)
> 2. Gather project list and expose it to each subproject (for the tabbed 
> browsing). Also expose the top level project target directory (this way 
> all docs are generated directly on the top level target directory - 
> multiproject just makes a copy).
> 3. Execute goal build on each subproject (which is the one in 
> common-build/maven.xml)
> 4. We have tabbed browsing so we don't need aggregate navigation. Just 
> create the overview page.
> 5. Create top level site
> 
> Does this sound reasonable?

sounds good. it'd be nice to have this in the documentation somewhere.

BTW i think that we might be able to use a plugin to generate the
docbook manual using maven.

i've generated a descriptor for gump (you'll need to latest version of
the gump plugin and use the gump:multiproject task to generate it). i'll
talk to stefan and brett about testing this.

- robert

Attachment: signature.asc
Description: This is a digitally signed message part

Reply via email to