[jira] Created: (MAVEN-525) maven-eclipse-plugin doesnot generate all expected artifacts
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-525 Here is an overview of the issue: - Key: MAVEN-525 Summary: maven-eclipse-plugin doesnot generate all expected artifacts Type: Improvement Status: Unassigned Priority: Trivial Time Spent: Unknown Estimate: 0 minutes Project: maven Assignee: Reporter: gilles dodinet Created: Mon, 30 Jun 2003 1:43 AM Updated: Mon, 30 Jun 2003 1:43 AM Description: eclipse plugin doesnot generate all expected artifacts. for instance : * if build/aspectSourceDirectory is present in the pom, a source folder corresponding to this source directory should be added to the project AND aspectj nature should be attached to the eclipse project (assuming aspectj plugin has been installed) * if build/resource(s) are declared in the pom, a source folder should be created in the eclipse project for every unique resource folder. same goes for unitTest/resources (and perhaps integrationUnitTest ? never used it so im not sure of whats declared in the pom) - 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/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] Closed: (MAVEN-510) Eclipse plugin external-tools goal doesn't work with eclipse 2.1
Message: The following issue has been closed. Resolver: dion gillard Date: Mon, 30 Jun 2003 1:19 AM Added eclipse:external-tools-21 goal - View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-510 Here is an overview of the issue: - Key: MAVEN-510 Summary: Eclipse plugin external-tools goal doesn't work with eclipse 2.1 Type: Bug Status: Closed Priority: Major Resolution: FIXED Time Spent: Unknown Estimate: 0 minutes Project: maven Components: plugin-other Fix Fors: 1.0-beta-10 Versions: 1.0-beta-10 Assignee: dion gillard Reporter: dion gillard Created: Sun, 22 Jun 2003 10:19 PM Updated: Mon, 30 Jun 2003 1:19 AM Description: I'm running Maven with Eclipse and found the eclipse:external-tools goal in maven's eclipse plugin that is supposed to automatically create external tool entries in eclipse for maven. When properly set up and executed, an externaltools.xml is placed in eclipse's workspace\.metadata\.plugins\org.eclipse.ui.externaltools directory but this doesn't seem to be enough for eclipse. I suspect that this used to work in an earlier version of eclipse, but that the interface has since changed and this particular goal hasn't been updated to reflect the changes made in eclipse. I've browsed the mailing list archive to no avail trying to figure this out. Any suggestions? Is this supposed to work in the current eclipse release? (I'm running Eclipse 2.1.0). Thanks! t -- Thomas Burns [EMAIL PROTECTED] - 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/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/plugins-build/eclipse plugin.jelly project.xml
dion2003/06/29 22:56:07
Modified:src/plugins-build/eclipse/xdocs changes.xml goals.xml
src/plugins-build/eclipse plugin.jelly project.xml
Log:
external-tools support for eclipse 2.1
Note: this is not thoroughly tested
Revision ChangesPath
1.4 +7 -1 maven/src/plugins-build/eclipse/xdocs/changes.xml
Index: changes.xml
===
RCS file: /home/cvs/maven/src/plugins-build/eclipse/xdocs/changes.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- changes.xml 9 May 2003 08:42:21 - 1.3
+++ changes.xml 30 Jun 2003 05:56:07 - 1.4
@@ -6,7 +6,13 @@
-
+
+
+Added support for Eclipse 2.1 external tools
+
+
+
+
Smarter generation of .classpath file.
${basedir} prefix is cut off if present in any path.
1.4 +22 -0 maven/src/plugins-build/eclipse/xdocs/goals.xml
Index: goals.xml
===
RCS file: /home/cvs/maven/src/plugins-build/eclipse/xdocs/goals.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- goals.xml 10 Apr 2003 06:39:37 - 1.3
+++ goals.xml 30 Jun 2003 05:56:07 - 1.4
@@ -66,6 +66,28 @@
+
+ eclipse:external-tools-21
+
+
+ Generates an external tool file for each default goal available to
+ a Maven project into the ${maven.build.dir}/eclipse/
directory
+
+
+ If the ${maven.eclipse.workspace}
+ property is set, the file is copied to the correct location within
+ that workspace
+
+
+ If the ${maven.eclipse.workspace}
+ is not set, the files should be manually copied to
+
+${your eclipse workspace}/.metadata/.plugins/org.eclipse.debug.core/.launches/
+
+
+
+
+
eclipse:add-maven-repo
1.19 +70 -1 maven/src/plugins-build/eclipse/plugin.jelly
Index: plugin.jelly
===
RCS file: /home/cvs/maven/src/plugins-build/eclipse/plugin.jelly,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -r1.18 -r1.19
--- plugin.jelly 10 Jun 2003 10:17:26 - 1.18
+++ plugin.jelly 30 Jun 2003 05:56:07 - 1.19
@@ -3,7 +3,8 @@
+ xmlns:test="test"
+ xmlns:util="jelly:util">
@@ -242,6 +243,74 @@
+
+
+
+
+
+
+
+Creating external tools
+
+
+
+Adapting the generated file for a ${os} box.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Generating ${fileName}
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Please set maven.eclipse.workspace to the location of your eclipse workspace.
+ Alternatively, copy
+${maven.build.dir}/eclipse/*.launch
+ to
+[maven.eclipse.workspace]/.metadata/.plugins/org.eclipse.debug.core/.launches/
+
+
+
+
+
1.11 +1 -1 maven/src/plugins-build/eclipse/project.xml
Index: project.xml
===
RCS file: /home/cvs/maven/src/plugins-build/eclipse/project.xml,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- project.xml 9 Apr 2003 01:06:45 - 1.10
+++ project.xml 30 Jun 2003 05:56:07 - 1.11
@@ -5,7 +5,7 @@
3
maven-eclipse-plugin
Maven Eclipse Plug-in
- 1.3
+ 1.4-SNAPSHOT
A plugin to generate various files for the Eclipse IDE and ease the
use of Maven within that environment
Eclipse Plugin for Maven
http://maven.apache.org/reference/plugins/eclipse/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven/src/plugins-build/eclipse/src/plugin-resources/templates launch.jelly
dion2003/06/29 22:53:17 Added: src/plugins-build/eclipse/src/plugin-resources/templates launch.jelly Log: Template for the eclipse 2.1 launch files Revision ChangesPath 1.1 maven/src/plugins-build/eclipse/src/plugin-resources/templates/launch.jelly Index: launch.jelly === - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven/src/plugins-build/eclipse/src/plugin-resources/templates - New directory
dion2003/06/29 22:53:07 maven/src/plugins-build/eclipse/src/plugin-resources/templates - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven/src/plugins-build/eclipse/src/plugin-resources - New directory
dion2003/06/29 22:53:07 maven/src/plugins-build/eclipse/src/plugin-resources - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven/src/plugins-build/eclipse/src - New directory
dion2003/06/29 22:53:07 maven/src/plugins-build/eclipse/src - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven/src/templates/standard project.xml
jvanzyl 2003/06/29 22:10:07 Removed: src/templates/sourceforge project.xml src/templates/standard project.xml Log: o These are out of date and not documented. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven/src/tools migrate-repo.pl
jvanzyl 2003/06/29 22:03:46 Removed: src/tools migrate-repo.pl Log: o unlikely this is being used and it's not documented at any rate. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven/src/tex ruminations.tex
jvanzyl 2003/06/29 22:02:53 Removed: src/tex ruminations.tex Log: o This doc hasn't been looked at for a while and almost all the ideas have now been incorporated into Maven. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven-new/core/src/aspect/org/apache/maven PomInheritanceAspect.java PomInterpolationAspect.java
jvanzyl 2003/06/29 22:01:10 Removed: core/src/aspect/org/apache/maven PomInheritanceAspect.java PomInterpolationAspect.java Log: o Trying to avoid the use of aspectj in the core for the sake of simplicity. Without much effort it can be done. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MAVEN-510) Eclipse plugin external-tools goal doesn't work with eclipse 2.1
The following issue has been updated: Updater: dion gillard (mailto:[EMAIL PROTECTED]) Date: Sun, 29 Jun 2003 11:10 PM Comment: We'll need something like this for each goal we want added to the external tools entry Changes: Attachment changed from to maven clean.launch - For a full history of the issue, see: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-510&page=history - View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-510 Here is an overview of the issue: - Key: MAVEN-510 Summary: Eclipse plugin external-tools goal doesn't work with eclipse 2.1 Type: Bug Status: Assigned Priority: Major Time Spent: Unknown Estimate: 0 minutes Project: maven Components: plugin-other Versions: 1.0-beta-10 Assignee: dion gillard Reporter: dion gillard Created: Sun, 22 Jun 2003 10:19 PM Updated: Sun, 29 Jun 2003 11:10 PM Description: I'm running Maven with Eclipse and found the eclipse:external-tools goal in maven's eclipse plugin that is supposed to automatically create external tool entries in eclipse for maven. When properly set up and executed, an externaltools.xml is placed in eclipse's workspace\.metadata\.plugins\org.eclipse.ui.externaltools directory but this doesn't seem to be enough for eclipse. I suspect that this used to work in an earlier version of eclipse, but that the interface has since changed and this particular goal hasn't been updated to reflect the changes made in eclipse. I've browsed the mailing list archive to no avail trying to figure this out. Any suggestions? Is this supposed to work in the current eclipse release? (I'm running Eclipse 2.1.0). Thanks! t -- Thomas Burns [EMAIL PROTECTED] - 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/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-510) Eclipse plugin external-tools goal doesn't work with eclipse 2.1
The following comment has been added to this issue:
Author: dion gillard
Created: Sun, 29 Jun 2003 11:09 PM
Body:
It appears that eclipse 2.1 stores this information differently:
it looks like it goes in
${maven.eclipse.workspace}\.metadata\.plugins\org.eclipse.debug.core\.launches\${name}.launch
where name is the name of the tool, e.g. maven clean.
Here's a sample file:
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-510
Here is an overview of the issue:
-
Key: MAVEN-510
Summary: Eclipse plugin external-tools goal doesn't work with eclipse 2.1
Type: Bug
Status: Assigned
Priority: Major
Time Spent: Unknown
Estimate: 0 minutes
Project: maven
Components:
plugin-other
Versions:
1.0-beta-10
Assignee: dion gillard
Reporter: dion gillard
Created: Sun, 22 Jun 2003 10:19 PM
Updated: Mon, 23 Jun 2003 1:35 AM
Description:
I'm running Maven with Eclipse and found the eclipse:external-tools goal in maven's
eclipse plugin that is supposed to automatically create external tool entries in
eclipse for maven. When properly set up and executed, an externaltools.xml is placed
in eclipse's workspace\.metadata\.plugins\org.eclipse.ui.externaltools directory but
this doesn't seem to be enough for eclipse. I suspect that this used to work in an
earlier version of eclipse, but that the interface has since changed and this
particular goal hasn't been updated to reflect the changes made in eclipse.
I've browsed the mailing list archive to no avail trying to figure this out. Any
suggestions? Is this supposed to work in the current eclipse release? (I'm running
Eclipse 2.1.0).
Thanks!
t
--
Thomas Burns
[EMAIL PROTECTED]
-
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/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 status.xml
dion2003/06/29 20:25:11 Modified:xdocsstatus.xml Log: Fix typo on beta 8 -> beta 9 Revision ChangesPath 1.13 +2 -4 maven/xdocs/status.xml Index: status.xml === RCS file: /home/cvs/maven/xdocs/status.xml,v retrieving revision 1.12 retrieving revision 1.13 diff -u -r1.12 -r1.13 --- status.xml26 Feb 2003 11:05:01 - 1.12 +++ status.xml30 Jun 2003 03:25:11 - 1.13 @@ -18,10 +18,8 @@ - We are currently working on Maven 1.0 Beta 9. The next release will - focus on resolving many of the outstanding issues with Maven. Many users - have submitted tests cases to help track down problems and we hope - to get most of them resolved by Beta 9. + We are currently working on Maven 1.0 Beta 10. The next release will + focus on resolving many of the outstanding issues with Maven. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven/src/plugins-build/reactor .cvsignore project.properties plugin.jelly project.xml plugin.properties
dion2003/06/29 20:19:26 Removed: src/plugins-build/reactor/xdocs .cvsignore changes.xml goals.xml properties.xml navigation.xml index.xml src/plugins-build/reactor .cvsignore project.properties plugin.jelly project.xml plugin.properties Log: Rename from reactor plugin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven/src/plugins-build/multiproject/xdocs .cvsignore goals.xml properties.xml navigation.xml changes.xml index.xml
dion2003/06/29 20:18:49
Added: src/plugins-build/multiproject project.properties
project.xml plugin.properties .cvsignore
plugin.jelly
src/plugins-build/multiproject/xdocs .cvsignore goals.xml
properties.xml navigation.xml changes.xml index.xml
Log:
Rename from reactor
Revision ChangesPath
1.1 maven/src/plugins-build/multiproject/project.properties
Index: project.properties
===
# ---
# P R O J E C T P R O P E R T I E S
# ---
maven.xdoc.date=left
maven.xdoc.version=${pom.currentVersion}
maven.license.licenseFile=${basedir}/../../../LICENSE.txt
1.1 maven/src/plugins-build/multiproject/project.xml
Index: project.xml
===
${basedir}/../project.xml
maven-multiproject-plugin
Maven Multi-Project Plug-in
1.0-SNAPSHOT
A plugin to handle the building of multiple projects within
maven
Multi-Project Plugin for Maven
http://maven.apache.org/reference/plugins/multiproject/
/www/maven.apache.org/reference/plugins/multiproject/
scm:cvs:pserver:[EMAIL
PROTECTED]:/home/cvspublic:maven/src/plugins-build/multiproject/
http://cvs.apache.org/viewcvs/maven/src/plugins-build/multiproject/
dIon Gillard
dion
[EMAIL PROTECTED]
Multitask Consulting
Java Developer
1.1 maven/src/plugins-build/multiproject/plugin.properties
Index: plugin.properties
===
# ---
# P L U G I N P R O P E R I E S
# ---
# MultiProject plugin.
# ---
maven.multiproject.basedir=${basedir}
maven.multiproject.includes=*/project.xml
maven.multiproject.excludes=
maven.multiproject.ignoreFailures=false
1.1 maven/src/plugins-build/multiproject/.cvsignore
Index: .cvsignore
===
target
*.log
1.1 maven/src/plugins-build/multiproject/plugin.jelly
Index: plugin.jelly
===
A goal to run must be specified, e.g.
maven -Dgoal=clean multiproject:goal
Executing ${goal} on all projects
1.1 maven/src/plugins-build/multiproject/xdocs/.cvsignore
Index: .cvsignore
===
stylesheets
1.1 maven/src/plugins-build/multiproject/xdocs/goals.xml
Index: goals.xml
===
Maven Multi-Project Plug-in Goals
dIon Gillard
multiproject
Run the site goal of all projects
multiproject:site
Run the site goal of all projects
multiproject:goal
Run the comma separated list of goals provided by the variable
goal for all projects
e.g.
maven -Dgoal=java:compile multiproject:goal
or
maven -Dgoal=clean,java:compile,test multiproject:goal
1.1 maven/src/plugins-build/multiproject/xdocs/properties.xml
Index: properties.xml
===
Maven Multi-Project Plug-in Properties
dIon Gillard
Property
Optional?
Description
maven.multiproject.basedir
Yes
This is the base directory that the plugin will use when searching for
projects to be processed. It is also the 'current directory' for
relative paths
Default value is ${basedir}.
maven.multiproject.excludes
Yes
This is the list of file specifications to be excluded wh
cvs commit: maven/src/plugins-build/multiproject - New directory
dion2003/06/29 20:18:34 maven/src/plugins-build/multiproject - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven/src/plugins-build/multiproject/xdocs - New directory
dion2003/06/29 20:18:35 maven/src/plugins-build/multiproject/xdocs - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MAVEN-522) Clarification of POM elements that use paths.
The following comment has been added to this issue:
Author: Brett Porter
Created: Sun, 29 Jun 2003 9:44 PM
Body:
> I thought it was the opposite. We currently are expecting
> sourceDirectory to be absolute.
sourceDirectory will be absolute once loaded (File object will be made absolute by
prepending ${basedir} - we can never use relative File objects). However I believe the
specification in the POM does not need the basedir and is potential mail list flooder
:)
I'm happy to change this to requiring ${basedir} and giving a deprecation mesage (but
working) on relative paths, but it seems unnecessary. More people will play with
project.xml than maven.xml.
>>- all properties that specify files and use of files in maven.xml will
>> have to have ${basedir} or absolute paths as there is no way to track
>> CWD from there, or to know which properties are files.
> Why is this different from project.xml? I'm not sure I understand why > paths in
> maven.xml can't be relative to it's project.xml.
This is just my understanding, but wouldn't Jelly need to be made aware of ${basedir}
and handle that?
> Is project.xml still optional to run Maven? It currently is.
Yes, this doesn't change that.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-522
Here is an overview of the issue:
-
Key: MAVEN-522
Summary: Clarification of POM elements that use paths.
Type: Task
Status: Unassigned
Priority: Major
Time Spent: Unknown
Estimate: 0 minutes
Project: maven
Assignee:
Reporter: Jason van Zyl
Created: Sat, 28 Jun 2003 8:13 AM
Updated: Sat, 28 Jun 2003 8:13 AM
Description:
Currently there are several elements in the POM that use paths in order to find
various resources. The currently accepted pattern is to use ${basedir} as a prefix for
all these paths so that they work in the reactor environment. We can certainly
identify all the elements in the POM that are path related. We need to decide whether
to mandate the use of ${basedir} or make it implicit in POM elements that store paths.
Once this is decided the plugins all need to be audited to ensure they follow the
pattern we mandate.
-
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/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]
Re: Use of Jelly scopes in plugins
Jason van Zyl <[EMAIL PROTECTED]> wrote on 30/06/2003 11:48:55 AM: > On Sun, 2003-06-29 at 19:01, [EMAIL PROTECTED] wrote: > > With the repository plugin, the use of the parent scope is to 'return' a > > variable from a tag in a plugin. The use of the system scope is to access > > system properties. > > The system properties have always been available so that's not a > problem. > > So in the repository plugin it's used as a means to return a value. > You're using it like a method, sort of? Sort of. One tag parses a file and makes it available in the caller's context, e.g. The caller is the parent scope to the tag. > > With the plugin plugin, it's used to read a property file into it's own > > scope and pass them as a single map back to the parent. > > What's the parent in this case? A goal in the same plugin. -- dIon Gillard, Multitask Consulting Blog: http://blogs.codehaus.org/people/dion/ Work: http://www.multitask.com.au
[jira] Commented: (MAVEN-522) Clarification of POM elements that use paths.
The following comment has been added to this issue:
Author: dion gillard
Created: Sun, 29 Jun 2003 9:19 PM
Body:
> - all paths in project.xml should not use ${basedir}, and should be
> considered relative to project.xml. There is no need to have any
> absolute paths.
I thought it was the opposite. We currently are expecting sourceDirectory to be
absolute.
>- all properties that specify files and use of files in maven.xml will
> have to have ${basedir} or absolute paths as there is no way to track
> CWD from there, or to know which properties are files.
Why is this different from project.xml? I'm not sure I understand why paths in
maven.xml can't be relative to it's project.xml.
Is project.xml still optional to run Maven? It currently is.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-522
Here is an overview of the issue:
-
Key: MAVEN-522
Summary: Clarification of POM elements that use paths.
Type: Task
Status: Unassigned
Priority: Major
Time Spent: Unknown
Estimate: 0 minutes
Project: maven
Assignee:
Reporter: Jason van Zyl
Created: Sat, 28 Jun 2003 8:13 AM
Updated: Sat, 28 Jun 2003 8:13 AM
Description:
Currently there are several elements in the POM that use paths in order to find
various resources. The currently accepted pattern is to use ${basedir} as a prefix for
all these paths so that they work in the reactor environment. We can certainly
identify all the elements in the POM that are path related. We need to decide whether
to mandate the use of ${basedir} or make it implicit in POM elements that store paths.
Once this is decided the plugins all need to be audited to ensure they follow the
pattern we mandate.
-
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/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]
Re: Use of Jelly scopes in plugins
On Sun, 2003-06-29 at 19:01, [EMAIL PROTECTED] wrote: > With the repository plugin, the use of the parent scope is to 'return' a > variable from a tag in a plugin. The use of the system scope is to access > system properties. The system properties have always been available so that's not a problem. So in the repository plugin it's used as a means to return a value. You're using it like a method, sort of? > With the plugin plugin, it's used to read a property file into it's own > scope and pass them as a single map back to the parent. What's the parent in this case? > These, or something to replace them are necessary. Yup, no problem. > -- > dIon Gillard, Multitask Consulting > Blog: http://blogs.codehaus.org/people/dion/ > Work: http://www.multitask.com.au > > > Jason van Zyl <[EMAIL PROTECTED]> wrote on 30/06/2003 05:59:52 AM: > > > Howdy, > > > > The last hiccup I've run into is the jelly scope test in the touchstone > > build. I looked at it and wondered why this is even needed so I looked > > through the plugins and found all sorts of references to setting > > variables with scopes. The following plugins have this attribute: > > > > clover > > javadoc > > junit-report > > plugin > > repository > > > > For anyone who added the use of scopes what exactly is the purpose? I'm > > trying to clarify where things are defined and the exact behaviour of > > contexts. Are these uses for cross-plugin communication? I would really > > like to eliminate the use of scopes all together. > > > > -- > > jvz. > > > > Jason van Zyl > > [EMAIL PROTECTED] > > http://tambora.zenplex.org > > > > In short, man creates for himself a new religion of a rational > > and technical order to justify his work and to be justified in it. > > > > -- Jacques Ellul, The Technological Society > > > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > -- jvz. Jason van Zyl [EMAIL PROTECTED] http://tambora.zenplex.org In short, man creates for himself a new religion of a rational and technical order to justify his work and to be justified in it. -- Jacques Ellul, The Technological Society - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MAVEN-489) Checkstyle Error - "Got an exception - java.lang.ClassCastException "
The following comment has been added to this issue:
Author: Steve Ovens
Created: Sun, 29 Jun 2003 8:11 PM
Body:
I should note that swapping the order of reports (jdepend and checkstyle) (as
suggested above by Incze Lajos [ 16/Jun/03 07:19 PM ]) did not have any effect - I get
the ClassCastException reported either way.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-489
Here is an overview of the issue:
-
Key: MAVEN-489
Summary: Checkstyle Error - "Got an exception - java.lang.ClassCastException "
Type: New Feature
Status: Unassigned
Priority: Major
Time Spent: Unknown
Estimate: 0 minutes
Project: maven
Components:
plugin-other
Versions:
1.0-beta-10
Assignee:
Reporter: Nick Minutello
Created: Sat, 14 Jun 2003 6:05 AM
Updated: Mon, 23 Jun 2003 1:40 AM
Environment: JDK1.4.1_01 on Win2K
Description:
I have the latest HEAD build of Maven (built late 13th June GMT) and I am seeing this
error 100s of times over in the checkstyle report.
Error Line
Got an exception - java.lang.ClassCastException 0
Mailing list conversations:
On Fri, Jun 13, 2003 at 04:40:44PM +0800, Willie Vu wrote:
>> > Vincent,
>> >
>> > After I changed antlr plugin to use 2.7.2, I run into this problem:
>> >
>> > XXX.java: 0: Got an exception - java.lang.ClassCastException
>> >
>> > What is the problem?
>> >
>> > Willie
>> >
>> >
>> I think, I've ran into the same problem - and nothing to do with
>> the new checkstyle jar in my case. You cab check this by looking at
>> the checkstyle reports in target - they are all right at me.
>>
>> The problem is that in my project.xml I'm using the
>>
>> ${basedir}/src/java
>>
>> convention, and in the checkstyle jsl, that formats the raw checkstyle
>> report expects the sourceDirectory as a ${baseDir} relative value (line 56):
>>
>>
>> And the whole jsl processing is went wrog from this, as the transformer
>> would be working with a ${basedir}/ ${basedir}/
>> from here. Sometimes it causes exception, sometimes simply wrong.
>>
>> A dirty/quick cure to modify project.xml not to use ${basedir} (altough
>> if you use reactor you may get troubles with that). I'm thinking how to
>> patch the jsl script, just wrote this, maybe more knowledgeable jelliers
>> are faster at fix than I am.
>>
>> incze
However, my Project.xml uses relative "src/java" and I still have the same problem.
-
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/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-489) Checkstyle Error - "Got an exception - java.lang.ClassCastException "
The following comment has been added to this issue:
Author: Steve Ovens
Created: Sun, 29 Jun 2003 8:03 PM
Body:
Don't know if this helps narrow it down, but if I run a checkstyle report as part of
the "site" or "dist" goals, then I get the same problem - each source file reports a
"Class Cast Exception" on line 0, and in the System error output I see the message
"Can't find/access AST Node typecom.puppycrawl.tools.checkstyle.api.DetailAST".
However, if I subsequently run a "maven checkstyle" by itself, the checkstyle executes
correctly and the checkstyle-raw-report (and xml version of the report) are full of
the expected checkstyle errors.
My build source code is under src/java as specified in my project.xml file.
(src/java)
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-489
Here is an overview of the issue:
-
Key: MAVEN-489
Summary: Checkstyle Error - "Got an exception - java.lang.ClassCastException "
Type: New Feature
Status: Unassigned
Priority: Major
Time Spent: Unknown
Estimate: 0 minutes
Project: maven
Components:
plugin-other
Versions:
1.0-beta-10
Assignee:
Reporter: Nick Minutello
Created: Sat, 14 Jun 2003 6:05 AM
Updated: Mon, 23 Jun 2003 1:40 AM
Environment: JDK1.4.1_01 on Win2K
Description:
I have the latest HEAD build of Maven (built late 13th June GMT) and I am seeing this
error 100s of times over in the checkstyle report.
Error Line
Got an exception - java.lang.ClassCastException 0
Mailing list conversations:
On Fri, Jun 13, 2003 at 04:40:44PM +0800, Willie Vu wrote:
>> > Vincent,
>> >
>> > After I changed antlr plugin to use 2.7.2, I run into this problem:
>> >
>> > XXX.java: 0: Got an exception - java.lang.ClassCastException
>> >
>> > What is the problem?
>> >
>> > Willie
>> >
>> >
>> I think, I've ran into the same problem - and nothing to do with
>> the new checkstyle jar in my case. You cab check this by looking at
>> the checkstyle reports in target - they are all right at me.
>>
>> The problem is that in my project.xml I'm using the
>>
>> ${basedir}/src/java
>>
>> convention, and in the checkstyle jsl, that formats the raw checkstyle
>> report expects the sourceDirectory as a ${baseDir} relative value (line 56):
>>
>>
>> And the whole jsl processing is went wrog from this, as the transformer
>> would be working with a ${basedir}/ ${basedir}/
>> from here. Sometimes it causes exception, sometimes simply wrong.
>>
>> A dirty/quick cure to modify project.xml not to use ${basedir} (altough
>> if you use reactor you may get troubles with that). I'm thinking how to
>> patch the jsl script, just wrote this, maybe more knowledgeable jelliers
>> are faster at fix than I am.
>>
>> incze
However, my Project.xml uses relative "src/java" and I still have the same problem.
-
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/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]
[PATCH] maven/src/message/messages_zh_CN.properties
Hello, I created 'messages_zh_CN.properties' file based on the 'messages_zh_CN.properties' (existing one /binary) and performed "native2ascii -encoding EUC_CN". (maven/src/messages/messages_zh_CN.properties) I'll attach the file, named message_zh_CN.zip, zip compressed. Please uncompress this, delete the existing one (preferable), put the unzipped file to maven/src/messages/ directory and commit the file. Sincerely, -- Tetsuya ([EMAIL PROTECTED]) - Tetsuya Kitahata -- Terra-International, Inc. E-mail: [EMAIL PROTECTED] : [EMAIL PROTECTED] http://www.terra-intl.com/ (Apache Jakarta Translation, Japanese) http://jakarta.terra-intl.com/ message_zh_CN.zip Description: Zip compressed data - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MAVEN-522) Clarification of POM elements that use paths.
The following comment has been added to this issue:
Author: Brett Porter
Created: Sun, 29 Jun 2003 7:09 PM
Body:
The elements in question are:
<*sourceDirectory> (ie includeing unit tests, etc)
(under )
Indication from discussion on the mailing list is this:
- all paths in project.xml should not use ${basedir}, and should be considered
relative to project.xml. There is no need to have any absolute paths.
- all properties that specify files and use of files in maven.xml will have to have
${basedir} or absolute paths as there is no way to track CWD from there, or to know
which properties are files.
One other element of concern is within , as it is relative
to another base. For now, clear documentation will have to suffice unless a better
idea emerges.
I'm ready to work on this as soon as the refactoring of Project lands.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-522
Here is an overview of the issue:
-
Key: MAVEN-522
Summary: Clarification of POM elements that use paths.
Type: Task
Status: Unassigned
Priority: Major
Time Spent: Unknown
Estimate: 0 minutes
Project: maven
Assignee:
Reporter: Jason van Zyl
Created: Sat, 28 Jun 2003 8:13 AM
Updated: Sat, 28 Jun 2003 8:13 AM
Description:
Currently there are several elements in the POM that use paths in order to find
various resources. The currently accepted pattern is to use ${basedir} as a prefix for
all these paths so that they work in the reactor environment. We can certainly
identify all the elements in the POM that are path related. We need to decide whether
to mandate the use of ${basedir} or make it implicit in POM elements that store paths.
Once this is decided the plugins all need to be audited to ensure they follow the
pattern we mandate.
-
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/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]
Re: Use of Jelly scopes in plugins
With the repository plugin, the use of the parent scope is to 'return' a variable from a tag in a plugin. The use of the system scope is to access system properties. With the plugin plugin, it's used to read a property file into it's own scope and pass them as a single map back to the parent. These, or something to replace them are necessary. -- dIon Gillard, Multitask Consulting Blog: http://blogs.codehaus.org/people/dion/ Work: http://www.multitask.com.au Jason van Zyl <[EMAIL PROTECTED]> wrote on 30/06/2003 05:59:52 AM: > Howdy, > > The last hiccup I've run into is the jelly scope test in the touchstone > build. I looked at it and wondered why this is even needed so I looked > through the plugins and found all sorts of references to setting > variables with scopes. The following plugins have this attribute: > > clover > javadoc > junit-report > plugin > repository > > For anyone who added the use of scopes what exactly is the purpose? I'm > trying to clarify where things are defined and the exact behaviour of > contexts. Are these uses for cross-plugin communication? I would really > like to eliminate the use of scopes all together. > > -- > jvz. > > Jason van Zyl > [EMAIL PROTECTED] > http://tambora.zenplex.org > > In short, man creates for himself a new religion of a rational > and technical order to justify his work and to be justified in it. > > -- Jacques Ellul, The Technological Society > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
Use of Jelly scopes in plugins
Howdy, The last hiccup I've run into is the jelly scope test in the touchstone build. I looked at it and wondered why this is even needed so I looked through the plugins and found all sorts of references to setting variables with scopes. The following plugins have this attribute: clover javadoc junit-report plugin repository For anyone who added the use of scopes what exactly is the purpose? I'm trying to clarify where things are defined and the exact behaviour of contexts. Are these uses for cross-plugin communication? I would really like to eliminate the use of scopes all together. -- jvz. Jason van Zyl [EMAIL PROTECTED] http://tambora.zenplex.org In short, man creates for himself a new religion of a rational and technical order to justify his work and to be justified in it. -- Jacques Ellul, The Technological Society - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MAVEN-485) user guide documentation fix
Message: The following issue has been closed. Resolver: Emmanuel Venisse Date: Sun, 29 Jun 2003 1:39 PM Fixed by Jason - View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-485 Here is an overview of the issue: - Key: MAVEN-485 Summary: user guide documentation fix Type: Bug Status: Closed Priority: Trivial Resolution: FIXED Time Spent: Unknown Estimate: 1 minute Project: maven Components: documentation Fix Fors: 1.0-beta-10 Versions: 1.0-beta-10 Assignee: Emmanuel Venisse Reporter: Brett Porter Created: Fri, 13 Jun 2003 12:43 AM Updated: Sun, 29 Jun 2003 1:39 PM Description: please apply this patch to user-guide.xml It stops the guide implying you can create $MAVEN_HOME/bin/driver.properties and expect it to be used. - 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/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] Closed: (MAVEN-524) jellydoc expects relative path for pom.sourceDirectory
Message: The following issue has been closed. Resolver: dion gillard Date: Sun, 29 Jun 2003 1:29 PM Made them use full path. - View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-524 Here is an overview of the issue: - Key: MAVEN-524 Summary: jellydoc expects relative path for pom.sourceDirectory Type: Bug Status: Closed Priority: Major Resolution: FIXED Time Spent: Unknown Estimate: 0 minutes Project: maven Components: plugin-other Fix Fors: 1.0-beta-10 Versions: 1.0-beta-10 Assignee: dion gillard Reporter: dion gillard Created: Sun, 29 Jun 2003 1:11 PM Updated: Sun, 29 Jun 2003 1:29 PM Description: jellydoc:doclet: [echo] Generating jellydoc for packages org.apache.maven.* [echo] Source directory is C:\source\maven/C:\source\maven/src/java BUILD FAILED null:37:50: null:66:55: C:\source\maven\C not found. Total time: 1 minutes 31 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/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/plugins-build/jellydoc/xdocs changes.xml
dion2003/06/29 10:59:33
Modified:src/plugins-build/jellydoc project.xml plugin.jelly
Added: src/plugins-build/jellydoc/xdocs changes.xml
Log:
Remove ${basedir} from pom.build.sourceDirectory
Revision ChangesPath
1.11 +10 -1 maven/src/plugins-build/jellydoc/project.xml
Index: project.xml
===
RCS file: /home/cvs/maven/src/plugins-build/jellydoc/project.xml,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- project.xml 9 Apr 2003 01:06:46 - 1.10
+++ project.xml 29 Jun 2003 17:59:32 - 1.11
@@ -5,7 +5,7 @@
3
maven-jellydoc-plugin
Maven JellyDoc Plug-in
- 1.0
+ 1.1-SNAPSHOT
jakarta
@@ -23,6 +23,15 @@
jstrachan
[EMAIL PROTECTED]
SpiritSoft, Inc.
+
+Java Developer
+
+
+
+ dIon Gillard
+ dion
+ [EMAIL PROTECTED]
+ Apache Software Foundation
Java Developer
1.12 +3 -3 maven/src/plugins-build/jellydoc/plugin.jelly
Index: plugin.jelly
===
RCS file: /home/cvs/maven/src/plugins-build/jellydoc/plugin.jelly,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- plugin.jelly 30 Mar 2003 23:29:45 - 1.11
+++ plugin.jelly 29 Jun 2003 17:59:32 - 1.12
@@ -56,10 +56,10 @@
-Source directory is ${basedir}/${pom.build.sourceDirectory}
+Source directory is ${pom.build.sourceDirectory}
Changes
dIon Gillard
Kurt Schrader
Change use of pom.build.sourceDirectory to not include the basedir. This
must be placed in the pom
if a ${basedir} prefix is required.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MAVEN-524) jellydoc expects relative path for pom.sourceDirectory
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-524 Here is an overview of the issue: - Key: MAVEN-524 Summary: jellydoc expects relative path for pom.sourceDirectory Type: Bug Status: Unassigned Priority: Major Time Spent: Unknown Estimate: 0 minutes Project: maven Components: plugin-other Versions: 1.0-beta-10 Assignee: Reporter: dion gillard Created: Sun, 29 Jun 2003 1:11 PM Updated: Sun, 29 Jun 2003 1:11 PM Description: jellydoc:doclet: [echo] Generating jellydoc for packages org.apache.maven.* [echo] Source directory is C:\source\maven/C:\source\maven/src/java BUILD FAILED null:37:50: null:66:55: C:\source\maven\C not found. Total time: 1 minutes 31 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/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]
1.0-beta10 STATUS
We currently have the following 15 issues linked to MAVEN-401 that are outstanding http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-125 http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-461 http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-470 http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-473 http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-481 http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-482 http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-483 http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-485 http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-489 http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-491 http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-492 http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-493 http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-494 http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-495 http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-510 If any of these is unimportant for b10 or there are others that are important, please update MAVEN-401 ( http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-401 ) ASAP. Regards, -- dIon Gillard, Multitask Consulting Blog: http://blogs.codehaus.org/people/dion/ Work: http://www.multitask.com.au
[jira] Closed: (MAVEN-512) EJB Dependencies are not added to classpath
Message: The following issue has been closed. Resolver: dion gillard Date: Sun, 29 Jun 2003 12:50 PM jar and ejb types are added to the dependency classpath now - View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-512 Here is an overview of the issue: - Key: MAVEN-512 Summary: EJB Dependencies are not added to classpath Type: Bug Status: Closed Priority: Major Resolution: FIXED Time Spent: 5 minutes Estimate: 0 minutes Project: maven Components: core Fix Fors: 1.0-beta-10 Versions: 1.0-beta-10 Assignee: dion gillard Reporter: dion gillard Created: Sun, 22 Jun 2003 10:38 PM Updated: Sun, 29 Jun 2003 12:50 PM Description: Hi Folks, I'm using beta-9 sucessfully. A minor problem leads me to a new question: How does maven assebles maven.depedency.classpath? For instance the following dependencies _won't_ work with java:compile: jPortal-ejb ejb jPortal-ejb-0.6.1.jar jPortal-security ejb jPortal-security-0.1.5.jar It seems that java:compile will take care only on assemblies under jar/ and not under the type you mave configure. This coulde be very usefull if you try to assemble a modular enterprise application. Or is this against a strategy the maven.dependecy.classpath follows? Thx Toby - 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/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 DependencyClasspathBuilder.java
dion2003/06/29 10:25:34
Modified:src/java/org/apache/maven DependencyClasspathBuilder.java
Log:
Fix for MAVEN-512
Revision ChangesPath
1.11 +5 -7 maven/src/java/org/apache/maven/DependencyClasspathBuilder.java
Index: DependencyClasspathBuilder.java
===
RCS file: /home/cvs/maven/src/java/org/apache/maven/DependencyClasspathBuilder.java,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- DependencyClasspathBuilder.java 12 Apr 2003 00:02:05 - 1.10
+++ DependencyClasspathBuilder.java 29 Jun 2003 17:25:34 - 1.11
@@ -97,14 +97,12 @@
Artifact artifact = (Artifact) i.next();
Dependency d = artifact.getDependency();
-// Only add jar dependencies to the classpath
-if ( d.getType().equals( "jar" ) == false )
+// Only add jar or ejb (MAVEN-512) dependencies to the classpath
+if ( d.getType().equals("jar") || d.getType().equals("ejb") )
{
-continue;
+classpath.append( artifact.getPath() ).append( cps );
+project.setDependencyPath( d.getId(), artifact.getPath() );
}
-
-classpath.append( artifact.getPath() ).append( cps );
-project.setDependencyPath( d.getId(), artifact.getPath() );
}
return classpath.toString();
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MAVEN-523) java plugin not respecting fork settings
Message: The following issue has been closed. Resolver: dion gillard Date: Sun, 29 Jun 2003 12:00 PM It appears this has been fixed for quite some time. plugin.jelly for the java plugin doesn't use fork="" as a javac attribute - View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-523 Here is an overview of the issue: - Key: MAVEN-523 Summary: java plugin not respecting fork settings Type: Bug Status: Closed Priority: Minor Resolution: FIXED Time Spent: Unknown Estimate: 0 minutes Project: maven Components: plugin-java Fix Fors: 1.0-beta-10 Versions: 1.0-beta-10 Assignee: dion gillard Reporter: dion gillard Created: Sun, 29 Jun 2003 9:59 AM Updated: Sun, 29 Jun 2003 12:00 PM Description: In the Java jelly.plugin, it looks like fork is being set to true in all cases, even when I have maven.compile.fork=no in my project.properties (or my build.properties, or on the command line as a system property). What dumb thing am I doing wrong? Excerpt: [snip] [snip] In my case, that ant:setProperty call is not being picked up; fork is apparently always "yes". Cheers, Laird (new and enthusiastic Maven user) -- Laird J. Nelson Electronic Channel Group, Fidelity eBusiness (Veritude) - 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/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-461) Patches for JBuilder plugin
The following comment has been added to this issue: Author: dion gillard Created: Sun, 29 Jun 2003 11:40 AM Body: Not sure which are the correct files here and they're not diffs which makes it hard too - View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-461 Here is an overview of the issue: - Key: MAVEN-461 Summary: Patches for JBuilder plugin Type: Improvement Status: Unassigned Priority: Major Time Spent: Unknown Estimate: 1 day Project: maven Components: plugin-other Versions: 1.0-beta-9 Assignee: Reporter: David Zeleznik Created: Tue, 3 Jun 2003 5:08 PM Updated: Tue, 24 Jun 2003 1:48 PM Description: - The plugin attempts to find JBuilder's "HOME" directory where it will read the user's default project properties file. - The JBuilder "HOME" directory is also where library files are generated. This is a major rewrite of the JBuilder plugin that keeps backwards compatibility, while adding much more complete generation of project and library files. Some of the ideas have been borrowed from the latest versions of the IDEA and Eclipse plugins. Here is a short summary that covers some of the highlights: - The plugin attempts to find JBuilder's "HOME" directory where it will read the user's default project properties file. The JBuilder "HOME" directory is also where library files are generated. - When you generate a JBuilder project file, the plugin iterates through its dependencies. For each dependency, a library definition file is generated for the dependency jar in the local repo. This dependent library file is generated if, and only if, the library file does not already exist or the library file was previously generated the same way (as a dependency on a jar in the local repo). - The previous point means that when you generate a jbuilder library definition file directly from a Maven project (using the jbuilder:generate-library goal) you will replace any previous definition of the library that was generated as a jar-only dependency with a library definition that references both the source and class files. - For library definitions that remain jar-only references to the local repo, you can specify a path to the corresponding source code via properties. - Support has been added for generating JBuilder application and applet runtime configurations from properties. - Any resources are added to the JBuilder project source path. - Using an optional property, you can specify a list of explicit files that will be included in the JBuilder project if they exist. The default list are project.xml, project.properties, and maven.xml. - 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/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]
Unlinked from b10 release: MAVEN-454.
See previous justification... -- dIon Gillard, Multitask Consulting Blog: http://blogs.codehaus.org/people/dion/ Work: http://www.multitask.com.au
Removing Maven-465 from b10 release list
I don't feel that this issue is important enough to hold up the b10 release, and hence have unlinked it from MAVEN-401. If you feel strongly that it MUST be in b10, please relink the issue and vote for it. Regards, -- dIon Gillard, Multitask Consulting Blog: http://blogs.codehaus.org/people/dion/ Work: http://www.multitask.com.au
[jira] Closed: (MAVEN-453) exclude no in effect
Message: The following issue has been closed. Resolver: dion gillard Date: Sun, 29 Jun 2003 11:25 AM Done recently by Vincent - View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-453 Here is an overview of the issue: - Key: MAVEN-453 Summary: exclude no in effect Type: Bug Status: Closed Priority: Blocker Resolution: FIXED Time Spent: Unknown Estimate: 0 minutes Project: maven Fix Fors: 1.0-beta-10 Versions: 1.0-beta-10 Assignee: dion gillard Reporter: Kuisong Tong Created: Sat, 31 May 2003 10:32 PM Updated: Sun, 29 Jun 2003 11:25 AM Description: the exclude isn't in effect in the 2.0-snapshot.this is a patch. - 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/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]
[patch] torque plugin update
* use the torque-3.1-alpha2 release * upgrade some dependencies * change version to 3.2-SNAPSHOT Index: project.xml === RCS file: /home/cvspublic/maven/src/plugins-build/torque/project.xml,v retrieving revision 1.7 diff -u -r1.7 project.xml --- project.xml9 Apr 2003 01:06:49 -1.7 +++ project.xml29 Jun 2003 16:02:12 - @@ -5,7 +5,7 @@ 3 maven-torque-plugin Maven Torque Plug-in - 3.1 + 3.2-SNAPSHOT Maven Plugin for Torque Maven Plugin for Torque http://maven.apache.org/reference/plugins/torque/ @@ -73,7 +73,7 @@ commons-configuration - 20030311.152757 + 1.0-dev-3.20030607.194155 root @@ -93,8 +93,16 @@ + commons-logging + 1.0.3 + http://jakarta.apache.org/commons/ + +root + + + log4j - 1.2.7 + 1.2.8 root @@ -109,21 +117,21 @@ torque torque-gen - 20030327.070220 + 3.1-alpha2 root velocity - 1.3 + 1.3.1 root village - 2.0-dev-2002 + 2.0-dev-20030625 root - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven/src/plugins-build/clean/xdocs goals.xml changes.xml
dion2003/06/29 09:03:44
Modified:src/plugins-build/clean/xdocs goals.xml changes.xml
Log:
Fix docs
Revision ChangesPath
1.3 +0 -8 maven/src/plugins-build/clean/xdocs/goals.xml
Index: goals.xml
===
RCS file: /home/cvs/maven/src/plugins-build/clean/xdocs/goals.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- goals.xml 3 Jun 2003 06:36:56 - 1.2
+++ goals.xml 29 Jun 2003 16:03:43 - 1.3
@@ -18,14 +18,6 @@
clean:clean
Removes ${maven.build.dir} and
${basedir}/velocity.log.
-
-clean:classes
-Removes ${maven.build.dest} and ${maven.test.dest}
directories.
-
-
-clean:docs
-Removes the ${maven.gen.docs} and ${maven.docs.dest}
directories.
-
1.4 +3 -0 maven/src/plugins-build/clean/xdocs/changes.xml
Index: changes.xml
===
RCS file: /home/cvs/maven/src/plugins-build/clean/xdocs/changes.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- changes.xml 3 Jun 2003 06:36:56 - 1.3
+++ changes.xml 29 Jun 2003 16:03:43 - 1.4
@@ -7,6 +7,9 @@
+
+Remove clean:classes and clean:docs goals, as they are in an inappropriate
place
+
Apply docs patch, fix bad code in the clean:classes and clean:docs goals
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MAVEN-363) Determine if licensing has change for jfreechart and upload new version
Message: The following issue has been closed. Resolver: dion gillard Date: Sun, 29 Jun 2003 11:13 AM jfreechart 0.9.8 and jcommon 0.8.3 uploaded - View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-363 Here is an overview of the issue: - Key: MAVEN-363 Summary: Determine if licensing has change for jfreechart and upload new version Type: Task Status: Closed Priority: Trivial Resolution: FIXED Time Spent: Unknown Estimate: 3 days Project: maven Assignee: dion gillard Reporter: dion gillard Created: Tue, 1 Apr 2003 7:55 PM Updated: Sun, 29 Jun 2003 11:13 AM Environment: N/A Description: JFreeChart 0.9.6 - http://prdownloads.sourceforge.net/jfreechart/jfreechart-0.9.6.zip?download JCommon - http://prdownloads.sourceforge.net/jfreechart/jcommon-0.7.2.zip?download - 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/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] Closed: (MAVEN-451) patch for clean
Message: The following issue has been closed. Resolver: Jason van Zyl Date: Sun, 29 Jun 2003 11:12 AM Dion identified the cross plugin cleaning as not being appropriate so this is not an issue anymore. The clean plugin is strictly source related. - View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-451 Here is an overview of the issue: - Key: MAVEN-451 Summary: patch for clean Type: Bug Status: Closed Priority: Blocker Resolution: WON'T FIX Time Spent: Unknown Estimate: 0 minutes Project: maven Versions: 1.0-beta-10 Assignee: Jason van Zyl Reporter: Kuisong Tong Created: Sat, 31 May 2003 10:24 PM Updated: Sun, 29 Jun 2003 11:12 AM Description: clean:classes and clean:docs is crash, this is a patch for this - 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/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]
Re: cvs commit: maven/src/plugins-build/clean plugin.jelly
On Sun, 2003-06-29 at 11:43, [EMAIL PROTECTED] wrote: > dion2003/06/29 08:43:15 > > Modified:src/plugins-build/clean plugin.jelly > Log: > Remove goals that were cross plugin. > If someone wants clean:classes or clean:docs, then they should > be implemented in the plugins that create the directories: java, test and xdoc > > Revision ChangesPath > 1.5 +0 -12 maven/src/plugins-build/clean/plugin.jelly > > Index: plugin.jelly > === > RCS file: /home/cvs/maven/src/plugins-build/clean/plugin.jelly,v > retrieving revision 1.4 > retrieving revision 1.5 > diff -u -r1.4 -r1.5 > --- plugin.jelly3 Jun 2003 06:36:56 - 1.4 > +++ plugin.jelly29 Jun 2003 15:43:15 - 1.5 > @@ -13,16 +13,4 @@ > > > > - - description="Remove all build and test classes"> > - > - > - > - > - - description="Remove all docs and generated xdocs"> > - > - > - > - > Good call, those definitely shouldn't be in there. That issue dealing with this linked under 401 can be scrapped now. > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] -- jvz. Jason van Zyl [EMAIL PROTECTED] http://tambora.zenplex.org In short, man creates for himself a new religion of a rational and technical order to justify his work and to be justified in it. -- Jacques Ellul, The Technological Society - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven/src/plugins-build/clean plugin.jelly
dion2003/06/29 08:43:15 Modified:src/plugins-build/clean plugin.jelly Log: Remove goals that were cross plugin. If someone wants clean:classes or clean:docs, then they should be implemented in the plugins that create the directories: java, test and xdoc Revision ChangesPath 1.5 +0 -12 maven/src/plugins-build/clean/plugin.jelly Index: plugin.jelly === RCS file: /home/cvs/maven/src/plugins-build/clean/plugin.jelly,v retrieving revision 1.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- plugin.jelly 3 Jun 2003 06:36:56 - 1.4 +++ plugin.jelly 29 Jun 2003 15:43:15 - 1.5 @@ -13,16 +13,4 @@ - - - - - - - - - - - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MAVEN-363) Determine if licensing has change for jfreechart and upload new version
The following comment has been added to this issue: Author: dion gillard Created: Sun, 29 Jun 2003 10:43 AM Body: Looks LGPL to me - View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-363 Here is an overview of the issue: - Key: MAVEN-363 Summary: Determine if licensing has change for jfreechart and upload new version Type: Task Status: Assigned Priority: Trivial Time Spent: Unknown Estimate: 3 days Project: maven Assignee: dion gillard Reporter: dion gillard Created: Tue, 1 Apr 2003 7:55 PM Updated: Tue, 1 Apr 2003 7:55 PM Environment: N/A Description: JFreeChart 0.9.6 - http://prdownloads.sourceforge.net/jfreechart/jfreechart-0.9.6.zip?download JCommon - http://prdownloads.sourceforge.net/jfreechart/jcommon-0.7.2.zip?download - 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/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] Created: (MAVEN-523) java plugin not respecting fork settings
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-523 Here is an overview of the issue: - Key: MAVEN-523 Summary: java plugin not respecting fork settings Type: Bug Status: Unassigned Priority: Minor Time Spent: Unknown Estimate: 0 minutes Project: maven Components: plugin-java Versions: 1.0-beta-10 Assignee: Reporter: dion gillard Created: Sun, 29 Jun 2003 9:59 AM Updated: Sun, 29 Jun 2003 9:59 AM Description: In the Java jelly.plugin, it looks like fork is being set to true in all cases, even when I have maven.compile.fork=no in my project.properties (or my build.properties, or on the command line as a system property). What dumb thing am I doing wrong? Excerpt: [snip] [snip] In my case, that ant:setProperty call is not being picked up; fork is apparently always "yes". Cheers, Laird (new and enthusiastic Maven user) -- Laird J. Nelson Electronic Channel Group, Fidelity eBusiness (Veritude) - 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/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] Closed: (MAVEN-490) Jelly Errors (maven.log full of them)
Message: The following issue has been closed. Resolver: Jason van Zyl Date: Sun, 29 Jun 2003 9:13 AM Dion fixed this in CVS HEAD. - View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-490 Here is an overview of the issue: - Key: MAVEN-490 Summary: Jelly Errors (maven.log full of them) Type: Bug Status: Closed Priority: Major Resolution: FIXED Time Spent: Unknown Estimate: 0 minutes Project: maven Versions: 1.0-beta-10 Assignee: Jason van Zyl Reporter: Nick Minutello Created: Sat, 14 Jun 2003 2:02 PM Updated: Sun, 29 Jun 2003 9:13 AM Description: Building my current project seems to generate 10,000's of Jelly AntTag errors. Building Maven itself generates a few. Here are some examples ERROR org.apache.commons.jelly.tags.ant.AntTag - Class org.apache.commons.jelly.tags.core.IfTag doesn't support the nested "available" element. ERROR org.apache.commons.jelly.tags.ant.AntTag - Class com.werken.werkz.jelly.ProjectTag doesn't support the nested "path" element. WARN org.apache.commons.jelly.tags.ant.AntTag - Could not convert tag: td into an Ant task, data type or property There are some other errors with stack traces - I will attach two macen.logs - 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/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]
Re: [PATCH] maven/src/message/messages_ja.properties
confirmed. Sincerely, -- Tetsuya ([EMAIL PROTECTED]) - On Sun, 29 Jun 2003 23:48:31 +1000 (Subject: Re: [PATCH] maven/src/message/messages_ja.properties) Ben Walding <[EMAIL PROTECTED]> wrote: > Done. > > Tetsuya Kitahata wrote: > > >Hello, > > > >I created 'messages_ja.properties' file based on the > >'messages_en.properties' and performed "native2ascii". > >(maven/src/message/messages_ja.properties) > > > >I'll attach the file, named message_jp.zip, zip compressed. > > > >Please uncompress this, put the unzipped file to > >maven/src/message/ directory and commit the file. > > > >Sincerely, > > > >-- Tetsuya ([EMAIL PROTECTED]) - Tetsuya Kitahata -- Terra-International, Inc. E-mail: [EMAIL PROTECTED] : [EMAIL PROTECTED] http://www.terra-intl.com/ (Apache Jakarta Translation, Japanese) http://jakarta.terra-intl.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PATCH] maven/src/message/messages_ja.properties
Done. Tetsuya Kitahata wrote: Hello, I created 'messages_ja.properties' file based on the 'messages_en.properties' and performed "native2ascii". (maven/src/message/messages_ja.properties) I'll attach the file, named message_jp.zip, zip compressed. Please uncompress this, put the unzipped file to maven/src/message/ directory and commit the file. Sincerely, -- Tetsuya ([EMAIL PROTECTED]) - Tetsuya Kitahata -- Terra-International, Inc. E-mail: [EMAIL PROTECTED] : [EMAIL PROTECTED] http://www.terra-intl.com/ (Apache Jakarta Translation, Japanese) http://jakarta.terra-intl.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven/src/messages messages_ja.properties
bwalding2003/06/29 06:48:58
Added: src/messages messages_ja.properties
Log:
Japanese messages
Submitted by: Tetsuya Kitahata
Revision ChangesPath
1.1 maven/src/messages/messages_ja.properties
Index: messages_ja.properties
===
# --
# Project Verifier
# --
failed.download.warning=\u8b66\u544a\uff1a${1}
\u306e\u30c0\u30a6\u30f3\u30ed\u30fc\u30c9\u306b\u5931\u6557\u3057\u307e\u3057\u305f\u3002
remote.repository.disabled.warning=\u30ea\u30e2\u30fc\u30c8\u306b\u3042\u308b\u30ec\u30dd\u30b8\u30c8\u30ea\u306e\u4f7f\u7528\u304c\u4e0d\u53ef\u80fd\u3067\u3057\u305f\u3002
directory.nonexistant.warning=\u30c7\u30a3\u30ec\u30af\u30c8\u30ea\u300c${1}\u300d\u306f\u5b58\u5728\u3057\u307e\u305b\u3093\u3002\u30c7\u30a3\u30ec\u30af\u30c8\u30ea\u306e\u4f5c\u6210\u3092\u8a66\u307f\u3066\u3044\u307e\u3059\u3002
not.directory.warning=\u300c${1}\u300d\u306f\u30c7\u30a3\u30ec\u30af\u30c8\u30ea\u3067\u306f\u3042\u308a\u307e\u305b\u3093\u3002
not.writable.warning=\u300c${1}\u300d\u306f\u66f8\u304d\u8fbc\u307f\u53ef\u80fd\u3067\u306f\u3042\u308a\u307e\u305b\u3093\u3002
cannot.create.directory.warning=\u30c7\u30a3\u30ec\u30af\u30c8\u30ea\u300c${1}\u300d\u306e\u4f5c\u6210\u304c\u51fa\u6765\u307e\u305b\u3093\u3067\u3057\u305f\u3002
maven.repo.local.unset.warning=maven.repo.local
\u304c\u30bb\u30c3\u30c8\u3055\u308c\u3066\u304a\u308a\u307e\u305b\u3093\u3002
single.unsatisfied.dependency.error=\u30d3\u30eb\u30c9\u306e\u30d7\u30ed\u30bb\u30b9\u3092\u7d9a\u3051\u308b\u4e8b\u304c\u51fa\u6765\u307e\u305b\u3093\u3002\u4ee5\u4e0b\u306e\u4f9d\u5b58\u95a2\u4fc2\u304c\u6e80\u305f\u3055\u308c\u3066\u3044\u306a\u3044\u70ba\u3067\u3059\uff1a
multiple.unsatisfied.dependency.error=\u30d3\u30eb\u30c9\u306e\u30d7\u30ed\u30bb\u30b9\u3092\u7d9a\u3051\u308b\u4e8b\u304c\u51fa\u6765\u307e\u305b\u3093\u3002\u4ee5\u4e0b\u306e\u4f9d\u5b58\u95a2\u4fc2\u304c\u6e80\u305f\u3055\u308c\u3066\u3044\u306a\u3044\u70ba\u3067\u3059\uff1a
offline.snapshot.warning=\u30aa\u30d5\u30e9\u30a4\u30f3\u3067\u4f5c\u696d\u3057\u3066\u3044\u308b\u70ba\u3001\u30d3\u30eb\u30c9\u306e\u30d7\u30ed\u30bb\u30b9\u306f\u5f15\u304d\u7d9a\u3044\u3066\u884c\u308f\u308c\u307e\u3059\u304c\u3001\u300c${1}\u300d\u304c\u53e4\u3044\u53ef\u80fd\u6027\u304c\u3042\u308a\u307e\u3059\uff01
download.message=\u300c${1}\u300d\u306e\u30c0\u30a6\u30f3\u30ed\u30fc\u30c9\u3092\u8a66\u307f\u3066\u3044\u307e\u3059\u3002
plugin.loading.error=\u30d7\u30e9\u30b0\u30a4\u30f3\u300c${1}\u300d\u304c\u30ed\u30fc\u30c9\u51fa\u6765\u307e\u305b\u3093\u3067\u3057\u305f\u3002
empty.descriptor.error=\u6307\u5b9a\u3057\u305f\u30d5\u30a1\u30a4\u30eb\u300c${1}\u300d\u306e\u30b5\u30a4\u30ba\u304c\uff10\u3067\u3059\u3002
checksum.verification.error=\u4ee5\u4e0b\u306e\u7269\u304c\u58ca\u308c\u3066\u3044\u307e\u3059\uff1a${1}
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[PATCH] maven/src/message/messages_ja.properties
Hello, I created 'messages_ja.properties' file based on the 'messages_en.properties' and performed "native2ascii". (maven/src/message/messages_ja.properties) I'll attach the file, named message_jp.zip, zip compressed. Please uncompress this, put the unzipped file to maven/src/message/ directory and commit the file. Sincerely, -- Tetsuya ([EMAIL PROTECTED]) - Tetsuya Kitahata -- Terra-International, Inc. E-mail: [EMAIL PROTECTED] : [EMAIL PROTECTED] http://www.terra-intl.com/ (Apache Jakarta Translation, Japanese) http://jakarta.terra-intl.com/ message_ja.zip Description: Zip compressed data - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven/src/plugins-build/word2html/xdocs changes.xml
dion2003/06/29 06:39:58 Modified:src/plugins-build/word2html/xdocs changes.xml Log: Docs on latest changes Revision ChangesPath 1.3 +3 -0 maven/src/plugins-build/word2html/xdocs/changes.xml Index: changes.xml === RCS file: /home/cvs/maven/src/plugins-build/word2html/xdocs/changes.xml,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- changes.xml 18 Jun 2003 04:28:59 - 1.2 +++ changes.xml 29 Jun 2003 13:39:58 - 1.3 @@ -9,6 +9,9 @@ +Correctly handle files with .. in the names + + Open the word documents in readonly mode - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven/src/plugins-build/word2html/src/plugin-resources word2html.vbs
dion2003/06/29 06:39:03
Modified:src/plugins-build/word2html/src/plugin-resources
word2html.vbs
Log:
Fully resolve file names so that reactored builds with .. in the path are handled
correctly
Revision ChangesPath
1.4 +8 -7
maven/src/plugins-build/word2html/src/plugin-resources/word2html.vbs
Index: word2html.vbs
===
RCS file:
/home/cvs/maven/src/plugins-build/word2html/src/plugin-resources/word2html.vbs,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- word2html.vbs 18 Jun 2003 06:39:54 - 1.3
+++ word2html.vbs 29 Jun 2003 13:39:02 - 1.4
@@ -44,18 +44,19 @@
On Error Resume Next
HTMLFormat = 8
+' work out the directory structure for the input file
+Set FileSys = WScript.CreateObject("Scripting.FileSystemObject")
+
' Fully Qualified File name
-inputFile=WScript.Arguments(0)
+inputFile=FileSys.GetAbsolutePathName(WScript.Arguments(0))
' Directory to place results in
-outputDir=WScript.Arguments(1)
+outputDir=FileSys.GetAbsolutePathName(WScript.Arguments(1))
' base directory for the input file
-basedir = WScript.Arguments(2)
-' work out the directory structure for the input file
-Set FileSys = WScript.CreateObject("Scripting.FileSystemObject")
+basedir = FileSys.GetAbsolutePathName(WScript.Arguments(2))
outputFile = CreateOutputDirectories(basedir, inputFile, outputDir) & "\" & _
FileSys.GetBaseName(inputFile) & ".html"
-
+
Set obj = WScript.CreateObject("Word.Application")
obj.Visible = FALSE
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven/src/plugins-build/artifact project.xml
dion2003/06/29 06:23:54 Modified:src/plugins-build/artifact project.xml Log: Make it a snapshot Revision ChangesPath 1.5 +1 -1 maven/src/plugins-build/artifact/project.xml Index: project.xml === RCS file: /home/cvs/maven/src/plugins-build/artifact/project.xml,v retrieving revision 1.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- project.xml 29 Jun 2003 13:23:27 - 1.4 +++ project.xml 29 Jun 2003 13:23:54 - 1.5 @@ -5,7 +5,7 @@ 3 maven-artifact-plugin Maven Artifact Plug-in - 1.0 + 1.0-SNAPSHOT Tools to manage artifacts and deployment http://maven.apache.org/reference/plugins/artifact/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven/src/plugins-build/artifact project.xml
dion2003/06/29 06:23:27 Modified:src/plugins-build/artifact project.xml Log: Fix descriptions Revision ChangesPath 1.4 +2 -2 maven/src/plugins-build/artifact/project.xml Index: project.xml === RCS file: /home/cvs/maven/src/plugins-build/artifact/project.xml,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- project.xml 24 Jun 2003 22:22:55 - 1.3 +++ project.xml 29 Jun 2003 13:23:27 - 1.4 @@ -6,8 +6,8 @@ maven-artifact-plugin Maven Artifact Plug-in 1.0 - - Java Project Management Tools + + Tools to manage artifacts and deployment http://maven.apache.org/reference/plugins/artifact/ /www/maven.apache.org/reference/plugins/artifact/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: New 'reactor' plugin
On Sun, 2003-06-29 at 08:36, [EMAIL PROTECTED] wrote: > I'm open to name changes here, but lets get some consensus. > > I personally favour reactortools, but it's long winded, like multiproject. > Since the reactor is designed to do multiproject builds, maybe that makes > more sense. > > ok, so now I'm leaning towards multiproject. Any objections? Nope. > -- > dIon Gillard, Multitask Consulting > Blog: http://blogs.codehaus.org/people/dion/ > Work: http://www.multitask.com.au > > > Brian Ewins <[EMAIL PROTECTED]> wrote on 27/06/2003 > 11:21:50 PM: > > > > > > > Rafal Krzewski wrote: > > > > > I admit that having reactor tag (backed by reactor bean) and reactor > > > plugin may be confusing. Still I don't see any compelling alternative. > > > > > > > How about giving it a different name that new users would recognize? The > > > 'reactor' is something people only learn about by reading through the > > manual[1] or asking on the mailing lists. The name just isn't > > recognizable as doing what it does. > > > > Something like 'multiproject:build' is a bit more obvious than > > 'reactor:build' for example. Some other example names - mainly taken > > from what people use before they know about the reactor, or when > > describing the reactor: > > > > subprojects:build, subprojects:site [2] > > master:build, master:site > > masterproject:build, masterproject:site > > mainproject:build, mainproject:site > > aggregate:build, aggregate:site [3] > > > > Just a suggestion. > > > > -Baz > > > > [1] I know, I know, RTFM... > > [2] this is the one that makes most sense to me > > [3] the 'reactor' concept is called an aggregate build in the GNU make > > manual, I dont think the name is very clear though. > > > > > > > > Privacy and Confidentiality Notice > > > > > > > > The information contained in this E-Mail message is intended only > > for the person or persons to whom it is addressed. Such information > > is confidential and privileged and no mistake in transmission is > > intended to waive or compromise such privilege. If you have > > received it in error, please destroy it and notify us on the > > telephone number printed above. If you do not receive complete and > > legible copies, please telephone us immediately. Any opinions > > expressed herein including attachments are those of the author only. > > i-documentsystems Ltd. does not accept responsibility for the > > accuracy or completeness of the information provided or for any > > changes to this Email, however made, after it was sent. (Please note > > that it is your responsibility to scan this message for viruses). > > > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > -- jvz. Jason van Zyl [EMAIL PROTECTED] http://tambora.zenplex.org In short, man creates for himself a new religion of a rational and technical order to justify his work and to be justified in it. -- Jacques Ellul, The Technological Society - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven/src/plugins-build/artifact project.properties
dion2003/06/29 06:22:24
Modified:src/plugins-build/artifact project.properties
Log:
Fix properties for site publishing
Revision ChangesPath
1.2 +3 -0 maven/src/plugins-build/artifact/project.properties
Index: project.properties
===
RCS file: /home/cvs/maven/src/plugins-build/artifact/project.properties,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- project.properties16 Jun 2003 14:26:01 - 1.1
+++ project.properties29 Jun 2003 13:22:23 - 1.2
@@ -1,3 +1,6 @@
# ---
# P R O J E C T P R O P E R T I E S
# ---
+maven.xdoc.date=left
+maven.xdoc.version=${pom.currentVersion}
+maven.license.licenseFile=${basedir}/../../../LICENSE.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[Fwd: ScanMail Message: To Sender Match eManager setting and takeaction.]
Anyone else getting these when they commit files with bits of HTML in them? It seems a bit dubious to me... --- Begin Message --- eManager Notification * The following mail was blocked since it contains sensitive content. Source mailbox: [EMAIL PROTECTED] Destination mailbox(es): [EMAIL PROTECTED] Rule/Policy: Block HTML script messages Action: Delete Die Mail enthielt einen nicht zulaessigen Ausdruck, einen Automatischen Link oder war komplett in HTML formatiert (Bitte versenden Sie erneut im Text/RichText-Format (RTF)). Aus Sicherheitsgruenden wurde diese Mail NICHT ZUGESTELLT. *** End of message * --- End Message --- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven/src/plugins-build/artifact/xdocs authentication.xml properties.xml protocols.xml examples.xml tags.xml navigation.xml security.xml index.xml authentification.xml
bwalding2003/06/29 06:16:02 Modified:src/plugins-build/artifact/xdocs properties.xml protocols.xml examples.xml tags.xml navigation.xml security.xml index.xml Added: src/plugins-build/artifact/xdocs authentication.xml Removed: src/plugins-build/artifact/xdocs authentification.xml Log: Cleanup of doco by request. Revision ChangesPath 1.2 +10 -10maven/src/plugins-build/artifact/xdocs/properties.xml Index: properties.xml === RCS file: /home/cvs/maven/src/plugins-build/artifact/xdocs/properties.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- properties.xml29 Jun 2003 11:57:39 - 1.1 +++ properties.xml29 Jun 2003 13:16:02 - 1.2 @@ -2,7 +2,7 @@ -Maven Artifact Plugin Properties +Properties Michal Maczka @@ -50,29 +50,29 @@ maven.repo.x.directory -The path at remote file system where artifacts will be put +The path on the remote file system where artifacts will be placed No maven.repo.x.username - The user name which will be used to authetificated - user if access to repository requires authentification. + The user name that will be used to authenticated + user if access to repository requires authentication. Yes maven.repo.x.password -The password which will be used to authetificate +The password which will be used to authenticate user. -If server/protocol supports authetification via +If server/protocol supports authentication via both private/public keys and password, -first will try to use keys for authentication +it will first try to use keys for authentication and if that doesn't work then -we fall back to using the username and password +will fall back to using the username and password Yes @@ -88,10 +88,10 @@ maven.repo.x.privatekey - The absoluth path to private key file. + The absolute path to private key file. Thie is used only for when protocol - supports authetification via private/public + supports authetication via private/public key pair. Yes 1.2 +5 -5 maven/src/plugins-build/artifact/xdocs/protocols.xml Index: protocols.xml === RCS file: /home/cvs/maven/src/plugins-build/artifact/xdocs/protocols.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- protocols.xml 29 Jun 2003 11:57:39 - 1.1 +++ protocols.xml 29 Jun 2003 13:16:02 - 1.2 @@ -2,7 +2,7 @@ -Maven Artifact Plugin Properties +Protocols Michal Maczka @@ -32,7 +32,7 @@ Optional Optional Optional - Optional (deafult is 22) + Optional (default is 22) @@ -42,11 +42,11 @@ sftp:// Mandatory Mandatory - Mandatory if private key unless private key is provided + Mandatory unless private key is provided Optional Optional Optional - Optional (deafult is 22) + Optional (default is 22) FTP @@ -57,7 +57,7 @@ Not supported Not supported Not supported - Optional (deafult is 21) + Optional (default is 21) FILE 1.2 +4 -4 maven/src/plugins-build/artifact/xdocs/examples.xml Index: examples.xml === RCS file: /home/cvs/maven/src/plugins-build/artifact/xdocs/examples.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- examples.xml 29 Jun 2003 11:57:39 - 1.1 +++ examples.xml 29 Jun 2003 13:16:02 - 1.2 @@ -2,7 +2,7 @@ -Maven Artifact Plug-in Examples +Examples Tim Anderson @@ -10,7 +10,7 @@ The following example demonstrates how to depoyment -of artifact to remote repsoito
RE: cvs commit: maven/src/plugins-build/artifact/src/main/org/apache/maven/deployDeployRequest.java DeployTool.java
Michal, sounds like u need some mock objects -- dIon Gillard, Multitask Consulting Blog: http://blogs.codehaus.org/people/dion/ Work: http://www.multitask.com.au "Michal Maczka" <[EMAIL PROTECTED]> wrote on 29/06/2003 10:24:17 PM: > I have commited latest version of Artifact Plugin. > The most important addition is the documentation. > > I would like to use deploy, deploy-snapshot, install and install-snapshot > facility in other plugins. > > I have tested the code and it works for me. > The problem is that is quite difficult to automate tests of > this plugin (I habve to deploy using ssh, ftp etc) > > I have tested it on MS Windows plugin. > I will be grateful is somebody can check if documentation > is "correct" from the point of view of native speaker. > > I have also updated POM plugin and now it uses artifact plugin. > I have chosen this plugin as I think it is not so often > used. > > I will be grateful if somebody else can also test artifact plugin > (via using POM plugin) > > and see if > > pom:install > pom:deploy > pom:install-snapshot > pom:deploy-snapshot > > also work for you > > > Once I am sure that is works also on (L/U)nix machines and works for other > users > and hearing no objections > I would like to propagate the usage of this code in other places. > > regards > > Michal > > > -Original Message- > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > > Sent: Sunday, June 29, 2003 1:58 PM > > To: [EMAIL PROTECTED] > > Subject: cvs commit: > > maven/src/plugins-build/artifact/src/main/org/apache/maven/deploy > > DeployRequest.java DeployTool.java > > > > > > michal 2003/06/29 04:57:40 > > > > Modified: > > src/plugins-build/artifact/src/main/org/apache/maven/deploy/exceptions > > DeployException.java > > > > src/plugins-build/artifact/src/main/org/apache/maven/artifact/deployer > > DefaultArtifactDeployer.java DeployBean.java > > DeployRequestBuilder.java ArtifactDeployer.java > > > > src/plugins-build/artifact/src/main/org/apache/maven/deploy/deployers > > HttpDeployer.java FtpDeployer.java > > SFtpDeployer.java ScpDeployer.java > > FileDeployer.java Deployer.java > > GenericSshDeployer.java > > src/plugins-build/artifact/src/main/org/apache/maven/deploy > > DeployRequest.java DeployTool.java > > Added: > > src/plugins-build/artifact/src/main/org/apache/maven/deploy/exceptions > > UnsupportedProtocolException.java > > TransferFailedException.java > > WrongParameterException.java > >src/plugins-build/artifact/xdocs protocols.xml examples.xml > > index.xml tags.xml navigation.xml > > authentification.xml properties.xml changes.xml > > security.xml .cvsignore > > Removed: > > src/plugins-build/artifact/src/main/org/apache/maven/deploy/exceptions > > UnsupportedProtocolDeployException.java > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
Re: New 'reactor' plugin
I'm open to name changes here, but lets get some consensus. I personally favour reactortools, but it's long winded, like multiproject. Since the reactor is designed to do multiproject builds, maybe that makes more sense. ok, so now I'm leaning towards multiproject. Any objections? -- dIon Gillard, Multitask Consulting Blog: http://blogs.codehaus.org/people/dion/ Work: http://www.multitask.com.au Brian Ewins <[EMAIL PROTECTED]> wrote on 27/06/2003 11:21:50 PM: > > > Rafal Krzewski wrote: > > > I admit that having reactor tag (backed by reactor bean) and reactor > > plugin may be confusing. Still I don't see any compelling alternative. > > > > How about giving it a different name that new users would recognize? The > 'reactor' is something people only learn about by reading through the > manual[1] or asking on the mailing lists. The name just isn't > recognizable as doing what it does. > > Something like 'multiproject:build' is a bit more obvious than > 'reactor:build' for example. Some other example names - mainly taken > from what people use before they know about the reactor, or when > describing the reactor: > > subprojects:build, subprojects:site [2] > master:build, master:site > masterproject:build, masterproject:site > mainproject:build, mainproject:site > aggregate:build, aggregate:site [3] > > Just a suggestion. > > -Baz > > [1] I know, I know, RTFM... > [2] this is the one that makes most sense to me > [3] the 'reactor' concept is called an aggregate build in the GNU make > manual, I dont think the name is very clear though. > > > > Privacy and Confidentiality Notice > > > > The information contained in this E-Mail message is intended only > for the person or persons to whom it is addressed. Such information > is confidential and privileged and no mistake in transmission is > intended to waive or compromise such privilege. If you have > received it in error, please destroy it and notify us on the > telephone number printed above. If you do not receive complete and > legible copies, please telephone us immediately. Any opinions > expressed herein including attachments are those of the author only. > i-documentsystems Ltd. does not accept responsibility for the > accuracy or completeness of the information provided or for any > changes to this Email, however made, after it was sent. (Please note > that it is your responsibility to scan this message for viruses). > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
RE: cvs commit: maven/src/plugins-build/artifact/src/main/org/apache/maven/deploy DeployRequest.java DeployTool.java
I have commited latest version of Artifact Plugin. The most important addition is the documentation. I would like to use deploy, deploy-snapshot, install and install-snapshot facility in other plugins. I have tested the code and it works for me. The problem is that is quite difficult to automate tests of this plugin (I habve to deploy using ssh, ftp etc) I have tested it on MS Windows plugin. I will be grateful is somebody can check if documentation is "correct" from the point of view of native speaker. I have also updated POM plugin and now it uses artifact plugin. I have chosen this plugin as I think it is not so often used. I will be grateful if somebody else can also test artifact plugin (via using POM plugin) and see if pom:install pom:deploy pom:install-snapshot pom:deploy-snapshot also work for you Once I am sure that is works also on (L/U)nix machines and works for other users and hearing no objections I would like to propagate the usage of this code in other places. regards Michal > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Sunday, June 29, 2003 1:58 PM > To: [EMAIL PROTECTED] > Subject: cvs commit: > maven/src/plugins-build/artifact/src/main/org/apache/maven/deploy > DeployRequest.java DeployTool.java > > > michal 2003/06/29 04:57:40 > > Modified: > src/plugins-build/artifact/src/main/org/apache/maven/deploy/exceptions > DeployException.java > > src/plugins-build/artifact/src/main/org/apache/maven/artifact/deployer > DefaultArtifactDeployer.java DeployBean.java > DeployRequestBuilder.java ArtifactDeployer.java > > src/plugins-build/artifact/src/main/org/apache/maven/deploy/deployers > HttpDeployer.java FtpDeployer.java > SFtpDeployer.java ScpDeployer.java > FileDeployer.java Deployer.java > GenericSshDeployer.java >src/plugins-build/artifact/src/main/org/apache/maven/deploy > DeployRequest.java DeployTool.java > Added: > src/plugins-build/artifact/src/main/org/apache/maven/deploy/exceptions > UnsupportedProtocolException.java > TransferFailedException.java > WrongParameterException.java >src/plugins-build/artifact/xdocs protocols.xml examples.xml > index.xml tags.xml navigation.xml > authentification.xml properties.xml changes.xml > security.xml .cvsignore > Removed: > src/plugins-build/artifact/src/main/org/apache/maven/deploy/exceptions > UnsupportedProtocolDeployException.java - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: maven/src/plugins-build/pom plugin.jelly
michal 2003/06/29 05:23:07 Modified:src/plugins-build/pom plugin.jelly Log: maven-artifact-plugin used for deployment/installation Revision ChangesPath 1.9 +47 -18maven/src/plugins-build/pom/plugin.jelly Index: plugin.jelly === RCS file: /home/cvs/maven/src/plugins-build/pom/plugin.jelly,v retrieving revision 1.8 retrieving revision 1.9 diff -u -r1.8 -r1.9 --- plugin.jelly 20 Apr 2003 06:32:20 - 1.8 +++ plugin.jelly 29 Jun 2003 12:23:07 - 1.9 @@ -3,9 +3,10 @@ + xmlns:util="jelly:util" + xmlns:artifact="artifact" + > @@ -74,10 +75,10 @@ - - + @@ -91,19 +92,47 @@ - - - - - - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Deploy API (artifact plugin)
distributionSite and distributionDirectory are used for 'publishing' the generated site and other artifacts, the central repo is a global space where many projects artifacts are published. -- dIon Gillard, Multitask Consulting Blog: http://blogs.codehaus.org/people/dion/ Work: http://www.multitask.com.au Michal Maczka <[EMAIL PROTECTED]> wrote on 27/06/2003 06:12:25 PM: > > > > -Original Message- > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > > Sent: Friday, June 27, 2003 6:16 AM > > To: Maven Developers List > > Subject: RE: Deploy API (artifact plugin) > > > > I think I've asked this before, but AFAIK, > > > > distributionSiteare not related AT ALL to > > maven.repo.central. > > > > > Last time you asked: > > " > > maven.apache.org > > /www/maven.apache.org/ > This is the web site address and directory, not a repo???" > > :) > > I was sure that you just wanted to get sure that I use distributionSite and > distributionDirectory. > > > > distributionSite is not described in > http://maven.apache.org/reference/project-descriptor.html > > > While > distributionDirectory: > > Optional. The directory on the web server where the final distributions will > be published. This is used when the distributions are deployed > > (the word deployed is a hyper link which points to "site" plugin) > > > I though that "final distributions" are the distribution of artifacts > delivered by projects: jars, javadoc, project src zipped, > > Now I see I finaly understand that you might want e.g to publish > "distribution" of > entire project at sourceforge... and not to deploy to any repository. > > > > If I am still wrong: can you then explain briefly the difference? > > I want to centralized the code which does remote copying of the files > And I see now that "distribution" requires special handling ... I will/want > to change my code to support it. > > BTW: > > For the moment I have tested my API with username, user password > kept in properties file. I think such approach is not acceptable. > > You can use command line to pass properties to maven: > > maven war:deloy -Dmaven.repo.ibiblio.password = ** > > > This is already better ... but still not perfect. > > I will try to implement/use(if I find one) simple "Prompter" which will ask > to type your password (eventually to enter other required parameters which > are missing) > > regards > > > Michal > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
Re: New 'reactor' plugin
This is a plugin with properties to help use the standard reactor. It means that using the standard reactor doesn't have to involve writing jelly in maven.xml. -- dIon Gillard, Multitask Consulting Blog: http://blogs.codehaus.org/people/dion/ Work: http://www.multitask.com.au Jason van Zyl <[EMAIL PROTECTED]> wrote on 27/06/2003 10:39:13 PM: > On Fri, 2003-06-27 at 03:19, [EMAIL PROTECTED] wrote: > > I've just added this plugin as it has come in handy when working with > > multiple projects in my day job. > > How is this different than the standard reactor? Please don't name it > the reactor as having two entities with the same name will be confusing. > > > I haven't yet add the site aggregation I was hoping to have done by now. > > > > The plan is to allow for multiple strategies for implementing site > > aggregation: > > 1) independent sites, ala db.apache.org and subprojects with templated > > navigation > > 2) aggregated site where site docs are copied to > > masterProject/target/docs/ at completion > > 3) custom aggregation > > > > If anyone wants to help, let me know > > -- > > dIon Gillard, Multitask Consulting > > Blog: http://blogs.codehaus.org/people/dion/ > > Work: http://www.multitask.com.au > -- > jvz. > > Jason van Zyl > [EMAIL PROTECTED] > http://tambora.zenplex.org > > In short, man creates for himself a new religion of a rational > and technical order to justify his work and to be justified in it. > > -- Jacques Ellul, The Technological Society > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
RE: New 'reactor' plugin
I believe this is included as the reactor:goal goal.
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
Work: http://www.multitask.com.au
Michal Maczka <[EMAIL PROTECTED]> wrote on 27/06/2003 06:18:01 PM:
> I also need it!
>
> Just in case you find it useful/worthed to put to this plugin:
>
>
> I often use such "generic" goal (bit modified here, hope that it still
> works)
>
> name="reactor:for-all">
>
>basedir="${basedir}/.."
> includes="${includes}"
> excludes="${excludes}"
> goals="${goals}"
> banner="Building"
> ignoreFailures="false"
> />
>
>
> Then from command line
>
> maven reactor:for-all -Dgoals=jar:install-snapshot
>
>
> I find it very useful.
>
> Michal
>
>
> > -Original Message-
> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> > Sent: Friday, June 27, 2003 9:19 AM
> > To: [EMAIL PROTECTED]
> > Subject: New 'reactor' plugin
> >
> > I've just added this plugin as it has come in handy when working with
> > multiple projects in my day job.
> >
> > I haven't yet add the site aggregation I was hoping to have done by
now.
> >
> > The plan is to allow for multiple strategies for implementing site
> > aggregation:
> > 1) independent sites, ala db.apache.org and subprojects with templated
> > navigation
> > 2) aggregated site where site docs are copied to
> > masterProject/target/docs/ at completion
> > 3) custom aggregation
> >
> > If anyone wants to help, let me know
> > --
> > dIon Gillard, Multitask Consulting
> > Blog: http://blogs.codehaus.org/people/dion/
> > Work: http://www.multitask.com.au
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
Re: Aligning plugin artifacts with normal projects
As well, Ant already has an xml format for it's properties. See http://ant.apache.org/manual/CoreTasks/xmlproperty.html -- dIon Gillard, Multitask Consulting Blog: http://blogs.codehaus.org/people/dion/ Work: http://www.multitask.com.au Rafal Krzewski <[EMAIL PROTECTED]> wrote on 27/06/2003 06:20:10 PM: > [EMAIL PROTECTED] wrote: > > >>We also need it for documentation. Its quite common for people to ask > >>'what property do I set to do' because there are so many > >>undocumented properties. If there was a metadata file that described > >>plugin properties, it could be used to generate the xdocs. > > > > There is one. It's called plugin.properties, and it can be used to > > generate the xdocs :-) > > We could probably make a contract that the comment block directly above > the property contains it's description, but I'm not sure if this is > what we really want? > > Generating an xdoc from the property files itself has an advantage > of "on the spot" documentation, just like JavaDoc - you can read it in > the Java source, but also in the generated HTML pages. We also don't > have two files that need to be kept in sync (humans *always* forget...) > > We could go the other way around, and generated plugin.properties files > from the metadata, to lift the need for synchronizing files. > Descriptions in the metadata file could be emmited into the file as > well. The metadata file would be xml (seems natural to me), so we > could have a schema for it and take advantage of validation. On the > other hand, should we really introduce a new format for specifying > properties? > > Given the choice I'd probably stay with .properties files only, > and write the PropertyDoc thingy. > > > The reason the documentation is lacking is noone has been willing to > > do it. > > True. No matter which way we go - metadata files, or "PropertiesDoc" > plugin maintainers will have to fill in the descriptions anyway... > > R. > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
cvs commit: maven/src/plugins-build/artifact/src/main/org/apache/maven/deploy DeployRequest.java DeployTool.java
michal 2003/06/29 04:57:40
Modified:src/plugins-build/artifact/src/main/org/apache/maven/deploy/exceptions
DeployException.java
src/plugins-build/artifact/src/main/org/apache/maven/artifact/deployer
DefaultArtifactDeployer.java DeployBean.java
DeployRequestBuilder.java ArtifactDeployer.java
src/plugins-build/artifact/src/main/org/apache/maven/deploy/deployers
HttpDeployer.java FtpDeployer.java
SFtpDeployer.java ScpDeployer.java
FileDeployer.java Deployer.java
GenericSshDeployer.java
src/plugins-build/artifact/src/main/org/apache/maven/deploy
DeployRequest.java DeployTool.java
Added: src/plugins-build/artifact/src/main/org/apache/maven/deploy/exceptions
UnsupportedProtocolException.java
TransferFailedException.java
WrongParameterException.java
src/plugins-build/artifact/xdocs protocols.xml examples.xml
index.xml tags.xml navigation.xml
authentification.xml properties.xml changes.xml
security.xml .cvsignore
Removed: src/plugins-build/artifact/src/main/org/apache/maven/deploy/exceptions
UnsupportedProtocolDeployException.java
Log:
Code clean-up and docs provided
Revision ChangesPath
1.2 +3 -3
maven/src/plugins-build/artifact/src/main/org/apache/maven/deploy/exceptions/DeployException.java
Index: DeployException.java
===
RCS file:
/home/cvs/maven/src/plugins-build/artifact/src/main/org/apache/maven/deploy/exceptions/DeployException.java,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- DeployException.java 17 Jun 2003 22:06:00 - 1.1
+++ DeployException.java 29 Jun 2003 11:57:39 - 1.2
@@ -58,11 +58,11 @@
/**
- *
+ * Root class for all exception thrown by Deployers
* @author Michal Maczka
* @version $Id$
*/
-public class DeployException extends Exception
+public abstract class DeployException extends Exception
{
private final String message;
private final Throwable cause;
1.1
maven/src/plugins-build/artifact/src/main/org/apache/maven/deploy/exceptions/UnsupportedProtocolException.java
Index: UnsupportedProtocolException.java
===
package org.apache.maven.deploy.exceptions;
/*
* The Apache Software License, Version 1.1
*
* Copyright (c) 2003 The Apache Software Foundation. All rights
* reserved.
*
* Redistribution and use in source and binary forms, with or without
* modification, are permitted provided that the following conditions
* are met:
*
* 1. Redistributions of source code must retain the above copyright
*notice, this list of conditions and the following disclaimer.
*
* 2. Redistributions in binary form must reproduce the above copyright
*notice, this list of conditions and the following disclaimer in
*the documentation and/or other materials provided with the
*distribution.
*
* 3. The end-user documentation included with the redistribution,
*if any, must include the following acknowledgment:
* "This product includes software developed by the
*Apache Software Foundation (http://www.apache.org/)."
*Alternately, this acknowledgment may appear in the software itself,
*if and wherever such third-party acknowledgments normally appear.
*
* 4. The names "Apache" and "Apache Software Foundation" and
*"Apache Maven" must not be used to endorse or promote products
*derived from this software without prior written permission. For
*written permission, please contact [EMAIL PROTECTED]
*
* 5. Products derived from this software may not be called "Apache",
*"Apache Maven", nor may "Apache" appear in their name, without
*prior written permission of the Apache Software Foundation.
*
* THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED
* WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
* OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
* DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR
* ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
* SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
* LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF
* USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
* ON ANY
cvs commit: maven/src/plugins-build/artifact/xdocs - New directory
michal 2003/06/29 04:57:08 maven/src/plugins-build/artifact/xdocs - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MAVEN-509) upload nanning 0.8 to repo
Message: The following issue has been closed. Resolver: Ben Walding Date: Sun, 29 Jun 2003 5:27 AM Done. Still need a license file though - View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-509 Here is an overview of the issue: - Key: MAVEN-509 Summary: upload nanning 0.8 to repo Type: Task Status: Closed Priority: Major Resolution: FIXED Time Spent: Unknown Estimate: 0 minutes Project: maven Components: Repo Jar Requests Assignee: Ben Walding Reporter: Jon Tirsen Created: Sat, 21 Jun 2003 2:09 PM Updated: Sun, 29 Jun 2003 5:27 AM Description: The following 'script' can be used to accomplish this: wget http://nanning.sourceforge.net/maven-repo/nanning/jars/nanning-0.8.jar wget http://nanning.sourceforge.net/maven-repo/nanning/jars/nanning-contract-0.8.jar wget http://nanning.sourceforge.net/maven-repo/nanning/jars/nanning-locking-0.8.jar wget http://nanning.sourceforge.net/maven-repo/nanning/jars/nanning-profiler-0.8.jar - 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/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/plugins-build/jnlp/xdocs changes.xml properties.xml
evenisse2003/06/29 02:28:11
Modified:src/plugins-build/jnlp plugin.jelly project.xml
src/plugins-build/jnlp/xdocs changes.xml properties.xml
Log:
Fix generated jnlp file. We use now the correct tag for argument main class.
Sysproperty isn't in jnlp dtd.
Revision ChangesPath
1.10 +2 -2 maven/src/plugins-build/jnlp/plugin.jelly
Index: plugin.jelly
===
RCS file: /home/cvs/maven/src/plugins-build/jnlp/plugin.jelly,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- plugin.jelly 24 Apr 2003 13:41:31 - 1.9
+++ plugin.jelly 29 Jun 2003 09:28:11 - 1.10
@@ -121,7 +121,7 @@
${maven.jnlp.mainclass.arguments}
-
+ ${someArgument}
@@ -135,7 +135,7 @@
${maven.jnlp.mainclass.arguments}
-
+ ${someArgument}
1.10 +1 -1 maven/src/plugins-build/jnlp/project.xml
Index: project.xml
===
RCS file: /home/cvs/maven/src/plugins-build/jnlp/project.xml,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- project.xml 24 Apr 2003 13:06:22 - 1.9
+++ project.xml 29 Jun 2003 09:28:11 - 1.10
@@ -5,7 +5,7 @@
3
maven-jnlp-plugin
Maven JNLP Plug-in
- 1.1
+ 1.2-SNAPSHOT
JNLP Plugin for Maven
http://maven.apache.org/reference/plugins/jnlp/
/www/maven.apache.org/reference/plugins/jnlp/
1.2 +6 -0 maven/src/plugins-build/jnlp/xdocs/changes.xml
Index: changes.xml
===
RCS file: /home/cvs/maven/src/plugins-build/jnlp/xdocs/changes.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- changes.xml 24 Apr 2003 13:06:22 - 1.1
+++ changes.xml 29 Jun 2003 09:28:11 - 1.2
@@ -3,9 +3,15 @@
Changes
dIon Gillard
+Emmanuel Venisse
+
+
+Fix generated jnlp file. We use now argument tag instead of sysproperty tag.
+
+
Add the possibility to choose the main jar.
1.5 +8 -0 maven/src/plugins-build/jnlp/xdocs/properties.xml
Index: properties.xml
===
RCS file: /home/cvs/maven/src/plugins-build/jnlp/xdocs/properties.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- properties.xml24 Apr 2003 13:06:22 - 1.4
+++ properties.xml29 Jun 2003 09:28:11 - 1.5
@@ -238,6 +238,14 @@
+
+ maven.jnlp.mainclass.arguments
+ Yes
+
+The argument list for the main class. All arguments are separated by a
space.
+
+
+
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Results of clean bootstrap at 20030629-0317
Last 500 lines of a clean bootstrap build of maven at 20030629-0317 U maven/src/plugins-build/xdoc/src/plugin-resources/images/icon_alert.gif U maven/src/plugins-build/xdoc/src/plugin-resources/images/nw_min.gif U maven/src/plugins-build/xdoc/src/plugin-resources/images/remove.gif U maven/src/plugins-build/xdoc/src/plugin-resources/images/strich.gif U maven/src/plugins-build/xdoc/src/plugin-resources/images/sw_min.gif U maven/src/plugins-build/xdoc/src/plugin-resources/images/update.gif cvs server: Updating maven/src/plugins-build/xdoc/src/plugin-resources/images/logos U maven/src/plugins-build/xdoc/src/plugin-resources/images/logos/maven-bolt.png U maven/src/plugins-build/xdoc/src/plugin-resources/images/logos/maven-brewed.png U maven/src/plugins-build/xdoc/src/plugin-resources/images/logos/maven-build-successfull.png U maven/src/plugins-build/xdoc/src/plugin-resources/images/logos/maven-built.png U maven/src/plugins-build/xdoc/src/plugin-resources/images/logos/maven-bulldozer.png U maven/src/plugins-build/xdoc/src/plugin-resources/images/logos/maven-button-1.png U maven/src/plugins-build/xdoc/src/plugin-resources/images/logos/maven-button-2.png U maven/src/plugins-build/xdoc/src/plugin-resources/images/logos/maven-button-3.png U maven/src/plugins-build/xdoc/src/plugin-resources/images/logos/maven-button-4.png U maven/src/plugins-build/xdoc/src/plugin-resources/images/logos/maven-button-5.png U maven/src/plugins-build/xdoc/src/plugin-resources/images/logos/maven-button-black.png U maven/src/plugins-build/xdoc/src/plugin-resources/images/logos/maven-button-blue.png U maven/src/plugins-build/xdoc/src/plugin-resources/images/logos/maven-button-copper.png U maven/src/plugins-build/xdoc/src/plugin-resources/images/logos/maven-button-green.png U maven/src/plugins-build/xdoc/src/plugin-resources/images/logos/maven-button-pinky.png U maven/src/plugins-build/xdoc/src/plugin-resources/images/logos/maven-button-purple.png U maven/src/plugins-build/xdoc/src/plugin-resources/images/logos/maven-button-teal.png U maven/src/plugins-build/xdoc/src/plugin-resources/images/logos/maven-feather.png U maven/src/plugins-build/xdoc/src/plugin-resources/images/logos/maven-frankenstein.png U maven/src/plugins-build/xdoc/src/plugin-resources/images/logos/maven-mavenfactured.png U maven/src/plugins-build/xdoc/src/plugin-resources/images/logos/maven-petesucks.png U maven/src/plugins-build/xdoc/src/plugin-resources/images/logos/maven-propaganda-2.png U maven/src/plugins-build/xdoc/src/plugin-resources/images/logos/maven-propaganda.png U maven/src/plugins-build/xdoc/src/plugin-resources/images/logos/maven-redgreen.png cvs server: Updating maven/src/plugins-build/xdoc/src/plugin-resources/jelly-templates U maven/src/plugins-build/xdoc/src/plugin-resources/jelly-templates/cvs-usage.xml U maven/src/plugins-build/xdoc/src/plugin-resources/jelly-templates/dependencies.xml U maven/src/plugins-build/xdoc/src/plugin-resources/jelly-templates/index.xml U maven/src/plugins-build/xdoc/src/plugin-resources/jelly-templates/issue-tracking.xml U maven/src/plugins-build/xdoc/src/plugin-resources/jelly-templates/mail-lists.xml U maven/src/plugins-build/xdoc/src/plugin-resources/jelly-templates/maven-reports.xml U maven/src/plugins-build/xdoc/src/plugin-resources/jelly-templates/project-info.xml U maven/src/plugins-build/xdoc/src/plugin-resources/jelly-templates/team-list.xml cvs server: Updating maven/src/plugins-build/xdoc/src/plugin-resources/templates U maven/src/plugins-build/xdoc/src/plugin-resources/templates/cvs-usage.xml U maven/src/plugins-build/xdoc/src/plugin-resources/templates/dependencies.xml U maven/src/plugins-build/xdoc/src/plugin-resources/templates/index.xml U maven/src/plugins-build/xdoc/src/plugin-resources/templates/issue-tracking.xml U maven/src/plugins-build/xdoc/src/plugin-resources/templates/mail-lists.xml U maven/src/plugins-build/xdoc/src/plugin-resources/templates/maven-reports.xml U maven/src/plugins-build/xdoc/src/plugin-resources/templates/project-info.xml U maven/src/plugins-build/xdoc/src/plugin-resources/templates/team-list.xml cvs server: Updating maven/src/plugins-build/xdoc/src/test U maven/src/plugins-build/xdoc/src/test/.cvsignore U maven/src/plugins-build/xdoc/src/test/project.properties U maven/src/plugins-build/xdoc/src/test/project.xml cvs server: Updating maven/src/plugins-build/xdoc/src/test/org cvs server: Updating maven/src/plugins-build/xdoc/src/test/org/apache cvs server: Updating maven/src/plugins-build/xdoc/src/test/org/apache/maven U maven/src/plugins-build/xdoc/src/test/org/apache/maven/NavBeanTest.java cvs server: Updating maven/src/plugins-build/xdoc/src/test/xdocs U maven/src/plugins-build/xdoc/src/test/xdocs/index.xml U maven/src/plugins-build/xdoc/src/test/xdocs/navigation.xml cvs server: Updating maven/src/plugins-build/xdoc/src/test/xdocs/alpha U maven/src/plugins-build/xdoc/src/test/xdocs/alpha/index.xml cvs server: Updating maven/src/plugins-build/xdoc/src/test/xdocs/alpha/one U maven
ejb, war, ear patches + little jboss plugin suggestion
Hi Everyone, Attached are maven ejb, war and ear plugin patches, based on a 2 weeks old discussion on maven-users (titled 'j2ee workflow' if I remember correctly). I was hoping to get this emailed earlier but got caught up with other things. 1. ejb patch = the basic idea is to get ejb plugin in line with jar,war,ear plugins (e.g. things like install, install-snapshot deploy, etc). 2. war plugin suggestion - maybe maven.final.name should be used as a basis for the war file name rather than pom.artifactId to be consistent? 2. ear patch = the idea is to be able to package in project's own war or jar file without having to create a whole new POM just for that. Here is a simple example: given the following project.xml extract: bla.for.war SNAPSHOT true bla.for.ear SNAPSHOT true ejb.for.ear SNAPSHOT true ejb and the following in project.properties: maven.ear.include.project.war=true maven.project.context-root=/test given the above, you could produce a war file, an ear file (as usual) and optionally package in project's own war file (including generating the descriptor). The same logic applies for project's jar file (if any). 4. jboss plugin.properties I've noticed the that JXM deploy/undeploy URL in jboss 3.2 is slightly different from what was originally in the plugin.properties. I was wondering if one of the committers could have a quick look through the attached patches and see if these suggestions are of any use. thanks in advance. dima - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
