So in other words 'deploy jar to shell' in the same way as 'deploy
war to webserver'.
Would we need different flavors such as:
deploy-to-bash
deploy-to-dos
etc? Maybe not since the java command I think is the same in all
those environments.
Would the shell script be an artifact in its own right? Probably
crazy but just throwing
out a few ideas.
Also I would still like to launch the app as one command rather than
having to wait
for the shell script to appear and then execute it at the prompt.
On 19 Sep 2005, at 20:17, Jesse McConnell wrote:
trygvis has a spiffy idea a bit ago about a new assembly type
plugin that
would produce a set up shell scripts (or batch files, wherever the
case may
be) that could be used for launching command line based applications..
the idea scales nicely into a handy mechanism for launching servers or
things of that nature.
I think the general feeling behind the concern was pretty well
summed up
with the alternative name of maven-pandorasbox-plugin since it
really is an
adhoc extension on the end of the build system. Sure it works but
it is
pretty low-tech.
I am looking into what it will take to put together a more complete
solution
to the problem a la trygvis's idea....it already exists in some
from inside
of plexus so it shouldn't be too terrible to put together..
I am thinking of two modes for the plugin atm, one that scans the
source of
the subproject for main methods and generates stubs for calling all
of those
objects, and another one that lets you specify in the
<configuration> of the
plugin that lets you map a script name to generate for a given
class's main
method. additional ideas along this vien are more then welcome atm :)
not sure when I'll have this together though...so would say go
ahead and
tweak the execute plugin if you like it to more things...submit
patchs on it
and I'll review/commit them if you don't already have commit access
to mojo.
jesse
On 9/19/05, Ashley Williams <[EMAIL PROTECTED]> wrote:
Just wondering why the controversy. Is it about where to best place
the task, or even whether it belongs in maven at all?
On 19 Sep 2005, at 18:38, Jesse McConnell wrote:
hi,
I was the one that cobbled that maven-execute-plugin together in
the sandbox
that you are referring too..
there is some discussion on irc around it...
my general feeling on it, and the reason I created it in the first
place was
that it was a great (and simple) way to have m2 manage the classpath
automatically for me. the idea behind the maven-execute-plugin
might not be
the best way about going it really. However, there are a number of
ways to
skin this cat..
I am not sure about going too far down this path since some of the
m2 devs
are _really_ not hot on this idea atm :) The best thing might be to
get a
bit of further comment on ths subject from kenney and trygvis..and
maybe
brett if he sees this.. If they have a solution they are happy with
then
I'll certainly put it together if it doesn't already exist in some
form...I
use this plugin in its current state all the time for running
little one off
programs I don't want to mess about with classpaths for.
btw, execute:jar shouldn't be too bad...though it might be that if
this
plugin lives on then it ought to be renamed...it doesn't exec perl
afterall.
Jesse
On 9/19/05, Kristian Nordal <[EMAIL PROTECTED]> wrote:
On Sep 19, 2005, at 6:55 PM, Kenney Westerhof wrote:
On Mon, 19 Sep 2005, Kristian Nordal wrote:
You could file a JIRA issue for that plugin to request a
'execute:jar' goal that executes the jar if it is an auto-
executable
jar (i.e. it's manifest has a Main-Class entry).
Done. http://jira.codehaus.org/browse/MOJO-34
Note that maven2 is a project management/build tool, not a generic
execution environment, so plugins like these don't belong there
(for now,
at least :))
Noted =)
--
Kristian
But I agree it would be easy if jar:execute worked too. ;)
On Sep 19, 2005, at 5:58 PM, Ashley Williams wrote:
Is there currently a java plugin for running regular main()
apps?
I've just checked the repository and I couldn't find one.
Currently
I define the following plugin in my pom:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-jar-plugin</artifactId>
<configuration>
<archive>
<manifest>
<mainClass>Server</mainClass>
</manifest>
</archive>
</configuration>
</plugin>
</plugins>
and would like to do something like this to run the app:
m2 java:java
but at the moment I have to do this:
java -jar file://<myrepository>/<myartifact>/myapp.jar
In fact I'd ideally like to run the app immediately after the
install:
m2 install java:java
Hi,
I've been thinking about the same thing. It would be nice to be
able
to just run the jar file with the correct dependencies in the
classpath directly.
There's a plugin at org.codehaus.mojo called maven-execute-
plugin (in
the sandbox), which does something like this (I don't know if it
currently works). From the docs: "A useful little plugin for
leveraging maven to build the required classpath to
execute the main method on an object." With an example for
running it
directly (can also be configured in the POM): "m2
execute:resources -
Dexecute.class="com.foo.X" -Dexecute.args="-h bar".
For this you would need an additional plugin (execute), why not
just
put this functionality into the jar plugin? So no more
configuration
is needed. It might be the wrong place for it, I don't know,
but it
would be nice to just write "m2 jar:run" =)
--
Regards,
Kristian
Thanks
AW
----------------------------------------------------------------
--
--
-
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]
--
Kenney Westerhof
http://www.neonics.com
GPG public key: http://www.gods.nl/~forge/kenneyw.key
------------------------------------------------------------------
--
-
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]
--
jesse mcconnell
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
jesse mcconnell
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
