[jira] (MRELEASE-674) release plugin converts explicit version to snapshot
[ https://jira.codehaus.org/browse/MRELEASE-674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=298493#comment-298493 ] Jim McCaskey commented on MRELEASE-674: --- I've noticed the release plugin has been released a few times with out this even though a patch is available. I was curious if there was any reason why. release plugin converts explicit version to snapshot - Key: MRELEASE-674 URL: https://jira.codehaus.org/browse/MRELEASE-674 Project: Maven 2.x Release Plugin Issue Type: Bug Components: update-versions Affects Versions: 2.1 Environment: Apache Maven 3.0.2 (r1056850; 2011-01-09 01:58:10+0100) Java version: 1.6.0_23, vendor: Sun Microsystems Inc. Java home: i:\tools\jdk\1.6.0_23\jre Default locale: de_DE, platform encoding: Cp1252 OS name: windows xp, version: 5.1, arch: x86, family: windows Reporter: Bernd Mau Attachments: MapVersionPhase.patch I would like to use release:update-versions to explicitly update the versions of my multiproject. Unfortunetly the release plugin converts the given developmentVersion to a SNAPSHOT version. It happens in MapVersionPhase.getNextVersion(). I would expect the plugin to leave the given developmentVersion property as it is, because the prompt version will not be converted. Here is my command line: mvn release:update-versions -DautoVersionSubmodules=true -DdevelopmentVersion=2.0.1 -DpushChanges=false I made a patch and attached it to the issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MSITE-621) empty outputDirectory causes mvn clean to delete whole tree
empty outputDirectory causes mvn clean to delete whole tree
---
Key: MSITE-621
URL: https://jira.codehaus.org/browse/MSITE-621
Project: Maven 2.x and 3.x Site Plugin
Issue Type: Bug
Components: documentation
Affects Versions: 3.0
Environment: Apache Maven 3.0.3 (r1075438; 2011-02-28 11:31:09-0600)
Maven home: D:\maven\apache-maven-3.0.3\bin\..
Java version: 1.6.0_24, vendor: Sun Microsystems Inc.
Java home: D:\j2sdk1.6.0_24\jre
Default locale: en_US, platform encoding: Cp1252
OS name: windows 7, version: 6.1, arch: x86, family: windows
Reporter: Jim McCaskey
On this page:
http://maven.apache.org/plugins/maven-site-plugin/maven-3.html#Old_configuration_Maven_2__3
There is this little code snippet:
{code}
reporting
excludeDefaultstrue/excludeDefaults
outputDirectory/outputDirectory
plugins
{code}
Notice the empty outputDirectory property? Well, in Maven 2.2.1 that appears to
be ignored. In Maven 3.0.3 however, it deletes the entire project! The
documentation for this should be changed as soon as possible. We lost a bit of
work because of this.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MSITE-621) empty outputDirectory causes mvn clean to delete whole tree
[
https://jira.codehaus.org/browse/MSITE-621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=285152#comment-285152
]
Jim McCaskey commented on MSITE-621:
I forgot to mention that the directories disappear when you run {{mvn clean}}
empty outputDirectory causes mvn clean to delete whole tree
---
Key: MSITE-621
URL: https://jira.codehaus.org/browse/MSITE-621
Project: Maven 2.x and 3.x Site Plugin
Issue Type: Bug
Components: documentation
Affects Versions: 3.0
Environment: Apache Maven 3.0.3 (r1075438; 2011-02-28 11:31:09-0600)
Maven home: D:\maven\apache-maven-3.0.3\bin\..
Java version: 1.6.0_24, vendor: Sun Microsystems Inc.
Java home: D:\j2sdk1.6.0_24\jre
Default locale: en_US, platform encoding: Cp1252
OS name: windows 7, version: 6.1, arch: x86, family: windows
Reporter: Jim McCaskey
On this page:
http://maven.apache.org/plugins/maven-site-plugin/maven-3.html#Old_configuration_Maven_2__3
There is this little code snippet:
{code}
reporting
excludeDefaultstrue/excludeDefaults
outputDirectory/outputDirectory
plugins
{code}
Notice the empty outputDirectory property? Well, in Maven 2.2.1 that appears
to be ignored. In Maven 3.0.3 however, it deletes the entire project! The
documentation for this should be changed as soon as possible. We lost a bit
of work because of this.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRELEASE-674) release plugin converts explicit version to snapshot
[ https://jira.codehaus.org/browse/MRELEASE-674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=277665#comment-277665 ] Jim McCaskey commented on MRELEASE-674: --- FWIW: I have verified that this patch works for the use case specified. release plugin converts explicit version to snapshot - Key: MRELEASE-674 URL: https://jira.codehaus.org/browse/MRELEASE-674 Project: Maven 2.x Release Plugin Issue Type: Bug Components: prepare Affects Versions: 2.1 Environment: Apache Maven 3.0.2 (r1056850; 2011-01-09 01:58:10+0100) Java version: 1.6.0_23, vendor: Sun Microsystems Inc. Java home: i:\tools\jdk\1.6.0_23\jre Default locale: de_DE, platform encoding: Cp1252 OS name: windows xp, version: 5.1, arch: x86, family: windows Reporter: Bernd Mau Attachments: MapVersionPhase.patch I would like to use release:update-versions to explicitly update the versions of my multiproject. Unfortunetly the release plugin converts the given developmentVersion to a SNAPSHOT version. It happens in MapVersionPhase.getNextVersion(). I would expect the plugin to leave the given developmentVersion property as it is, because the prompt version will not be converted. Here is my command line: mvn release:update-versions -DautoVersionSubmodules=true -DdevelopmentVersion=2.0.1 -DpushChanges=false I made a patch and attached it to the issue. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MDEP-250) Add a skip paramater to dependency:unpack
Add a skip paramater to dependency:unpack - Key: MDEP-250 URL: http://jira.codehaus.org/browse/MDEP-250 Project: Maven 2.x Dependency Plugin Issue Type: Improvement Components: unpack Affects Versions: 2.1 Environment: Windows XP Reporter: Jim McCaskey Assignee: Brian Fox We would like to have a skip paramater for dependency:unpack. This would cause the unpack to be skipped if true. We are currently working around the lack of this with profiles. The jetspeed plugin has a skip option that we have found some uses for, but jetspeed is not as robust as the dependency plugin (specifically with multi-module builds). We would prefer to use the core modules anyway. Here is a link to the jetspeed configuration page: http://portals.apache.org/jetspeed-2/maven/jetspeed-maven-plugins.html#Configuration_and_usage_of_the_jetspeed-unpack:unpack_Maven_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] Created: (MDEPLOY-99) deploy:deploy-file over rights maven-metadata.xml
deploy:deploy-file over rights maven-metadata.xml - Key: MDEPLOY-99 URL: http://jira.codehaus.org/browse/MDEPLOY-99 Project: Maven 2.x Deploy Plugin Issue Type: Bug Components: deploy:deploy-file Affects Versions: 2.4 Environment: Windows XP Reporter: Jim McCaskey Using deploy:deploy-file to add multiple version of an artifact causes the artifactId maven-metadata.xml file to be recreated new and the old contents to be removed. Once done I am left with contents like this: ?xml version=1.0 encoding=UTF-8?metadata groupIdcom.pervasive.component/groupId artifactIdartifact-distribution/artifactId version4.0.2.11/version versioning versions version4.0.2.11/version /versions lastUpdated20090401013925/lastUpdated /versioning /metadata This is using Maven 2.1.0 and maven-deploy-plugin 2.4. -- 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: (MNG-4122) deploy:deploy-file over rights maven-metadata.xml
deploy:deploy-file over rights maven-metadata.xml - Key: MNG-4122 URL: http://jira.codehaus.org/browse/MNG-4122 Project: Maven 2 Issue Type: Bug Components: Deployment Affects Versions: 2.1.0 Environment: Windows XP Reporter: Jim McCaskey Using deploy:deploy-file to add multiple version of an artifact causes the artifactId maven-metadata.xml file to be recreated new and the old contents to be removed. Once done I am left with contents like this: ?xml version=1.0 encoding=UTF-8?metadata groupIdcom.pervasive.component/groupId artifactIdartifact-distribution/artifactId version4.0.2.11/version versioning versions version4.0.2.11/version /versions lastUpdated20090401013925/lastUpdated /versioning /metadata This is using Maven 2.1.0 and maven-deploy-plugin 2.4. -- 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-4122) deploy:deploy-file over rights maven-metadata.xml
[ http://jira.codehaus.org/browse/MNG-4122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim McCaskey closed MNG-4122. - Resolution: Fixed Opened this in the wrong place. Opened it in the right place here: http://jira.codehaus.org/browse/MDEPLOY-99 deploy:deploy-file over rights maven-metadata.xml - Key: MNG-4122 URL: http://jira.codehaus.org/browse/MNG-4122 Project: Maven 2 Issue Type: Bug Components: Deployment Affects Versions: 2.1.0 Environment: Windows XP Reporter: Jim McCaskey Using deploy:deploy-file to add multiple version of an artifact causes the artifactId maven-metadata.xml file to be recreated new and the old contents to be removed. Once done I am left with contents like this: ?xml version=1.0 encoding=UTF-8?metadata groupIdcom.pervasive.component/groupId artifactIdartifact-distribution/artifactId version4.0.2.11/version versioning versions version4.0.2.11/version /versions lastUpdated20090401013925/lastUpdated /versioning /metadata This is using Maven 2.1.0 and maven-deploy-plugin 2.4. -- 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: (MNG-4083) project.build.directory not set properly for plugins
project.build.directory not set properly for plugins
Key: MNG-4083
URL: http://jira.codehaus.org/browse/MNG-4083
Project: Maven 2
Issue Type: Bug
Components: Settings
Affects Versions: 2.0.10, 2.0.9
Environment: Windows XP
Reporter: Jim McCaskey
Priority: Minor
Maven 2.0.9 and above do not seem to set project.build.directory properly in
down stream plugins. I have the below test case that shows the problem in the
ant plugin, but I have also seen in in the javadoc plugin. Below is my test
case and the results as seen from 2.0.7, 2.0.8, 2.0.9, and 2.0.10.
Test POM:
?xml version=1.0 encoding=UTF-8?
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
groupIdtest/groupId
artifactIdtest/artifactId
packagingjar/packaging
version1.0.0/version
nameFoo/name
properties
djobjE:\obj/djobj
/properties
build
defaultGoalpackage/defaultGoal
outputDirectory${djobj}/${project.artifactId}/classes/outputDirectory
testOutputDirectory${djobj}/${project.artifactId}/test-classes/testOutputDirectory
directory${djobj}/${project.artifactId}/directory
plugins
plugin
artifactIdmaven-antrun-plugin/artifactId
executions
execution
phasepackage/phase
configuration
tasks
echo message=Debug data/
echo message=basedir =
${basedir}/
echo message=djobj = ${djobj}/
echo message=project.build.sourceDirectory =
${project.build.sourceDirectory}/
echo message=project.build.scriptSourceDirectory =
${project.build.scriptSourceDirectory}/
echo message=project.build.testSourceDirectory =
${project.build.testSourceDirectory}/
echo message=project.build.outputDirectory =
${project.build.outputDirectory}/
echo message=project.build.testOutputDirectory =
${project.build.testOutputDirectory}/
echo message=project.build.directory =
${project.build.directory}/
/tasks
/configuration
goals
goalrun/goal
/goals
/execution
/executions
/plugin
/plugins
/build
/project
Test output:
Maven 2.0.7
[INFO] [antrun:run {execution: default}]
[INFO] Executing tasks
[echo] Debug data
[echo] basedir = E:\foo
[echo] djobj = E:\obj
[echo] project.build.sourceDirectory = E:\foo\src\main\java
[echo] project.build.scriptSourceDirectory = src/main/scripts
[echo] project.build.testSourceDirectory = E:\foo\src\test\java
[echo] project.build.outputDirectory = E:\obj/test/classes
[echo] project.build.testOutputDirectory = E:\obj/test/test-classes
[echo] project.build.directory = E:\obj/test
[INFO] Executed tasks
Maven 2.0.8
[INFO] [antrun:run {execution: default}]
[INFO] Executing tasks
[echo] Debug data
[echo] basedir = E:\foo
[echo] djobj = E:\obj
[echo] project.build.sourceDirectory = E:\foo\src\main\java
[echo] project.build.scriptSourceDirectory = src/main/scripts
[echo] project.build.testSourceDirectory = E:\foo\src\test\java
[echo] project.build.outputDirectory = E:\obj/test/classes
[echo] project.build.testOutputDirectory = E:\obj/test/test-classes
[echo] project.build.directory = E:\obj/test
[INFO] Executed tasks
Maven 2.0.9
[INFO] [antrun:run {execution: default}]
[INFO] Executing tasks
[echo] Debug data
[echo] basedir = E:\foo
[echo] djobj = E:\obj
[echo] project.build.sourceDirectory = E:\foo\src\main\java
[echo] project.build.scriptSourceDirectory = src/main/scripts
[echo] project.build.testSourceDirectory = E:\foo\src\test\java
[echo] project.build.outputDirectory = E:\foo\E:\obj\test\classes
[echo] project.build.testOutputDirectory =
E:\foo\E:\obj\test\test-classes
[echo] project.build.directory = E:\foo\E:\obj\test
[INFO] Executed tasks
Maven 2.0.10
[INFO] [antrun:run {execution: default}]
[INFO] Executing tasks
[echo] Debug data
[echo] basedir = E:\foo
[echo] djobj = E:\obj
[echo] project.build.sourceDirectory = E:\foo\src\main\java
[echo] project.build.scriptSourceDirectory = src/main/scripts
[echo]
