Re: Opening up Maven CVS a bit...
On Sunday 04 April 2004 14:01, Jason van Zyl wrote: > We are trying to do the exact opposite. Ok, fair enough. Q1; Do you have any pointers on how to publish plug-ins? Q2; But then you will require that the user download the 500 plugins that you end up using, no? Cheers Niclas -- +-//---+ | http://www.bali.ac | | http://niclas.hedhman.org | +--//--+ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Opening up Maven CVS a bit...
On Sun, 2004-04-04 at 00:23, Niclas Hedhman wrote: > Hi, > > I would like the Maven community to discuss a solution where other Apache > projects are given a 'partitition' in Maven Plugins to create their own > solutions to be automatically included in Maven distros. We are trying to do the exact opposite. We don't want them hosted under Maven. If you have a plugin for project Foo, then develop the plugin in Foo land. This is what Cactus does, this is what Torque does so there is nothing stopping you from doing it too. You can develop your plugins wherever you like and it's simple for users to download them. We will ultimately keep what we consider to be core but the rest of them will eventually be flushed out to places where those interested in them can develop them. We already have too many plugins that aren't properly taken care of. > It wouldn't be harder than; > > for PROJECT in `cat projectsfile` ; do > if [ -d /home/cvs/maven-plugins/$PROJECT ] ; then > echo "$PROJECT is already in maven-plugins. Resolve manually!" > else > mkdir /home/cvs/maven-plugins/$PROJECT > chmod g+w /home/cvs/maven-plugins/$PROJECT > chgrp $PROJECT /home/cvs/maven-plugins/$PROJECT > fi > done > > > Cheers > Niclas -- jvz. Jason van Zyl [EMAIL PROTECTED] http://maven.apache.org happiness is like a butterfly: the more you chase it, the more it will elude you, but if you turn your attention to other things, it will come and sit softly on your shoulder ... -- Thoreau - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Opening up Maven CVS a bit...
Hi, I would like the Maven community to discuss a solution where other Apache projects are given a 'partitition' in Maven Plugins to create their own solutions to be automatically included in Maven distros. It wouldn't be harder than; for PROJECT in `cat projectsfile` ; do if [ -d /home/cvs/maven-plugins/$PROJECT ] ; then echo "$PROJECT is already in maven-plugins. Resolve manually!" else mkdir /home/cvs/maven-plugins/$PROJECT chmod g+w /home/cvs/maven-plugins/$PROJECT chgrp $PROJECT /home/cvs/maven-plugins/$PROJECT fi done Cheers Niclas -- +-//---+ | http://www.bali.ac | | http://niclas.hedhman.org | +--//--+ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/gump plugin.jelly
brett 2004/04/03 20:14:54
Modified:jellydoc plugin.jelly project.xml
gump plugin.jelly
Log:
remove use of target, replace with properties
Revision ChangesPath
1.18 +1 -1 maven-plugins/jellydoc/plugin.jelly
Index: plugin.jelly
===
RCS file: /home/cvs/maven-plugins/jellydoc/plugin.jelly,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -r1.17 -r1.18
--- plugin.jelly 4 Mar 2004 18:36:13 - 1.17
+++ plugin.jelly 4 Apr 2004 04:14:54 - 1.18
@@ -65,7 +65,7 @@
Generating jellydoc for packages ${maven.jellydoc.packages}
-
+
Source directory is ${pom.build.sourceDirectory}
1.27 +1 -1 maven-plugins/jellydoc/project.xml
Index: project.xml
===
RCS file: /home/cvs/maven-plugins/jellydoc/project.xml,v
retrieving revision 1.26
retrieving revision 1.27
diff -u -r1.26 -r1.27
--- project.xml 7 Mar 2004 01:06:31 - 1.26
+++ project.xml 4 Apr 2004 04:14:54 - 1.27
@@ -23,7 +23,7 @@
3
maven-jellydoc-plugin
Maven JellyDoc Plug-in
- 1.2
+ 1.3-SNAPSHOT
jakarta
1.5 +7 -3 maven-plugins/gump/plugin.jelly
Index: plugin.jelly
===
RCS file: /home/cvs/maven-plugins/gump/plugin.jelly,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- plugin.jelly 4 Mar 2004 18:13:38 - 1.4
+++ plugin.jelly 4 Apr 2004 04:14:54 - 1.5
@@ -21,6 +21,7 @@
@@ -96,12 +97,15 @@
-
-
+
+
+
+
${scmTokens[5]}
-
+
+
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/jdeveloper plugin.jelly project.xml
brett 2004/04/03 20:01:36
Modified:jdeveloper plugin.jelly project.xml
Log:
remove use of target, replace with properties
Revision ChangesPath
1.8 +8 -5 maven-plugins/jdeveloper/plugin.jelly
Index: plugin.jelly
===
RCS file: /home/cvs/maven-plugins/jdeveloper/plugin.jelly,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- plugin.jelly 4 Mar 2004 18:36:12 - 1.7
+++ plugin.jelly 4 Apr 2004 04:01:36 - 1.8
@@ -20,6 +20,7 @@
@@ -37,6 +38,8 @@
+
+
http://xmlns.oracle.com/jdeveloper/903/jproject"; encoding="Cp1252">
@@ -45,7 +48,7 @@
${pom.package}
-
+
${maven.jdeveloper.workspace}-${maven.war.final.name}
${maven.jdeveloper.workspace}-${ear.bundle.war.context-root}
@@ -181,7 +184,7 @@
32
false
-
+
-protected
@@ -229,7 +232,7 @@
-
+
@@ -356,8 +359,8 @@
-
-
+
+
1.27 +1 -1 maven-plugins/jdeveloper/project.xml
Index: project.xml
===
RCS file: /home/cvs/maven-plugins/jdeveloper/project.xml,v
retrieving revision 1.26
retrieving revision 1.27
diff -u -r1.26 -r1.27
--- project.xml 10 Mar 2004 14:08:52 - 1.26
+++ project.xml 4 Apr 2004 04:01:36 - 1.27
@@ -23,7 +23,7 @@
3
maven-jdeveloper-plugin
Maven JDeveloper Plug-in
- 1.3
+ 1.4-SNAPSHOT
2002
A plugin to generate various files for Oracle's JDeveloper IDE and
ease the use of Maven within that environment
JDeveloper Plugin for Maven
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/faq maven.xml project.xml
brett 2004/04/03 19:55:48 Modified:faq maven.xml project.xml Log: remove use of target, replace with properties Revision ChangesPath 1.3 +2 -2 maven-plugins/faq/maven.xml Index: maven.xml === RCS file: /home/cvs/maven-plugins/faq/maven.xml,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- maven.xml 4 Mar 2004 18:05:31 - 1.2 +++ maven.xml 4 Apr 2004 03:55:48 - 1.3 @@ -18,8 +18,8 @@ - - + + 1.26 +1 -1 maven-plugins/faq/project.xml Index: project.xml === RCS file: /home/cvs/maven-plugins/faq/project.xml,v retrieving revision 1.25 retrieving revision 1.26 diff -u -r1.25 -r1.26 --- project.xml 10 Mar 2004 11:30:43 - 1.25 +++ project.xml 4 Apr 2004 03:55:48 - 1.26 @@ -23,7 +23,7 @@ 3 maven-faq-plugin Maven FAQ Plug-in - 1.2 + 1.3-SNAPSHOT jakarta - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MAVEN-1219) Goals from plugin dependencies fail if the plugin is installed as part of the build process
The following comment has been added to this issue:
Author: Chad Brandon
Created: Sat, 3 Apr 2004 11:01 PM
Body:
On yeah and one more thing - as part of the plugin:install, I perform a postGoal step
which does copy it to the local repository (like you were saying I should do)
-
View this comment:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1219&page=comments#action_18150
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1219
Here is an overview of the issue:
-
Key: MAVEN-1219
Summary: Goals from plugin dependencies fail if the plugin is installed as part of
the build process
Type: Bug
Status: Unassigned
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven
Fix Fors:
1.0-rc3
Versions:
1.0-rc3
Assignee:
Reporter: Chad Brandon
Created: Sat, 3 Apr 2004 10:30 PM
Updated: Sat, 3 Apr 2004 11:01 PM
Environment: Windows XP, JDK 1.4.2_03
Description:
I have a project consisting of multiple subprojects. One of these subprojects
includes a plugin which is built and installed via "plugin:install" during my project
build. A goal is then used from this previously installed plugin to build the rest of
the project's subprojects (in other words other subprojects have a dependency on this
plugin which is installed during the build process).
Using maven-rc1 this used to be no problem, but as of yesterday (I checked out and
built MAVEN-1_0_Branch) using rc3 this fails. If the plugin doesn't already exist in
the ${maven.home}/plugins directory things work fine (if I delete the plugin out
before the build starts), the plugin is installed and other subprojects needing to use
goal(s) from this plugin find it and the build completes successfully. But if the
plugin already exists in ${maven.home}/plugins, I'll get something like below telling
me it can't parse the project.xml, when it fact that file does exist, or I sometimes
get a message telling me the plugin.jelly from that plugin can't be found:
BUILD FAILED
File.. file:/H:/Documents and
Settings/Administrator/.maven/plugins/maven-multiproject-plugin-1.2/plugin.jelly
Element... maven:reactor
Line.. 202
Column 9
Unable to obtain goal [multiproject:install-callback] --
file:/I:/java/eclipse/andromda-all/metafacades/uml/maven.xml:17
:42: Error parsing project.xml 'H:\Documents and
Settings\Administrator\.maven\plugins\maven-andromda-plugi
n-3.0-SNAPSHOT\project.xml'
Total time: 23 seconds
-
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/examples/plugin-script maven.xml
brett 2004/04/03 19:50:06 Modified:examples/plugin-script maven.xml Log: remove use of target, replace with maven.build.dir Revision ChangesPath 1.3 +2 -2 maven-plugins/examples/plugin-script/maven.xml Index: maven.xml === RCS file: /home/cvs/maven-plugins/examples/plugin-script/maven.xml,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- maven.xml 4 Mar 2004 18:05:27 - 1.2 +++ maven.xml 4 Apr 2004 03:50:06 - 1.3 @@ -19,7 +19,7 @@ - + @@ -66,4 +66,4 @@ - \ No newline at end of file + - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MAVEN-1219) Goals from plugin dependencies fail if the plugin is installed as part of the build process
The following comment has been added to this issue:
Author: Chad Brandon
Created: Sat, 3 Apr 2004 10:59 PM
Body:
I never moved to rc2 because of the fact that any plugin that was installed to the
repository during the build process (one that was marked as a dependency in my
project.xml) the goals weren't found and the build failed. I filled a bug on this and
you fixed it a week or so ago. So I figured I would try out the latest rc3 build and
now I'm running into this error.
Our plugin is part of our over all project and basically this plugin is one of the
first submodules installed into the local repository using plugin:install. It is then
used to build the rest of the project (other modules have it marked as a plugin
dependency). Our project builds itself (similar to Maven). It would be nice to not
have to install it first into the remote repository as a seperate step. Why wouldn't
you expect this to work?
The strange thing is, that it does work if the plugin is not in the
$MAVEN_HOME/plugins directory, but when its there (any subsequent build after the
first), I get these build failures telling me it can't either parse the project.xml or
the plugin.jelly of the plugin.
-
View this comment:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1219&page=comments#action_18149
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1219
Here is an overview of the issue:
-
Key: MAVEN-1219
Summary: Goals from plugin dependencies fail if the plugin is installed as part of
the build process
Type: Bug
Status: Unassigned
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven
Fix Fors:
1.0-rc3
Versions:
1.0-rc3
Assignee:
Reporter: Chad Brandon
Created: Sat, 3 Apr 2004 10:30 PM
Updated: Sat, 3 Apr 2004 10:59 PM
Environment: Windows XP, JDK 1.4.2_03
Description:
I have a project consisting of multiple subprojects. One of these subprojects
includes a plugin which is built and installed via "plugin:install" during my project
build. A goal is then used from this previously installed plugin to build the rest of
the project's subprojects (in other words other subprojects have a dependency on this
plugin which is installed during the build process).
Using maven-rc1 this used to be no problem, but as of yesterday (I checked out and
built MAVEN-1_0_Branch) using rc3 this fails. If the plugin doesn't already exist in
the ${maven.home}/plugins directory things work fine (if I delete the plugin out
before the build starts), the plugin is installed and other subprojects needing to use
goal(s) from this plugin find it and the build completes successfully. But if the
plugin already exists in ${maven.home}/plugins, I'll get something like below telling
me it can't parse the project.xml, when it fact that file does exist, or I sometimes
get a message telling me the plugin.jelly from that plugin can't be found:
BUILD FAILED
File.. file:/H:/Documents and
Settings/Administrator/.maven/plugins/maven-multiproject-plugin-1.2/plugin.jelly
Element... maven:reactor
Line.. 202
Column 9
Unable to obtain goal [multiproject:install-callback] --
file:/I:/java/eclipse/andromda-all/metafacades/uml/maven.xml:17
:42: Error parsing project.xml 'H:\Documents and
Settings\Administrator\.maven\plugins\maven-andromda-plugi
n-3.0-SNAPSHOT\project.xml'
Total time: 23 seconds
-
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/jdee plugin.jelly project.xml
brett 2004/04/03 19:38:03
Modified:jdee plugin.jelly project.xml
Log:
remove use of target, replace with maven.build.dir
Revision ChangesPath
1.7 +7 -4 maven-plugins/jdee/plugin.jelly
Index: plugin.jelly
===
RCS file: /home/cvs/maven-plugins/jdee/plugin.jelly,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- plugin.jelly 4 Mar 2004 18:36:01 - 1.6
+++ plugin.jelly 4 Apr 2004 03:38:03 - 1.7
@@ -51,11 +51,14 @@
(quote (jde-sourcepath (quote ("./${srcDir}"
- (quote (jde-compile-option-directory "./target/classes"))
- (quote (jde-javadoc-gen-destination-directory "./target/docs/apidocs"))
+
+
+
+ (quote (jde-compile-option-directory "./${mavenBuildDest}"))
+ (quote (jde-javadoc-gen-destination-directory "./${mavenDocsDest}/apidocs"))
(quote (jde-project-file-name "${projectFile}"))
(quote (jde-javadoc-gen-window-title "${pom.name} - ${pom.organization}
(${pom.inceptionYear})"))
- (quote (jde-import-excluded-packages (quote ("target.*"
+ (quote (jde-import-excluded-packages (quote ("${mavenBuildDir}.*"
@@ -63,7 +66,7 @@
(quote (jde-run-application-class "${mainClass}"))
-(quote (jde-global-classpath (quote ("./target/classes"
+(quote (jde-global-classpath (quote ("./${mavenBuildDest}"
"./${srcDir}"
1.11 +1 -1 maven-plugins/jdee/project.xml
Index: project.xml
===
RCS file: /home/cvs/maven-plugins/jdee/project.xml,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- project.xml 10 Mar 2004 12:03:50 - 1.10
+++ project.xml 4 Apr 2004 03:38:03 - 1.11
@@ -23,7 +23,7 @@
3
maven-jdee-plugin
Maven JDEE Plug-in
- 1.0
+ 1.1-SNAPSHOT
A plugin to create a project file to be used within the
[jira] Updated: (MAVEN-1219) Goals from plugin dependencies fail if the plugin is installed as part of the build process
The following issue has been updated:
Updater: Brett Porter (mailto:[EMAIL PROTECTED])
Date: Sat, 3 Apr 2004 10:46 PM
Changes:
Fix Version changed to 1.0-rc3
-
For a full history of the issue, see:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1219&page=history
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1219
Here is an overview of the issue:
-
Key: MAVEN-1219
Summary: Goals from plugin dependencies fail if the plugin is installed as part of
the build process
Type: Bug
Status: Unassigned
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven
Fix Fors:
1.0-rc3
Versions:
1.0-rc3
Assignee:
Reporter: Chad Brandon
Created: Sat, 3 Apr 2004 10:30 PM
Updated: Sat, 3 Apr 2004 10:46 PM
Environment: Windows XP, JDK 1.4.2_03
Description:
I have a project consisting of multiple subprojects. One of these subprojects
includes a plugin which is built and installed via "plugin:install" during my project
build. A goal is then used from this previously installed plugin to build the rest of
the project's subprojects (in other words other subprojects have a dependency on this
plugin which is installed during the build process).
Using maven-rc1 this used to be no problem, but as of yesterday (I checked out and
built MAVEN-1_0_Branch) using rc3 this fails. If the plugin doesn't already exist in
the ${maven.home}/plugins directory things work fine (if I delete the plugin out
before the build starts), the plugin is installed and other subprojects needing to use
goal(s) from this plugin find it and the build completes successfully. But if the
plugin already exists in ${maven.home}/plugins, I'll get something like below telling
me it can't parse the project.xml, when it fact that file does exist, or I sometimes
get a message telling me the plugin.jelly from that plugin can't be found:
BUILD FAILED
File.. file:/H:/Documents and
Settings/Administrator/.maven/plugins/maven-multiproject-plugin-1.2/plugin.jelly
Element... maven:reactor
Line.. 202
Column 9
Unable to obtain goal [multiproject:install-callback] --
file:/I:/java/eclipse/andromda-all/metafacades/uml/maven.xml:17
:42: Error parsing project.xml 'H:\Documents and
Settings\Administrator\.maven\plugins\maven-andromda-plugi
n-3.0-SNAPSHOT\project.xml'
Total time: 23 seconds
-
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MAVEN-1219) Goals from plugin dependencies fail if the plugin is installed as part of the build process
The following comment has been added to this issue:
Author: Brett Porter
Created: Sat, 3 Apr 2004 10:44 PM
Body:
I'm somewhat surprised this could have ever worked, and a bit confused as to what is
actually happening. What is the behaviour under RC2? Some improvements to the cache
happened on CVS since, but I would think it was the plugin loading changes in RC2 that
changed the behaviour.
plugin installation is not seamless and I would recommend using plugin:install as part
of a build process. What I think you want is to build the plugin, copy it to the
repository, the load it via a plugin dependency? Unfortunately this is not what
plugin:install does at present.
-
View this comment:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1219&page=comments#action_18148
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1219
Here is an overview of the issue:
-
Key: MAVEN-1219
Summary: Goals from plugin dependencies fail if the plugin is installed as part of
the build process
Type: Bug
Status: Unassigned
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven
Versions:
1.0-rc3
Assignee:
Reporter: Chad Brandon
Created: Sat, 3 Apr 2004 10:30 PM
Updated: Sat, 3 Apr 2004 10:44 PM
Environment: Windows XP, JDK 1.4.2_03
Description:
I have a project consisting of multiple subprojects. One of these subprojects
includes a plugin which is built and installed via "plugin:install" during my project
build. A goal is then used from this previously installed plugin to build the rest of
the project's subprojects (in other words other subprojects have a dependency on this
plugin which is installed during the build process).
Using maven-rc1 this used to be no problem, but as of yesterday (I checked out and
built MAVEN-1_0_Branch) using rc3 this fails. If the plugin doesn't already exist in
the ${maven.home}/plugins directory things work fine (if I delete the plugin out
before the build starts), the plugin is installed and other subprojects needing to use
goal(s) from this plugin find it and the build completes successfully. But if the
plugin already exists in ${maven.home}/plugins, I'll get something like below telling
me it can't parse the project.xml, when it fact that file does exist, or I sometimes
get a message telling me the plugin.jelly from that plugin can't be found:
BUILD FAILED
File.. file:/H:/Documents and
Settings/Administrator/.maven/plugins/maven-multiproject-plugin-1.2/plugin.jelly
Element... maven:reactor
Line.. 202
Column 9
Unable to obtain goal [multiproject:install-callback] --
file:/I:/java/eclipse/andromda-all/metafacades/uml/maven.xml:17
:42: Error parsing project.xml 'H:\Documents and
Settings\Administrator\.maven\plugins\maven-andromda-plugi
n-3.0-SNAPSHOT\project.xml'
Total time: 23 seconds
-
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/jboss/sample maven.xml project.properties
brett 2004/04/03 19:30:34
Modified:jbossproject.xml
jboss/sample maven.xml project.properties
Log:
remove use of target, replace with maven.build.dir
Revision ChangesPath
1.23 +1 -1 maven-plugins/jboss/project.xml
Index: project.xml
===
RCS file: /home/cvs/maven-plugins/jboss/project.xml,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -r1.22 -r1.23
--- project.xml 10 Mar 2004 12:10:27 - 1.22
+++ project.xml 4 Apr 2004 03:30:34 - 1.23
@@ -23,7 +23,7 @@
3
maven-jboss-plugin
Maven JBoss Plug-in
- 1.4
+ 1.5-SNAPSHOT
Plugin for JBoss.
JBoss plugin
http://maven.apache.org/reference/plugins/jboss/
1.4 +3 -3 maven-plugins/jboss/sample/maven.xml
Index: maven.xml
===
RCS file: /home/cvs/maven-plugins/jboss/sample/maven.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- maven.xml 4 Mar 2004 18:36:00 - 1.3
+++ maven.xml 4 Apr 2004 03:30:34 - 1.4
@@ -23,13 +23,13 @@
-
+
-
+
-
+
1.3 +3 -3 maven-plugins/jboss/sample/project.properties
Index: project.properties
===
RCS file: /home/cvs/maven-plugins/jboss/sample/project.properties,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- project.properties4 Mar 2004 18:36:00 - 1.2
+++ project.properties4 Apr 2004 03:30:34 - 1.3
@@ -15,9 +15,9 @@
# ---
maven.jboss.conf.name = my
-maven.jboss.appconf.dir = target/appconf
-maven.jboss.conf.dir = target/jboss/conf
-maven.jboss.deploy.dir = target/jboss/deploy
+maven.jboss.appconf.dir = ${maven.build.dir}/appconf
+maven.jboss.conf.dir = ${maven.build.dir}/jboss/conf
+maven.jboss.deploy.dir = ${maven.build.dir}/jboss/deploy
env.name = development
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-plugins/html2xdoc/src/test/org/apache/maven/html2xdoc codeinpara.xml comment.xml h1h2.xml link.xml linkInHeading.xml missingParaBug.xml output1.xml
brett 2004/04/03 19:23:50 Modified:html2xdoc project.xml html2xdoc/src/test/org/apache/maven/html2xdoc codeinpara.xml comment.xml h1h2.xml link.xml linkInHeading.xml missingParaBug.xml output1.xml Removed: html2xdoc maven.xml Log: re-enable unit tests (must remove license from test data files as they must match the generated copy) Revision ChangesPath 1.25 +16 -0 maven-plugins/html2xdoc/project.xml Index: project.xml === RCS file: /home/cvs/maven-plugins/html2xdoc/project.xml,v retrieving revision 1.24 retrieving revision 1.25 diff -u -r1.24 -r1.25 --- project.xml 28 Mar 2004 22:00:54 - 1.24 +++ project.xml 4 Apr 2004 03:23:50 - 1.25 @@ -110,4 +110,20 @@ MAVEN_HTML2XDOC_1_2 + + + +**/Test*.java + + + + src/test + +**/*.xml +**/*.html + + + + + 1.3 +0 -17 maven-plugins/html2xdoc/src/test/org/apache/maven/html2xdoc/codeinpara.xml Index: codeinpara.xml === RCS file: /home/cvs/maven-plugins/html2xdoc/src/test/org/apache/maven/html2xdoc/codeinpara.xml,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- codeinpara.xml4 Mar 2004 18:13:56 - 1.2 +++ codeinpara.xml4 Apr 2004 03:23:50 - 1.3 @@ -1,20 +1,3 @@ - A title 1.3 +0 -17 maven-plugins/html2xdoc/src/test/org/apache/maven/html2xdoc/comment.xml Index: comment.xml === RCS file: /home/cvs/maven-plugins/html2xdoc/src/test/org/apache/maven/html2xdoc/comment.xml,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- comment.xml 4 Mar 2004 18:13:56 - 1.2 +++ comment.xml 4 Apr 2004 03:23:50 - 1.3 @@ -1,20 +1,3 @@ - A title 1.3 +0 -17 maven-plugins/html2xdoc/src/test/org/apache/maven/html2xdoc/h1h2.xml Index: h1h2.xml === RCS file: /home/cvs/maven-plugins/html2xdoc/src/test/org/apache/maven/html2xdoc/h1h2.xml,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- h1h2.xml 4 Mar 2004 18:13:56 - 1.2 +++ h1h2.xml 4 Apr 2004 03:23:50 - 1.3 @@ -1,20 +1,3 @@ - A title 1.3 +0 -17 maven-plugins/html2xdoc/src/test/org/apache/maven/html2xdoc/link.xml Index: link.xml === RCS file: /home/cvs/maven-plugins/html2xdoc/src/test/org/apache/maven/html2xdoc/link.xml,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- link.xml 4 Mar 2004 18:13:56 - 1.2 +++ link.xml 4 Apr 2004 03:23:50 - 1.3 @@ -1,20 +1,3 @@ - A title 1.3 +0 -17 maven-plugins/html2xdoc/src/test/org/apache/maven/html2xdoc/linkInHeading.xml Index: linkInHeading.xml === RCS file: /home/cvs/maven-plugins/html2xdoc/src/test/org/apache/maven/html2xdoc/linkInHeading.xml,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- linkInHeading.xml 4 Mar 2004 18:13:56 - 1.2 +++ linkInHeading.xml 4 Apr 2004 03:23:50 - 1.3 @@ -1,20 +1,3 @@ - A title 1.3 +0 -17 maven-plugins/html2xdoc/src/test/org/apache/maven/html2xdoc/missingParaBug.xml Index: missingParaBug.xml === RCS file: /home/cvs/maven-plugins/html2xdoc/src/test/org/apache/maven/html2xdoc/missingParaBug.xml,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- missingParaBug.xml4 Mar 2004 18:13:56 - 1.2 +++ missingParaBug.xml4 Apr 2004 03:23:50 - 1.3 @@ -1,20 +1,3 @@ - A title 1.3 +1 -18 maven-plugins/html2xdoc/src/test/org/apache/maven/html2xdoc/output1.xml Index: output1.xml === RCS file: /home/cvs/maven-plugins/html2xdoc/src/test/org/apache/maven/html2xdoc/output1.xml,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- output1.xml 4 Mar 2004 18:13:56 - 1.2 +++ output1.xml 4 Apr 2004 03:23:50 - 1.3 @@ -1,20 +1,3 @@ - A title @@ -30,4 +13,4 @@ hi there
[jira] Created: (MAVEN-1219) Goals from plugin dependencies fail if the plugin is installed as part of the build process
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1219
Here is an overview of the issue:
-
Key: MAVEN-1219
Summary: Goals from plugin dependencies fail if the plugin is installed as part of
the build process
Type: Bug
Status: Unassigned
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven
Versions:
1.0-rc3
Assignee:
Reporter: Chad Brandon
Created: Sat, 3 Apr 2004 10:30 PM
Updated: Sat, 3 Apr 2004 10:30 PM
Environment: Windows XP, JDK 1.4.2_03
Description:
I have a project consisting of multiple subprojects. One of these subprojects
includes a plugin which is built and installed via "plugin:install" during my project
build. A goal is then used from this previously installed plugin to build the rest of
the project's subprojects (in other words other subprojects have a dependency on this
plugin which is installed during the build process).
Using maven-rc1 this used to be no problem, but as of yesterday (I checked out and
built MAVEN-1_0_Branch) using rc3 this fails. If the plugin doesn't already exist in
the ${maven.home}/plugins directory things work fine (if I delete the plugin out
before the build starts), the plugin is installed and other subprojects needing to use
goal(s) from this plugin find it and the build completes successfully. But if the
plugin already exists in ${maven.home}/plugins, I'll get something like below telling
me it can't parse the project.xml, when it fact that file does exist, or I sometimes
get a message telling me the plugin.jelly from that plugin can't be found:
BUILD FAILED
File.. file:/H:/Documents and
Settings/Administrator/.maven/plugins/maven-multiproject-plugin-1.2/plugin.jelly
Element... maven:reactor
Line.. 202
Column 9
Unable to obtain goal [multiproject:install-callback] --
file:/I:/java/eclipse/andromda-all/metafacades/uml/maven.xml:17
:42: Error parsing project.xml 'H:\Documents and
Settings\Administrator\.maven\plugins\maven-andromda-plugi
n-3.0-SNAPSHOT\project.xml'
Total time: 23 seconds
-
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MAVEN-1150) maven.xml inheritance strangeness
The following issue has been updated: Updater: Brett Porter (mailto:[EMAIL PROTECTED]) Date: Sat, 3 Apr 2004 10:16 PM Changes: Fix Version changed to 1.1 Fix Version changed from 1.0-rc3 - For a full history of the issue, see: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1150&page=history - View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1150 Here is an overview of the issue: - Key: MAVEN-1150 Summary: maven.xml inheritance strangeness Type: Bug Status: Open Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven Components: inheritance Fix Fors: 1.1 Versions: 1.0-rc2 Assignee: Brett Porter Reporter: Sean Timm Created: Wed, 4 Feb 2004 4:52 PM Updated: Sat, 3 Apr 2004 10:16 PM Description: The attachment contains child/project.xml that extends project-base.xml. There is a maven.xml file in the folder with project-base.xml as well as a maven.xml in the child folder. If you go to the child folder and type "maven different", it will successfully output "ECHO". If you type "maven" or "maven footest", you'll get a TargetInvocationException due to the echo call in the parent's maven.xml. Note that other jelly tags work successfully in the parent...it appears to be an issue just with Ant tags. Additionally, if you remove the maven.xml from the child folder, and then type "maven footest" in the child folder, you get a "no such goal" error rather than executing the inherited maven.xml goal. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven/xdocs changes.xml
brett 2004/04/03 19:04:56 Modified:xdocsTag: MAVEN-1_0-BRANCH changes.xml Log: change log Revision ChangesPath No revision No revision 1.14.4.5 +6 -0 maven/xdocs/changes.xml Index: changes.xml === RCS file: /home/cvs/maven/xdocs/changes.xml,v retrieving revision 1.14.4.4 retrieving revision 1.14.4.5 diff -u -r1.14.4.4 -r1.14.4.5 --- changes.xml 23 Mar 2004 01:45:57 - 1.14.4.4 +++ changes.xml 4 Apr 2004 03:04:56 - 1.14.4.5 @@ -24,6 +24,12 @@ Vincent Massol + + Apply patch to use system encoding for project so that xdoc transformation of POM works on non-ISO8859-1 systems. + +Improve error handling of HttpUtils + + More than I can remember. Redesigned plugin manager internals to fix the memory leak in the reactor. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MAVEN-558) Errors incorrectly reported when an artifact does not exist on a remote repo
Message: The following issue has been closed. Resolver: Brett Porter Date: Sat, 3 Apr 2004 10:13 PM applied - View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-558 Here is an overview of the issue: - Key: MAVEN-558 Summary: Errors incorrectly reported when an artifact does not exist on a remote repo Type: Bug Status: Closed Priority: Major Resolution: FIXED Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven Components: core Fix Fors: 1.0-rc3 Versions: 1.0-beta-9 Assignee: Reporter: David Zeleznik Created: Wed, 9 Jul 2003 9:25 PM Updated: Sat, 3 Apr 2004 10:13 PM Description: The expected behavior of the DependencyVerifier is to check all remote repos for an artifact. If the artifact is successfully downloaded from at least one remote repo, the fact that the artifact may not exist on other remote repos is supposed to be ignored. Instead, the error is reported to the console "Error retrieving artifact from ...". The logic in DependencyVerifier is actually correct. The problem is in r1.26 of HttpUtils.getFile() which incorrectly throws a generic Exception when a file is not found at a remote URL. Instead, HttpUtils should throw a FileNotFound exception for this case, which will then be caught and handled properly by DependencyVerifier. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven/src/java/org/apache/maven/util HttpUtils.java
brett 2004/04/03 19:02:16
Modified:src/java/org/apache/maven/util Tag: MAVEN-1_0-BRANCH
HttpUtils.java
Log:
PR: MAVEN-558
Submitted by: David Zeleznik
improve error handling in HttpUtils
Revision ChangesPath
No revision
No revision
1.28.4.4 +64 -38maven/src/java/org/apache/maven/util/HttpUtils.java
Index: HttpUtils.java
===
RCS file: /home/cvs/maven/src/java/org/apache/maven/util/HttpUtils.java,v
retrieving revision 1.28.4.3
retrieving revision 1.28.4.4
diff -u -r1.28.4.3 -r1.28.4.4
--- HttpUtils.java1 Mar 2004 22:36:39 - 1.28.4.3
+++ HttpUtils.java4 Apr 2004 03:02:16 - 1.28.4.4
@@ -24,9 +24,11 @@
import java.io.InputStream;
import java.net.Authenticator;
import java.net.HttpURLConnection;
+import java.net.MalformedURLException;
import java.net.PasswordAuthentication;
import java.net.URL;
import java.net.URLConnection;
+import java.util.Date;
/**
* Http utils for retrieving files.
@@ -104,7 +106,7 @@
String proxyUserName,
String proxyPassword,
boolean useChecksum )
-throws Exception
+throws IOException
{
// Get the requested file.
getFile( url,
@@ -165,7 +167,58 @@
String proxyPort,
String proxyUserName,
String proxyPassword )
-throws Exception
+throws IOException
+{
+//set the timestamp to the file date.
+Date timestamp = null;
+if ( useTimestamp && destinationFile.exists() )
+{
+timestamp = new Date(destinationFile.lastModified());
+}
+
+try
+{
+getFile(url,
+destinationFile,
+timestamp,
+proxyHost,
+proxyPort,
+proxyUserName,
+proxyPassword);
+}
+catch ( IOException ex )
+{
+if ( !ignoreErrors )
+{
+throw ex;
+}
+}
+}
+
+/**
+ * Retrieve a remote file.
+ *
+ * @param url the URL of the file to retrieve
+ * @param destinationFile where to store it
+ * @param timestamp if provided, the remote URL is only retrieved if it was
+ * modified more recently than timestamp. Otherwise, null indicates that
+ * the remote URL should be retrieved unconditionally.
+ * @param proxyHost Proxy Host (if proxy is required), or null
+ * @param proxyPort Proxy Port (if proxy is required), or null
+ * @param proxyUserName Proxy Username (if authentification is required),
+ *or null
+ * @param proxyPassword Proxy Password (if authentification is required),
+ *or null
+ * @exception IOException If an I/O exception occurs.
+ */
+public static void getFile( String url,
+ File destinationFile,
+ Date timestamp,
+ String proxyHost,
+ String proxyPort,
+ String proxyUserName,
+ String proxyPassword )
+ throws IOException
{
String[] s = parseUrl( url );
String username = s[0];
@@ -174,25 +227,17 @@
URL source = new URL( parsedUrl );
-//set the timestamp to the file date.
-long timestamp = 0;
-boolean hasTimestamp = false;
-if ( useTimestamp && destinationFile.exists() )
-{
-timestamp = destinationFile.lastModified();
-hasTimestamp = true;
-}
-
//set proxy connection
useProxyUser( proxyHost, proxyPort, proxyUserName, proxyPassword );
//set up the URL connection
URLConnection connection = source.openConnection();
+
//modify the headers
//NB: things like user authentication could go in here too.
-if ( useTimestamp && hasTimestamp )
+if ( timestamp != null )
{
-connection.setIfModifiedSince( timestamp );
+connection.setIfModifiedSince( timestamp.getTime() );
}
// prepare Java 1.1 style credentials
if ( username != null || password != null )
@@ -228,10 +273,6 @@
// test for 404 ourselves, and throw FileNotFoundException as needed
if ( httpConnection.getResponseCode() ==
HttpURLConnection.HTTP_NOT_FOUND)
{
-
[jira] Closed: (MAVEN-1098) cleanup touchstone
Message: The following issue has been closed. - View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1098 Here is an overview of the issue: - Key: MAVEN-1098 Summary: cleanup touchstone Type: Task Status: Closed Priority: Major Resolution: FIXED Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven Fix Fors: 1.0-rc3 Versions: 1.0-rc2 Assignee: Reporter: Brett Porter Created: Tue, 30 Dec 2003 10:50 PM Updated: Sat, 3 Apr 2004 10:10 PM Description: touchstone has a number of goals that are not used because they don't work. These are annotated with @todo tags and should be resolved. Additionally, there are tests for plugins in there (sea, deploy) - these should be moved to a plugin:test type goal in the plugin itself. Finally, the following touchstone/src/reactor-build subdirectories don't seem to work because the tests are incorrectly specified: * legacy * legacy-fugly * clean (does nothing) * standard They should be made useful or removed. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven/src/java/org/apache/maven/cli App.java
brett 2004/04/03 18:56:32
Modified:src/java/org/apache/maven/cli Tag: MAVEN-1_0-BRANCH App.java
Log:
PR: MAVEN-1204
-o on command line conquers all
Revision ChangesPath
No revision
No revision
1.37.4.17 +6 -3 maven/src/java/org/apache/maven/cli/App.java
Index: App.java
===
RCS file: /home/cvs/maven/src/java/org/apache/maven/cli/App.java,v
retrieving revision 1.37.4.16
retrieving revision 1.37.4.17
diff -u -r1.37.4.16 -r1.37.4.17
--- App.java 1 Apr 2004 08:09:30 - 1.37.4.16
+++ App.java 4 Apr 2004 02:56:32 - 1.37.4.17
@@ -27,6 +27,7 @@
import org.apache.commons.logging.LogFactory;
import org.apache.log4j.Level;
import org.apache.log4j.Logger;
+import org.apache.maven.MavenConstants;
import org.apache.maven.MavenSession;
import org.apache.maven.MavenUtils;
import org.apache.maven.NoGoalException;
@@ -369,11 +370,13 @@
if ( getCli().hasOption( WORK_OFFLINE ) )
{
-getRootContext().setOnline( Boolean.FALSE );
+//getRootContext().setOnline( Boolean.FALSE );
+System.setProperty( MavenConstants.ONLINE, "false" );
}
else
{
-getRootContext().setOnline( Boolean.TRUE );
+//getRootContext().setOnline( Boolean.TRUE );
+System.setProperty( MavenConstants.ONLINE, "true" );
}
}
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven/src/java/org/apache/maven/cli CLIManager.java
brett 2004/04/03 18:55:58 Modified:src/java/org/apache/maven/cli Tag: MAVEN-1_0-BRANCH CLIManager.java Log: clarify option Revision ChangesPath No revision No revision 1.12.4.5 +1 -1 maven/src/java/org/apache/maven/cli/CLIManager.java Index: CLIManager.java === RCS file: /home/cvs/maven/src/java/org/apache/maven/cli/CLIManager.java,v retrieving revision 1.12.4.4 retrieving revision 1.12.4.5 diff -u -r1.12.4.4 -r1.12.4.5 --- CLIManager.java 1 Mar 2004 22:36:36 - 1.12.4.4 +++ CLIManager.java 4 Apr 2004 02:55:57 - 1.12.4.5 @@ -75,7 +75,7 @@ options.addOption( OptionBuilder .withLongOpt( "dir" ) .hasArg() - .withDescription( "Set effective working directory" ) + .withDescription( "Set effective working directory (ignored with -p or -f)" ) .create( 'd' ) ); options.addOption( OptionBuilder - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MAVEN-1181) maven -d doesn't work when combined with -p
Message: The following issue has been closed. Resolver: Brett Porter Date: Sat, 3 Apr 2004 10:05 PM no use case for this - View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1181 Here is an overview of the issue: - Key: MAVEN-1181 Summary: maven -d doesn't work when combined with -p Type: Bug Status: Closed Priority: Minor Resolution: WON'T FIX Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven Components: cli Fix Fors: 1.0-rc3 Versions: 1.0-rc2 Assignee: Reporter: Brett Porter Created: Tue, 2 Mar 2004 6:35 AM Updated: Sat, 3 Apr 2004 10:05 PM Description: - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MAVEN-1056) separate release-independant documentation
The following issue has been updated:
Updater: Brett Porter (mailto:[EMAIL PROTECTED])
Date: Sat, 3 Apr 2004 10:03 PM
Changes:
environment changed to
Fix Version changed to 1.1
Fix Version changed from 1.0-rc3
-
For a full history of the issue, see:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1056&page=history
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1056
Here is an overview of the issue:
-
Key: MAVEN-1056
Summary: separate release-independant documentation
Type: Task
Status: Unassigned
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven
Components:
documentation
Fix Fors:
1.1
Assignee:
Reporter: Brett Porter
Created: Wed, 26 Nov 2003 5:28 PM
Updated: Sat, 3 Apr 2004 10:03 PM
Description:
We need to separate the documentation that is release independant (or applies to
multiple releases) to a separate "subproject" that can be deployed and versioned
appropriately. This would mean that the current site can reflect the latest release,
but have up to date news, FAQs, articles, etc.
maven.apache.org/1.0-rc2/ - generated site with reports, javadoc, installation
instructions, download links
maven.apache.org/1.1-SNAPSHOT/ - current CVS HEAD, as above for current.
/www/maven.apache.org/${pom.currentVersion}
maven.apache.org/ - home page, navigation that refers to the last release, and has
documentation such as users guide, FAQs etc. While it may contain 1.1 documentation,
this must be clearly denoted
The same approach should be taken for the plugins.
/www/maven.apache.org/reference/plugins/ear/${pom.current
Version}
The navigation can include links to other versions at the top. At the point where a
version is removed from there, it should also be archived and removed from
/www/maven.apache.org
Setting up the navigation for the main site and making it consistent with subsections
could be tedious and tricky - it may be good to have the xdoc-plugin support this in
some fashion.
-
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven/src/test/touchstone-build maven.xml
brett 2004/04/03 18:50:45 Modified:src/test/touchstone-build Tag: MAVEN-1_0-BRANCH maven.xml Log: cleanup Revision ChangesPath No revision No revision 1.43.4.12 +3 -16 maven/src/test/touchstone-build/maven.xml Index: maven.xml === RCS file: /home/cvs/maven/src/test/touchstone-build/maven.xml,v retrieving revision 1.43.4.11 retrieving revision 1.43.4.12 diff -u -r1.43.4.11 -r1.43.4.12 --- maven.xml 2 Apr 2004 23:43:09 - 1.43.4.11 +++ maven.xml 4 Apr 2004 02:50:45 - 1.43.4.12 @@ -22,8 +22,7 @@ xmlns:u="jelly:util" xmlns:maven="jelly:maven" xmlns:define="jelly:define" - xmlns:i="jelly:interaction" - xmlns:deploy="deploy"> + xmlns:i="jelly:interaction"> Touchstone complete @@ -456,17 +456,6 @@ - - - - - - @@ -474,7 +463,6 @@ @@ -540,7 +528,6 @@ @@ -580,7 +567,7 @@ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MAVEN-1050) cannot get multibyte string from project.xml
Message: The following issue has been closed. Resolver: Brett Porter Date: Sat, 3 Apr 2004 9:59 PM applied - View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1050 Here is an overview of the issue: - Key: MAVEN-1050 Summary: cannot get multibyte string from project.xml Type: Bug Status: Closed Priority: Major Resolution: FIXED Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven Components: core Fix Fors: 1.0-rc3 Versions: 1.0-rc1 Assignee: Brett Porter Reporter: Shinsuke SUGAYA Created: Sun, 23 Nov 2003 1:20 AM Updated: Sat, 3 Apr 2004 9:59 PM Environment: Redhat9, J2SE 1.4.1_04-b01 Description: Maven cannot get multibyte strings from project.xml. For example, in Japanese environment, if you run site plugin, Japanese project and organization name defined by project.xml are displayed as garbage. You should have the same result even if Japanese characters are escaped to "&n;" in project.xml(defined by ISO-8859-1). The issue is reproduced from RC 1(including CVS HEAD), but not reproduced in beta10. I think CJK users encounter this issue. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven/src/java/org/apache/maven MavenUtils.java
brett 2004/04/03 18:48:03
Modified:src/java/org/apache/maven Tag: MAVEN-1_0-BRANCH
MavenUtils.java
Log:
PR: MAVEN-1050
Submitted by: Shinsuke SUGAYA
Use system file encoding for POM
Revision ChangesPath
No revision
No revision
1.107.4.17 +3 -11 maven/src/java/org/apache/maven/MavenUtils.java
Index: MavenUtils.java
===
RCS file: /home/cvs/maven/src/java/org/apache/maven/MavenUtils.java,v
retrieving revision 1.107.4.16
retrieving revision 1.107.4.17
diff -u -r1.107.4.16 -r1.107.4.17
--- MavenUtils.java 2 Apr 2004 23:37:19 - 1.107.4.16
+++ MavenUtils.java 4 Apr 2004 02:48:03 - 1.107.4.17
@@ -81,9 +81,6 @@
/** Log. */
private static final Log log = LogFactory.getLog( MavenUtils.class );
-/** Internal encoding used for Jelly interpolation. */
-private static final String INTERNAL_ENCODING = "ISO-8859-1";
-
/** we want to parse something */
private static final ThreadLocal xmlReaderPool = new ThreadLocal();
@@ -423,10 +420,7 @@
beanWriter.setWriteIDs( true );
beanWriter.write( project );
-// We do not care what the original encoding was originally. This
-// is all completely internal. Our StringInputStream requires
-// everything to be encoded in "ISO-8859-1".
-return projectStream.toString( INTERNAL_ENCODING );
+return projectStream.toString( System.getProperty( "file.encoding" ) );
}
/**
@@ -718,7 +712,7 @@
* @return The generated maven based on the contents of the standard maven
* properties files.
*/
-public static MavenJellyContext createContext( File descriptorDirectory,
+public static MavenJellyContext createContext( File descriptorDirectory,
MavenJellyContext parentContext )
{
// System properties
@@ -758,8 +752,6 @@
// child's context values into the jelly context because we want the
// child values to win and only use the parent in the event the
// child cannot provide the value.
-
- // TODO: need an exception for those specified on the command line
if ( parentContext != null )
{
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MAVEN-1204) build and project properties should not override command line
Message: The following issue has been closed. Resolver: Brett Porter Date: Sat, 3 Apr 2004 9:55 PM fixed for -o. No other cmd line properties equate to context properties. done. - View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1204 Here is an overview of the issue: - Key: MAVEN-1204 Summary: build and project properties should not override command line Type: Bug Status: Closed Priority: Minor Resolution: FIXED Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven Components: cli Fix Fors: 1.0-rc3 Versions: 1.0-rc2 Assignee: Brett Porter Reporter: John Casey Created: Fri, 19 Mar 2004 4:03 PM Updated: Sat, 3 Apr 2004 9:55 PM Environment: windows (at least) Description: when running maven, if I specify something like: maven -o goal it will still try to satisfy dependencies by d/l'ing from remote repository. This is NOT the case if I re-run with: maven -Dmaven.mode.online=false goal it looks like there might be an inheritance issue with the MavenJellyContext, but this is just a guess. I've tried setting inherit=false, then true around the section in App.java where the options are set, but no luck... - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven/src/test/touchstone-build/src/reactor-build/default project.properties
brett 2004/04/03 18:44:06 Added: src/test/touchstone-build/src/reactor-build/default Tag: MAVEN-1_0-BRANCH project.properties Log: missing file for touchstone Revision ChangesPath No revision No revision 1.1.2.1 +1 -0 maven/src/test/touchstone-build/src/reactor-build/default/Attic/project.properties - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MAVEN-1216) NoClassDefFoundError for org/jaxen/JaxenException and org/saxpath/SAXPathException
The following comment has been added to this issue:
Author: Brett Porter
Created: Sat, 3 Apr 2004 9:53 PM
Body:
works for me.
What non-standard plugins do you have installed?
-
View this comment:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1216&page=comments#action_18142
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1216
Here is an overview of the issue:
-
Key: MAVEN-1216
Summary: NoClassDefFoundError for org/jaxen/JaxenException and
org/saxpath/SAXPathException
Type: Bug
Status: Unassigned
Priority: Major
Original Estimate: 1 hour
Time Spent: Unknown
Remaining: 1 hour
Project: maven
Components:
jelly/ant integration
Fix Fors:
1.0-rc3
Versions:
1.0-rc2
Assignee:
Reporter: Vladimir Kralik
Created: Thu, 1 Apr 2004 9:51 AM
Updated: Sat, 3 Apr 2004 9:53 PM
Environment: maven-1.0-rc2
jdk 1.4.2_03
M$ Windows 2000 SP 4
cygwin
Description:
When I try install my own plugin ( by using "maven plugin:install" ),then I get :
<>
Caused by: java.lang.NoClassDefFoundError: org/jaxen/JaxenException
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:141)
at
org.apache.commons.jelly.tags.xml.XMLTagLibrary.class$(XMLTagLibrary.java:82)
<>
after "cp jaxen-core-1.0-FCS.jar $MAVEN_HOME/lib" :
<>
Caused by: java.lang.NoClassDefFoundError: org/saxpath/SAXPathException
<>>
at
org.apache.commons.jelly.tags.xml.XMLTagLibrary.class$(XMLTagLibrary.java:82)
<>
after "cp saxpath-1.0-FCS.jar $MAVEN_HOME/lib"
it works fine.
jaxen and saxpath are not listed as dependecies in my plugin.
I use very simple Hello World plugin ( see below )
I thing that problem is in jelly-integration, because jelly
(org.apache.commons.jelly.tags.xml.ForEachTag) requires org.jaxen.JaxenException and
dom4j (org.dom4j.xpath.XPathPattern) requieres org.saxpath.SAXPathException.
===
project.xml
===
3
maven-hello-plugin
Maven Hello World Plug-in
1.0.0-SNAPSHOT
${basedir}
plugin.jelly
plugin.properties
project.xml
===
plugin.jelly
===
Hello, ${maven.hello.world}
===
plugin.properties
===
maven.hello.world=World
-
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Missing sources for GPLd and LGPLd artifacts
Hi Maven developers, while browsing the ibiblio repository, I noticed that some LGPLd and GPLd artifacts didn't have their sources available. I hope that's just some glitch that happened when the artifacts were uploaded. Since the GPL and LGPL both require the sources for binaries to be distributed as well, it'd be nice if the ibiblio repository could include them, too. See the GPL FAQ for more information: http://www.gnu.org/licenses/gpl-faq.html On a side note, I've seen that recently even hard-core Maven developers have began to recognize the value of having source code available though Maven. Congratulations on that amazing breakthrough. Hosting the free software sources in your central repository would make it easy for you comply with licenses of respective free software, while making it very convenient for maven users to access these sources through your tool. cheers, dalibor topic - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
