The following comment has been added to this issue:
Author: Brett Porter
Created: Fri, 3 Sep 2004 2:53 AM
Body:
that would have been me taking the snapshot.
We are not using the new jelly/jexl versions on the branch because of the potential
for far reaching changes. The branch sh
Howdy
I just grabbed maven from cvs (head view), and when building I got a
[junit] [ERROR] TEST org.apache.maven.plugin.PluginManagerTest FAILED
here the test log :
Testsuite: org.apache.maven.plugin.PluginManagerTest
Tests run: 7, Failures: 0, Errors: 1, Time elapsed: 9,281 sec
-
The following comment has been added to this issue:
Author: dion gillard
Created: Fri, 3 Sep 2004 2:51 AM
Body:
no:
jexl: 1.0-beta-1
jelly: 20030902.160215
-
View this comment:
http://jira.codehaus.or
The following comment has been added to this issue:
Author: Arnaud HERITIER
Created: Fri, 3 Sep 2004 2:45 AM
Body:
Are we using the last Jelly/Jexl releases (snapshots) in the 1.0 branch ?
-
View this comment:
ht
There looks like an easy fix for MAVEN-1434.
On Fri, 3 Sep 2004 08:36:08 +0200, Arnaud HERITIER <[EMAIL PROTECTED]> wrote:
> Ok, that's done.
> It's MAVEN-1434.
>
> I'll correct the plugin to make them work with the 1.0 branch.
> I think that I use some Jelly functions bugged in maven 1.0 but not
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MAVENUPLOAD-206
Here is an overview of the issue:
-
Ok, that's done.
It's MAVEN-1434.
I'll correct the plugin to make them work with the 1.0 branch.
I think that I use some Jelly functions bugged in maven 1.0 but not in 1.1.
Arnaud
On Fri, 3 Sep 2004 08:51:56 +091800, Brett Porter <[EMAIL PROTECTED]> wrote:
> Can you file a bug in JIRA gainst 1.
The following comment has been added to this issue:
Author: dion gillard
Created: Fri, 3 Sep 2004 2:39 AM
Body:
I believe this is a bad dependency. It looks like someone took a cut of JEWL while it
had JDK 1.4 only methods in it. It was fixed a day later.
Upgrade JEXL to 1.0-RC1.
The following issue has been updated:
Updater: Arnaud HERITIER (mailto:[EMAIL PROTECTED])
Date: Fri, 3 Sep 2004 2:33 AM
Comment:
Full log
Changes:
Attachment changed to maven1.1withJdk1.3.log
-
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MAVEN-1434
Here is an overview of the issue:
-
Key:
The following comment has been added to this issue:
Author: Arnaud HERITIER
Created: Fri, 3 Sep 2004 2:25 AM
Body:
It works also for me.
But I think that it is because I use maven HEAD and not maven 1.0 branch.
I'll try with the 1.0 branch.
-
The following comment has been added to this issue:
Author: Dan Greening
Created: Fri, 3 Sep 2004 1:46 AM
Body:
The patch I provided does include a couple of test cases, but if more are needed I can
add them.
-
Vi
The following comment has been added to this issue:
Author: Felipe Leme
Created: Thu, 2 Sep 2004 9:59 PM
Body:
Independently on what how M2 is going to handle it, I think we should fix this
situation on Maven 1.x, preferably at the 1.0 branch.
So, did anybody test this patch? Wha
The following comment has been added to this issue:
Author: dion gillard
Created: Thu, 2 Sep 2004 7:32 PM
Body:
Arnaud, you're in the wrong directory to reproduce the problem.
You need to be in:
maven-plugins/html2xdoc/src/plugin-test
Quoting Martijn Dashorst <[EMAIL PROTECTED]>:
> Hi,
>
> I saw an issue in JIRA for upgrading maven to use ant 1.6.2. I was
> wondering if this is done, or that I can provide any help on the matter.
Not started (hence the reason the JIRA issue is still open). You are welcome to
give it a go, bu
Can you file a bug in JIRA gainst 1.1?
I wouldn't recommend testing your plugins against 1.1/HEAD at the moment. Test
against 1.0 release or 1.0.1 (the MAVEN-1_0-BRANCH).
Once they work there, then you can test them against HEAD.
- Brett
Quoting Arnaud HERITIER <[EMAIL PROTECTED]>:
> I have th
The following comment has been added to this issue:
Author: dion gillard
Created: Thu, 2 Sep 2004 7:15 PM
Body:
I tried with JDK1.4:
C:\source\maven-plugins\html2xdoc\src\plugin-test>set JAVA_HOME=c:\j2sdk1.4.2_03
C:\source\maven-plugins\html2xdoc\src\plugin-test>maven site
__
The following comment has been added to this issue:
Author: Robert Newson
Created: Thu, 2 Sep 2004 6:39 PM
Body:
FYI: This appears to only be a requirement for WIN32.
I can run the native:jniheader goal successfully with the default properties.
The class I'm generating the header
The following comment has been added to this issue:
Author: Dan Greening
Created: Thu, 2 Sep 2004 6:27 PM
Body:
Today's plugins make distinctions on basis of type. Some simple examples: dll vs.
jar, ejb and war, etc. Having the same name, such as "user.dll" and "user.jar"
(som
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MPNATIVE-9
Here is an overview of the issue:
-
Key:
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MPCLOVER-22
Here is an overview of the issue:
-
Key
Hi,
I saw an issue in JIRA for upgrading maven to use ant 1.6.2. I was
wondering if this is done, or that I can provide any help on the matter.
I constantly run into problems with the maven test plugin (more
specifically the dependency on the ant 1.5.3 junit task).
Any thoughts on the release d
The following comment has been added to this issue:
Author: Arnaud HERITIER
Created: Thu, 2 Sep 2004 4:34 PM
Body:
I don't reproduce this problem with the current maven-core (HEAD branch) and JDK 1.4.
But I have a problem if I use a JDK 1.3 (certainly due to the last jelly update)
The following comment has been added to this issue:
Author: Thomas Hallgren
Created: Thu, 2 Sep 2004 4:29 PM
Body:
I've tried from several different places. wget on the given URL works everywhere.
Could you try with wget --server-response so that I can figure out what your problem
Message:
The following issue has been closed.
-
View the issue:
http://jira.codehaus.org/browse/MAVENUPLOAD-205
Here is an overview of the issue:
-
The following comment has been added to this issue:
Author: Carlos Sanchez
Created: Thu, 2 Sep 2004 3:56 PM
Body:
Same result.
Upload a jar to any server, there are many with free hosting
-
View this comment:
htt
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MAVENUPLOAD-205
Here is an overview of the issue:
-
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MAVENUPLOAD-204
Here is an overview of the issue:
-
The following issue has been updated:
Updater: Thomas Recloux (mailto:[EMAIL PROTECTED])
Date: Thu, 2 Sep 2004 1:09 PM
Changes:
Attachment changed to Coverage.java
-
For a full history of the issue,
The following issue has been updated:
Updater: Thomas Recloux (mailto:[EMAIL PROTECTED])
Date: Thu, 2 Sep 2004 1:09 PM
Changes:
Attachment changed to Package.java
-
For a full history of the issue,
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MPJCOVERAGE-14
Here is an overview of the issue:
-
The following comment has been added to this issue:
Author: Thomas Hallgren
Created: Thu, 2 Sep 2004 1:00 PM
Body:
That's strange. I have no problem whatsoever using wget. I just do:
bash-2.05b$ wget
ftp://gborg.postgresql.org/pub/pljava/stable/pljava-public-1.0.0b4-bundle.zip
I
vmassol 2004/09/02 09:46:36
Modified:abbot/xdocs using.xml
Log:
The MRJToolkitStubs jar is now on the iblbio repo so it's not needed to install it
manuall.
Revision ChangesPath
1.2 +1 -14 maven-plugins/abbot/xdocs/using.xml
Index: using.xml
I have the same error if I try to build maven (ant -f
build-bootstrap.xml) with the JDK 1.3
java version "1.3.1_11"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1_11-b02)
Java HotSpot(TM) Client VM (build 1.3.1_11-b02, mixed mode)
On Thu, 2 Sep 2004 18:06:19 +0200, Arnaud HERITIE
Message:
The following issue has been closed.
Resolver: Carlos Sanchez
Date: Thu, 2 Sep 2004 12:12 PM
You have to use jar, not zip
Also it can't be downloaded with wget
Connecting to gborg.postgresql.org[200.46.204.176]:21... connected.
Logging in as anonymous ... Logged in!
==> SY
But I have a problem if I launch plugin:test with a jdk 1.3 :
Now loading uncached plugins
Finished initializing Plugins!
Using userBuildPropertiesFile: C:\Documents and
Settings\aheritier\build.properties
Using projectPropertiesFile:
C:\Work\Opensources\maven-plugins\javadoc\project.properties
Us
Message:
The following issue has been closed.
Resolver: Carlos Sanchez
Date: Thu, 2 Sep 2004 12:07 PM
artifact name doesn't match pom id
-
View the issue:
http://jira.codehaus.org/browse/MAVENUPLOAD-201
Here is a
I found what happens and why I have a difference between home and work.
At work I didn't update maven core from several days.
I did it and from now javadoc tests work.
These dependencies were updated in maven core :
- commons-jelly-20040821.000223.jar
- commons-jexl-20040821.000101.jar
If you can
I just reproduced it at work.
The problem must be due to tests :
and
I modified it to recently but it worked :-(
I'll do some tests to see what happens !
Arnaud.
On Thu, 2 Sep 2004 09:57:51 -0300, Felipe Leme <[EMAIL PROTECTED]> wrote:
> On Thu, 2 Sep 2004 14:20:57 +0200, "Emmanuel Venisse
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MAVENUPLOAD-203
Here is an overview of the issue:
-
The following comment has been added to this issue:
Author: Felipe Leme
Created: Thu, 2 Sep 2004 10:52 AM
Body:
Nope, it doesn't show me that info (at least not on 1.0 - I haven't the 1.0.1 or 1.1
branches set here to check on them).
---
The following comment has been added to this issue:
Author: Emmanuel Venisse
Created: Thu, 2 Sep 2004 10:44 AM
Body:
You can obtain it with maven -X or maven -e
-
View this comment:
http://jira.codehaus.org/brows
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MAVEN-1433
Here is an overview of the issue:
-
Key:
On Thu, 2 Sep 2004 14:20:57 +0200, "Emmanuel Venisse" <[EMAIL PROTECTED]> wrote:
> It fails too for me with jdk1.4. The problem is due to the copy tag in
> javadoc:init because the project doen't have a source directory definition
> in the project.xml (and source files)
I think the plugin should
Message:
The following issue has been closed.
Resolver: Emmanuel Venisse
Date: Thu, 2 Sep 2004 8:42 AM
Applied.
-
View the issue:
http://jira.codehaus.org/browse/MPJALOPY-3
Here is an overview of the issue:
-
evenisse2004/09/02 05:36:46
Modified:jalopy plugin.properties
jalopy/src/plugin-resources jalopy_maven.xml
jalopy/xdocs changes.xml properties.xml
Log:
MPJALOPY-3. Matchs Jalopy and checkstyle.
Revision ChangesPath
1.6 +1 -1 mave
With the javadoc debug mode, I see that sourcemodification is used. I think
the test of the existence of sourcemodification is incorrect.
+
| Test MPJAVADOC-40
| Memory: 13M/15M
+
Plugin 'maven-deploy-plugin' in projec
- Original Message -
From: "Felipe Leme" <[EMAIL PROTECTED]>
To: "Maven Developers List" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Thursday, September 02, 2004 1:29 PM
Subject: Re: cvs commit: maven-plugins maven.xml
> On Thu, 2 Sep 2004 12:46:02 +0200, Arnaud HERITIER <[EMAIL P
felipeal2004/09/01 20:18:10
maven-plugins/javadoc/src/plugin-test/test08/src/main/org - New directory
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
On Thu, 2 Sep 2004 12:46:02 +0200, Arnaud HERITIER <[EMAIL PROTECTED]> wrote:
> > Even javadoc/test07?
> yes. I updated and tested it this morning.
I tested again this morning at home and now at work, and it failed on both. Here is
what I'm doing:
- go to maven-plugins/javadoc
- type maven plug
The following comment has been added to this issue:
Author: Eric Bottard
Created: Thu, 2 Sep 2004 7:29 AM
Body:
Regarding your comment Carlos :
I have always felt there was something odd about artifacts and dependencies in the POM
(maven1) : an artifact is something 'physical', in
>
> > All tests in javadoc and xdoc work for me with a JDK 1.4.
>
> Even javadoc/test07?
yes. I updated and tested it this morning.
>
> > ===
> > D:\Work\Dev\maven-plugins>maven plugins:test-all
> > __ __
> > | \/ |__ _Apache__ ___
> > |
On Thu, 2004-09-02 at 03:39, Arnaud HERITIER wrote:
> All tests in javadoc and xdoc work for me with a JDK 1.4.
Even javadoc/test07?
> ===
> D:\Work\Dev\maven-plugins>maven plugins:test-all
> __ __
> | \/ |__ _Apache__ ___
> | |\/| / _` \
Message:
The following issue has been closed.
-
View the issue:
http://jira.codehaus.org/browse/MAVENUPLOAD-202
Here is an overview of the issue:
-
The following comment has been added to this issue:
Author: Carlos Sanchez
Created: Thu, 2 Sep 2004 5:56 AM
Body:
Quoting Trygve:
The type is not going to be a part of the dependency id in maven 2 so it should not
become a part in maven 1 either.
-
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MPECLIPSE-43
Here is an overview of the issue:
-
Ke
Hi all
As nobody answered I started working on it, but two issues are blocking me
:
* the dependency type problem that have just been reraised
http://jira.codehaus.org/browse/MAVEN-1365 because i have a "source" and a "jar"
artifact
with the same id
* the http://jira.codehaus.org/browse/MAVE
Usually I do
On Thu, 2 Sep 2004 08:39:10 +0200, Arnaud HERITIER <[EMAIL PROTECTED]> wrote:
> Hi Dion,
>
> Do you use a JDK 1.3 ?
>
> All tests in javadoc and xdoc work for me with a JDK 1.4.
>
> ===
> D:\Work\Dev\maven-plugins>
The following comment has been added to this issue:
Author: Jan-Helge Bergesen
Created: Thu, 2 Sep 2004 3:24 AM
Body:
I'm suspecting it might be the XDOC generation, or possibly the XDOC to HTML
conversion.
Anyway it fails even with -Xmx512m - adding more will all but kill of Wind
isn't it
http://jira.codehaus.org/browse/MAVEN-1087
?
Julien
Extranet
[EMAIL PROTECTED] - 02/09/2004 00:30
Veuillez répondre à [EMAIL PROTECTED]
Pour : dev, maven
cc :
Objet : Re: Multiple dependencies with the same id but different types
This is a known issue.
On Wed, 1 Sep 200
60 matches
Mail list logo
