felipeal2004/09/05 21:26:10
Modified:artifact/src/main/org/apache/maven/artifact/deployer
DefaultArtifactDeployer.java ArtifactDeployer.java
Log:
fixed mispelled comments
Revision ChangesPath
1.23 +3 -3
maven-plugins/artifact/src/main/or
The following issue has been updated:
Updater: Archimedes Trajano (mailto:[EMAIL PROTECTED])
Date: Sun, 5 Sep 2004 10:43 PM
Comment:
zipped template to extract to plugin-resources
Changes:
Attachment changed to tapestry-20040905.zip
It still is AFAIK. It's in the maven.bat and the forehead.conf.
On Mon, 6 Sep 2004 11:19:41 +1000, Brett Porter <[EMAIL PROTECTED]> wrote:
> Is that still set by the maven startup script? I didn't think it was, because we
> had tried to get Maven working with other JVMs such as Kaffe.
>
> - Bre
Is that still set by the maven startup script? I didn't think it was, because we
had tried to get Maven working with other JVMs such as Kaffe.
- Brett
Quoting [EMAIL PROTECTED]:
> dion2004/09/05 17:57:59
>
> Modified:jellydoc project.properties
> Log:
> Rely on tools.jar from
> Hmm, I think I wasn't clear in my previous message: the reason I'd like
> to create a branch is that I can work in the issue without messing with
> the main branch (in this case, the 1_0_BRANCH) while all the changes are
> not ready. Once I finish the changes, I would merge them back to the
> mai
dion2004/09/05 17:57:59
Modified:jellydoc project.properties
Log:
Rely on tools.jar from Maven
Revision ChangesPath
1.9 +2 -0 maven-plugins/jellydoc/project.properties
Index: project.properties
Brett,
On Sun, 2004-09-05 at 21:03, Brett Porter wrote:
> 1) branching/versioning should be on a per-plugin level, if needed
> 2) changes should be backwards compatible at this stage, indicating that a
> branch may not be needed.
Hmm, I think I wasn't clear in my previous message: the reason I'd
I'll can reply in more detail when I get a chance if needed, but I don't think
this is the right approach.
Two reasons:
1) branching/versioning should be on a per-plugin level, if needed
2) changes should be backwards compatible at this stage, indicating that a
branch may not be needed.
IIRC this
Hi all,
I'd like to fix issue MPJAVA-8
(http://jira.codehaus.org/browse/MPJAVA-8) but in order to do so I will
need to change many plugins and hence the fix itself will take a while
(as I will have to write new test cases for each affected plugin).
So, I was thinking about working on a separate b
The following comment has been added to this issue:
Author: Malachi de AElfweald
Created: Sun, 5 Sep 2004 7:58 PM
Body:
Sure, I can try it. I tried to figure out how to download it (via maven
plugin:download), but it didn't like the version number. Go ahead and email it to me.
--
The following comment has been added to this issue:
Author: Archimedes Trajano
Created: Sun, 5 Sep 2004 7:31 PM
Body:
patch file added to MPJAVA-22 that will fix this problem.
-
View this comment:
http://jira.cod
The following issue has been updated:
Updater: Archimedes Trajano (mailto:[EMAIL PROTECTED])
Date: Sun, 5 Sep 2004 7:30 PM
Comment:
Patch file to make maven.compile.source property in plugin.jelly match the
documentation. Added contributor data.
Changes:
Attachmen
The following comment has been added to this issue:
Author: Archimedes Trajano
Created: Sun, 5 Sep 2004 7:25 PM
Body:
related to MPJAVA-22.
-
View this comment:
http://jira.codehaus.org/browse/MAVEN-1437?page=com
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MAVEN-1437
Here is an overview of the issue:
-
Key:
carlos 2004/09/05 14:17:50
Modified:aspectj plugin.jelly
Log:
Removed TODOs
Revision ChangesPath
1.22 +0 -4 maven-plugins/aspectj/plugin.jelly
Index: plugin.jelly
===
RCS file: /home/cvs/
felipeal2004/09/05 14:00:34
Modified:javadoc/src/main/org/apache/maven/javadoc
JavadocWarningsTextToXml.java
javadoc/src/test/org/apache/maven/javadoc
JavadocWarningsTextToXmlTest.java
Log:
applied 'maven jalopy' to fix m
felipeal2004/09/05 13:37:56
Modified:.project.xml
Log:
added myself as developer
Revision ChangesPath
1.24 +11 -0 maven-plugins/project.xml
Index: project.xml
===
RCS file: /home/cvs
Message:
The following issue has been closed.
Resolver: Felipe Leme
Date: Sun, 5 Sep 2004 4:07 PM
Fixed, adding 2 new properties: maven.aspectj.noweave and maven.aspectj.lint.
-
View the issue:
http://jira.codehau
felipeal2004/09/05 13:00:25
Modified:aspectj plugin.jelly plugin.properties project.xml
aspectj/xdocs changes.xml properties.xml
Log:
fix for MPASPECTJ-13: new properties maven.aspectj.noweave and maven.aspectj.lint
Revision ChangesPath
1.21 +2 -0
felipeal2004/09/05 12:56:57
Modified:javadoc/xdocs changes.xml
Log:
added entry for MPJAVADOC-42
Revision ChangesPath
1.51 +1 -0 maven-plugins/javadoc/xdocs/changes.xml
Index: changes.xml
===
felipeal2004/09/05 12:56:37
Modified:javadoc project.xml
Log:
added myself as developer
Revision ChangesPath
1.47 +11 -0 maven-plugins/javadoc/project.xml
Index: project.xml
===
RCS file: /
The following comment has been added to this issue:
Author: Arnaud HERITIER
Created: Sun, 5 Sep 2004 2:55 PM
Body:
Can you try to clean your plugin cache directory ?
You have several releases registred for each plugin and it is anormal.
-
The following comment has been added to this issue:
Author: Chris Rose
Created: Sun, 5 Sep 2004 2:48 PM
Body:
With apologies, because the bug description is pretty poor.
Basically, I'm running maven in the mevenide for Eclipse, and i'm using the genapp
plugin (I'm led to understa
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MAVEN-1436
Here is an overview of the issue:
-
Key:
24 matches
Mail list logo
