On Mon, 2003-01-06 at 03:25, Nick Minutello wrote: > I am putting together a Maven build for a number of eclipse plugins. > > At first glance, it seems trickier than I had anticipated.... > I wonder if anyone already has any experience with this or has some > advice
Still on my todo list. > > Dependancies: > Eclipse requires all its dependancy jars to be deployed as plugins > (There is a plugin.xml and a bunch of other stuff). > Does anyone know if there is a Maven plugin that generates eclipse > plugin.xml files? I didn't encounter one. The other way around though seems more usefull (maven can use the plugin.xml to build the project..) > > Versions: > Eclipse embeds the version in the directory name rather than the jar > name (opposite of Maven). > This means that jar produced by Maven is not immediately usable > (deployable) You can probably fix that in a mven.xml post goal. > > Repository: > We currently dont have any eclipse jars in ibiblio - is anyone else > interested in having them there? > What naming/versioning convention should we use? > > So far, I need : > org.eclipse.core.runtime_2.0.0/runtime.jar > org.eclipse.core.boot_2.0.0/boot.jar > org.eclipse.core.resources_2.0.0/resources.jar > org.eclipse.core.resources.win32_2.0.0/os/win32/x86/core_2_0_5.dll (not > sure how we store this) > org.eclipse.update.core_2.0.0/updatecore.jar > startup.jar (for 2.0.0) I doubt you need the dll to build the plugin. (at least I don't need it for swt stuff). Btw swt.jar is already on ibiblio and eclipse already is on 2.0.1. You can have a look at how jelly handles the SWT stuff. (the win32 swt.jar also lets swt stuff build on unix eg..) I think a seperate (maven) plugin is the best to handle this, so it can also depend on a a plain eclipse installation, instead of a huge amount of jars on ibiblio that change quite often. (eg depending on an ECLIPSE_HOME env variable or property setting. Mvgr, Martin -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
