[jira] Closed: (SUREFIRE-596) Junit test output is broken with junit4-7+

[ http://jira.codehaus.org/browse/SUREFIRE-596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen Connolly closed SUREFIRE-596. - Resolution: Fixed Fix Version/s: 2.5 r898206 > Junit test output is broken with junit

[jira] Commented: (SUREFIRE-596) Junit test output is broken with junit4-7+

[ http://jira.codehaus.org/browse/SUREFIRE-596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=206561#action_206561 ] Brett Porter commented on SUREFIRE-596: --- not sure how it was generated, but somehow it thinks

[jira] Updated: (SUREFIRE-596) Junit test output is broken with junit4-7+

[ http://jira.codehaus.org/browse/SUREFIRE-596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Rosenvold updated SUREFIRE-596: Attachment: junit2.zip junit2.diff This made me realize I have /no idea

[jira] Commented: (MEV-639) log4j bad metadata

[ http://jira.codehaus.org/browse/MEV-639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=206555#action_206555 ] Jim At Company commented on MEV-639: Too bad this has not been addressed yet. I don't know who's in

[jira] Closed: (MNG-3061) Circular dependencyManagement excludes all classpath dependencies

[ http://jira.codehaus.org/browse/MNG-3061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed MNG-3061. - Resolution: Cannot Reproduce Fix Version/s: (was: 2.2.x) can't reproduce in 2.0.6, let alone a recent

[jira] Closed: (MNG-2686) POM dependency scope auto-downgrades from provided to test

[ http://jira.codehaus.org/browse/MNG-2686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed MNG-2686. - Resolution: Cannot Reproduce Fix Version/s: (was: 2.2.x) Assignee: Brett Porter as of 2.0.9,

[jira] Created: (MWAR-216) Changes in dependencies aren't reflected in target/modulename/WEB-INF/lib

Changes in dependencies aren't reflected in target/modulename/WEB-INF/lib - Key: MWAR-216 URL: http://jira.codehaus.org/browse/MWAR-216 Project: Maven 2.x WAR Plugin Iss

[jira] Updated: (MNG-2523) OS name activation does not work for Mac OS X

[ http://jira.codehaus.org/browse/MNG-2523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MNG-2523: -- Fix Version/s: (was: 2.2.x) > OS name activation does not work for Mac OS X > -

[jira] Commented: (MAVEN-1831) Ibiblio Repository access that has items marked as '301: Moved permanently' causes maven to barf.

[ http://jira.codehaus.org/browse/MAVEN-1831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=206529#action_206529 ] Carlos Sanchez commented on MAVEN-1831: --- see MNG-4428 > Ibiblio Repository access that has ite

[jira] Created: (MREPOSITORY-20) 301 permanently moved (not following redirect)

301 permanently moved (not following redirect) -- Key: MREPOSITORY-20 URL: http://jira.codehaus.org/browse/MREPOSITORY-20 Project: Maven 2.x Repository Plugin Issue Type: Bug Affects Versions:

[jira] Issue Comment Edited: (MAVEN-1831) Ibiblio Repository access that has items marked as '301: Moved permanently' causes maven to barf.

[ http://jira.codehaus.org/browse/MAVEN-1831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=206528#action_206528 ] Trenton edited comment on MAVEN-1831 at 1/11/10 7:14 PM: - Oh, oops, this is h

[jira] Commented: (MAVEN-1831) Ibiblio Repository access that has items marked as '301: Moved permanently' causes maven to barf.

[ http://jira.codehaus.org/browse/MAVEN-1831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=206528#action_206528 ] Trenton commented on MAVEN-1831: Oh, oops, this is happening on 2.0.10 for me by the way, as well as

[jira] Commented: (MAVEN-1831) Ibiblio Repository access that has items marked as '301: Moved permanently' causes maven to barf.

[ http://jira.codehaus.org/browse/MAVEN-1831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=206527#action_206527 ] Trenton commented on MAVEN-1831: > See the news entry from 7 December 2006 on the main > Maven 1.x s

[jira] Issue Comment Edited: (MAVEN-1831) Ibiblio Repository access that has items marked as '301: Moved permanently' causes maven to barf.

[ http://jira.codehaus.org/browse/MAVEN-1831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=206525#action_206525 ] Trenton edited comment on MAVEN-1831 at 1/11/10 7:00 PM: - I am seeing this on

[jira] Commented: (MAVEN-1831) Ibiblio Repository access that has items marked as '301: Moved permanently' causes maven to barf.

[ http://jira.codehaus.org/browse/MAVEN-1831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=206525#action_206525 ] Trenton commented on MAVEN-1831: I am seeing this on multiple JARs. I've been using them for awhile

[jira] Commented: (SUREFIRE-596) Junit test output is broken with junit4-7+

[ http://jira.codehaus.org/browse/SUREFIRE-596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=206524#action_206524 ] Stephen Connolly commented on SUREFIRE-596: --- The patch is malformed, specifically: |

[jira] Created: (SUREFIRE-596) Junit test output is broken with junit4-7+

Junit test output is broken with junit4-7+ --- Key: SUREFIRE-596 URL: http://jira.codehaus.org/browse/SUREFIRE-596 Project: Maven Surefire Issue Type: Bug Components: Junit 4.x support A

[jira] Issue Comment Edited: (MASSEMBLY-463) Assembly fails Problem creating war: JAR entry not found

[ http://jira.codehaus.org/browse/MASSEMBLY-463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=206490#action_206490 ] Mike Key edited comment on MASSEMBLY-463 at 1/11/10 2:26 PM: - It would

[jira] Commented: (MASSEMBLY-463) Assembly fails Problem creating war: JAR entry not found

[ http://jira.codehaus.org/browse/MASSEMBLY-463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=206490#action_206490 ] Mike Key commented on MASSEMBLY-463: It would appear this issue can likely be closed or reduce

[jira] Created: (MSHADE-72) Classes from current artifact are excluded when explicit shaded includes are provided

Classes from current artifact are excluded when explicit shaded includes are provided - Key: MSHADE-72 URL: http://jira.codehaus.org/browse/MSHADE-72 Project: Maven 2

[jira] Updated: (MPLUGIN-165) Upgrading to Maven Site 2.1 messes up plugin site generation

[ http://jira.codehaus.org/browse/MPLUGIN-165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Youngstrom updated MPLUGIN-165: Attachment: deployable-mojo.html plugin-report.jpg I've attached a screen shot a

[jira] Commented: (MSHARED-140) MANEFEST class path attribute uses repository style name despite setting classpathMavenRepositoryLayout to false

[ http://jira.codehaus.org/browse/MSHARED-140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=206462#action_206462 ] Mike Power commented on MSHARED-140: You are right I get the same behaviour on both my windows a

[jira] Commented: (MWAR-215) class file JAR inconsistency (archiveClasses and attachClasses options)

[ http://jira.codehaus.org/browse/MWAR-215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=206455#action_206455 ] Stephane Nicoll commented on MWAR-215: -- Exactly what I said on the dev list. > class file JAR inc

[jira] Commented: (MWAR-215) class file JAR inconsistency (archiveClasses and attachClasses options)

[ http://jira.codehaus.org/browse/MWAR-215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=206454#action_206454 ] Jason van Zyl commented on MWAR-215: What are you plans to preserve backward compatibility? We are

[jira] Created: (MWAR-215) class file JAR inconsistency (archiveClasses and attachClasses options)

class file JAR inconsistency (archiveClasses and attachClasses options) --- Key: MWAR-215 URL: http://jira.codehaus.org/browse/MWAR-215 Project: Maven 2.x WAR Plugin Issue T

[jira] Commented: (MRELEASE-350) Option '0' for "specify the selection number ( 0:All 1:Project Dependencies 2:Plugins 3:Reports 4:Extensions ):" is broken

[ http://jira.codehaus.org/browse/MRELEASE-350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=206265#action_206265 ] Patrick Phelan commented on MRELEASE-350: - I'm surprised this issue is not of higher priori

[jira] Created: (MRESOURCES-115) Documentation improvement: default delimiters ${*} should be escaped

Documentation improvement: default delimiters ${*} should be escaped Key: MRESOURCES-115 URL: http://jira.codehaus.org/browse/MRESOURCES-115 Project: Maven 2.x Resources Plugin

[jira] Created: (MNG-4527) Surefire tests in integration-test phase are not executed

Surefire tests in integration-test phase are not executed - Key: MNG-4527 URL: http://jira.codehaus.org/browse/MNG-4527 Project: Maven 2 & 3 Issue Type: Bug Environment: jdk1.6

[jira] Closed: (SCM-261) Synergy provider assumes instance of 1 for projects... won't work for distributed CM (and some other scenarios)

[ http://jira.codehaus.org/browse/SCM-261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed SCM-261. Resolution: Fixed documentation patch rev 897841. Thanks ! > Synergy provider assumes instance of 1 for projects...

[jira] Reopened: (SCM-261) Synergy provider assumes instance of 1 for projects... won't work for distributed CM (and some other scenarios)

[ http://jira.codehaus.org/browse/SCM-261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy reopened SCM-261: -- patch for site to apply > Synergy provider assumes instance of 1 for projects... won't work for > distributed CM (

[jira] Commented: (MEAR-116) different build results from single module build and from reactor build

[ http://jira.codehaus.org/browse/MEAR-116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=206195#action_206195 ] Milos Kleint commented on MEAR-116: --- the project is basically what we generate in netbeans when someo

[jira] Commented: (MEAR-116) different build results from single module build and from reactor build

[ http://jira.codehaus.org/browse/MEAR-116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=206192#action_206192 ] Stephane Nicoll commented on MEAR-116: -- That's also what I think. It might be a misuse of core API

[jira] Issue Comment Edited: (WAGON-297) Wagon SCM does not automatically create missing directories during deployment

[ http://jira.codehaus.org/browse/WAGON-297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=206171#action_206171 ] Maria Odea Ching edited comment on WAGON-297 at 1/11/10 2:45 AM: - The

[jira] Commented: (SCM-511) Build error when publishing a new version of the site through the command line. Error: Embedded error: Unable to commit file. The svn command failed. svn: URL '----------'

[ http://jira.codehaus.org/browse/SCM-511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=206173#action_206173 ] Maria Odea Ching commented on SCM-511: -- Attached patch in WAGON-297 to fix this problem (if not usi

[jira] Updated: (WAGON-297) Wagon SCM does not automatically create missing directories during deployment

[ http://jira.codehaus.org/browse/WAGON-297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching updated WAGON-297: --- Attachment: WAGON-297.patch The attached patch automatically creates the missing directory when put(

[jira] Created: (WAGON-297) Wagon SCM does not automatically create missing directories during deployment

Wagon SCM does not automatically create missing directories during deployment - Key: WAGON-297 URL: http://jira.codehaus.org/browse/WAGON-297 Project: Maven Wagon Is

[jira] Updated: (MEAR-116) different build results from single module build and from reactor build

[ http://jira.codehaus.org/browse/MEAR-116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Milos Kleint updated MEAR-116: -- Attachment: ear116.zip here are the projects. > different build results from single module build and from rea

[jira] Commented: (MEAR-116) different build results from single module build and from reactor build

[ http://jira.codehaus.org/browse/MEAR-116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=206162#action_206162 ] Milos Kleint commented on MEAR-116: --- I'm not entirely sure this is a ear plugin problem only, could b