Re: [tycho-dev] Plans for hooking into tycho lifecycle?

["Roland Oldenburg" <roland.oldenburg@xxxxxx>]

Hi,

thank you for this info. Concerning that "missing Maven feature": It is a
bit disillusioning when you take a look at that jira-entry: Since 2008
nothing happened any more on it...
I am quite astonished that this issue has not come up yet within the
eclipse-projects. As I read they are all switching to tycho because of that
CBI-initiative.

However.

> ... Maybe you can even come up with a proposal...
I would love to but I am a tycho newbie so far. Maybe when I gathered some
more experiences on all that.

> Tycho could allow users to create their own...
I will vote for the bug.

Thanks again.

Regards,
Roland


Date: Tue, 12 Feb 2013 08:07:34 +0000
From: "Oberlies, Tobias" <tobias.oberlies@xxxxxxx>
To: Tycho developers list <tycho-dev@xxxxxxxxxxx>
Subject: Re: [tycho-dev] Plans for hooking into tycho lifecycle?
Message-ID:
	
<D9B0E18147535141AFBBA24DCD46D8F5070C7DBC@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
Content-Type: text/plain; charset="us-ascii"

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<http://jira.codehaus.org/browse/MNG-2804>, 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<https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Tycho>. 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<https://bugs.eclipse.org/bugs/show_bug.cgi?id=349115>

Regards
Tobias


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