[jira] Commented: (MSHADE-59) XmlAppendingTransformer fails when running behind a firewall

[ http://jira.codehaus.org/browse/MSHADE-59?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=185332#action_185332 ] Yuri Schimke commented on MSHADE-59: BTW the workaround we are using, is just to specify the proxy

[jira] Created: (MSHADE-59) XmlAppendingTransformer fails when running behind a firewall

XmlAppendingTransformer fails when running behind a firewall Key: MSHADE-59 URL: http://jira.codehaus.org/browse/MSHADE-59 Project: Maven 2.x Shade Plugin Issue Type: Bug

[jira] Commented: (MECLIPSE-407) EclipsePlugin parameter to skip dependency resolution

[ http://jira.codehaus.org/browse/MECLIPSE-407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=132572#action_132572 ] Yuri Schimke commented on MECLIPSE-407: --- Because we want PDE dependencies in the Eclipse, we

[jira] Commented: (MECLIPSE-407) EclipsePlugin parameter to skip dependency resolution

[ http://jira.codehaus.org/browse/MECLIPSE-407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_127905 ] Yuri Schimke commented on MECLIPSE-407: --- If there are other ways of achieving this then please let us know. BTW we a

[jira] Created: (MECLIPSE-407) EclipsePlugin parameter to skip dependency resolution

EclipsePlugin parameter to skip dependency resolution - Key: MECLIPSE-407 URL: http://jira.codehaus.org/browse/MECLIPSE-407 Project: Maven 2.x Eclipse Plugin Issue Type: Improvement

[jira] Commented: (MNG-1412) dependency sorting in classpath

[ http://jira.codehaus.org/browse/MNG-1412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_117661 ] Yuri Schimke commented on MNG-1412: --- Yes you are probably right, its mainly architectural issues i.e. patch jars. But fixin

[jira] Created: (SUREFIRE-410) Surefire swallows serious errors in fork mode "once"

Surefire swallows serious errors in fork mode "once" Key: SUREFIRE-410 URL: http://jira.codehaus.org/browse/SUREFIRE-410 Project: Maven Surefire Issue Type: Bug Components: class

[jira] Created: (MRM-618) PLEXUS_BASE does not work for local databases

PLEXUS_BASE does not work for local databases - Key: MRM-618 URL: http://jira.codehaus.org/browse/MRM-618 Project: Archiva Issue Type: Bug Components: system Affects Versions: 1.0

[jira] Created: (MRM-581) Proxied Repository causes Snapshot plugins to be selected

Proxied Repository causes Snapshot plugins to be selected - Key: MRM-581 URL: http://jira.codehaus.org/browse/MRM-581 Project: Archiva Issue Type: Bug Affects Versions: 1.0-beta-3

[jira] Created: (MNG-3275) Maven 2.0.6 pom missing from ibiblio

Maven 2.0.6 pom missing from ibiblio Key: MNG-3275 URL: http://jira.codehaus.org/browse/MNG-3275 Project: Maven 2 Issue Type: Bug Components: Artifacts and Repositories Reporter: Yur

[jira] Closed: (MECLIPSE-283) Can't set ProjectNatures and BuildCommands for a Multi Module Build

[ http://jira.codehaus.org/browse/MECLIPSE-283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yuri Schimke closed MECLIPSE-283. - Resolution: Fixed Fix Version/s: 2.3 OK I worked it out, while I need to define the defaults i

[jira] Created: (MECLIPSE-283) Can't set ProjectNatures and BuildCommands for a Multi Module Build

Can't set ProjectNatures and BuildCommands for a Multi Module Build --- Key: MECLIPSE-283 URL: http://jira.codehaus.org/browse/MECLIPSE-283 Project: Maven 2.x Eclipse Plugin Iss

[jira] Commented: (MNG-2917) Ant classpath issue in maven 2.0.6

[ http://jira.codehaus.org/browse/MNG-2917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_92135 ] Yuri Schimke commented on MNG-2917: --- This seems like the most appropriate solution http://www.nabble.com/Re%3A-maven-2.0.6-an

[jira] Closed: (MNG-2917) Ant classpath issue in maven 2.0.6

[ http://jira.codehaus.org/browse/MNG-2917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yuri Schimke closed MNG-2917. - Resolution: Incomplete I'm closing this one because after making some cleanups of our POMs etc, the issue has go

[jira] Created: (MNG-2917) Ant classpath issue in maven 2.0.6

Ant classpath issue in maven 2.0.6 -- Key: MNG-2917 URL: http://jira.codehaus.org/browse/MNG-2917 Project: Maven 2 Issue Type: Bug Affects Versions: 2.0.6 Reporter: Yuri Schimke Pri

[jira] Created: (MJAR-68) multi module release fails because of test-jar

multi module release fails because of test-jar -- Key: MJAR-68 URL: http://jira.codehaus.org/browse/MJAR-68 Project: Maven 2.x Jar Plugin Issue Type: Bug Affects Versions: 2.1 Environm

[jira] Created: (MDEP-56) test-jar

test-jar Key: MDEP-56 URL: http://jira.codehaus.org/browse/MDEP-56 Project: Maven 2.x Dependency Plugin Issue Type: Bug Affects Versions: 2.0-alpha-1 Reporter: Yuri Schimke Assigned To: Brian Fox For the f

[jira] Commented: (MNGECLIPSE-203) Maven Eclipse Plugin fails to read POM while command line works

[ http://jira.codehaus.org/browse/MNGECLIPSE-203?page=comments#action_78818 ] Yuri Schimke commented on MNGECLIPSE-203: - No problem. We get errors similar to this occasionally. Some combination of Full clean rebuilds, Eclipse refreshes

[jira] Created: (MNGECLIPSE-203) Maven Eclipse Plugin fails to read POM while command line works

Maven Eclipse Plugin fails to read POM while command line works --- Key: MNGECLIPSE-203 URL: http://jira.codehaus.org/browse/MNGECLIPSE-203 Project: Maven 2.x Extension for Eclipse

[jira] Created: (MNGECLIPSE-200) Maven Enabled Projects should have target directory marked as derived

Maven Enabled Projects should have target directory marked as derived - Key: MNGECLIPSE-200 URL: http://jira.codehaus.org/browse/MNGECLIPSE-200 Project: Maven 2.x Extension for Eclips

[jira] Commented: (MNGECLIPSE-59) Allow artifact resolution from workspace projects

[ http://jira.codehaus.org/browse/MNGECLIPSE-59?page=comments#action_72477 ] Yuri Schimke commented on MNGECLIPSE-59: Eugene, We've got a multimodule maven project. I've tried both approaches, i.e. seperate eclipse projects and a single

[jira] Commented: (SCM-227) Document use cases for maven-scm-plugin

[ http://jira.codehaus.org/browse/SCM-227?page=comments#action_72380 ] Yuri Schimke commented on SCM-227: -- Hey, this might be largely from unrealistic expectations from my part. I was expecting scm:checkout to immediately give you a valid proj

[jira] Created: (SCM-227) Document use cases for maven-scm-plugin

Document use cases for maven-scm-plugin --- Key: SCM-227 URL: http://jira.codehaus.org/browse/SCM-227 Project: Maven SCM Issue Type: Improvement Components: maven-plugin Affects Versions: 1.0

[jira] Commented: (SCM-221) scm:update has no effect

[ http://jira.codehaus.org/browse/SCM-221?page=comments#action_72365 ] Yuri Schimke commented on SCM-221: -- We are avoiding using scm:update in the cruisecontrol project config. Its easy enough to use the cruisecontrol options, and probably safe

[jira] Commented: (WAGON-60) wagon-webdav fails with commons-logging classloader issues

[ http://jira.codehaus.org/browse/WAGON-60?page=comments#action_72332 ] Yuri Schimke commented on WAGON-60: --- I deleted ~/.m2/repository and tried it again, its now working. I guess I had a bad jar, or possibly one of the snapshots I had built

[jira] Commented: (MRELEASE-150) Can't add prefix to tags without affecting version

[ http://jira.codehaus.org/browse/MRELEASE-150?page=comments#action_72321 ] Yuri Schimke commented on MRELEASE-150: --- Just realised, the default is obviously null, so that it prompts you to enter the label. So its actually set at a point

[jira] Commented: (SCM-226) Optionally lock perforce labels

[ http://jira.codehaus.org/browse/SCM-226?page=comments#action_72311 ] Yuri Schimke commented on SCM-226: -- I realise > Optionally lock perforce labels > --- > > Key: SCM-226 > URL:

[jira] Commented: (SCM-226) Optionally lock perforce labels

[ http://jira.codehaus.org/browse/SCM-226?page=comments#action_72310 ] Yuri Schimke commented on SCM-226: -- Is there an easy way to integrate this with the release plugin? A system property seems fine for using the scm plugin directly. but when

[jira] Created: (MRELEASE-150) Can't add prefix to tags without affecting version

Can't add prefix to tags without affecting version -- Key: MRELEASE-150 URL: http://jira.codehaus.org/browse/MRELEASE-150 Project: Maven 2.x Release Plugin Issue Type: Bug Affects Versions:

[jira] Created: (MRELEASE-149) Optionally lock perforce labels

Optionally lock perforce labels --- Key: MRELEASE-149 URL: http://jira.codehaus.org/browse/MRELEASE-149 Project: Maven 2.x Release Plugin Issue Type: Improvement Affects Versions: 2.0-beta-4 Report

[jira] Commented: (WAGON-60) wagon-webdav fails with commons-logging classloader issues

[ http://jira.codehaus.org/browse/WAGON-60?page=comments#action_72249 ] Yuri Schimke commented on WAGON-60: --- I'm assuming its because there are two copies of commons-logging loaded by different extensions or plugins. Is there somewhere I can p

[jira] Created: (WAGON-60) wagon-webdav fails with commons-logging classloader issues

wagon-webdav fails with commons-logging classloader issues -- Key: WAGON-60 URL: http://jira.codehaus.org/browse/WAGON-60 Project: wagon Issue Type: Bug Components: wagon-webd

[jira] Closed: (MNGECLIPSE-172) Eclipse PDE seems slightly incompatible with plugin

[ http://jira.codehaus.org/browse/MNGECLIPSE-172?page=all ] Yuri Schimke closed MNGECLIPSE-172. --- Resolution: Duplicate duplicate of MNGECLIPSE-106 > Eclipse PDE seems slightly incompatible with plugin >

[jira] Created: (MNGECLIPSE-172) Eclipse PDE seems slightly incompatible with plugin

Eclipse PDE seems slightly incompatible with plugin --- Key: MNGECLIPSE-172 URL: http://jira.codehaus.org/browse/MNGECLIPSE-172 Project: Maven 2.x Extension for Eclipse Issue Type: Improvement

[jira] Commented: (SCM-221) scm:update has no effect

[ http://jira.codehaus.org/browse/SCM-221?page=comments#action_70088 ] Yuri Schimke commented on SCM-221: -- is maven.scm.persistcheckout the system property to use the existing p4 clientspec > scm:update has no effect >

[jira] Commented: (SCM-221) scm:update has no effect

[ http://jira.codehaus.org/browse/SCM-221?page=comments#action_70087 ] Yuri Schimke commented on SCM-221: -- We are trying to use the perforce support for three things. 1) scm:update in cruisecontrol - must use existing clientspec 2) maven-chang

[jira] Created: (SCM-221) scm:update has no effect

scm:update has no effect Key: SCM-221 URL: http://jira.codehaus.org/browse/SCM-221 Project: Maven SCM Issue Type: Bug Components: maven-scm-provider-perforce Affects Versions: 1.0 Environment:

[jira] Commented: (MNGECLIPSE-59) Allow artifact resolution from workspace projects

[ http://jira.codehaus.org/browse/MNGECLIPSE-59?page=comments#action_69483 ] Yuri Schimke commented on MNGECLIPSE-59: False alarm. Was actually to do with some of my eclipse source paths being out of date. Just something to watch out for when you

[jira] Commented: (MNGECLIPSE-59) Allow artifact resolution from workspace projects

[ http://jira.codehaus.org/browse/MNGECLIPSE-59?page=comments#action_69440 ] Yuri Schimke commented on MNGECLIPSE-59: The patch fixes a number of issues that I had reported in MNGECLIPSE-147, however it does not seem to find resources, only the actu

[jira] Created: (MNGECLIPSE-147) Problem with Eclipse Project Dependencies

Problem with Eclipse Project Dependencies - Key: MNGECLIPSE-147 URL: http://jira.codehaus.org/browse/MNGECLIPSE-147 Project: Maven 2.x Extension for Eclipse Type: Bug Versions: 0.0.9 Reporter: Yuri Schimke Assigne