abovesun wrote:
But there is several question about Tycho:
1. why it uses maven 3?
Tycho extends maven core functionality (as apposed to just providing new
plugins) and maven 3 introduces several new and/or revised APIs that
either make tycho implementation easier or possible at all. I can
provide more details, if you are interested.
2. why tycho build is actually extended maven pack? Are you using aspects or
byte code changing to inject Tycho behavior in maven stages?
no aspcts or byte-code manipulation, just regular subclassing. tycho
extends couple of core maven components and tycho-distribution uses
classpath order to inject these custom components into maven runtime
(see bin/m2.conf). there are plans to introduce support for this kind of
extensions into maven 3.0, so custom maven distribution will not be
necessary.
3. is there are any predefined goals to deploy compiled and packed bundle to
target platform?
Target platform management is the next big feature we are going to
introduce into tycho. I expect first implementation to be available next
few weeks, so stay tuned.
--
Regards,
Igor
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
