Re: [m2] Extending Eclipse plugin

[Kenney Westerhof <ke...@apache.org>]

On Tue, 20 Sep 2005, Rinku wrote:

> Hi,
>
> I have a use case where I need to reuse/extend the functionality
> provided by existing M2 Eclipse plugin. The use case involves creating
> "deployables" directory from defined project properties and some other
> updates to ".wtpmodules" contents.
>
> What I want to do is to create sort of a wrapper plugin that can
> delegate 'standard' goals to the Eclipse plugin and do some pre/post
> processing around these 'standard' goals. Could anyone please explain
> what would be a neat way to achieve this and keep the option of being
> able to reuse future Eclipse plugin releases but just updating the
> version numbers in pom.

I think it would be better if your changes are put in the eclipse plugin
(at least for the contents of the .wtpmodules). Creation of custom
directories on the other hand is not something the eclipse plugin should
do - the maven build should create those too as it needs it.. maybe just
use a target/... directory for that and let eclipse automatically create
it, like target/classes?

What are the exact changes? Do you think they are general enough
to be added to the eclipse plugin?

-- Kenney
>
> Thanks in advance for all the help.
>
> Cheers,
>
> Rahul
>
>

--
Kenney Westerhof
http://www.neonics.com
GPG public key: http://www.gods.nl/~forge/kenneyw.key

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: [m2] Extending Eclipse plugin

[Rinku <ra...@gmail.com>]

Hi Kenney,

My comments inline...

Kenney Westerhof wrote:

>On Tue, 20 Sep 2005, Rinku wrote:
>
>  
>
>>Hi,
>>
>>I have a use case where I need to reuse/extend the functionality
>>provided by existing M2 Eclipse plugin. The use case involves creating
>>"deployables" directory from defined project properties and some other
>>updates to ".wtpmodules" contents.
>>
>>What I want to do is to create sort of a wrapper plugin that can
>>delegate 'standard' goals to the Eclipse plugin and do some pre/post
>>processing around these 'standard' goals. Could anyone please explain
>>what would be a neat way to achieve this and keep the option of being
>>able to reuse future Eclipse plugin releases but just updating the
>>version numbers in pom.
>>    
>>
>
>I think it would be better if your changes are put in the eclipse plugin
>(at least for the contents of the .wtpmodules). Creation of custom
>directories on the other hand is not something the eclipse plugin should
>do - the maven build should create those too as it needs it.. maybe just
>use a target/... directory for that and let eclipse automatically create
>it, like target/classes?
>  
>
Yes, I thought about putting my changes into the existing plugin but 
then I can't simply reuse any future versions of the Eclipse plugin. 
Agreed that creation of custom directories is not something that Eclipse 
plugin should do by default, hence motivation behind creation of wrapper 
plugin that can handle my project specific properties and delegate them 
to Eclipse plugin to get the common/standard stuff done.

>What are the exact changes? Do you think they are general enough
>to be added to the eclipse plugin?
>
>  
>
For instance, I need to be able to:
a) create additional <wb-resource> definitions such that I can overlay 
resource patches for my development environment as per project properties.
b) setup <wb-module> definitions and a context path from my project 
properties for my application server for use from within Eclipse IDE.

I'd prefer to use Eclipse plugin to get the work done to the extent 
possible and handle only bits that are driven by custom project properties.

Appreciate any thoughts, suggestions. 

Cheers,

Rahul .

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org