+1
--jason
On Jul 8, 2007, at 4:56 PM, Brian E. Fox wrote:
Last release vote this weekend, I promise ;-)
The rule api is used by the plugin and is included with this vote. The
only change was to the pom to remove an unnecessary dependency.
This release contains a few small fixes and sev
+1
On 8 Jul 07, at 4:56 PM 8 Jul 07, Brian E. Fox wrote:
Last release vote this weekend, I promise ;-)
The rule api is used by the plugin and is included with this vote. The
only change was to the pom to remove an unnecessary dependency.
This release contains a few small fixes and several
+1
On 8 Jul 07, at 4:37 PM 8 Jul 07, Brian E. Fox wrote:
There have been tons of enhancements to the plugin testing harness
since
the last release in April. Several plugins require the new version
before release.
Tag:
https://svn.apache.org/repos/asf/maven/shared/tags/maven-plugin-
testi
+1
Typo in the site url, correct url is:
http://people.apache.org/~jdcasey/stage/sites/maven-patch-plugin
Also, I noticed the faq seems malformed with 2 lists of questions
instead of 1 list with 2 questions. Otherwise looks interesting.
-Original Message-
From: John Casey [mailto:[EMAIL
+1
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 04, 2007 5:18 AM
To: Maven Developers List
Subject: [vote] Release Maven Shared JAR component 1.0
This component is used in the project-info-reports plugin (and is a
prereq to its next release) and
Last release vote this weekend, I promise ;-)
The rule api is used by the plugin and is included with this vote. The
only change was to the pom to remove an unnecessary dependency.
This release contains a few small fixes and several new enforcer rules.
The site has been updated with info a
+1 to release 2.4, tested with several projects mine.
-D
On 7/8/07, Brian E. Fox <[EMAIL PROTECTED]> wrote:
The problem is in the invoker. When the pom is specified as is in the
case of the plugin tools, the -F command line is used to specify it:
if ( !"pom.xml".equals( pom.getNam
There have been tons of enhancements to the plugin testing harness since
the last release in April. Several plugins require the new version
before release.
Tag:
https://svn.apache.org/repos/asf/maven/shared/tags/maven-plugin-testing-
harness-1.1
Staged at:
http://people.apache.org/~brianf
The problem is in the invoker. When the pom is specified as is in the
case of the plugin tools, the -F command line is used to specify it:
if ( !"pom.xml".equals( pom.getName() ) )
{
logger
.debug( "Specified POM file is not named
\'pom.x
Sorry to -1 after all the recent hard work fixing the tests, but they
still break on Windows when run in a path with spaces - see
MECLIPSE-291.
Should be an easy fix, although I'm not sure if I'll get a chance to
take a proper look immediately.
Cheers,
Mark
On 08/07/07, Brian E. Fox <[EMAIL PR
After battling with the braindead resource filtering once again for the
ump-teenth time, I've decided I need to do something about it
The main thing I'd like to do is allow use of a better filter engine
(like velocity) that would provide much more flexibility. The issue is
how to do i
On 7/8/07, Jochen Wiedmann <[EMAIL PROTECTED]> wrote:
On 7/8/07, Carlos Sanchez <[EMAIL PROTECTED]> wrote:
> that could be post 1.0 to mitigate risk
Please have a look at the proposed changes before considering it a risk.
I just meant that if it were a risk (as you said it changed the whole
s
On 7/8/07, Carlos Sanchez <[EMAIL PROTECTED]> wrote:
that could be post 1.0 to mitigate risk
Please have a look at the proposed changes before considering it a risk.
Thanks,
Jochen
--
"Besides, manipulating elections is under penalty of law, resulting in
a preventative effect against manip
On 7/8/07, Jochen Wiedmann <[EMAIL PROTECTED]> wrote:
On 7/8/07, Kenney Westerhof <[EMAIL PROTECTED]> wrote:
> I'd like to see wheter it's feasible to release this wagon provider
> separately as rc1, or wheter we have to release the entire wagon
> stack.
that will depend on what changes are in
On 7/8/07, Kenney Westerhof <[EMAIL PROTECTED]> wrote:
I'd like to see wheter it's feasible to release this wagon provider
separately as rc1, or wheter we have to release the entire wagon
stack.
IMO, wagon-webdav is almosu unusable without proxy support. Which
requires that WAGON-82 be fixed f
I was confused when I first looked at the code also, but on XP at least it does
work. (I stepped through it with the debugger).
The details on the problems I found are in MNG-3085, but in short sometimes the
variable is retrieved literally as "${env.M2_HOME}" so it's not resolving
correctly som
Hi,
I recently fixed 2 bugs in wagon-webdav rc1-snapshot
that make it possible to use it with maven 2.1 and 2.0.6/2.0.7.
One bug was the addition of the omitted and required plexus-utils
dependency - the code directly uses it. Since 2.0.6, plexus-utils
is shaded and plugins and extensions are re
Brian E. Fox wrote:
I recently had some trouble with the invoker getting a good maven.home
value from the mvn script. I came across this code in the eclipse tests
that seems to work pretty well. Is there any objection to moving this
code into the invoker in a fall back scenario? (ie if the exec
18 matches
Mail list logo
