[jira] (MDEP-430) Dependency plugin does not seem to respect profile specific copy goals
Kamaldeep Tumkur created MDEP-430:
-
Summary: Dependency plugin does not seem to respect profile
specific copy goals
Key: MDEP-430
URL: https://jira.codehaus.org/browse/MDEP-430
Project: Maven Dependency Plugin
Issue Type: Bug
Components: copy
Affects Versions: 2.1
Environment: Mac OSX Mountain Lion 10.8.4
Reporter: Kamaldeep Tumkur
I am using the dependency plugin inside a swf type project that builds using
Maven. Ant is currently being used to copy the target files to the destination
directories, but my hope is to use the dependency plugin so that everything is
included inside the POM.
Here's my rough POM structure:
!-- Below build properties are listed outside of 'profile' since they are not
supported inside a 'profile' tag.
build
sourceDirectorydir/sourceDirectory
finalName${project.name}/finalName
/build
profiles
profile
idprofile1/id
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-dependency-plugin/artifactId
.
goalcopy/goal
.
configuration ... /configuration
outputDirectoryDIR1/outputDirectory
/plugin
/plugins
/build
/profile
profile
idprofile2/id
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-dependency-plugin/artifactId
.
goalcopy/goal
.
configuration ... /configuration
outputDirectoryDIR2/outputDirectory
/plugin
/plugins
/build
/profile
/profiles
What I am seeing:
When I run: 'mvn -U clean install -P profile1', the execution for profile1
proceeds and the files are copied to DIR1 as expected.
When I run: 'mvn -U clean install -P profile2', the execution for profile1 and
profile2 both happen and the file meant to go into DIR2 is also copied into
DIR1. This is undesirable.
Please let me know if any further details may be helpful here. Thanks for your
time.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRELEASE-594) release:prepare should stop when there is snapshots in dependencies management
[ https://jira.codehaus.org/browse/MRELEASE-594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Foegen updated MRELEASE-594: --- Attachment: allowUnusedSnapshotsInDependencyManagement.patch Hi, please have a look at the patch I've attached. By default the behaviour of the plugin remains the same but it can be enabled by adding the following flag -DallowUnusedSnapshotsInDependencyManagement=false (the default is true). If enabled, it treats snapshots in the dependency management section the same way as snapshots in the dependency section, i.e. snapshots can be resolved or the release fails. release:prepare should stop when there is snapshots in dependencies management -- Key: MRELEASE-594 URL: https://jira.codehaus.org/browse/MRELEASE-594 Project: Maven Release Plugin Issue Type: Bug Components: prepare Reporter: Thomas Bruyelle Assignee: Olivier Lamy Fix For: Backlog Attachments: allowUnusedSnapshotsInDependencyManagement.patch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Maven parsing pom.xml incorrectly
I'm using Thrift in my Maven project, compiling my .thrift code to .java as part of the generate-sources step. To do this, I use the maven antrun plugin in my pom.xml, which executes a command line call to the thrift executable, and sends it the appropriate argument flags, such as -out and --gen. However, when I comment out this plugin with the standard XML comment syntax !-- ... --, Maven fails to parse the pom file. It doesn't like the fact that the comment contains --gen, expecting the comment to end right there. Can we please improve Maven's comment syntax parsing for pom.xml?
[jira] (MSITE-665) Site plugin version 3.2 seems to modify a project's classpath.
[ https://jira.codehaus.org/browse/MSITE-665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=332939#comment-332939 ] Christian Schulte commented on MSITE-665: - Could someone please perform a release of the site plugin with the attached patch applied ? It is a regression and is blocking the upgrade to Maven 3.1.x. Site plugin version 3.2 seems to modify a project's classpath. -- Key: MSITE-665 URL: https://jira.codehaus.org/browse/MSITE-665 Project: Maven Site Plugin Issue Type: Bug Affects Versions: 3.2 Environment: Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100) Java version: 1.7.0_03, vendor: Oracle Corporation Reporter: Christian Schulte Attachments: MSITE-665.patch, MSITE-665.zip, msp-3.1.log, msp-3.2.log -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
