[jira] Updated: (CONTINUUM-311) add JDK and OS name to the build result mail (web?)
[ http://jira.codehaus.org/browse/CONTINUUM-311?page=all ] Emmanuel Venisse updated CONTINUUM-311: --- Fix Version: (was: 1.0-beta-1) 1.0-alpha-4 add JDK and OS name to the build result mail (web?) --- Key: CONTINUUM-311 URL: http://jira.codehaus.org/browse/CONTINUUM-311 Project: Continuum Type: New Feature Reporter: Brett Porter Fix For: 1.0-alpha-4 if you can sneak this into alpha-4, that'd be great! -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (CONTINUUM-311) add JDK and OS name to the build result mail (web?)
[ http://jira.codehaus.org/browse/CONTINUUM-311?page=all ] Emmanuel Venisse closed CONTINUUM-311: -- Resolution: Fixed Done in mail. I'll add it to the build result screen later. add JDK and OS name to the build result mail (web?) --- Key: CONTINUUM-311 URL: http://jira.codehaus.org/browse/CONTINUUM-311 Project: Continuum Type: New Feature Reporter: Brett Porter Assignee: Emmanuel Venisse Fix For: 1.0-alpha-4 Original Estimate: 30 minutes Time Spent: 30 minutes Remaining: 0 minutes if you can sneak this into alpha-4, that'd be great! -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[continuum build - SUCCESS - update] Wed Sep 14 15:30:03 GMT 2005
Distribution: http://maven.zones.apache.org/~continuum/builds/continuum-20050914.153003.tar.gz Log: http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20050914.153003.txt
[continuum build - SUCCESS - checkout] Thu Sep 15 00:30:00 GMT 2005
Distribution: http://maven.zones.apache.org/~continuum/builds/continuum-20050915.003000.tar.gz Log: http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20050915.003000.txt
[jira] Updated: (MNG-842) release plugin creates tag that truncates path information after /trunk/ in the original
[ http://jira.codehaus.org/browse/MNG-842?page=all ] Brett Porter updated MNG-842: - Component: (was: maven-plugins) maven-release-plugin release plugin creates tag that truncates path information after /trunk/ in the original Key: MNG-842 URL: http://jira.codehaus.org/browse/MNG-842 Project: Maven 2 Type: Bug Components: maven-release-plugin Reporter: Brett Porter witness modello: modello-1.0-alpha-4 is created instead of modello-1.0-alpha-4/modello (prefer the first layout, but that doesn't match how the SCM is set up) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MNG-884) release:perform doesn't work at all without release.properties
release:perform doesn't work at all without release.properties -- Key: MNG-884 URL: http://jira.codehaus.org/browse/MNG-884 Project: Maven 2 Type: Bug Components: maven-release-plugin Reporter: Brett Porter it should be able to derive this from the mojo configuration in most cases -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MNG-885) no project definition leads to NPE in plugin parameter expression evaluator
no project definition leads to NPE in plugin parameter expression evaluator
---
Key: MNG-885
URL: http://jira.codehaus.org/browse/MNG-885
Project: Maven 2
Type: Bug
Components: maven-core
Reporter: Brett Porter
Fix For: 2.0-beta-2
there are two places this can occur:
1) calculation of ${basedir} ro a path derived from it
2) missing values that go to check project properties
Should project be null, or should it be a skeleton instance? Either the
expression evaluator needs to be fixed (set basedir to user.dir, don't look for
properties), or the project needs to be populated.
I encountered this attempting to use scm:checkout.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MNG-886) use of reporting plugins results in NPE
use of reporting plugins results in NPE --- Key: MNG-886 URL: http://jira.codehaus.org/browse/MNG-886 Project: Maven 2 Type: Bug Components: maven-release-plugin Reporter: Brett Porter Doxia had: reporting plugins plugin artifactIdmaven-project-info-reports-plugin/artifactId /plugin /plugins /reporting This caused an NPE as the resolved artifact was not found in the map. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MNG-887) default tag to ${artifactId}-${version}
default tag to ${artifactId}-${version}
---
Key: MNG-887
URL: http://jira.codehaus.org/browse/MNG-887
Project: Maven 2
Type: Improvement
Components: maven-release-plugin
Reporter: Brett Porter
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r280776 - /maven/components/trunk/maven-1.x-integration/pom.xml
Author: brett Date: Tue Sep 13 23:35:35 2005 New Revision: 280776 URL: http://svn.apache.org/viewcvs?rev=280776view=rev Log: fix deps Modified: maven/components/trunk/maven-1.x-integration/pom.xml Modified: maven/components/trunk/maven-1.x-integration/pom.xml URL: http://svn.apache.org/viewcvs/maven/components/trunk/maven-1.x-integration/pom.xml?rev=280776r1=280775r2=280776view=diff == --- maven/components/trunk/maven-1.x-integration/pom.xml (original) +++ maven/components/trunk/maven-1.x-integration/pom.xml Tue Sep 13 23:35:35 2005 @@ -11,11 +11,13 @@ inceptionYear2004/inceptionYear dependencies dependency + groupIdplexus/groupId + artifactIdplexus-container-default/artifactId +/dependency +dependency groupIdforehead/groupId artifactIdforehead/artifactId version1.0-beta-5/version - typejar/type - scopecompile/scope /dependency /dependencies /model - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MNG-888) occasional deployment failure - No such file or directory
occasional deployment failure - No such file or directory - Key: MNG-888 URL: http://jira.codehaus.org/browse/MNG-888 Project: Maven 2 Type: Bug Reporter: Brett Porter Fix For: 2.0-beta-2 When the deployment directory doesn't occur in the remote deployment repo, I have seen occasions where this fails, but on a subsequent attempt succeeds. This only seems to be at release time, so may be a case of wrong order of directory creation. It is over SCP. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build - SUCCESS - update] Wed Sep 14 06:45:00 GMT 2005
Distribution: http://maven.zones.apache.org/~maven/builds/m2-20050914.064500.tar.gz Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20050914.064500.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MNG-889) m2 should warn (fail?) if a parent POM is discovered in the USD with a different version to the one requested
m2 should warn (fail?) if a parent POM is discovered in the USD with a different version to the one requested - Key: MNG-889 URL: http://jira.codehaus.org/browse/MNG-889 Project: Maven 2 Type: Improvement Components: maven-project Reporter: Brett Porter Fix For: 2.0-beta-2 if the project file is found but has a different version, this may indicate a sync issue in the code or SCM. This should either warn or fail (with option to bypass if intentional) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MNG-881) release:perform can't build plexus utils/container
[ http://jira.codehaus.org/browse/MNG-881?page=all ] Brett Porter updated MNG-881: - Assign To: John Casey this happens to anything with tests that use the plexus container. It also happens when running: m2 test -DperformRelease=true on plexus-velocity, for example. so it seems related to that profile, not the release plugin release:perform can't build plexus utils/container -- Key: MNG-881 URL: http://jira.codehaus.org/browse/MNG-881 Project: Maven 2 Type: Bug Components: maven-release-plugin Reporter: Brett Porter Assignee: John Casey the tests fail. It looks like the user.dir may not be set. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MNG-886) use of reporting plugins results in NPE
[ http://jira.codehaus.org/browse/MNG-886?page=all ] Brett Porter updated MNG-886: - Assign To: John Casey use of reporting plugins results in NPE --- Key: MNG-886 URL: http://jira.codehaus.org/browse/MNG-886 Project: Maven 2 Type: Bug Components: maven-release-plugin Reporter: Brett Porter Assignee: John Casey Doxia had: reporting plugins plugin artifactIdmaven-project-info-reports-plugin/artifactId /plugin /plugins /reporting This caused an NPE as the resolved artifact was not found in the map. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MNG-878) pom no longer correctly populated
[ http://jira.codehaus.org/browse/MNG-878?page=all ] Brett Porter updated MNG-878: - Assign To: John Casey pom no longer correctly populated - Key: MNG-878 URL: http://jira.codehaus.org/browse/MNG-878 Project: Maven 2 Type: Bug Components: maven-release-plugin Reporter: Brett Porter Assignee: John Casey problems with the release pom generated by the release plugin: - RELEASE is the populated version for a plugin, instead of being resolved - plugins used in the build process but not explicitly listed in the pom are not populated - parent is not merge in -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MNG-879) snapshots are not recognised by release plugin
[ http://jira.codehaus.org/browse/MNG-879?page=all ] Brett Porter updated MNG-879: - Assign To: John Casey snapshots are not recognised by release plugin -- Key: MNG-879 URL: http://jira.codehaus.org/browse/MNG-879 Project: Maven 2 Type: Bug Components: maven-release-plugin Reporter: Brett Porter Assignee: John Casey the release plugin checks for snapshots, but when they are resolved to the timestamped version it doesn't recognise them as snapshots and so doesn't fail. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MNG-880) release pom still contains snapshot version
[ http://jira.codehaus.org/browse/MNG-880?page=all ] Brett Porter updated MNG-880: - Assign To: John Casey release pom still contains snapshot version --- Key: MNG-880 URL: http://jira.codehaus.org/browse/MNG-880 Project: Maven 2 Type: Bug Components: maven-release-plugin Reporter: Brett Porter Assignee: John Casey this is a recent regression -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MNG-890) release plugin should exec maven in batch mode
release plugin should exec maven in batch mode -- Key: MNG-890 URL: http://jira.codehaus.org/browse/MNG-890 Project: Maven 2 Type: Improvement Components: maven-release-plugin Reporter: Brett Porter Assigned to: John Casey this would avoid output like this: 4/11K 8/11K 11/11K 11K uploaded -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r280797 - in /maven/components/trunk/maven-reporting: maven-reporting-api/pom.xml maven-reporting-impl/pom.xml
Author: brett Date: Wed Sep 14 00:36:29 2005 New Revision: 280797 URL: http://svn.apache.org/viewcvs?rev=280797view=rev Log: use doxia release Modified: maven/components/trunk/maven-reporting/maven-reporting-api/pom.xml maven/components/trunk/maven-reporting/maven-reporting-impl/pom.xml Modified: maven/components/trunk/maven-reporting/maven-reporting-api/pom.xml URL: http://svn.apache.org/viewcvs/maven/components/trunk/maven-reporting/maven-reporting-api/pom.xml?rev=280797r1=280796r2=280797view=diff == --- maven/components/trunk/maven-reporting/maven-reporting-api/pom.xml (original) +++ maven/components/trunk/maven-reporting/maven-reporting-api/pom.xml Wed Sep 14 00:36:29 2005 @@ -42,7 +42,7 @@ dependency groupIddoxia/groupId artifactIddoxia-sink-api/artifactId - version1.0-alpha-4-SNAPSHOT/version + version1.0-alpha-4/version /dependency /dependencies /project Modified: maven/components/trunk/maven-reporting/maven-reporting-impl/pom.xml URL: http://svn.apache.org/viewcvs/maven/components/trunk/maven-reporting/maven-reporting-impl/pom.xml?rev=280797r1=280796r2=280797view=diff == --- maven/components/trunk/maven-reporting/maven-reporting-impl/pom.xml (original) +++ maven/components/trunk/maven-reporting/maven-reporting-impl/pom.xml Wed Sep 14 00:36:29 2005 @@ -51,7 +51,7 @@ dependency groupIddoxia/groupId artifactIddoxia-core/artifactId - version1.0-alpha-4-SNAPSHOT/version + version1.0-alpha-4/version /dependency dependency groupIdorg.apache.maven/groupId - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r280799 - /maven/components/trunk/maven-plugins/maven-site-plugin/pom.xml
Author: brett Date: Wed Sep 14 00:37:03 2005 New Revision: 280799 URL: http://svn.apache.org/viewcvs?rev=280799view=rev Log: use component release Modified: maven/components/trunk/maven-plugins/maven-site-plugin/pom.xml Modified: maven/components/trunk/maven-plugins/maven-site-plugin/pom.xml URL: http://svn.apache.org/viewcvs/maven/components/trunk/maven-plugins/maven-site-plugin/pom.xml?rev=280799r1=280798r2=280799view=diff == --- maven/components/trunk/maven-plugins/maven-site-plugin/pom.xml (original) +++ maven/components/trunk/maven-plugins/maven-site-plugin/pom.xml Wed Sep 14 00:37:03 2005 @@ -49,7 +49,7 @@ dependency groupIdplexus/groupId artifactIdplexus-site-renderer/artifactId - version1.0-alpha-2-SNAPSHOT/version + version1.0-alpha-2/version /dependency dependency groupIdorg.apache.maven.wagon/groupId - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build - FAILED - update] Wed Sep 14 07:45:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20050914.074500.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r280802 - /maven/maven-1/core/trunk/xdocs/reference/project-descriptor.xml
Author: aheritier Date: Wed Sep 14 01:06:02 2005 New Revision: 280802 URL: http://svn.apache.org/viewcvs?rev=280802view=rev Log: rename packageName to package as it was before. I forgot to update the documentation Modified: maven/maven-1/core/trunk/xdocs/reference/project-descriptor.xml Modified: maven/maven-1/core/trunk/xdocs/reference/project-descriptor.xml URL: http://svn.apache.org/viewcvs/maven/maven-1/core/trunk/xdocs/reference/project-descriptor.xml?rev=280802r1=280801r2=280802view=diff == --- maven/maven-1/core/trunk/xdocs/reference/project-descriptor.xml (original) +++ maven/maven-1/core/trunk/xdocs/reference/project-descriptor.xml Wed Sep 14 01:06:02 2005 @@ -108,7 +108,7 @@ lt;logo/gt; lt;/organizationgt; lt;properties/gt; - lt;packageName/gt; + lt;package/gt; lt;a href=#class_Buildbuild/agt; lt;nagEmailAddress/gt; lt;sourceDirectory/gt; @@ -476,7 +476,7 @@ /tr tr td - codepackageName/code + codepackage/code /td td The Java package name of the project. This value is used - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[REPOCLEAN] Error(s) occurred while converting repository
Errors occurred while performing maven-1 to maven-2 repository conversion. For more details, see: http://test.maven.codehaus.org/reports/repoclean/14-Sep-2005_04.01.09/repository.report.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build - SUCCESS - update] Wed Sep 14 08:15:00 GMT 2005
Distribution: http://maven.zones.apache.org/~maven/builds/m2-20050914.081500.tar.gz Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20050914.081500.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MNG-891) Javadoc fails to include libraries
[ http://jira.codehaus.org/browse/MNG-891?page=all ] Vincent Siveton closed MNG-891: --- Resolution: Fixed Fix Version: 2.0-beta-1 Fix in SVN Javadoc fails to include libraries -- Key: MNG-891 URL: http://jira.codehaus.org/browse/MNG-891 Project: Maven 2 Type: Bug Versions: 2.0-beta-1 Environment: SVN revision 280814 on Linux using JRockit 1.4.2 Reporter: Bob Allison Assignee: Vincent Siveton Priority: Critical Fix For: 2.0-beta-1 Attachments: javadoc-failure.zip I am writing a simple extension to log4j that consists of a new class which extends Level to add more values. I have zipped up the project (the pom and a single source file) and attached them. The project compiles fine. When I try to generate the JavaDoc for the project, JavaDoc fails to include the log4j library in the classpath which causes it to fail. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build - SUCCESS - update] Wed Sep 14 12:15:00 GMT 2005
Distribution: http://maven.zones.apache.org/~maven/builds/m2-20050914.121500.tar.gz Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20050914.121500.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MAVEN-1691) Variable scope problem
Variable scope problem -- Key: MAVEN-1691 URL: http://jira.codehaus.org/browse/MAVEN-1691 Project: Maven Type: Bug Components: jelly/ant integration Versions: 1.1-beta-2 Reporter: Arnaud Heritier Priority: Blocker Attachments: plugin-test.zip There's a bug in m1.1 that doesn't exist in m1.0.X When you define a variable in a custom goal for a project, this last one is available for others projects. It cause a problem for example if you use several multiproject:goal. We have this problem in maven-plugins when we launch the goal plugins:test-all If a plugin use the multiproject with a new goal (j:set:var=goal ...), than the reactor use this goal for all plugins after it. I attached a test case for the multiproject plugin. It works with maven 1.0.2 but not with maven 1.1-beta2. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: svn commit: r280755 - in /maven/components/trunk: maven-core-it/ maven-core-it/it0068/ maven-core-it/it2001/ maven-core-it/it2001/a/ maven-core-it/it2001/a/src/ maven-core-it/it2001/a/src/main/ maven-
On Wed, 14 Sep 2005 [EMAIL PROTECTED] wrote: Hi, I've also worked on the it0068 you sent me yesterday, and added two custom repo's that display the behaviour better. See http://gods.nl/~forge/it0068.tgz. The problem with this it test is that it uses the default snapshot repo, which is already present within maven poms (specified in the root pom). Using non-builtin repo's seems to demonstrate problems better. However, even this new version can't reproduce the problem. Btw, i needed a plugin and a normal artifact in 2 repo's. I've included the source for a dummy plugin, and just added an empty jar in the artifact repo. Since you've looked into it into more detail yesterday, you decide if you want to take my changes. Also, I didn't know how to build the dummy plugin and deploy it in the test repo in 1 it test (unless I was using maven-it-plugin in the sandbox :)) -- Kenney Author: jdcasey Date: Tue Sep 13 20:40:17 2005 New Revision: 280755 URL: http://svn.apache.org/viewcvs?rev=280755view=rev Log: Re-resolving: MNG-757 o Added it0068 to guard against regressions of the type causing MNG-836 o Added it2001, which must be run manually, to verify the test case laid out in MNG-757 o Reinstated the repository accumulation for successive traversal down the transitivity chain, so that transitively resolved artifacts can be found in repositories declared by POMs up the chain. o Added a check for 'file:' at the beginning of the Settings.getLocalRepository() result, before prepending 'file://' to allow for relative definition of the local repository in test cases Added: maven/components/trunk/maven-core-it/it0068/ maven/components/trunk/maven-core-it/it0068/expected-results.txt (with props) maven/components/trunk/maven-core-it/it0068/goals.txt (with props) maven/components/trunk/maven-core-it/it0068/pom.xml (with props) maven/components/trunk/maven-core-it/it0068/prebuild-hook.txt (with props) maven/components/trunk/maven-core-it/it0068/test.mdo (with props) maven/components/trunk/maven-core-it/it2001/ maven/components/trunk/maven-core-it/it2001/a/ maven/components/trunk/maven-core-it/it2001/a/pom.xml (with props) maven/components/trunk/maven-core-it/it2001/a/src/ maven/components/trunk/maven-core-it/it2001/a/src/main/ maven/components/trunk/maven-core-it/it2001/a/src/main/java/ maven/components/trunk/maven-core-it/it2001/a/src/main/java/org/ maven/components/trunk/maven-core-it/it2001/a/src/main/java/org/apache/ maven/components/trunk/maven-core-it/it2001/a/src/main/java/org/apache/maven/ maven/components/trunk/maven-core-it/it2001/a/src/main/java/org/apache/maven/it2001/ maven/components/trunk/maven-core-it/it2001/a/src/main/java/org/apache/maven/it2001/a/ maven/components/trunk/maven-core-it/it2001/a/src/main/java/org/apache/maven/it2001/a/Client.java (with props) maven/components/trunk/maven-core-it/it2001/b/ maven/components/trunk/maven-core-it/it2001/b/pom.xml (with props) maven/components/trunk/maven-core-it/it2001/b/src/ maven/components/trunk/maven-core-it/it2001/b/src/main/ maven/components/trunk/maven-core-it/it2001/b/src/main/java/ maven/components/trunk/maven-core-it/it2001/b/src/main/java/org/ maven/components/trunk/maven-core-it/it2001/b/src/main/java/org/apache/ maven/components/trunk/maven-core-it/it2001/b/src/main/java/org/apache/maven/ maven/components/trunk/maven-core-it/it2001/b/src/main/java/org/apache/maven/it2001/ maven/components/trunk/maven-core-it/it2001/b/src/main/java/org/apache/maven/it2001/b/ maven/components/trunk/maven-core-it/it2001/b/src/main/java/org/apache/maven/it2001/b/Layer.java (with props) maven/components/trunk/maven-core-it/it2001/c/ maven/components/trunk/maven-core-it/it2001/c/pom.xml (with props) maven/components/trunk/maven-core-it/it2001/c/src/ maven/components/trunk/maven-core-it/it2001/c/src/main/ maven/components/trunk/maven-core-it/it2001/c/src/main/java/ maven/components/trunk/maven-core-it/it2001/c/src/main/java/org/ maven/components/trunk/maven-core-it/it2001/c/src/main/java/org/apache/ maven/components/trunk/maven-core-it/it2001/c/src/main/java/org/apache/maven/ maven/components/trunk/maven-core-it/it2001/c/src/main/java/org/apache/maven/it2001/ maven/components/trunk/maven-core-it/it2001/c/src/main/java/org/apache/maven/it2001/c/ maven/components/trunk/maven-core-it/it2001/c/src/main/java/org/apache/maven/it2001/c/Core.java (with props) maven/components/trunk/maven-core-it/it2001/settings.xml (with props) maven/components/trunk/maven-core-it/it2001/test.sh (with props) Modified: maven/components/trunk/maven-core-it/README.txt maven/components/trunk/maven-core/src/main/java/org/apache/maven/cli/MavenCli.java
[jira] Reopened: (MNG-514) Provided dependencies not included in eclipse build path
[ http://jira.codehaus.org/browse/MNG-514?page=all ] Kenney Westerhof reopened MNG-514: -- The problem is back :-( Provided dependencies not included in eclipse build path -- Key: MNG-514 URL: http://jira.codehaus.org/browse/MNG-514 Project: Maven 2 Type: Bug Components: maven-plugins Environment: Windows XP SP2, J2SE 5.0, running against main trunk in SVN. Reporter: Nathaniel Stoddard Assignee: Kenney Westerhof Fix For: 2.0-beta-1 When an eclipse project is generated for a project with a dependency whose scope is provided, the dependency is not included in the build path of the project. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[continuum build - SUCCESS - update] Wed Sep 14 12:30:00 GMT 2005
Distribution: http://maven.zones.apache.org/~continuum/builds/continuum-20050914.123000.tar.gz Log: http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20050914.123000.txt
svn commit: r280860 - in /maven/maven-1/plugins/trunk: ./ abbot/src/plugin-test/ clover/src/plugin-test/ cruisecontrol/src/plugin-test/ dashboard/src/plugin-test/ eclipse/src/plugin-test/
Author: aheritier
Date: Wed Sep 14 07:06:20 2005
New Revision: 280860
URL: http://svn.apache.org/viewcvs?rev=280860view=rev
Log:
Replace the multiproject:goal by the reactor (workaround for MAVEN-1691).
Fix all tests in all plugins.
Removed:
maven/maven-1/plugins/trunk/abbot/src/plugin-test/project.properties
maven/maven-1/plugins/trunk/clover/src/plugin-test/project.properties
maven/maven-1/plugins/trunk/cruisecontrol/src/plugin-test/project.properties
maven/maven-1/plugins/trunk/eclipse/src/plugin-test/project.properties
Modified:
maven/maven-1/plugins/trunk/abbot/src/plugin-test/maven.xml
maven/maven-1/plugins/trunk/clover/src/plugin-test/maven.xml
maven/maven-1/plugins/trunk/cruisecontrol/src/plugin-test/maven.xml
maven/maven-1/plugins/trunk/dashboard/src/plugin-test/maven.xml
maven/maven-1/plugins/trunk/dashboard/src/plugin-test/project.properties
maven/maven-1/plugins/trunk/eclipse/src/plugin-test/maven.xml
maven/maven-1/plugins/trunk/maven.xml
Modified: maven/maven-1/plugins/trunk/abbot/src/plugin-test/maven.xml
URL:
http://svn.apache.org/viewcvs/maven/maven-1/plugins/trunk/abbot/src/plugin-test/maven.xml?rev=280860r1=280859r2=280860view=diff
==
--- maven/maven-1/plugins/trunk/abbot/src/plugin-test/maven.xml (original)
+++ maven/maven-1/plugins/trunk/abbot/src/plugin-test/maven.xml Wed Sep 14
07:06:20 2005
@@ -1,6 +1,6 @@
?xml version=1.0?
-project xmlns:j=jelly:core
+project xmlns:j=jelly:core xmlns:maven=jelly:maven
goal name=testPlugin
echoThis plugin must be tested manually (with the testPlugin-manual
goal) as it requires defining a build.properties containing
environment-dependent configuration./echo
@@ -13,8 +13,7 @@
environment variable must be set. --
goal name=testPlugin-manual
- j:set var=goal value=dist/
-attainGoal name=multiproject:goal/
+maven:reactor basedir=${basedir} includes=*/project.xml goals=dist
banner=Test ignoreFailures=false/
/goal
/project
Modified: maven/maven-1/plugins/trunk/clover/src/plugin-test/maven.xml
URL:
http://svn.apache.org/viewcvs/maven/maven-1/plugins/trunk/clover/src/plugin-test/maven.xml?rev=280860r1=280859r2=280860view=diff
==
--- maven/maven-1/plugins/trunk/clover/src/plugin-test/maven.xml (original)
+++ maven/maven-1/plugins/trunk/clover/src/plugin-test/maven.xml Wed Sep 14
07:06:20 2005
@@ -15,11 +15,10 @@
* limitations under the License.
*/
--
-project default=testPlugin xmlns:j=jelly:core
+project default=testPlugin xmlns:j=jelly:core xmlns:maven=jelly:maven
goal name=testPlugin
-j:set var=goal value=testPlugin/
-attainGoal name=multiproject:goal/
+maven:reactor basedir=${basedir} includes=test*/project.xml
goals=testPlugin banner=Test ignoreFailures=false/
/goal
/project
Modified: maven/maven-1/plugins/trunk/cruisecontrol/src/plugin-test/maven.xml
URL:
http://svn.apache.org/viewcvs/maven/maven-1/plugins/trunk/cruisecontrol/src/plugin-test/maven.xml?rev=280860r1=280859r2=280860view=diff
==
--- maven/maven-1/plugins/trunk/cruisecontrol/src/plugin-test/maven.xml
(original)
+++ maven/maven-1/plugins/trunk/cruisecontrol/src/plugin-test/maven.xml Wed Sep
14 07:06:20 2005
@@ -15,14 +15,10 @@
* limitations under the License.
*/
--
-project xmlns:util=jelly:util xmlns:j=jelly:core
+project xmlns:util=jelly:util xmlns:j=jelly:core
xmlns:maven=jelly:maven
goal name=testPlugin
-
-!-- Generate project artifacts --
- j:set var=goal value=testPlugin/
-attainGoal name=multiproject:goal/
-
+maven:reactor basedir=${basedir} includes=*/project.xml
goals=testPlugin banner=Test ignoreFailures=false/
/goal
/project
Modified: maven/maven-1/plugins/trunk/dashboard/src/plugin-test/maven.xml
URL:
http://svn.apache.org/viewcvs/maven/maven-1/plugins/trunk/dashboard/src/plugin-test/maven.xml?rev=280860r1=280859r2=280860view=diff
==
--- maven/maven-1/plugins/trunk/dashboard/src/plugin-test/maven.xml (original)
+++ maven/maven-1/plugins/trunk/dashboard/src/plugin-test/maven.xml Wed Sep 14
07:06:20 2005
@@ -20,6 +20,7 @@
xmlns:j=jelly:core
xmlns:ant=jelly:ant
xmlns:x=jelly:xml
+ xmlns:maven=jelly:maven
xmlns:assert=assert
goal name=testPlugin
@@ -30,8 +31,7 @@
goal name=fixture
!-- Setup --
-j:set var=goal value=clean/
-attainGoal name=multiproject:goal/
+maven:reactor basedir=${maven.multiproject.basedir}
includes=${maven.multiproject.includes}
excludes=${maven.multiproject.excludes} goals=clean banner=Clean
ignoreFailures=false/
attainGoal name=clean/
!-- Call goal to test --
Modified:
[jira] Commented: (MNG-514) Provided dependencies not included in eclipse build path
[ http://jira.codehaus.org/browse/MNG-514?page=comments#action_46367 ] Kenney Westerhof commented on MNG-514: -- I made a testcase for eclipse, but since that doesn't use the full m2 environment that test always fails. Here's how to reproduce: - project A is the one you are calling eclipse:eclipse on - it has a dependency on project B (in the local repo), packaging war (not sure if that matters). - project B has a dependency on C (for instance) with scope=provided. B ends up in .classpath, but C doesnt. Direct dependencies for A with scope=provided do end up in .classpath. So it seems when transitively resolving deps the scope is lost (dependencyResolution = test). Provided dependencies not included in eclipse build path -- Key: MNG-514 URL: http://jira.codehaus.org/browse/MNG-514 Project: Maven 2 Type: Bug Components: maven-plugins Environment: Windows XP SP2, J2SE 5.0, running against main trunk in SVN. Reporter: Nathaniel Stoddard Assignee: Kenney Westerhof Fix For: 2.0-beta-1 When an eclipse project is generated for a project with a dependency whose scope is provided, the dependency is not included in the build path of the project. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNG-886) use of reporting plugins results in NPE
[ http://jira.codehaus.org/browse/MNG-886?page=comments#action_46370 ] John Casey commented on MNG-886: do you have that NPE? that would make this process alot quicker... use of reporting plugins results in NPE --- Key: MNG-886 URL: http://jira.codehaus.org/browse/MNG-886 Project: Maven 2 Type: Bug Components: maven-release-plugin Reporter: Brett Porter Assignee: John Casey Doxia had: reporting plugins plugin artifactIdmaven-project-info-reports-plugin/artifactId /plugin /plugins /reporting This caused an NPE as the resolved artifact was not found in the map. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MNG-886) use of reporting plugins results in NPE
[ http://jira.codehaus.org/browse/MNG-886?page=all ] John Casey updated MNG-886: --- Fix Version: 2.0-beta-2 Complexity: Expert (was: Intermediate) Remaining Estimate: 6 hours Original Estimate: 21600 hour estimate is probably high (6h) right now, because I have to decipher the meaning of this issue's description, and then reproduce it. use of reporting plugins results in NPE --- Key: MNG-886 URL: http://jira.codehaus.org/browse/MNG-886 Project: Maven 2 Type: Bug Components: maven-release-plugin Reporter: Brett Porter Assignee: John Casey Fix For: 2.0-beta-2 Original Estimate: 6 hours Remaining: 6 hours Doxia had: reporting plugins plugin artifactIdmaven-project-info-reports-plugin/artifactId /plugin /plugins /reporting This caused an NPE as the resolved artifact was not found in the map. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Newbie question: language-dependencies of Maven
Hi, (Sorry, I hoped to find this in the FAQ, but didn't. You may want to actually answer there, preferably.) Is it documented somewhere, how exactly Maven is tied to Java? What level of efforts would it take to make it language-neutral (with certain limitations, or perhaps even without limitations, assuming language-dependent plugins, whatever...)? Thanks very much, Szabolcs - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MNG-881) release:perform can't build plexus utils/container
[ http://jira.codehaus.org/browse/MNG-881?page=all ] John Casey updated MNG-881: --- Fix Version: 2.0-beta-2 Remaining Estimate: 4 hours Original Estimate: 14400 release:perform can't build plexus utils/container -- Key: MNG-881 URL: http://jira.codehaus.org/browse/MNG-881 Project: Maven 2 Type: Bug Components: maven-release-plugin Reporter: Brett Porter Assignee: John Casey Fix For: 2.0-beta-2 Original Estimate: 4 hours Remaining: 4 hours the tests fail. It looks like the user.dir may not be set. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MNG-890) release plugin should exec maven in batch mode
[ http://jira.codehaus.org/browse/MNG-890?page=all ] John Casey updated MNG-890: --- Fix Version: (was: 2.0-beta-1) 2.0-beta-2 release plugin should exec maven in batch mode -- Key: MNG-890 URL: http://jira.codehaus.org/browse/MNG-890 Project: Maven 2 Type: Improvement Components: maven-release-plugin Reporter: Brett Porter Assignee: John Casey Fix For: 2.0-beta-2 Original Estimate: 1 hour Remaining: 1 hour this would avoid output like this: 4/11K 8/11K 11/11K 11K uploaded -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MNG-880) release pom still contains snapshot version
[ http://jira.codehaus.org/browse/MNG-880?page=all ] John Casey updated MNG-880: --- Fix Version: 2.0-beta-2 Remaining Estimate: 3 hours Original Estimate: 10800 release pom still contains snapshot version --- Key: MNG-880 URL: http://jira.codehaus.org/browse/MNG-880 Project: Maven 2 Type: Bug Components: maven-release-plugin Reporter: Brett Porter Assignee: John Casey Fix For: 2.0-beta-2 Original Estimate: 3 hours Remaining: 3 hours this is a recent regression -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MNG-879) snapshots are not recognised by release plugin
[ http://jira.codehaus.org/browse/MNG-879?page=all ] John Casey updated MNG-879: --- Fix Version: 2.0-beta-2 Remaining Estimate: 4 hours Original Estimate: 14400 snapshots are not recognised by release plugin -- Key: MNG-879 URL: http://jira.codehaus.org/browse/MNG-879 Project: Maven 2 Type: Bug Components: maven-release-plugin Reporter: Brett Porter Assignee: John Casey Fix For: 2.0-beta-2 Original Estimate: 4 hours Remaining: 4 hours the release plugin checks for snapshots, but when they are resolved to the timestamped version it doesn't recognise them as snapshots and so doesn't fail. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MNG-878) pom no longer correctly populated
[ http://jira.codehaus.org/browse/MNG-878?page=all ] John Casey updated MNG-878: --- Fix Version: 2.0-beta-2 Remaining Estimate: 3 hours Original Estimate: 10800 pom no longer correctly populated - Key: MNG-878 URL: http://jira.codehaus.org/browse/MNG-878 Project: Maven 2 Type: Bug Components: maven-release-plugin Reporter: Brett Porter Assignee: John Casey Fix For: 2.0-beta-2 Original Estimate: 3 hours Remaining: 3 hours problems with the release pom generated by the release plugin: - RELEASE is the populated version for a plugin, instead of being resolved - plugins used in the build process but not explicitly listed in the pom are not populated - parent is not merge in -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MNG-876) release plugin increments version incorrectly
[ http://jira.codehaus.org/browse/MNG-876?page=all ] John Casey updated MNG-876: --- Fix Version: 2.0-beta-2 Remaining Estimate: 4 hours Original Estimate: 14400 time estimate is high for the last bit about using ArtifactVersion with incrementing...this may require some code-reading on my part, and a little design work (for the incrementing part) release plugin increments version incorrectly - Key: MNG-876 URL: http://jira.codehaus.org/browse/MNG-876 Project: Maven 2 Type: Bug Components: maven-release-plugin Reporter: Brett Porter Assignee: John Casey Fix For: 2.0-beta-2 Original Estimate: 4 hours Remaining: 4 hours I think this was changed recently. 1.0.2 gets incremented to 3-SNAPSHOT instead of 1.0.3-SNAPSHOT We should parse it as an ArtifactVersion and increment it that way, but also have an interactive menu to confirm, and fail if we didn't know how to parse it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r280867 - in /maven/maven-1/plugins/trunk/plugin/xdocs: changes.xml tags.xml
Author: aheritier Date: Wed Sep 14 07:51:38 2005 New Revision: 280867 URL: http://svn.apache.org/viewcvs?rev=280867view=rev Log: the tag I added works only with maven 1.1 because of the jelly:util bundle in 1.0 which doesn't allow to replace a string by another in a string. Modified: maven/maven-1/plugins/trunk/plugin/xdocs/changes.xml maven/maven-1/plugins/trunk/plugin/xdocs/tags.xml Modified: maven/maven-1/plugins/trunk/plugin/xdocs/changes.xml URL: http://svn.apache.org/viewcvs/maven/maven-1/plugins/trunk/plugin/xdocs/changes.xml?rev=280867r1=280866r2=280867view=diff == --- maven/maven-1/plugins/trunk/plugin/xdocs/changes.xml (original) +++ maven/maven-1/plugins/trunk/plugin/xdocs/changes.xml Wed Sep 14 07:51:38 2005 @@ -24,7 +24,7 @@ /properties body release version=1.7-SNAPSHOT date=In SVN - action dev=aheritier type=addnew plugin:available tag to check if a minimal release of a plugin is present./action + action dev=aheritier type=addnew plugin:available tag to check if a minimal release of a plugin is present. (for maven 1.1 only)/action /release release version=1.6 date=2005-06-03 action dev=vmassol type=addAdded new Modified: maven/maven-1/plugins/trunk/plugin/xdocs/tags.xml URL: http://svn.apache.org/viewcvs/maven/maven-1/plugins/trunk/plugin/xdocs/tags.xml?rev=280867r1=280866r2=280867view=diff == --- maven/maven-1/plugins/trunk/plugin/xdocs/tags.xml (original) +++ maven/maven-1/plugins/trunk/plugin/xdocs/tags.xml Wed Sep 14 07:51:38 2005 @@ -71,8 +71,9 @@ /p pThere are no attributes for this tag/p /subsection - subsection name='assertFileExists Tag' + subsection name='available Tag' pFails the build if the given plugin does not exist or hasn't the minimal release number. Otherwise no effect./p +pbWorks only with maven 1.1./b/p table trthAttribute/ththOptional?/ththDescription/th/tr tr - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r280869 - in /maven/maven-1/plugins/trunk/faq: project.xml xdocs/changes.xml xdocs/index.xml
Author: aheritier Date: Wed Sep 14 07:56:42 2005 New Revision: 280869 URL: http://svn.apache.org/viewcvs?rev=280869view=rev Log: 1.6-SNAPSHOT : compatible with maven 1.1 only because of maven-plugin-plugin-1.7 :-( Modified: maven/maven-1/plugins/trunk/faq/project.xml maven/maven-1/plugins/trunk/faq/xdocs/changes.xml maven/maven-1/plugins/trunk/faq/xdocs/index.xml Modified: maven/maven-1/plugins/trunk/faq/project.xml URL: http://svn.apache.org/viewcvs/maven/maven-1/plugins/trunk/faq/project.xml?rev=280869r1=280868r2=280869view=diff == --- maven/maven-1/plugins/trunk/faq/project.xml (original) +++ maven/maven-1/plugins/trunk/faq/project.xml Wed Sep 14 07:56:42 2005 @@ -22,7 +22,7 @@ pomVersion3/pomVersion idmaven-faq-plugin/id nameMaven FAQ Plug-in/name - currentVersion1.5/currentVersion + currentVersion1.6-SNAPSHOT/currentVersion gumpRepositoryIdjakarta/gumpRepositoryId descriptionCreates XDoc documentation from an FAQ XML document./description shortDescriptionFAQ Plugin/shortDescription Modified: maven/maven-1/plugins/trunk/faq/xdocs/changes.xml URL: http://svn.apache.org/viewcvs/maven/maven-1/plugins/trunk/faq/xdocs/changes.xml?rev=280869r1=280868r2=280869view=diff == --- maven/maven-1/plugins/trunk/faq/xdocs/changes.xml (original) +++ maven/maven-1/plugins/trunk/faq/xdocs/changes.xml Wed Sep 14 07:56:42 2005 @@ -1,5 +1,4 @@ ?xml version=1.0 encoding=UTF-8? - !-- /* * Copyright 2001-2005 The Apache Software Foundation. @@ -23,6 +22,8 @@ author email=[EMAIL PROTECTED]dIon Gillard/author /properties body +release version=1.6-SNAPSHOT date=In SVN description=FAQ plugin compatible with maven 1.1 only +/release release version=1.5 date=2005-09-05 action dev=aheritier type=add issue=MPFAQ-19 due-to=Lukas TheusslOptional toplinks and layout fix./action action dev=aheritier type=fix issue=MPFAQ-16 due-to=Lukas TheusslFAQ plugin does not produce valid XHTML 1.0 Transitional./action Modified: maven/maven-1/plugins/trunk/faq/xdocs/index.xml URL: http://svn.apache.org/viewcvs/maven/maven-1/plugins/trunk/faq/xdocs/index.xml?rev=280869r1=280868r2=280869view=diff == --- maven/maven-1/plugins/trunk/faq/xdocs/index.xml (original) +++ maven/maven-1/plugins/trunk/faq/xdocs/index.xml Wed Sep 14 07:56:42 2005 @@ -67,7 +67,8 @@ /source /section section name=Requirements - pBe Careful, the following plugins must be installed to use the FAQ plugin :/p + pMaven 1.1 is required./p + pAlso be careful, the following plugins must be installed to use the FAQ plugin :/p ul limaven-plugin-plugin 1.7 (at least)/li limaven-xdoc-plugin 1.9.2 (at least)/li - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MAVENUPLOAD-515) Please upload tm-extractors 0.4
[ http://jira.codehaus.org/browse/MAVENUPLOAD-515?page=all ] Carlos Sanchez closed MAVENUPLOAD-515: -- Assign To: Carlos Sanchez Resolution: Fixed Please upload tm-extractors 0.4 --- Key: MAVENUPLOAD-515 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-515 Project: maven-upload-requests Type: Task Reporter: Yann Le Du Assignee: Carlos Sanchez http://www.textmining.org/ Could not find a license, so provided an empty one -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MEV-83) Dumbster 1.6 POM uses non-standard Sun names
[ http://jira.codehaus.org/browse/MEV-83?page=all ] Carlos Sanchez closed MEV-83: - Assign To: Carlos Sanchez Resolution: Fixed Dumbster 1.6 POM uses non-standard Sun names Key: MEV-83 URL: http://jira.codehaus.org/browse/MEV-83 Project: Maven Evangelism Type: Bug Reporter: mike perham Assignee: Carlos Sanchez Uses non-standard names for the Sun jars. http://maven.apache.org/reference/standard-sun-jar-names.html -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MAVENUPLOAD-517) Upload XOM 1.1 beta 3 to Maven
[ http://jira.codehaus.org/browse/MAVENUPLOAD-517?page=comments#action_46378 ] Carlos Sanchez commented on MAVENUPLOAD-517: Problems with poms should be submitted to http://jira.codehaus.org/browse/MEV, but removing all the dependencies is not the way to make it work. Upload XOM 1.1 beta 3 to Maven -- Key: MAVENUPLOAD-517 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-517 Project: maven-upload-requests Type: Task Reporter: Elliotte Rusty Harold Assignee: Carlos Sanchez http://www.cafeconleche.org/XOM/xom-maven-1.1b3.jar http://www.xom.nu/ http://www.xom.nu/ -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MNG-893) NPE in PluginParameterExpressionEvaluator when a mojo need the basedir and pom.xml doesn't exist
NPE in PluginParameterExpressionEvaluator when a mojo need the basedir and pom.xml doesn't exist Key: MNG-893 URL: http://jira.codehaus.org/browse/MNG-893 Project: Maven 2 Type: Bug Versions: 2.0-beta-1 Reporter: Emmanuel Venisse Fix For: 2.0-beta-2 m2 scm:checkout -Dmaven.scm.url=scm:cvs:pserver:my-userid@my.cvs.server.com:my-cvs-repository:my-module and receiving the following response: [INFO] Searching repository for plugin with prefix: 'scm'. [INFO] [INFO] Building Maven Default Project [INFO]task-segment: [scm:checkout] [INFO] --- constituent[0]: file:/c:/maven-2.0-alpha-3/lib/commons-cli-1.0-beta-2.jar constituent[1]: file:/c:/maven-2.0-alpha-3/lib/doxia-sink-api-1.0-alpha-4-20050721.064859-1.jar constituent[2]: file:/c:/maven-2.0-alpha-3/lib/jline-0.9.1.jar constituent[3]: file:/c:/maven-2.0-alpha-3/lib/jsch-0.1.21.jar constituent[4]: file:/c:/maven-2.0-alpha-3/lib/maven-artifact-2.0-beta-1-SNAPSHOT.jar constituent[5]: file:/c:/maven-2.0-alpha-3/lib/maven-artifact-manager-2.0-beta-1-SNAPSHOT.jar constituent[6]: file:/c:/maven-2.0-alpha-3/lib/maven-core-2.0-beta-1-SNAPSHOT.jar constituent[7]: file:/c:/maven-2.0-alpha-3/lib/maven-model-2.0-beta-1-SNAPSHOT.jar constituent[8]: file:/c:/maven-2.0-alpha-3/lib/maven-monitor-2.0-beta-1-SNAPSHOT.jar constituent[9]: file:/c:/maven-2.0-alpha-3/lib/maven-plugin-api-2.0-beta-1-SNAPSHOT.jar constituent[10]: file:/c:/maven-2.0-alpha-3/lib/maven-plugin-descriptor-2.0-beta-1-SNAPSHOT.jar constituent[11]: file:/c:/maven-2.0-alpha-3/lib/maven-plugin-registry-2.0-beta-1-SNAPSHOT.jar constituent[12]: file:/c:/maven-2.0-alpha-3/lib/maven-profile-2.0-beta-1-SNAPSHOT.jar constituent[13]: file:/c:/maven-2.0-alpha-3/lib/maven-project-2.0-beta-1-SNAPSHOT.jar constituent[14]: file:/c:/maven-2.0-alpha-3/lib/maven-reporting-api-2.0-beta-1-SNAPSHOT.jar constituent[15]: file:/c:/maven-2.0-alpha-3/lib/maven-repository-metadata-2.0-beta-1-SNAPSHOT.jar constituent[16]: file:/c:/maven-2.0-alpha-3/lib/maven-settings-2.0-beta-1-SNAPSHOT.jar constituent[17]: file:/c:/maven-2.0-alpha-3/lib/plexus-input-handler-1.0-alpha-2.jar constituent[18]: file:/c:/maven-2.0-alpha-3/lib/wagon-file-1.0-alpha-4.jar constituent[19]: file:/c:/maven-2.0-alpha-3/lib/wagon-http-lightweight-1.0-alpha-4.jar constituent[20]: file:/c:/maven-2.0-alpha-3/lib/wagon-provider-api-1.0-alpha-4.jar constituent[21]: file:/c:/maven-2.0-alpha-3/lib/wagon-ssh-1.0-alpha-4.jar --- java.lang.NullPointerException at org.apache.maven.plugin.PluginParameterExpressionEvaluator.evaluate(PluginParameterExpressionEvaluator.java:221) at org.apache.maven.plugin.DefaultPluginManager.checkRequiredParameters(DefaultPluginManager.java:705) at org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:513) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:330) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:479) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:460) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:442) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:131) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:186) at org.apache.maven.cli.MavenCli.main(MavenCli.java:316) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL
Headache to create plugins compatibles with both m1.0 and m1.1
Hi guys, As you seen it, I'm working on maven 1.1 to allow us to publish it ASAP. I'm facing to more and more problems to create plugins compatibles with maven 1.0 and 1.1 : - We had a lot of problems with the xml parser. - Today I realized that the little tag I created on the plugin-plugin works only with maven 1.1 because the jelly-util API is different in 1.0 and doesn't support to replace a String in another one. I'm afraid to encounter more and more problems We lost a lot of time to create plugins compatibles with both maven releases (without talking about maven 2 !!) and it put back the release for maven 1.1 I would like to know your point of view about these problems. Must we focus on the release for maven 1.1 (and there's again a lot of work - I found a new blocking issue today with the mutliproject :-( ) or take the time to create plugins at most compatible with maven 1.0. WDYT ? Arnaud
scope provided not transitively inherited?
Hi, i'm facing this problem: Project A has a servlet implementation that (obviously) extends HttpServlet and has a dependency on servletapi, scope=provided. Project B depends on project A (scope=compile), and extends the servlet defined in A. Now, if it doesn't call/override methods in A that have a servletapi parameter (i.e. HttpServletRequest), B doesn't need to have a dep on servletapi. However, as soon as B overrides/uses a method that has HttpServletRequest as a parameter, it requires a dependency on servletapi. This seems odd to me. I just want to extend A, depend on it, so I get everything I need, and just override a method that does a System.out.prinltn and delegates to the parent (for instance). Why would I need to specify a dependency on servletapi then myself? I've located the place where scope=provided gets nuked in transitive dependencies: maven-artifact's DefaultArtifactFactory.createArtifact. I really want to make the provided scope inheritable, but wanted to check with you guys first to see wheter this is wanted and wheter to do this now of after beta-1 is released. WDYT? -- Kenney - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[REPOCLEAN] Error(s) occurred while converting repository
Errors occurred while performing maven-1 to maven-2 repository conversion. For more details, see: http://test.maven.codehaus.org/reports/repoclean/14-Sep-2005_12.00.54/repository.report.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MAVENUPLOAD-517) Upload XOM 1.1 beta 3 to Maven
[ http://jira.codehaus.org/browse/MAVENUPLOAD-517?page=comments#action_46380 ] Elliotte Rusty Harold commented on MAVENUPLOAD-517: --- Could you please explain what you mean by a .pom file I'm just following the directions on http://maven.apache.org/repository-upload.html and that doesn;t mention any such file. What I uploaded does seem to have a project.xml file. If you let know what I did wrong I shoudl be able to fix it for future releases, but I do it all throughy ant so otherwise I'm likely to do the same thing again. Also, if you let me know what's the problem with jaxen I may be able to do something about fixing that. However XOM 1.1 depends fairly critically on Jaxen. Upload XOM 1.1 beta 3 to Maven -- Key: MAVENUPLOAD-517 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-517 Project: maven-upload-requests Type: Task Reporter: Elliotte Rusty Harold Assignee: Carlos Sanchez http://www.cafeconleche.org/XOM/xom-maven-1.1b3.jar http://www.xom.nu/ http://www.xom.nu/ -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MPSITE-38) Ugly exception stacktraces created while running 'maven site' in non-debug mode.
[ http://jira.codehaus.org/browse/MPSITE-38?page=all ] Lukas Theussl closed MPSITE-38: --- Resolution: Duplicate It's a JDepend issue: MPJDEPEND-5 Ugly exception stacktraces created while running 'maven site' in non-debug mode. - Key: MPSITE-38 URL: http://jira.codehaus.org/browse/MPSITE-38 Project: maven-site-plugin Type: Improvement Components: plugin Versions: 1.6.1 Environment: - Maven 1.1 beta1 - Windows 2000 Server Reporter: Davy Toch Priority: Minor Fix For: 1.6.2 Attachments: maven-site-output.log Running 'maven site' works without a problem, but apparently some ugly stacktraces are generated in the process (cf log file). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MPSITE-5) SAXParserFactoryImpl not found from maven/lib/endorsed
[ http://jira.codehaus.org/browse/MPSITE-5?page=all ] Lukas Theussl closed MPSITE-5: -- Resolution: Cannot Reproduce SAXParserFactoryImpl not found from maven/lib/endorsed -- Key: MPSITE-5 URL: http://jira.codehaus.org/browse/MPSITE-5 Project: maven-site-plugin Type: Bug Versions: 1.3 Environment: cygwin over win2k professional SP2 Reporter: bmak Priority: Blocker Fix For: 1.6.2 BUILD FAILED File.. file:/d:/data/bmak/.maven/plugins/maven-site-plugin-1.2/ Element... attainGoal Line.. 24 Column 42 Provider org.apache.xerces.jaxp.SAXParserFactoryImpl not found I am able to run genapp and eclipse plugins just fine. but not site:generate I see that maven, per se, has maven/lib/endorsed/xerces-2.2.1.jar holding org.apache.xerces.jaxp.SAXParserFactoryImpl within it. And I see that the site plugin does NOT call out any xerces dependency -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MNG-894) Add task-oriented mini-HOWTO's to Maven 2.0 documentation
Add task-oriented mini-HOWTO's to Maven 2.0 documentation - Key: MNG-894 URL: http://jira.codehaus.org/browse/MNG-894 Project: Maven 2 Type: Improvement Components: documentation Reporter: John Casey Fix For: 2.0 See http://www.biojava.org/docs/bj_in_anger/index.htm for an example of this. It's a sort of hybrid between FAQ and HOW-TO, and would be really useful for beginners. As the complexity of m2 increases, we need to seriously consider helping people bootstrap into using m2. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MPXDOC-171) Display status of inclusion in remote Maven repository on generated dependency page
[ http://jira.codehaus.org/browse/MPXDOC-171?page=all ] Lukas Theussl moved MPSITE-7 to MPXDOC-171: --- Version: (was: 1.3) 1.9.2 Fix Version: (was: 1.6.2) Key: MPXDOC-171 (was: MPSITE-7) Project: maven-xdoc-plugin (was: maven-site-plugin) Display status of inclusion in remote Maven repository on generated dependency page --- Key: MPXDOC-171 URL: http://jira.codehaus.org/browse/MPXDOC-171 Project: maven-xdoc-plugin Type: Improvement Versions: 1.9.2 Reporter: Charlie Dobbie Priority: Trivial My project contains several dependencies that are not yet (or never will be) available from ibiblio. It would be useful to have an indication on the dependency page to distinguish these entries. As each environment has its own opinion of where dependencies come from, and thus what is and isn't custom, this would require a property named something like maven.repo.remote.official to store the project's opinion of standard repository locations. I can see this being implemented in one of two different ways: 1) At time of page generation, check whether each dependency exists in one of the official/standard repository locations. If in off-line mode, don't check and don't render any indication. 2) At time of dependency download, store extra information in the local repository detailing where the file came from. At page generation time, check these values instead. The first option is quick and easy, but requires network access which will slow a build down. The second option is more correct, but requires a (minor) change to a core Maven process. The second option may become out-of-sync with reality if a custom library is added - the local repository wouldn't be aware of this. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r280897 - in /maven/maven-1/plugins/trunk/xdoc/src/main/org/apache/maven: DependencyDescriberBean.java xdoc/XdocTagLibrary.java xdoc/util/ScmUtil.java
Author: ltheussl
Date: Wed Sep 14 11:02:45 2005
New Revision: 280897
URL: http://svn.apache.org/viewcvs?rev=280897view=rev
Log:
Fix javadocs
Modified:
maven/maven-1/plugins/trunk/xdoc/src/main/org/apache/maven/DependencyDescriberBean.java
maven/maven-1/plugins/trunk/xdoc/src/main/org/apache/maven/xdoc/XdocTagLibrary.java
maven/maven-1/plugins/trunk/xdoc/src/main/org/apache/maven/xdoc/util/ScmUtil.java
Modified:
maven/maven-1/plugins/trunk/xdoc/src/main/org/apache/maven/DependencyDescriberBean.java
URL:
http://svn.apache.org/viewcvs/maven/maven-1/plugins/trunk/xdoc/src/main/org/apache/maven/DependencyDescriberBean.java?rev=280897r1=280896r2=280897view=diff
==
---
maven/maven-1/plugins/trunk/xdoc/src/main/org/apache/maven/DependencyDescriberBean.java
(original)
+++
maven/maven-1/plugins/trunk/xdoc/src/main/org/apache/maven/DependencyDescriberBean.java
Wed Sep 14 11:02:45 2005
@@ -40,13 +40,13 @@
{
//~ Instance fields
- /** dependencies list */
+ /** Dependencies list. */
private List dependencies = new ArrayList();
- /** for debug output */
+ /** For debug output. */
private Log log = LogFactory.getLog(DependencyDescriberBean.class);
- /** project reference */
+ /** Project reference. */
private Project project;
//~ Methods
@@ -64,8 +64,8 @@
}
/**
- * Project provides context/session related information. e.g where
- * maven repo local is
+ * Project provides context/session related information, e.g where
+ * maven repo local is.
*
* @param projectValue project to scan
*/
Modified:
maven/maven-1/plugins/trunk/xdoc/src/main/org/apache/maven/xdoc/XdocTagLibrary.java
URL:
http://svn.apache.org/viewcvs/maven/maven-1/plugins/trunk/xdoc/src/main/org/apache/maven/xdoc/XdocTagLibrary.java?rev=280897r1=280896r2=280897view=diff
==
---
maven/maven-1/plugins/trunk/xdoc/src/main/org/apache/maven/xdoc/XdocTagLibrary.java
(original)
+++
maven/maven-1/plugins/trunk/xdoc/src/main/org/apache/maven/xdoc/XdocTagLibrary.java
Wed Sep 14 11:02:45 2005
@@ -28,7 +28,7 @@
public class XdocTagLibrary extends TagLibrary
{
/**
- * Create an instance of the [EMAIL PROTECTED] MavenTagLibrary},
registering related
+ * Create an instance of the MavenTagLibrary, registering related
* tag libraries
*/
public XdocTagLibrary()
Modified:
maven/maven-1/plugins/trunk/xdoc/src/main/org/apache/maven/xdoc/util/ScmUtil.java
URL:
http://svn.apache.org/viewcvs/maven/maven-1/plugins/trunk/xdoc/src/main/org/apache/maven/xdoc/util/ScmUtil.java?rev=280897r1=280896r2=280897view=diff
==
---
maven/maven-1/plugins/trunk/xdoc/src/main/org/apache/maven/xdoc/util/ScmUtil.java
(original)
+++
maven/maven-1/plugins/trunk/xdoc/src/main/org/apache/maven/xdoc/util/ScmUtil.java
Wed Sep 14 11:02:45 2005
@@ -35,7 +35,7 @@
{
/**
- * Get the SCM type
+ * Get the SCM type.
*
* @param scmConnection the scm connection to analyse.
* @return the scm type : cvs, svn , ...
@@ -66,7 +66,8 @@
}
/**
- * Get cvs server. Used in
xdocs/src/plugin-resources/templates/cvs-usage.xml
+ * Get cvs server. Used in
+ * xdocs/src/plugin-resources/templates/cvs-usage.xml.
*
* @param conn six token connection string
* @return CVS module.
@@ -90,7 +91,7 @@
}
/**
- * Get cvs root. Used in xdocs/src/plugin-resources/templates/cvs-usage.xml
+ * Get cvs root. Used in
xdocs/src/plugin-resources/templates/cvs-usage.xml.
*
* @param conn six token connection string
* @param username username override if non-empty.
@@ -118,7 +119,8 @@
}
/**
- * Get cvs module. Used in
xdocs/src/plugin-resources/templates/cvs-usage.xml
+ * Get cvs module. Used in
+ * xdocs/src/plugin-resources/templates/cvs-usage.xml.
*
* @param conn six token connection string
* @return CVS module.
@@ -140,10 +142,10 @@
}
/**
- * Splits an SCM string into parts
+ * Splits an SCM string into parts.
*
* @param connection
- * @return
+ * @return A string array of SCM parts
*/
public String[] splitSCMConnection(String connection)
{
@@ -181,7 +183,8 @@
}
/**
- * Converts a tokenizer to an array of strings FIXME: This should be in a
string util class
+ * Converts a tokenizer to an array of strings FIXME: This should be in a
+ * string util class.
*
* @param tok
* @return String[]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL
svn commit: r280903 - in /maven/components/trunk: maven-plugins/maven-project-info-reports-plugin/src/main/java/org/apache/maven/report/projectinfo/ maven-project/src/main/java/org/apache/maven/project/
Author: jdcasey
Date: Wed Sep 14 11:38:54 2005
New Revision: 280903
URL: http://svn.apache.org/viewcvs?rev=280903view=rev
Log:
Fixing case where non-POM artifacts are passed to the project builder for
parsing...doing defensive construction of POM artifacts inside the project
builder, and fixed the call in the DependenciesReport.
Modified:
maven/components/trunk/maven-plugins/maven-project-info-reports-plugin/src/main/java/org/apache/maven/report/projectinfo/DependenciesReport.java
maven/components/trunk/maven-project/src/main/java/org/apache/maven/project/DefaultMavenProjectBuilder.java
Modified:
maven/components/trunk/maven-plugins/maven-project-info-reports-plugin/src/main/java/org/apache/maven/report/projectinfo/DependenciesReport.java
URL:
http://svn.apache.org/viewcvs/maven/components/trunk/maven-plugins/maven-project-info-reports-plugin/src/main/java/org/apache/maven/report/projectinfo/DependenciesReport.java?rev=280903r1=280902r2=280903view=diff
==
---
maven/components/trunk/maven-plugins/maven-project-info-reports-plugin/src/main/java/org/apache/maven/report/projectinfo/DependenciesReport.java
(original)
+++
maven/components/trunk/maven-plugins/maven-project-info-reports-plugin/src/main/java/org/apache/maven/report/projectinfo/DependenciesReport.java
Wed Sep 14 11:38:54 2005
@@ -335,8 +335,15 @@
private MavenProject getMavenProjectFromRepository( Artifact artifact,
ArtifactRepository localRepository )
throws ProjectBuildingException
{
+Artifact projectArtifact = artifact;
+
+if ( !pom.equals( artifact.getType() ) )
+{
+projectArtifact =
artifactFactory.createProjectArtifact(artifact.getGroupId(),
artifact.getArtifactId(), artifact.getVersion(), artifact.getScope() );
+}
+
// TODO: we should use the MavenMetadataSource instead
-return mavenProjectBuilder.buildFromRepository( artifact,
project.getRepositories(), localRepository );
+return mavenProjectBuilder.buildFromRepository( projectArtifact,
project.getRepositories(), localRepository );
}
}
Modified:
maven/components/trunk/maven-project/src/main/java/org/apache/maven/project/DefaultMavenProjectBuilder.java
URL:
http://svn.apache.org/viewcvs/maven/components/trunk/maven-project/src/main/java/org/apache/maven/project/DefaultMavenProjectBuilder.java?rev=280903r1=280902r2=280903view=diff
==
---
maven/components/trunk/maven-project/src/main/java/org/apache/maven/project/DefaultMavenProjectBuilder.java
(original)
+++
maven/components/trunk/maven-project/src/main/java/org/apache/maven/project/DefaultMavenProjectBuilder.java
Wed Sep 14 11:38:54 2005
@@ -321,17 +321,33 @@
ArtifactRepository localRepository )
throws ProjectBuildingException
{
-MavenProject project = getCachedProject( artifact.getGroupId(),
artifact.getArtifactId(),
- artifact.getVersion() );
+Artifact projectArtifact;
+
+if ( pom.equals( artifact.getType() ) )
+{
+projectArtifact = artifact;
+}
+else
+{
+getLogger().warn(
+ Attempting to build MavenProject instance for
Artifact of type: + artifact.getType()
+ + ; constructing POM artifact instead. );
+
+projectArtifact = artifactFactory.createProjectArtifact(
artifact.getGroupId(), artifact.getArtifactId(),
+
artifact.getVersion(), artifact.getScope() );
+}
+
+MavenProject project = getCachedProject( projectArtifact.getGroupId(),
projectArtifact.getArtifactId(),
+ projectArtifact.getVersion()
);
Model model;
if ( project == null )
{
// TODO: can't assume artifact is a POM
try
{
-artifactResolver.resolve( artifact,
remoteArtifactRepositories, localRepository );
+artifactResolver.resolve( projectArtifact,
remoteArtifactRepositories, localRepository );
-File file = artifact.getFile();
+File file = projectArtifact.getFile();
model = readModel( file );
String downloadUrl = null;
@@ -346,7 +362,7 @@
}
// TODO: configurable actions dependant on status
-if ( !artifact.isSnapshot() status.compareTo(
ArtifactStatus.DEPLOYED ) 0 )
+if ( !projectArtifact.isSnapshot() status.compareTo(
ArtifactStatus.DEPLOYED ) 0 )
{
svn commit: r280905 - /maven/components/trunk/maven-plugins/maven-release-plugin/src/main/java/org/apache/maven/plugins/release/PerformReleaseMojo.java
Author: jdcasey Date: Wed Sep 14 11:41:55 2005 New Revision: 280905 URL: http://svn.apache.org/viewcvs?rev=280905view=rev Log: Resolving: MNG-890, putting m2 invocation in batch mode when doing release:perform. Modified: maven/components/trunk/maven-plugins/maven-release-plugin/src/main/java/org/apache/maven/plugins/release/PerformReleaseMojo.java Modified: maven/components/trunk/maven-plugins/maven-release-plugin/src/main/java/org/apache/maven/plugins/release/PerformReleaseMojo.java URL: http://svn.apache.org/viewcvs/maven/components/trunk/maven-plugins/maven-release-plugin/src/main/java/org/apache/maven/plugins/release/PerformReleaseMojo.java?rev=280905r1=280904r2=280905view=diff == --- maven/components/trunk/maven-plugins/maven-release-plugin/src/main/java/org/apache/maven/plugins/release/PerformReleaseMojo.java (original) +++ maven/components/trunk/maven-plugins/maven-release-plugin/src/main/java/org/apache/maven/plugins/release/PerformReleaseMojo.java Wed Sep 14 11:41:55 2005 @@ -101,6 +101,8 @@ cl.createArgument().setLine( -DperformRelease=true ); cl.createArgument().setLine( --no-plugin-updates ); + +cl.createArgument().setLine( --batch-mode ); StreamConsumer consumer = new DefaultConsumer(); - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MNG-890) release plugin should exec maven in batch mode
[ http://jira.codehaus.org/browse/MNG-890?page=all ] John Casey closed MNG-890: -- Resolution: Fixed Fix Version: (was: 2.0-beta-2) 2.0-beta-1 release plugin should exec maven in batch mode -- Key: MNG-890 URL: http://jira.codehaus.org/browse/MNG-890 Project: Maven 2 Type: Improvement Components: maven-release-plugin Reporter: Brett Porter Assignee: John Casey Fix For: 2.0-beta-1 Original Estimate: 1 hour Time Spent: 1 hour Remaining: 0 minutes this would avoid output like this: 4/11K 8/11K 11/11K 11K uploaded -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build - SUCCESS - update] Wed Sep 14 18:45:00 GMT 2005
Distribution: http://maven.zones.apache.org/~maven/builds/m2-20050914.184500.tar.gz Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20050914.184500.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[REPOCLEAN] Error(s) occurred while converting repository
Errors occurred while performing maven-1 to maven-2 repository conversion. For more details, see: http://test.maven.codehaus.org/reports/repoclean/14-Sep-2005_04.01.10/repository.report.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MNG-895) Profile resources not merged with main POM
Profile resources not merged with main POM -- Key: MNG-895 URL: http://jira.codehaus.org/browse/MNG-895 Project: Maven 2 Type: Bug Versions: 2.0-beta-1 Reporter: Mark Hobson Profile resources are not merged with resources specified in the main POM, e.g.: project ... build resources resourcea/resource /resources /build profiles profile ... build resources resourceb/resource /resources /build ... /profile /profiles ... /project The effective resources block should consist of both 'a' and 'b' when the profile is activated, but currently 'b' overrides 'a'. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MNG-896) Need to declare dependencies as resources outside of WEB-INF in WARs
Need to declare dependencies as resources outside of WEB-INF in WARs Key: MNG-896 URL: http://jira.codehaus.org/browse/MNG-896 Project: Maven 2 Type: Improvement Components: maven-war-plugin Reporter: Mark Hobson Need to be able to declare maven dependencies as resources within WARs. Currently all dependencies are placed within WEB-INF/lib. Typical use-case is for a war project to pull in an applet from the repo to be included in the package. Would need to specify the whereabouts of the applet in the WAR. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNG-441) surefire plugin needs to be able to fork tests
[ http://jira.codehaus.org/browse/MNG-441?page=comments#action_46387 ] Andy Glick commented on MNG-441: Is the intention to have M2 do the forking, or will the forking behavior be added to surefire, and be passed from the plugin to surefire by parameter? That seems like a better separation of concerns. The differences between surefire and the JUnit Ant Task are pretty significant, and surefire's native mode is to run tests in separate threads, using an isolated class loader so it might be a good idea to get the surefire guys input concerning forking the test cases. surefire plugin needs to be able to fork tests -- Key: MNG-441 URL: http://jira.codehaus.org/browse/MNG-441 Project: Maven 2 Type: Improvement Components: maven-plugins Reporter: Brett Porter Fix For: 2.0-beta-2 they can leak memory, so a fork once for all option would be good. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MPPOM-5) pom:validate doesn't work in maven-1.1-beta-1
[ http://jira.codehaus.org/browse/MPPOM-5?page=comments#action_46388 ] Davy Toch commented on MPPOM-5: --- The case can be closed. I noticed that you now need a namespace http://maven.apache.org/POM/3.0.0; in the root of the POM xml document. After adding this I still had a little problem because the genapp wizard creates an element package, while in POM 3.0.0 packageName is declared. From other posts on the Maven user/dev mailing lists, it seems the latter is incorrect and will be corrected in the final 1.1 version of Maven. So sorry for wasting your time. pom:validate doesn't work in maven-1.1-beta-1 - Key: MPPOM-5 URL: http://jira.codehaus.org/browse/MPPOM-5 Project: maven-pom-plugin Type: Bug Versions: 1.4.1 Environment: Windows 2000, JDK 1.4.2_07 Reporter: Davy Toch Assignee: Arnaud Heritier Attachments: project.xml Using the genapp plugin (2.2) of Maven-1.1-beta-1, I created a simple jar project. Running pom:validate on the POM gave errors due to the fact that project.xml generated by the genapp plugin isn't a model-3.0.0 POM, because e.g. the package element generated by the genapp wizard isn't defined in the model-3.0.0 xsd. So I modified project.xml in order to be conform with the model-3.0.0 xsd. However running pom:validate still gives the following error: ~~~ $maven -e pom:validate __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.1-beta-1 build:start: pom:verify-version: pom:validate: [echo] == CUSTOM ADDED IN POM PLUGIN [echo] XSD file : c:\devtools\maven-1.1-beta-1/maven-project-3.xsd [echo] POM file : C:\tmp\myapp\project.xml [echo] === [java] C:\tmp\myapp\project.xml:19:10: error: cvc-elt.1: Cannot find the declaration of element 'project'. [java] [ERROR] Java Result: 1 BUILD SUCCESSFUL Total time : 4 seconds Finished at : zondag 31 juli 2005 12:58:49 CEST ~~~ The POM file project.xml is included as attachment. Additional question : is the pom plugin still necessary from maven-1.1-beta-1 onwards, because I thought the Maven core would verify more strictly the POM itself (cf http://maven.apache.org/reference/backwards-compatibility.html)? Regards, Davy Toch -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MPPOM-5) pom:validate doesn't work in maven-1.1-beta-1
[ http://jira.codehaus.org/browse/MPPOM-5?page=comments#action_46389 ] Arnaud Heritier commented on MPPOM-5: - I also noticed the namespace problem. I'm checking to see if it's not possible to have a workaround. For the packageName attribute, I fixed the xsd today on the web site. You can download it. pom:validate doesn't work in maven-1.1-beta-1 - Key: MPPOM-5 URL: http://jira.codehaus.org/browse/MPPOM-5 Project: maven-pom-plugin Type: Bug Versions: 1.4.1 Environment: Windows 2000, JDK 1.4.2_07 Reporter: Davy Toch Assignee: Arnaud Heritier Attachments: project.xml Using the genapp plugin (2.2) of Maven-1.1-beta-1, I created a simple jar project. Running pom:validate on the POM gave errors due to the fact that project.xml generated by the genapp plugin isn't a model-3.0.0 POM, because e.g. the package element generated by the genapp wizard isn't defined in the model-3.0.0 xsd. So I modified project.xml in order to be conform with the model-3.0.0 xsd. However running pom:validate still gives the following error: ~~~ $maven -e pom:validate __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.1-beta-1 build:start: pom:verify-version: pom:validate: [echo] == CUSTOM ADDED IN POM PLUGIN [echo] XSD file : c:\devtools\maven-1.1-beta-1/maven-project-3.xsd [echo] POM file : C:\tmp\myapp\project.xml [echo] === [java] C:\tmp\myapp\project.xml:19:10: error: cvc-elt.1: Cannot find the declaration of element 'project'. [java] [ERROR] Java Result: 1 BUILD SUCCESSFUL Total time : 4 seconds Finished at : zondag 31 juli 2005 12:58:49 CEST ~~~ The POM file project.xml is included as attachment. Additional question : is the pom plugin still necessary from maven-1.1-beta-1 onwards, because I thought the Maven core would verify more strictly the POM itself (cf http://maven.apache.org/reference/backwards-compatibility.html)? Regards, Davy Toch -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MPPOM-5) pom:validate doesn't work in maven-1.1-beta-1
[ http://jira.codehaus.org/browse/MPPOM-5?page=comments#action_46390 ] Arnaud Heritier commented on MPPOM-5: - packageName isn't an attribute but an element :-) pom:validate doesn't work in maven-1.1-beta-1 - Key: MPPOM-5 URL: http://jira.codehaus.org/browse/MPPOM-5 Project: maven-pom-plugin Type: Bug Versions: 1.4.1 Environment: Windows 2000, JDK 1.4.2_07 Reporter: Davy Toch Assignee: Arnaud Heritier Attachments: project.xml Using the genapp plugin (2.2) of Maven-1.1-beta-1, I created a simple jar project. Running pom:validate on the POM gave errors due to the fact that project.xml generated by the genapp plugin isn't a model-3.0.0 POM, because e.g. the package element generated by the genapp wizard isn't defined in the model-3.0.0 xsd. So I modified project.xml in order to be conform with the model-3.0.0 xsd. However running pom:validate still gives the following error: ~~~ $maven -e pom:validate __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.1-beta-1 build:start: pom:verify-version: pom:validate: [echo] == CUSTOM ADDED IN POM PLUGIN [echo] XSD file : c:\devtools\maven-1.1-beta-1/maven-project-3.xsd [echo] POM file : C:\tmp\myapp\project.xml [echo] === [java] C:\tmp\myapp\project.xml:19:10: error: cvc-elt.1: Cannot find the declaration of element 'project'. [java] [ERROR] Java Result: 1 BUILD SUCCESSFUL Total time : 4 seconds Finished at : zondag 31 juli 2005 12:58:49 CEST ~~~ The POM file project.xml is included as attachment. Additional question : is the pom plugin still necessary from maven-1.1-beta-1 onwards, because I thought the Maven core would verify more strictly the POM itself (cf http://maven.apache.org/reference/backwards-compatibility.html)? Regards, Davy Toch -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MPPOM-5) pom:validate doesn't work in maven-1.1-beta-1
[ http://jira.codehaus.org/browse/MPPOM-5?page=comments#action_46391 ] Davy Toch commented on MPPOM-5: --- I suppose the best solution is to modify the maven genapp plugin so it can create Maven projects with v3.0.0 POM's (instead of adding a workaround in the maven pom plugin). pom:validate doesn't work in maven-1.1-beta-1 - Key: MPPOM-5 URL: http://jira.codehaus.org/browse/MPPOM-5 Project: maven-pom-plugin Type: Bug Versions: 1.4.1 Environment: Windows 2000, JDK 1.4.2_07 Reporter: Davy Toch Assignee: Arnaud Heritier Attachments: project.xml Using the genapp plugin (2.2) of Maven-1.1-beta-1, I created a simple jar project. Running pom:validate on the POM gave errors due to the fact that project.xml generated by the genapp plugin isn't a model-3.0.0 POM, because e.g. the package element generated by the genapp wizard isn't defined in the model-3.0.0 xsd. So I modified project.xml in order to be conform with the model-3.0.0 xsd. However running pom:validate still gives the following error: ~~~ $maven -e pom:validate __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.1-beta-1 build:start: pom:verify-version: pom:validate: [echo] == CUSTOM ADDED IN POM PLUGIN [echo] XSD file : c:\devtools\maven-1.1-beta-1/maven-project-3.xsd [echo] POM file : C:\tmp\myapp\project.xml [echo] === [java] C:\tmp\myapp\project.xml:19:10: error: cvc-elt.1: Cannot find the declaration of element 'project'. [java] [ERROR] Java Result: 1 BUILD SUCCESSFUL Total time : 4 seconds Finished at : zondag 31 juli 2005 12:58:49 CEST ~~~ The POM file project.xml is included as attachment. Additional question : is the pom plugin still necessary from maven-1.1-beta-1 onwards, because I thought the Maven core would verify more strictly the POM itself (cf http://maven.apache.org/reference/backwards-compatibility.html)? Regards, Davy Toch -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: svn commit: r280867 - in /maven/maven-1/plugins/trunk/plugin/xdocs: changes.xml tags.xml
is that necessary? [EMAIL PROTECTED] wrote: Author: aheritier Date: Wed Sep 14 07:51:38 2005 New Revision: 280867 URL: http://svn.apache.org/viewcvs?rev=280867view=rev Log: the tag I added works only with maven 1.1 because of the jelly:util bundle in 1.0 which doesn't allow to replace a string by another in a string. Modified: maven/maven-1/plugins/trunk/plugin/xdocs/changes.xml maven/maven-1/plugins/trunk/plugin/xdocs/tags.xml Modified: maven/maven-1/plugins/trunk/plugin/xdocs/changes.xml URL: http://svn.apache.org/viewcvs/maven/maven-1/plugins/trunk/plugin/xdocs/changes.xml?rev=280867r1=280866r2=280867view=diff == --- maven/maven-1/plugins/trunk/plugin/xdocs/changes.xml (original) +++ maven/maven-1/plugins/trunk/plugin/xdocs/changes.xml Wed Sep 14 07:51:38 2005 @@ -24,7 +24,7 @@ /properties body release version=1.7-SNAPSHOT date=In SVN - action dev=aheritier type=addnew plugin:available tag to check if a minimal release of a plugin is present./action + action dev=aheritier type=addnew plugin:available tag to check if a minimal release of a plugin is present. (for maven 1.1 only)/action /release release version=1.6 date=2005-06-03 action dev=vmassol type=addAdded new Modified: maven/maven-1/plugins/trunk/plugin/xdocs/tags.xml URL: http://svn.apache.org/viewcvs/maven/maven-1/plugins/trunk/plugin/xdocs/tags.xml?rev=280867r1=280866r2=280867view=diff == --- maven/maven-1/plugins/trunk/plugin/xdocs/tags.xml (original) +++ maven/maven-1/plugins/trunk/plugin/xdocs/tags.xml Wed Sep 14 07:51:38 2005 @@ -71,8 +71,9 @@ /p pThere are no attributes for this tag/p /subsection - subsection name='assertFileExists Tag' + subsection name='available Tag' pFails the build if the given plugin does not exist or hasn't the minimal release number. Otherwise no effect./p +pbWorks only with maven 1.1./b/p table trthAttribute/ththOptional?/ththDescription/th/tr tr - 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]
Re: Headache to create plugins compatibles with both m1.0 and m1.1
It entirely depends on the work being done on the plugin, and how hard it is. I thought there might have been an easier alternative for the jelly-util problem. The XML stuff is trickier, but I think all the plugins most affected by it are done now. I think it is entirely reasonable to release a plugin as beta that is 1.1 only, and release it as final at the 1.1 release. But that's just my opinion. I would not jump to that first without investigating a 1.0.2 compatible solution though - otherwise if there is a lot of differences it could become confusing. - Brett Arnaud HERITIER wrote: Hi guys, As you seen it, I'm working on maven 1.1 to allow us to publish it ASAP. I'm facing to more and more problems to create plugins compatibles with maven 1.0 and 1.1 : - We had a lot of problems with the xml parser. - Today I realized that the little tag I created on the plugin-plugin works only with maven 1.1 because the jelly-util API is different in 1.0 and doesn't support to replace a String in another one. I'm afraid to encounter more and more problems We lost a lot of time to create plugins compatibles with both maven releases (without talking about maven 2 !!) and it put back the release for maven 1.1 I would like to know your point of view about these problems. Must we focus on the release for maven 1.1 (and there's again a lot of work - I found a new blocking issue today with the mutliproject :-( ) or take the time to create plugins at most compatible with maven 1.0. WDYT ? Arnaud - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r280967 - /maven/components/trunk/maven-plugins/maven-release-plugin/src/main/java/org/apache/maven/plugins/release/PerformReleaseMojo.java
Author: brett
Date: Wed Sep 14 16:45:29 2005
New Revision: 280967
URL: http://svn.apache.org/viewcvs?rev=280967view=rev
Log:
set eol style
Modified:
maven/components/trunk/maven-plugins/maven-release-plugin/src/main/java/org/apache/maven/plugins/release/PerformReleaseMojo.java
(contents, props changed)
Modified:
maven/components/trunk/maven-plugins/maven-release-plugin/src/main/java/org/apache/maven/plugins/release/PerformReleaseMojo.java
URL:
http://svn.apache.org/viewcvs/maven/components/trunk/maven-plugins/maven-release-plugin/src/main/java/org/apache/maven/plugins/release/PerformReleaseMojo.java?rev=280967r1=280966r2=280967view=diff
==
---
maven/components/trunk/maven-plugins/maven-release-plugin/src/main/java/org/apache/maven/plugins/release/PerformReleaseMojo.java
(original)
+++
maven/components/trunk/maven-plugins/maven-release-plugin/src/main/java/org/apache/maven/plugins/release/PerformReleaseMojo.java
Wed Sep 14 16:45:29 2005
@@ -1,137 +1,137 @@
-package org.apache.maven.plugins.release;
-
-/*
- * Copyright 2001-2005 The Apache Software Foundation.
- *
- * Licensed under the Apache License, Version 2.0 (the License);
- * you may not use this file except in compliance with the License.
- * You may obtain a copy of the License at
- *
- * http://www.apache.org/licenses/LICENSE-2.0
- *
- * Unless required by applicable law or agreed to in writing, software
- * distributed under the License is distributed on an AS IS BASIS,
- * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
- * See the License for the specific language governing permissions and
- * limitations under the License.
- */
-
-import org.apache.maven.plugin.MojoExecutionException;
-import org.apache.maven.plugins.release.helpers.ReleaseProgressTracker;
-import org.apache.maven.plugins.release.helpers.ScmHelper;
-import org.codehaus.plexus.util.cli.CommandLineException;
-import org.codehaus.plexus.util.cli.CommandLineUtils;
-import org.codehaus.plexus.util.cli.Commandline;
-import org.codehaus.plexus.util.cli.DefaultConsumer;
-import org.codehaus.plexus.util.cli.StreamConsumer;
-
-import java.io.IOException;
-
-/**
- * Perform a release from SCM
- *
- * @author a href=mailto:[EMAIL PROTECTED]Emmanuel Venisse/a
- * @version $Id: DoxiaMojo.java 169372 2005-05-09 22:47:34Z evenisse $
- * @aggregator
- * @goal perform
- */
-public class PerformReleaseMojo
-extends AbstractReleaseMojo
-{
-/**
- * @parameter expression=${basedir}
- * @required
- * @readonly
- */
-private String basedir;
-
-/**
- * @parameter expression=${goals}
- */
-private String goals = deploy;
-
-/**
- * @parameter expression=${project.build.directory}/checkout
- * @required
- */
-protected String workingDirectory;
-
-private ReleaseProgressTracker releaseProgress;
-
-protected void executeTask()
-throws MojoExecutionException
-{
-checkout();
-
-runGoals();
-}
-
-private void checkout()
-throws MojoExecutionException
-{
-getLog().info( Checking out the project to perform the release ... );
-
-try
-{
-ScmHelper scm = getScm( workingDirectory );
-
-scm.checkout();
-}
-catch ( Exception e )
-{
-throw new MojoExecutionException( An error is occurred in the
checkout process., e );
-}
-}
-
-private void runGoals()
-throws MojoExecutionException
-{
-// TODO: we need to get a reference to the maven component and use
that so this
-// will work purely in an embedded mode. Not sure how to pass the
release setting to the plugin in that
-// instance though - still via -D, or is there a better way?
-
-Commandline cl = new Commandline();
-
-cl.setExecutable( m2 );
-
-cl.setWorkingDirectory( workingDirectory );
-
-cl.createArgument().setLine( goals );
-
-cl.createArgument().setLine( -DperformRelease=true );
-
-cl.createArgument().setLine( --no-plugin-updates );
-
-cl.createArgument().setLine( --batch-mode );
-
-StreamConsumer consumer = new DefaultConsumer();
-
-try
-{
-CommandLineUtils.executeCommandLine( cl, consumer, consumer );
-}
-catch ( CommandLineException e )
-{
-throw new MojoExecutionException( Can't run goal + goals, e );
-}
-}
-
-protected ReleaseProgressTracker getReleaseProgress()
-throws MojoExecutionException
-{
-if ( releaseProgress == null )
-{
-try
-{
-releaseProgress = ReleaseProgressTracker.load( basedir );
-}
-catch (
[jira] Commented: (MNG-886) use of reporting plugins results in NPE
[ http://jira.codehaus.org/browse/MNG-886?page=comments#action_46392 ] Brett Porter commented on MNG-886: -- I don't believe that providing a means of reproducing it is harder than getting an arbitrary stack trace :) 1) paste above text into doxia-core/pom.xml 2) try release:prepare (turn off commit - probably a flag we should add - dryRun=true) The exception is at line 1057, caused by not being found at line 898. use of reporting plugins results in NPE --- Key: MNG-886 URL: http://jira.codehaus.org/browse/MNG-886 Project: Maven 2 Type: Bug Components: maven-release-plugin Reporter: Brett Porter Assignee: John Casey Fix For: 2.0-beta-2 Original Estimate: 6 hours Remaining: 6 hours Doxia had: reporting plugins plugin artifactIdmaven-project-info-reports-plugin/artifactId /plugin /plugins /reporting This caused an NPE as the resolved artifact was not found in the map. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MNG-514) Provided dependencies not included in eclipse build path
[ http://jira.codehaus.org/browse/MNG-514?page=all ] Brett Porter updated MNG-514: - Fix Version: (was: 2.0-beta-1) 2.0-beta-2 Provided dependencies not included in eclipse build path -- Key: MNG-514 URL: http://jira.codehaus.org/browse/MNG-514 Project: Maven 2 Type: Bug Components: maven-plugins Environment: Windows XP SP2, J2SE 5.0, running against main trunk in SVN. Reporter: Nathaniel Stoddard Assignee: Kenney Westerhof Fix For: 2.0-beta-2 When an eclipse project is generated for a project with a dependency whose scope is provided, the dependency is not included in the build path of the project. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MNG-893) NPE in PluginParameterExpressionEvaluator when a mojo need the basedir and pom.xml doesn't exist
[ http://jira.codehaus.org/browse/MNG-893?page=all ] Brett Porter closed MNG-893: Assign To: Brett Porter Resolution: Duplicate Fix Version: (was: 2.0-beta-2) NPE in PluginParameterExpressionEvaluator when a mojo need the basedir and pom.xml doesn't exist Key: MNG-893 URL: http://jira.codehaus.org/browse/MNG-893 Project: Maven 2 Type: Bug Versions: 2.0-beta-1 Reporter: Emmanuel Venisse Assignee: Brett Porter m2 scm:checkout -Dmaven.scm.url=scm:cvs:pserver:my-userid@my.cvs.server.com:my-cvs-repository:my-module and receiving the following response: [INFO] Searching repository for plugin with prefix: 'scm'. [INFO] [INFO] Building Maven Default Project [INFO]task-segment: [scm:checkout] [INFO] --- constituent[0]: file:/c:/maven-2.0-alpha-3/lib/commons-cli-1.0-beta-2.jar constituent[1]: file:/c:/maven-2.0-alpha-3/lib/doxia-sink-api-1.0-alpha-4-20050721.064859-1.jar constituent[2]: file:/c:/maven-2.0-alpha-3/lib/jline-0.9.1.jar constituent[3]: file:/c:/maven-2.0-alpha-3/lib/jsch-0.1.21.jar constituent[4]: file:/c:/maven-2.0-alpha-3/lib/maven-artifact-2.0-beta-1-SNAPSHOT.jar constituent[5]: file:/c:/maven-2.0-alpha-3/lib/maven-artifact-manager-2.0-beta-1-SNAPSHOT.jar constituent[6]: file:/c:/maven-2.0-alpha-3/lib/maven-core-2.0-beta-1-SNAPSHOT.jar constituent[7]: file:/c:/maven-2.0-alpha-3/lib/maven-model-2.0-beta-1-SNAPSHOT.jar constituent[8]: file:/c:/maven-2.0-alpha-3/lib/maven-monitor-2.0-beta-1-SNAPSHOT.jar constituent[9]: file:/c:/maven-2.0-alpha-3/lib/maven-plugin-api-2.0-beta-1-SNAPSHOT.jar constituent[10]: file:/c:/maven-2.0-alpha-3/lib/maven-plugin-descriptor-2.0-beta-1-SNAPSHOT.jar constituent[11]: file:/c:/maven-2.0-alpha-3/lib/maven-plugin-registry-2.0-beta-1-SNAPSHOT.jar constituent[12]: file:/c:/maven-2.0-alpha-3/lib/maven-profile-2.0-beta-1-SNAPSHOT.jar constituent[13]: file:/c:/maven-2.0-alpha-3/lib/maven-project-2.0-beta-1-SNAPSHOT.jar constituent[14]: file:/c:/maven-2.0-alpha-3/lib/maven-reporting-api-2.0-beta-1-SNAPSHOT.jar constituent[15]: file:/c:/maven-2.0-alpha-3/lib/maven-repository-metadata-2.0-beta-1-SNAPSHOT.jar constituent[16]: file:/c:/maven-2.0-alpha-3/lib/maven-settings-2.0-beta-1-SNAPSHOT.jar constituent[17]: file:/c:/maven-2.0-alpha-3/lib/plexus-input-handler-1.0-alpha-2.jar constituent[18]: file:/c:/maven-2.0-alpha-3/lib/wagon-file-1.0-alpha-4.jar constituent[19]: file:/c:/maven-2.0-alpha-3/lib/wagon-http-lightweight-1.0-alpha-4.jar constituent[20]: file:/c:/maven-2.0-alpha-3/lib/wagon-provider-api-1.0-alpha-4.jar constituent[21]: file:/c:/maven-2.0-alpha-3/lib/wagon-ssh-1.0-alpha-4.jar --- java.lang.NullPointerException at org.apache.maven.plugin.PluginParameterExpressionEvaluator.evaluate(PluginParameterExpressionEvaluator.java:221) at org.apache.maven.plugin.DefaultPluginManager.checkRequiredParameters(DefaultPluginManager.java:705) at org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:513) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:330) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:479) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:460) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:442) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:131) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:186) at org.apache.maven.cli.MavenCli.main(MavenCli.java:316) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly
[REPOCLEAN] Error(s) occurred while converting repository
Errors occurred while performing maven-1 to maven-2 repository conversion. For more details, see: http://test.maven.codehaus.org/reports/repoclean/14-Sep-2005_08.00.37/repository.report.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MPJIRA-14) Please offer to work with Atlassian for the plugin to be up to date.
Please offer to work with Atlassian for the plugin to be up to date. - Key: MPJIRA-14 URL: http://jira.codehaus.org/browse/MPJIRA-14 Project: maven-jira-plugin Type: Improvement Reporter: Arun Nachimuthu Please offer to work with Atlassian for the plugin to be up to date. There is no much progress here and all the important requests for enhancements are just piled up. http://jira.atlassian.com/browse/JRA-7954 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build - SUCCESS - checkout] Thu Sep 15 00:15:00 GMT 2005
Distribution: http://maven.zones.apache.org/~maven/builds/m2-20050915.001500.tar.gz Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20050915.001500.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MAVEN-1692) improve error when 1.0.2 was in path but MAVEN_HOME is 1.1
improve error when 1.0.2 was in path but MAVEN_HOME is 1.1 -- Key: MAVEN-1692 URL: http://jira.codehaus.org/browse/MAVEN-1692 Project: Maven Type: Improvement Reporter: Brett Porter Fix For: 1.1-beta-3 currently, this errors out when trying to do XML things as the parser sys properties are set. At the start of the app, test the sys props, and if set, check they are available. Give a helpful error message if not. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[vote] New Web Site CSS
Hi, Previously we polled for responses on an improved CSS and the opinions were that 31 was the best by far. We've had this turned into CSS which is applied to 2 pages that cover all styles here: http://people.apache.org/~brett/web-dev/ http://people.apache.org/~brett/web-dev/download.html [ ] +1 - Go ahead with it as is [ ] +0 - Go ahead with it, but I have some feedback that I'd like incorporated/discussed [ ] -0 - I have feedback I think must be addressed before we do this, but in general agree with the redesign [ ] -1 - I'm opposed to this design/any redesign This vote will run until the end of next Monday. (I will be running this by the Apache PRC as well) Cheers, Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] New Web Site CSS
Brett Porter wrote: [X] +1 - Go ahead with it as is [ ] +0 - Go ahead with it, but I have some feedback that I'd like incorporated/discussed [ ] -0 - I have feedback I think must be addressed before we do this, but in general agree with the redesign [ ] -1 - I'm opposed to this design/any redesign - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Subscription: Outstanding Repository Maintenance: Evangelism
Issue Subscription Filter: Outstanding Repository Maintenance: Evangelism (29 issues) Subscriber: mavendevlist Project: Maven Evangelism Resolution: Unresolved Key Summary MEV-51 broken geronimo POMS http://jira.codehaus.org/browse/MEV-51 MEV-77 Hibernate 2.1.8 pom dependency is empty http://jira.codehaus.org/browse/MEV-77 MEV-52 broken active MQ poms http://jira.codehaus.org/browse/MEV-52 MEV-64 wrong version for emma/emma is declared, there is no 2.0.latest in the repository. http://jira.codehaus.org/browse/MEV-64 MEV-63 jpox-c3p0 does not need jdbc-stdext-2.0 ( already included in jdk 1.4) http://jira.codehaus.org/browse/MEV-63 MEV-28 bogus dependencies in commons-configuration http://jira.codehaus.org/browse/MEV-28 MEV-48 openejb poms http://jira.codehaus.org/browse/MEV-48 MEV-46 Missing JDBC POM http://jira.codehaus.org/browse/MEV-46 MEV-45 Full list of poms that doesn't respect the m2 format http://jira.codehaus.org/browse/MEV-45 MEV-43 Hibernate 3.0 pom doesn't have any dependencies declared http://jira.codehaus.org/browse/MEV-43 MEV-40 URL tag invalids http://jira.codehaus.org/browse/MEV-40 MEV-39 Junit scope in commons-lang pom not in scope test. http://jira.codehaus.org/browse/MEV-39 MEV-38 POM for commons-jelly-tags-ant has incorrect artifact references bogus dependency http://jira.codehaus.org/browse/MEV-38 MEV-36 Exo POM(s) missing dependency versions http://jira.codehaus.org/browse/MEV-36 MEV-34 XOM POM references icu4j which is not in the repo http://jira.codehaus.org/browse/MEV-34 MEV-35 XOM POM references tagsoup which is not in the repo http://jira.codehaus.org/browse/MEV-35 MEV-33 XOM POM references xercesImpl v.2.2.1 which does not exist in repo http://jira.codehaus.org/browse/MEV-33 MEV-32 XOM POM references invalid servlet API location http://jira.codehaus.org/browse/MEV-32 MEV-31 XOM POM references xmlParserAPIs v2.6.1 which is not in the repo http://jira.codehaus.org/browse/MEV-31 MEV-20 clean up bad IDs in the repository http://jira.codehaus.org/browse/MEV-20 MEV-2 Broken dependency for groovy http://jira.codehaus.org/browse/MEV-2 MEV-4 Misnamed pom for Postgresql http://jira.codehaus.org/browse/MEV-4 MEV-9 jmock-cglib should depend on cglib http://jira.codehaus.org/browse/MEV-9 MEV-17 nanocontainer junit compile scope dependency http://jira.codehaus.org/browse/MEV-17 MEV-16 picocontainer junit compile scope dependency http://jira.codehaus.org/browse/MEV-16 MEV-15 commons-pool junit compile scope dependency http://jira.codehaus.org/browse/MEV-15 MEV-14 commons-loggin junit compile scope dependency http://jira.codehaus.org/browse/MEV-14 MEV-13 commons-cli junit compile scope dependency http://jira.codehaus.org/browse/MEV-13 MEV-3 Broken dependencies for nanocontainer http://jira.codehaus.org/browse/MEV-3 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Subscription: Outstanding Repository Maintenance: Uploads
Issue Subscription Filter: Outstanding Repository Maintenance: Uploads (1 issues) Subscriber: mavendevlist Project: maven-upload-requests Resolution: Unresolved Key Summary MAVENUPLOAD-502Please upload Maven Hammurapi Plugin http://jira.codehaus.org/browse/MAVENUPLOAD-502 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] New Web Site CSS
Cool! +1 On 9/14/05, Brett Porter [EMAIL PROTECTED] wrote: Hi, Previously we polled for responses on an improved CSS and the opinions were that 31 was the best by far. We've had this turned into CSS which is applied to 2 pages that cover all styles here: http://people.apache.org/~brett/web-dev/ http://people.apache.org/~brett/web-dev/download.html [ ] +1 - Go ahead with it as is [ ] +0 - Go ahead with it, but I have some feedback that I'd like incorporated/discussed [ ] -0 - I have feedback I think must be addressed before we do this, but in general agree with the redesign [ ] -1 - I'm opposed to this design/any redesign This vote will run until the end of next Monday. (I will be running this by the Apache PRC as well) Cheers, Brett - 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]
Re: [vote] New Web Site CSS
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 +1 Brett Porter wrote: | Hi, | | Previously we polled for responses on an improved CSS and the opinions | were that 31 was the best by far. We've had this turned into CSS which | is applied to 2 pages that cover all styles here: | | http://people.apache.org/~brett/web-dev/ | http://people.apache.org/~brett/web-dev/download.html | | | [ ] +1 - Go ahead with it as is | [ ] +0 - Go ahead with it, but I have some feedback that I'd like | incorporated/discussed | [ ] -0 - I have feedback I think must be addressed before we do this, | but in general agree with the redesign | [ ] -1 - I'm opposed to this design/any redesign | | | This vote will run until the end of next Monday. | | (I will be running this by the Apache PRC as well) | | Cheers, | Brett | | - | To unsubscribe, e-mail: [EMAIL PROTECTED] | For additional commands, e-mail: [EMAIL PROTECTED] | | | -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.6 (GNU/Linux) iD8DBQFDKN1sK3h2CZwO/4URAsc8AJ9UID4GkStCqTWnR0z6N/jqw9f1hQCeKFGz zlOp587qbjVebbLmLAtG1Es= =8CE8 -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MNG-661) In parent site, automatically create link to modules sites and vice-versa
[ http://jira.codehaus.org/browse/MNG-661?page=all ] Brett Porter updated MNG-661: - Component: (was: maven-plugins) maven-site-plugin In parent site, automatically create link to modules sites and vice-versa - Key: MNG-661 URL: http://jira.codehaus.org/browse/MNG-661 Project: Maven 2 Type: Improvement Components: maven-site-plugin Versions: 2.0-alpha-3 Reporter: Yann Le Du Assignee: Vincent Siveton Priority: Minor Fix For: 2.0-beta-2 Say we have the following project structure : A +-- B +-- C +-- D It would be nice to have the following links in the left menu of the generated sites : A : Modules : B, D B : Parent : A Modules : C C : Parent : B D : Parent : A -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MNG-867) Add a list of available language in site plugin
[ http://jira.codehaus.org/browse/MNG-867?page=all ] Brett Porter updated MNG-867: - Component: (was: maven-plugins) maven-site-plugin Add a list of available language in site plugin --- Key: MNG-867 URL: http://jira.codehaus.org/browse/MNG-867 Project: Maven 2 Type: Improvement Components: maven-site-plugin Reporter: Vincent Siveton Fix For: 2.0-beta-2 Attachments: language_menu.jpg, language_menu.jpg, language_menu.jpg, language_menu_as_select.jpg Please see the attached screenshots This preference menu could be a list of links or a select/ tag. The site descriptor needs to be updated: * for select/, by adding asSelect attribute in the menu element. * for links list, by adding nostrong attribute in the menu element (to not display as strong the current language and the current page) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MNG-690) Make text in code/code appear the same size as the rest of the text
[ http://jira.codehaus.org/browse/MNG-690?page=all ]
Brett Porter updated MNG-690:
-
Component: (was: maven-plugins)
maven-site-plugin
Make text in code/code appear the same size as the rest of the text
---
Key: MNG-690
URL: http://jira.codehaus.org/browse/MNG-690
Project: Maven 2
Type: Improvement
Components: maven-site-plugin
Versions: 2.0-alpha-3
Reporter: Bob Allison
Priority: Minor
Fix For: 2.0-beta-2
As currently defined, text in a paragraph that is enclosed in
code.../code will appear much smaller. This has been true since v1.0.2
or earlier.
Adding the following four lines to maven-theme.css will fix the problem (I
would suggest adding them right after the first four lines which set similar
information for most other text):
code{
font-family: Courier, monospace;
font-size: 13px;
}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MNG-554) site:site launched from parent project doesn't parse child custom site source sub-directories
[ http://jira.codehaus.org/browse/MNG-554?page=all ] Brett Porter updated MNG-554: - Component: (was: maven-plugins) maven-site-plugin site:site launched from parent project doesn't parse child custom site source sub-directories - Key: MNG-554 URL: http://jira.codehaus.org/browse/MNG-554 Project: Maven 2 Type: Bug Components: maven-site-plugin Versions: 2.0-alpha-3 Environment: Windows XP Reporter: Yann Le Du Assignee: Vincent Siveton Fix For: 2.0-beta-2 Attachments: common.zip Project A contains a module B. B's site source directory is different from the default one and contains a sub-directory apt : A / B / site / site.xml A / B / site / apt / index.apt ... so I've put this in the B / pom.xml plugins section : groupIdorg.apache.maven.plugins/groupId artifactIdmaven-site-plugin/artifactId configuration siteDirectorysite/siteDirectory /configuration When I launch site:site from B directory, B's site is correclty built. But when I launch from A directory, B's index.html is missing. I guess that site.xml was correctly taken, but that apt sub-directory was ignored. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MNG-384) make site reactor aware
[ http://jira.codehaus.org/browse/MNG-384?page=all ] Brett Porter updated MNG-384: - Component: (was: maven-plugins) maven-site-plugin make site reactor aware --- Key: MNG-384 URL: http://jira.codehaus.org/browse/MNG-384 Project: Maven 2 Type: Improvement Components: maven-site-plugin Versions: 2.0-alpha-2 Reporter: Brett Porter Priority: Blocker Fix For: 2.0-beta-2 there are a few things I'd like to do to make the sites more workable: - it's good they can still build independantly - however, if built from the parent, it would be good to go into aggregation mode and pull in those separately built sites, do any dashboards and deploy together - some reports would aggregate themselves, as well as participate in the dashboards (eg javadoc) - I'd like the navigation to behave hierachically (sections of the parent navigation marked as inherited remain on the child sites) - this means that when building from independant projects they'd need to be able to locate the parent site descriptor. This could be tricky without a USD - should it fail if it is not a USD, or should the site descriptor be published/referenced externally somehow? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MNG-535) Imposible to generated UTF-8 site with APT
[ http://jira.codehaus.org/browse/MNG-535?page=all ] Brett Porter updated MNG-535: - Component: (was: maven-plugins) maven-site-plugin Imposible to generated UTF-8 site with APT -- Key: MNG-535 URL: http://jira.codehaus.org/browse/MNG-535 Project: Maven 2 Type: Bug Components: maven-site-plugin Versions: 2.0-alpha-3 Environment: Linux 2.6.10, JDK 1.5, Maven 2.0-alpha-3 Reporter: Jean-Charles Giardina Fix For: 2.0-beta-2 Maven plugin's site cannot generated HTML files from APT files using charset UTF-8 rather than ISO-8859-1. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MNG-577) surefire plugin doesn't generate a report
[ http://jira.codehaus.org/browse/MNG-577?page=all ] Brett Porter updated MNG-577: - Component: (was: maven-plugins) maven-surefire-plugin surefire plugin doesn't generate a report - Key: MNG-577 URL: http://jira.codehaus.org/browse/MNG-577 Project: Maven 2 Type: Improvement Components: maven-surefire-plugin Versions: 2.0-alpha-3 Reporter: Yann Le Du Assignee: Johnny R. Ruiz III Fix For: 2.0-beta-2 For the moment, maven-surefire-plugin doesn't generate a report (as junit-report used to do in Maven 1). If we try to include surefire in the reports list of the pom, we get a ClassCastException : java.lang.ClassCastException: org.apache.maven.test.SurefirePlugin -| at org.apache.maven.doxia.DoxiaMojo.categorizeReports(DoxiaMojo.java:332) ... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MNG-682) Surefire interferes with ClassLoader.getResource() and Class.getResourceAsStream() calls.
[ http://jira.codehaus.org/browse/MNG-682?page=all ] Brett Porter updated MNG-682: - Component: (was: maven-plugins) maven-surefire-plugin Surefire interferes with ClassLoader.getResource() and Class.getResourceAsStream() calls. - Key: MNG-682 URL: http://jira.codehaus.org/browse/MNG-682 Project: Maven 2 Type: Bug Components: maven-surefire-plugin Versions: 2.0-beta-1 Environment: Using a 2.0-beta-1 clean build (svn checkout on 20050730-1345) on linux (and XP) . Reporter: Joakim Erdfelt Assignee: John Casey Fix For: 2.0-beta-2 Attachments: needs-classloader-clean.tar.gz, needs-classloader.tar.gz When using the Class.getResourceAsStream() or ClassLoader.getResourceAsStream() method calls in your own project, the tests succeed outside of m2 (in eclipse, on junit command line, and ant build). But all tests fail when running under Surefire. A simple m2 project demonstrating this is attached. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MNG-441) surefire plugin needs to be able to fork tests
[ http://jira.codehaus.org/browse/MNG-441?page=all ] Brett Porter updated MNG-441: - Component: (was: maven-plugins) maven-surefire-plugin surefire plugin needs to be able to fork tests -- Key: MNG-441 URL: http://jira.codehaus.org/browse/MNG-441 Project: Maven 2 Type: Improvement Components: maven-surefire-plugin Reporter: Brett Porter Fix For: 2.0-beta-2 they can leak memory, so a fork once for all option would be good. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MNG-237) surefire should not run abstract test cases
[ http://jira.codehaus.org/browse/MNG-237?page=all ] Brett Porter updated MNG-237: - Component: (was: maven-plugins) maven-surefire-plugin surefire should not run abstract test cases --- Key: MNG-237 URL: http://jira.codehaus.org/browse/MNG-237 Project: Maven 2 Type: Bug Components: maven-surefire-plugin Reporter: Brett Porter Fix For: 2.0-beta-2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MNG-458) unpacked dependencies need to merge components.xml
[ http://jira.codehaus.org/browse/MNG-458?page=all ] Brett Porter updated MNG-458: - Component: (was: maven-plugins) maven-assembly-plugin unpacked dependencies need to merge components.xml -- Key: MNG-458 URL: http://jira.codehaus.org/browse/MNG-458 Project: Maven 2 Type: Improvement Components: maven-assembly-plugin Reporter: Brett Porter in the assembly plugin, the unpacking and merging of classes from several dependencies works well, but a components.xml file (and possibly others?) must be manually maintained. It should be merged from the originals. We could have some pluggable tools for merging well known files like these in the correct fashion. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MNG-735) Assembly plugin to support 'directory' archive type
[ http://jira.codehaus.org/browse/MNG-735?page=all ] Brett Porter updated MNG-735: - Component: (was: maven-plugins) maven-assembly-plugin Assembly plugin to support 'directory' archive type --- Key: MNG-735 URL: http://jira.codehaus.org/browse/MNG-735 Project: Maven 2 Type: Improvement Components: maven-assembly-plugin Reporter: Daniel Krisher Priority: Minor Fix For: 2.0-beta-2 Attachments: AssemblyMojo.java.diff, AssemblyMojo.java.diff, DirectoryArchiver.java, descriptor.mdo.diff Add the ability for the assembly plugin to create an assembly on the native file system (i.e. a directory) that is not an archive (zip/jar/tar/etc). The assembly plugin supports configuration of a directory structure containing pom dependencies and other files based on the specified assembly xml definition. Presently this is used to create various types of archives. Using the assembly plugin is the only way I have found to create the correct directory structure for an application I am developing however I would like to do this without actually archiving the components (i.e. create the file structure but don't tar/zip/etc it). Building (and compressing) the archive takes a significant amount of time, and more often than not, we don't ever use the archive (except to extract the contents to the filesystem, run the application for testing, and never use it again), at least during development. I propose adding a 'directory' archive type that simply copies the xml specified files/dependencies to a specified path. This archive type might be specified in the assembly xml file, or alternatively, via a runtime parameter (profile/property) overriding the archive type(s) specified in the assembly xml, for use during development. I am currently working on a solution as this will be useful for our application that is built with m2, I will submit a patch as soon as I have something workable. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MNG-778) ant tasks don't use correct environment in antrun plugin
[ http://jira.codehaus.org/browse/MNG-778?page=all ]
Brett Porter updated MNG-778:
-
Component: (was: maven-plugins)
maven-antrun-plugin
ant tasks don't use correct environment in antrun plugin
Key: MNG-778
URL: http://jira.codehaus.org/browse/MNG-778
Project: Maven 2
Type: Bug
Components: maven-antrun-plugin
Reporter: Brett Porter
eg, ${user.home} does not resolve to the java system property as it would
when you execute it standalone
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MNG-777) no output from ant tasks in antrun plugin
[ http://jira.codehaus.org/browse/MNG-777?page=all ] Brett Porter updated MNG-777: - Component: (was: maven-plugins) maven-antrun-plugin no output from ant tasks in antrun plugin - Key: MNG-777 URL: http://jira.codehaus.org/browse/MNG-777 Project: Maven 2 Type: Bug Components: maven-antrun-plugin Reporter: Brett Porter -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MNG-862) Compiler arguments cause maven-compiler-plugin to fail when forked
[ http://jira.codehaus.org/browse/MNG-862?page=all ]
Brett Porter updated MNG-862:
-
Component: (was: maven-plugins)
maven-compiler-plugin
Compiler arguments cause maven-compiler-plugin to fail when forked
--
Key: MNG-862
URL: http://jira.codehaus.org/browse/MNG-862
Project: Maven 2
Type: Bug
Components: maven-compiler-plugin
Versions: 2.0-beta-1
Reporter: Rod Coffin
Priority: Minor
Attachments: patch-862.txt
Adding a compiler argument to a forked compiler causes maven to fail. An
example plugin configuration causing this error is:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-compiler-plugin/artifactId
configuration
forktrue/fork
executableC:\oss\aspectj1.5\bin\ajc/executable
source1.5/source
target1.5/target
compilerArguments
sourcerootsrc/main/java/sourceroot
/compilerArguments
/configuration
/plugin
The stack trace produced is:
[ERROR] Cause:
org.apache.maven.plugin.MojoExecutionException: Error configuring plugin for
execution of 'compiler:compile'.
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:335)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:479)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:452)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:438)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:131)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:186)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:316)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.PluginConfigurationException: Unable to
parse the created DOM for plugin configuration
at
org.apache.maven.plugin.DefaultPluginManager.populatePluginFields(DefaultPluginManager.java:1019)
at
org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:515)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:330)
... 15 more
Caused by:
org.codehaus.plexus.component.configurator.ComponentConfigurationException:
Cannot assign value '{sourceroot=src/main/java}' to field:
org.apache.maven.plugin.CompilerMojo.compilerArguments; type:
java.util.TreeMap
at
org.codehaus.plexus.component.configurator.converters.ComponentValueSetter.setValueUsingField(ComponentValueSetter.java:151)
at
org.codehaus.plexus.component.configurator.converters.ComponentValueSetter.configure(ComponentValueSetter.java:259)
at
org.codehaus.plexus.component.configurator.converters.composite.ObjectWithFieldsConverter.processConfiguration(ObjectWithFieldsConverter.java:116)
at
org.codehaus.plexus.component.configurator.BasicComponentConfigurator.configureComponent(BasicComponentConfigurator.java:55)
at
org.apache.maven.plugin.DefaultPluginManager.populatePluginFields(DefaultPluginManager.java:1014)
... 17 more
Caused by: java.lang.IllegalArgumentException
at
sun.reflect.UnsafeObjectFieldAccessorImpl.set(UnsafeObjectFieldAccessorImpl.java:63)
at java.lang.reflect.Field.set(Field.java:656)
at
org.codehaus.plexus.component.configurator.converters.ComponentValueSetter.setValueUsingField(ComponentValueSetter.java:136)
... 21 more
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
