dion2003/08/31 17:23:34
Modified:src/plugins-build/ear/xdocs changes.xml
Log:
Fix typo
Revision ChangesPath
1.7 +1 -1 maven/src/plugins-build/ear/xdocs/changes.xml
Index: changes.xml
dion2003/08/31 17:24:15
Modified:src/plugins-build/java plugin.properties
Log:
Comment on need to move properties
Revision ChangesPath
1.6 +1 -0 maven/src/plugins-build/java/plugin.properties
Index: plugin.properties
dion2003/08/31 17:24:50
Modified:src/plugins-build/multiproject project.xml
Log:
Add versions to project file
Revision ChangesPath
1.10 +15 -0 maven/src/plugins-build/multiproject/project.xml
Index: project.xml
dion2003/08/31 17:26:06
Modified:src/plugins-build project.xml
Log:
Remove unneeded ${basedir}
Revision ChangesPath
1.5 +4 -4 maven/src/plugins-build/project.xml
Index: project.xml
===
dion2003/08/31 17:31:49
Modified:xdocs/reference/developers releasing-plugins.xml
Log:
Update details to be more clear on whihch version tag
Revision ChangesPath
1.3 +18 -12maven/xdocs/reference/developers/releasing-plugins.xml
Index:
dion2003/08/31 17:34:40
Modified:src/java/org/apache/maven MavenUtils.java
Log:
Change POM interpolation from compiling as a script to evaluating as an expression.
This saves around 40M on bootstrapping.
Checkstyle fixes.
Revision ChangesPath
1.100 +72 -38
Hi,
After doing a little with the plugin manager on the weekend, I noticed (as I
suspected), that plugin upgrading (or downgrading via a dependency),
doesn't do what you might expect.
It seems it will always load both plugins, and I suspect it will call the
latest, even when using a dependency
brett 2003/08/31 18:06:32
Modified:src/java/org/apache/maven/plugin PluginManager.java
Log:
add new task
Revision ChangesPath
1.66 +3 -2 maven/src/java/org/apache/maven/plugin/PluginManager.java
Index: PluginManager.java
brett 2003/08/31 18:48:25
Modified:src/test/java/org/apache/maven/plugin PluginManagerTest.java
src/test/java/org/apache/maven/plugin/maven.home/plugins
maven-clean-plugin-1.1-SNAPSHOT.jar
Added: src/test/java/org/apache/maven/plugin
I'd prefer that maven die an ungainly death if it encountered two
plugins with the same identifying mark.
The identifying mark being the id (groupId:artifactid:type) (type =
plugin)
Is there some particular use case for allowing multiple plugins with
different versions confusing things?
As I
Is there some particular use case for allowing multiple plugins with
different versions confusing things?
Maybe if it comes installed with one version and you get a project with a
dependency on a newer one?
I think dying a horrible death is a great thing to do if more than one turn
up in the
The following comment has been added to this issue:
Author: dion gillard
Created: Sun, 31 Aug 2003 11:08 PM
Body:
Give me a typical use case
-
View the issue:
The following issue has been updated:
Updater: dion gillard (mailto:[EMAIL PROTECTED])
Date: Mon, 1 Sep 2003 12:39 AM
Changes:
Fix Version changed to 1.1
Fix Version changed from 1.0-rc1
The following comment has been added to this issue:
Author: dion gillard
Created: Mon, 1 Sep 2003 12:38 AM
Body:
From what I can tell, the main reason to use XPP3 was the memory leak.
I think there are bigger issues on that front:
- PluginManager caches plugins on a per project
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: 01 September 2003 05:43
To: 'Maven Developers List'
Subject: RE: plugin version upgrading/downgrading
[snip]
As I have mentioned before, we need to get a bit clearer about which
goals can have been touched
Hey Emannuelle,
what happens if the version is something like 1.3-SNAPSHOT?
I'm -1 on this change for the above reason, as it breaks existing
assumptions.
Anyone else have some ideas?
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
[EMAIL PROTECTED]
Last 500 lines of a clean bootstrap build of maven at 20030830-2200
[exec] java:jar-resources:
[exec] Copying 1 file to
/usr/local/builds/maven/src/maven/src/plugins-build/webserver/target/classes/plugin-resources
[exec] Copying 4 files to
Brett Porter [EMAIL PROTECTED] wrote on 01/09/2003 09:01:49 AM:
Hi,
After doing a little with the plugin manager on the weekend, I noticed
(as I
suspected), that plugin upgrading (or downgrading via a dependency),
doesn't do what you might expect.
Well, yes... it depends what u expect :-)
Last 500 lines of a clean bootstrap build of maven at 20030831-2200
[copy] Copying 83 files to
/usr/local/builds/maven/src/maven/bootstrap/install-phase1/plugins
[echo]
[echo] +--+
[echo] |
I see this as a set of 'helper' plugins or extensions to the existing
ones.
i.e. something that knows where the checkstyle output files are and knows
how to sort them and produce trending output.
ditto for pmd, activity, etc. etc.
It's definitely a plugin or a set of them, and not part of
Ben Walding [EMAIL PROTECTED] wrote on 01/09/2003 07:31:00 AM:
I missed discussion of the previous version unfortunately. And it isn't
listed on the main page at the maven-plugins.sf.net site - only in CVS.
Usually the major sticking point for our use of LGPL is if we have to
import
The following issue has been updated:
Updater: dion gillard (mailto:[EMAIL PROTECTED])
Date: Mon, 1 Sep 2003 12:55 AM
Comment:
Related to the use of XPP3. Moving to 1.1
Changes:
Fix Version changed to 1.1
Fix Version changed from 1.0-rc1
The following issue has been updated:
Updater: dion gillard (mailto:[EMAIL PROTECTED])
Date: Mon, 1 Sep 2003 12:57 AM
Comment:
Related to XPP3 parsing. Moved to 1.1.
Changes:
Fix Version changed to 1.1
Fix Version changed from 1.0-rc1
What about making the goal public when it has a description
element defined? I had reported a bug (dunno if it had been
fixed) where currently the maven -g displays null as the
description for non-public goals (i.e. those that have no
description). I believe it was implemented like this
Brett Porter wrote:
Is there some particular use case for allowing multiple plugins with
different versions confusing things?
Maybe if it comes installed with one version and you get a project with a
dependency on a newer one?
I think dying a horrible death is a great thing to do if more than
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-759
Here is an overview of the issue:
The following issue has been updated:
Updater: Joachim Bader (mailto:[EMAIL PROTECTED])
Date: Mon, 1 Sep 2003 1:04 AM
Changes:
Attachment changed to patch.diff
-
For a full history of the issue,
The following issue has been updated:
Updater: dion gillard (mailto:[EMAIL PROTECTED])
Date: Mon, 1 Sep 2003 1:09 AM
Comment:
Other than httpclient and dbcp this is done.
Changes:
Version changed to 1.1
Version changed from 1.0-rc1
The following issue has been updated:
Updater: dion gillard (mailto:[EMAIL PROTECTED])
Date: Mon, 1 Sep 2003 1:09 AM
Changes:
Version changed to 1.0-rc1
Version changed from 1.1
Fix Version changed to 1.1
Fix Version changed from
Message:
The following issue has been closed.
Resolver: dion gillard
Date: Mon, 1 Sep 2003 1:11 AM
Fixed previously
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-704
Here is an
dion2003/08/31 22:34:08
Modified:src/java/org/apache/maven MavenUtils.java
Log:
rename local variable to not hide outer one
Revision ChangesPath
1.101 +4 -4 maven/src/java/org/apache/maven/MavenUtils.java
Index: MavenUtils.java
The following comment has been added to this issue:
Author: dion gillard
Created: Mon, 1 Sep 2003 1:16 AM
Body:
I've attacked part of this problem:
a) Compilation of project.xml unnecessarily.
We need to do:
b) Make Plugin Manager load plugins once for all projects and reassign
dion2003/08/31 21:26:33
Modified:src/test/java/org/apache/maven/plugin PluginManagerTest.java
Log:
Add a deletePlugin method to call at the start and end of tests
Revision ChangesPath
1.9 +20 -0
dion2003/08/31 21:27:27
Added: src/plugins-build/cruisecontrol .cvsignore
Log:
Ignore target
Revision ChangesPath
1.1 maven/src/plugins-build/cruisecontrol/.cvsignore
Index: .cvsignore
So as a project builds, there should only be 1 plugin of a given id
loaded, but there may be multiple unpacked (contrary to your
statement).
Yep. Sorry, I was thinking that using dependencies didn't unpack it, but it
does.
What should really happen is every plugin you ever install should be
brett 2003/08/31 22:18:04
Modified:src/java/org/apache/maven/jelly/tags/maven
MakeRelativePathTag.java
Log:
must change both separators. Lets hope there aren't any bizarre ones out there.
Revision ChangesPath
1.4 +1 -1
dion2003/08/31 21:28:49
Added: src/plugins-build/scm .cvsignore
Log:
Ignore target
Revision ChangesPath
1.1 maven/src/plugins-build/scm/.cvsignore
Index: .cvsignore
===
target
dion2003/08/31 21:47:04
Modified:src/test/java/org/apache/maven/plugin PluginManagerTest.java
Log:
Woops...delete them from fakeHome
Revision ChangesPath
1.10 +3 -7
maven/src/test/java/org/apache/maven/plugin/PluginManagerTest.java
Index:
The following issue has been updated:
Updater: dion gillard (mailto:[EMAIL PROTECTED])
Date: Mon, 1 Sep 2003 2:01 AM
Changes:
Fix Version changed to 1.1
-
For a full history of the issue, see:
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: 01 September 2003 07:36
To: 'Maven Developers List'
Subject: RE: plugin version upgrading/downgrading
What about making the goal public when it has a description
element defined? I had reported a bug (dunno
dion2003/08/31 22:07:26
Modified:src/java/org/apache/maven/plugin PluginManager.java
Log:
Remove trailing space
Revision ChangesPath
1.67 +2 -2 maven/src/java/org/apache/maven/plugin/PluginManager.java
Index: PluginManager.java
dion2003/08/31 23:56:58
Modified:src/java/org/apache/maven MavenUtils.java
Log:
Remove local variable
Revision ChangesPath
1.102 +3 -4 maven/src/java/org/apache/maven/MavenUtils.java
Index: MavenUtils.java
dion2003/08/31 23:59:12
Modified:src/plugins-build/checkstyle/src/plugin-resources
turbine_checks.xml
Log:
PR: MAVEN-750
Obtained from: Jira
Submitted by: Anonymous
Revision ChangesPath
1.2 +1 -0
Message:
The following issue has been closed.
Resolver: dion gillard
Date: Mon, 1 Sep 2003 2:11 AM
Applied today
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-750
Here is an
dion2003/09/01 00:14:47
Added: src/plugins-build/checkstyle/announcements 2.0.ann
Log:
Prep for release
Revision ChangesPath
1.1 maven/src/plugins-build/checkstyle/announcements/2.0.ann
Index: 2.0.ann
Message:
The following issue has been closed.
Resolver: dion gillard
Date: Mon, 1 Sep 2003 2:28 AM
Applied today
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-700
Here is an
dion2003/09/01 00:20:42
maven/src/plugins-build/checkstyle/xdocs/current - New directory
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
dion2003/09/01 00:20:42
maven/src/plugins-build/checkstyle/xdocs/releases/v2.0 - New directory
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
dion2003/09/01 00:20:42
maven/src/plugins-build/checkstyle/xdocs/releases - New directory
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
dion2003/09/01 00:14:38
maven/src/plugins-build/checkstyle/announcements - New directory
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
dion2003/09/01 00:26:53
Modified:src/plugins-build/checkstyle/announcements 2.0.ann
Log:
*** keyword substitution change ***
Revision ChangesPath
1.2 +16 -16maven/src/plugins-build/checkstyle/announcements/2.0.ann
Index: 2.0.ann
dion2003/09/01 00:01:20
Modified:src/plugins-build/checkstyle/xdocs changes.xml
Log:
MAVEN 750
Revision ChangesPath
1.9 +3 -3 maven/src/plugins-build/checkstyle/xdocs/changes.xml
Index: changes.xml
dion2003/09/01 00:31:15
Modified:src/plugins-build/checkstyle/xdocs/current changes.xml
src/plugins-build/checkstyle project.xml
Log:
Continuing work
Revision ChangesPath
1.2 +3 -0 maven/src/plugins-build/checkstyle/xdocs/current/changes.xml
dion2003/09/01 00:31:50
Modified:src/plugins-build/checkstyle project.properties
Log:
Ensure site says released version
Revision ChangesPath
1.3 +1 -1 maven/src/plugins-build/checkstyle/project.properties
Index: project.properties
dion2003/09/01 00:25:17
Modified:src/plugins-build/checkstyle project.xml
Log:
Update for release
Revision ChangesPath
1.19 +2 -2 maven/src/plugins-build/checkstyle/project.xml
Index: project.xml
dion2003/09/01 00:34:12
Modified:src/plugins-build/word2html/xdocs/current changes.xml
Log:
Fix maven.xdoc.version
Revision ChangesPath
1.3 +1 -0 maven/src/plugins-build/word2html/xdocs/current/changes.xml
Index: changes.xml
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-760
Here is an overview of the issue:
Message:
The following issue has been reopened.
Reopener: dion gillard
Date: Mon, 1 Sep 2003 2:29 AM
Woops, meant to close 700
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-750
The following comment has been added to this issue:
Author: Joachim Bader
Created: Mon, 1 Sep 2003 1:19 AM
Body:
wrong issue name: add jar.bundle property for dependencies better is add
jar.include property for dependencies, sorry
Message:
The following issue has been reopened.
Reopener: dion gillard
Date: Sun, 31 Aug 2003 10:56 PM
I'd prefer we changed the javadoc on this one.
I'm -1 on the change
-
View the issue:
dion2003/09/01 00:36:49
Modified:src/plugins-build/word2html project.properties
Log:
Fix maven.xdoc.version
Revision ChangesPath
1.3 +1 -1 maven/src/plugins-build/word2html/project.properties
Index: project.properties
dion2003/09/01 00:44:43
Modified:src/plugins-build/multiproject/xdocs/current changes.xml
src/plugins-build/multiproject project.properties
Log:
Fix maven.xdoc.version
Revision ChangesPath
1.3 +1 -0
I think Ben suggested that too. That's probably a better idea, yes :)
What about introducing an attribute on the goal element?
Like public for example?
goal name=cactus:whatever public=true
[...]
By default, a goal would be private.
-Vincent
The following comment has been added to this issue:
Author: Piotr Maj
Created: Mon, 1 Sep 2003 5:05 AM
Body:
I use fresh CVS version of Maven and I think there is still something wrong with
checkstyle plugin.
I've got two classes under src/java:
1) SchemaException extends
Hey Emannuelle,
My name is Emmanuel!!!
what happens if the version is something like 1.3-SNAPSHOT?
I'm -1 on this change for the above reason, as it breaks existing
assumptions.
I think that current version is necessary in jar name for project that work
on several version/branch. When You
Usually the major sticking point for our use of LGPL is if we have to
import code (i.e. import com.* statements). Since neither of the
findbugs plugins do this, I'd wager that it being lgpl isn't an issue.
If it is, then we're going to have to take yet another look at plugins -
dion2003/09/01 06:31:18
Modified:src/java/org/apache/maven/project Project.java
Log:
Directories should be resolved before initialising the driver, as it may rely on the
paths begin absolute
Revision ChangesPath
1.89 +3 -3
Emmanuel Venisse [EMAIL PROTECTED] wrote on 01/09/2003 07:43:41 PM:
Hey Emannuelle,
My name is Emmanuel!!!
Woops, sorry about that. I thought I had it wrong as I typed it.
what happens if the version is something like 1.3-SNAPSHOT?
I'm -1 on this change for the above reason, as it
Please upload Javassist 2.6. The distro is available at:
http://prdownloads.sourceforge.net/jboss/javassist-2.6.zip?download
2.6 is a follow on to Javassist 2.5.1, which is already in the Maven repository.
Thanks!
--
Howard M. Lewis Ship
Creator, Tapestry: Java Web Components
- Original Message -
From: [EMAIL PROTECTED]
To: Maven Developers List [EMAIL PROTECTED]
Sent: Monday, September 01, 2003 3:22 PM
Subject: Re: cvs commit: maven/src/java/org/apache/maven/jelly/tags/maven
SnapshotSignature.java
Emmanuel Venisse [EMAIL PROTECTED] wrote on 01/09/2003
Could you post the demand on JIRA?
http://maven.apache.org/repository-upload.html
Thanks
Emmanuel
- Original Message -
From: Howard M. Lewis Ship [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, September 01, 2003 4:20 PM
Subject: [UPLOAD] Javassist 2.6
Please upload Javassist
The following issue has been updated:
Updater: dion gillard (mailto:[EMAIL PROTECTED])
Date: Mon, 1 Sep 2003 11:05 AM
Changes:
Fix Version changed to 1.1
Fix Version changed from 1.0-final
On Mon, 2003-09-01 at 11:41, Emmanuel Venisse wrote:
- Original Message -
From: [EMAIL PROTECTED]
To: Maven Developers List [EMAIL PROTECTED]
Sent: Monday, September 01, 2003 3:22 PM
Subject: Re: cvs commit: maven/src/java/org/apache/maven/jelly/tags/maven
SnapshotSignature.java
evenisse2003/09/01 09:09:21
Modified:src/java/org/apache/maven/jelly/tags/maven
SnapshotSignature.java
Log:
- Rollback my previous change.
- Update javadoc
Revision ChangesPath
1.11 +4 -5
The following issue has been updated:
Updater: Martin Poeschl (mailto:[EMAIL PROTECTED])
Date: Mon, 1 Sep 2003 4:15 PM
Comment:
patch to fix the typo
Changes:
Attachment changed to jdepend.jsl.patch
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-762
Here is an overview of the issue:
dion2003/09/01 15:21:52
Modified:src/plugins-build/jdepend/src/plugin-resources jdepend.jsl
Log:
Fix typo thanks to Martin Poeschl
Revision ChangesPath
1.6 +1 -1 maven/src/plugins-build/jdepend/src/plugin-resources/jdepend.jsl
Index: jdepend.jsl
Message:
The following issue has been closed.
Resolver: dion gillard
Date: Mon, 1 Sep 2003 5:33 PM
Fix typo.
Thanks, applied
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-762
Here
78 matches
Mail list logo
