Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipse-dev] Confirm that Tycho can't manage BOTH p2 and Maven artifacts?

The answer is that it depends. 

Tycho either can be driven by a plugin manifest or Pom.xml to resolve its p2 dependencies and here I believe it is true - it has to be either/or. 

but what you can do in your specific case of having nested jars inside your plugin is to use mvn copy-dependencies which allow you to remove lib content from your source Repo and have it dynamically downloaded and put into the lib folder during build. has more
on it. 

Jbosstools projects uses this for a few things where creating a full set of Osgi dependencies was not feasible.

Hope that helps.  


> On 18 Jan 2016, at 14:27, David M. Karr <davidmichaelkarr@xxxxxxxxx> wrote:
> I inherited a large Eclipse plugin codebase, but I'm pretty new to Eclipse plugin development.
> I happened to notice that one of the subprojects had a few jars just dumped into a "lib" folder, and those jars are referenced from the .classpath,, and META-INF/MANIFEST.MF file.  This subproject also has several bundles that it depends on.
> I wondered why these artifacts weren't just specified as Maven artifacts.  I asked about this odd convention on the IRC #eclipse channel, and someone said that Tycho can't handle BOTH p2 and Maven artifacts.  I took him at his word, but I need to get more information about this.  I'm working with someone else who believes this shouldn't be a problem, so I need to find some proof for this statement.
> _______________________________________________
> eclipse-dev mailing list
> eclipse-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit

Back to the top