I've have built a custom solution for the Geronimo eclipse plugin using M1 and almost done with migrating it over to M2. I wouldn't say the project structure is necessarily the issue. The issue is encapsulating the function of the PDE builder in a reusable way. The other issue is handling eclipse dependencies. I currently have a plugin that essentaially allows you to compile against a given distribution of eclipse or a set of eclipse projects mimicking the concept of the "target workbench" in eclipse. This I'm sure you could reuse/enhance. Then the only thing left is to create reusable plugins that create the distributions.

If you want to take a look at what I currently have for M2 take a look at..

https://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/trunk/

I also have a M2 plugin that allows you to run any headless eclipse application, for example in the Geronimo case, using the EMF headless applications to generate EMF models.

- sachin



On Mar 22, 2006, at 6:41 AM, [EMAIL PROTECTED] wrote:

Hi,

Does anyone have any tips or best practices for handling Eclipse plugin
development in maven?

We are developing an product in Eclipse consiting of multiple plugins and features. The maven directory structure is not the same as the struture
created by Eclipse PDE. I know maven's structure can be changed, but I
don't know if that is the "right" solution.

Regards

Henrik

______________________________________________________________________ _________________________________________

This e-mail communication (and any attachment/s) may contain confidential or privileged information and is intended only for the individual (s) or entity named above and to others who have been specifically authorized to
receive it. If you are not the intended recipient, please do not read,
copy, use or disclose the contents of this communication to others. Please
notify the sender that you have received this e-mail in error by reply
e-mail, and delete the e-mail subsequently.
Thank you.
______________________________________________________________________ ___________________________________________


Ce message (ainsi que le(s) fichier/s), transmis par courriel, peut
contenir des renseignements confidentiels ou protégés et est destiné à
l?usage exclusif du destinataire ci-dessus. Toute autre personne est par
les présentes avisée qu?il est strictement interdit de le diffuser, le
distribuer ou le reproduire. Si vous l?avez reçu par inadvertance,
veuillez nous en aviser et détruire ce message.
Merci.
______________________________________________________________________ ___________________________________________




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to