You are on the right track. The target-platform-configuration configuration is read manually by Tycho (in DefaultTargetPlatformConfigurationReader.getTargetPlatformConfiguration)
because the configuration is needed in the afterProjectsRead Maven 3 lifecycle hook. At that point, Tycho does it’s OSGi based dependency resolution so that for example the module build order can be determined before the default lifecycle starts.
This approach works, but it has various limitations (e.g. it prevents to combine the maven-bundle-plugin and Tycho in the same build). So in the
long term, we are planning to turn target-platform-configuration into a “regular” Maven plugin (see
bug 353889).
Regards
Tobias
From: tycho-user-bounces@xxxxxxxxxxx [mailto:tycho-user-bounces@xxxxxxxxxxx]
On Behalf Of Anders Hammar
Sent: Dienstag, 4. September 2012 10:17
To: Tycho user list
Subject: Re: [tycho-user] What's org.eclipse.tycho:target-platform-configuration about?
Right, that might be it.
Thanks for the pointers!
/Anders
On Tue, Sep 4, 2012 at 10:09 AM, Jeff MAURY <jeffmaury@xxxxxxxxxxxxx> wrote:
I think the configuration is retrieved and managed by another Mojo. I think Tycho is using Maven3 lifecycle extensions, may be it is done during this processing
Jeff
On Tue, Sep 4, 2012 at 10:06 AM, Anders Hammar <anders@xxxxxxxxxx> wrote:
Hm, ok. But it's no-op mojo that does nothing. How is it storing config info? You've trigger my Maven brain here...
As Maven person I did help:describe on the mojo, but it doesn't list any params (as there aren't any declared) which makes me wonder.
/Anders
On Tue, Sep 4, 2012 at 9:52 AM, Jeff MAURY <jeffmaury@xxxxxxxxxxxxx> wrote:
No,
this MOJO is here only to store configuration information (Eclipse target platform information) that is used by other Tycho MOJOs. It is not legacy at all, I would say it's one of the central piece of Tycho !!!
Jeff
Being a Maven person I'm trying to understand the Maven configuration
of projects using Tycho. Looking at examples (inluding m2e) I see that
org.eclipse.tycho:target-platform-configuration is bound to the
lifecycle and also most often has some configuration. But when I look
at the code I only see a no-op Mojo (without configuration options of
course).
Am I missing something here, or is the usage of this plugin simply
some legacy stuff and not needed any more?
/Anders
_______________________________________________
tycho-user mailing list
tycho-user@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/tycho-user
--
Jeff MAURY
Error! Filename not specified.
"Legacy code" often differs from its suggested alternative by actually working and scaling.
- Bjarne Stroustrup
http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com
http://www.twitter.com/jeffmaury
_______________________________________________
tycho-user mailing list
tycho-user@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/tycho-user
_______________________________________________
tycho-user mailing list
tycho-user@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/tycho-user
--
Jeff MAURY
Error! Filename not specified.
"Legacy code" often differs from its suggested alternative by actually working and scaling.
- Bjarne Stroustrup
http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com
http://www.twitter.com/jeffmaury
_______________________________________________
tycho-user mailing list
tycho-user@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/tycho-user
|
