One plugin provides general JRebel/Eclipse integration, another embeds JRebel itself, and others provide debugger, WTP and RAD integration. JRebel for Eclipse consists of 6 Eclipse plugins, some of which depend on each other. I figured that since others may have similar needs to ours at ZeroTurnaround, it would be cool to share this experience with everyone (*note: this post assumes some experience with Maven and PDE).įirst, I'll describe what we needed from Tycho. The information I found was sometimes outdated, though, or didn't go into the things that we needed to make a headless build for JRebel for Eclipse, which has had over 800 downloads in February alone and continues to climb the charts on the Eclipse Marketplace. It doesn't yet have a lot of updated or detailed documentation, but I found help in blog posts about building with Tycho. Tycho still doesn't have an 1.0 release, but seems pretty stable, if lacking a few features. Tycho for Maven 3 aims to change that, making it possible to build OSGi bundles / Eclipse plugins in an environment familiar to most developers and with minimal additional configuration. There are, of course, some tools provided by the Eclipse Foundation for headless building of plugins, but they don't seem easy to set up or convenient to use. > Deployable plugins., but it can't do this when building a whole update site. If you are used to Maven, Ant or another command line build tool, then things like this are truly annoying. Running the build manually from PDE works, but it's pretty much a black box and you can't always get what you want from that. It can sign plugins when choosing Export. Automatically building Eclipse plugins has been sort of difficult for quite a while.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |