[jira] Created: (MAVENUPLOAD-1169) please upload this bundle to ibiblio

please upload this bundle to ibiblio Key: MAVENUPLOAD-1169 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1169 Project: maven-upload-requests Issue Type: Task Reporter: geoff hendrey shade

[jira] Reopened: (MECLIPSE-120) Force inter-project dependencies

[ http://jira.codehaus.org/browse/MECLIPSE-120?page=all ] Joerg Schaible reopened MECLIPSE-120: - "Sorry but we can't do this. This would present the user with a different set of dependency relations in eclipse than is really defined." Gosh

[jira] Commented: (MECLIPSE-100) should have option to download and attach javadocs regardless of source archive status

[ http://jira.codehaus.org/browse/MECLIPSE-100?page=comments#action_76884 ] Kenney Westerhof commented on MECLIPSE-100: --- See MECLIPSE-143 for technical solution > should have option to download and attach javadocs regardless of source

[jira] Commented: (MECLIPSE-32) Allow for forcing the creation of direct project references for dependencies

[ http://jira.codehaus.org/browse/MECLIPSE-32?page=comments#action_76883 ] Kenney Westerhof commented on MECLIPSE-32: -- Hm. Not sure I like this solution in this case. I've got the same issue here - when importing the m2 source tree and p

[jira] Commented: (MECLIPSE-40) Multi project dependencies should not require eclipse project names to be the artifactId

[ http://jira.codehaus.org/browse/MECLIPSE-40?page=comments#action_76882 ] Kenney Westerhof commented on MECLIPSE-40: -- you should indeed use the artifactId, not the module name. But if more people want this, we could do one of 2 things:

[jira] Closed: (MECLIPSE-80) Be able to exclude specific projects from having Eclipse .project/.classpath generated for them

[ http://jira.codehaus.org/browse/MECLIPSE-80?page=all ] Kenney Westerhof closed MECLIPSE-80. Resolution: Won't Fix the reactor excludes is the proper solution as it only affects imports in eclipse. I'd hate to see custom 'skip this' configurations

[jira] Closed: (MECLIPSE-158) Add the ability to selectively treat a referenced project as a local repository file

[ http://jira.codehaus.org/browse/MECLIPSE-158?page=all ] Kenney Westerhof closed MECLIPSE-158. - Resolution: Won't Fix Yup, makes perfect sense. But this is such a rare case (you should really try to fix that classname problem), that you should us

[jira] Commented: (MECLIPSE-156) Plugin should support setting file encoding

[ http://jira.codehaus.org/browse/MECLIPSE-156?page=comments#action_76878 ] Kenney Westerhof commented on MECLIPSE-156: --- What's your usecase? It might be better to detect the encoding automatically rather than having to specify a comple

[jira] Commented: (MECLIPSE-119) Allow custom project name for eclipse projects

[ http://jira.codehaus.org/browse/MECLIPSE-119?page=comments#action_76879 ] Kenney Westerhof commented on MECLIPSE-119: --- I prefer a switch like 'eclipse.addVersionToProjectNames'. The -Declipse.projectname=LITERAL_STRING is dangerous a

[jira] Commented: (MWAR-79) copy fails in a multi-project build

[ http://jira.codehaus.org/browse/MWAR-79?page=comments#action_76877 ] Elliot Metsger commented on MWAR-79: May want to take out the System.out.println in my patch... forgot to clean that up, sorry about that. > copy fails in a multi-projec

[jira] Updated: (MWAR-79) copy fails in a multi-project build

[ http://jira.codehaus.org/browse/MWAR-79?page=all ] Elliot Metsger updated MWAR-79: --- Attachment: MWAR-79.patch Prepending the Project's baseDir to the resource directory (if the resource directory is not absolute) fixed this issue. Attached is a patch.

[jira] Commented: (MECLIPSE-152) Write .classpath with ordered dependencies [incl. Patch]

[ http://jira.codehaus.org/browse/MECLIPSE-152?page=comments#action_76875 ] Kenney Westerhof commented on MECLIPSE-152: --- Crap. I wrote a few Kb and accidently closed the window. I hate web-guis. Short story: continuum-release depends o

[jira] Created: (MWAR-79) copy fails in a multi-project build

copy fails in a multi-project build -- Key: MWAR-79 URL: http://jira.codehaus.org/browse/MWAR-79 Project: Maven 2.x War Plugin Issue Type: Bug Affects Versions: 2.0.2 Environment:

[jira] Commented: (MECLIPSE-34) Goals to build eclipse plugin/feature and site

[ http://jira.codehaus.org/browse/MECLIPSE-34?page=comments#action_76873 ] Kenney Westerhof commented on MECLIPSE-34: -- Shouldn't we have an eclipse packaging mojo for this that doesn't depend on an eclipse installation? Could this possi

[jira] Commented: (MECLIPSE-78) create eclipse projects which are m2eclipse ready

[ http://jira.codehaus.org/browse/MECLIPSE-78?page=comments#action_76871 ] Kenney Westerhof commented on MECLIPSE-78: -- Hi, I'm not sure wheter this patch is needed at all - m2eclipse should be able to import existing projects just fine

[jira] Commented: (MECLIPSE-58) Links should not be created when current directory = target directory (eclipse.workspace=***)

[ http://jira.codehaus.org/browse/MECLIPSE-58?page=comments#action_76870 ] Kenney Westerhof commented on MECLIPSE-58: -- Cool. Thanks for understanding :) Please keep up the bugreports - still lots of stuff not working properly.. Thanks!

[jira] Commented: (MECLIPSE-147) Dependencies that are inherited from subprojects that are specified in Require-Bundle or Import-Package should be excluded

[ http://jira.codehaus.org/browse/MECLIPSE-147?page=comments#action_76869 ] Kenney Westerhof commented on MECLIPSE-147: --- I'm sorry but this patch is totally useless :) Where did you specify the 'Require-Bundle'? I don't think you can j

[jira] Closed: (MECLIPSE-144) mvn breaks some buildCommand section in .project

[ http://jira.codehaus.org/browse/MECLIPSE-144?page=all ] Kenney Westerhof closed MECLIPSE-144. - Resolution: Duplicate Duplicate of MECLIPSE-128 > mvn breaks some buildCommand section in .project > >

[jira] Commented: (MECLIPSE-58) Links should not be created when current directory = target directory (eclipse.workspace=***)

[ http://jira.codehaus.org/browse/MECLIPSE-58?page=comments#action_76866 ] Stephen Duncan Jr commented on MECLIPSE-58: --- Based on Eclipse 3.2's support for nested projects, I no longer have interest in the -Declipse.workspace= features.

[jira] Closed: (MECLIPSE-122) Eclipse plugin doesn't use dependency conflict resolution mechanism

[ http://jira.codehaus.org/browse/MECLIPSE-122?page=all ] Kenney Westerhof closed MECLIPSE-122. - Resolution: Fixed At this time this issue seems to be solved. > Eclipse plugin doesn't use dependency conflict resolution mechanism > --

[jira] Commented: (MECLIPSE-128) Eclipse goal breaks manually-configured external builder

[ http://jira.codehaus.org/browse/MECLIPSE-128?page=comments#action_76864 ] Kenney Westerhof commented on MECLIPSE-128: --- Could you please verify if this is still the case? Lots of effort has gone into preserving existing configurations.

[jira] Closed: (MECLIPSE-120) Force inter-project dependencies

[ http://jira.codehaus.org/browse/MECLIPSE-120?page=all ] Kenney Westerhof closed MECLIPSE-120. - Resolution: Won't Fix Sorry but we can't do this. This would present the user with a different set of dependency relations in eclipse than is really def

[jira] Closed: (MECLIPSE-69) can plugin support equivalent of maven.eclipse.classpath.include feature found in 1.x version?

[ http://jira.codehaus.org/browse/MECLIPSE-69?page=all ] Kenney Westerhof closed MECLIPSE-69. Resolution: Won't Fix no, this is not possible in m2. If you want to add extra paths to the classpath, you should also add them to the pom, otherwise the

[jira] Commented: (MECLIPSE-118) J2EE (runtime) dependencies of a Webapp-Library-Parent hierarchy not correct

[ http://jira.codehaus.org/browse/MECLIPSE-118?page=comments#action_76861 ] Kenney Westerhof commented on MECLIPSE-118: --- I believe this is fixed in trunk - dependencies are automatically exported. Can you verify this using the latest ma

[jira] Closed: (MECLIPSE-115) The generated .project and .classpath files have to edited before using

[ http://jira.codehaus.org/browse/MECLIPSE-115?page=all ] Kenney Westerhof closed MECLIPSE-115. - Resolution: Cannot Reproduce The bug was in eclipse, not in maven; I checked the link and it's fixed. Never had any problems with it, though. As for th

[jira] Commented: (MECLIPSE-56) Generated .project-file misses encoding declaration

[ http://jira.codehaus.org/browse/MECLIPSE-56?page=comments#action_76859 ] Kenney Westerhof commented on MECLIPSE-56: -- There's no need to specify an encoding in the Generated .project-file misses encoding declaration > --

[jira] Commented: (MECLIPSE-37) eclipse:eclipse should execute in a later phase than "generate-sources"

[ http://jira.codehaus.org/browse/MECLIPSE-37?page=comments#action_76857 ] Kenney Westerhof commented on MECLIPSE-37: -- First - only the generate-* phases should add (test)compileSourceRoots. The problem is that the generate-test* phases

[jira] Commented: (MECLIPSE-58) Links should not be created when current directory = target directory (eclipse.workspace=***)

[ http://jira.codehaus.org/browse/MECLIPSE-58?page=comments#action_76856 ] Kenney Westerhof commented on MECLIPSE-58: -- You should NEVER point the eclipse.workspace to the actual project locations! I can see why you did it - flatten the p

[jira] Closed: (MECLIPSE-53) Output Location When Using -Declipse.workspace= should point to linked Maven Project location

[ http://jira.codehaus.org/browse/MECLIPSE-53?page=all ] Kenney Westerhof closed MECLIPSE-53. Resolution: Won't Fix The whole idea of specifying a workspace location is so you can have a workspace (i.e. write access on disk) in ANOTHER location than

[jira] Commented: (MECLIPSE-140) SNAPSHOT plugin versions are not supported for PDE projects. Error in MANIFEST.MF

[ http://jira.codehaus.org/browse/MECLIPSE-140?page=comments#action_76854 ] Kenney Westerhof commented on MECLIPSE-140: --- I'm not sure wheter this should be fixed. If you're using PDE you have to abide by the OSGI versioning limitations,

[jira] Commented: (MECLIPSE-139) Eclipse plugin cannot handle Java source files in resource directories

[ http://jira.codehaus.org/browse/MECLIPSE-139?page=comments#action_76853 ] Kenney Westerhof commented on MECLIPSE-139: --- Hi, Thanks for the patch, but a few comments: - Could you please sync it with the current trunk? I know we slacked

[jira] Commented: (MRM-207) POM error when indexing an m1 repository

[ http://jira.codehaus.org/browse/MRM-207?page=comments#action_76849 ] Henri Yandell commented on MRM-207: --- I'm not sure if this happened while indexing actually - I think the bug in indexing was: 2006-10-06 15:26:38,343 [http-8080-Processor24

[jira] Closed: (MJAVADOC-93) Allow commas in text arguments doctitle, windowtitle, header, footer, and bottom [PATCH ATTACHED]

[ http://jira.codehaus.org/browse/MJAVADOC-93?page=all ] Brian Fox closed MJAVADOC-93. - Resolution: Fixed Fix Version/s: 2.1 Merged into trunk > Allow commas in text arguments doctitle, windowtitle, header, footer, and > bottom [PATCH ATTACHED] > --

[jira] Commented: (MSUREFIREREP-6) surefire-report reruns tests

[ http://jira.codehaus.org/browse/MSUREFIREREP-6?page=comments#action_76845 ] Chris Hagmann commented on MSUREFIREREP-6: -- (Another attempt - JIRA administrator please remove my previous comment) I would add a second goal (e.g. report-on

[jira] Created: (MRM-208) Javadoc error while indexing m1 repository

Javadoc error while indexing m1 repository -- Key: MRM-208 URL: http://jira.codehaus.org/browse/MRM-208 Project: Archiva Issue Type: Bug Components: indexing Reporter: Henri Yande

[jira] Commented: (MSUREFIREREP-6) surefire-report reruns tests

[ http://jira.codehaus.org/browse/MSUREFIREREP-6?page=comments#action_76844 ] Chris Hagmann commented on MSUREFIREREP-6: -- I would add a second goal (e.g. report-only) which doesn't execute the phase "test". Meaning: surefire-report:rep

[jira] Created: (MRM-207) POM error when indexing an m1 repository

POM error when indexing an m1 repository Key: MRM-207 URL: http://jira.codehaus.org/browse/MRM-207 Project: Archiva Issue Type: Bug Components: indexing Reporter: Henri Yandell

[jira] Commented: (MNG-915) circular dependency failure in the reactor with activated plugins

[ http://jira.codehaus.org/browse/MNG-915?page=comments#action_76842 ] Kenney Westerhof commented on MNG-915: -- I can't find any commits on this, and it's still a problem when you run mvn eclipse:eclipse -r -Dmaven.reactor.includes=componen

[jira] Commented: (SUREFIRE-31) support junit 4.0

[ http://jira.codehaus.org/browse/SUREFIRE-31?page=comments#action_76836 ] Karl M. Davis commented on SUREFIRE-31: --- Oh, I should also mention that you will not be able to run both JUnit3 and JUnit4 tests alongside each other with this patch

[jira] Updated: (SUREFIRE-31) support junit 4.0

[ http://jira.codehaus.org/browse/SUREFIRE-31?page=all ] Karl M. Davis updated SUREFIRE-31: -- Attachment: SUREFIRE31_karl_surefire_surefire-providers_surefire-junit.patch > support junit 4.0 > - > > Key: SUREFIRE-31 >

[jira] Updated: (SUREFIRE-31) support junit 4.0

[ http://jira.codehaus.org/browse/SUREFIRE-31?page=all ] Karl M. Davis updated SUREFIRE-31: -- Attachment: SUREFIRE31_karl_maven-surefire-plugin.patch > support junit 4.0 > - > > Key: SUREFIRE-31 > URL: http

[jira] Commented: (SUREFIRE-31) support junit 4.0

[ http://jira.codehaus.org/browse/SUREFIRE-31?page=comments#action_76833 ] Karl M. Davis commented on SUREFIRE-31: --- As near as I can tell, none of the previous patches work: - surefire-junit4.zip: Does not compile and after spending a bit l

[jira] Created: (MPIDEA-49) idea:module fails on project:type of ejb

idea:module fails on project:type of ejb Key: MPIDEA-49 URL: http://jira.codehaus.org/browse/MPIDEA-49 Project: maven-idea-plugin Issue Type: Bug Affects Versions: 1.6 Environment: Maven

[jira] Created: (MECLIPSE-167) .component assumes all dependencies should be packaged in WAR

.component assumes all dependencies should be packaged in WAR - Key: MECLIPSE-167 URL: http://jira.codehaus.org/browse/MECLIPSE-167 Project: Maven 2.x Eclipse Plugin Issue Type: Bug

[jira] Commented: (MNG-2593) Maven 2 stumbels upon non ASCII characters in the value of a value in the $HOME/.m2/settings.xml

[ http://jira.codehaus.org/browse/MNG-2593?page=comments#action_76825 ] Milos Kleint commented on MNG-2593: --- it's MEVENIDE-449, not MNG-449 > Maven 2 stumbels upon non ASCII characters in the value of a > value in the $HOME/.m2/settings.xml >

[jira] Created: (MECLIPSE-166) Configure Eclipse Checkstyle plugin

Configure Eclipse Checkstyle plugin --- Key: MECLIPSE-166 URL: http://jira.codehaus.org/browse/MECLIPSE-166 Project: Maven 2.x Eclipse Plugin Issue Type: New Feature Reporter: Julien HENRY It wou

[jira] Closed: (MAVENUPLOAD-1053) Upload hibernate-tools 3.2.0-beta6

[ http://jira.codehaus.org/browse/MAVENUPLOAD-1053?page=all ] Johann Reyes closed MAVENUPLOAD-1053. - Resolution: Won't Fix Since this tools version bundle is already release, seems the best solution would be to go to the next release. > Upload hib

[jira] Updated: (CONTINUUM-954) verify all checkbox persistence in continuum

[ http://jira.codehaus.org/browse/CONTINUUM-954?page=all ] Marvin King updated CONTINUUM-954: -- Attachment: CONTINUUM954-continuum-webapp.patch - fixed checkbox of edit schedule > verify all checkbox persistence in continuum > ---

[jira] Commented: (SCM-241) scm:bootstrap does not propogate --settings or -s command line option

[ http://jira.codehaus.org/browse/SCM-241?page=comments#action_76819 ] Dan Tran commented on SCM-241: -- mvn -s settings-file scm:bootstrap works at first, but internally scm:bootstrap also invoke a shell to run the goal but it does not include the se

[jira] Closed: (MAVENUPLOAD-978) Upload ejb-3.0-public-draft-20060502 (needed for hibernate)

[ http://jira.codehaus.org/browse/MAVENUPLOAD-978?page=all ] Carlos Sanchez closed MAVENUPLOAD-978. -- Assignee: Carlos Sanchez Resolution: Won't Fix At its time this was not uploaded due to license constraints that might prevent it's upload.

[jira] Commented: (MAVENUPLOAD-1053) Upload hibernate-tools 3.2.0-beta6

[ http://jira.codehaus.org/browse/MAVENUPLOAD-1053?page=comments#action_76809 ] Carlos Sanchez commented on MAVENUPLOAD-1053: - Can anybody clarify what bundles need to be on ibiblio? this thread is confusing > Upload hibernate-tools

[jira] Closed: (MAVENUPLOAD-1153) Please upload MessAdmin 4.0

[ http://jira.codehaus.org/browse/MAVENUPLOAD-1153?page=all ] Carlos Sanchez closed MAVENUPLOAD-1153. --- Assignee: Carlos Sanchez Resolution: Fixed > Please upload MessAdmin 4.0 > --- > > Key: MAVENUPLOAD

[jira] Closed: (MAVENUPLOAD-1160) Upload Stripes 1.4.1 to IBiblio Repository

[ http://jira.codehaus.org/browse/MAVENUPLOAD-1160?page=all ] Carlos Sanchez closed MAVENUPLOAD-1160. --- Assignee: Carlos Sanchez Resolution: Fixed > Upload Stripes 1.4.1 to IBiblio Repository > -- > >

[jira] Closed: (MAVENUPLOAD-1162) Jackcess 1.1.7 release

[ http://jira.codehaus.org/browse/MAVENUPLOAD-1162?page=all ] Carlos Sanchez closed MAVENUPLOAD-1162. --- Assignee: Carlos Sanchez Resolution: Fixed > Jackcess 1.1.7 release > -- > > Key: MAVENUPLOAD-1162 >

[jira] Closed: (MAVENUPLOAD-1152) Upload log4j 1.2.14 release

[ http://jira.codehaus.org/browse/MAVENUPLOAD-1152?page=all ] Carlos Sanchez closed MAVENUPLOAD-1152. --- Assignee: Carlos Sanchez Resolution: Won't Fix > Upload log4j 1.2.14 release > --- > > Key: MAVENUP

[jira] Closed: (MAVENUPLOAD-1167) Upload Click 1.0 bundles

[ http://jira.codehaus.org/browse/MAVENUPLOAD-1167?page=all ] Carlos Sanchez closed MAVENUPLOAD-1167. --- Assignee: Carlos Sanchez Resolution: Fixed > Upload Click 1.0 bundles > > > Key: MAVENUPLOAD-1167

[jira] Commented: (MAVENUPLOAD-1155) Spring modules 0.6 bundles

[ http://jira.codehaus.org/browse/MAVENUPLOAD-1155?page=comments#action_76807 ] Carlos Sanchez commented on MAVENUPLOAD-1155: - It was not skipped, the bundle is wrong, check dashes in file names > Spring modules 0.6 bundles > ---

[jira] Closed: (MAVENUPLOAD-1165) Sync with Databinder repository

[ http://jira.codehaus.org/browse/MAVENUPLOAD-1165?page=all ] Carlos Sanchez closed MAVENUPLOAD-1165. --- Assignee: Carlos Sanchez Resolution: Fixed > Sync with Databinder repository > --- > > Key: MAV

[jira] Closed: (MAVENUPLOAD-1121) Jericho HTML Parser 2.3

[ http://jira.codehaus.org/browse/MAVENUPLOAD-1121?page=all ] Carlos Sanchez closed MAVENUPLOAD-1121. --- Assignee: Carlos Sanchez Resolution: Fixed The way to speed up is create your own repo and we'll sync from it, see end of http://maven.apa

[jira] Closed: (MAVENUPLOAD-1168) Junit 4.1

[ http://jira.codehaus.org/browse/MAVENUPLOAD-1168?page=all ] Carlos Sanchez closed MAVENUPLOAD-1168. --- Assignee: Carlos Sanchez Resolution: Fixed > Junit 4.1 > - > > Key: MAVENUPLOAD-1168 > URL: http://

[jira] Closed: (CONTINUUM-943) Initial password for admin validation

[ http://jira.codehaus.org/browse/CONTINUUM-943?page=all ] Edwin Punzalan closed CONTINUUM-943. Resolution: Fixed Fix Version/s: 1.1 Closing this issue now... I guess it was either fixed or my copy was invalid. > Initial password for admin va

[jira] Commented: (MSUREFIRE-115) Classloading problem for getting a resource

[ http://jira.codehaus.org/browse/MSUREFIRE-115?page=comments#action_76786 ] Ronny Naess commented on MSUREFIRE-115: --- Anything new in this matter? I have testresources in two test dependent jars. My artifacts has who depends this test-jar

[jira] Closed: (MCLOVER-47) Align plugin documentation with Maven standards

[ http://jira.codehaus.org/browse/MCLOVER-47?page=all ] Vincent Massol closed MCLOVER-47. - Resolution: Fixed docck plugin is passing now. > Align plugin documentation with Maven standards > --- > >

[jira] Commented: (MSUREFIREREP-6) surefire-report reruns tests

[ http://jira.codehaus.org/browse/MSUREFIREREP-6?page=comments#action_76778 ] Anders Sveen commented on MSUREFIREREP-6: - Same prob, and experiencing excessive build times which is a big problem for our project. > surefire-report reruns

[jira] Commented: (SCM-241) scm:bootstrap does not propogate --settings or -s command line option

[ http://jira.codehaus.org/browse/SCM-241?page=comments#action_76775 ] L Northrop commented on SCM-241: I would like to specify options for servers, profiles and most importantly active profiles however these settings need to override all setting

[jira] Updated: (CONTINUUM-945) Build Project command in projectGroupSummary will redirect you to groupSummary after queueing the command

[ http://jira.codehaus.org/browse/CONTINUUM-945?page=all ] Marvin King updated CONTINUUM-945: -- Attachment: CONTINUUM945-continuum-webapp-10062006-2.patch the page should be redirected to projectGroupSummary > Build Project command in projectGroupSumm

[jira] Commented: (MCLOVER-47) Align plugin documentation with Maven standards

[ http://jira.codehaus.org/browse/MCLOVER-47?page=comments#action_76773 ] Vincent Massol commented on MCLOVER-47: --- Thanks a lot Franz. Good job! I've applied it with some modifications: * Swapped order of features and goals overview in ind

[jira] Commented: (CONTINUUM-943) Initial password for admin validation

[ http://jira.codehaus.org/browse/CONTINUUM-943?page=comments#action_76772 ] Jesse McConnell commented on CONTINUUM-943: --- I couldn't replicate this, but edwin is going to try it again and the close it if is not valid any longer > Init

[jira] Closed: (MNG-2555) maven-metadata.xml for springframework.spring is missing recent versions

[ http://jira.codehaus.org/browse/MNG-2555?page=all ] Carlos Sanchez closed MNG-2555. --- Assignee: Carlos Sanchez Resolution: Duplicate > maven-metadata.xml for springframework.spring is missing recent versions > ---

[jira] Commented: (MNG-2555) maven-metadata.xml for springframework.spring is missing recent versions

[ http://jira.codehaus.org/browse/MNG-2555?page=comments#action_76767 ] Andres Rodriguez commented on MNG-2555: --- Version 2.0 isn't included either, even though it's been already uploaded. What is the procedure for that? > maven-metadata.xm

[jira] Closed: (MRELEASE-118) Invalid tag proposal for CVS

[ http://jira.codehaus.org/browse/MRELEASE-118?page=all ] Damien Lecan closed MRELEASE-118. - Resolution: Duplicate Duplicate of MRELEASE-110 > Invalid tag proposal for CVS > > > Key: MRELEASE-118 >

[jira] Commented: (MRELEASE-169) Provide a mechanism to undo the effects of prepare

[ http://jira.codehaus.org/browse/MRELEASE-169?page=comments#action_76763 ] Daniel Nilsson commented on MRELEASE-169: - Hi! Mayby a prepare-commit-rollback scenario would work. Ie you first do a release:prepare (which makes a couple of tem