[jira] Created: (MECLIPSE-184) Ear utility-jar are put in WEB-INF/lib of the wtp ear
Ear utility-jar are put in WEB-INF/lib of the wtp ear - Key: MECLIPSE-184 URL: http://jira.codehaus.org/browse/MECLIPSE-184 Project: Maven 2.x Eclipse Plugin Issue Type: Improvement Components: WTP support Affects Versions: 2.3 Environment: Tested on Windows XP and Linux Ubuntu Dapper Drake Reporter: Elid OR Priority: Critical It seems that the maven eclipse plugin add ear jar dependencies in the WEB-INF/lib directory. I've used the following command : mvn eclipse:clean eclipse:eclipse -Dwtpversion=1.0 (I've also tried 1.5 with the snapshot version) And when deploy the ear project through WTP in a J2EE Server I see the following structure : my-ear | my-ejb.jar | my-webapp.war | META-INF/ | application.xml | MANIFEST.MF | |- WEB-INF/ | lib | dependency-1.jar | dependency-2.jar But I don't expect these dependencies to be here, I expect something like this : my-ear | my-ejb.jar | my-webapp.war | META-INF/ | application.xml | MANIFEST.MF | |- dependency-1.jar |- dependency-2.jar So I've checked quickly the SVN repository and it seems that the directory in which we put ear utility jar is hard coded as WEB-INF/lib (- AbstractWtpResourceWritter.addDependency() which is the same for the war and the ear ... ) Are you OK with this packaging ? It can be a good thing if we could configure where wtp will put these ear utility-jars and by default it would be in / or lib. Thanks In Advance Elid OR -- 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] Commented: (MPTEST-65) Upgrade to Junit 4.0
[ http://jira.codehaus.org/browse/MPTEST-65?page=comments#action_79070 ]
Arnaud Heritier commented on MPTEST-65:
---
It's possible to use JUnit 4.x with maven 1.x :
- add Junit 4.X in your dependencies
- Use the JUnit4TestAdapter in your test classes :
/**
* @return instance of this as Junit test case
*/
public static junit.framework.Test suite()
{
return new JUnit4TestAdapter(MyTestClass.class);
}
- run maven with a jdk = 5
Upgrade to Junit 4.0
Key: MPTEST-65
URL: http://jira.codehaus.org/browse/MPTEST-65
Project: maven-test-plugin
Issue Type: Task
Affects Versions: 1.8
Reporter: Arnaud Heritier
Assigned To: Arnaud Heritier
Priority: Minor
Upgrade to Junit 4.0
JUnit 4.1 isn't (yet) available on ibiblio.
--
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] Created: (MCLEAN-22) Possibility to ignore deletion failures
Possibility to ignore deletion failures --- Key: MCLEAN-22 URL: http://jira.codehaus.org/browse/MCLEAN-22 Project: Maven 2.x Clean Plugin Issue Type: Improvement Affects Versions: 2.1, 2.1.1 Environment: WinXP SP2 Reporter: Bugittaa Pahasti Fix For: 2.1.1 If deletion of the output directories during clean fails, the build will fail. It would be good to have a configuration option, so that the plugin would just print a warning and continue cleaning with the rest of the directories. -- 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] Commented: (WAGON-64) File cannot be created error...
[ http://jira.codehaus.org/browse/WAGON-64?page=comments#action_79074 ]
Caleb Lyness commented on WAGON-64:
---
I updated to the latest version: 1.0-beta-1, inserted some println in the
org.apache.maven.wagon.AbstractWagon.createParentDirectories and reran
deployment. Here is the output:
Will deploy to 1 repository(ies): internal
Deploying to repository: internal
Uploading to System/poms/Service-1.4.0.pom:
Destination file:
\\192.168.150.7\Maven.Internal.Repo\System\poms\Service-1.4.0.pom
Destination directory: \\192.168.150.7\Maven.Internal.Repo\System\poms
Directory exists (or not specified)
(6K)
Destination file:
\\192.168.150.7\Maven.Internal.Repo\System\poms\Service-1.4.0.pom.md5
Destination directory: \\192.168.150.7\Maven.Internal.Repo\System\poms
Destination does not exist... create it...
Failed to deploy to: internal Reason:
org.apache.maven.wagon.TransferFailedException: Specified dest
ination directory cannot be created:
\\192.168.150.7\Maven.Internal.Repo\System\poms
org.apache.maven.wagon.TransferFailedException: Specified destination directory
cannot be created: \
\192.168.150.7\Maven.Internal.Repo\System\poms
at
org.apache.maven.wagon.AbstractWagon.createParentDirectories(AbstractWagon.java:172)
at
org.apache.maven.wagon.providers.file.FileWagon.fillOutputData(FileWagon.java:82)
at org.apache.maven.wagon.StreamWagon.put(StreamWagon.java:133)
at
org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deployFiles(DefaultArtifactDep
Here is the code I changed with printlns
protected void createParentDirectories( File destination )
throws TransferFailedException
{
System.out.println(Destination file: +destination);
File destinationDirectory = destination.getParentFile();
System.out.println(Destination directory: +destinationDirectory);
if ( destinationDirectory != null !destinationDirectory.exists() )
{
System.out.println(Destination does not exist... create it...);
if ( !destinationDirectory.mkdirs() )
{
throw new TransferFailedException(
Specified destination directory cannot be created: +
destinationDirectory );
} else {
System.out.println(Directory created);
}
} else {
System.out.println(Directory exists (or not specified));
}
}
File cannot be created error...
---
Key: WAGON-64
URL: http://jira.codehaus.org/browse/WAGON-64
Project: wagon
Issue Type: Bug
Components: wagon-file
Affects Versions: 1.0-alpha-2, 1.0-alpha-3, 1.0-alpha-4, 1.0-alpha-5,
1.0-alpha-6, 1.0-alpha-7
Reporter: Caleb Lyness
I am using maven 1.0 to build and deploy. As of a couple of days back I
started getting deploy problems.
I am completely lost as to explain the error and desperately would like some
one to shed some light
I am deploying to maven repository which lives in a windows share.
The repository is defined as follows in the project.properties file:
maven.repo.list=internal
maven.repo.internal=file://
maven.repo.internal.directory=192.168.150.7\\Maven.Internal.Repo
This has been working for nearly a year now. (An aside any other arrangment
of URL sepecification always results
in the deployment to the local host... yes I have tried all combinations and
read the stuff out there. Makes no difference)
It now fails with the following error:
Will deploy to 1 repository(ies): internal
Deploying to repository: internal
Uploading to System/poms/Service-1.4.0.pom:
(6K)
Failed to deploy to: internal Reason:
org.apache.maven.wagon.TransferFailedException: Specified destination
directory cannot be created: \\192.168.150.7\Maven.Internal.Repo\System\poms
org.apache.maven.wagon.TransferFailedException: Specified destination
directory cannot be created: \\192.168.150.7\Maven.Internal.Repo\System\poms
at
org.apache.maven.wagon.AbstractWagon.createParentDirectories(AbstractWagon.java:169)
at
org.apache.maven.wagon.providers.file.FileWagon.fillOutputData(FileWagon.java:82)
at org.apache.maven.wagon.StreamWagon.put(StreamWagon.java:133)
at
org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deployFiles(DefaultArtifactDeployer.java:407)
at
org.apache.maven.artifact.deployer.DefaultArtifactDeployer.doDeploy(DefaultArtifactDeployer.java:324)
at
org.apache.maven.artifact.deployer.DefaultArtifactDeployer.handleDeploy(DefaultArtifactDeployer.java:131)
at
org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:102)
at
[jira] Closed: (MRM-215) Fails to build from clean checkout
[ http://jira.codehaus.org/browse/MRM-215?page=all ] Max Bowsher closed MRM-215. --- Resolution: Fixed Fixed by joakime in r470095. Fails to build from clean checkout -- Key: MRM-215 URL: http://jira.codehaus.org/browse/MRM-215 Project: Archiva Issue Type: Bug Environment: Linux, Maven 2.0.4 Reporter: Max Bowsher $ svn co $ra/maven/archiva/trunk archiva-trunk $ cd archiva-trunk/ $ mvn install [INFO] Scanning for projects... [INFO] [ERROR] FATAL ERROR [INFO] [INFO] Error building POM (may not be this project's POM). Project ID: org.apache.maven.archiva:archiva-plexus-application POM Location: /home/maxb/work/proving/archiva-trunk/archiva-plexus-application/pom.xml Validation Messages: [0] 'dependencies.dependency.version' is missing for org.apache.maven.archiva:archiva-webapp Reason: Failed to validate POM .. This patch made the build work for me: --- archiva-plexus-application/pom.xml (revision 470042) +++ archiva-plexus-application/pom.xml (working copy) @@ -49,6 +49,7 @@ dependency groupIdorg.apache.maven.archiva/groupId artifactIdarchiva-webapp/artifactId + typewar/type /dependency /dependencies !-- For filtering -- -- 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] Updated: (MNG-2539) Transitive dependencies referenced by a plugin are searched only in the plugin-repositories
[ http://jira.codehaus.org/browse/MNG-2539?page=all ] Kenney Westerhof updated MNG-2539: -- Fix Version/s: 2.0.5 Confirmed. This is about specifying dependencies within a plugin tag. Only pluginRepositories from the pom are used, not the normal repository definitions. Transitive dependencies referenced by a plugin are searched only in the plugin-repositories --- Key: MNG-2539 URL: http://jira.codehaus.org/browse/MNG-2539 Project: Maven 2 Issue Type: Bug Components: Plugins and Lifecycle, Dependencies Affects Versions: 2.0.4 Environment: WinXP, JDK 1.5_08 Reporter: Thomas Minor Fix For: 2.0.5 Transitive dependencies referenced by a plugin are searched only in the plugin-repositories In my case, the axis plugin references th javax.activation artifact. this artifact is keep at our site in a 3rd-party repo. If this repo is only addressed in the Repositories, the build fails.If it is also refereced in the pluginRepositories everything works fine. Is this the intended practice? -- 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] Commented: (MSUREFIRE-156) The plugin does not use JAVA_HOME variable and launches default JVM
[ http://jira.codehaus.org/browse/MSUREFIRE-156?page=comments#action_79082 ] David J. M. Karlsen commented on MSUREFIRE-156: --- It can probably be closed as this already happens: mvn.bat (or .sh) uses JAVA_HOME to run maven. Surefire (at least rev441093 in trunk) the system property java.home to find the executable to fork (when in fork mode). Thus this should point to JAVA_HOME if the variable is declared. The plugin does not use JAVA_HOME variable and launches default JVM --- Key: MSUREFIRE-156 URL: http://jira.codehaus.org/browse/MSUREFIRE-156 Project: Maven 2.x Surefire Plugin Issue Type: Improvement Environment: Windows 2000, Maven 2.0.4 Reporter: Andrey Somov Assigned To: Carlos Sanchez Priority: Minor Fix For: 2.3 Attachments: MSUREFIREREP-25.log The plugin does not use JAVA_HOME variable and launches default JVM (in this case default is not defined): [INFO] Surefire report directory: D:\tools\workspace\DB2Monster\monster-axis\target\surefire-reports 'java' is not recognized as an internal or external command, operable program or batch file. [INFO] [ERROR] BUILD FAILURE [INFO] JAVA_HOME does not necessary point to the default JVM. The plugin shall use the same JVM as Maven. -- 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] Commented: (MWAR-48) review plugin documentation
[ http://jira.codehaus.org/browse/MWAR-48?page=comments#action_79083 ] John Tolentino commented on MWAR-48: Just wondering why this was reopened? Was there any problem with the current documentation or is this just waiting for the plugin documentation to be released? review plugin documentation --- Key: MWAR-48 URL: http://jira.codehaus.org/browse/MWAR-48 Project: Maven 2.x War Plugin Issue Type: Task Affects Versions: 2.0 Reporter: Marvin King Fix For: 2.0.2 Attachments: MWAR-48-maven-war-plugin[draft4-1-1].patch, MWAR-48-maven-war-plugin[draft4-1].patch, MWAR-48-maven-war-plugin[draft4].patch Time Spent: 1 day, 13 hours, 30 minutes Remaining Estimate: 0 minutes -- 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] Commented: (MWAR-58) consider the artifact classifier when checking for duplicated artifacts
[ http://jira.codehaus.org/browse/MWAR-58?page=comments#action_79084 ] John Tolentino commented on MWAR-58: I assume this haven't been applied yet. I'll look into this and write some test cases if it doesn't have any. Same goes with MWAR-59. consider the artifact classifier when checking for duplicated artifacts --- Key: MWAR-58 URL: http://jira.codehaus.org/browse/MWAR-58 Project: Maven 2.x War Plugin Issue Type: New Feature Affects Versions: 2.1 Reporter: Marvin King Assigned To: John Tolentino Fix For: 2.0.2 Attachments: MWAR-58.patch Original Estimate: 1 hour Remaining Estimate: 1 hour see http://www.nabble.com/-m2--war-plugin%2C-ignores-classifier-in-dependency-tf1903970.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
[jira] Commented: (MWAR-59) artifact extension set incorrectly in a multi-module build
[ http://jira.codehaus.org/browse/MWAR-59?page=comments#action_79085 ] John Tolentino commented on MWAR-59: Checking. I assume that this haven't been applied as well. artifact extension set incorrectly in a multi-module build -- Key: MWAR-59 URL: http://jira.codehaus.org/browse/MWAR-59 Project: Maven 2.x War Plugin Issue Type: Bug Affects Versions: 2.0, 2.0.1 Reporter: Brett Porter Assigned To: John Tolentino Fix For: 2.0.2 Attachments: ejb-client-patch.txt, ejb-client-test-patch.txt from the list... unfortunately [MWAR-38] is not fully fixed - It still does not work in a multi-module build. We do have here the following structure: root jarmodule ejb webapp Running a mvn package inside the webapp module, the EJB-Client jar from the ejb module is resolved correctly and copied to WEB-INF/lib with the correct .jar ending. Running the mvn package from the root module, the ejb-client jar from the ejb module is resolved but copied with a .ejb-client ending, and not with .jar. You can test this by using the daytrader example from the Maven book. -- 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] Updated: (MSUREFIREREP-22) Aggragated surefire report from modules
[ http://jira.codehaus.org/browse/MSUREFIREREP-22?page=all ] J-C updated MSUREFIREREP-22: Attachment: patch.patch report.JPG I patch surefire-reporting 2.0 to include an report for pom packaging. In 2.0, report is done only if language is java. In my patch it is also apply on pom packaging file. When packaging is pom, it checked for modules and create a report page that contains the total number of test executed, failed, ... If there is some failure, test in failure are listed ordered by module. It supports several level of modules. A hyperlink on the module title allow to navigate to the reporting page of the module I tried it on a sample project: Sample(packaging pom) |--- sample 1 (jar with some failure in testcase) |sample 2 (jar with some failure in testcase) |sample 3 (packaging pom) |sample 4 (jar with some failure in testcase) Aggregated report looks like report.jpg Problem is that before running the plugin tests must have been executed. It might be a nice feature to include that patch in surefire-reporting ... Aggragated surefire report from modules --- Key: MSUREFIREREP-22 URL: http://jira.codehaus.org/browse/MSUREFIREREP-22 Project: Maven 2.x Surefire report Plugin Issue Type: New Feature Affects Versions: 2.0 Environment: all Reporter: Bugittaa Pahasti Attachments: patch.patch, report.JPG Aggregated surefire report from child modules. I think this has been discussed in the mailing lists, but seemed not to be on Jira yet. -- 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] Commented: (MSUREFIREREP-22) Aggragated surefire report from modules
[ http://jira.codehaus.org/browse/MSUREFIREREP-22?page=comments#action_79087 ] J-C commented on MSUREFIREREP-22: - Structure of my demo is : Sample(packaging pom) --- sample 1 (jar with some failure in testcase) sample 2 (jar with some failure in testcase) sample 3 (packaging pom) sample 4 (jar with some failure in testcase) It is a project with several level of modules Aggragated surefire report from modules --- Key: MSUREFIREREP-22 URL: http://jira.codehaus.org/browse/MSUREFIREREP-22 Project: Maven 2.x Surefire report Plugin Issue Type: New Feature Affects Versions: 2.0 Environment: all Reporter: Bugittaa Pahasti Attachments: patch.patch, report.JPG Aggregated surefire report from child modules. I think this has been discussed in the mailing lists, but seemed not to be on Jira yet. -- 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] Updated: (MRM-212) configure checksum policy for proxied repository
[ http://jira.codehaus.org/browse/MRM-212?page=all ] Arnaud Heritier updated MRM-212: Summary: configure checksum policy for proxied repository (was: configure checksum policty for proxied repository) configure checksum policy for proxied repository Key: MRM-212 URL: http://jira.codehaus.org/browse/MRM-212 Project: Archiva Issue Type: Improvement Components: remote proxy Reporter: nicolas de loof Priority: Minor Attachments: 2006-10-26-checksum-policy.patch Some artifact on repo1.maven.org have bad checksum. This need fix, but this also make archiva not usable as a replacement for maven-proxy. As maven itself allow to configure a checksum policy, a new configuration parameter on proxied repo would be nice. -- 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: (MNG-1059) update mojo API documentation
[ http://jira.codehaus.org/browse/MNG-1059?page=all ] Vincent Siveton closed MNG-1059. Assignee: Vincent Siveton Resolution: Fixed fixed in svn (r466408) update mojo API documentation - Key: MNG-1059 URL: http://jira.codehaus.org/browse/MNG-1059 Project: Maven 2 Issue Type: Task Components: Documentation: General Reporter: Brett Porter Assigned To: Vincent Siveton Fix For: 2.0.5 -- 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: (MNG-1645) document clean and site lifecycles in the build lifecycle doc
[ http://jira.codehaus.org/browse/MNG-1645?page=all ] Vincent Siveton closed MNG-1645. Assignee: Vincent Siveton Resolution: Duplicate MNG-2008 is already fixed document clean and site lifecycles in the build lifecycle doc - Key: MNG-1645 URL: http://jira.codehaus.org/browse/MNG-1645 Project: Maven 2 Issue Type: Bug Components: Documentation: Introductions Reporter: Brett Porter Assigned To: Vincent Siveton Fix For: 2.0.5 -- 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] Updated: (MNG-2612) antrun's exec task breaks in 2.0.5-SNAPSHOT
[ http://jira.codehaus.org/browse/MNG-2612?page=all ] Dan Tran updated MNG-2612: -- Affects Version/s: (was: 2.0.5) 2.0.4 Fix Version/s: 2.0.5 antrun's exec task breaks in 2.0.5-SNAPSHOT --- Key: MNG-2612 URL: http://jira.codehaus.org/browse/MNG-2612 Project: Maven 2 Issue Type: Bug Affects Versions: 2.0.4 Environment: windows Reporter: Dan Tran Fix For: 2.0.5 Attachments: pom.xml I have no problem run the below pom in 2.0.4, but in 2.0.5-SNAPSHOT. mvn package throws this [INFO] Error executing ant tasks Embedded error: Execute failed: java.io.IOException: CreateProcess: mvn.bat --he lp error=5 Here is the pom project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd; modelVersion4.0.0/modelVersion groupIdorg.codehaus.mojo.pde/groupId artifactIdm2eclipse/artifactId version1.0-SNAPSHOT/version packagingpom/packaging nameAntRun break in 2.0.5-SNAPSHOT Build/name build plugins plugin artifactIdmaven-antrun-plugin/artifactId executions execution idbuild/id phasecompile/phase goals goalrun/goal /goals configuration tasks exec executable=mvn.bat arg line=--help / /exec /tasks /configuration /execution /executions /plugin /plugins /build /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
[jira] Created: (MRM-216) Upload (deploy) artifacts to a repository
Upload (deploy) artifacts to a repository - Key: MRM-216 URL: http://jira.codehaus.org/browse/MRM-216 Project: Archiva Issue Type: New Feature Components: web application Reporter: Oliver Fink The web interface should allow to upload artifacts to the repository. For M1 one could just ftp the artifacts as neededm but with M2 having to go through the file:deploy plugin is a pain. Archiva could help a lot here -- 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] Updated: (MRM-209) plexus.sh must include tools.jar on the classpath
[ http://jira.codehaus.org/browse/MRM-209?page=all ]
Joakim Erdfelt updated MRM-209:
---
Description:
The plexush.sh that's generated in the archiva-plexus-runtime model does not
include tools.jar to the classpath of the JVM that is started. This causes
error messages when first accessing the web application about being unable to
compile JSPs.
The last line of plexus.sh currently looks like this:
{code}
exec $JAVACMD \
$PLEXUS_OPTS \
-classpath ${PLEXUS_HOME}/core/boot/classworlds-*.jar \
{code}
but should have $TOOLS_JAR included in the -classpath argument's parameter.
was:
The plexush.sh that's generated in the archiva-plexus-runtime model does not
include tools.jar to the classpath of the JVM that is started. This causes
error messages when first accessing the web application about being unable to
compile JSPs.
The last line of plexus.sh currently looks like this:
exec $JAVACMD \
$PLEXUS_OPTS \
-classpath ${PLEXUS_HOME}/core/boot/classworlds-*.jar \
but should have $TOOLS_JAR included in the -classpath argument's parameter.
plexus.sh must include tools.jar on the classpath
-
Key: MRM-209
URL: http://jira.codehaus.org/browse/MRM-209
Project: Archiva
Issue Type: Bug
Components: web application
Reporter: Dirk Olmes
The plexush.sh that's generated in the archiva-plexus-runtime model does not
include tools.jar to the classpath of the JVM that is started. This causes
error messages when first accessing the web application about being unable to
compile JSPs.
The last line of plexus.sh currently looks like this:
{code}
exec $JAVACMD \
$PLEXUS_OPTS \
-classpath ${PLEXUS_HOME}/core/boot/classworlds-*.jar \
{code}
but should have $TOOLS_JAR included in the -classpath argument's parameter.
--
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] Commented: (MASSEMBLY-90) add a DependencySet filter based on type
[ http://jira.codehaus.org/browse/MASSEMBLY-90?page=comments#action_79116 ] Richard van der Hoff commented on MASSEMBLY-90: --- Yup, that all seems to be working - thanks! add a DependencySet filter based on type Key: MASSEMBLY-90 URL: http://jira.codehaus.org/browse/MASSEMBLY-90 Project: Maven 2.x Assembly Plugin Issue Type: Improvement Reporter: Jason Chaffee Assigned To: John Casey Fix For: 2.2 Attachments: AbstractAssemblyMojo-patch.txt, AbstractAssemblyMojo.java, AbstractAssemblyMojo.java, AbstractAssemblyMojo.java, AssemblyClassifierArtifactFilter.java, AssemblyTypeArtifactFilter.java, AssemblyTypeArtifactFilter.java, component.mdo, component.mdo-patch.txt, descriptor.mdo, descriptor.mdo-patch-.txt It would be nice to create a distribution bundle that contains both jars and webapps. These would be built by different projects and then an assembly project would list these in the pom. However, there is no way to filter the dependencies based on their type. This would be be a pretty easy thing to add. I have attached a new class, AssemblyTypeArtifactFilter and the required change to AbstractAsseblyMojo. The DependencySet class needs to be modified as well to add the type field, but I was not able to find it in the maven repository. -- 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] Commented: (MRM-209) plexus.sh must include tools.jar on the classpath
[ http://jira.codehaus.org/browse/MRM-209?page=comments#action_79117 ]
Emmanuel Venisse commented on MRM-209:
--
it's fixed in plexus-appserver 2.0-alpha-4. We need to update it in Archiva.
plexus.sh must include tools.jar on the classpath
-
Key: MRM-209
URL: http://jira.codehaus.org/browse/MRM-209
Project: Archiva
Issue Type: Bug
Components: web application
Reporter: Dirk Olmes
The plexush.sh that's generated in the archiva-plexus-runtime model does not
include tools.jar to the classpath of the JVM that is started. This causes
error messages when first accessing the web application about being unable to
compile JSPs.
The last line of plexus.sh currently looks like this:
{code}
exec $JAVACMD \
$PLEXUS_OPTS \
-classpath ${PLEXUS_HOME}/core/boot/classworlds-*.jar \
{code}
but should have $TOOLS_JAR included in the -classpath argument's parameter.
--
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: (MWAR-48) review plugin documentation
[ http://jira.codehaus.org/browse/MWAR-48?page=all ] Brett Porter closed MWAR-48. Resolution: Fixed it was reopened for the additional patch, but not closed after being applied review plugin documentation --- Key: MWAR-48 URL: http://jira.codehaus.org/browse/MWAR-48 Project: Maven 2.x War Plugin Issue Type: Task Affects Versions: 2.0 Reporter: Marvin King Fix For: 2.0.2 Attachments: MWAR-48-maven-war-plugin[draft4-1-1].patch, MWAR-48-maven-war-plugin[draft4-1].patch, MWAR-48-maven-war-plugin[draft4].patch Time Spent: 1 day, 13 hours, 30 minutes Remaining Estimate: 0 minutes -- 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] Commented: (MCHECKSTYLE-59) Checkstyle Report fails if propertyExpansion contains file names
[ http://jira.codehaus.org/browse/MCHECKSTYLE-59?page=comments#action_79119
]
Carsten Karkola commented on MCHECKSTYLE-59:
Thank you for your hint, I tried the suggested solution. In the parent pom I
have:
suppressionsLocationde/mms_dresden/checkstyle/suppressions.xml/suppressionsLocation
headerLocationde/mms_dresden/checkstyle/mms_header_regexp.txt/headerLocation
On the console I get:
...
[INFO] Generate Checkstyle report.
[DEBUG] resolveLocation(de/mms_dresden/checkstyle/t_cruiting_checks.xml,
checkstyle-checker.xml)
[DEBUG] Location is not a URL.
[DEBUG] Location is not a File.
[DEBUG] Potential Resource:
jar:file:/D:/ckk/m2/de/telekom/mms-dresden/checkstyle/1.0/checkstyle-1.0.jar!/de/mms_dresden
/checkstyle/t_cruiting_checks.xml
[DEBUG] resolveLocation(null, checkstyle-checker.properties)
[DEBUG] resolveLocation(de/mms_dresden/checkstyle/mms_header_regexp.txt,
checkstyle-header.txt)
[DEBUG] Location is not a URL.
[DEBUG] Location is not a File.
[DEBUG] Potential Resource:
jar:file:/D:/ckk/m2/de/telekom/mms-dresden/checkstyle/1.0/checkstyle-1.0.jar!/de/mms_dresden
/checkstyle/mms_header_regexp.txt
[DEBUG] resolveLocation(null, checkstyle-packages.xml)
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error during page generation
Embedded error: Error rendering Maven report: Failed during checkstyle
configuration
Property ${checkstyle.suppressions.location} has not been set
[INFO]
The header variable is resolved, but the suppresions variable not?
Checkstyle Report fails if propertyExpansion contains file names
Key: MCHECKSTYLE-59
URL: http://jira.codehaus.org/browse/MCHECKSTYLE-59
Project: Maven 2.x Checkstyle Plugin
Issue Type: Bug
Affects Versions: 2.1
Environment: Windows XP, JDK 1.4, Maven 2.0.4
Reporter: Carsten Karkola
Assigned To: Joakim Erdfelt
The chechkstyle plugin fails on windows plattforms, if the propertyExpansion
element contains file names like
mms.suppressions.file=${basedir}/../../project/resources/checkstyle/suppressions.xml
The backslashes in ${basedir} (like D:\foo\bar) are missing (D:foobar) and
checkstyle fails. It seems to be an issue with StringInputStream.
I've replaced the following old code in CheckstyleReport.java
if ( StringUtils.isNotEmpty( propertyExpansion ) )
{
p.load( new StringInputStream( propertyExpansion ) );
}
with the new Code
if ( StringUtils.isNotEmpty( propertyExpansion ) ) {
BufferedReader reader = new BufferedReader(new
StringReader(propertyExpansion));
String line = reader.readLine();
while (line != null) {
int delimPosition = line.indexOf('=');
if (delimPosition -1) {
String name = line.substring(0, delimPosition).trim();
delimPosition++;
if (delimPosition line.length()) {
String value = line.substring(delimPosition).trim();
if (value.length() 0) {
p.put(name, value);
getLog().info(Property: + name + = +
p.getProperty(name));
}
}
}
line = reader.readLine();
}
reader.close();
}
and it works.
Regards, carsten
--
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] Updated: (MNG-2539) Transitive dependencies referenced by a plugin are searched only in the plugin-repositories
[ http://jira.codehaus.org/browse/MNG-2539?page=all ] John Casey updated MNG-2539: Attachment: mng-2539.zip This is a test for the issue. Simply call `mvn clean` Transitive dependencies referenced by a plugin are searched only in the plugin-repositories --- Key: MNG-2539 URL: http://jira.codehaus.org/browse/MNG-2539 Project: Maven 2 Issue Type: Bug Components: Plugins and Lifecycle, Dependencies Affects Versions: 2.0.4 Environment: WinXP, JDK 1.5_08 Reporter: Thomas Minor Fix For: 2.0.5 Attachments: mng-2539.zip Transitive dependencies referenced by a plugin are searched only in the plugin-repositories In my case, the axis plugin references th javax.activation artifact. this artifact is keep at our site in a 3rd-party repo. If this repo is only addressed in the Repositories, the build fails.If it is also refereced in the pluginRepositories everything works fine. Is this the intended practice? -- 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] Commented: (MNG-2539) Transitive dependencies referenced by a plugin are searched only in the plugin-repositories
[ http://jira.codehaus.org/browse/MNG-2539?page=comments#action_79124 ] John Casey commented on MNG-2539: - This is ready to close, but I want to hold off until I can find out from Jason how to add the attached test project into the core integration-test suite. Transitive dependencies referenced by a plugin are searched only in the plugin-repositories --- Key: MNG-2539 URL: http://jira.codehaus.org/browse/MNG-2539 Project: Maven 2 Issue Type: Bug Components: Plugins and Lifecycle, Dependencies Affects Versions: 2.0.4 Environment: WinXP, JDK 1.5_08 Reporter: Thomas Minor Fix For: 2.0.5 Attachments: mng-2539.zip Transitive dependencies referenced by a plugin are searched only in the plugin-repositories In my case, the axis plugin references th javax.activation artifact. this artifact is keep at our site in a 3rd-party repo. If this repo is only addressed in the Repositories, the build fails.If it is also refereced in the pluginRepositories everything works fine. Is this the intended practice? -- 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] Updated: (MNG-2117) Update doap file descriptor
[ http://jira.codehaus.org/browse/MNG-2117?page=all ] Kenney Westerhof updated MNG-2117: -- Fix Version/s: (was: 2.0.5) 2.0.6 Update doap file descriptor --- Key: MNG-2117 URL: http://jira.codehaus.org/browse/MNG-2117 Project: Maven 2 Issue Type: Task Components: Sites Reporting Affects Versions: 2.0.3 Reporter: Emmanuel Venisse Fix For: 2.0.6 -- 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] Updated: (MNG-1981) move maven snapshots to the apache snapshot repo
[ http://jira.codehaus.org/browse/MNG-1981?page=all ] Kenney Westerhof updated MNG-1981: -- Fix Version/s: (was: 2.0.5) 2.0.6 move maven snapshots to the apache snapshot repo Key: MNG-1981 URL: http://jira.codehaus.org/browse/MNG-1981 Project: Maven 2 Issue Type: Bug Components: Bootstrap Build Reporter: Brett Porter Fix For: 2.0.6 -- 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] Updated: (MNG-1204) don't show disabled repositories in artifact exceptions
[ http://jira.codehaus.org/browse/MNG-1204?page=all ] Kenney Westerhof updated MNG-1204: -- Fix Version/s: (was: 2.0.5) 2.0.6 don't show disabled repositories in artifact exceptions --- Key: MNG-1204 URL: http://jira.codehaus.org/browse/MNG-1204 Project: Maven 2 Issue Type: Bug Components: Artifacts and Repositories Reporter: Brett Porter Assigned To: Edwin Punzalan Priority: Minor Fix For: 2.0.6 Attachments: MNG-1204-maven-artifact.patch -- 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] Updated: (MNG-2352) Upgrade to plexus-container-default-alpha-10
[ http://jira.codehaus.org/browse/MNG-2352?page=all ] Kenney Westerhof updated MNG-2352: -- Fix Version/s: (was: 2.0.5) 2.0.6 Upgrade to plexus-container-default-alpha-10 Key: MNG-2352 URL: http://jira.codehaus.org/browse/MNG-2352 Project: Maven 2 Issue Type: Improvement Reporter: Jerome Lacoste Priority: Blocker Fix For: 2.0.6 Attachments: MNG-2352.diff This is required for MNG-2201 in particular. -- 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] Updated: (MNG-2386) document how to write packaging plugins
[ http://jira.codehaus.org/browse/MNG-2386?page=all ] Kenney Westerhof updated MNG-2386: -- Fix Version/s: (was: 2.0.5) 2.0.6 document how to write packaging plugins --- Key: MNG-2386 URL: http://jira.codehaus.org/browse/MNG-2386 Project: Maven 2 Issue Type: Task Components: Documentation: Guides Reporter: Brett Porter Fix For: 2.0.6 we particularly need to highlight that this: project.getArtifact().setFile( fileYouGenerated ) must be called, as well as referencing the appropriate components definitions from the lifecycle introduction. (ideally, we could get rid of the requirement for the above, but it is a necessity in 2.0) -- 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] Updated: (MNG-2339) ${project.*} are interpreted in the wrong place
[ http://jira.codehaus.org/browse/MNG-2339?page=all ]
Kenney Westerhof updated MNG-2339:
--
Fix Version/s: (was: 2.0.5)
2.0.6
${project.*} are interpreted in the wrong place
---
Key: MNG-2339
URL: http://jira.codehaus.org/browse/MNG-2339
Project: Maven 2
Issue Type: Bug
Components: General
Affects Versions: 2.0.4
Reporter: Emmanuel Venisse
Priority: Critical
Fix For: 2.0.6
If a plugin use ${project.version}, this parameter is interpreted with the
version of the current project and not the plugin version. I think we have
the same pb with dependencies and other ${project.*}
For a plugin in version 2.0 used in a project in version 1.0-SNAPSHOT,
${project.version} used in the plugin will be interpreted as 1.0-SNAPSHOT
instead of 2.0
--
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] Updated: (MNG-1128) Create an archetype demonstrating the use of profiles targeting different environments
[ http://jira.codehaus.org/browse/MNG-1128?page=all ] Kenney Westerhof updated MNG-1128: -- Fix Version/s: (was: 2.0.5) 2.0.6 Create an archetype demonstrating the use of profiles targeting different environments -- Key: MNG-1128 URL: http://jira.codehaus.org/browse/MNG-1128 Project: Maven 2 Issue Type: New Feature Components: Documentation: General Reporter: Jason van Zyl Fix For: 2.0.6 Having an archetype which encapsulates how to use profiles to in order to do things like filtering log4.properties files according to their target environment would be useful. -- 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] Updated: (MNG-1928) ignores pluginRepository in settings.xml, honors in POM
[ http://jira.codehaus.org/browse/MNG-1928?page=all ] Kenney Westerhof updated MNG-1928: -- Fix Version/s: (was: 2.0.5) 2.0.6 ignores pluginRepository in settings.xml, honors in POM --- Key: MNG-1928 URL: http://jira.codehaus.org/browse/MNG-1928 Project: Maven 2 Issue Type: Bug Components: Plugins and Lifecycle Affects Versions: 2.0.1 Environment: mvn 2.0.1, jvm 1.5.0_05, OSX 10.4.3 Reporter: Ryan Marsh Fix For: 2.0.6 if specified in the POM as a plugin repo, maven can use the team.andromda.org/maven2 repo for finding, downloading, and installing plugins. however, settings.xml ignores plugin repos and only checks central if the plugin has never been downloaded before. for instance. if settings.xml has a pluginRepository entry for team.andromda.org/maven2 then: mvn andromdapp:generate should download the andromdapp plugin from our repo. but it doesn't. only central is checked and it fails to find the plugin. -- 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] Updated: (MNG-1299) Document m1 xdocs compatibility with the m2 site plug-in
[ http://jira.codehaus.org/browse/MNG-1299?page=all ]
Kenney Westerhof updated MNG-1299:
--
Fix Version/s: (was: 2.0.5)
2.0.6
Document m1 xdocs compatibility with the m2 site plug-in
Key: MNG-1299
URL: http://jira.codehaus.org/browse/MNG-1299
Project: Maven 2
Issue Type: Improvement
Reporter: Jason van Zyl
Fix For: 2.0.6
The m2 site plugin now supports the ${basedir}/xdocs directory.
--
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] Updated: (MNG-1522) assembly guide enhancements
[ http://jira.codehaus.org/browse/MNG-1522?page=all ] Kenney Westerhof updated MNG-1522: -- Fix Version/s: (was: 2.0.5) 2.0.6 assembly guide enhancements --- Key: MNG-1522 URL: http://jira.codehaus.org/browse/MNG-1522 Project: Maven 2 Issue Type: Task Components: Documentation: Guides Reporter: Brett Porter Fix For: 2.0.6 - describe dependency sets - describe default descriptors (bin, src, jar-with-dependencies) - link to generated descriptor reference - link to actualy plugin reference -- 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] Updated: (MNG-2056) Exception when starting new page with AbstractMavenMultiPageReport
[ http://jira.codehaus.org/browse/MNG-2056?page=all ] Kenney Westerhof updated MNG-2056: -- Fix Version/s: (was: 2.0.5) 2.0.6 Exception when starting new page with AbstractMavenMultiPageReport -- Key: MNG-2056 URL: http://jira.codehaus.org/browse/MNG-2056 Project: Maven 2 Issue Type: Bug Components: Sites Reporting Affects Versions: 2.0.2 Environment: OS X 10.3.4. running JDK 1.5 (1.5.0_06-93) Reporter: Adam Winer Fix For: 2.0.6 Attempts to call AbstractMavenMultiPageReport.startPage() from a custom report result in the following exception: Caused by: java.io.EOFException: input contained no data at org.codehaus.plexus.util.xml.pull.MXParser.fillBuf(MXParser.java:2979) at org.codehaus.plexus.util.xml.pull.MXParser.more(MXParser.java:3022) at org.codehaus.plexus.util.xml.pull.MXParser.parseProlog(MXParser.java:1407) at org.codehaus.plexus.util.xml.pull.MXParser.nextImpl(MXParser.java:1392) at org.codehaus.plexus.util.xml.pull.MXParser.next(MXParser.java:1090) at org.codehaus.plexus.util.xml.Xpp3DomBuilder.build(Xpp3DomBuilder.java:172) at org.codehaus.plexus.util.xml.Xpp3DomBuilder.build(Xpp3DomBuilder.java:83) at org.codehaus.plexus.util.xml.Xpp3DomBuilder.build(Xpp3DomBuilder.java:48) at org.codehaus.doxia.module.xhtml.decoration.model.DecorationModelReader.createNavigation(DecorationModelReader.java:30) at org.codehaus.doxia.site.renderer.DefaultSiteRenderer.createSink(DefaultSiteRenderer.java:244) at org.apache.maven.reporting.sink.SinkFactory.getSink(SinkFactory.java:76) at org.apache.maven.reporting.AbstractMavenMultiPageReport.getSink(AbstractMavenMultiPageReport.java:79) at org.apache.maven.reporting.AbstractMavenMultiPageReport.startPage(AbstractMavenMultiPageReport.java:85) FYI, I'm creating the SinkFactory for the multipage report using: SinkFactory factory = new SinkFactory(); factory.setSiteRenderer(getSiteRenderer()); factory.setSiteDirectory(getOutputDirectory()); setSinkFactory(factory); Without this code, you just get a NullPointerException in AbstractMavenMultiPageReport.getSink(). -- 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] Updated: (MNG-1323) Plugin extensions (dependencies) not resolved in reactor build
[ http://jira.codehaus.org/browse/MNG-1323?page=all ] Kenney Westerhof updated MNG-1323: -- Fix Version/s: (was: 2.0.5) 2.0.6 Plugin extensions (dependencies) not resolved in reactor build -- Key: MNG-1323 URL: http://jira.codehaus.org/browse/MNG-1323 Project: Maven 2 Issue Type: Bug Components: Plugins and Lifecycle Affects Versions: 2.0 Reporter: Kenney Westerhof Fix For: 2.0.6 I've added a dependency on an Ant Task in project/build/plugins/plugin[artifactId='maven-antrun-plugin']/dependencies/ and run that anttask using the antrun plugin. When run from the project dir itself it runs fine. When running from the root of the project tree (reactor build, project one level below root), antrun bails out because the taskdef can't be found (not on classpath). It looks like the dependency isn't resolved, or not added to the plugins' classrealm. -- 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] Updated: (MNG-1290) What is a Mojo?
[ http://jira.codehaus.org/browse/MNG-1290?page=all ] Kenney Westerhof updated MNG-1290: -- Fix Version/s: (was: 2.0.5) 2.0.6 What is a Mojo? --- Key: MNG-1290 URL: http://jira.codehaus.org/browse/MNG-1290 Project: Maven 2 Issue Type: Bug Components: Documentation: General Affects Versions: 2.0 Reporter: Binil Thomas Fix For: 2.0.6 On http://maven.apache.org/developers/mojo-api-specification.html page titled Mojo API, I see : snip Starting with Maven 2.0, plugins can be written in Java or any of a number of scripting languages. Additionally, Maven tries to stay out of the way of the programmer with its new Mojo API. This opens up the opportunity for many Mojos to be reused outside of Maven, or bridged into Maven from external systems like Ant. /snip The first line states a fact - that Maven plugins can now be written in plain Java. The second line doesnt suggest anything to me besides the irritating name-dropping Mojo API. The third line adds further confusion by the usage many Mojos planting the supiscion that this things called Mojo might be more than an API! Two paragraph later, I see: snip As mentioned before, each Plugin - or packaged set of Mojos .. /snip Ah! so thats it - Mojo is what constitues a Maven plugin - and there might be some API to write these. It would have been much less intimidating had this fact be stated upfront. A note here - the term plugin was did not need any introduction to me - because it is a widely one used in the software scene. At this point I don't even know what a Maven plugin can do - yet I have a vague notion that a plugin might be something that enhances the out-of-the-box behaviour of Maven. The same familiarity does not apply to the term Mojo - I am guessing here, but I think the Maven team invented the term. If so, kindly desrcibe it fully instead of confusing the reader. -- 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] Updated: (MNG-1911) Building plugins with extensions in a reactor fails
[ http://jira.codehaus.org/browse/MNG-1911?page=all ] Kenney Westerhof updated MNG-1911: -- Fix Version/s: (was: 2.0.5) 2.0.6 Building plugins with extensions in a reactor fails --- Key: MNG-1911 URL: http://jira.codehaus.org/browse/MNG-1911 Project: Maven 2 Issue Type: Bug Affects Versions: 2.0.1 Reporter: Guillaume Nodet Priority: Critical Fix For: 2.0.6 I have the following in my main pom build pluginManagement plugins plugin groupIdorg.apache.servicemix.plugins/groupId artifactIdmaven2-jbi-plugin/artifactId version1.0-SNAPSHOT/version extensionstrue/extensions /plugin /plugins /pluginManagement /build If i try to add it to the modules, the first time, maven complains that it can not download the plugin. If i remove the extensions tag, all works, but i need 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
[jira] Updated: (MNG-1169) Support profiles in pom type
[ http://jira.codehaus.org/browse/MNG-1169?page=all ] Kenney Westerhof updated MNG-1169: -- Fix Version/s: (was: 2.0.5) 2.0.6 Support profiles in pom type Key: MNG-1169 URL: http://jira.codehaus.org/browse/MNG-1169 Project: Maven 2 Issue Type: Improvement Components: Ant tasks Affects Versions: 2.0 (RC) Reporter: Mark Hobson Fix For: 2.0.6 Need to be able to pass in a list of profiles to activate in pom type - there's currently a TODO in Pom.java for 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
[jira] Updated: (MNG-2392) document relativePath/
[ http://jira.codehaus.org/browse/MNG-2392?page=all ] Kenney Westerhof updated MNG-2392: -- Fix Version/s: (was: 2.0.5) 2.0.6 document relativePath/ Key: MNG-2392 URL: http://jira.codehaus.org/browse/MNG-2392 Project: Maven 2 Issue Type: Task Components: Documentation: General Reporter: Brett Porter Fix For: 2.0.6 see: http://mail-archives.apache.org/mod_mbox/maven-users/200511.mbox/[EMAIL PROTECTED] -- 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] Updated: (MNG-1818) update team list
[ http://jira.codehaus.org/browse/MNG-1818?page=all ] Kenney Westerhof updated MNG-1818: -- Fix Version/s: (was: 2.0.5) 2.0.6 update team list Key: MNG-1818 URL: http://jira.codehaus.org/browse/MNG-1818 Project: Maven 2 Issue Type: Task Components: Documentation: General Reporter: Brett Porter Fix For: 2.0.6 1) list all pmc members 2) list all committers in developers 3) seek out Submitted by in svn logs to populate contributors -- 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] Updated: (MNG-1379) Wrong path for artifacts with system scope
[ http://jira.codehaus.org/browse/MNG-1379?page=all ] Kenney Westerhof updated MNG-1379: -- Fix Version/s: (was: 2.0.5) 2.0.6 Wrong path for artifacts with system scope -- Key: MNG-1379 URL: http://jira.codehaus.org/browse/MNG-1379 Project: Maven 2 Issue Type: Bug Components: Plugins and Lifecycle Affects Versions: 2.0 Reporter: fabrizio giustina Assigned To: Edwin Punzalan Fix For: 2.0.6 Attachments: MNG-1379-maven-project.patch For system dependencies artifact.getFile() returns a wrong file. While dependency.getSystemPath() correctly returns the user-set path, artifact.getPath always returns the path in the local repository. For example a dependency with system path = /test.jar will result in: dependency.getSystemPath() = /test.jar artifact.getFile().getAbsolutePath()= M2_REPO/groupid/artifactid/version/artifactid-1.0.jar -- 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] Updated: (MNG-2349) dependency management, report-plugins and deploy-site
[ http://jira.codehaus.org/browse/MNG-2349?page=all ] Kenney Westerhof updated MNG-2349: -- Fix Version/s: (was: 2.0.5) 2.0.6 dependency management, report-plugins and deploy-site - Key: MNG-2349 URL: http://jira.codehaus.org/browse/MNG-2349 Project: Maven 2 Issue Type: Bug Affects Versions: 2.0.4 Environment: jdk 1.4.2_11, windows 2000 Reporter: Thiago Gozzi Prado Fix For: 2.0.6 Attachments: myproject.zip When I run mvn -e clean site site-deploy for the root pom, maven throws a NullPointerException. If I remove the javadoc report plugin declaration, the site is deployed. Or if I keep the javadoc report plugin declaration, but remove the dependency management declaration, the site is deployed. This happens for some report plugins, not all. Checkstyle, for instance, works fine. myproject.zip contains the project structure and the project definition. -- 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] Updated: (MNG-2341) Shell script mvn too old
[ http://jira.codehaus.org/browse/MNG-2341?page=all ] Kenney Westerhof updated MNG-2341: -- Fix Version/s: (was: 2.0.5) 2.0.6 Shell script mvn too old Key: MNG-2341 URL: http://jira.codehaus.org/browse/MNG-2341 Project: Maven 2 Issue Type: Bug Components: Command Line Affects Versions: 2.0.4 Environment: For *nix OS (Linux, *BSD etc.) Reporter: Vitaly Berdinskikh Fix For: 2.0.6 Shell script not equivalent on content mvn.bat. In mvn use old environment variable MAVEN_HOME instead of M2_HOME: quote ... if [ -z $M2_HOME ] ; then # try to find MAVEN if [ -d /opt/m2 ] ; then MAVEN_HOME=/opt/m2 fi if [ -d $HOME/m2 ] ; then MAVEN_HOME=$HOME/m2 fi ## resolve links - $0 may be a link to maven's home PRG=$0 # need this for relative symlinks while [ -h $PRG ] ; do ls=`ls -ld $PRG` link=`expr $ls : '.*- \(.*\)$'` if expr $link : '/.*' /dev/null; then PRG=$link else PRG=`dirname $PRG`/$link fi done saveddir=`pwd` M2_HOME=`dirname $PRG`/.. # make it fully qualified M2_HOME=`cd $M2_HOME pwd` cd $saveddir # echo Using m2 at $M2_HOME fi ... quote Also in header present old string of copyright, absent description used environment varibles unlike mvn.bat. -- 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] Updated: (MNG-2230) The How do I create documentation? part of the Maven Gettting Started Guide features an invalid example
[ http://jira.codehaus.org/browse/MNG-2230?page=all ] Kenney Westerhof updated MNG-2230: -- Fix Version/s: (was: 2.0.5) 2.0.6 The How do I create documentation? part of the Maven Gettting Started Guide features an invalid example --- Key: MNG-2230 URL: http://jira.codehaus.org/browse/MNG-2230 Project: Maven 2 Issue Type: Bug Components: Documentation: Guides Reporter: Timo Westkämper Priority: Minor Fix For: 2.0.6 The guide gives earlier the following example of a simple project creation : mvn archetype:create -DgroupId=com.mycompany.app -DartifactId=my-app Afterwards it gives the following example under How do I create documentation?: To get you jump started with Maven's documentation system you can use the archetype mechanism to generate a site for you without your existing project using the following command: mvn archetype:create -DgroupId=com.mycompany.app -DartifactId=my-app -DarchetypeGroupId=org.apache.maven.archetypes -DarchetypeArtifactId=maven-archetype-site When executed on the same top level where the first project is created, Maven 2 complains my-app already exists - please run from a clean directory When executed in the my-app directory the generated directory is different from the one presented. A possible solution could be to replace the text under How do I create documentation? with (other artifactId and some other changes): To get you jump started with Maven's documentation system you can use the archetype mechanism to generate a site for you without your existing project using the following command : mvn archetype:create -DgroupId=com.mycompany.app -DartifactId=my-app-site -DarchetypeGroupId=org.apache.maven.archetypes -DarchetypeArtifactId=maven-archetype-site If you take a look in your directory structure it should look like the following: my-app-site |-- pom.xml `-- src `-- site |-- apt | |-- format.apt | `-- index.apt |-- fml | `-- faq.fml |-- fr | |-- apt | | |-- format.apt | | `-- index.apt | |-- fml | | `-- faq.fml | `-- xdoc | `-- xdoc.xml |-- site.xml |-- site_fr.xml `-- xdoc `-- xdoc.xml Br, Timo Westkämper. -- 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] Updated: (MNG-1486) Can't use pom properties inside resource directory tag
[ http://jira.codehaus.org/browse/MNG-1486?page=all ]
Kenney Westerhof updated MNG-1486:
--
Fix Version/s: (was: 2.0.5)
2.0.6
Can't use pom properties inside resource directory tag
---
Key: MNG-1486
URL: http://jira.codehaus.org/browse/MNG-1486
Project: Maven 2
Issue Type: Bug
Components: Inheritence and Interpolation
Affects Versions: 2.0
Reporter: Filip Vuksanovic
Priority: Minor
Fix For: 2.0.6
I have pom.xml with following snippet:
build
sourceDirectorysrc\JavaSource/sourceDirectory
resources
resource
directorysrc\JavaSource/directory
and it works.
If I use property like this
build
sourceDirectorysrc\JavaSource/sourceDirectory
resources
resource
directory${project.build.sourceDirectory}/directory
it doesn't work.
--
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] Updated: (MNG-2061) DistributionManagement properties don't get copied in cloned executionProject while lifecycle fork
[ http://jira.codehaus.org/browse/MNG-2061?page=all ] Kenney Westerhof updated MNG-2061: -- Fix Version/s: (was: 2.0.5) 2.0.6 DistributionManagement properties don't get copied in cloned executionProject while lifecycle fork -- Key: MNG-2061 URL: http://jira.codehaus.org/browse/MNG-2061 Project: Maven 2 Issue Type: Bug Components: Plugins and Lifecycle Affects Versions: 2.0.2 Reporter: Max Feldman Fix For: 2.0.6 Define a new Maven plugin with the goal described like this: /** * @execute phase=deploy * @goal deploy-custom */ When running 'mvn deploy-custom', deploy phase execution fails with 'Class 'org.apache.maven.artifact.repository.ArtifactRepository' cannot be instantiated'. It seems the problem raises from the fact that releaseArtifactRepository/snapshotArtifactRepository don't get copied in the cloned executionProject while lifecycle fork. -- 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] Updated: (MNG-1962) allow empty deprecation messages in plugin descriptor/annotation and document usage of deprecation in descriptor/annotation.
[ http://jira.codehaus.org/browse/MNG-1962?page=all ] Kenney Westerhof updated MNG-1962: -- Fix Version/s: (was: 2.0.5) 2.0.6 allow empty deprecation messages in plugin descriptor/annotation and document usage of deprecation in descriptor/annotation. Key: MNG-1962 URL: http://jira.codehaus.org/browse/MNG-1962 Project: Maven 2 Issue Type: Improvement Components: Documentation: General, Plugin Creation Tools Affects Versions: 2.0.1 Reporter: John Casey Priority: Minor Fix For: 2.0.6 currently, the deprecation features for plugins (not the java deprecation mechanism, necessarily) require a message for the deprecation warning to be printed. This point is poorly documented. Allow an empty deprecation message (make one up when the plugin descriptor is read, if the deprecation/ element is present but empty), and then document the usage of plugin deprecations at the class and parameter level. -- 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] Updated: (MNG-2539) Transitive dependencies referenced by a plugin are searched only in the plugin-repositories
[ http://jira.codehaus.org/browse/MNG-2539?page=all ] Kenney Westerhof updated MNG-2539: -- Fix Version/s: (was: 2.0.5) 2.0.6 Transitive dependencies referenced by a plugin are searched only in the plugin-repositories --- Key: MNG-2539 URL: http://jira.codehaus.org/browse/MNG-2539 Project: Maven 2 Issue Type: Bug Components: Plugins and Lifecycle, Dependencies Affects Versions: 2.0.4 Environment: WinXP, JDK 1.5_08 Reporter: Thomas Minor Assigned To: John Casey Fix For: 2.0.6 Attachments: mng-2539.zip Transitive dependencies referenced by a plugin are searched only in the plugin-repositories In my case, the axis plugin references th javax.activation artifact. this artifact is keep at our site in a 3rd-party repo. If this repo is only addressed in the Repositories, the build fails.If it is also refereced in the pluginRepositories everything works fine. Is this the intended practice? -- 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] Updated: (MNG-1508) Need a process-test-classes phase
[ http://jira.codehaus.org/browse/MNG-1508?page=all ] Kenney Westerhof updated MNG-1508: -- Fix Version/s: (was: 2.0.5) 2.0.6 Need a process-test-classes phase - Key: MNG-1508 URL: http://jira.codehaus.org/browse/MNG-1508 Project: Maven 2 Issue Type: Improvement Components: Design, Patterns Best Practices Affects Versions: 2.0 Reporter: Mike Perham Fix For: 2.0.6 The compile phase has a process-classes phase after it to do instrumentation. The test-compile phase should have a similar phase after it also. -- 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] Updated: (MNG-1592) Top level element in POM is not correctly validated
[ http://jira.codehaus.org/browse/MNG-1592?page=all ] Kenney Westerhof updated MNG-1592: -- Fix Version/s: (was: 2.0.5) 2.0.6 Top level element in POM is not correctly validated --- Key: MNG-1592 URL: http://jira.codehaus.org/browse/MNG-1592 Project: Maven 2 Issue Type: Bug Components: Plugins and Lifecycle Affects Versions: 2.0 Reporter: Carlos Sanchez Fix For: 2.0.6 Attachments: it1019.patch this pom doesn't make the build break modelzz modelVersion4.0.0/modelVersion groupIdtest/groupId artifactIdtest/artifactId version1.0/version /modelzz and I'm starting to see wrong poms with a top level model instead of 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
[jira] Updated: (MNG-2299) org.apache.maven.it.Verifier.loadProperties(..) does not close FileInputStream (relies upon finalizer being called)
[ http://jira.codehaus.org/browse/MNG-2299?page=all ] Kenney Westerhof updated MNG-2299: -- Fix Version/s: (was: 2.0.5) 2.0.6 org.apache.maven.it.Verifier.loadProperties(..) does not close FileInputStream (relies upon finalizer being called) --- Key: MNG-2299 URL: http://jira.codehaus.org/browse/MNG-2299 Project: Maven 2 Issue Type: Bug Components: Performance Reporter: John Sisson Fix For: 2.0.6 Attachments: verifier.patch The loadProperties(..) method in the Verifier class needs to close the FileInputStream. See attached patch. -- 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] Updated: (MNG-2010) Add new lifecycle phases for IT
[ http://jira.codehaus.org/browse/MNG-2010?page=all ] Kenney Westerhof updated MNG-2010: -- Fix Version/s: (was: 2.0.5) 2.0.6 Add new lifecycle phases for IT --- Key: MNG-2010 URL: http://jira.codehaus.org/browse/MNG-2010 Project: Maven 2 Issue Type: Task Components: Plugins and Lifecycle, integration tests Reporter: Vincent Massol Fix For: 2.0.6 Namely: * generate-integration-test-sources * process-integration-test-sources * generate-integration-test-resources * process-integration-test-resources * integration-test-compile and possibly a: * integration-test-package -- 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] Updated: (MNG-2165) Provide links to release notes on download page, navigation, and README.txt in binaries
[ http://jira.codehaus.org/browse/MNG-2165?page=all ] Kenney Westerhof updated MNG-2165: -- Fix Version/s: (was: 2.0.5) 2.0.6 Provide links to release notes on download page, navigation, and README.txt in binaries --- Key: MNG-2165 URL: http://jira.codehaus.org/browse/MNG-2165 Project: Maven 2 Issue Type: Task Components: Documentation: General Reporter: Anuerin Diaz Priority: Minor Fix For: 2.0.6 The downlodable binary distribution of Maven does not include any release notes which is helpful to people who needs to analyze what exactly has changed in each version (contrary to the latest and the greatest mindset). It might be possible to get a list using JIRA but it would be convenient if each (fix) distribution can include a file listing the major enhancements and bug fixes similar to the following format: ver 2.0.2 - change 1 - bugfix for bleh ver 2.0.1 - enhancement 1 - new feature even a listing of the JIRA numbers (and some summary) of the included fixes and enhancement would be useful in this regard. Thank you. -- 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] Updated: (MNG-1494) Create comprehensive m2 feature list
[ http://jira.codehaus.org/browse/MNG-1494?page=all ] Kenney Westerhof updated MNG-1494: -- Fix Version/s: (was: 2.0.5) 2.0.6 Create comprehensive m2 feature list Key: MNG-1494 URL: http://jira.codehaus.org/browse/MNG-1494 Project: Maven 2 Issue Type: New Feature Components: Documentation: General Reporter: Jason van Zyl Fix For: 2.0.6 -- 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] Updated: (MNG-1325) Document ibiblio synchronization process
[ http://jira.codehaus.org/browse/MNG-1325?page=all ] Kenney Westerhof updated MNG-1325: -- Fix Version/s: (was: 2.0.5) 2.0.6 Document ibiblio synchronization process Key: MNG-1325 URL: http://jira.codehaus.org/browse/MNG-1325 Project: Maven 2 Issue Type: Task Reporter: Carlos Sanchez Assigned To: Carlos Sanchez Fix For: 2.0.6 -- 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] Updated: (MNG-1256) antlib + http based repository + version range errors badly
[ http://jira.codehaus.org/browse/MNG-1256?page=all ]
Kenney Westerhof updated MNG-1256:
--
Fix Version/s: (was: 2.0.5)
2.0.6
antlib + http based repository + version range errors badly
---
Key: MNG-1256
URL: http://jira.codehaus.org/browse/MNG-1256
Project: Maven 2
Issue Type: Bug
Components: Ant tasks
Environment: maven 2.0 (release), antlib, ant, apache 2 webserver on
windows
Reporter: spencer portee
Priority: Critical
Fix For: 2.0.6
In my pom file, I have a dependency, it has no child dependencies beyond that
looks like this:
dependency
groupIdorg.sporty/groupId
artifactIdxwork/artifactId
version[1.0.5,1.1)/version
scoperuntime/scope
/dependency
and use the following in my build script:
artifact:dependencies verbose=true useScope=runtime
pathId=project.classpath.runtime
artifact:pom file=pom.xml /
artifact:remoteRepository url=${project.repository}
layout=default /
/artifact:dependencies
The variable I have above is being set right per tests 1-3. The last test..
it gets strange.
I deployed xwork, as an empty jar by accident, so don't be surprised there's
nothing in the jar. But the dependency downloading from the webserver breaks
horribly. I tested 4 scenarios:
1. If I put in my pom as my remote repository as file://c:/temp/repository
and deploy to there, the above pom works flawlessly.
2 3. If I replace the range w/ a simple: version1.0.5/version and set
my repository to http://sporty.org/java/repository, it downloads fine as
well. It works with the filesystem remote repository of my c:/temp...
directory.
4. If I use the http repository AND use a range version as I originally
wanted, I get an ugly error:
C:\development\eclipse 3.0\workspace\hibernate-3\common.xml:4: Unable to
resolve
artifact: Unable to get dependency information: Unable to read local copy of
me
tadata: Cannot read metadata from 'C:\Documents and
Settings\sportee\.m2\reposit
ory\org\sporty\xwork\maven-metadata-remote.xml': end tag name /pre must
match
start tag name hr from line 11 (position: START_TAG seen .../a
11-Oct-2005 17:52- \nhr/pre... @11:11)
org.sporty:xwork:null:jar
from the specified remote repositories:
remote (http://sporty.org/java/repository )
Path to dependency:
1) org.sporty:xdoclet-xwork:jar:1.0-SNAPSHOT
--
The contents of the ...-remote.xml file, I see a directory listing, and not
the contents of the repository file on the server. My naive guess is the
repository file to look for is getting lost, or not passed, if it's in a
hashmap, not being referenced properly...
Thanks,
-s
--
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] Updated: (MNG-2267) Introduction to Repositories contains incorrect information
[ http://jira.codehaus.org/browse/MNG-2267?page=all ] Kenney Westerhof updated MNG-2267: -- Fix Version/s: (was: 2.0.5) 2.0.6 Introduction to Repositories contains incorrect information --- Key: MNG-2267 URL: http://jira.codehaus.org/browse/MNG-2267 Project: Maven 2 Issue Type: Bug Components: Documentation: Introductions Reporter: David Jackman Fix For: 2.0.6 The Introduction to Repositories document contains some incorrect information. I can't be certain everything that's incorrect (if I knew everything already I wouldn't have been reading the page), but here's a list of some things I'm pretty sure are incorrect or incomplete: * Downloading from a Remote Repository talks about build.properties and project.properties, and I thought these were no longer used in Maven 2. * Building Offline section should be expanded a bit. It only makes sense if you already know what it's talking about. * The example in Using the Internal Repository doesn't have a url element, which the previous example does have. * These examples show the tags to use, but give no examples of values for these tags or explain what they mean or how to come up with values. A start-to-finish example of creating a repository and setting a project/environment up to use it would be most helpful. Would that sort of thing belong in this introduction document, or would it be better suited in one of the guide documents? -- 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] Updated: (MNG-2438) search for metadata in legacy repositories causes wrong repository source to be used for artifact resolution
[ http://jira.codehaus.org/browse/MNG-2438?page=all ] Kenney Westerhof updated MNG-2438: -- Fix Version/s: (was: 2.0.5) 2.0.6 search for metadata in legacy repositories causes wrong repository source to be used for artifact resolution Key: MNG-2438 URL: http://jira.codehaus.org/browse/MNG-2438 Project: Maven 2 Issue Type: Bug Components: Artifacts and Repositories Affects Versions: 2.0.4 Reporter: John Casey Fix For: 2.0.6 legacy repositories store all version metadata in a single file under the /poms/ subdirectory of the artifactId dir. This means that snapshot resolution will result in the legacy repository being marked as the source for the artifact, regardless of whether that metadata file contains the snapshot is actually in that repository's metadata file or not. This is because the metadata manager (and metadata class itself, possibly) assumes that all metadata files resolved for a particular artifact/snapshot are relevant to that snapshot...when the legacy repo's metadata is merged into the rest of the in-progress metadata, changes are detected, and the legacy repo is adopted as the source for the latest artifact information, regardless of whether it actually contains information about that snapshot or 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
[jira] Updated: (MNG-2213) Current settings.xml example incorrect
[ http://jira.codehaus.org/browse/MNG-2213?page=all ] Kenney Westerhof updated MNG-2213: -- Fix Version/s: (was: 2.0.5) 2.0.6 Current settings.xml example incorrect --- Key: MNG-2213 URL: http://jira.codehaus.org/browse/MNG-2213 Project: Maven 2 Issue Type: Improvement Affects Versions: 2.0.3 Reporter: Todd Nine Fix For: 2.0.6 The settings.xml in the example is incorrect. The child tags of repository and pluginRepository are releases and snapshots, not release and snapshot. Todd -- 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] Updated: (MNG-2379) review and link to free Maven courseware
[ http://jira.codehaus.org/browse/MNG-2379?page=all ] Kenney Westerhof updated MNG-2379: -- Fix Version/s: (was: 2.0.5) 2.0.6 review and link to free Maven courseware Key: MNG-2379 URL: http://jira.codehaus.org/browse/MNG-2379 Project: Maven 2 Issue Type: Improvement Components: Documentation: General Reporter: Brett Porter Fix For: 2.0.6 http://cvs.peopleware.be/training/maven/maven2/ Could be in the articles/books section -- 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] Updated: (MNG-1985) Triggering Profiles bugs
[ http://jira.codehaus.org/browse/MNG-1985?page=all ] Kenney Westerhof updated MNG-1985: -- Fix Version/s: (was: 2.0.5) 2.0.6 Triggering Profiles bugs Key: MNG-1985 URL: http://jira.codehaus.org/browse/MNG-1985 Project: Maven 2 Issue Type: Bug Affects Versions: 2.0.2 Environment: windows2000 maven 2.02 Reporter: pinghe Priority: Critical Fix For: 2.0.6 ===env 1, inside pom.xml profiles profile idenv-common/id activation activeByDefaulttrue/activeByDefault /activation /profile profile idos-win32/id activation activeByDefaulttrue/activeByDefault !--os familywindows/family /os-- property nameperformRelease/name /property /activation /profile profile idenv-prod/id activation property nameperformRelease/name /property /activation /profile /profiles exec: mvn projecthelp:active-profiles output: - env-common (source: pom) - os-win32 (source: pom) exec: mvn projecthelp:active-profiles -DperformRelease output: - env-prod (source: pom) - os-win32 (source: pom) expect: - env-prod (source: pom) - os-win32 (source: pom) - env-common (source: pom) ===env 2: inside pom.xml profiles profile idenv-common/id activation activeByDefaulttrue/activeByDefault /activation /profile profile idos-win32/id activation activeByDefaulttrue/activeByDefault os familywindows/family /os property nameperformRelease/name /property /activation /profile profile idenv-prod/id activation property nameperformRelease/name /property /activation /profile /profiles exec: mvn projecthelp:active-profiles output: - os-win32 (source: pom) expect: - env-prod (source: pom) - os-win32 (source: pom) -- 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] Updated: (MNG-1106) Stdout in MavenEmbedder.readProjectWithDependencies() method
[ http://jira.codehaus.org/browse/MNG-1106?page=all ] Kenney Westerhof updated MNG-1106: -- Fix Version/s: (was: 2.0.5) 2.0.6 Stdout in MavenEmbedder.readProjectWithDependencies() method Key: MNG-1106 URL: http://jira.codehaus.org/browse/MNG-1106 Project: Maven 2 Issue Type: Bug Components: Embedding Affects Versions: 2.0 Reporter: Eugene Kuleshov Fix For: 2.0.6 MavenEmbedder.readProjectWithDependencies() method is is dumping the following to stdout. [WARNING] Unable to get resource from repository snapshots (http://snapshots.maven.codehaus.org/maven2) This is happening when ArtifactResolutionException is thrown: org.apache.maven.artifact.resolver.ArtifactResolutionException: Unable to download the artifact from any repository org.apache.maven:maven-artifact-manager:2.0-beta-4-SNAPSHOT:jar from the specified remote repositories: snapshots (http://snapshots.maven.codehaus.org/maven2), central (http://repo1.maven.org/maven2) Path to dependency: 1) org.apache.maven:maven-plugin-tools-java:jar:2.0-beta-4-SNAPSHOT 2) org.apache.maven:maven-plugin-tools-api:jar:2.0-beta-4-SNAPSHOT 3) org.apache.maven:maven-project:jar:2.0-beta-4-SNAPSHOT 4) org.apache.maven:maven-artifact-manager:jar:2.0-beta-4-SNAPSHOT -- 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] Updated: (MNG-2038) A mini guide covering the interplay between SCM and maven releases
[ http://jira.codehaus.org/browse/MNG-2038?page=all ] Kenney Westerhof updated MNG-2038: -- Fix Version/s: (was: 2.0.5) 2.0.6 A mini guide covering the interplay between SCM and maven releases -- Key: MNG-2038 URL: http://jira.codehaus.org/browse/MNG-2038 Project: Maven 2 Issue Type: Improvement Components: Documentation: Guides Reporter: Julian Wood Priority: Minor Fix For: 2.0.6 Attachments: project_process.apt Emmanuel Venisse asked if I would contribute this document, so here it is. It is a step by step guide which covers releasing a project using maven, but also demonstrates some best practices when it comes to making branches, tags, and of course versions, all while touching on how maven makes these practices so much less of a headache. -- 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] Updated: (MNG-2153) Updated resource bundles for pl and en locales
[ http://jira.codehaus.org/browse/MNG-2153?page=all ] Kenney Westerhof updated MNG-2153: -- Fix Version/s: (was: 2.0.5) 2.0.6 Updated resource bundles for pl and en locales -- Key: MNG-2153 URL: http://jira.codehaus.org/browse/MNG-2153 Project: Maven 2 Issue Type: Improvement Reporter: Jacek Laskowski Fix For: 2.0.6 Attachments: messages.patch Attached you can find updated resource bundles for pl and en locales that belong to components/maven-core module. -- 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] Updated: (MNG-2164) Generated plugin documentation lists wrong data type
[ http://jira.codehaus.org/browse/MNG-2164?page=all ] Kenney Westerhof updated MNG-2164: -- Fix Version/s: (was: 2.0.5) 2.0.6 Generated plugin documentation lists wrong data type Key: MNG-2164 URL: http://jira.codehaus.org/browse/MNG-2164 Project: Maven 2 Issue Type: Bug Components: Plugin Creation Tools Affects Versions: 2.0.2 Reporter: Mike Perham Fix For: 2.0.6 Attachments: MPLUGIN-12-maven-plugin-tools-java.patch The PMD Report has a String[] rulesets parameter. The generated documentation says that rulesets is of type String. -- 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] Updated: (MNG-1945) project.getBuild().setSourceDirectory() should modify the compile source roots automatically
[ http://jira.codehaus.org/browse/MNG-1945?page=all ]
Kenney Westerhof updated MNG-1945:
--
Fix Version/s: (was: 2.0.5)
2.0.6
project.getBuild().setSourceDirectory() should modify the compile source
roots automatically
Key: MNG-1945
URL: http://jira.codehaus.org/browse/MNG-1945
Project: Maven 2
Issue Type: Improvement
Affects Versions: 2.0.1
Reporter: Vincent Massol
Fix For: 2.0.6
Here's the code that I have in the clover plugin right now:
private void redirectSourceDirectories()
{
String oldSourceDirectory =
this.project.getBuild().getSourceDirectory();
this.project.getBuild().setSourceDirectory(
this.cloverOutputSourceDirectory );
// Maven2 limitation: changing the source directory doesn't change
the compile source roots
Iterator sourceRoots =
this.project.getCompileSourceRoots().iterator();
for (int i = 0; sourceRoots.hasNext(); i++)
{
String sourceRoot = (String)
this.project.getCompileSourceRoots().get( i );
if (sourceRoot.equals(oldSourceDirectory))
{
this.project.getCompileSourceRoots().remove( i );
// Note: Ideally we should add the new compile source root at
the same place as the
// one we're removing but there's no API for this...
this.project.addCompileSourceRoot(
this.project.getBuild().getSourceDirectory() );
}
}
}
I believe this could be put in Maven core.
--
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] Updated: (MNG-2143) Proposition of documentation
[ http://jira.codehaus.org/browse/MNG-2143?page=all ] Kenney Westerhof updated MNG-2143: -- Fix Version/s: (was: 2.0.5) 2.0.6 Proposition of documentation Key: MNG-2143 URL: http://jira.codehaus.org/browse/MNG-2143 Project: Maven 2 Issue Type: Improvement Components: Documentation: General Reporter: Raphaël Piéroni Fix For: 2.0.6 Attachments: AdvancedDocumentation.apt, Categories.txt, MainPage.apt Here attached are 2 apt file that describe a first attempt to refactor the maven documentation site. -- 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] Updated: (MNG-2306) mojo javadoc annotations support for IntelliJ Idea
[ http://jira.codehaus.org/browse/MNG-2306?page=all ] Kenney Westerhof updated MNG-2306: -- Fix Version/s: (was: 2.0.5) 2.0.6 mojo javadoc annotations support for IntelliJ Idea -- Key: MNG-2306 URL: http://jira.codehaus.org/browse/MNG-2306 Project: Maven 2 Issue Type: Improvement Components: Sites Reporting Reporter: Roald Bankras Fix For: 2.0.6 Attachments: MNG-2306.txt I've created Live templates config file for the mojo javadoc annotations. This file can be made available through the maven site (i.e. on the mojo-api-specification 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
[jira] Updated: (MNG-2318) When a project has modules and its parent is not preinstalled the build fails
[ http://jira.codehaus.org/browse/MNG-2318?page=all ] Kenney Westerhof updated MNG-2318: -- Fix Version/s: (was: 2.0.5) 2.0.6 When a project has modules and its parent is not preinstalled the build fails - Key: MNG-2318 URL: http://jira.codehaus.org/browse/MNG-2318 Project: Maven 2 Issue Type: Bug Components: Inheritence and Interpolation Affects Versions: 2.0.4 Reporter: Carlos Sanchez Fix For: 2.0.6 . |-- A | `-- pom.xml (A) |-- C | `-- pom.xml (C) - module of B `-- pom.xml (B) C parent is B and B parent is A, trying to build B it fails -- 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] Updated: (MNG-1452) best practices: deployment of aggregate JARs produced by the assembly plug-in
[ http://jira.codehaus.org/browse/MNG-1452?page=all ] Kenney Westerhof updated MNG-1452: -- Fix Version/s: (was: 2.0.5) 2.0.6 best practices: deployment of aggregate JARs produced by the assembly plug-in - Key: MNG-1452 URL: http://jira.codehaus.org/browse/MNG-1452 Project: Maven 2 Issue Type: Task Components: Design, Patterns Best Practices Reporter: Jason van Zyl Priority: Trivial Fix For: 2.0.6 We need a way to deploy aggregate JARs produced by the assembly plug-in. Some things to consider: 1) A new POM will need to be created to reflect the contents of the aggregate JAR 2) Do we want a standard name or classifier for these aggregate JARs, one standard name might not be enough as different assemblies for the same project might contain slightly different things. 3) Do we want assemblies like this to be in their own builds? Right now the J2EE JAR in the Geronimo build is like this whereas the assembly for the embedder is part of the embedder build. Would separating the build make it easier to deploy? Maybe. -- 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] Updated: (MNG-2413) maven version insistence based on wrong variable
[ http://jira.codehaus.org/browse/MNG-2413?page=all ] Kenney Westerhof updated MNG-2413: -- Fix Version/s: (was: 2.0.5) 2.0.6 maven version insistence based on wrong variable Key: MNG-2413 URL: http://jira.codehaus.org/browse/MNG-2413 Project: Maven 2 Issue Type: Bug Components: Bootstrap Build Affects Versions: 2.0.4 Environment: OS : ubuntu dapper java vm : SableVM 1.11.3 Reporter: j Fix For: 2.0.6 MavenCli does if (System.getProperty(java.class.version, 44.0).compareTo(48.0) 0) //then echo sorry we need version 1.4 however java.class.version is the binary packaging format for the classes, not the supported API. java.version is the supported api, for which sable returns 1.4.2. So the process aborts out, wanting the 1.4 API, when it has 1.4 API (sable has 46.0 instead of 48.0 as the class packaging format used) -- 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] Updated: (MNG-1371) How to deal with encoding and documentation
[ http://jira.codehaus.org/browse/MNG-1371?page=all ] Kenney Westerhof updated MNG-1371: -- Fix Version/s: (was: 2.0.5) 2.0.6 How to deal with encoding and documentation --- Key: MNG-1371 URL: http://jira.codehaus.org/browse/MNG-1371 Project: Maven 2 Issue Type: Task Components: Documentation: Guides Reporter: Jason van Zyl Fix For: 2.0.6 Show how people can use different encodings with APT. This can probably be added to the guide-site.apt. -- 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] Updated: (MNG-1121) document standard location for plugin configuration files
[ http://jira.codehaus.org/browse/MNG-1121?page=all ] Kenney Westerhof updated MNG-1121: -- Fix Version/s: (was: 2.0.5) 2.0.6 document standard location for plugin configuration files - Key: MNG-1121 URL: http://jira.codehaus.org/browse/MNG-1121 Project: Maven 2 Issue Type: Task Components: Documentation: General Reporter: Brett Porter Fix For: 2.0.6 discussion: http://mail-archives.apache.org/mod_mbox/maven-users/200505.mbox/[EMAIL PROTECTED] things like checkstyle configuration files. also see Vincent's recent discussion: http://mail-archives.apache.org/mod_mbox/maven-dev/200510.mbox/[EMAIL PROTECTED] -- 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] Updated: (MNG-2209) Calculation of module URLs does not match deployment
[ http://jira.codehaus.org/browse/MNG-2209?page=all ] Kenney Westerhof updated MNG-2209: -- Fix Version/s: (was: 2.0.5) 2.0.6 Calculation of module URLs does not match deployment Key: MNG-2209 URL: http://jira.codehaus.org/browse/MNG-2209 Project: Maven 2 Issue Type: Bug Affects Versions: 2.0.4 Environment: Site plugin built from SVN revision 391930 Reporter: Bob Allison Priority: Blocker Fix For: 2.0.6 Attachments: sitetest.tar In a project where the parent project is a peer directory with its children (e.g., top/parent/pom.xml, top/child/pom.xml, ...) the site is deployed correctly (site/parent, site/parent/child, ...) but the links in the left menu are not generated correctly (site/parent, site/child, ...) Attached tar file contains three projects: parent, child1, and child2. Unpack these into a directory, change to the parent directory, and do a mvn site. The generated links for the first child project is http://child1/index.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
[jira] Updated: (MNG-1524) artifact:dependencies related error: No files specified for filelist
[ http://jira.codehaus.org/browse/MNG-1524?page=all ] Kenney Westerhof updated MNG-1524: -- Fix Version/s: (was: 2.0.5) 2.0.6 artifact:dependencies related error: No files specified for filelist Key: MNG-1524 URL: http://jira.codehaus.org/browse/MNG-1524 Project: Maven 2 Issue Type: Bug Components: Ant tasks Affects Versions: 2.0 Reporter: Chad Berghorst Fix For: 2.0.6 -- 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] Updated: (MNG-1120) don't require modelVersion / if there is a valid schema element
[ http://jira.codehaus.org/browse/MNG-1120?page=all ] Kenney Westerhof updated MNG-1120: -- Fix Version/s: (was: 2.0.5) 2.0.6 don't require modelVersion / if there is a valid schema element - Key: MNG-1120 URL: http://jira.codehaus.org/browse/MNG-1120 Project: Maven 2 Issue Type: Bug Reporter: Brett Porter Priority: Minor Fix For: 2.0.6 -- 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] Updated: (MNG-1370) Guide to attached artifacts
[ http://jira.codehaus.org/browse/MNG-1370?page=all ] Kenney Westerhof updated MNG-1370: -- Fix Version/s: (was: 2.0.5) 2.0.6 Guide to attached artifacts --- Key: MNG-1370 URL: http://jira.codehaus.org/browse/MNG-1370 Project: Maven 2 Issue Type: Task Components: Documentation: Guides Reporter: Jason van Zyl Fix For: 2.0.6 Show how to use attached artifacts like source bundles and javadocs, and the use the ejb plugin which creates the ejb-client attached artiact. -- 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] Updated: (MNG-1637) Maven bootstrap requires old libraries, like 2.0-beta-3
[ http://jira.codehaus.org/browse/MNG-1637?page=all ] Kenney Westerhof updated MNG-1637: -- Fix Version/s: (was: 2.0.5) 2.0.6 Maven bootstrap requires old libraries, like 2.0-beta-3 --- Key: MNG-1637 URL: http://jira.codehaus.org/browse/MNG-1637 Project: Maven 2 Issue Type: Bug Components: Bootstrap Build Reporter: Brett Porter Fix For: 2.0.6 haven't checked where these are pulled from - could be plugins, or a dependency. Need to hunt them down and update them, and should problbay filter them out in the bootstrap. For any library built via the bootstrap, only the newest version should be used. -- 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] Updated: (MNG-1425) best practices: the location of configuration files vs resources
[ http://jira.codehaus.org/browse/MNG-1425?page=all ] Kenney Westerhof updated MNG-1425: -- Fix Version/s: (was: 2.0.5) 2.0.6 best practices: the location of configuration files vs resources Key: MNG-1425 URL: http://jira.codehaus.org/browse/MNG-1425 Project: Maven 2 Issue Type: Task Components: Design, Patterns Best Practices Reporter: Jason van Zyl Priority: Trivial Fix For: 2.0.6 This may collapse into one of the other best practices issues, but this will hold the thought for now. Vincent maybe you can link in some thoughts from the mailing list? -- 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] Updated: (MNG-1922) Rename maven-it-plugin plugin as its name implies it is for performing integration tests in general
[ http://jira.codehaus.org/browse/MNG-1922?page=all ] Kenney Westerhof updated MNG-1922: -- Fix Version/s: (was: 2.0.5) 2.0.6 Rename maven-it-plugin plugin as its name implies it is for performing integration tests in general --- Key: MNG-1922 URL: http://jira.codehaus.org/browse/MNG-1922 Project: Maven 2 Issue Type: Task Components: integration tests Affects Versions: 2.0.1 Reporter: Vincent Massol Fix For: 2.0.6 The it plugin is really meant to perform functional tests of plugins and as such should be renamed. Ideas: * maven-plugin-it-plugin * maven-test-plugin-plugin *Another idea is to include its feature in the plugin plugin under a plugin:test mojo.* -- 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] Updated: (MNG-2007) Exported POM still has dependency version ranges
[ http://jira.codehaus.org/browse/MNG-2007?page=all ] Kenney Westerhof updated MNG-2007: -- Fix Version/s: (was: 2.0.5) 2.0.6 Exported POM still has dependency version ranges Key: MNG-2007 URL: http://jira.codehaus.org/browse/MNG-2007 Project: Maven 2 Issue Type: Bug Components: maven-archiver Affects Versions: 2.0.2 Reporter: Matthew Beermann Fix For: 2.0.6 If you have a version range for one of your dependencies, then the exported POM (the one that's placed in the repository and in the jar itself) will still have a range there. This seems at odds with (one) point of exporting a POM, which is to have all the information you need to reconstruct the state of a build at a particular moment in time. Without knowing which version number was chosen, you can't be sure you're reconstructing the same build later. It also seems to be at odds with the behavior elsewhere in this exported artifact: the plugins section shows the actual version number used, and active profiles are quietly merged into the main POM. -- 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] Updated: (MNG-2089) APT AspectJ plugins
[ http://jira.codehaus.org/browse/MNG-2089?page=all ] Kenney Westerhof updated MNG-2089: -- Fix Version/s: (was: 2.0.5) 2.0.6 APT AspectJ plugins - Key: MNG-2089 URL: http://jira.codehaus.org/browse/MNG-2089 Project: Maven 2 Issue Type: Wish Components: Sandbox Affects Versions: 2.0.3 Reporter: Juraj Burian Priority: Minor Fix For: 2.0.6 Attachments: APTexamplePrj.zip, plugins.zip We have prototypes of AspectJ APT plugins ready. Can you put it into the Sanbox? Thanx. best regards J.Burian -- 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] Updated: (MNG-1304) Create a standard versioning document
[ http://jira.codehaus.org/browse/MNG-1304?page=all ] Kenney Westerhof updated MNG-1304: -- Fix Version/s: (was: 2.0.5) 2.0.6 Create a standard versioning document - Key: MNG-1304 URL: http://jira.codehaus.org/browse/MNG-1304 Project: Maven 2 Issue Type: Improvement Components: Documentation: General Reporter: Jason van Zyl Fix For: 2.0.6 We need to document how SNAPSHOTs work and how we move from one version to another. There are the starts of decent documents in the xstream project and the commons project at Apache. -- 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] Updated: (MNG-66) Create a matrix of possible exceptional conditions
[ http://jira.codehaus.org/browse/MNG-66?page=all ] Kenney Westerhof updated MNG-66: Fix Version/s: (was: 2.0.5) 2.0.6 Create a matrix of possible exceptional conditions -- Key: MNG-66 URL: http://jira.codehaus.org/browse/MNG-66 Project: Maven 2 Issue Type: Task Components: Documentation: General Reporter: Jason van Zyl Priority: Minor Fix For: 2.0.6 We need a little matrix of possible exception conditions, what causes them, what resources we can point users to for help, and how we can format the exception message as to make the most sense to users. -- 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] Updated: (MNG-1817) Debug System.out statement snuck through
[ http://jira.codehaus.org/browse/MNG-1817?page=all ] Kenney Westerhof updated MNG-1817: -- Fix Version/s: (was: 2.0.5) 2.0.6 Debug System.out statement snuck through Key: MNG-1817 URL: http://jira.codehaus.org/browse/MNG-1817 Project: Maven 2 Issue Type: Bug Components: Ant tasks Affects Versions: 2.0.1 Reporter: Eric Andresen Priority: Trivial Fix For: 2.0.6 In the maven-artifact-ant tasks, a debug statement snuck through to the final release: Repository.getId() == central This happens in the artifact:dependencies task. -- 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] Updated: (MNG-2026) Document how parent-child POM relationships, modules/, and parentrelativePath/ works
[ http://jira.codehaus.org/browse/MNG-2026?page=all ] Kenney Westerhof updated MNG-2026: -- Fix Version/s: (was: 2.0.5) 2.0.6 Document how parent-child POM relationships, modules/, and parentrelativePath/ works -- Key: MNG-2026 URL: http://jira.codehaus.org/browse/MNG-2026 Project: Maven 2 Issue Type: Task Components: Documentation: General Reporter: John Casey Fix For: 2.0.6 Create a document that will describe how POMs can be related to one another in a multimodule build. Specifically, document: * The parent-child relationship - how is this manifest in the POMs * How does the modules/ section work * How does the relativePath/ element of the parent/ section work...and what is required in the parent/ section? * How to install ONLY the parent POM for a multimodule setup (mvn -N pom.xml at the top level) * How to build an entire multimodule setup from one command (tie all of this together into a working example) Related to this, but in another document, should be a list of things that are inherited (could be a link to somewhere else, if this documentation exists in other places). Also, the algorithm used to merge inherited and local POM sections should be in this other document. -- 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] Updated: (MNG-2385) incorporate plugin configuration conventions into the standard directory layout
[ http://jira.codehaus.org/browse/MNG-2385?page=all ] Kenney Westerhof updated MNG-2385: -- Fix Version/s: (was: 2.0.5) 2.0.6 incorporate plugin configuration conventions into the standard directory layout --- Key: MNG-2385 URL: http://jira.codehaus.org/browse/MNG-2385 Project: Maven 2 Issue Type: Task Components: Documentation: General Reporter: Brett Porter Fix For: 2.0.6 see: http://mail-archives.apache.org/mod_mbox/maven-users/200601.mbox/[EMAIL PROTECTED] we need a standard way to locate config for modello, checkstyle, etc. we may also want to later adopt this as a way of setting a convenient default for location some configuration. Note also that this may involved being able to turn such configuration into an artifact (perhaps a group of them) so that it can be used from multiple projects without having to cutpaste -- 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] Updated: (MNG-1560) Guide to accessing repository with https client authentication
[ http://jira.codehaus.org/browse/MNG-1560?page=all ] Kenney Westerhof updated MNG-1560: -- Fix Version/s: (was: 2.0.5) 2.0.6 Guide to accessing repository with https client authentication -- Key: MNG-1560 URL: http://jira.codehaus.org/browse/MNG-1560 Project: Maven 2 Issue Type: Improvement Components: Documentation: Guides Affects Versions: 2.0 Reporter: Arnaud Bailly Priority: Minor Fix For: 2.0.6 Attachments: guide-repository-ssl.apt, guide-repository-ssl.apt, MavenRepoSSLAccess.apt The attachment describes a way (in APT format) to use a remote repository through HTTPS with client-side certificate authentication. This may be useful in corporate or private development settings. -- 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] Updated: (MNG-1546) no way to retrieve/change plugin configuration in the POM or globally
[ http://jira.codehaus.org/browse/MNG-1546?page=all ] Kenney Westerhof updated MNG-1546: -- Fix Version/s: (was: 2.0.5) 2.0.6 no way to retrieve/change plugin configuration in the POM or globally - Key: MNG-1546 URL: http://jira.codehaus.org/browse/MNG-1546 Project: Maven 2 Issue Type: Bug Components: Embedding Affects Versions: 2.0 Reporter: Milos Kleint Assigned To: Jason van Zyl Fix For: 2.0.6 there is not way to figure the configuration of a given plugin in the pom. usecase: have the surefire plugin with test includes/excludes. in the UI mark the included/excluded. allow changing these settings.. another usecase: figure if a plugin is added to the pom that generates some sources.. another usecase: dynamically allow to run a single test from the IDE, requires me to manipulate the surefire's includes/excluse or test pattern property.. -- 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] Updated: (MNG-2411) Mistake in guide-building-m2.html
[ http://jira.codehaus.org/browse/MNG-2411?page=all ] Kenney Westerhof updated MNG-2411: -- Fix Version/s: (was: 2.0.5) 2.0.6 Mistake in guide-building-m2.html - Key: MNG-2411 URL: http://jira.codehaus.org/browse/MNG-2411 Project: Maven 2 Issue Type: Task Components: Documentation: Guides Affects Versions: 2.0.4 Environment: - Reporter: Martin Zeltner Fix For: 2.0.6 Hi, I think on page http://maven.apache.org/guides/development/guide-building-m2.html in chapter Building Maven with Maven installed there should be written cd maven-cli and not cd maven-core. Cheers, Martin -- 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] Updated: (MNG-1678) missing element does not trigger any warning
[ http://jira.codehaus.org/browse/MNG-1678?page=all ] Kenney Westerhof updated MNG-1678: -- Fix Version/s: (was: 2.0.5) 2.0.6 missing element does not trigger any warning Key: MNG-1678 URL: http://jira.codehaus.org/browse/MNG-1678 Project: Maven 2 Issue Type: Improvement Affects Versions: 2.0, 2.0.4 Reporter: Jorg Heymans Assigned To: Maria Odea Ching Fix For: 2.0.6 Original Estimate: 12 hours Remaining Estimate: 12 hours spot the subtle error in below pom : ?xml version=1.0 encoding=UTF-8? project modelVersion4.0.0/modelVersion groupIdorg.my.project/groupId artifactIdmyProject/artifactId version0.1/version nameThe Project/name packagingjar/packaging repositories repository idapache-maven2-snapshot/id nameApache Maven2 Snapshot Repository/name urlhttp://cvs.apache.org/maven-snapshot-repository/url /repository /repositories dependencies groupIdorg.apache.cocoon/groupId artifactIdcocoon-core/artifactId version2.2.0-SNAPSHOT/version /dependencies /project The dependency element is missing inside dependencies. Maven did not give any warning or error though. Note that in my actual project, the dependency was not needed for compilation -- 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] Updated: (MNG-1118) mavenEmbedder.readProjectWithDependencies improvements
[ http://jira.codehaus.org/browse/MNG-1118?page=all ] Kenney Westerhof updated MNG-1118: -- Fix Version/s: (was: 2.0.5) 2.0.6 mavenEmbedder.readProjectWithDependencies improvements -- Key: MNG-1118 URL: http://jira.codehaus.org/browse/MNG-1118 Project: Maven 2 Issue Type: Improvement Components: POM, Embedding Reporter: Eugene Kuleshov Assigned To: Jason van Zyl Fix For: 2.0.6 Currently mavenEmbedder.readProjectWithDependencies return instance of MavenProject. So, collection of artifacts in this instance (including transient dependencies) does not have information where those artifacts had been declared. It would be useful for an IDE to be able to get this information somehow (e.g. getArtifactMap(), which could return map of artifacts to list of pom files). -- 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] Updated: (MNG-1593) Typo in settings doc
[ http://jira.codehaus.org/browse/MNG-1593?page=all ] Kenney Westerhof updated MNG-1593: -- Fix Version/s: (was: 2.0.5) 2.0.6 Typo in settings doc Key: MNG-1593 URL: http://jira.codehaus.org/browse/MNG-1593 Project: Maven 2 Issue Type: Bug Components: Documentation: General Affects Versions: 2.0 Reporter: Carlos Sanchez Assigned To: Maria Odea Ching Priority: Minor Fix For: 2.0.6 http://maven.apache.org/maven-settings/settings.html under repository and pluginRepository release should be releases snapshot should be snapshots -- 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] Updated: (MNG-1140) document how other common directory layouts could be used within/migrated to m2
[ http://jira.codehaus.org/browse/MNG-1140?page=all ] Kenney Westerhof updated MNG-1140: -- Fix Version/s: (was: 2.0.5) 2.0.6 document how other common directory layouts could be used within/migrated to m2 --- Key: MNG-1140 URL: http://jira.codehaus.org/browse/MNG-1140 Project: Maven 2 Issue Type: Task Components: Documentation: General Reporter: Brett Porter Priority: Minor Fix For: 2.0.6 -- 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] Updated: (MNG-1497) remove old html files from the site
[ http://jira.codehaus.org/browse/MNG-1497?page=all ] Kenney Westerhof updated MNG-1497: -- Fix Version/s: (was: 2.0.5) 2.0.6 remove old html files from the site --- Key: MNG-1497 URL: http://jira.codehaus.org/browse/MNG-1497 Project: Maven 2 Issue Type: Improvement Reporter: Alex Wood Priority: Minor Fix For: 2.0.6 The Maven Directory Layout page (http://maven.apache.org/reference/dirlayout.html) notes for the src directory that The code may be placed into separate source code directories by language, as in src/java/ and src/php/ for source code in the Java and PHP languages respectively. The separation into directories according to function (src/share, src/core, src/web) is currently not supported by Maven. It is highly recommended that sub-directories be used under src/. The Maven Conventions Page (http://maven.apache.org/reference/conventions.html) advises that projects should follow another directory structure: src/main/$LANGUAGE, src/test/$LANGUAGE, src/site/xdocs, etc. To me this seems to contradict the statement that Maven doesn't support separation into directories according to function. The examples given of structures to avoid (src/core and src/web) match closely to what's encouraged elsewhere (src/main and src/site). The directory layout page is marked as being for v1.0.2, but the conventions page is not marked with a version. If the conventions are different for different versions, clearer labeling is needed. If the conventions are constant across versions, then the documentation should be changed so that it is not contradicting itself. -- 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] Updated: (MNG-2048) Quote args in mvn script
[ http://jira.codehaus.org/browse/MNG-2048?page=all ]
Kenney Westerhof updated MNG-2048:
--
Fix Version/s: (was: 2.0.5)
2.0.6
Quote args in mvn script
Key: MNG-2048
URL: http://jira.codehaus.org/browse/MNG-2048
Project: Maven 2
Issue Type: Bug
Components: Command Line
Affects Versions: 2.0.2
Environment: Windows XP
Cygwin
Reporter: Dale Wyttenbach
Priority: Minor
Fix For: 2.0.6
The mvn script as distributed does not handle quoted args such as:
m2 -Dgreeting=huh bah hello:sayhi
You get the error:
Invalid task 'bah': you must specify a valid lifecycle phase, or a goal in
the format plugin:goal or pluginGroupId:pluginArtifactId:pluginVersion:goal
Here is a fix for the mvn script:
*** mvn 2006/02/07 15:58:33 1.1
--- mvn 2006/02/07 15:58:38
***
*** 134,138
-classpath ${M2_HOME}/core/boot/classworlds-*.jar \
-Dclassworlds.conf=${M2_HOME}/bin/m2.conf \
-Dmaven.home=${M2_HOME} \
! ${CLASSWORLDS_LAUNCHER} $@
--- 134,138
-classpath ${M2_HOME}/core/boot/classworlds-*.jar \
-Dclassworlds.conf=${M2_HOME}/bin/m2.conf \
-Dmaven.home=${M2_HOME} \
! ${CLASSWORLDS_LAUNCHER} $@
--
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] Updated: (MNG-2107) Only warn once about invalid poms
[ http://jira.codehaus.org/browse/MNG-2107?page=all ] Kenney Westerhof updated MNG-2107: -- Fix Version/s: (was: 2.0.5) 2.0.6 Only warn once about invalid poms - Key: MNG-2107 URL: http://jira.codehaus.org/browse/MNG-2107 Project: Maven 2 Issue Type: Improvement Components: Artifacts and Repositories Affects Versions: 2.0.3, 2.0.2 Reporter: Dan Diephouse Fix For: 2.0.6 Tested this on 2.0.2 and on the 2.0.3 RC. I get warned many many times about bad poms, it would be great if this only happened once: [INFO] [INFO] Building XFire JAX-WS Support [INFO]task-segment: [install] [INFO] [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [WARNING] POM for 'stax:stax:pom:1.1.2-dev:test' is invalid. It will be ignored for artifact resolution. Reason: Not a v 4.0.0 POM. [WARNING] POM for 'jaxen:jaxen:pom:1.1-beta-8:compile' is invalid. It will be ignored for artifact resolution. Reason: N ot a v4.0.0 POM. [WARNING] POM for 'jdom:jdom:pom:1.0:compile' is invalid. It will be ignored for artifact resolution. Reason: Parse erro r reading POM. Reason: comment started on line 32 and column 9 was not closed (position: END_TAG seen .../dependencies \n/project... @40:11) caused by: java.io.EOFException: no more data available - expected end tags /dependencies/pro ject to close start tag dependencies from line 6 and start tag project from line 1, parser stopped on END_TAG seen .../dependencies\n/project... @40:11 [WARNING] POM for 'xfire:xfire-jsr181-api:pom:1.0-M1:compile' is invalid. It will be ignored for artifact resolution. Re ason: Not a v4.0.0 POM. [WARNING] POM for 'jaxen:jaxen:pom:1.1-beta-8:compile' is invalid. It will be ignored for artifact resolution. Reason: N ot a v4.0.0 POM. [WARNING] POM for 'jdom:jdom:pom:1.0:compile' is invalid. It will be ignored for artifact resolution. Reason: Parse erro r reading POM. Reason: comment started on line 32 and column 9 was not closed (position: END_TAG seen .../dependencies \n/project... @40:11) caused by: java.io.EOFException: no more data available - expected end tags /dependencies/pro ject to close start tag dependencies from line 6 and start tag project from line 1, parser stopped on END_TAG seen .../dependencies\n/project... @40:11 Downloading: https://maven-repository.dev.java.net/nonav/repository/xfire/poms/sun-saaj-impl-2.0-ea3.pom [WARNING] Unable to get resource from repository java.net (https://maven-repository.dev.java.net/nonav/repository) Downloading: http://dist.codehaus.org//xfire/poms/sun-saaj-impl-2.0-ea3.pom [WARNING] Unable to get resource from repository codehaus (http://dist.codehaus.org/) Downloading: http://cvs.apache.org/maven-snapshot-repository//xfire/poms/sun-saaj-impl-2.0-ea3.pom [WARNING] Unable to get resource from repository apache-snapshots (http://cvs.apache.org/maven-snapshot-repository/) Downloading: http://test.maven.codehaus.org/maven2//xfire/sun-saaj-impl/2.0-ea3/sun-saaj-impl-2.0-ea3.pom [WARNING] Unable to get resource from repository central (http://repo1.maven.org/maven2) Downloading: https://maven-repository.dev.java.net/nonav/repository/xfire/poms/sun-saaj-api-2.0-ea3.pom [WARNING] Unable to get resource from repository java.net (https://maven-repository.dev.java.net/nonav/repository) Downloading: http://dist.codehaus.org//xfire/poms/sun-saaj-api-2.0-ea3.pom [WARNING] Unable to get resource from repository codehaus (http://dist.codehaus.org/) Downloading: http://cvs.apache.org/maven-snapshot-repository//xfire/poms/sun-saaj-api-2.0-ea3.pom [WARNING] Unable to get resource from repository apache-snapshots (http://cvs.apache.org/maven-snapshot-repository/) Downloading: http://test.maven.codehaus.org/maven2//xfire/sun-saaj-api/2.0-ea3/sun-saaj-api-2.0-ea3.pom [WARNING] Unable to get resource from repository central (http://repo1.maven.org/maven2) Downloading: https://maven-repository.dev.java.net/nonav/repository/xfire/poms/sun-jaxws-api-2.0-ea3.pom [WARNING] Unable to get resource from repository java.net (https://maven-repository.dev.java.net/nonav/repository) Downloading: http://dist.codehaus.org//xfire/poms/sun-jaxws-api-2.0-ea3.pom [WARNING] Unable to get resource from repository codehaus (http://dist.codehaus.org/) Downloading: http://cvs.apache.org/maven-snapshot-repository//xfire/poms/sun-jaxws-api-2.0-ea3.pom [WARNING] Unable to get resource from repository apache-snapshots (http://cvs.apache.org/maven-snapshot-repository/) Downloading:
[jira] Updated: (MNG-2247) Release-Dates of maven releases not documented on website?
[ http://jira.codehaus.org/browse/MNG-2247?page=all ] Kenney Westerhof updated MNG-2247: -- Fix Version/s: (was: 2.0.5) 2.0.6 Release-Dates of maven releases not documented on website? -- Key: MNG-2247 URL: http://jira.codehaus.org/browse/MNG-2247 Project: Maven 2 Issue Type: Bug Components: Documentation: General Affects Versions: 2.0.4 Environment: firefox Reporter: Oliver Nölle Assigned To: Alex Mayorga Adame Priority: Minor Fix For: 2.0.6 Scanning projects on the web I often want to know how active these projects are by checking the dates of the last release(s). After browsing for half an hour on the maven website (http://maven.apache.org/) I give up to find the dates of the last releases... = Please add them somewhere in a prominent place (in many open source projects there is something like a news section with release dates or in sourceforge you find the release dates looking into the files section) (In case the information is there, please check whether it's me who was too stupid to find it or whether it's really hidden...) Same thing applies for http://m2eclipse.codehaus.org/: I find 5 versions, but no date information... = I guess you might want to forward this bug to the maven plugin generating the website? -- 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] Updated: (MNG-1709) Project source path not generated correctly
[ http://jira.codehaus.org/browse/MNG-1709?page=all ] Kenney Westerhof updated MNG-1709: -- Fix Version/s: (was: 2.0.5) 2.0.6 Project source path not generated correctly --- Key: MNG-1709 URL: http://jira.codehaus.org/browse/MNG-1709 Project: Maven 2 Issue Type: Bug Components: Inheritence and Interpolation Reporter: Mike Perham Fix For: 2.0.6 Maven's project reports require the source directories to reflect the artifactId of the related POM. We do not currently use that format and find that the source repository path, for instance, is not generated correctly in our case. I don't know if it is possible to support our source layout: wsf/ pom.xml support/ pom.xml (artifactId = wsf-support) common/ pom.xml (artifactId = wsf-common-support) We do this so that our directory structure is not redundant, as the maven structure is now: maven-scm/ maven-scm-providers/ maven-scm-provider-perforce/ Is there any way to support this type of layout? I would like to specify the top-level repository location and have maven figure out the correct structure to tack on to the end of the URL. The generated repository URL is: http://server/wsf/wsf-support/wsf-common-support when it should be: http://server/wsf/support/common If you are not going to support this alternative multi-module layout, could you document the existing naming standards required when doing this type of inheritance? The current documentation [http://maven.apache.org/guides/mini/guide-multi-module.html] is somewhat lacking. :-) -- 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
