On 6/4/10 10:43 AM, D. Stuart Freeman wrote: > OK, that makes sense. Great.
If it works... any chance you would want to do submit a patch for a new module illustrating this and/or write it up on the wiki? Thanks, Justin > We don't use the default bundle list, so I think > this will work. > > Thanks. > > On Fri, Jun 04, 2010 at 10:39:35AM -0400, Justin Edelson wrote: >> launchpad:start doesn't actually use *anything* in the target directory. >> >> It sounds like you want to use instrumented bundles. This should be >> possible if you install those bundles into your local maven repository >> with a classifier and then use an alternate bundle list file which >> specifies the classifier for the instrumented bundles. >> >> Due to the way that bundle list files are merged, you could only do this >> for bundles you define, not those in the default bundle list (if you use >> the default bundle list). >> >> Justin >> >> On 6/4/10 10:18 AM, D. Stuart Freeman wrote: >>> Is it possible to configure the path the the jar that gets started by the >>> maven-launchpad-plugin's start goal? I'd like it to start a jar that's >>> instrumented by emma (in target/emma/) instead of the default one in >>> target/. >>> >> >
