[jira] Commented: (DOXIA-60) Use a external XML Pull parser instead of plexus one

[ http://jira.codehaus.org/browse/DOXIA-60?page=comments#action_64371 ] Carlos Sanchez commented on DOXIA-60: - Another nice set of utilities at http://wiki.java.net/bin/view/Javawsxml/StaxUtilsProject The indentator could be used instead of the

[jira] Closed: (MPJALOPY-7) replace textarea dependency by jext

[ http://jira.codehaus.org/browse/MPJALOPY-7?page=all ] Lukas Theussl closed MPJALOPY-7: Resolution: Won't Fix replace textarea dependency by jext --- Key: MPJALOPY-7 URL:

[jira] Closed: (MPJALOPY-10) Jalopy removes import statements

[ http://jira.codehaus.org/browse/MPJALOPY-10?page=all ] Lukas Theussl closed MPJALOPY-10: - Assign To: Lukas Theussl Resolution: Fixed I deployed a new snapshot. Please test. Jalopy removes import statements

[jira] Created: (MNG-2254) the encoding parameter in xml declaration of POM is ignored

the encoding parameter in xml declaration of POM is ignored Key: MNG-2254 URL: http://jira.codehaus.org/browse/MNG-2254 Project: Maven 2 Type: Bug Reporter: Naoki Nose Attachments:

[jira] Updated: (MNG-2254) the encoding parameter in xml declaration of POM is ignored

[ http://jira.codehaus.org/browse/MNG-2254?page=all ] Naoki Nose updated MNG-2254: Attachment: DefaultMavenProjectBuilder.diff the encoding parameter in xml declaration of POM is ignored

[jira] Commented: (MNG-2254) the encoding parameter in xml declaration of POM is ignored

[ http://jira.codehaus.org/browse/MNG-2254?page=comments#action_64373 ] Naoki Nose commented on MNG-2254: - Attached files are the patch to fix this issue. These files depend on the patch of MXParser which I attached to the following issue.

[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

[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:

[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:

[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

[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

[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

[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: (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: (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

[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 description element, it easily can

[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

[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 description element, it

[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_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

[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] 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:

[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,

[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,

[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:

[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

[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

[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]

[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: (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:

[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

[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_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: eclipse.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: 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 ] Eugene Kuleshov updated MNGECLIPSE-114: --- Attachment: (was: workspace.tgz) cannot run junit testcases from within Eclipse --