cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel Fagerstrom <dani...@nada.kth.se>
Subject Re: Using trunk
Date Mon, 27 Feb 2006 20:53:38 GMT
Jean-Baptiste Quenot skrev:
> * Jean-Baptiste Quenot:
...
> Also had to disable this:
> 
> @@ -36,9 +36,9 @@
>    <modules>
>      <module>cocoon-archetypes</module>
>      <module>cocoon-core</module>
> -    <module>cocoon-block-deployer</module>
> -    <module>cocoon-blocks-fw</module>
> -    <module>cocoon-default</module>
> +    <!--module>cocoon-block-deployer</module-->
> +    <!--module>cocoon-blocks-fw</module-->
> +    <!--module>cocoon-default</module-->
>      <module>cocoon-mocks</module>
>      <!--  Blocks  -->
>      <module>cocoon-ajax</module>

They compile for me with a fresh update.

> BTW why blocks are downloaded instead of being built?  Example:
> 
> Downloading: http://cvs.apache.org/maven-snapshot-repository/org/apache/cocoon/cocoon-captcha-impl/1.0-SNAPSHOT/cocoon-captcha-impl-1.0-20060124.010051-6.jar

Probably you problem comes from downloading obsolete snapshot builds. I 
don't know exactly what algorithm Maven use for deciding if it should 
download snapshots from your local repository or the remote one. If you 
make a clean build from top level it works at least:

$ cd cocoon-trunk
$ mvn -Dmaven.test.skip=true clean install

Getting our automated snapshot build to work again would of course be 
much more convenient.

/Daniel

Mime
View raw message