[jira] Updated: (MNGECLIPSE-114) cannot run junit testcases from within Eclipse

[ http://jira.codehaus.org/browse/MNGECLIPSE-114?page=all ] Torsten Curdt updated MNGECLIPSE-114: - Attachment: commons-jci.tgz > cannot run junit testcases from within Eclipse > -- > > Key: MNGECLI

[jira] Commented: (MNG-2257) Failed to parse pom.xml when set to 1.5 source and target

[ http://jira.codehaus.org/browse/MNG-2257?page=comments#action_64420 ] Wayne Fay commented on MNG-2257: This is just a bad pom. You're missing a node inside the node to contain the artifactId, configuration, etc nodes. > Failed to parse pom.xml when set

[jira] Commented: (MNG-2257) Failed to parse pom.xml when set to 1.5 source and target

[ http://jira.codehaus.org/browse/MNG-2257?page=comments#action_64421 ] Wendy Smoak commented on MNG-2257: -- This probably would have been better directed to the user list than the issue tracker. The reason for the failure is that the (singular) element fo

[jira] Commented: (MNGECLIPSE-114) cannot run junit testcases from within Eclipse

[ http://jira.codehaus.org/browse/MNGECLIPSE-114?page=comments#action_64419 ] Eugene Kuleshov commented on MNGECLIPSE-114: What can I say. You'll have to show me your eclipse projects. Try to zip them up, but make sure they are in the archive (e

[jira] Commented: (MNG-2257) Failed to parse pom.xml when set to 1.5 source and target

[ http://jira.codehaus.org/browse/MNG-2257?page=comments#action_64418 ] Hanson Char commented on MNG-2257: -- The mvn.log was generated when I typed: mvn compile | tee mvn.log > Failed to parse pom.xml when set to 1.5 source and target > --

[jira] Created: (MNG-2257) Failed to parse pom.xml when set to 1.5 source and target

Failed to parse pom.xml when set to 1.5 source and target - Key: MNG-2257 URL: http://jira.codehaus.org/browse/MNG-2257 Project: Maven 2 Type: Bug Components: POM Versions: 2.0.4 Environment: java

[jira] Commented: (MNGECLIPSE-114) cannot run junit testcases from within Eclipse

[ http://jira.codehaus.org/browse/MNGECLIPSE-114?page=comments#action_64417 ] Torsten Curdt commented on MNGECLIPSE-114: -- >From the command line test are running fine for me as well. Started with a fresh launch config and this is what gets called:

[jira] Commented: (MNGECLIPSE-114) cannot run junit testcases from within Eclipse

[ http://jira.codehaus.org/browse/MNGECLIPSE-114?page=comments#action_64416 ] Eugene Kuleshov commented on MNGECLIPSE-114: Apparently your attachment haven't had any code. So, I checked out project from SVN and were able to run some tests. It wo

[jira] Updated: (MNGECLIPSE-114) cannot run junit testcases from within Eclipse

[ http://jira.codehaus.org/browse/MNGECLIPSE-114?page=all ] Eugene Kuleshov updated MNGECLIPSE-114: --- Attachment: (was: workspace.tgz) > cannot run junit testcases from within Eclipse > -- > >

[jira] Updated: (MNGECLIPSE-114) cannot run junit testcases from within Eclipse

[ http://jira.codehaus.org/browse/MNGECLIPSE-114?page=all ] Eugene Kuleshov updated MNGECLIPSE-114: --- Attachment: (was: tests.tgz) > cannot run junit testcases from within Eclipse > -- > > Key

[jira] Updated: (MNGECLIPSE-114) cannot run junit testcases from within Eclipse

[ http://jira.codehaus.org/browse/MNGECLIPSE-114?page=all ] Torsten Curdt updated MNGECLIPSE-114: - Attachment: run.png > cannot run junit testcases from within Eclipse > -- > > Key: MNGECLIPSE-114

[jira] Updated: (MNGECLIPSE-114) cannot run junit testcases from within Eclipse

[ http://jira.codehaus.org/browse/MNGECLIPSE-114?page=all ] Torsten Curdt updated MNGECLIPSE-114: - Attachment: eclipse.png > cannot run junit testcases from within Eclipse > -- > > Key: MNGECLIPSE-

[jira] Commented: (MNGECLIPSE-114) cannot run junit testcases from within Eclipse

[ http://jira.codehaus.org/browse/MNGECLIPSE-114?page=comments#action_64414 ] Eugene Kuleshov commented on MNGECLIPSE-114: Ok, great. But how are you running this stuff? And just in case, what Eclipse version you are running? And on what JRE? >

[jira] Updated: (MNGECLIPSE-114) cannot run junit testcases from within Eclipse

[ http://jira.codehaus.org/browse/MNGECLIPSE-114?page=all ] Torsten Curdt updated MNGECLIPSE-114: - Attachment: tests.tgz workspace.tgz > cannot run junit testcases from within Eclipse > -- >

[jira] Commented: (MNGECLIPSE-114) cannot run junit testcases from within Eclipse

[ http://jira.codehaus.org/browse/MNGECLIPSE-114?page=comments#action_64411 ] Eugene Kuleshov commented on MNGECLIPSE-114: Torsten, would you mind to attach your Eclipse project here (or something we can test with) and provide step by step instr

[jira] Created: (MNGECLIPSE-114) cannot run junit testcases from within Eclipse

cannot run junit testcases from within Eclipse -- Key: MNGECLIPSE-114 URL: http://jira.codehaus.org/browse/MNGECLIPSE-114 Project: Maven 2.x Extension for Eclipse Type: Bug Environment: OSX, Eclipse 3.2RC1 Reporter: T

[jira] Updated: (MCHANGELOG-35) Wrong time format, unable to be parsed by cvs

[ http://jira.codehaus.org/browse/MCHANGELOG-35?page=all ] Carlos Sanchez updated MCHANGELOG-35: - Version: 2.0 Fix Version: 2.0 > Wrong time format, unable to be parsed by cvs > - > > Key:

[jira] Created: (MCHANGELOG-35) Wrong time format, unable to be parsed by cvs

Wrong time format, unable to be parsed by cvs - Key: MCHANGELOG-35 URL: http://jira.codehaus.org/browse/MCHANGELOG-35 Project: Maven 2.x Changelog Plugin Type: Bug Reporter: Carlos Sanchez >From th log [INFO] Execut

[jira] Commented: (MNG-1330) direct support for mock classes

[ http://jira.codehaus.org/browse/MNG-1330?page=comments#action_64410 ] Arik Kfir commented on MNG-1330: I disagree - there are too many source dirs already, and the test-jar works perfectly...no need to complicate things, IMO. > direct support for mock cla

[jira] Created: (MASSEMBLY-89) outputFileNameMapping broken

outputFileNameMapping broken Key: MASSEMBLY-89 URL: http://jira.codehaus.org/browse/MASSEMBLY-89 Project: Maven 2.x Assembly Plugin Type: Bug Versions: 2.1 Reporter: Dan Tran Priority: Critical Fix For: 2.1 Prior t

[jira] Updated: (MASSEMBLY-89) outputFileNameMapping broken

[ http://jira.codehaus.org/browse/MASSEMBLY-89?page=all ] Dan Tran updated MASSEMBLY-89: -- Fix Version: 2.1 Environment: xp > outputFileNameMapping broken > > > Key: MASSEMBLY-89 > URL: http://jira.codehaus.

[jira] Commented: (MNG-624) automatic parent versioning

[ http://jira.codehaus.org/browse/MNG-624?page=comments#action_64409 ] Arik Kfir commented on MNG-624: --- two more cents: imo the algoritm should do the following: (in specified order) 1. if a version is given, resolve it from reactor/repository 2. otherwise, if

[jira] Closed: (SUREFIRE-37) System properties not working during forking [surefire-testng branch, patch attached]

[ http://jira.codehaus.org/browse/SUREFIRE-37?page=all ] Brett Porter closed SUREFIRE-37: Assign To: Brett Porter (was: Jason van Zyl) Resolution: Fixed applied, thanks > System properties not working during forking [surefire-testng branch, p

[jira] Updated: (SUREFIRE-35) refine use of assertion enablement

[ http://jira.codehaus.org/browse/SUREFIRE-35?page=all ] Brett Porter updated SUREFIRE-35: - Fix Version: 2.0 > refine use of assertion enablement > -- > > Key: SUREFIRE-35 > URL: http://jira.codehaus.org/

[jira] Closed: (MSUREFIRE-57) Forking documentation improvement to help with class loader constrainst issues

[ http://jira.codehaus.org/browse/MSUREFIRE-57?page=all ] Brett Porter closed MSUREFIRE-57: - Assign To: Brett Porter Resolution: Fixed Fix Version: 2.1.4 > Forking documentation improvement to help with class loader constrainst issues > -

[jira] Commented: (MJAR-38) Maven Puts Arbitrary Extension Definition in JAR Manifest by Default.

[ http://jira.codehaus.org/browse/MJAR-38?page=comments#action_64393 ] Steven Coco commented on MJAR-38: - I should have marked this as a Blocker since there is no way to prevent Maven from merging these attributes into the final Manifest. I downloaded SVN i

[jira] Commented: (MJAR-39) Maven Sets Manifest Attribute Values to Multi-Line Strings

[ http://jira.codehaus.org/browse/MJAR-39?page=comments#action_64392 ] Steven Coco commented on MJAR-39: - Oops: the first comment I made, which appears redundant with a self-reference, was intended for another issue. Sorry. > Maven Sets Manifest Attribute

[jira] Commented: (MJAR-38) Maven Puts Arbitrary Extension Definition in JAR Manifest by Default.

[ http://jira.codehaus.org/browse/MJAR-38?page=comments#action_64391 ] Steven Coco commented on MJAR-38: - This issue is related to MJAR-39 and MWAR-34 in that since it sets the Specification-Title element by default to the POM's element, it easily can crea

[jira] Commented: (MJAR-39) Maven Sets Manifest Attribute Values to Multi-Line Strings

[ http://jira.codehaus.org/browse/MJAR-39?page=comments#action_64390 ] Steven Coco commented on MJAR-39: - This behavior is also happening in the War creation; and there are even more problems there. I have filed an issue on that: MWAR-34. > Maven Sets Mani

[jira] Created: (MWAR-34) Maven Puts Arbitrary Extension Definition in WAR Manifest by Default.

Maven Puts Arbitrary Extension Definition in WAR Manifest by Default. - Key: MWAR-34 URL: http://jira.codehaus.org/browse/MWAR-34 Project: Maven 2.x War Plugin Type: Bug Environment: Maven version:

[jira] Commented: (MJAR-39) Maven Sets Manifest Attribute Values to Multi-Line Strings

[ http://jira.codehaus.org/browse/MJAR-39?page=comments#action_64389 ] Steven Coco commented on MJAR-39: - This issue is related to MJAR-39 in that since it sets the Specification-Title element by default to the POM's element, it easily can create an invali

[jira] Closed: (MNGECLIPSE-113) M2 Plugin Breaks Content Assist

[ http://jira.codehaus.org/browse/MNGECLIPSE-113?page=all ] Todd Orr closed MNGECLIPSE-113: --- Resolution: Won't Fix > M2 Plugin Breaks Content Assist > --- > > Key: MNGECLIPSE-113 > URL: http://jira.codehau

[jira] Commented: (MNGECLIPSE-113) M2 Plugin Breaks Content Assist

[ http://jira.codehaus.org/browse/MNGECLIPSE-113?page=comments#action_64388 ] Todd Orr commented on MNGECLIPSE-113: - This has been cleared up by changing the vm that eclipse was using in its configuration. The default install of fedora creates a link in

[jira] Commented: (MNGECLIPSE-113) M2 Plugin Breaks Content Assist

[ http://jira.codehaus.org/browse/MNGECLIPSE-113?page=comments#action_64386 ] Eugene Kuleshov commented on MNGECLIPSE-113: I doubt this is a plugin issue, especially because there is no plugin classes in your stack trace. Loking at the stack t

[jira] Created: (MNGECLIPSE-113) M2 Plugin Breaks Content Assist

M2 Plugin Breaks Content Assist --- Key: MNGECLIPSE-113 URL: http://jira.codehaus.org/browse/MNGECLIPSE-113 Project: Maven 2.x Extension for Eclipse Type: Bug Versions: 0.0.5 Environment: Fedora Core 4 JDK 1.5.0_06 Eclipse3.2

[jira] Commented: (MAVENUPLOAD-867) slf4j 1.0 sources

[ http://jira.codehaus.org/browse/MAVENUPLOAD-867?page=comments#action_64385 ] Carlos Sanchez commented on MAVENUPLOAD-867: as it's modification, can you put them in a zip as they'd be in the repo? > slf4j 1.0 sources > - > >

[jira] Created: (MPECLIPSE-117) Add the ability to specify source exclusions

Add the ability to specify source exclusions Key: MPECLIPSE-117 URL: http://jira.codehaus.org/browse/MPECLIPSE-117 Project: maven-eclipse-plugin Type: New Feature Reporter: James Mitchell Priority: Minor Attachme

[jira] Updated: (MDEPLOY-31) deploy-file: Custom description in generated pom

[ http://jira.codehaus.org/browse/MDEPLOY-31?page=all ] Fabian Bauschulte updated MDEPLOY-31: - Attachment: MDEPLOY-31-maven-deploy-plugin.patch > deploy-file: Custom description in generated pom > > >

[jira] Created: (MDEPLOY-31) deploy-file: Custom description in generated pom

deploy-file: Custom description in generated pom Key: MDEPLOY-31 URL: http://jira.codehaus.org/browse/MDEPLOY-31 Project: Maven 2.x Deploy Plugin Type: Improvement Reporter: Fabian Bauschulte It would be very he

[jira] Created: (MAVENUPLOAD-867) slf4j 1.0 sources

slf4j 1.0 sources - Key: MAVENUPLOAD-867 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-867 Project: maven-upload-requests Type: Task Reporter: fabrizio giustina The following bundles contain source jars for the slf4j 1.0 release. Binary jars

[jira] Created: (MAVENUPLOAD-866) UISpec4J is an Open Source functional and/or unit testing library for Swing-based Java applications, built on top of the JUnit test harness.

UISpec4J is an Open Source functional and/or unit testing library for Swing-based Java applications, built on top of the JUnit test harness. Key: M

[jira] Created: (MNG-2256) Misleading documentation regarding configuration of java.utils.Properties

Misleading documentation regarding configuration of java.utils.Properties - Key: MNG-2256 URL: http://jira.codehaus.org/browse/MNG-2256 Project: Maven 2 Type: Bug Components: Documentation: G

[jira] Created: (MNG-2255) Use a external XML Pull parser instead of plexus one

Use a external XML Pull parser instead of plexus one Key: MNG-2255 URL: http://jira.codehaus.org/browse/MNG-2255 Project: Maven 2 Type: Improvement Components: POM Versions: 2.0.4 Reporter: Carlos