You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Jorg Heymans <jh...@apache.org> on 2006/10/08 16:47:31 UTC
Re: svn commit: r454149 - /cocoon/trunk/pom.xml
vgritsenko@apache.org wrote:
> Author: vgritsenko
> Date: Sun Oct 8 07:18:47 2006
> New Revision: 454149
>
> URL: http://svn.apache.org/viewvc?view=rev&rev=454149
> Log:
> include dists
>
> Modified:
> cocoon/trunk/pom.xml
>
> Modified: cocoon/trunk/pom.xml
> URL: http://svn.apache.org/viewvc/cocoon/trunk/pom.xml?view=diff&rev=454149&r1=454148&r2=454149
> ==============================================================================
> --- cocoon/trunk/pom.xml (original)
> +++ cocoon/trunk/pom.xml Sun Oct 8 07:18:47 2006
> @@ -37,13 +37,16 @@
> <name>Apache Cocoon</name>
> <url>http://cocoon.apache.org</url>
> <inceptionYear>1999</inceptionYear>
> +
> <modules>
> <module>blocks</module>
> <module>commons</module>
> <module>core</module>
> <module>tools</module>
> <module>site/cocoon-maven-site-skin</module>
> + <module>dists</module>
> </modules>
I think we should move everything that is not needed on a 'daily' basis
(eg assembly and site generation) out of the default build profile.
Based on this i would create a "dist" and "site" profile and move the
modules and required plugin configurations to this profile.
WDOT?
Jorg
Re: svn commit: r454149 - /cocoon/trunk/pom.xml
Posted by Jorg Heymans <jh...@apache.org>.
Reinhard Poetz wrote:
> Site generation has already moved to trunk/site/pom.xml - see my reply
> to your question from some days ago (I would also be interested in your
> opinion on the questions there).
The idea of site/pom.xml as central point for site generation is
perfectly fine.
> I only left the skin in the core to ensure that it gets installed to the
> local repo. I could deploy it to a snapshot repository though. WDYT?
Yep good idea just snapshot it to people.a.o. Once this is done we can
remove the module ref from the root pom.
I'll think again about my profile idea, perhaps we can just leave the
module poms for site and dist disconnected from the root pom by simply
not referencing them there.
Thanks
Jorg
Re: svn commit: r454149 - /cocoon/trunk/pom.xml
Posted by Reinhard Poetz <re...@apache.org>.
Jorg Heymans wrote:
> I think we should move everything that is not needed on a 'daily' basis
> (eg assembly and site generation) out of the default build profile.
>
> Based on this i would create a "dist" and "site" profile and move the
> modules and required plugin configurations to this profile.
Site generation has already moved to trunk/site/pom.xml - see my reply to your
question from some days ago (I would also be interested in your opinion on the
questions there).
I only left the skin in the core to ensure that it gets installed to the local
repo. I could deploy it to a snapshot repository though. WDYT?
--
Reinhard Pötz Independent Consultant, Trainer & (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
--------------------------------------------------------------------
___________________________________________________________
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
Re: svn commit: r454149 - /cocoon/trunk/pom.xml
Posted by Vadim Gritsenko <va...@reverycodes.com>.
Jorg Heymans wrote:
>
> Based on this i would create a "dist" and "site" profile and move the
> modules and required plugin configurations to this profile.
Dists is already "profilized" and includes only the thing you need daily - the
sample web application. Everything else is optional.
Vadim