[jira] Commented: (MECLIPSE-334) Add a rule that determined artifacts will be always recognized as reactor projects

[ http://jira.codehaus.org/browse/MECLIPSE-334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_116337 ] Martin Zeltner commented on MECLIPSE-334: - After the discussion with Richie I'm convinced now that the MECLIPSE-344

[jira] Commented: (MECLIPSE-344) connecting existing workspace artifact-projects

[ http://jira.codehaus.org/browse/MECLIPSE-344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_116338 ] Martin Zeltner commented on MECLIPSE-344: - After the discussion with Richie I'm convinced now that the MECLIPSE-344

[jira] Updated: (MJAR-30) Allow includes/excludes specification

[ http://jira.codehaus.org/browse/MJAR-30?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated MJAR-30: - Fix Version/s: 2.2 > Allow includes/excludes specification > - > >

[jira] Commented: (CONTINUUM-1568) Release fails hard in prepare-release

[ http://jira.codehaus.org/browse/CONTINUUM-1568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_116339 ] Magnus Sandberg commented on CONTINUUM-1568: I will test as soon as I get some time to install final, if I re

[jira] Updated: (MJAR-71) use manifest in classesdir/META-INF if exists

[ http://jira.codehaus.org/browse/MJAR-71?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jerome Lacoste updated MJAR-71: --- Attachment: MJAR-71-disabled_by_default.diff Here's a tentative fix for the issue. I've made 2 versions, one w

[jira] Updated: (MJAR-71) use manifest in classesdir/META-INF if exists

[ http://jira.codehaus.org/browse/MJAR-71?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jerome Lacoste updated MJAR-71: --- Attachment: MJAR-71-enabled_by_default.diff > use manifest in classesdir/META-INF if exists >

[jira] Commented: (MJAR-71) use manifest in classesdir/META-INF if exists

[ http://jira.codehaus.org/browse/MJAR-71?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_116342 ] Jerome Lacoste commented on MJAR-71: Please comment on the approach and the parameters. I can provide documentation later o

[jira] Commented: (MJAR-82) Class-Path manifest entry should support maven repository layout

[ http://jira.codehaus.org/browse/MJAR-82?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_116343 ] Jerome Lacoste commented on MJAR-82: This one requires changes in the archiver, so fixing it would require releasing other

[jira] Created: (CONTINUUM-1596) The release perform doesn't work when a scm password is required

The release perform doesn't work when a scm password is required Key: CONTINUUM-1596 URL: http://jira.codehaus.org/browse/CONTINUUM-1596 Project: Continuum Issue Type: Bug

[jira] Updated: (CONTINUUM-567) A build must be launched if we have changes since last build (for same build definition) and not only if we have detected changes when we run scm update commad

[ http://jira.codehaus.org/browse/CONTINUUM-567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Goeser updated CONTINUUM-567: --- Attachment: continuum-bug.png I think we got some sort of a regression in 1.1see the attached sc

[jira] Commented: (MRELEASE-201) Deployed POM is not valid XML

[ http://jira.codehaus.org/browse/MRELEASE-201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_116346 ] Benjamin Bentmann commented on MRELEASE-201: Another encoding problem: The plugin (2.0-beta-7) does not output

[jira] Updated: (MECLIPSE-333) WTP-2.0 support with howto apt, refactoring and contextroot handling

[ http://jira.codehaus.org/browse/MECLIPSE-333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Zeltner updated MECLIPSE-333: Attachment: Eclipse-3.3.0-about.png Eclipse-3.3.0-project-upgrade.png I'm worki

[jira] Commented: (MJAR-53) In pom with packaging "war" the generated jar will be installed in repo instead of the war

[ http://jira.codehaus.org/browse/MJAR-53?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_116348 ] Joerg Schaible commented on MJAR-53: This is more or less the functionality of MWAR-33. > In pom with packaging "war" the g

[jira] Commented: (MEAR-43) add ability to do filtering (i.e. template var replacement) for files in src/main/application/

[ http://jira.codehaus.org/browse/MEAR-43?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_116349 ] Holger Stolzenberg commented on MEAR-43: Can somehow please provide a simple example of how to filter application.xml w

[jira] Commented: (MECLIPSE-333) WTP-2.0 support with howto apt, refactoring and contextroot handling

[ http://jira.codehaus.org/browse/MECLIPSE-333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_116350 ] Richard van Nieuwenhoven commented on MECLIPSE-333: --- please specify the parameters do you give eclipse:ec

[jira] Commented: (MJAR-53) In pom with packaging "war" the generated jar will be installed in repo instead of the war

[ http://jira.codehaus.org/browse/MJAR-53?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_116351 ] Martin Zeltner commented on MJAR-53: No. The MWAR-33 concerns about dependency version mixup. But this issue is used to cre

[jira] Commented: (MECLIPSE-344) connecting existing workspace artifact-projects

[ http://jira.codehaus.org/browse/MECLIPSE-344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_116352 ] Richard van Nieuwenhoven commented on MECLIPSE-344: --- this part of file format did not change since 2.0 an

[jira] Commented: (MJAR-53) In pom with packaging "war" the generated jar will be installed in repo instead of the war

[ http://jira.codehaus.org/browse/MJAR-53?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_116353 ] Joerg Schaible commented on MJAR-53: You should have read all comments to that issue ;-) > In pom with packaging "war" the

[jira] Commented: (MJAR-53) In pom with packaging "war" the generated jar will be installed in repo instead of the war

[ http://jira.codehaus.org/browse/MJAR-53?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_116354 ] Martin Zeltner commented on MJAR-53: I've read all comment but can not like these two issues. Example: I have a war artifac

[jira] Created: (MRM-624) Failed to install Archiva as windows service

Failed to install Archiva as windows service Key: MRM-624 URL: http://jira.codehaus.org/browse/MRM-624 Project: Archiva Issue Type: Bug Affects Versions: 1.0 Environment: Win XP/ JDK:

[jira] Created: (CONTINUUM-1598) upgrade from 1.0.3 to 1.1: data-management-cli crashes

upgrade from 1.0.3 to 1.1: data-management-cli crashes -- Key: CONTINUUM-1598 URL: http://jira.codehaus.org/browse/CONTINUUM-1598 Project: Continuum Issue Type: Bug Components: Da

[jira] Commented: (MRESOURCES-43) resources:resources overwrites destination files when filtering is on, not when filtering is off

[ http://jira.codehaus.org/browse/MRESOURCES-43?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_116355 ] Bart Robeyns commented on MRESOURCES-43: I've created a patch that allows you to set a 'forceWrite'-flag on the r

[jira] Commented: (MJAR-53) In pom with packaging "war" the generated jar will be installed in repo instead of the war

[ http://jira.codehaus.org/browse/MJAR-53?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_116356 ] Joerg Schaible commented on MJAR-53: The proposed solution at the end is that "mvn install" creates a war that does not inc

[jira] Moved: (DOXIASITETOOLS-7) site.xml attribute no more working

[ http://jira.codehaus.org/browse/DOXIASITETOOLS-7?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Theussl moved MSITE-278 to DOXIASITETOOLS-7: -- Affects Version/s: (was: 2.0-beta-7)

[jira] Updated: (DOXIASITETOOLS-7) site.xml attribute no more working

[ http://jira.codehaus.org/browse/DOXIASITETOOLS-7?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Theussl updated DOXIASITETOOLS-7: --- Component/s: Decoration model This has to be added in the doxia decoration model firs

[jira] Commented: (MEAR-43) add ability to do filtering (i.e. template var replacement) for files in src/main/application/

[ http://jira.codehaus.org/browse/MEAR-43?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_116366 ] Ian Springer commented on MEAR-43: -- Here's an example: 1) In your pom, add: [...] src/main/resources

[jira] Created: (CONTINUUM-1599) Migration tool for continuum 1.0.3

Migration tool for continuum 1.0.3 -- Key: CONTINUUM-1599 URL: http://jira.codehaus.org/browse/CONTINUUM-1599 Project: Continuum Issue Type: Bug Components: Data Management Affects Versions: 1.1

[jira] Created: (CONTINUUM-1600) there is no function that returns a WorkingDirectory path

there is no function that returns a WorkingDirectory path - Key: CONTINUUM-1600 URL: http://jira.codehaus.org/browse/CONTINUUM-1600 Project: Continuum Issue Type: New Feature Affect

[jira] Created: (MNG-3315) Path normalization during inheritance prohibits usage of properties

Path normalization during inheritance prohibits usage of properties --- Key: MNG-3315 URL: http://jira.codehaus.org/browse/MNG-3315 Project: Maven 2 Issue Type: Bug Co

[jira] Commented: (MRELEASE-201) Deployed POM is not valid XML

[ http://jira.codehaus.org/browse/MRELEASE-201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_116377 ] Nathan Beyer (Cerner) commented on MRELEASE-201: +1 for ALWAYS including an XML prolog that includes the en

[jira] Updated: (MNG-3315) Path normalization during inheritance prohibits usage of properties

[ http://jira.codehaus.org/browse/MNG-3315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann updated MNG-3315: --- Attachment: project.zip This dummy projects demonstrates the issue. Just run "mvn site" and look at t

[jira] Closed: (SUREFIRE-393) Measure test coverage for surefire, including ITs

[ http://jira.codehaus.org/browse/SUREFIRE-393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich closed SUREFIRE-393. - Resolution: Fixed Fix Version/s: (was: 2.4) Measured coverage by hand; results available h

[jira] Closed: (SUREFIRE-50) write comprehensive tests for surefire

[ http://jira.codehaus.org/browse/SUREFIRE-50?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich closed SUREFIRE-50. Resolution: Fixed Coverage is now at 79.4%. > write comprehensive tests for surefire >

[jira] Closed: (SUREFIRE-158) Web site has incorrect source repository information

[ http://jira.codehaus.org/browse/SUREFIRE-158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich closed SUREFIRE-158. - Resolution: Fixed This is fixed in the trunk code; it will be resolved when the website is updated a

[jira] Created: (MDEP-124) Dependency incorrectly reported as "Unused declared"

Dependency incorrectly reported as "Unused declared" Key: MDEP-124 URL: http://jira.codehaus.org/browse/MDEP-124 Project: Maven 2.x Dependency Plugin Issue Type: Bug Components:

[jira] Commented: (SUREFIRE-394) Resolve snapshot dependencies in Surefire 2.4

[ http://jira.codehaus.org/browse/SUREFIRE-394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_116389 ] Olivier Lamy commented on SUREFIRE-394: --- now we depend on a new version of p-u (1.4.9-SNAPSHOT). > Resolve snapshot

[jira] Closed: (SUREFIRE-403) TestNgPathWithSpaces integration test fails on Unix

[ http://jira.codehaus.org/browse/SUREFIRE-403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed SUREFIRE-403. - Resolution: Fixed upgrade to last p-u SNAPSHOT on rev 602989. > TestNgPathWithSpaces integration tes

[jira] Closed: (SUREFIRE-404) Set testFailureIgnore=false on surefire-integration-tests

[ http://jira.codehaus.org/browse/SUREFIRE-404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich closed SUREFIRE-404. - Resolution: Fixed Fix Version/s: (was: 2.4) Fixed in revision 603004. > Set testFailureIg

[jira] Created: (ARCHETYPE-113) examples/webapp.html documentation is incorrect

examples/webapp.html documentation is incorrect - Key: ARCHETYPE-113 URL: http://jira.codehaus.org/browse/ARCHETYPE-113 Project: Maven Archetype Issue Type: Bug Reporter: Scott Cy

[jira] Updated: (MANTTASKS-91) [task dependencies]Trouble between mvn and manttasks

[ http://jira.codehaus.org/browse/MANTTASKS-91?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MANTTASKS-91: --- Fix Version/s: (was: 2.0.8) > [task dependencies]Trouble between mvn and manttasks >

[jira] Reopened: (MANTTASKS-91) [task dependencies]Trouble between mvn and manttasks

[ http://jira.codehaus.org/browse/MANTTASKS-91?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy reopened MANTTASKS-91: had to revert ProfileManager use since it breaks dependencies order when read pom.xml > [task dep

[jira] Updated: (MRELEASE-294) Generated release-pom.xml does not contain plugins configured in a super pom.

[ http://jira.codehaus.org/browse/MRELEASE-294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Rankin updated MRELEASE-294: -- Attachment: patch.txt > Generated release-pom.xml does not contain plugins configured in a super po

[jira] Commented: (MRELEASE-294) Generated release-pom.xml does not contain plugins configured in a super pom.

[ http://jira.codehaus.org/browse/MRELEASE-294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_116416 ] Scott Rankin commented on MRELEASE-294: --- I've encountered the same problem. It's because in the GenerateReleasePoms

[jira] Commented: (MJAR-53) In pom with packaging "war" the generated jar will be installed in repo instead of the war

[ http://jira.codehaus.org/browse/MJAR-53?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_116417 ] Dennis Lundberg commented on MJAR-53: - Martin, do you mean that you are no longer in need of a fix for this issue? It sound

[jira] Created: (MAVENUPLOAD-1845) Upload Objenesis 1.1 and parent pom

Upload Objenesis 1.1 and parent pom --- Key: MAVENUPLOAD-1845 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1845 Project: maven-upload-requests Issue Type: Task Reporter: Henri Tremblay

[jira] Created: (SUREFIRE-405) Make useSystemClassLoader the default

Make useSystemClassLoader the default - Key: SUREFIRE-405 URL: http://jira.codehaus.org/browse/SUREFIRE-405 Project: Maven Surefire Issue Type: Improvement Affects Versions: 2.4 Reporter: D

[jira] Commented: (MINVOKER-14) release maven-invoker

[ http://jira.codehaus.org/browse/MINVOKER-14?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_116431 ] John Allen commented on MINVOKER-14: would allow us to drop local corporate version +1 > release maven-invoker > --

[jira] Closed: (SUREFIRE-405) Make useSystemClassLoader the default

[ http://jira.codehaus.org/browse/SUREFIRE-405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich closed SUREFIRE-405. - Resolution: Fixed Fixed in revision 603083. > Make useSystemClassLoader the default > --

[jira] Created: (SUREFIRE-406) Can't use -Dtest from root in a reactor build

Can't use -Dtest from root in a reactor build - Key: SUREFIRE-406 URL: http://jira.codehaus.org/browse/SUREFIRE-406 Project: Maven Surefire Issue Type: Bug Affects Versions: 2.4 Rep

[jira] Updated: (SUREFIRE-406) Can't use -Dtest from root in a reactor build

[ http://jira.codehaus.org/browse/SUREFIRE-406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich updated SUREFIRE-406: -- Fix Version/s: 2.x > Can't use -Dtest from root in a reactor build > --

[jira] Commented: (SUREFIRE-381) TestNG Reporter.log() calls don't show up in any reports

[ http://jira.codehaus.org/browse/SUREFIRE-381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_116434 ] Dan Fabulich commented on SUREFIRE-381: --- Now we let testng generate its own XML. It still doesn't appear in any HTML

[jira] Closed: (SUREFIRE-94) Implement getTestCount for TestNG

[ http://jira.codehaus.org/browse/SUREFIRE-94?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich closed SUREFIRE-94. Resolution: Won't Fix Fix Version/s: (was: 2.x) getTestCount has been deleted > Implement ge

[jira] Commented: (MJAR-71) use manifest in classesdir/META-INF if exists

[ http://jira.codehaus.org/browse/MJAR-71?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_116438 ] Olivier Lamy commented on MJAR-71: -- Thanks for patch but I'm not sure adding a new parameter to set the default manifest file

[jira] Closed: (MJAR-71) use manifest in classesdir/META-INF if exists

[ http://jira.codehaus.org/browse/MJAR-71?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed MJAR-71. Assignee: Olivier Lamy Resolution: Fixed committed in rev 603097/603098. > use manifest in classesdir/META-IN

[jira] Commented: (MJAR-49) Jarsigner fails on windows due to spaces in pathnames

[ http://jira.codehaus.org/browse/MJAR-49?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_116440 ] Olivier Lamy commented on MJAR-49: -- I have updated plexus-utils dependency version to last SNAPSHOT (see PLXUTILS-54) which sh

[jira] Created: (SUREFIRE-407) maven-invoker tests failed with surefire snapshot 2.4-20071210.231259-24

maven-invoker tests failed with surefire snapshot 2.4-20071210.231259-24 Key: SUREFIRE-407 URL: http://jira.codehaus.org/browse/SUREFIRE-407 Project: Maven Surefire Iss

[jira] Closed: (NMAVEN-94) Archetypes packaging changed to 'jar'

[ http://jira.codehaus.org/browse/NMAVEN-94?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed NMAVEN-94. -- Assignee: Brett Porter Resolution: Fixed Fix Version/s: 0.14 > Archetypes packaging changed to

[jira] Closed: (NMAVEN-95) artifacts in the GAC should be deployed to the repository with their public token key id

[ http://jira.codehaus.org/browse/NMAVEN-95?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed NMAVEN-95. -- Assignee: Brett Porter Resolution: Fixed Fix Version/s: 0.14 > artifacts in the GAC should be

[jira] Created: (NMAVEN-95) artifacts in the GAC should be deployed to the repository with their public token key id

artifacts in the GAC should be deployed to the repository with their public token key id Key: NMAVEN-95 URL: http://jira.codehaus.org/browse/NMAVEN-95 Project: N

[jira] Closed: (NMAVEN-96) repository builder fails to create missing directories in the local repository

[ http://jira.codehaus.org/browse/NMAVEN-96?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed NMAVEN-96. -- Resolution: Fixed Fix Version/s: 0.14 > repository builder fails to create missing directories in the l

[jira] Created: (NMAVEN-96) repository builder fails to create missing directories in the local repository

repository builder fails to create missing directories in the local repository -- Key: NMAVEN-96 URL: http://jira.codehaus.org/browse/NMAVEN-96 Project: NMaven Issue

[jira] Commented: (NMAVEN-95) artifacts in the GAC should be deployed to the repository with their public token key id

[ http://jira.codehaus.org/browse/NMAVEN-95?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_116451 ] Shane Isbell commented on NMAVEN-95: I took a look at the check in. I think that it will get things working but we should

[jira] Commented: (NMAVEN-95) artifacts in the GAC should be deployed to the repository with their public token key id

[ http://jira.codehaus.org/browse/NMAVEN-95?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_116452 ] Brett Porter commented on NMAVEN-95: I can open a new issue for that - is that the case with the 0.14 code though, or onl

[jira] Commented: (NMAVEN-95) artifacts in the GAC should be deployed to the repository with their public token key id

[ http://jira.codehaus.org/browse/NMAVEN-95?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_116454 ] Shane Isbell commented on NMAVEN-95: The standard deploy plugin works since the introduction of the RDF repo (trunk revis

[jira] Created: (NMAVEN-97) remove the alternative deploy plugin and change the lifecycle to use the standard one

remove the alternative deploy plugin and change the lifecycle to use the standard one - Key: NMAVEN-97 URL: http://jira.codehaus.org/browse/NMAVEN-97 Project: NMaven

[jira] Created: (WAGON-93) Cannot deploy with using webdav: 409 error

Cannot deploy with using webdav: 409 error -- Key: WAGON-93 URL: http://jira.codehaus.org/browse/WAGON-93 Project: wagon Issue Type: Bug Components: wagon-webdav Affects Versions: 1.0-bet

[jira] Commented: (MJAR-53) In pom with packaging "war" the generated jar will be installed in repo instead of the war

[ http://jira.codehaus.org/browse/MJAR-53?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_116458 ] Martin Zeltner commented on MJAR-53: We can close this issue. I do not need this fix anymore. > In pom with packaging "war"

[jira] Closed: (MSHADE-6) Replacement failures should halt the build

[ http://jira.codehaus.org/browse/MSHADE-6?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich closed MSHADE-6. - Resolution: Fixed Fix Version/s: 1.0-alpha-14 Fixed in revision 603163. > Replacement failures should hal

[jira] Reopened: (MSHADE-5) 50% of the time I run the shade plugin, it's unable to replace the original jar

[ http://jira.codehaus.org/browse/MSHADE-5?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich reopened MSHADE-5: --- Actually, it seems that it just made the issue much more rare. Unfortunately, it stung me just as I went to dep

[jira] Updated: (MSHADE-5) 5% of the time I run the shade plugin, it's unable to replace the original jar

[ http://jira.codehaus.org/browse/MSHADE-5?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich updated MSHADE-5: -- Priority: Major (was: Blocker) > 5% of the time I run the shade plugin, it's unable to replace the original ja

[jira] Updated: (MSHADE-5) 5% of the time I run the shade plugin, it's unable to replace the original jar

[ http://jira.codehaus.org/browse/MSHADE-5?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich updated MSHADE-5: -- Summary: 5% of the time I run the shade plugin, it's unable to replace the original jar (was: 50% of the time

[jira] Updated: (MSHADE-5) Whenever I do a deploy and run the shade plugin, it's unable to replace the original jar

[ http://jira.codehaus.org/browse/MSHADE-5?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich updated MSHADE-5: -- Priority: Blocker (was: Major) Summary: Whenever I do a deploy and run the shade plugin, it's unable to r