You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@buildr.apache.org by Ian Nowland <ia...@gmail.com> on 2011/08/05 16:41:51 UTC
Re: Java Processes
Do you want me to file an issue, and upload the code I have that produces
this?
--Ian
On Thu, Jul 28, 2011 at 10:16 AM, Alex Boisvert <al...@gmail.com>wrote:
> On Wed, Jul 27, 2011 at 12:29 PM, Ian Nowland <ia...@gmail.com>
> wrote:
>
> > I've got a buildr/jetty/jersey setup I've been playing around with (that
> > took an annoyingly long time to get configured) which is working pretty
> > much
> > as I would like iht to, except for that the process seems to kick off on
> > it's
> > own, meaning I can't see console output and I have to kill -9 it whenever
> I
> > want it to stop. I'm setting it off with a pretty typical:
> >
>
> Hmmm. I can't reproduce this with a simple Java main program. Output goes
> to stdout (as expected) and Ctrl-C kills both the buildr and the java main
> processes.
>
> task :run => :compile do
> > puts('Starting up with classpath ' + compile.dependencies.to_s + "
> "
> > + [compile.target.to_s].to_s)
> > Java::Commands.java('launcher.
> > MyServer', :classpath => compile.dependencies + [compile.target.to_s])
> > end
> >
>
> By the way, there is a standard run task since Buildr 1.4.5 that may save
> you some keystrokes,
>
> http://buildr.apache.org/more_stuff.html#run
>
> alex
>
Re: Java Processes
Posted by Ian Nowland <ia...@gmail.com>.
I was out of town for a few days, and then the amazon instance my code was
on crashed and I had to recover. Anyhow, it looks like Apache's JIRA for
buildr doesn't allow file uploading, but I pasted my code into the bug:
https://issues.apache.org/jira/browse/BUILDR-607
--Ian
On Fri, Aug 5, 2011 at 1:33 PM, Antoine Toulme <an...@lunar-ocean.com>wrote:
> Please, that would certainly help!
>
> Antoine
>
> On Fri, Aug 5, 2011 at 07:41, Ian Nowland <ia...@gmail.com> wrote:
>
> > Do you want me to file an issue, and upload the code I have that produces
> > this?
> >
> > --Ian
> >
> > On Thu, Jul 28, 2011 at 10:16 AM, Alex Boisvert <alex.boisvert@gmail.com
> > >wrote:
> >
> > > On Wed, Jul 27, 2011 at 12:29 PM, Ian Nowland <ia...@gmail.com>
> > > wrote:
> > >
> > > > I've got a buildr/jetty/jersey setup I've been playing around with
> > (that
> > > > took an annoyingly long time to get configured) which is working
> pretty
> > > > much
> > > > as I would like iht to, except for that the process seems to kick off
> > on
> > > > it's
> > > > own, meaning I can't see console output and I have to kill -9 it
> > whenever
> > > I
> > > > want it to stop. I'm setting it off with a pretty typical:
> > > >
> > >
> > > Hmmm. I can't reproduce this with a simple Java main program. Output
> > goes
> > > to stdout (as expected) and Ctrl-C kills both the buildr and the java
> > main
> > > processes.
> > >
> > > task :run => :compile do
> > > > puts('Starting up with classpath ' + compile.dependencies.to_s
> +
> > "
> > > "
> > > > + [compile.target.to_s].to_s)
> > > > Java::Commands.java('launcher.
> > > > MyServer', :classpath => compile.dependencies +
> [compile.target.to_s])
> > > > end
> > > >
> > >
> > > By the way, there is a standard run task since Buildr 1.4.5 that may
> save
> > > you some keystrokes,
> > >
> > > http://buildr.apache.org/more_stuff.html#run
> > >
> > > alex
> > >
> >
>
Re: Java Processes
Posted by Antoine Toulme <an...@lunar-ocean.com>.
Please, that would certainly help!
Antoine
On Fri, Aug 5, 2011 at 07:41, Ian Nowland <ia...@gmail.com> wrote:
> Do you want me to file an issue, and upload the code I have that produces
> this?
>
> --Ian
>
> On Thu, Jul 28, 2011 at 10:16 AM, Alex Boisvert <alex.boisvert@gmail.com
> >wrote:
>
> > On Wed, Jul 27, 2011 at 12:29 PM, Ian Nowland <ia...@gmail.com>
> > wrote:
> >
> > > I've got a buildr/jetty/jersey setup I've been playing around with
> (that
> > > took an annoyingly long time to get configured) which is working pretty
> > > much
> > > as I would like iht to, except for that the process seems to kick off
> on
> > > it's
> > > own, meaning I can't see console output and I have to kill -9 it
> whenever
> > I
> > > want it to stop. I'm setting it off with a pretty typical:
> > >
> >
> > Hmmm. I can't reproduce this with a simple Java main program. Output
> goes
> > to stdout (as expected) and Ctrl-C kills both the buildr and the java
> main
> > processes.
> >
> > task :run => :compile do
> > > puts('Starting up with classpath ' + compile.dependencies.to_s +
> "
> > "
> > > + [compile.target.to_s].to_s)
> > > Java::Commands.java('launcher.
> > > MyServer', :classpath => compile.dependencies + [compile.target.to_s])
> > > end
> > >
> >
> > By the way, there is a standard run task since Buildr 1.4.5 that may save
> > you some keystrokes,
> >
> > http://buildr.apache.org/more_stuff.html#run
> >
> > alex
> >
>