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>maven plugins:test-all
__ __
| \/ |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
|_|
The following comment has been added to this issue:
Author: Ben Gidley
Created: Thu, 2 Sep 2004 2:42 AM
Body:
See http://zebra.tigris.org/nonav/penguin/
and
http://zebra.tigris.org/nonav/penguin/team-list.html
-
Vi
felipeal2004/09/01 20:37:21
Modified:javadoc/src/main/org/apache/maven/javadoc
JavadocWarningsTextToXml.java
Log:
first fix for MPJAVADOC-42: instead of failing due to an exception, a WARNING
message is logged to the console
Revision ChangesPath
1
felipeal2004/09/01 20:19:35
Added: javadoc/src/plugin-test/test08 .cvsignore maven.xml
project.xml
javadoc/src/plugin-test/test08/src/main/org/apache/maven
Dummy.java
Log:
testcase for MPJAVADOC-42 - if fails when runni
Message:
Work on this issue has been stopped by Felipe Leme (mailto:[EMAIL PROTECTED])
-
View the issue:
http://jira.codehaus.org/browse/MPJAVADOC-42
Here is an overview of the issue:
---
The following comment has been added to this issue:
Author: Felipe Leme
Created: Wed, 1 Sep 2004 11:53 PM
Body:
Ok, I fixed the code to ignore the exception. Now I've found the issue:
On JDK 1.4, javadoc prints the file and number that raised the issue:
[javadoc]
/home/felipea
The following work log has been added to this issue:
Logged By: Felipe Leme
Created: Wed, 1 Sep 2004 11:46 PM
Time Logged: 20 minutes
Description:
First workaround: ignore error and log a warning message
-
View this work log
Message:
Work on this issue has been started by Felipe Leme (mailto:[EMAIL PROTECTED])
-
View the issue:
http://jira.codehaus.org/browse/MPJAVADOC-42
Here is an overview of the issue:
---
The following work log has been added to this issue:
Logged By: Felipe Leme
Created: Wed, 1 Sep 2004 11:23 PM
Time Logged: 20 minutes
Description:
Created a test case that fails, only when compiling using JDK 1.3:
maven-javadoc-plugin:report:
[mkdir] Created dir:
/home/felipeal/cvs/mave
Message:
The following issue has been reopened.
Reopener: Felipe Leme
Date: Wed, 1 Sep 2004 11:02 PM
Test case 07 is failing:
maven-javadoc-plugin:report:
[mkdir] Created dir:
/home/felipeal/cvs/maven/maven-plugins/javadoc/src/plugin-test/test07/target/javadoc
[mkdir] Creat
dion2004/09/01 18:29:37
Modified:linkcheck project.xml
Log:
Upgrade to later version of the Ant tag library
Revision ChangesPath
1.55 +1 -1 maven-plugins/linkcheck/project.xml
Index: project.xml
dion2004/09/01 18:28:55
Modified:.Tag: MAVEN-1_0-BRANCH project.xml
Log:
Upgrade to later version of the Ant tag library
Revision ChangesPath
No revision
No revision
1.317.4.34 +2 -2 maven/project.xml
Index: pr
dion2004/09/01 18:12:33
Modified:.maven.xml
Log:
exclude failing plugin
Revision ChangesPath
1.13 +1 -1 maven-plugins/maven.xml
Index: maven.xml
===
RCS file: /home/cvs/maven-pl
dion2004/09/01 18:08:03
Modified:.maven.xml
Log:
exclude failing plugin
Revision ChangesPath
1.12 +1 -1 maven-plugins/maven.xml
Index: maven.xml
===
RCS file: /home/cvs/maven-pl
dion2004/09/01 18:05:37
Modified:.maven.xml
Log:
exclude failing plugin
Revision ChangesPath
1.11 +1 -1 maven-plugins/maven.xml
Index: maven.xml
===
RCS file: /home/cvs/maven-pl
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MPJAVADOC-43
Here is an overview of the issue:
-
Ke
dion2004/09/01 18:01:06
Modified:.maven.xml
Log:
exclude failing plugin
Revision ChangesPath
1.10 +1 -1 maven-plugins/maven.xml
Index: maven.xml
===
RCS file: /home/cvs/maven-pl
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MPECLIPSE-42
Here is an overview of the issue:
-
Ke
See http://jira.codehaus.org/browse/MAVEN-1087
On Wed, 01 Sep 2004 21:27:43 -0300, Felipe Leme <[EMAIL PROTECTED]> wrote:
> On Wed, 2004-09-01 at 19:30, Dion Gillard wrote:
> > This is a known issue.
>
> So, this is a bug, not a feature (i.e., a limitation on the dependecy
> model)? If that's the
On Wed, 2004-09-01 at 19:30, Dion Gillard wrote:
> This is a known issue.
So, this is a bug, not a feature (i.e., a limitation on the dependecy
model)? If that's the case and there isn't a Jira issue for it yet, I
can open one.
Felipe
---
If no one can actually fix your problem, you can always build the
adapter jar in one project and package it into the rar in another, with
slightly different names. I would definitely prefer that someone
figure out how to have multiple dependencies such as you ask for.
thanks
david jencks
On Se
Artifact just defines taglibs and that works from war I believe? I think all 3
use cases are covered (call a jelly tag, attain a goal, manipulate a property).
Cheers,
Brett
Quoting Felipe Leme <[EMAIL PROTECTED]>:
> Hi Carlos,
>
> On Wed, 1 Sep 2004 20:25:18 +0200, "Carlos Sanchez"
> <[EMAIL PR
Actually, I was referring to:
http://jira.codehaus.org/browse/MAVEN-1388
as for (3)
www.ibiblio.org/maven/maven/jars/maven-model-2.0-SNAPSHOT.jar
Like I said, this is pre-alpha code. We're not really ready to support it yet,
but if you want to take a stab - knock yourself out :)
Cheers,
Brett
Q
The following issue has been updated:
Updater: Archimedes Trajano (mailto:[EMAIL PROTECTED])
Date: Wed, 1 Sep 2004 7:16 PM
Comment:
Patched to fix checkstyle formatting issues. (Updated documentation as well)
Changes:
Attachment changed to checkstyle.patch
The following comment has been added to this issue:
Author: Arnaud HERITIER
Created: Wed, 1 Sep 2004 6:35 PM
Body:
+1 for me Felipe. The plugin mustn't fail if there's a problem with the warnings
report.
-
View th
This is a known issue.
On Wed, 1 Sep 2004 17:24:15 -0300, Felipe Leme <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> Here I am again without another weird issue (sorry if it was discussed before, but I
> didn't find it on Jira/eyebrowse).
>
> Is there a known limitation that a project can't have mor
The following comment has been added to this issue:
Author: Archimedes Trajano
Created: Wed, 1 Sep 2004 6:24 PM
Body:
Perhaps something is not being GCed, but you can increase the amount of RAM that can
be used by maven.
I run multiproject on about 40 projects with no problems as
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MPDOCBOOK-4
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/MPJAVADOC-42
Here is an overview of the issue:
-
Ke
The following comment has been added to this issue:
Author: Felipe Leme
Created: Wed, 1 Sep 2004 4:49 PM
Body:
It works for me (not sure what't the cygwin version though)...
-
View this comment:
http://jira.code
Hi all,
Here I am again without another weird issue (sorry if it was discussed before, but I
didn't find it on Jira/eyebrowse).
Is there a known limitation that a project can't have more than one dependency with
the same id but different types?
Before someone shouts 'use multi-project', let m
Hi Carlos,
On Wed, 1 Sep 2004 20:25:18 +0200, "Carlos Sanchez" <[EMAIL PROTECTED]> wrote:
> Not sure but I think that you have to load the plugin before you can use the
> taglib, as it happens with the plugin properties.
Yes, I think so.
> You can use attainGoal, maven:get,...
It worked when
The following comment has been added to this issue:
Author: Carlos Sanchez
Created: Wed, 1 Sep 2004 2:34 PM
Body:
Please add a comment with:
* an url where the project can be found.
* if you are one of its developers, an url where your name or email can be found
inside the proje
Hi,
Not sure but I think that you have to load the plugin before you can use the
taglib, as it happens with the plugin properties. You can use attainGoal,
maven:get,...
Regards
Carlos Sanchez
A Coruña, Spain
Oness Project
http://oness.sourceforge.net
> -Original Message-
> From: Feli
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MPRAR-1
Here is an overview of the issue:
-
Key: MP
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MAVENUPLOAD-202
Here is an overview of the issue:
-
Vincent,
I was already using a namespace, but looks like maven was not loading the plugin that
defined the taglib. If I called a goal from that plugin (using ) before
using the tag, it worked though. That might be some issue in my code though, as maven
executes all plugin.jellys and plugin.prop
On Wed, 1 Sep 2004 11:27:28 -0300, "Felipe Leme" <[EMAIL PROTECTED]> wrote:
> My undestanding is that the taglib scope is limited to the Jelly script that defined
> it. So, my question is: is it possible to 'export' that taglib? If so, how do I do
> it?
Actually, I partially solved the problem:
Hi Felipe,
You can. Check the existing maven-plugins. You'll need to use a namespace.
For example you can check the artifact plugin which provides tags used in
the war plugin.
-Vincent
> -Original Message-
> From: Felipe Leme [mailto:[EMAIL PROTECTED]
> Sent: mercredi 1 septembre 2004 1
Hi all,
Is it possible to use (inside a plugin or in maven.xml) a Jelly taglib defined
somewhere else?
For instance, let's say a have a plugin A below:
If I try to access taglibA from a plugin B, it doesn't work:
My undest
Some questions now that I've had a chance to poke around in JIRA and
CVS:
1) I'm assuming the JIRA issues referred to are the ones for the
"model" component:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&mode=hide&pid=10030&sorter/order=DESC&sorter/field=priority&resolutionIds=-1&
The following work log has been added to this issue:
Logged By: Felipe Leme
Created: Wed, 1 Sep 2004 6:30 AM
Time Logged: 30 minutes
Description:
Adapting the original patch to the current CVS code and creating a new patch.
Hello maveners
On our project we used to includes the sources files in our jars and ejbs files so the
developers can easily debug the program.
Now for various reasons we need to remove the sources from the artifact and put them
in separated archives (so a normal classes archive and a sources
ar
43 matches
Mail list logo
