longer need to use <dependency> sections to declare your dependencies—Tycho
ignores them. Although Maven repositories still have their place, how they're used
and what gets put into them are different. If you're a long-time Maven user, you may
find the Tycho experience unsettling; but if your heart lies with Eclipse, Tycho will feel
warm and comforting, like an old pair of slippers.
Because it's so different from conventional Maven, Tycho works best if you've already
got your projects set up in Eclipse, but haven't yet written an automated build for them.
If you already have everything laid out on disk in the standard Maven way, you can make
Tycho work with Maven's build layouts, but it will require extra plug-in configuration.
Tycho is a Maven plug-in, so getting started with Tycho is easy. All you'll need is
Maven 3 and a pom file. One of the nice things about Tycho is that Tycho poms are
small, especially if you put the plug-in configuration in a parent pom (which we
haven't done here!). Almost all of the information needed to build the plug-in is
shared between the IDE and the build tooling.
The pom.xml file for a Tycho build of the fancyfoods.business bundle
<name>Fancy Foods Cheese Department Bundle</name>
To generate bundle,
must be explicitly
Like Eclipse PDE , Tycho uses the terms plug-in and bundle somewhat interchangeably,
so to build a normal bundle, you'll have to use Tycho's eclipse-plugin packaging
type. Don't worry, Tycho will build you a standard OSG i bundle, despite the name!
Almost all of the information about how your bundle should be built is drawn
from the bundle manifest and the eclipse metadata, rather than the pom. This avoids
duplication, and it has the added bonus that you can use Eclipse's nice tools (which
we'll come to in section 9.1.1) to control things. The symbolic name and version
strings should exactly match the ones in your manifest, but that's the only information
you'll need to duplicate.
Search WWH ::