Thanks... I'm not sure why that is a warn either... :-\
--jason
On Apr 24, 2008, at 4:40 AM, Hervé BOUTEMY wrote:
where:
http://maven.apache.org/ref/2.0.9/maven-project/xref/org/apache/maven/project/DefaultMavenProjectBuilder.html#525
hope this will help to understand why: I don't really kno
I am curious too. Anyone?
Cheers,
Vincent
2008/4/23 Jesse McConnell <[EMAIL PROTECTED]>:
> I don't see why that is a warn condition
>
> jesse
>
> On Wed, Apr 23, 2008 at 4:40 PM, Hervé BOUTEMY <[EMAIL PROTECTED]>
> wrote:
>
>
>
> > where:
> >
> >
> http://maven.apache.org/ref/2.0.9/ma
I don't see why that is a warn condition
jesse
On Wed, Apr 23, 2008 at 4:40 PM, Hervé BOUTEMY <[EMAIL PROTECTED]>
wrote:
> where:
>
> http://maven.apache.org/ref/2.0.9/maven-project/xref/org/apache/maven/project/DefaultMavenProjectBuilder.html#525
>
> hope this will help to understand why: I
where:
http://maven.apache.org/ref/2.0.9/maven-project/xref/org/apache/maven/project/DefaultMavenProjectBuilder.html#525
hope this will help to understand why: I don't really know
Hervé
Le mercredi 23 avril 2008, Jason Dillon a écrit :
> Anyone know what this warning means:
>
>
> [WARNING] Att
Anyone know what this warning means:
[WARNING] Attempting to build MavenProject instance for Artifact
(org.codehaus.mojo:ianal-maven-plugin:1.0-alpha-1-20080423.162027-1)
of type: maven-plugin; constructing POM artifact instead. ?
Not specific to the ianal plugin, but gmaven plugins spit
That's exactly what I'm looking for.
But this requires some knoledge about eclipse plugins development and
packaging.
A sample "bridge" would help a lot ;-)
2008/4/23, Igor Fedorenko <[EMAIL PROTECTED]>:
>
> Yes, this is it and you'd need to write an Eclipse plugin to use this.
> Taking Checksty
FWIW, I was able to use 2.0-alpha-2 without any issues on my current setup.
This makes me believe something is broken in the alpha-3.
-Original Message-
From: Brian E. Fox [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 23, 2008 11:42 AM
To: Maven Developers List
Subject: RE: [VOTE] Rel
Yes, this is it and you'd need to write an Eclipse plugin to use this.
Taking Checkstyle as an example, you probably want to use one of
existing Eclipse/Checkstyle plugins, so m2e project configurator would
work as a sort of configuration bridge, i.e it would take checkstyle
settings from pom.x
yup. changing to +1.
Still investigating the issue with embedded use, most probably issue
with the 2.1-SNAPSHOT core maven.
Milos
On Wed, Apr 23, 2008 at 5:26 PM, Raphaël Piéroni
<[EMAIL PROTECTED]> wrote:
> IIRC the
> mvn archetype:generate -Darchetype.interactive=false
> can be safely replace
Hi there,
I'd like to move maven-runtime out of the sandbox and release 1.0-alpha-1:
http://svn.apache.org/repos/asf/maven/sandbox/trunk/shared/maven-runtime/
Maven Runtime allows introspection of Maven project metadata at
runtime. For example, MavenProject instances can be obtained for all
pro
-1 for now since I'm getting an error:
Choose a number:
(1/2/3/4/5/6/7/8/9/10/11/12/13/14/15/16/17/18/19/20/21/22/23/24/25/26/27/28/29/30/31/32/33/3
4/35/36/37/38/39/40/41/42/43/44) 15: : 15
[INFO] artifact org.apache.maven.archetypes:maven-archetype-quickstart:
checking for updates from maven-
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
IIRC the
mvn archetype:generate -Darchetype.interactive=false
can be safely replaced with
mvn archetype:generate -B
In your correction email, you didn't changed your -1, is it intentional?
or did you just forget changing to +1 ;-)
Regards,
Raphaël
2008/4/23 Milos Kleint <[EMAIL PROTECTED]>:
>
This one ?
http://docs.codehaus.org/display/M2ECLIPSE/Extensible+project+import+and+configuration+framework
I've installed m2eclipse for evaluation, but don't know where I can setup
those extensions.
Does a new configurator require to include some new eclipse plugins, or can
it be set as "free" ja
-1 the generate goal in non-interactive mode asks for confirmation of values..
Milos
On Wed, Apr 23, 2008 at 2:38 PM, Brian E. Fox <[EMAIL PROTECTED]> wrote:
> Thanks for the reminder. I will look this morning.
>
>
>
> -Original Message-
> From: Arnaud HERITIER [mailto:[EMAIL PROTECTED]
This is probably offtopic, but m2e does support custom project
configurators so it is possible to plugin support for checkstyle or
whatever happens to be your favourite plugin.
Brian E. Fox wrote:
Both are still early and I'm sure there will be support for these
things, especially if they are
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 being less popular over time. I know that I used to live or die by
the m-e-p, but once
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(*)
Exactly. What's the chance that Q4E and/or m2eclipse will support RAD-6 and
MyEclipse?
On Wed, Apr 23, 2008 at 4:01 PM, Arnaud HERITIER <[EMAIL PROTECTED]>
wrote:
> That is THE question and why I didn't yet start this dev.
> In fact it depends a lot of those IDE plugins. I don't know how many
> t
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
correction. I seems to be connected to 2.1-SNAPSHOT embedded maven.
with command-line 2.0.9 it works fine. I use
-Darchetype.interactive=false in both cases..
Milos
On Wed, Apr 23, 2008 at 3:42 PM, Milos Kleint <[EMAIL PROTECTED]> wrote:
> -1 the generate goal in non-interactive mode asks for con
That is THE question and why I didn't yet start this dev.
In fact it depends a lot of those IDE plugins. I don't know how many
time they will need to support all our features even if they are
working fast. We have a lot of features now (which is also a problem
now) but they are used a lot in corpor
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
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?
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of nicolas de loof
Sent: Wednesday, April 23, 2008 9
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
Thanks for the reminder. I will look this morning.
-Original Message-
From: Arnaud HERITIER [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 23, 2008 6:18 AM
To: Maven Developers List
Subject: Re: [VOTE] Release Maven Archetype plugin version 2.0-alpha-3 [take 2]
anyone else (I real
+1
-Lukas
Raphaël Piéroni wrote:
Hi,
According To the committer list in
http://svn.apache.org/repos/asf/maven/pom/trunk/maven/pom.xml
We have currently:
2 non binding vote (Jason, Raphaël)
1 binding vote (Arnaud)
IIRC the voting process, we need 3 binding vote (PMC), for a
plugin release.
Pl
anyone else (I really need this release ;-) )
Arnaud
On Tue, Apr 22, 2008 at 9:14 AM, Raphaël Piéroni
<[EMAIL PROTECTED]> wrote:
> Hi,
> According To the committer list in
> http://svn.apache.org/repos/asf/maven/pom/trunk/maven/pom.xml
> We have currently:
> 2 non binding vote (Jason, Ra
34 matches
Mail list logo
