+1
Emmanuel
John Casey a écrit :
Hi again,
I wanted to let everyone know that we've got the latest round of
regressions fixed, including:
* Fabrizio's lingering path problems from MNG-2006
* MNG-2136
* MNG-2124
* MNG-2130
These fixes also took care of some other outstanding issues, which h
I am currently using 2.0.3 snapshot(s) in my production build.
So far all my builds work great
+1 and looking forward to the release.
-Dan
On 3/10/06, Wayne Fay <[EMAIL PROTECTED]> wrote:
>
> Well I did say "correct me if I'm wrong"... ;-)
>
> Thanks for the education, Brett.
>
> Wayne
>
>
> On
Well I did say "correct me if I'm wrong"... ;-)
Thanks for the education, Brett.
Wayne
On 3/10/06, Brett Porter <[EMAIL PROTECTED]> wrote:
> http://www.apache.org/foundation/voting.html
>
> Actually, it's just PMC members. They are the ones with the authority to
> make a release official.
>
> O
+1
John Casey wrote:
> Hi again,
>
> I wanted to let everyone know that we've got the latest round of
> regressions fixed, including:
>
> * Fabrizio's lingering path problems from MNG-2006
> * MNG-2136
> * MNG-2124
> * MNG-2130
>
> These fixes also took care of some other outstanding issues, wh
http://www.apache.org/foundation/voting.html
Actually, it's just PMC members. They are the ones with the authority to
make a release official.
Of course, we like to hear from everyone that has tested something to
confirm whether it is working or not.
- Brett
Wayne Fay wrote:
> Correct me if I'm
Correct me if I'm wrong... but I'm pretty certain non-binding votes
are when "people who aren't official Maven devs but happen to
subscribe to this list" (like me) feel like voting on dev issues. ;-)
Edwin, you're a "real Maven dev" so your votes on an issue are always "binding".
Wayne
On 3/10
+1
(what's non-binding?)
^_^
John Casey wrote:
Hi again,
I wanted to let everyone know that we've got the latest round of
regressions fixed, including:
* Fabrizio's lingering path problems from MNG-2006
* MNG-2136
* MNG-2124
* MNG-2130
These fixes also took care of some other outstandin
No, I'm using the cli. That would be a result of the svn:keywords being
set correctly under tortoise and not eclipse, I'd guess.
Anyway, no big concern, it wasn't what I wanted anyway.
- Brett
Rinku wrote:
> Are you using Eclipse to commit? I have noticed this behaviour with
> Eclipse when commi
Are you using Eclipse to commit? I have noticed this behaviour with
Eclipse when committing to CVS (not sure about SVN).
If I commit a resource with $Id$ using tortoiseSVN for first ever
commit, the $Id$ gets interpolated correctly for all subsequent commits
(even from within Eclipse)...
Rah
SVN is meant to fill it in, and I had svn:keywords set correctly, but it
wasn't working. I think it would leave the $$ on there anyway so I
Realised it wasn't what I wanted.
- Brett
dan tran wrote:
> Hi Brett,
>
> What is $Revision$ ?
>
> -D
>
>
> On 3/10/06, [EMAIL PROTECTED] <[EMAIL PROTECT
+1, I hope we'll not have the same problem to maintain a lot of plugins like
in maven 1 but these plugins are important and our team must ensure that the
quality of them is decent.
Arnaud
On 3/10/06, Carlos Sanchez <[EMAIL PROTECTED]> wrote:
>
> +1 for all but dependency-maven-plugin
> +0 for de
+1
On 3/10/06, John Casey <[EMAIL PROTECTED]> wrote:
> Hi again,
>
> I wanted to let everyone know that we've got the latest round of
> regressions fixed, including:
>
> * Fabrizio's lingering path problems from MNG-2006
> * MNG-2136
> * MNG-2124
> * MNG-2130
>
> These fixes also took care of some
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
+1 (non-binding)
John Casey wrote:
> Hi again,
>
> I wanted to let everyone know that we've got the latest round of
> regressions fixed, including:
>
> * Fabrizio's lingering path problems from MNG-2006
> * MNG-2136
> * MNG-2124
> * MNG-2130
>
> Th
+1
-Vincent
> -Original Message-
> From: John Casey [mailto:[EMAIL PROTECTED]
> Sent: vendredi 10 mars 2006 21:40
> To: Maven Developers List
> Subject: [vote] Release Maven 2.0.3 (third RC)
>
> Hi again,
>
> I wanted to let everyone know that we've got the latest round of
> regressions
+1 (non-binding) :)
On 3/10/06, John Casey <[EMAIL PROTECTED]> wrote:
>
> Hi again,
>
> I wanted to let everyone know that we've got the latest round of
> regressions fixed, including:
>
> * Fabrizio's lingering path problems from MNG-2006
> * MNG-2136
> * MNG-2124
> * MNG-2130
>
> These fixes als
Hi again,
I wanted to let everyone know that we've got the latest round of
regressions fixed, including:
* Fabrizio's lingering path problems from MNG-2006
* MNG-2136
* MNG-2124
* MNG-2130
These fixes also took care of some other outstanding issues, which have
also been closed:
* MNG-1882
+1 for all but dependency-maven-plugin
+0 for dependency-maven-plugin (I've never used it)
On 3/9/06, Brett Porter <[EMAIL PROTECTED]> wrote:
> A month ago I sent a proposal for discussion, to bring some mojos into
> the Maven plugins project, because
> a) originally coming from here in Maven 1.x
Hi Brett,
What is $Revision$ ?
-D
On 3/10/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> Author: brett
> Date: Fri Mar 10 07:17:04 2006
> New Revision: 384810
>
> URL: http://svn.apache.org/viewcvs?rev=384810&view=rev
> Log:
> try using keyword
>
> Modified:
>maven/pom/asf/pom.xml
>
>
Done
http://jira.codehaus.org/browse/MNG-2143
Raphaël
Brett Porter a écrit :
Cool. I think this is a good idea.
In my original proposal:
"* The documentation is a big list of links. I think we should categorise
them by topic instead of type, or perhaps as Jesse suggests we should
have a cross
+1
Brett Porter wrote:
Hi,
Brian has done a great job in keeping the mojo project in order and has
developed the dependency plugin there, which we previously indicated
we'd like to have as a part of the Maven plugin artillery.
He has also actively helped on the users list and participated on t
sounds great.
+1
Brett Porter wrote:
Hi,
Fabrice worked on the JXR plugin, fixed a number of bugs in the original
library and improved the mojo. Active on the users list, with a
particular interest in the site plugin, I believe would be a good
addition to the project.
Please vote:
[ ] +1
[ ]
+1 to all.
Brett Porter wrote:
A month ago I sent a proposal for discussion, to bring some mojos into
the Maven plugins project, because
a) originally coming from here in Maven 1.x
b) having the core libraries located here
c) being essential to the day to day use of the project.
So, here is a v
Hi,
I started to put together the pom hierarchy. I'll finish rolling it
through the subprojects and plugins tomorrow.
- Brett
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
+1
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: Friday, March 10, 2006 12:36 AM
To: Maven Developers List
Subject: [vote] Brian Fox as a plugins committer
Hi,
Brian has done a great job in keeping the mojo project in order and has
developed the dependency plugi
+1
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: Friday, March 10, 2006 12:36 AM
To: Maven Developers List
Cc: [EMAIL PROTECTED]
Subject: [vote] Fabrice Bellingard as a plugins committer
Hi,
Fabrice worked on the JXR plugin, fixed a number of bugs in the origina
+1
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: Friday, March 10, 2006 12:37 AM
To: Maven Developers List
Subject: [vote] Bring plugins to Maven
A month ago I sent a proposal for discussion, to bring some mojos into
the Maven plugins project, because
a) original
look into the plexus-containers/plexus-container-default and the
plexus-components/plexus-compiler in the plexus source tree
The container has the code that does the private variable injection and
populates what the compiler manager needs...it takes a bit to work out but
it is really quite neat :)
The project's artifact file is populated in the package phase of the
lifecycle, at least in the case of the jar lifecycle. I'd say this is a
pretty standard place for it, since the assumption is that the jar would
not exist until this phase is complete. Once that phase has completed,
your mojo
Brett,
Sure will do, I think a JIRA task wouldn't do this justice. I'm working on
a mockup in Adobe Illustrator ;-)
On 3/9/06, Brett Porter <[EMAIL PROTECTED]> wrote:
>
> Tim,
>
> There's plenty of points here and on your blog. Can you please put this
> in a proposal form for how to make specifi
On 3/9/06, Brett Porter <[EMAIL PROTECTED]> wrote:
> Tim O'Brien wrote:
> > I read your response, clicked on the Geronimo site, and wanted to
> believe
> > that that was possible with Maven. But, if you look at
> > https://svn.apache.org/repos/asf/geronimo/site/
> >
> > It's either Maven 1.x or
+1 for all (non-binding)
IMHO, taglist report could as well be moved, though less essential.
- Yann
On 3/10/06, Brett Porter < [EMAIL PROTECTED]> wrote:
>
> A month ago I sent a proposal for discussion, to bring some mojos into
> the Maven plugins project, because
> a) originally coming from here
Ok. Well, that is what it is supposed to do, though. I just don't quite
understand the problem being had without more investigation. It should
be scheduled for 2.0.4.
Cheers,
Brett
Brian E. Fox wrote:
> To me these are all related because the reactor seems to link the
> sibling directly (for exam
When a JAR is added to Plexus, it is scanned for
META-INF/plexus/components.xml, and if that exists the components are
registered.
So, plexus-compiler-manager has:
org.codehaus.plexus.compiler.manager.CompilerManager
org.codehaus.plexus.compiler.manager.DefaultCompilerManager
org
To me these are all related because the reactor seems to link the
sibling directly (for example ../sibling/target/foo.jar) rather than
finding it in the repository.
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: Friday, March 10, 2006 12:22 AM
To: Maven Developers L
Hi,
in an attempt to resolve MCOMPILER-8, I have had a look at the
plexus-compiler-api.
What I found is, that the compiler API seems to have some magic way of
configuring itself, most possibly through
META-INF/plexus/components.xml.
I do not have the slightest idea, how this self configuration w
On Fri, 10 Mar 2006, Brett Porter wrote:
+1
> A month ago I sent a proposal for discussion, to bring some mojos into
> the Maven plugins project, because
> a) originally coming from here in Maven 1.x
> b) having the core libraries located here
> c) being essential to the day to day use of the pro
I'm sorry,
I don't know what to say to the jira issue
As you know i'm a bit new to open source processes.
I never released the freeform plugin because i don't know how.
Regards,
Raphaël
2006/3/10, Brett Porter <[EMAIL PROTECTED]>:
>
> Cool. I think this is a good idea.
>
> In my original propos
There is only one issue left (MIDEA-32) for 2.0.
Remains:
* MIDEA-19: nice but not necessary for a 2.0 I would say
* MIDEA-30: sounds quite major
What about fixing 32 and 30 so that we can release a 2.0-RC1?
WDYT?
s/
On 3/10/06, Manfred Geiler <[EMAIL PROTECTED]> wrote:
> Hi Maven gurus,
> Ma
Hi Maven gurus,
May I ask if there is a current roadmap for releasing
maven-idea-plugin 2.0-beta-2 ?
I ask because we plan to build a new MyFaces release in the next days
and - because of our current complex project structure - we need the
latest idea-plugin features (useClassifiers, linkModules, .
+1 for all
fabrizio
On 3/10/06, Brett Porter <[EMAIL PROTECTED]> wrote:
> So, here is a vote to bring the following plugins to Maven:
> - jxr report (relates to jxr)
> - surefire report (relates to surefire)
> - changes/jira/announcement report (relates to issue stuff in sandbox)
> - changelog r
+1
fabrizio
On 3/10/06, Brett Porter <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Brian has done a great job in keeping the mojo project in order and has
> developed the dependency plugin there, which we previously indicated
> we'd like to have as a part of the Maven plugin artillery.
--
+1
On 3/10/06, Brett Porter <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Fabrice worked on the JXR plugin, fixed a number of bugs in the original
> library and improved the mojo. Active on the users list, with a
> particular interest in the site plugin, I believe would be a good
> addition to the project.
+ 1
Brett Porter wrote:
Hi,
Fabrice worked on the JXR plugin, fixed a number of bugs in the original
library and improved the mojo. Active on the users list, with a
particular interest in the site plugin, I believe would be a good
addition to the project.
Please vote:
[ ] +1
[ ] +0 abstain
[
+ 1
Brett Porter wrote:
Hi,
Brian has done a great job in keeping the mojo project in order and has
developed the dependency plugin there, which we previously indicated
we'd like to have as a part of the Maven plugin artillery.
He has also actively helped on the users list and participated on
+1
Arnaud
On 3/10/06, Brett Porter <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> Brian has done a great job in keeping the mojo project in order and has
> developed the dependency plugin there, which we previously indicated
> we'd like to have as a part of the Maven plugin artillery.
>
> He has also act
+1
Arnaud
On 3/10/06, Brett Porter <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> Fabrice worked on the JXR plugin, fixed a number of bugs in the original
> library and improved the mojo. Active on the users list, with a
> particular interest in the site plugin, I believe would be a good
> addition to th
You're right but I didn't have the time to check how to finely configure it.
It should be :
/plugins-sandbox/*.html -> /plugins/sandbox/ (to move the root site of
sandbox plugins)
/plugins-sandbox//* -> /plugins//* (to move
plugins sites from the sandbox)
/reference/plugins/*.html -> /plugins/bun
+1
^_^
Brett Porter wrote:
Hi,
Brian has done a great job in keeping the mojo project in order and has
developed the dependency plugin there, which we previously indicated
we'd like to have as a part of the Maven plugin artillery.
He has also actively helped on the users list and participa
+1
^_^
Brett Porter wrote:
Hi,
Fabrice worked on the JXR plugin, fixed a number of bugs in the original
library and improved the mojo. Active on the users list, with a
particular interest in the site plugin, I believe would be a good
addition to the project.
Please vote:
[ ] +1
[ ] +0 abst
Cool. I think this is a good idea.
In my original proposal:
"* The documentation is a big list of links. I think we should categorise
them by topic instead of type, or perhaps as Jesse suggests we should
have a cross reference/index - so we could have a page that lists all
the howtos and guides, t
It aims to be a page or a couple of pages.
I don't have clear idea on it.
yesterday i wrote it in two pages : a main page with sample doco and an
advanced page with an exhautive doco (not in my sample be should be)
But i think it is not a navigation.
Raphaël
2006/3/10, Brett Porter <[EMAIL PRO
+1 (non-binding)
2006/3/10, Brett Porter <[EMAIL PROTECTED]>:
>
> A month ago I sent a proposal for discussion, to bring some mojos into
> the Maven plugins project, because
> a) originally coming from here in Maven 1.x
> b) having the core libraries located here
> c) being essential to the day to
+1
s/
On 3/10/06, Brett Porter <[EMAIL PROTECTED]> wrote:
> A month ago I sent a proposal for discussion, to bring some mojos into
> the Maven plugins project, because
> a) originally coming from here in Maven 1.x
> b) having the core libraries located here
> c) being essential to the day to day
+1
s/
On 3/10/06, Brett Porter <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Fabrice worked on the JXR plugin, fixed a number of bugs in the original
> library and improved the mojo. Active on the users list, with a
> particular interest in the site plugin, I believe would be a good
> addition to the proj
54 matches
Mail list logo
