Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [tycho-dev] Invoke maven project extension before TychoMavenLifecycleParticipant - patch question

I agree with you to some extent. But the problem is that I still need such an extension.
What would you recommend in that case?
Is it possible to dispose the TychoParticipant in the plexus container and register an object with the same hint that would wrap it around? Or to use some kind of a proxy so that I can instrument the afterProjectsRead invocation.
I was thinking of javaagents but the invocation of maven is cumbersome then...
I don't want to modify tycho's source code locally and create my own local version. The plugin that I write my be really useful for other people as well...
Do you have any hints?


On Mar 11, 2012, at 1:14 PM, Igor Fedorenko wrote:

> It is not possible to share classes among extensions plugin. It maybe
> possible to use o.a.maven.classrealm.ClassRealmManagerDelegate to
> approximate this programmatically, but I vaguely remember something was
> missing from maven core to allow this in practice.
> This maven core limitation make your proposed Tycho extension mechanism
> much less generally useful, I think.
> --
> Regards,
> Igor
> On 12-03-11 7:55 AM, Tom Bujok wrote:
>> For my use case it's fine - I don't need mojos. In my case, the only
>> advantage of a mojo would be the parameters unmarshalling provided by
>> Maven, but I can live with parameters defined in a separate file that
>> I read when the participant is invoked.
>> BTW, speaking theoretically, do you know a way in which you could
>> share classes  among different extensions plugins? I was thinking
>> that  maybe it is possible by tweaking the context class loader in
>> the participant which has to reuse classes from a different extension
>> plugin?
>> Tom
>> On Mar 9, 2012, at 12:50 AM, Igor Fedorenko wrote:
>>> How do you plan to contribute your conponents to Tycho core class
>>> realm? Maven does not allow sharing of classes among different
>>> extensions plugins, which means you'd need to include your
>>> cimponents via<dependency>  element, which in turn means you won't
>>> be able to define additional mojos. Is this limitation 'okay' for
>>> your usecase? -- Sent from my SGS
> _______________________________________________
> tycho-dev mailing list
> tycho-dev@xxxxxxxxxxx

Back to the top