You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "D. Stuart Freeman" <st...@et.gatech.edu> on 2010/07/06 20:44:10 UTC

Re: maven-launchpad-plugin jar path

So, is it possible to tell the launchpad start to use an alternative
list.xml?  I'd like to have the integration tests run against an xslt
transformed version of the "real" list.xml that we use.

On Fri, Jun 04, 2010 at 10:43:16AM -0400, D. Stuart Freeman wrote:
> OK, that makes sense.  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/.
> > > 
> > 
> 
> -- 
> D. Stuart Freeman
> Georgia Institute of Technology



-- 
D. Stuart Freeman
Georgia Institute of Technology

Re: maven-launchpad-plugin jar path

Posted by "D. Stuart Freeman" <st...@et.gatech.edu>.
Thanks, that does indeed work.

On Tue, Jul 06, 2010 at 02:46:27PM -0400, Justin Edelson wrote:
> This should work:
> <configuration>
>   <bundleListFile>${basedir}/src/test/bundles/it-list.xml</bundleListFile>
> </configuration>
> 
> Justin
> 
> On 7/6/10 2:44 PM, D. Stuart Freeman wrote:
> > So, is it possible to tell the launchpad start to use an alternative
> > list.xml?  I'd like to have the integration tests run against an xslt
> > transformed version of the "real" list.xml that we use.
> > 
> > On Fri, Jun 04, 2010 at 10:43:16AM -0400, D. Stuart Freeman wrote:
> >> OK, that makes sense.  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/.
> >>>>
> >>>
> >>
> >> -- 
> >> D. Stuart Freeman
> >> Georgia Institute of Technology
> > 
> > 
> > 
> 

-- 
D. Stuart Freeman
Georgia Institute of Technology

Re: maven-launchpad-plugin jar path

Posted by Justin Edelson <ju...@gmail.com>.
This should work:
<configuration>
  <bundleListFile>${basedir}/src/test/bundles/it-list.xml</bundleListFile>
</configuration>

Justin

On 7/6/10 2:44 PM, D. Stuart Freeman wrote:
> So, is it possible to tell the launchpad start to use an alternative
> list.xml?  I'd like to have the integration tests run against an xslt
> transformed version of the "real" list.xml that we use.
> 
> On Fri, Jun 04, 2010 at 10:43:16AM -0400, D. Stuart Freeman wrote:
>> OK, that makes sense.  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/.
>>>>
>>>
>>
>> -- 
>> D. Stuart Freeman
>> Georgia Institute of Technology
> 
> 
>