On 18-Apr-08, at 7:22 PM, Brett Porter wrote:
On 19/04/2008, at 12:32 AM, Jason van Zyl wrote:
If this is the only one failing then it's a Maven problem and I'm
going to merge in XBR to Plexus and then in Maven.
Can you elaborate on what this will facilitate in Maven?
Employing a more w
On 19/04/2008, at 12:32 AM, Jason van Zyl wrote:
If this is the only one failing then it's a Maven problem and I'm
going to merge in XBR to Plexus and then in Maven.
Can you elaborate on what this will facilitate in Maven?
- Brett
--
Brett Porter
[EMAIL PROTECTED]
http://blogs.exist.com/bp
It looks like Maven 2.0.9 is refusing to resolve the JRuby 1.0 dependencies
due to a self referential property in its POM:
[WARNING] POM for 'org.jruby:jruby:pom:1.0:test' is invalid. It will be
ignored for artifact resolution. Reason: The POM expression:
${java.specification.version} could not be
FWIW, in 2.0.9 you can override the plugin dependency and force a newer
version of the PMD jar (provided the api is compatible of course)
-Original Message-
From: Benjamin Bentmann [mailto:[EMAIL PROTECTED]
Sent: Friday, April 18, 2008 3:08 PM
To: dev@maven.apache.org
Subject: Re: Maven P
You'll have to check who owns them and ask them to run the
fix-permissions script in the root of the m2-snap repo.
-Original Message-
From: Benjamin Bentmann [mailto:[EMAIL PROTECTED]
Sent: Friday, April 18, 2008 7:09 PM
To: Maven Developers List
Subject: Deployment of maven-pmd-plugin:2.
Hi,
I wanted to deploy a new 2.4-snapshot of the PMD Plugin but failed because
the existing metadata files are not group-writable. Can somebody help and
fix the file permissions?
Benjamin
-
To unsubscribe, e-mail: [EMAIL PR
Amir Eliaz wrote:
> So the problem really is a wrong dependency in maven-pmd-plugin-2.3.pom,
> which is the latest for this plugin.
The dependency in general is not wrong, it's just inappropriate for users
that would like to use newer rules.
The SVN head has just been updated to use 4.2.1 (see
h
Hi,
We solved 22 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11095&styleName=Html&version=14088
Staging repo:
http://people.apache.org/~rafale/archetype-stage-repository/
Staging site:
http://maven.apache.org/plugins/maven-archetype-plugin-2.0-alpha-3/
Guide to testing st
My +1
Raphaël
2008/4/18, Raphaël Piéroni <[EMAIL PROTECTED]>:
> Hi,
>
> We solved 22 issues:
>
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11095&styleName=Html&version=14088
>
> Staging repo:
> http://people.apache.org/~rafale/archetype-stage-repository/
>
> Staging site:
>
Hi Paul,
I think this thread is very close to this one:
http://www.nabble.com/How-to-use-central-repo-into-an-Eclipse-project--td16676423s177.html
Cheers,
Vincent
2008/4/15, Paul Gier <[EMAIL PROTECTED]>:
> Hi everyone,
>
> I'd like to make a small change to the artifact version parsing. We
>
yes, see http://docs.codehaus.org/display/MAVEN/Versioning
Le vendredi 18 avril 2008, Brett Porter a écrit :
> I believe Kenney wrote a proposal on the wiki, and maybe even some
> code, for some changes - it would be worth reviewing them too.
>
> - Brett
>
> On 18/04/2008, at 12:27 AM, Paul Gier w
I fixed that test last week in maven 2.1
-john
On Apr 18, 2008, at 12:32 PM, Jason van Zyl wrote:
John, was just talking to Brian to see how many ITs were failing
with 2.1.x as I used the whole system using xbean reflect and I
only see one IT failing:
testitMNG3473
(org.apache.maven.inte
John, was just talking to Brian to see how many ITs were failing with
2.1.x as I used the whole system using xbean reflect and I only see
one IT failing:
testitMNG3473
(org.apache.maven.integrationtests.MavenITmng3473PluginReportCrash)
I'm loading this back up in Hudson as the the last run
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
14 matches
Mail list logo
