Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [tycho-user] Sharing code with Tycho eclipse-plugin and normal Maven project using Eclipse

Use maven project as explained in maven-bundle-plugin wiki (see [1] in
my previous reply).

m2e/tycho provides integration between m2e, pde and maven-bundle-plugin.

Forgot to mention, this integration is fairly recent addition to all
tools involved, so make sure to use the following versions

maven-bundle-plugin 2.3.6
PDE 3.8M3 (comes with eclipse sdk 3.8M3)
m2e 1.1M3 (can be installed from juno release repository)
m2e/tycho 0.6.0.201112050222 (can be installed from Preferences->Maven->Discovery)

--
Regards,
Igor

On 11-12-08 5:01 PM, David Erickson wrote:
Hi Igor,
Thanks for the reply. What type of project would I create in Eclipse for
the common code? Would it be a Maven Project or a Plug-in Project? And
if BND is creating the MANIFEST after the fact how would Eclipse pick up
the project for inclusion into OSGi launches?

Thanks,
D

On 12/08/2011 01:16 PM, Igor Fedorenko wrote:
I am not sure about product export from eclipse, it never worked for me
reliably, so I gave up long time ago. Everything else is supposed to
"just work" with Eclipse PDE 3.8M3 and m2e 1.1M3 -- just move the common
code to a separate project and use maven-bundle-plugin [1] to generate
bundle manifest.

For command line build see [2]

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

--
Regards,
Igor

On 11-12-08 4:00 PM, David Erickson wrote:
Hi all-
I've got a project using Tycho that has multiple eclipse OSGi plugins
that are assembled into a stand alone product but I don't believe is
using any special Tycho building in Eclipse (call it project A), I also
have a regular Java Maven project that builds a standalone executable
jar file for execution (call it project B). What I'd like to do is share
some common code between the two projects and enable the following:

-Eclipse auto-builds both project A and B
-Able to run project A and B within Eclipse
-Able to export the project A using Eclipse product export including the
common code without any intermediate build steps
-Able to build project A/B using Maven on the command line, ideally it
auto builds and includes common code, but I am willing to run another
build step if needed

What I really want to avoid is having to build common code into a jar,
regenerate the target, and re-import it into Eclipse.. too much work.

Help is greatly appreciated.

Thanks,
David
_______________________________________________
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


Back to the top