It would be nice to be able to build/run things like the examples without
having the whole honkin' tree checked out.

Maybe we can just modify the default developer config to point to the
various jar files in the target directories, that way we don't even look in
the common lib directory except on machines where the assembly tarball has
been unpacked.

-Eric

On Thu, Mar 15, 2012 at 8:59 AM, Keith Turner <[email protected]> wrote:

> On Wed, Mar 14, 2012 at 1:48 PM, Benson Margulies <[email protected]>
> wrote:
> > On Wed, Mar 14, 2012 at 11:02 AM, John Vines <[email protected]>
> wrote:
> >> We run it in the svn structure, which makes testing easy. I would like
> to
> >> be able to avoid building and packaging it just to run it.
> >
> >
> > How about if we just take the config out of the top-level pom, and put
> > it into the specific poms that actually build the jars that belong in
> > lib? That way the examples won't go dropping jars in surprising
> > places.
> >
>
> I like that.
>

Reply via email to