Thanks Brett , your suggestion worked perfectly ....
my regards
Michele
|---------+---------------------------->
| | Brett Porter |
| | <[EMAIL PROTECTED]|
| | il.com> |
| | |
| | |
| | 15/07/2004 02:03 |
| | Please respond to|
| | "Maven Users |
| | List" |
| | |
|---------+---------------------------->
>------------------------------------------------------------------------------------------------------------------------------|
|
|
|
|
|
|
|
|
|
|
| To: Maven Users List <[EMAIL
PROTECTED]> |
| cc: (bcc: Michele Forte/SwissRe)
|
| bcc: Michele Forte/SwissRe
|
| Subject: Re: maven:maven jelly tag
|
>------------------------------------------------------------------------------------------------------------------------------|
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, [EMAIL PROTECTED]
<[EMAIL PROTECTED]> 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: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
