[jira] Created: (WAGON-336) remove Sytem.out.println in wagons
remove Sytem.out.println in wagons -- Key: WAGON-336 URL: http://jira.codehaus.org/browse/WAGON-336 Project: Maven Wagon Issue Type: Bug Affects Versions: 2.0 Reporter: Mark Struberg we still have System.out.println in some Wagons. Those should get dropped and replaces with PlexusLoggers -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MASSEMBLY-559) useTransitiveDependencies leaks from one dependency set to another
useTransitiveDependencies leaks from one dependency set to another -- Key: MASSEMBLY-559 URL: http://jira.codehaus.org/browse/MASSEMBLY-559 Project: Maven 2.x Assembly Plugin Issue Type: Bug Affects Versions: 2.2.1 Reporter: Julien HENRY I have several dependencySets in my assembly descriptor. As soon as I let useTransitiveDependencies parameter to be true (set it or rely on default) for one dependency set, it will extend to all others dependency sets, even when their useTransitiveDependencies parameter is explicitly set to false. See attached test project. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MASSEMBLY-559) useTransitiveDependencies leaks from one dependency set to another
[ http://jira.codehaus.org/browse/MASSEMBLY-559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julien HENRY updated MASSEMBLY-559: --- Attachment: MASSEMBLY-559.tar.gz useTransitiveDependencies leaks from one dependency set to another -- Key: MASSEMBLY-559 URL: http://jira.codehaus.org/browse/MASSEMBLY-559 Project: Maven 2.x Assembly Plugin Issue Type: Bug Affects Versions: 2.2.1 Reporter: Julien HENRY Attachments: MASSEMBLY-559.tar.gz I have several dependencySets in my assembly descriptor. As soon as I let useTransitiveDependencies parameter to be true (set it or rely on default) for one dependency set, it will extend to all others dependency sets, even when their useTransitiveDependencies parameter is explicitly set to false. See attached test project. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (SUREFIRE-749) Parallel methods should run in separate classloaders
Parallel methods should run in separate classloaders Key: SUREFIRE-749 URL: http://jira.codehaus.org/browse/SUREFIRE-749 Project: Maven Surefire Issue Type: Improvement Components: Junit 4.7+ (parallel) support Affects Versions: 2.8.1 Reporter: Gili Priority: Critical When running in parallel-method or parallel-both mode, each @Test should run in its own ClassLoader. I'm running into a lot of problems involving the use of static variables in 3rd-party libraries. Here are two examples: 1. slf4j: http://bugzilla.slf4j.org/show_bug.cgi?id=176 2. guice: http://code.google.com/p/google-guice/issues/detail?id=635 I believe running in isolated ClassLoaders would fix both problems and it makes a lot of sense from a test isolation point of view so we should do it anyway. I believe Surefire's forkMode is defined in terms of isolated JVMs instead of ClassLoaders. Furthermore, it only seems to support per-Class isolation instead of per-@Test isolation. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (WAGON-336) remove Sytem.out.println in wagons
[ http://jira.codehaus.org/browse/WAGON-336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg closed WAGON-336. --- Resolution: Fixed Fix Version/s: 2.0 Assignee: Mark Struberg fixed in r1137747. remove Sytem.out.println in wagons -- Key: WAGON-336 URL: http://jira.codehaus.org/browse/WAGON-336 Project: Maven Wagon Issue Type: Bug Affects Versions: 2.0 Reporter: Mark Struberg Assignee: Mark Struberg Fix For: 2.0 we still have System.out.println in some Wagons. Those should get dropped and replaces with PlexusLoggers -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (MPOM-13) Java 5 compiler settings is only in quality-checks profile: should be in the default config
Java 5 compiler settings is only in quality-checks profile: should be in the default config --- Key: MPOM-13 URL: https://issues.apache.org/jira/browse/MPOM-13 Project: Maven POM Issue Type: Bug Components: maven Affects Versions: MAVEN-20 Reporter: Hervé Boutemy Fix For: MAVEN-21 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (MPOM-13) Java 5 compiler settings is only in quality-checks profile: should be in the default config
[ https://issues.apache.org/jira/browse/MPOM-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy closed MPOM-13. - Resolution: Fixed fixed in r1137805 Java 5 compiler settings is only in quality-checks profile: should be in the default config --- Key: MPOM-13 URL: https://issues.apache.org/jira/browse/MPOM-13 Project: Maven POM Issue Type: Bug Components: maven Affects Versions: MAVEN-20 Reporter: Hervé Boutemy Fix For: MAVEN-21 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (MPOM-14) make reporting and quality checks plugin Java 5 compatible
make reporting and quality checks plugin Java 5 compatible -- Key: MPOM-14 URL: https://issues.apache.org/jira/browse/MPOM-14 Project: Maven POM Issue Type: Improvement Components: maven Affects Versions: MAVEN-20 Reporter: Hervé Boutemy Fix For: MAVEN-21 now that compile is defaulting to Java 5, reporting should do the same: PMD, Checkstyle -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (MPOM-14) make reporting and quality checks plugin Java 5 compatible
[ https://issues.apache.org/jira/browse/MPOM-14?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy closed MPOM-14. - Resolution: Fixed done in r1137820 make reporting and quality checks plugin Java 5 compatible -- Key: MPOM-14 URL: https://issues.apache.org/jira/browse/MPOM-14 Project: Maven POM Issue Type: Improvement Components: maven Affects Versions: MAVEN-20 Reporter: Hervé Boutemy Fix For: MAVEN-21 now that compile is defaulting to Java 5, reporting should do the same: PMD, Checkstyle -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (MPOM-15) code generation plugins should generate Java 5 sources by default
code generation plugins should generate Java 5 sources by default - Key: MPOM-15 URL: https://issues.apache.org/jira/browse/MPOM-15 Project: Maven POM Issue Type: Improvement Components: maven Affects Versions: MAVEN-20 Reporter: Hervé Boutemy Fix For: MAVEN-21 Modello and maven-plugin-plugin -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MPOM-13) Java 5 compiler settings is only in quality-checks profile: should be in the default config
[ https://issues.apache.org/jira/browse/MPOM-13?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13052275#comment-13052275 ] Hudson commented on MPOM-13: Integrated in maven-parent #37 (See [https://builds.apache.org/job/maven-parent/37/]) [MPOM-13] set Java 5 compiler settings in default configuration (was only in quality-checks profile) hboutemy : http://svn.apache.org/viewvc/?view=revrev=1137805 Files : * /maven/pom/trunk/maven/pom.xml Java 5 compiler settings is only in quality-checks profile: should be in the default config --- Key: MPOM-13 URL: https://issues.apache.org/jira/browse/MPOM-13 Project: Maven POM Issue Type: Bug Components: maven Affects Versions: MAVEN-20 Reporter: Hervé Boutemy Fix For: MAVEN-21 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MPOM-14) make reporting and quality checks plugin Java 5 compatible
[ https://issues.apache.org/jira/browse/MPOM-14?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13052276#comment-13052276 ] Hudson commented on MPOM-14: Integrated in maven-parent #37 (See [https://builds.apache.org/job/maven-parent/37/]) [MPOM-14] configured reporting to be Java 5 compatible hboutemy : http://svn.apache.org/viewvc/?view=revrev=1137820 Files : * /maven/pom/trunk/maven/pom.xml make reporting and quality checks plugin Java 5 compatible -- Key: MPOM-14 URL: https://issues.apache.org/jira/browse/MPOM-14 Project: Maven POM Issue Type: Improvement Components: maven Affects Versions: MAVEN-20 Reporter: Hervé Boutemy Fix For: MAVEN-21 now that compile is defaulting to Java 5, reporting should do the same: PMD, Checkstyle -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MPOM-15) code generation plugins should generate Java 5 sources by default
[ https://issues.apache.org/jira/browse/MPOM-15?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13052296#comment-13052296 ] Hudson commented on MPOM-15: Integrated in maven-parent #38 (See [https://builds.apache.org/job/maven-parent/38/]) [MPOM-15] configured code generation plugins (Modello and maven-plugin-plugin) to generate Java 5 sources hboutemy : http://svn.apache.org/viewvc/?view=revrev=1137822 Files : * /maven/pom/trunk/maven/pom.xml code generation plugins should generate Java 5 sources by default - Key: MPOM-15 URL: https://issues.apache.org/jira/browse/MPOM-15 Project: Maven POM Issue Type: Improvement Components: maven Affects Versions: MAVEN-20 Reporter: Hervé Boutemy Fix For: MAVEN-21 Modello and maven-plugin-plugin -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
