I started using Maven because we wanted to adopt Tycho to ditch PDEbuild. As I’ve grown more comfortable and familiar with Maven I see where Charlie is coming
from. The problem other Maven solutions have is they generally lack P2 dependency resolution and Eclipse doesn’t publish their platform to the public eclipse.org Maven repository (or Central). So people developing Equinox and wanting to use traditional Maven
process are kind of stuck in the middle. Over time I’ve come to think that maybe Tycho would have benefitted from using Gradle instead of Maven as it foundation.
From: tycho-user-bounces@xxxxxxxxxxx [mailto:tycho-user-bounces@xxxxxxxxxxx]
On Behalf Of Matthew Piggott
Sent: Thursday, November 10, 2016 8:54 AM
To: Tycho user list
Subject: [EXTERNAL] Re: [tycho-user] Please, make Tycho 1 more Maven friendly
External Sender: Use caution with links/attachments.
Did you try the consider pom dependencies option? We have a project that builds a few plugins with bnd which are consumed by a tycho project.
On 10 November 2016 at 09:48, Charlie Mordant <cmordant1@xxxxxxxxx> wrote:
Thank you for your (longer) answer. And you're right on the entire line, I'm totally following your POV.
In fact, I already tried to mix both world (bnd&Mvn + Tycho) without success.
The issues was that the update-site generation, tp one (and eclipse tp configuration), feature and product one ware requiring dependent plugins to have the 'eclipse-plugin' packaging.
I think that without this constraint, everything could be nice.
Would you be ok to try to make a MVN/Tycho POC and adapting (a tiny amount amount of) Tycho source code to additionally handle that use-case?
I can setup the repo, and try to go as far as I can, then tell you where I'm stuck... I don't think that this would be a high amount of work, but I don't want to
start useless tasks.
Hi Charlie,
Actually, as a Tycho user, I really like the Eclipse-centric approach and I think Tycho correctly maps the needs of Eclipse developers.
For these use-cases, most of your proposals actually sound like addition of a lot of complexity: generating MANIFEST, resolving against some other kinds of repositories, changing some versioning habits... All that is IMHO far from what most current Tycho users
are wanting.
What you suggest would probably be better as an alternative project than an improvement to Tycho. And it seems to me that your ideas are already mostly covered by bnd maven plugins and others.
Cheers,
_______________________________________________
tycho-user mailing list
tycho-user@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/tycho-user
--
_______________________________________________
tycho-user mailing list
tycho-user@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/tycho-user
This e-mail, including any attached files, may contain confidential and privileged information for the sole use of the intended recipient. Any review, use, distribution, or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive information for the intended recipient), please contact the sender by reply e-mail and delete all copies of this message.
|
