Yes I did see that, but I didn't find it a satisfactory answer because the settings.xml is a per-user artifact outside of the project. Anyway I see that this has stimulated further discussion on the ticket, so let's try to resolve it there.
Thanks for your work on this, it's certainly a step in the right direction!
As mentioned in the ticket you need to configure these in the
settings.xml (!) rather than in in the pom.xml than it works without a
problem. That is because there is no pom-context available at the point
of resolution.
Am 22.02.21 um 13:26 schrieb Neil Bartlett:
> I did try using the new Tycho feature for importing OSGi bundles from a
> plain Maven repository. Unfortunately it is not practically usable for a
> lot of use-cases at the moment because the Maven repository location
> cannot be configured in the POM:
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=570611
> <https://bugs.eclipse.org/bugs/show_bug.cgi?id=570611>
>
> This means you cannot consume artifacts from a hosted corporate
> repository such as Nexus or Artifactory, but only from Maven's
> "built-in" repositories such as Maven Central. Open source projects may
> be able to publish all their artifacts to Maven Central but this will
> not be the case for most commercial projects.
>
> Neil
>
> On Mon, 22 Feb 2021 at 10:11, Ahmet Bilgin <a.bilgin@xxxxxxxxxxxx
> <mailto:a.bilgin@xxxxxxxxxxxx>> wrote:
>
> Hi Michael,
>
> __ __
>
> Thank you for the advice. We are using the p2-maven-plugin for some
> of our dependencies.
>
> __ __
>
> I have been trying out the features of Tycho 2.2 and the new m2e PDE
> plugin. Under the hood they do what the p2-maven-plugin does, but
> integrate better between the maven and eclipse (build-)tooling as
> far as I can tell so far.
>
> __ __
>
> Best regards,
>
> Ahmet
>
> __ __
>
>
>
> Ahmet Bilgin, M.Sc.
> Software Development
>
> *MAGMA Gießereitechnologie GmbH*
>
> P: +49 241 88901 203
> Kackertstrasse 16-18, 52072 Aachen, Germany
> www.magmasoft.de <http://www.magmasoft.de>
> a.bilgin@xxxxxxxxxxxx <mailto:a.bilgin@xxxxxxxxxxxx>
>
> ------------------------------------------------------------------------
> *GERMANY ● USA ● BRAZIL ● SINGAPORE ● SOUTH KOREA ● CHINA ● INDIA ●
> TURKEY ● CZECH REPUBLIC*
>
> *<https://www.magmasoft.de/de/event/Die-virtuelle-Giesserei-Virtuelle-internationale-Konferenz-46.-Aachener-Giesserei-Kolloquium/?pk_campaign=Aachener-Giesserei-Kolloquium&pk_keyword=Aachener-Giesserei-Kolloquium&pk_source=Mailfooter&pk_medium=Email&pk_content=Link%20more%20Information>*
>
> SAVE THE DATE! 17 - 19 March 2021 - 46th Aachen Foundry Colloquium |
> The virtual foundry - status and future developments | Digital
> Conference - Aachen, Germany
>
> MAGMA Gießereitechnologie GmbH | Kackertstraße 16-18, 52072 Aachen,
> Germany | Legal form: GmbH, Register court: Aachen HRB 3912, Value
> added tax identification number: DE121745780 | Management: Dr. Marc
> C. Schneider (CEO and President), Dr.-Ing. Jörg C. Sturm (Managing
> Director)
>
> *From:*tycho-user [mailto:tycho-user-bounces@xxxxxxxxxxx
> <mailto:tycho-user-bounces@xxxxxxxxxxx>] *On Behalf Of *Keppler
> Michael (ETAS/ESW-CI)
> *Sent:* Wednesday, February 17, 2021 1:17 PM
> *To:* Tycho user list
> *Subject:* Re: [tycho-user] Produce artifacts consumable by Maven
> and Tycho
>
> __ __
>
> If you can’t or don’t want to use the new m2e and Tycho tooling,
> then https://github.com/reficio/p2-maven-plugin
> <https://github.com/reficio/p2-maven-plugin> might be an
> alternative. I use that to consume a 3 digit number of maven
> libraries in Eclipse. And this integrates completely with TPD files
> or Oomph targlets, where the new m2e tooling doesn’t fit, as far as
> I can tell.
>
> __ __
>
> Mit freundlichen Grüßen / Best regards
>
> *Michael Keppler
> *
> LTO Release Engineering (ETAS/ESW-CI)
> Tel. +49 711 3423-2429 | Fax +49 711 89661-0 |
> Michael.Keppler@xxxxxxxx <mailto:Michael.Keppler@xxxxxxxx>
>
> *Von:*tycho-user <tycho-user-bounces@xxxxxxxxxxx
> <mailto:tycho-user-bounces@xxxxxxxxxxx>> *Im Auftrag von *Ahmet Bilgin
> *Gesendet:* Montag, 15. Februar 2021 18:36
> *An:* tycho-user@xxxxxxxxxxx <mailto:tycho-user@xxxxxxxxxxx>
> *Betreff:* [tycho-user] Produce artifacts consumable by Maven and Tycho
>
> __ __
>
> Hi,
>
> __ __
>
> what is the current best practice to build common artifacts that are
> used in both Maven and Tycho builds?
>
> __ __
>
> Scenario:
>
> Here is a scenario (all listed modules are build inhouse, except the
> one called 3^rd -Party):
>
> __ __
>
> Let’s call the following modules our “core-utils”:
>
> - Module1 (depends on)
>
> -- Module2
>
> -- Module3 (depends on)
>
> --- 3^rd -Party
>
> -- Module4
>
> __ __
>
> Module1 – Module4 (“core-utils”) are all required in our Tycho RCP
> Build and in our Maven Builds (non-eclipse):
>
> - tycho-rcp-build (depends on)
>
> -- Module1
>
> -- Module2
>
> -- Module3
>
> -- Module4
>
> - maven-builds (depend on)
>
> -- Module1
>
> -- Module2
>
> -- Module3
>
> -- Module4
>
> __ __
>
> __ __
>
> And now the big price question:
>
> Which should be the leading build-system for these “core-utils” –
> Tycho or Maven?
>
> Additional info: we have way more tycho rcp bundles than plain maven
> artifacts.
>
> __ __
>
> __ __
>
> There are two options:
>
> __ __
>
> Option-1: Build maven-artifacts with maven
>
> - build and install to maven repo
>
> - Maven builds: can consume the artifacts without additional effort
>
> - Tycho builds: use on-the-fly conversion to Tycho/osgi artifact
>
> -- Tycho tooling for this is implemented in tycho v.2.2
>
> -- Alternative: something like maven-bnd-plugin
>
> -- Consume converted artifacts in tycho build
>
> __ __
>
> Option-2: Build tycho artifacts
>
> - build tycho artifacts but store artifacts in Maven style repo or
> use some other mechanisms to make the artifacts consumable from
> maven builds
>
> -- I know that the b3aggretor has this capability when
> mirroring P2-Repos. See
> https://wiki.eclipse.org/index.php?title=CBI/aggregator&redirect=no#Creating_a_Maven-conformant_p2_repo
> <https://eur03.safelinks.protection.outlook.com/?url="">>
>
> -- Has Tycho this feature too?
>
> -- Alternative: for example something like this:
> https://github.com/lhein/EclipseToMavenTooling
> <https://eur03.safelinks.protection.outlook.com/?url="">>
>
> - Tycho Builds: can consume the artifacts without additional effort
>
> - Maven-Builds: can consume the artifacts without additional effort
> (because the repo is structured like a maven repo, but also has p2
> metainformation)
>
> __ __
>
> Questions:
>
> 1. Which way is preferable / which should be the leading build
> system for these “core-utils”?
>
> 2. Is there any downside to one of the approaches, I’m maybe missing?
>
> __ __
>
> __ __
>
> Best regards,
>
> Ahmet
>
> __ __
>
> __ __
>
> __ __
>
> __ __
>
> _______________________________________________
> tycho-user mailing list
> tycho-user@xxxxxxxxxxx <mailto:tycho-user@xxxxxxxxxxx>
> To unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/tycho-user
> <https://www.eclipse.org/mailman/listinfo/tycho-user>
>
>
> _______________________________________________
> tycho-user mailing list
> tycho-user@xxxxxxxxxxx
> To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/tycho-user
>
_______________________________________________
tycho-user mailing list
tycho-user@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/tycho-user
