Migrate jelly execute scripts to M2? (was RE: Wanted: Help with documentation on M2)

[Siegfried Heintze <si...@heintze.com>]

I would like to migrate my custom m1 jelly script from m1 to m2 that
executes my program. As per Dan's advice, I have been searching with
"execute" and not having much luck. Can I get a few more hints?

Also, I've been thinking: what I really want is a way to automatically
generate either C++ (using JNI) or bat files or sh files that assemble the
monstrous class paths and run my java programs. Would such a code generator
be best implemented as a maven plugin or eclipse plugin -- or something
else?

Thanks,
Siegfried


-----Original Message-----
From: dan tran [mailto:dantran@gmail.com] 
Sent: Sunday, October 16, 2005 10:04 AM
To: Maven Users List
Subject: Re: Wanted: Help with documentation on M2

Siegfried,
 The development team is actively working on m2 documentation, and I beleive
you will see lots doco will be available soon. Voting is going on dev list
to
load up new doco site layout
 However, I have seen lot traffic discussion about having a mojo to do
exactly what
your try to do by invoking java with classpath containing dependency
artifacts.
 Here are some links that my help
 http://mojo.codehaus.org/maven-execute-plugin/ deprecated
 http://docs.codehaus.org/display/MAVEN/Maven+Runtime
 Search the archive for "execute", i am sure you will find more info.
 Assume that the desired plugin/mojo is available, all you need is
a pom.xml + the plugin's configuration in the pom
 Hope it helps
 -D

 On 10/16/05, Siegfried Heintze <si...@heintze.com> wrote:
>
> I'm reading http://maven.apache.org/maven2/general.html and
> http://maven.apache.org/maven2/maven1.html#m1-maven-xml and I still don't
> understand where I learn about converting the following maven.xml file
> (see
> below) for use with m2. Can someone point me to the proper URL that
> contains
> the M2 documentation that will tell me how to convert a minimal maven 1.1
> project to m2 given the maven.xml file below?
>
> Thanks,
> Siegfried
>
> <?xml version="1.0" encoding="utf-8"?>
>
> <project default="jar" xmlns:maven="jelly:maven" xmlns:ant="jelly:ant"
> xmlns:j="jelly:core" xmlns:u="jelly:util">
> <goal name="run" prereqs="jar">
> <ant:java classname="mdn.testapp.App" fork="true">
> <ant:classpath>
> <ant:pathelement
> location="${maven.build.dir}/${maven.final.name <http://maven.final.name>
> }.jar"/>
> <j:forEach var="lib" items="${pom.artifacts}">
> <ant:pathelement path="${lib.path}"/>
> </j:forEach>
> </ant:classpath>
> </ant:java>
> </goal>
> </project>
>
>
> ---------------------------------------------------------------------
> 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: Migrate jelly execute scripts to M2? (was RE: Wanted: Help with documentation on M2)

[Chris Berry <ch...@gmail.com>]

Hi Siegfried,
I think the short answer is; write a plugin.
Now if you're like me, and your Jelly was mostly just a bunch of Ant calls
with a bit of Jelly glue, then you might consider using the new m2 Ant
plugins. This would allow you to transfer the knowledge directly to an Ant
buildfile and simply execute that from your plugin. It's pretty straight
forward.
BTW: you may need to use the Ant Tasks in ant-contrib to fill in some of the
script functionality that is missing in Ant.
Cheers,
-- Chris

On 11/1/05, Siegfried Heintze <si...@heintze.com> wrote:
>
> I would like to migrate my custom m1 jelly script from m1 to m2 that
> executes my program. As per Dan's advice, I have been searching with
> "execute" and not having much luck. Can I get a few more hints?
>
> Also, I've been thinking: what I really want is a way to automatically
> generate either C++ (using JNI) or bat files or sh files that assemble the
> monstrous class paths and run my java programs. Would such a code
> generator
> be best implemented as a maven plugin or eclipse plugin -- or something
> else?
>
> Thanks,
> Siegfried
>
>
> -----Original Message-----
> From: dan tran [mailto:dantran@gmail.com]
> Sent: Sunday, October 16, 2005 10:04 AM
> To: Maven Users List
> Subject: Re: Wanted: Help with documentation on M2
>
> Siegfried,
> The development team is actively working on m2 documentation, and I
> beleive
> you will see lots doco will be available soon. Voting is going on dev list
> to
> load up new doco site layout
> However, I have seen lot traffic discussion about having a mojo to do
> exactly what
> your try to do by invoking java with classpath containing dependency
> artifacts.
> Here are some links that my help
> http://mojo.codehaus.org/maven-execute-plugin/ deprecated
> http://docs.codehaus.org/display/MAVEN/Maven+Runtime
> Search the archive for "execute", i am sure you will find more info.
> Assume that the desired plugin/mojo is available, all you need is
> a pom.xml + the plugin's configuration in the pom
> Hope it helps
> -D
>
> On 10/16/05, Siegfried Heintze <si...@heintze.com> wrote:
> >
> > I'm reading http://maven.apache.org/maven2/general.html and
> > http://maven.apache.org/maven2/maven1.html#m1-maven-xml and I still
> don't
> > understand where I learn about converting the following maven.xml file
> > (see
> > below) for use with m2. Can someone point me to the proper URL that
> > contains
> > the M2 documentation that will tell me how to convert a minimal maven
> 1.1
> > project to m2 given the maven.xml file below?
> >
> > Thanks,
> > Siegfried
> >
> > <?xml version="1.0" encoding="utf-8"?>
> >
> > <project default="jar" xmlns:maven="jelly:maven" xmlns:ant="jelly:ant"
> > xmlns:j="jelly:core" xmlns:u="jelly:util">
> > <goal name="run" prereqs="jar">
> > <ant:java classname="mdn.testapp.App" fork="true">
> > <ant:classpath>
> > <ant:pathelement
> > location="${maven.build.dir}/${maven.final.name<http://maven.final.name><
> http://maven.final.name>
> > }.jar"/>
> > <j:forEach var="lib" items="${pom.artifacts}">
> > <ant:pathelement path="${lib.path}"/>
> > </j:forEach>
> > </ant:classpath>
> > </ant:java>
> > </goal>
> > </project>
> >
> >
> > ---------------------------------------------------------------------
> > 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
>
>