You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Mi...@swissre.com on 2004/07/14 14:43:57 UTC
maven:maven jelly tag
I have a general question on maven jelly tag
when I launch from a maven project another project using the maven jelly
tag is the maven jelly context of the "father" inherited ? and in case how
to pass a parameter to the new project ?
I tried something like
<goal name="assemble-ear-application"
description="recursivelly calling all the defined components" >
<ant:echo>modules are already extracted from cvs</ant:echo>
<util:tokenize var="application.modules.sequence" delim=",">
${application.modules.sequence}</util:tokenize>
<j:forEach var="component.name" items="
${application.modules.sequence}" indexVar="moduleNumber">
<ant:echo> Module to extract ${moduleNumber}, which is
${component.name}</ant:echo>
<!-- calling maven on each module -->
<ant:echo message="component ${component.name}
about to build"/>
<util:available file="${basedir}/../../../
${component.name}/admin/project.xml">
<j:set var="my.parameter" value="test" /> <!--
trying to pass via the jelly context -->
<maven:maven descriptor="${basedir}/../../../
${component.name}/admin/project.xml" ignoreFailures="false">
</maven:maven>
</j:forEach>
</goal>
unfortunately in the son project I do not get any evidence of my.parameter
, is this feature not available or there is another way on how to pass
parameters ?
I will be greatfull to any of the community who could shed some light on
this argument.
By the way thanks a lot for the great work you have done on maven 1.0 ,
which I could easily test without collateral effects.
Regards
Michele
This e-mail, including attachments, is intended for the person(s) or
company named and may contain confidential and/or legally privileged
information. Unauthorized disclosure, copying or use of this information
may be unlawful and is prohibited. If you are not the intended recipient,
please delete this message and notify the sender
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: maven:maven jelly tag
Posted by "Jefferson K. French" <je...@frenches.org>.
Thanks, Brett. I thought my -D override wasn't being taken by a goal
in a subproject invoked with maven:maven. Based on your response I
figured I had a bug in my maven.xml. It turns out I had a line in the
subproject that explicitly loaded a property file, thereby overriding
the -D override.
Jeff
On Tue, 24 Aug 2004, at 15:12:07 [GMT +1000] Brett Porter wrote:
> yes, they should. they are also available from ${systemScope.getProperty('foo')}
> On Mon, 23 Aug 2004 23:38:34 -0500, Jefferson K. French
> <je...@frenches.org> wrote:
>> What about properties overridden with -D? Is there any way to get those
>> properties into the root context? Should they be there by default?
>>
>> Jeff
--
mailto:jeff@frenches.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: maven:maven jelly tag
Posted by Brett Porter <br...@gmail.com>.
yes, they should. they are also available from ${systemScope.getProperty('foo')}
On Mon, 23 Aug 2004 23:38:34 -0500, Jefferson K. French
<je...@frenches.org> wrote:
> What about properties overridden with -D? Is there any way to get those
> properties into the root context? Should they be there by default?
>
> Jeff
>
> On Thu, 15 Jul 2004, at 10:03:25 [GMT +1000] Brett Porter wrote:
>
> > no, the current context is not passed in. If you j:set with
> > scope="parent" it will be put into the root context which will be
> > shared everywhere.
>
> > On Wed, 14 Jul 2004 14:43:57 +0200, michele_forte@swissre.com
> > <mi...@swissre.com> wrote:
> >> I have a general question on maven jelly tag
> >>
> >> when I launch from a maven project another project using the maven jelly
> >> tag is the maven jelly context of the "father" inherited ? and in case how
> >> to pass a parameter to the new project ?
>
> --
> mailto:jeff@frenches.org
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: maven:maven jelly tag
Posted by "Jefferson K. French" <je...@frenches.org>.
What about properties overridden with -D? Is there any way to get those
properties into the root context? Should they be there by default?
Jeff
On Thu, 15 Jul 2004, at 10:03:25 [GMT +1000] Brett Porter wrote:
> no, the current context is not passed in. If you j:set with
> scope="parent" it will be put into the root context which will be
> shared everywhere.
> On Wed, 14 Jul 2004 14:43:57 +0200, michele_forte@swissre.com
> <mi...@swissre.com> wrote:
>> I have a general question on maven jelly tag
>>
>> when I launch from a maven project another project using the maven jelly
>> tag is the maven jelly context of the "father" inherited ? and in case how
>> to pass a parameter to the new project ?
--
mailto:jeff@frenches.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: maven:maven jelly tag
Posted by Brett Porter <br...@gmail.com>.
no, the current context is not passed in. If you j:set with
scope="parent" it will be put into the root context which will be
shared everywhere.
On Wed, 14 Jul 2004 14:43:57 +0200, michele_forte@swissre.com
<mi...@swissre.com> wrote:
> I have a general question on maven jelly tag
>
> when I launch from a maven project another project using the maven jelly
> tag is the maven jelly context of the "father" inherited ? and in case how
> to pass a parameter to the new project ?
>
> I tried something like
>
> <goal name="assemble-ear-application"
> description="recursivelly calling all the defined components" >
>
> <ant:echo>modules are already extracted from cvs</ant:echo>
>
> <util:tokenize var="application.modules.sequence" delim=",">
> ${application.modules.sequence}</util:tokenize>
> <j:forEach var="component.name" items="
> ${application.modules.sequence}" indexVar="moduleNumber">
> <ant:echo> Module to extract ${moduleNumber}, which is
> ${component.name}</ant:echo>
>
> <!-- calling maven on each module -->
> <ant:echo message="component ${component.name}
> about to build"/>
> <util:available file="${basedir}/../../../
> ${component.name}/admin/project.xml">
>
> <j:set var="my.parameter" value="test" /> <!--
> trying to pass via the jelly context -->
>
> <maven:maven descriptor="${basedir}/../../../
> ${component.name}/admin/project.xml" ignoreFailures="false">
>
> </maven:maven>
>
> </j:forEach>
>
> </goal>
>
> unfortunately in the son project I do not get any evidence of my.parameter
> , is this feature not available or there is another way on how to pass
> parameters ?
>
> I will be greatfull to any of the community who could shed some light on
> this argument.
>
> By the way thanks a lot for the great work you have done on maven 1.0 ,
> which I could easily test without collateral effects.
>
> Regards
>
> Michele
>
> This e-mail, including attachments, is intended for the person(s) or
> company named and may contain confidential and/or legally privileged
> information. Unauthorized disclosure, copying or use of this information
> may be unlawful and is prohibited. If you are not the intended recipient,
> please delete this message and notify the sender
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org