On 03/08/2016 11:09 AM, Dirk Fauth wrote:
A target platform only works with p2 repositories in
conjunction with Tycho.
Yes, I figured that. My build uses Tycho. Are you trying to make
some other point that is not obvious to me?
Am 08.03.2016 19:49 schrieb "David M.
Karr" < davidmichaelkarr@xxxxxxxxx>:
On
03/08/2016 10:28 AM, Tom Bryan (tombry) wrote:
I don't remember your original use case, but is the problem
you're hitting
similar to this user's situation?
http://stackoverflow.com/questions/35346113/using-third-party-libraries-in-
eclipse-rcp-tycho-app/
I think that my reply on that thread explains the current
state of affairs
and the problem bridging between Eclipse and Tycho on one
hand and normal
Maven artifacts and dependencies on the other.
I guess my situation is similar to that, yes.
The present build just "hard-stores" the jars in the project
and references them in the classpath in the manifest. I need
to remove them from the project itself and replace them with
some sort of declarative dependencies, as I can't store jars
in our git repo (it's a project policy, but I agree with it).
The problem is that even if you could automatically convert
a JAR to an
Eclipse plug-in and add it to the Maven repository, you're
still going to
have to reference that specific plug-in in your Eclipse
plug-in that uses
that library, right? Are you just hoping to create some
automation that
follows the Maven dependency tree for some specific artifact
and then
creates an equivalent set of Eclipse "library plug-ins" with
the correct
transitive references? Once you do that, your developers
will still need
all of those plug-ins in their local development
environments, right?
I had assumed that once the jars I need are properly
OSGi-configured into the Nexus p2 repo, I can specify that
repo in my target platform, along with the dependencies I
need, and then my code will be able to use those classes.
Is there anything else I need?
Tycho is great for handling Eclipse bundles, but as soon as
you try to
include a complex third party (JAR) library into your RCP
application,
you hit this problem. It would be great if Tycho users
could help
articulate what a workable solution would look like. That
way, maybe
someone can solve that problem so that we don't have a bunch
of different
software teams having to work around this disconnect between
the Maven
world and the Eclipse-tycho world.
---Tom
On 3/8/16, 12:53 PM, "tycho-user-bounces@xxxxxxxxxxx on
behalf of David M.
Karr" <tycho-user-bounces@xxxxxxxxxxx on
behalf of
davidmichaelkarr@xxxxxxxxx>
wrote:
A while ago, I asked questions in here (and other
channels) about my
Eclipse plugin build, using Tycho, which was
"hard-storing" some maven
artifacts in the project instead of specifying them
"declaratively". I
tried for quite a while to figure out how to specify them
as Maven
dependencies, but I never got it to work.
I started to understand that the only way to get this to
work was to be
able to access those artifacts in a p2 repository, so I
can specify
those dependencies in my target platform. The
administrator of the
Nexus server that I use has been working on this, but he's
telling me
that the artifacts mirrored in this repository have to be
OSGi bundles.
A "plain" Maven artifact jar won't work.
I'm now understanding that it's straightforward to
"augment" an existing
Maven artifact with the appropriate META-INF/MANIFEST.MF
file to have it
be recognized and properly used as an OSGi bundle. This
can be done at
build time with the "maven-bundle-plugin", but Nexus also
has the
ability (I don't know the details yet) to
semi-automatically add
manifest info to artifacts so they can be used in a p2
repo.
However, I'm also hearing that even if the artifact is a
valid OSGi
bundle, it won't properly work in a p2 repo unless it can
somehow see
"features". What do I have to do to plain Maven artifact
jars to make
them usable in an Eclipse plugin build as repository
targets in a target
platform specification?
_______________________________________________
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
_______________________________________________
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
|
