Mailing-List: contact users-help@buildr.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@buildr.apache.org
Received-SPF: pass (athena.apache.org: local policy)
Subject: Re: run jetty from a known webapp directory or with at least a
 known classes folder
From: Martin Grotzke <martin.grotzke@javakaffee.de>
To: users@buildr.apache.org
In-Reply-To: <2DD9A6DE-91C8-403E-BCE6-8B959F16459D@detailedbalance.net>
References: <1235946099.3789.18.camel@localhost.localdomain.tld>
	 <2DD9A6DE-91C8-403E-BCE6-8B959F16459D@detailedbalance.net>
Content-Type: multipart/signed; micalg="pgp-sha1";
 protocol="application/pgp-signature"; boundary="=-/EK2/tkfuoiwU/cq5wNI"
Date: Mon, 02 Mar 2009 08:37:03 +0100
Message-Id: <1235979423.4079.2.camel@localhost.localdomain.tld>
Mime-Version: 1.0

--=-/EK2/tkfuoiwU/cq5wNI
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

Hi Rhett,

thanx for the feedback! I'll try this and give feedback then.

Cheers,
Martin


On Sun, 2009-03-01 at 20:18 -0600, Rhett Sutphin wrote:
> Hi Martin,
>=20
> On Mar 1, 2009, at 4:21 PM, Martin Grotzke wrote:
>=20
> > Hi,
> >
> > I want to run our wicket application with the buildr jetty plugin and
> > want to use javarebel for reloading changed classes.
> >
> > I noticed, that the buildr jetty plugin runs jetty from a tmp webapps
> > location like e.g.
> >  /tmp/Jetty_0_0_0_0_8080_mywebapp-1.0.0.war___s129z2/webapp
> >
> > For javarebel I need to know/specify the location of classes that =20
> > shall
> > be monitored for changes.
> >
> > Is it possible to modify the jetty plugin so that it uses e.g.
> > target/classes or an exploded war in the target directory?
>=20
> The jetty plugin's jetty.deploy method can directly deploy an exploded =20
> webapp from whatever directory you specify.  buildr doesn't have a =20
> built-in exploded webapp task (AFAIK).  Here's the one I use:
>=20
>      directory(_('src/main/webapp/WEB-INF/lib'))
>=20
>      task :explode =3D> [compile, _('src/main/webapp/WEB-INF/lib')] do
>        packages.detect { |pkg| pkg.to_s =3D~ /war$/ }.tap do |war_package=
|
>          war_package.classes.each do |clz_src|
>            filter.from(clz_src).into(_('src/main/webapp/WEB-INF/=20
> classes')).run
>          end
>          war_package.libs.each do |lib|
>            cp lib.to_s, _('src/main/webapp/WEB-INF/lib')
>          end
>        end
>      end
>=20
> It builds an exploded war in place over the src/main/webapp =20
> directory.  The value of this is that changes to static resources and =20
> JSPs are immediately picked up (without a build separate step).  If =20
> you prefer, you could also write something which depends on the =20
> package step and then unpacks the war somewhere under target.
>=20
> In either case, you can use the built-in jetty support to deploy like =20
> so:
>=20
>    jetty.deploy "#{jetty.url}/path", _(exploded_path).to_s
>=20
> Rhett
>=20

--=-/EK2/tkfuoiwU/cq5wNI
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEABECAAYFAkmrjJwACgkQ7FvOl7Te+pYkLACeKl0sBQvrpi9cOUIsuuoE1WPO
rGoAoKpLkFgQ9Of4UpSEf45qeoyYG3lD
=UWqO
-----END PGP SIGNATURE-----

--=-/EK2/tkfuoiwU/cq5wNI--