Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [tycho-user] (no subject)

There are two distinct cases.

If dependencies available from Maven repositories are OSGi bundles, then
it is possible to consume such dependencies directly from Tycho build.
See [1] for more information how to set this up.

If dependencies available from Maven repositories are not OSGi bundles,
they need made OSGi bundles first. There is probably more than one way
to do this, but I had good experience with maven-bundle-plugin
<Embed-Dependency> feature to "wrap" maven artifacts in OSGi bundles.
See [2] for more information. Such wrapper bundles can then be consumed
from Tycho build as explained in [1].


[1] https://docs.sonatype.org/display/TYCHO/Dependency+on+pom-first+artifacts
[2] http://felix.apache.org/site/apache-felix-maven-bundle-plugin-bnd.html

--
Regards,
Igor


On 11-11-18 6:39 PM, Matthew O'Connor wrote:
Maybe this is the wrong question as I still want to be able to build the
project in Eclipse & thus it needs access to those jars.

Could I instead use Maven with Tycho to generate an extension to the
Eclipse target platform that could be used by Eclipse for its builds &
by Tycho for its? It would be nice if this could pull jars from Maven
repos, local supplied ones, etc.

On Fri, Nov 18, 2011 at 2:00 PM, Matthew O'Connor
<thegreendragon@xxxxxxxxx <mailto:thegreendragon@xxxxxxxxx>> wrote:

    Hi all,

    I'm in the process of converting an existing Equinox project from a
    PDE build to a Maven/Tycho build, given its size I've started a
    sample workspace with projects to test out what I'm trying to do.

    I used `mvn -e
    org.eclipse.tycho:tycho-pomgenerator-plugin:generate-poms
    -DgroupId=com.example` to build initial poms.

    I modified my root pom to reflect the "Exemplary parent POM" at
    http://wiki.eclipse.org/Tycho/Reference_Card.

    I want to enable Tycho to resolve artifacts/plugins from a Maven
    repository since we have dependencies that will exist in a Maven
    repo that won't be and aren't in a standard Eclipse p2 site. I'd
    like to keep our plugin dependencies specified in the manifests via
    "Import-Package". I've tried different permutations of this
    (removing the Eclipse Indigo p2 site from the pom repositories,
    adding explicit pom dependencies - like log4j:log4j, etc.), but have
    been unable to figure anything out.

    Is there a way to do this?

    Thanks,
    Matthew

    _______________________________________________
    tycho-user mailing list
    tycho-user@xxxxxxxxxxx <mailto:tycho-user@xxxxxxxxxxx>
    https://dev.eclipse.org/mailman/listinfo/tycho-user




_______________________________________________
tycho-user mailing list
tycho-user@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/tycho-user


Back to the top