Re: [tycho-user] Newbie question for Tycho/building eclipse plugins

[Igor Fedorenko <igor@xxxxxxxxxxxxxx>]

You can mix maven-bundle-plugin and tycho projects. This is how we build
m2e, for example. Embedded maven runtime and similar "wrapper" bundles
are setup as maven-bundle-plugin projects, while the rest of m2e is
built with Tycho [1].

The only real limitation, is that on command line maven-bundle-plugin
projects must be built separately before building tycho projects. This
is because Tycho needs bundle manifests of all dependencies before the
build.

[1] 
http://git.eclipse.org/c/m2e/m2e-core.git/tree/?id=milestones/1.1/1.1.0.20111210-1509

--
Regards,
Igor

On 12-01-04 2:41 PM, Roger Studner wrote:
> Well, that is partially the problem.
>
> For an eclipse RCP app or plugin.. there are always going to be some dependencies out on the eclipse repo/p2 (eclipse.ui lah lah).
>
> But then if I want to say, use a jar from a module in house that is in maven.. or want to use Spring 3.x's bean container..
>
> that is when it gets tricky.. there will always(?) be a mix of maven repo vs eclipse osgi bundle in every project I would think
>
> (again, i'm new to this, so not speaking with authority hah)
>
> Roger
>
> On Jan 4, 2012, at 2:01 PM, Igor Fedorenko wrote:
>
> > If all your dependencies are coming from Maven repositories,
> > maven-bundle-plugin [1] may be a better tool to develop OSGi bundles
> > with Maven.<Embed-Dependency>, in particular, is quite powerful when
> > you need to "wrap" existing jars in bundles.
> >
> > [1] http://felix.apache.org/site/apache-felix-maven-bundle-plugin-bnd.html
> >
> > --
> > Regards,
> > Igor
> >
> > On 12-01-04 9:11 AM, Roger Studner wrote:
> > > A canonical question that I can't find a solid answer too.
> > >
> > > I'm moving from ant/ivy over to maven/tycho.. so, how this worked, is
> > > i'd have ivy download a pile of jars into a lib folder, and have the
> > > MANIFEST just point at them.  Simple stuff.
> > >
> > > Is there a way, in tycho, to specify a dependency that would be in my
> > > maven repo (like say, Apache commons) and download it to "lib"
> > > *prior* to then having the rest of everything run/get built.
> > >
> > > I get a bit confused on that whole "everything must be an osgi
> > > bundle" versus the fact that I Just want my plugin to have a
> > > dependency on some maven repo jar's etc.
> > >
> > > Just can't seem to sort out the right path to resolution for these
> > > types of things
> > >
> > > Best, Roger
> > >
> > > _______________________________________________ tycho-user mailing
> > > list 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
>
> _______________________________________________
> tycho-user mailing list
> tycho-user@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/tycho-user