Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [tycho-dev] Plans for hooking into tycho lifecycle?

Maven already has an extension mechanism for adding goals to a packaging type – by adding them in the POM. However that mechanism does not allow to add goals between executions defined by the packaging type. This is a missing Maven feature, and I don’t think that it would make sense to add a second extension mechanism on top.


However, there are in fact a couple of things that Tycho could do:

·      Tycho could further spread out its activities across the lifecycle phases. There is no enhancement request for this yet. You seem to know the components.xml, so it would be good if you could open such a request. Maybe you can even come up with a proposal that fits your use case. Bear in mind that mvn <any phase> still has to work, so you can’t rely on the results of later phases  in other modules.

·      Tycho could allow users to create their own packaging types that use Tycho functionality. Right now this doesn’t work because Tycho hard-codes some of its behaviour (dependency resolution, …) on the packaging type name. The ticket for this is bug 349115






From: tycho-dev-bounces@xxxxxxxxxxx [mailto:tycho-dev-bounces@xxxxxxxxxxx] On Behalf Of Roland Oldenburg
Sent: Samstag, 9. Februar 2013 00:02
To: tycho-dev@xxxxxxxxxxx
Subject: [tycho-dev] Plans for hooking into tycho lifecycle?


Hi tycho-dev-list,


my team and me, we are currently trying to switch our “Buckminster driven RCP build” to tycho (0.16.0).

tycho seems to be the far better (more efficient) tool for RCP builds, especially when having lots of products with mostly same features/plugins.

Great work so far! Thank you very much!


The only thing currently being a hurdle for us is a missing possibility to hook into the lifecycle of a tycho build and to provide additional steps in a custom maven plugin.

In Buckminster there were some extension points to be able to provide custom types of build steps/artifacts, etc.


Are there plans for such a functionality? For example: What about an interface for plexus components that could contribute to the default lifecycle mapping (as maven does with its AbstractMavenLifecycleParticipant) ?

Maybe I am missing something, but I could not find a solution without using mavens “lib/ext”-folder or changing the components.xml of tycho-maven-plugin and then recompiling…

Both solutions are not easily maintainable/deployable. I personally don’t like such dirty hacks.


In our case it is necessary for us to do some changes on the p2 repo before it is zipped (so assumingly between “assemble-repository” and “archive-repository” goals). And there are some other steps that need to be included as well.

Any ideas/plans?


Thanks in advance,


Roland Oldenburg


Back to the top