Great,
Count on me for flexbuilder support.
VELO
On Wed, Apr 30, 2008 at 10:58 AM, Arnaud HERITIER <[EMAIL PROTECTED]>
wrote:
> both of them.
> If you specify your workspace location, the plugin will try to auto-detect
> your features plugins and if it find contributors compatible with them it
both of them.
If you specify your workspace location, the plugin will try to auto-detect
your features plugins and if it find contributors compatible with them it
will generate appropriate settings.
If not, you'll have to specify them (like is actually with properties like
wtpversion or custom goal
Question:
The extensions, will auto-actived according with installed eclipse (don't
like this idea) or I will declared on pom.xml my extensions?
VELO
On Wed, Apr 30, 2008 at 10:45 AM, nicolas de loof <[EMAIL PROTECTED]>
wrote:
> I've created an inital proposal for this on wiki :
>
>
> http://do
I've created an inital proposal for this on wiki :
http://docs.codehaus.org/display/MAVEN/Eclipse+plugin+refactored+for+extensibility
2008/4/24 VELO <[EMAIL PROTECTED]>:
> Flex / Flex builder
>
> I created a flexbuilder-mojo, who inherit from maven-eclipse-plugin
>
> If this goes on, I can cre
Flex / Flex builder
I created a flexbuilder-mojo, who inherit from maven-eclipse-plugin
If this goes on, I can create flexbuilder extension.
VELO
On Wed, Apr 23, 2008 at 9:39 AM, Simone Gianni <[EMAIL PROTECTED]> wrote:
> Hi Nicolas,
> yes, many Maven plugins have an Eclipse counterpart, and h
er way, I might suggest embarking on this rewrite on a separate
> > > > branch from the current m-e-p code so that you can still maintain
> > > > the
> > > > old one for a bit.
> > > >
> > > > -Original Message-
> > > &g
o that you can still maintain the
old one for a bit.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of nicolas de loof
Sent: Wednesday, April 23, 2008 10:46 AM
To: Maven Developers List
Subject: Re: [proposal] eclipse plugin extensibility
Because those plugins doesn&#x
On Wed, Apr 23, 2008 at 4:49 PM, Brian E. Fox <[EMAIL PROTECTED]> wrote:
> Both are still early and I'm sure there will be support for these
> things, especially if they are filed as requests. I'm not saying that
> the current eclipse plugin isn't still useful now, I just personally see
> it bei
from the current m-e-p code so that you can still maintain the
> > old one for a bit.
> >
> > -Original Message-
> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
> > Behalf Of nicolas de loof
> > Sent: Wednesday, April 23, 2008 10:46 AM
> > To: Mave
ers List
Subject: Re: [proposal] eclipse plugin extensibility
Because those plugins doesn't support custom setup :
I'm using the sysdeo-tomcat plugin to setup tomcat plugin for eclipse.
It
makes my life simplier but is ignored by q4e / m2eclipse.
And AFAIK neither m2eclipse nor q4e suppor
TECTED] On
Behalf Of nicolas de loof
Sent: Wednesday, April 23, 2008 10:46 AM
To: Maven Developers List
Subject: Re: [proposal] eclipse plugin extensibility
Because those plugins doesn't support custom setup :
I'm using the sysdeo-tomcat plugin to setup tomcat plugin for eclipse.
It
makes m
Because those plugins doesn't support custom setup :
I'm using the sysdeo-tomcat plugin to setup tomcat plugin for eclipse. It
makes my life simplier but is ignored by q4e / m2eclipse.
And AFAIK neither m2eclipse nor q4e support to read the maven checkstyle(*)
configuration to setup checkstyle(*)
-
> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
> > Behalf Of nicolas de loof
> > Sent: Wednesday, April 23, 2008 9:42 AM
> > To: Maven Developers List
> > Subject: Re: [proposal] eclipse plugin extensibility
> >
> > Right
> >
&g
Now that there are two real eclipse plugins for maven, I have to wonder
how much use this plugin will continue to get and if it's worth such a
major overhaul?
A possible reason to use the maven-eclipse-plugin:
It's not as invasive as Q4E or M2Eclipse. You can invoke it once on your own
discretio
>
>
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
> Behalf Of nicolas de loof
> Sent: Wednesday, April 23, 2008 9:42 AM
> To: Maven Developers List
> Subject: Re: [proposal] eclipse plugin extensibility
>
> Right
You're right. It's not only writers but all configuration files.
Arnaud
On Wed, Apr 23, 2008 at 3:41 PM, nicolas de loof <[EMAIL PROTECTED]> wrote:
> Right
>
> This will work on a "per file to generate" basis, isn't it ?
>
> What if a contributor want's to add a buildcommand (for example checkst
2008 9:42 AM
To: Maven Developers List
Subject: Re: [proposal] eclipse plugin extensibility
Right
This will work on a "per file to generate" basis, isn't it ?
What if a contributor want's to add a buildcommand (for example
checkstyle)
?
I don't think we just need a ecl
Right
This will work on a "per file to generate" basis, isn't it ?
What if a contributor want's to add a buildcommand (for example checkstyle)
?
I don't think we just need a eclipse-writers-api, but a larger
eclipse-plugin-contributor-api that includes
- eclipse feature detection (to allow my Fo
No it's impossible in maven 2.0.x to load those writers from another plugin.
In my mind we have to add all writers as plugin's dependency. By
default we'll propose a large set of existing writers, but users will
also be able to add their own.
By default we'll have something like :
eclipse-plugin
|-
Your idea is complementary to mine :
You want to discover what the target eclipse installation can do and extract
any usefull configuration from maven to setup the workspace.
My idea was to "plug" into the eclipse plugin the dedicated contributors -
but they could themself rely on what eclipse su
The main diffiulty to make plugins collaborate is taht they run in isolation
(distinct classloaders), so they can't share structured datas - until
declared in a maven extension.
The eclipse plugin can lookup the MavenProject for plugin, maybe detect some
contributors one, but cannot invoke code as
It's exactly why I want to do for a 3.0 release of the plugin.
What we could have is to try to discover features of eclipse reading
its workspace.
For each feature/plugin we try to find in the writers list (loaded by
default or through the plugin config) the most recent version of the
writer compat
On 23/04/2008, Simone Gianni <[EMAIL PROTECTED]> wrote:
> Hi Nicolas,
> yes, many Maven plugins have an Eclipse counterpart, and having the
> eclipse plugin discover this plugins and delegate to them the generation
> of eclipse specific configurations is a great idea. I don't know the
> interna
Hi Nicolas,
yes, many Maven plugins have an Eclipse counterpart, and having the
eclipse plugin discover this plugins and delegate to them the generation
of eclipse specific configurations is a great idea. I don't know the
internals of the Eclipse plugin well enough to understand the details of
your
Hello,
I'd like to propose an extension mecanism for the Eclipse plugin (and
potentially for other plugins).
The sysdeo-tomcat-maven-plugin (mojo project) for example has copie/pasted
the dependency resolution code from eclipse plugin. This was required to
create the .tomcatPlugin configuration f
25 matches
Mail list logo
