Michael Mühlebach wrote:
One of the biggest problems ist, that the pde-maven-plugin supports
building of a product ok,
But there is no easy way to build several plugins which depend on each
other. I have to manage the dependencies twice and even then the build
is quite erratic.
I would really like to use the tycho plugin build process which
utilized the manifest to validate my plugins even thought I do not
need the build results (jar etc) but the successful/failed state for
each plugin project would be quite useful in a larger project setup!
I do not know much/anything about pde-maven-plugin, so I would need more
information here. Ideally, I would like to see a small sample project
and description of desired behaviour. Or at least point me to relevant
documentation/wiki pages.
The thing with the newer versions: Do you mean with 2.1 3.0 or the
next release on the 2.0.9 line?
Ok it does not really matter any way: I will be able to force both
into our build process but only if they are official releases and
after they have proven their maturity.
This means for the moment 2.0.9 at most!
There was massive maven version rename recently.
There are talks about 2.0.10 release, which is strictly bug fixing
release with emphasis on backward compatibility with 2.0.9. Then, there
is 2.1-M1 (or something like that) that is a mostly bug fix release too,
but as far as I understood developers had to change maven internals too
much so it was not considered "bug fixing" any more. And, finally, there
is 3.0, which was called 2.1 until recently. This is what we use in
tycho and it is heading towards 3.0-alpha-1 release. Even though I can't
call it "rock-solid", it already works reasonably well for tycho itself,
m2e and couple of other projects.
P.S: The helping thing :-) Well if I could use tycho in my current
project setup I would certainly help ;-) Otherwise I have to follow
the dev env how-to an look how easy it is to contribute to your
project. But I can imagine to help because for the first time it looks
like a real solution. (And because I can not always complain about the
immaturity of maven and the eclipse integration of it an doing nothing
about it :-))
[1] provides instructions how to setup tycho dev env, if you are
interested. It also explains how to run tycho build directly from m2e
workspace (i.e. without installing/deploying tycho plugins first). And
do not hesitate to ask questions.
[1] http://docs.codehaus.org/display/M2ECLIPSE/Tycho+development+environment
On Mon, Oct 6, 2008 at 4:16 PM, Igor Fedorenko <[EMAIL PROTECTED]> wrote:
Michael,
Tycho depends on some new functionality that was added (and is being added)
to maven 3.0 specifically to support alternative project model formats and
repository layouts. It will not be possible to "mechanically" backport tycho
to work with earlier maven versions, and some features may not be possible
to backport at all.
At the same time, if you can explain what specific tycho features you want
to use, we might be able to suggest something. Especially if you're willing
to help ;-).
Also, do you know if you will be able to use newer maven 2.x versions (i.e.
the new 2.1, 2.2, etc)?
Michael Mühlebach wrote:
Hi,
I use maven together with eclipse RCP.
I tried to build the plugins, features and products with the
combination of the maven-eclipse-plugin and the pde-maven-plugin. Ok I
did not just try: I have a build for all but it is so terrible
inconvenient that I really would like to use tycho.
Unfortunately there is no way to use maven 2.1 (3.0) because of
company constraints.
So is there a way to use some features of tycho with maven 2.0.9?
Best wishes
Mike
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
