buildr-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Antoine Toulme <anto...@lunar-ocean.com>
Subject Re: Java Processes
Date Fri, 05 Aug 2011 17:33:33 GMT
Please, that would certainly help!

Antoine

On Fri, Aug 5, 2011 at 07:41, Ian Nowland <ian.nowland@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 <ian.nowland@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
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message