[jira] Created: (MDEP-253) Purge does not purge released artifacts
Purge does not purge released artifacts --- Key: MDEP-253 URL: http://jira.codehaus.org/browse/MDEP-253 Project: Maven 2.x Dependency Plugin Issue Type: Bug Components: purge-local-repository Affects Versions: 2.0 Environment: Linux, JDK 1.5, Maven 2.0.10 Reporter: James Lorenzen Assignee: Brian Fox I am running into a problem when running mvn dependency:purge-local-repository in that it does not remove any local artifacts for a large multi-module project. I run it from the parent directory and it reports the following for all my sub modules [INFO] Nothing to do for project: ... I expect the goal to examine all my dependencies, including transitive dependencies, and remove them from the local 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] Created: (MRELEASE-452) allowTimestampedSnapshots=true still fails with snapshot dependencies
allowTimestampedSnapshots=true still fails with snapshot dependencies - Key: MRELEASE-452 URL: http://jira.codehaus.org/browse/MRELEASE-452 Project: Maven 2.x Release Plugin Issue Type: Bug Components: prepare Affects Versions: 2.0-beta-9 Environment: maven 2.0.9 maven release plugin v 2.0-beta-9 Reporter: James Lorenzen When I try to use the config property, allowTimestampedSnapshots, to release our large multi-module project, the build still fails on snapshot dependencies. Here is the command I am running: mvn release:clean release:prepare -DallowTimestampedSnapshots=true -DpreparationGoals=clean install -Dmaven.test.skip=true -Dmaven.integration.skip=true -Dmaven.tck.skip=true -DdryRun=false -B Here is the failure: [ERROR] BUILD FAILURE [INFO] [INFO] Can't release project due to non released dependencies : com.accenture.identity.agent:identity-service-agent:jar:1.6.0-SNAPSHOT:compile in project 'netCDS Web Services' (com.accenture.netcds:netcds-ws:war:0.8.0906.0-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] Created: (MWAR-196) Need separate includes for just WEB-INF/lib
Need separate includes for just WEB-INF/lib --- Key: MWAR-196 URL: http://jira.codehaus.org/browse/MWAR-196 Project: Maven 2.x WAR Plugin Issue Type: Improvement Reporter: James Lorenzen I am trying to create a skinny war by limiting the WEB-INF/lib to just the jars that are needed, leaving the rest to be defined in the EAR/lib. Ideally I would like to be able to configure the war with just the jars I need vs defining all the ones I don't want. For example, I want to be able to configure my lite WAR with only a few xml jars, but by default I want it to include everything else under WEB-INF such as classes or flex or images, scripts, styles, etc. WEB-INF/lib/xml* Currently when I want to include just a few jars I have to list out all the folders under my war too. images/*, scripts/*, styles/*, META-INF/*, WEB-INF/*, WEB-INF/classes/*, WEB-INF/flex/*, WEB-INF/lib/xml*, -- 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: (MRELEASE-404) release:prepare does not use tagBase
release:prepare does not use tagBase
Key: MRELEASE-404
URL: http://jira.codehaus.org/browse/MRELEASE-404
Project: Maven 2.x Release Plugin
Issue Type: Bug
Components: prepare
Affects Versions: 2.0-beta-8
Environment: linux jdk 1.5
Reporter: James Lorenzen
When I run release:prepare I want the release plugin to create a branch verses
creating a tag. Currently it seems that it doesn't use the tagBase value
defined in the pom.
Here is my pom definition
org.apache.maven.plugins
maven-release-plugin
${next.release}
https://server/svn/netcds/branches
Jira: AC-100.
[maven-release-plugin]
When running mvn release:prepare the release plugin still creates a tag. Is the
syntax not correct for tagBase?
--
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: (MRELEASE-173) Allow command line specification of versions
[ http://jira.codehaus.org/browse/MRELEASE-173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=152052#action_152052 ] James Lorenzen commented on MRELEASE-173: - It would be really great if v 2.0-beta-8 could get released so I could use this feature. > Allow command line specification of versions > > > Key: MRELEASE-173 > URL: http://jira.codehaus.org/browse/MRELEASE-173 > Project: Maven 2.x Release Plugin > Issue Type: Improvement >Affects Versions: 2.0-beta-3, 2.0-beta-4, 2.0-beta-5 >Reporter: Chris Tucker >Assignee: Paul Gier > Fix For: 2.0-beta-8 > > Attachments: release-version.diff > > > It is convenient in a batchMode environment to specify the version to release > and the new version to update SNAPSHOT artifacts to. The attached patch > against maven-release-manager and maven-release-plugin provides the basic > functionality to allow this. > The maven-release-plugin will now accept two new arguments: > -DreleaseVersion= > -DdevVersion= > For example, to release version 1.2 of a project and move up to version > 2.0-SNAPSHOT one would issue: > $ mvn release:clean release:prepare -DreleaseVersion=1.2 -DdevVersion=2.0 > --batch-mode > This patch is against current trunk (471862). It currently doesn't support > resuming, so a release:clean is necessary if a previous release attempt has > been prepared. -- 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: (CONTINUUM-562) "groupId is null" when uploading maven 1 pom but it isn't
[ http://jira.codehaus.org/browse/CONTINUUM-562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_89219 ] James Lorenzen commented on CONTINUUM-562: -- I am also receiving this issue with a maven 1 project.xml. And the group id is not empty. > "groupId is null" when uploading maven 1 pom but it isn't > - > > Key: CONTINUUM-562 > URL: http://jira.codehaus.org/browse/CONTINUUM-562 > Project: Continuum > Issue Type: Bug > Components: Web interface >Affects Versions: 1.0.2 > Environment: Windows 2000, jdk 1.4.2_09, PIV 1Gb >Reporter: David MartÃnez > Fix For: 1.1 > > Attachments: project.xml > > > Hi, > I'm trying to upload enclosed maven 1 pom and get a message: > " * Error while reading maven POM. > Check the logs for more details. > * groupId is null. > Check the logs for more details." > But, as you can see in the enclosed pom, groupId is not null. > The pom works properly when unsing it maven 1. > Thank you in advance. -- 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
