Have a look at the maven invoker plugin.
You may have to unbind the bundle plugin from any phases and use the invoker
plugin to run the bundle plugin and then use buildhelper to attach the
artifact... it would be a hack until bundle is releasing file handles
correctly.
I suspect it would be quicker to fork bundle yourself
On Tue, Aug 5, 2008 at 1:01 AM, Harsha Godugu <Harsha.Godugu_at_sun.com> wrote:
> Stephen Connolly wrote:
>
> afaik forkMode only applies to junit tests
>
> I see that only surefire can take forkMode under plugin / configuration
> section in the pom.
> Is there a way, I can fork VM while running into maven-bundle plugin for a
> goal say, "process-classes"
>
>
> thanks..
>
>
> On Mon, Aug 4, 2008 at 10:23 PM, Harsha Godugu <Harsha.Godugu_at_sun.com>wrote:
>
>> Harsha Godugu wrote:
>>
>>> Shing Wai Chan wrote:
>>>
>>>> Jan.Luehe_at_Sun.COM wrote:
>>>>
>>>>>
>>>>> Is anybody else getting the attached error during "mvn install"?
>>>>>
>>>> This is a known issue.
>>>> Just run mvn install "again". Then the error will be gone.
>>>>
>>> A possible workaround is, to do an incremental build. Means, goto
>>> sub-dirs and do mvn isntall at that level. Then come back to the top level
>>> and give mvn install.
>>> A bug in maven-bundle plug-in is causing this failure.
>>>
>> Just realized that maven has something called forkMode that will fork the
>> vm process. Based on the nature of the bug here, I'm pretty sure that, we
>> will get away with this bug
>> by turning on the forMode in the pom at every level or at the parent / top
>> level.
>>
>> -hg
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>
>>
>
>