[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [tycho-dev] Build p2 update site from Maven artifacts
|
Hi Dirk,
Currently PDE requires some additional headers to really use source-jars
as source bundles. So if you bundle the sources as well appropriately
you can include them in tycho already.
Beside from that, automatically using maven-deps sources with
tycho-source-plugin is currently under development.
If you don't mind to use snapshots/latest builds or you can wait for the
next tycho + m2e release you can solve your use-case in an alternative way:
1) You can include your desired artifacts into the target file of your
project and choose "include source" and don't mind about building an
extra P2-Updatesite
2) Create a target for your updatesite build as above and wait until I
have implemented the m2e-source-feature in tycho (hopefully next week)
and proceed with deploying and all this additional stuff
That way you can even use artifacts that are not bundles at all, either
using some default mapping or create a BND mapping description from
within the target editor.
--
Mit freundlichen Grüßen
Christoph Läubrich
----------------------------------------------------
Christoph Läubrich
Freiberuflicher Diplom-Informatiker
Am 04.12.20 um 10:27 schrieb Fauth Dirk (CAP-SST/ESM1):
Hi,
I would like to create a p2 update site from Maven artifacts. I added
the OSGi metadata via bnd-maven-plugin to the Eclipse Collections
artifacts a while ago, so also in Maven Central the artifacts are
available to be used in OSGi projects.
The current approach to build the p2 repository for Eclipse collections
is to use EBR, which actually takes the build results and merge them
into a single bundle that combines API and IMPL. And that also creates a
source bundle.
To make the process more straight forward and easier to maintain, I
wanted to use the original artifacts available via Maven and drop the
EBR process. For this I configured the build with
pomDependencies=consider. But then the tycho-source-feature-plugin fails
as it can’t resolve the sources for the plugins. From the documentation
it searches for bundles with a .source suffix. But in Maven the bundles
are names with a -sources suffix.
Is it somehow possible to configure the tycho-source-feature-plugin to
consider the sources from Maven?
Mit freundlichen Grüßen / Best regards
*Dirk Fauth*
Cross Automotive Platforms - System, Software and Tools Engineering
Engineering Software Methods and Tools1 (CAP-SST/ESM1)
Robert Bosch GmbH | Postfach 10 60 50 | 70049 Stuttgart | GERMANY |
www.bosch.com <www.bosch.com>
Tel. +49 711 811-57819 | Telefax +49 711 811 | Dirk.Fauth@xxxxxxxxxxxx
<mailto:Dirk.Fauth@xxxxxxxxxxxx>
Sitz: Stuttgart, Registergericht: Amtsgericht Stuttgart, HRB 14000;
Aufsichtsratsvorsitzender: Franz Fehrenbach; Geschäftsführung: Dr.
Volkmar Denner,
Prof. Dr. Stefan Asenkerschbaumer, Dr. Michael Bolle, Dr. Christian
Fischer, Dr. Stefan Hartung,
Dr. Markus Heyn, Harald Kröger, Christoph Kübel, Rolf Najork, Uwe
Raschke, Peter Tyroller
_______________________________________________
tycho-dev mailing list
tycho-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/tycho-dev
