You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Philip Crotwell <cr...@seis.sc.edu> on 2003/01/28 16:12:37 UTC

reactor site-front-end and noop

Hi

The example reactor maven.xml from the commons project used to use noop
within the site-front-end to get a list of projects in order to build
navigaton.xml. This no longer seems to work with the current cvs. I did
some greping in the latest cvs but could find no reference to noop.

What is the new version of noop or is there a new way to do the reactor
site-front-end?

See
http://cvs.apache.org/viewcvs/jakarta-commons/maven.xml?rev=HEAD&content-type=text/vnd.viewcvs-markup
for the reactor example.

thanks,
Philip

Re: reactor site-front-end and noop

Posted by Jason van Zyl <ja...@zenplex.com>.
On Tue, 2003-01-28 at 10:12, Philip Crotwell wrote:
> Hi
> 
> The example reactor maven.xml from the commons project used to use noop
> within the site-front-end to get a list of projects in order to build
> navigaton.xml. This no longer seems to work with the current cvs. I did
> some greping in the latest cvs but could find no reference to noop.
> 
> What is the new version of noop or is there a new way to do the reactor
> site-front-end?

In CVS head if you don't define any goals to the reactor it just
processes the POMs. You don't need any dummy goals anymore. Just don't
specify any goals and the POMs will simply be aggregated into
${reactorProjects} in the current jelly context and then you can do
whatever you want.


> See
> http://cvs.apache.org/viewcvs/jakarta-commons/maven.xml?rev=HEAD&content-type=text/vnd.viewcvs-markup
> for the reactor example.
> 
> thanks,
> Philip
> 
> 
> --
> To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
-- 
jvz.

Jason van Zyl
jason@zenplex.com
http://tambora.zenplex.org

In short, man creates for himself a new religion of a rational
and technical order to justify his work and to be justified in it.
  
  -- Jacques Ellul, The Technological Society

Re: reactor site-front-end and noop

Posted by Jason van Zyl <ja...@zenplex.com>.
On Tue, 2003-01-28 at 12:46, Philip Crotwell wrote:
> That helped, at least I am not getting a error about noop. But with
> goals="" it appears that it is grabbing the default goal and trying to
> apply that to all the subprojects, instead of doing a "noop".

Don't even specify the goals attribute. I'll add a check for an empty
string.

> Just FYI, as I can simply remove the default goal. But if this is the
> expected behavior, then we may need a noop in cases where you want to do a
> noop, but there is a default goal???
> 
> thanks,
> PHilip
> 
> 
> --
> To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
-- 
jvz.

Jason van Zyl
jason@zenplex.com
http://tambora.zenplex.org

In short, man creates for himself a new religion of a rational
and technical order to justify his work and to be justified in it.
  
  -- Jacques Ellul, The Technological Society

Re: reactor site-front-end and noop

Posted by Jason van Zyl <ja...@zenplex.com>.
On Tue, 2003-01-28 at 14:45, Philip Crotwell wrote:
> Hi
> 
> I am using a cvs version that I grabbed and bootstrapped today.
> 
> Just in case, here is the section from the maven.xml, and the output is
> below. Is there another project that you know of that is using the
> reactor like this for comparison purposes?
> 
> thaks,
> Philip
> 
>   <goal name="site-front-end">
> 
> <echo>before reactor
> </echo>
>     <maven:reactor
>       basedir="${basedir}/geotools-src"
>       includes="*/project.xml"
>       excludes="gui/project.xml"
>       ignoreFailures="false"
>     />
> <echo>after reactor

Sorry, the reactor was also change NOT to hold on to projects after
processing unless specifically requested. So you also need the

postProcessing="true"

Then ${reactorProjects} will get populated.

> </echo>
> 
>     <!--
>       ||
>       || Generate the documentation for the front-end site. First we will
>       || generate the navigation based on the projects that we just
>       || processed, then we will generate the front-end site itself.
>       ||
>     -->
> 
>     <echo>
>       reactor list = ${reactorProjects}
>     </echo>
> 
>     <attainGoal name="init-texen-tag"/>
> 
>     <texen:generate
>       controlTemplate="navigation.vm"
>       outputDirectory="${basedir}/xdocs"
>       templatePath="${basedir}"
>       outputFile="navigation.xml"
>       reactorProjects="${reactorProjects}"
>     />

The texen stuff is gone too. You can either use JSL stuff now, or you
can use the velocity tag lib which kicks texen's ass.

>     <attainGoal name="xdoc"/>
> 
>   </goal>
> 
> and the output is:
> ...
> +----------------------------------------
> | Processing geotools-algorithms
> +----------------------------------------
> +----------------------------------------
> | Processing geotools-svgsupport
> +----------------------------------------
>     [echo] after reactor
> 
>     [echo]
>       reactor list = []
> 
> 
> BUILD FAILED
> No goal [init-texen-tag]
> Total time:  36 seconds
> 
> 
> 
> 
> 
> --
> To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
-- 
jvz.

Jason van Zyl
jason@zenplex.com
http://tambora.zenplex.org

In short, man creates for himself a new religion of a rational
and technical order to justify his work and to be justified in it.
  
  -- Jacques Ellul, The Technological Society

Re: reactor site-front-end and noop

Posted by Philip Crotwell <cr...@seis.sc.edu>.
Hi

I am using a cvs version that I grabbed and bootstrapped today.

Just in case, here is the section from the maven.xml, and the output is
below. Is there another project that you know of that is using the
reactor like this for comparison purposes?

thaks,
Philip

  <goal name="site-front-end">

<echo>before reactor
</echo>
    <maven:reactor
      basedir="${basedir}/geotools-src"
      includes="*/project.xml"
      excludes="gui/project.xml"
      ignoreFailures="false"
    />
<echo>after reactor
</echo>

    <!--
      ||
      || Generate the documentation for the front-end site. First we will
      || generate the navigation based on the projects that we just
      || processed, then we will generate the front-end site itself.
      ||
    -->

    <echo>
      reactor list = ${reactorProjects}
    </echo>

    <attainGoal name="init-texen-tag"/>

    <texen:generate
      controlTemplate="navigation.vm"
      outputDirectory="${basedir}/xdocs"
      templatePath="${basedir}"
      outputFile="navigation.xml"
      reactorProjects="${reactorProjects}"
    />

    <attainGoal name="xdoc"/>

  </goal>

and the output is:
...
+----------------------------------------
| Processing geotools-algorithms
+----------------------------------------
+----------------------------------------
| Processing geotools-svgsupport
+----------------------------------------
    [echo] after reactor

    [echo]
      reactor list = []


BUILD FAILED
No goal [init-texen-tag]
Total time:  36 seconds

Re: reactor site-front-end and noop

Posted by Jason van Zyl <ja...@zenplex.com>.
On Tue, 2003-01-28 at 13:56, Philip Crotwell wrote:
> >
> > Don't even specify the goals attribute. I'll add a check for an empty
> > string.
> >
> 
> Humm, it is still picking up the default goal from the maven.xml in the
> subproject, so there still may be a problem even with no goal tag in the
> reactor.
> 
> But, if I remove the default goal from the subprojects maven.xml, then it
> gets past that, but the reactor list is empty.
> 
>     [echo]
>       reactor list = []
> 
> Has the ${reactorProjects} var changed???

No it has not changed. Please tell me what version you are using.

> thanks,
> Philip
> 
> 
> 
> 
> --
> To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
-- 
jvz.

Jason van Zyl
jason@zenplex.com
http://tambora.zenplex.org

In short, man creates for himself a new religion of a rational
and technical order to justify his work and to be justified in it.
  
  -- Jacques Ellul, The Technological Society

Re: What is preferred format for referring to artifacts in dependencies?

Posted by Jason van Zyl <ja...@zenplex.com>.
On Tue, 2003-01-28 at 14:20, Colin Sampaleanu wrote:
> When you have artifacts with a groupId and artifactId that are 
> different, which format is preferred, and should generally be used? This?
> 
>     <dependency>
>       <id>xdoclet:xdoclet-jboss-module</id>
>       <version>1.2b3-dev</version>
>     </dependency>
> 
> or this?

This one:

>     <dependency>
>       <groupId>xdoclet</groupId>
>       <artifactId>xdoclet-jboss-module</artifactId>
>       <version>1.2b3-dev</version>
>     </dependency>
> 
> Are both likely to stick around?

They will both be supported.

> 
> 
> --
> To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
-- 
jvz.

Jason van Zyl
jason@zenplex.com
http://tambora.zenplex.org

In short, man creates for himself a new religion of a rational
and technical order to justify his work and to be justified in it.
  
  -- Jacques Ellul, The Technological Society

What is preferred format for referring to artifacts in dependencies?

Posted by Colin Sampaleanu <co...@exis.com>.
When you have artifacts with a groupId and artifactId that are 
different, which format is preferred, and should generally be used? This?

    <dependency>
      <id>xdoclet:xdoclet-jboss-module</id>
      <version>1.2b3-dev</version>
    </dependency>

or this?

    <dependency>
      <groupId>xdoclet</groupId>
      <artifactId>xdoclet-jboss-module</artifactId>
      <version>1.2b3-dev</version>
    </dependency>

Are both likely to stick around?

Re: reactor site-front-end and noop

Posted by Philip Crotwell <cr...@seis.sc.edu>.
>
> Don't even specify the goals attribute. I'll add a check for an empty
> string.
>

Humm, it is still picking up the default goal from the maven.xml in the
subproject, so there still may be a problem even with no goal tag in the
reactor.

But, if I remove the default goal from the subprojects maven.xml, then it
gets past that, but the reactor list is empty.

    [echo]
      reactor list = []

Has the ${reactorProjects} var changed???

thanks,
Philip

Re: reactor site-front-end and noop

Posted by Philip Crotwell <cr...@seis.sc.edu>.
I take it back, I am not sure what it is doing, but there is another
maven.xml within the subproject, and looks like it is trying to execute
the default goal in that subproject.

How can I force a noop short of making sure no maven.xml file in any
subproject has a default goal?

thanks,
PHilip


On Tue, 28 Jan 2003, Philip Crotwell wrote:

>
> That helped, at least I am not getting a error about noop. But with
> goals="" it appears that it is grabbing the default goal and trying to
> apply that to all the subprojects, instead of doing a "noop".
>
> Just FYI, as I can simply remove the default goal. But if this is the
> expected behavior, then we may need a noop in cases where you want to do a
> noop, but there is a default goal???
>
> thanks,
> PHilip
>
>


-------------------------------------------------------------------------------
Philip Crotwell             crotwell@seis.sc.edu                  803-777-0955
-------------------------------------------------------------------------------

Re: reactor site-front-end and noop

Posted by Philip Crotwell <cr...@seis.sc.edu>.
That helped, at least I am not getting a error about noop. But with
goals="" it appears that it is grabbing the default goal and trying to
apply that to all the subprojects, instead of doing a "noop".

Just FYI, as I can simply remove the default goal. But if this is the
expected behavior, then we may need a noop in cases where you want to do a
noop, but there is a default goal???

thanks,
PHilip