[jira] Reopened: (MNG-3586) jaxws mojo wsgen failure with maven 3.0
[ http://jira.codehaus.org/browse/MNG-3586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Henri Gomez reopened MNG-3586: -- I still got the problem with the embedded maven in the latest m2eclipse (0.9.7.200810211352). I attached a new sample project which works with maven 2.0.9 (Sun or IBM SDK), but failed with embedded maven. > jaxws mojo wsgen failure with maven 3.0 > --- > > Key: MNG-3586 > URL: http://jira.codehaus.org/browse/MNG-3586 > Project: Maven 2 > Issue Type: Bug > Components: Embedding >Affects Versions: 3.0 > Environment: Windows XP / Java 5 or 6 >Reporter: Henri Gomez >Assignee: Brett Porter > Fix For: 3.0-alpha-1 > > Attachments: pom.xml, sample-wsgen-fixed.zip, sample-wsgen.zip > > > I can build jar projects using the jaxws wsgen mojo (1.9) under maven > 2.0.x but it failed under m2eclipse (0.9.3) when using maven 2.1 > embedded (it works if I switch m2eclipse to use the maven 2.0.9 on my > system). > I tried with various JVM (Sun and IBM 5 and 6) but still got the > problem with maven 2.1 embedded (maven 2.1-620417 and 2.1-655675): > error is : > From file: C:\workspace\xxx-er-go\pom.xml > Reason: Failed to execute wsgen > java.lang.NoClassDefFoundError: com/sun/mirror/apt/AnnotationProcessorFactory > at java.lang.ClassLoader.defineClass1(Native Method) > at java.lang.ClassLoader.defineClass(ClassLoader.java:620) > at > java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124) > at java.net.URLClassLoader.defineClass(URLClassLoader.java:260) > at java.net.URLClassLoader.access$100(URLClassLoader.java:56) > at java.net.URLClassLoader$1.run(URLClassLoader.java:195) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(URLClassLoader.java:188) > at java.lang.ClassLoader.loadClass(ClassLoader.java:306) > at java.lang.ClassLoader.loadClass(ClassLoader.java:251) > at > org.codehaus.plexus.classworlds.realm.ClassRealm.loadRealmClass(ClassRealm.java:174) > at > org.codehaus.plexus.classworlds.strategy.DefaultStrategy.loadClass(DefaultStrategy.java:67) > at > org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:201) > at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) > at com.sun.tools.ws.WsGen.doMain(WsGen.java:69) > at > org.codehaus.mojo.jaxws.AbstractWsGenMojo.execute(AbstractWsGenMojo.java:91) > at org.codehaus.mojo.jaxws.MainWsGenMojo.execute(MainWsGenMojo.java:14) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:577) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:498) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmentForProject(DefaultLifecycleExecutor.java:265) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:191) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:149) > at > org.apache.maven.DefaultMaven.execute_aroundBody0(DefaultMaven.java:223) > at > org.apache.maven.DefaultMaven.execute_aroundBody1$advice(DefaultMaven.java:304) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:1) > at > org.apache.maven.embedder.MavenEmbedder.execute_aroundBody2(MavenEmbedder.java:903) > at > org.apache.maven.embedder.MavenEmbedder.execute_aroundBody3$advice(MavenEmbedder.java:304) > at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:1) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:176) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:63) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:52) > Any idea or fixes ? > my pom.xml wsgen is standard : > > > > maven-compiler-plugin > > 1.5 > 1.5 > > > > compile > > compile > > initialize > > > > > > > org.codehaus.mojo > jaxws-ma
[jira] Updated: (MNG-3586) jaxws mojo wsgen failure with maven 3.0
[ http://jira.codehaus.org/browse/MNG-3586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Henri Gomez updated MNG-3586: - Attachment: sample-wsgen-20081229.zip This project failed with : While building project: Group-Id: mycorp.com Artifact-Id: samplewsgen Version: 1.0.0-SNAPSHOT >From file: C:\Documents and Settings\gomezhe\Bureau\sample-wsgen\pom.xml Reason: Failed to execute wsgen java.lang.NoClassDefFoundError: com/sun/mirror/apt/AnnotationProcessorFactory at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:620) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124) at java.net.URLClassLoader.defineClass(URLClassLoader.java:260) at java.net.URLClassLoader.access$100(URLClassLoader.java:56) at java.net.URLClassLoader$1.run(URLClassLoader.java:195) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:188) at java.lang.ClassLoader.loadClass(ClassLoader.java:306) at java.lang.ClassLoader.loadClass(ClassLoader.java:251) at org.codehaus.plexus.classworlds.realm.ClassRealm.loadRealmClass(ClassRealm.java:174) at org.codehaus.plexus.classworlds.strategy.DefaultStrategy.loadClass(DefaultStrategy.java:67) at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:201) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) at com.sun.tools.ws.WsGen.doMain(WsGen.java:69) at org.codehaus.mojo.jaxws.AbstractWsGenMojo.execute(AbstractWsGenMojo.java:97) at org.codehaus.mojo.jaxws.MainWsGenMojo.execute(MainWsGenMojo.java:14) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:579) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:498) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmentForProject(DefaultLifecycleExecutor.java:265) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:191) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:149) at org.apache.maven.DefaultMaven.execute_aroundBody0(DefaultMaven.java:223) at org.apache.maven.DefaultMaven.execute_aroundBody1$advice(DefaultMaven.java:304) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:1) at org.apache.maven.embedder.MavenEmbedder.execute_aroundBody2(MavenEmbedder.java:904) at org.apache.maven.embedder.MavenEmbedder.execute_aroundBody3$advice(MavenEmbedder.java:304) at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:1) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:176) at org.apache.maven.cli.MavenCli.main(MavenCli.java:63) at org.apache.maven.cli.MavenCli.main(MavenCli.java:52) Error stacktrace: org.apache.maven.lifecycle.LifecycleExecutionException: Internal error in the plugin manager executing goal 'org.codehaus.mojo:jaxws-maven-plugin:1.10:wsgen': Mojo execution failed. at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:505) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmentForProject(DefaultLifecycleExecutor.java:265) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:191) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:149) at org.apache.maven.DefaultMaven.execute_aroundBody0(DefaultMaven.java:223) at org.apache.maven.DefaultMaven.execute_aroundBody1$advice(DefaultMaven.java:304) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:1) at org.apache.maven.embedder.MavenEmbedder.execute_aroundBody2(MavenEmbedder.java:904) at org.apache.maven.embedder.MavenEmbedder.execute_aroundBody3$advice(MavenEmbedder.java:304) at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:1) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:176) at org.apache.maven.cli.MavenCli.main(MavenCli.java:63) at org.apache.maven.cli.MavenCli.main(MavenCli.java:52) Caused by: org.apache.maven.plugin.PluginExecutionException: Mojo execution failed. at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:601) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:498) ... 12 more Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to execute wsg
[jira] Created: (MAVENUPLOAD-2318) Upload easystream library
Upload easystream library - Key: MAVENUPLOAD-2318 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2318 Project: Maven Upload Requests Issue Type: Wish Reporter: Davide Simonetti http://io-tools.googlecode.com/files/easystream-1.1-bundle.jar http://code.google.com/p/io-tools/ Hi! i'm the owner of the project io-tools, can you please upload the artifact easystream ? The project owner (me) is listed in the right bar of the home page, near the bottom line. My email is dvd.s...@gmail.com contact me for any problem or question. Best regards. Davide Simonetti -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MECLIPSE-518) NPE when generating WTP configuration files - sometimes - very strange
NPE when generating WTP configuration files - sometimes - very strange
--
Key: MECLIPSE-518
URL: http://jira.codehaus.org/browse/MECLIPSE-518
Project: Maven 2.x Eclipse Plugin
Issue Type: Bug
Components: WTP support
Affects Versions: 2.5.1
Environment: Windows XP, java 1.6, mvn 2.0.9
Reporter: Martin Monsorno
When running {{mvn eclipse:eclipse -Dwtpversion=2.0}} on my project, I get a
NullPointerException, but only in some directories! E.g. when the project
sources lie in d:\epa-trunk, I get the following output:
{quote}
D:\epa-trunk\web>mvn eclipse:eclipse -Dwtpversion=2.0
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'eclipse'.
[INFO]
[INFO] Building epa-web
[INFO]task-segment: [eclipse:eclipse]
[INFO]
[INFO] Preparing eclipse:eclipse
[INFO] [enforcer:enforce {execution: default}]
[INFO] [eclipse:eclipse]
[INFO] Adding support for WTP version 2.0.
[INFO] Using as WTP server : null
[INFO] Adding default classpath contaigner:
org.eclipse.jdt.launching.JRE_CONTAINER
[INFO] Using source status cache:
D:\epa-trunk\web\target\mvn-eclipse-cache.properties
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] null
[INFO]
[INFO] Trace
java.lang.NullPointerException
at
org.apache.maven.plugin.ide.IdeDependency.isSystemScopedOutsideProject(IdeDependency.java:519)
at
org.apache.maven.plugin.eclipse.writers.wtp.AbstractWtpResourceWriter.writeWarOrEarResources(AbstractWtpResourceWriter.java:280)
at
org.apache.maven.plugin.eclipse.writers.wtp.EclipseWtpComponentWriter.writeModuleTypeComponent(EclipseWtpComponentWriter.java:188)
at
org.apache.maven.plugin.eclipse.writers.wtp.EclipseWtpComponentWriter.write(EclipseWtpComponentWriter.java:105)
at
org.apache.maven.plugin.eclipse.EclipsePlugin.writeConfiguration(EclipsePlugin.java:945)
at
org.apache.maven.plugin.ide.AbstractIdeSupportMojo.execute(AbstractIdeSupportMojo.java:494)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
[INFO]
[INFO] Total time: 4 seconds
[INFO] Finished at: Mon Dec 29 15:00:14 CET 2008
[INFO] Final Memory: 19M/35M
[INFO]
{quote}
When moving the sources to d:\tmp, the build completes successfully:
{quote}
D:\epa-trunk\web>cd ..\..
D:\>move epa-trunk tmp
D:\>cd tmp\epa-trunk\web
D:\tmp\epa-trunk\web>mvn eclipse:eclipse -Dwtpversion=2.0
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'eclipse'.
[INFO]
[INFO] Building epa-web
[INFO]task-segment: [eclipse:eclipse]
[INFO]
[INFO] Preparing eclipse:eclipse
[INFO] [enforcer:enforce {execution: default}]
[INFO] [eclipse:eclipse]
[jira] Created: (SUREFIRE-535) surefire tries to treat nested classes, even anonymous ones, as test classes?
surefire tries to treat nested classes, even anonymous ones, as test classes? - Key: SUREFIRE-535 URL: http://jira.codehaus.org/browse/SUREFIRE-535 Project: Maven Surefire Issue Type: Bug Components: JUnit 3.x support Affects Versions: 2.4.2 Reporter: benson margulies Given a top-level test class that inherits from TestCase. If it, internally, declares an anonymous class, or even a named child class, surefire + junit tries to run it, and fails with a warning or an initializationError. This does not happen from the vanilla junit test runner. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-3586) jaxws mojo wsgen failure with maven 3.0
[ http://jira.codehaus.org/browse/MNG-3586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-3586: --- Fix Version/s: (was: 3.0-alpha-1) 3.0-alpha-3 > jaxws mojo wsgen failure with maven 3.0 > --- > > Key: MNG-3586 > URL: http://jira.codehaus.org/browse/MNG-3586 > Project: Maven 2 > Issue Type: Bug > Components: Embedding >Affects Versions: 3.0 > Environment: Windows XP / Java 5 or 6 >Reporter: Henri Gomez >Assignee: Brett Porter > Fix For: 3.0-alpha-3 > > Attachments: pom.xml, sample-wsgen-20081229.zip, > sample-wsgen-fixed.zip, sample-wsgen.zip > > > I can build jar projects using the jaxws wsgen mojo (1.9) under maven > 2.0.x but it failed under m2eclipse (0.9.3) when using maven 2.1 > embedded (it works if I switch m2eclipse to use the maven 2.0.9 on my > system). > I tried with various JVM (Sun and IBM 5 and 6) but still got the > problem with maven 2.1 embedded (maven 2.1-620417 and 2.1-655675): > error is : > From file: C:\workspace\xxx-er-go\pom.xml > Reason: Failed to execute wsgen > java.lang.NoClassDefFoundError: com/sun/mirror/apt/AnnotationProcessorFactory > at java.lang.ClassLoader.defineClass1(Native Method) > at java.lang.ClassLoader.defineClass(ClassLoader.java:620) > at > java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124) > at java.net.URLClassLoader.defineClass(URLClassLoader.java:260) > at java.net.URLClassLoader.access$100(URLClassLoader.java:56) > at java.net.URLClassLoader$1.run(URLClassLoader.java:195) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(URLClassLoader.java:188) > at java.lang.ClassLoader.loadClass(ClassLoader.java:306) > at java.lang.ClassLoader.loadClass(ClassLoader.java:251) > at > org.codehaus.plexus.classworlds.realm.ClassRealm.loadRealmClass(ClassRealm.java:174) > at > org.codehaus.plexus.classworlds.strategy.DefaultStrategy.loadClass(DefaultStrategy.java:67) > at > org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:201) > at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) > at com.sun.tools.ws.WsGen.doMain(WsGen.java:69) > at > org.codehaus.mojo.jaxws.AbstractWsGenMojo.execute(AbstractWsGenMojo.java:91) > at org.codehaus.mojo.jaxws.MainWsGenMojo.execute(MainWsGenMojo.java:14) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:577) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:498) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmentForProject(DefaultLifecycleExecutor.java:265) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:191) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:149) > at > org.apache.maven.DefaultMaven.execute_aroundBody0(DefaultMaven.java:223) > at > org.apache.maven.DefaultMaven.execute_aroundBody1$advice(DefaultMaven.java:304) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:1) > at > org.apache.maven.embedder.MavenEmbedder.execute_aroundBody2(MavenEmbedder.java:903) > at > org.apache.maven.embedder.MavenEmbedder.execute_aroundBody3$advice(MavenEmbedder.java:304) > at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:1) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:176) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:63) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:52) > Any idea or fixes ? > my pom.xml wsgen is standard : > > > > maven-compiler-plugin > > 1.5 > 1.5 > > > > compile > > compile > > initialize >
[jira] Commented: (MCHANGES-143) Specifying sender email address using fromDeveloperId is no longer working.
[
http://jira.codehaus.org/browse/MCHANGES-143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159383#action_159383
]
Chad Gorshing commented on MCHANGES-143:
This may not be directly related to this issue, but according to the
documentation at
http://maven.apache.org/plugins/maven-changes-plugin/examples/specifying-mail-sender.html,
it says "If no developer id is specified, the first in the list
will be used."
This is not happening on my machine (I'm sure I deserve
http://www.codinghorror.com/blog/archives/000818.html). Would this issue be
related to that or something entirely different?
> Specifying sender email address using fromDeveloperId is no longer working.
> ---
>
> Key: MCHANGES-143
> URL: http://jira.codehaus.org/browse/MCHANGES-143
> Project: Maven 2.x Changes Plugin
> Issue Type: Bug
> Components: announcement
>Affects Versions: 2.1
> Environment: Maven 2.0.9, Windows XP Pro SP3.
>Reporter: Christophe Labouisse
> Attachments: patch-maven-changes-plugin-rev-727375.txt
>
>
> According to the documentation and the available examples, it is possible
> specify the "from" address using either mailSend or fromDeveloperId. Starting
> with version 2.1, using fromDeveloperId leads to the following error:
> [INFO] Invalid mail sender: name and email is mandatory (null (null)).
> Looking at the source code, the regression seems to have been introduced by
> adding "@parameter expression="${changes.mailSender}"" to the declaration of
> the mailSender attribute.
> Attached is a patch fixing the issue from the svn repository at revision
> 727375.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNGSITE-76) The http://maven.apache.org/development-process.html WebPage has dead/broken links
The http://maven.apache.org/development-process.html WebPage has dead/broken links -- Key: MNGSITE-76 URL: http://jira.codehaus.org/browse/MNGSITE-76 Project: Maven 2 Project Web Site Issue Type: Bug Environment: not applicable Reporter: Andre Ouellet The links to "Best Practices Documents" on the "development-process.html " page of the Maven Website are all dead/broken Site/Page with broken links -> The http://maven.apache.org/development-process.html The following links are broken: - Branches - Deprecation - Distributions - Release Process Has the documents/content moved ? If so the ... page should be updated with new working links Has the documents/content been retired ? If so the ... page should reflect this -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SUREFIRE-377) When JUnit and TestNG tests are in same project, only one set gets run
[ http://jira.codehaus.org/browse/SUREFIRE-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159389#action_159389 ] Roger Pack commented on SUREFIRE-377: - In my case it might have been being caused by: org.apache.maven.plugins maven-surefire-plugin 2.1 in my pom.xml [note the old version] > When JUnit and TestNG tests are in same project, only one set gets run > -- > > Key: SUREFIRE-377 > URL: http://jira.codehaus.org/browse/SUREFIRE-377 > Project: Maven Surefire > Issue Type: Bug > Components: TestNG support >Affects Versions: 2.4 >Reporter: Dan Fabulich > Fix For: 2.4 > > Attachments: surefire377.patch, testng-junit-together.zip > > > The attached Maven project has two tests: one JUnit test and one TestNG test. > According to the documentation, in this case TestNG should run both tests. > Run "mvn test". Only the TestNG test will run. If you modify the pom to set > the property "junit=true", only the JUnit test will run. > > org.apache.maven.plugins > maven-surefire-plugin > 2.4-SNAPSHOT > > > > junit > true > > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SUREFIRE-157) Surefire Plugin fails to handle exception thrown from TestNG @BeforeTest method
[
http://jira.codehaus.org/browse/SUREFIRE-157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159390#action_159390
]
Roger Pack commented on SUREFIRE-157:
-
I think I get this with junit [and surefire] as well.
If a runtime exception is thrown in an @BeforeClass method, maven terminates
with "go and see the log generated" message, however the generated log files
are blank.
Any help on this?
> Surefire Plugin fails to handle exception thrown from TestNG @BeforeTest
> method
> ---
>
> Key: SUREFIRE-157
> URL: http://jira.codehaus.org/browse/SUREFIRE-157
> Project: Maven Surefire
> Issue Type: Bug
> Components: TestNG support
>Affects Versions: 2.0 (2.2 plugin), 2.3
> Environment: Windows XP, JDK 1.5, Maven 2.0.4, TestNG 5.1
>Reporter: Manish Shah
> Fix For: 2.4
>
>
> Create a TestNG test with a method as follows:
> @BeforeTest
> public void beforeTest() {
> throw new RuntimeException("Simulate an exception from a beforeTest
> method");
> }
> When surefire attempts to run this test, the plugin fails with the following
> stack trace:
> org.apache.maven.surefire.booter.SurefireExecutionException: null; nested
> exception is java.lang.NullPointerException: n
> ull
> java.lang.NullPointerException
> at
> org.apache.maven.surefire.report.AbstractTextReporter.testFailed(AbstractTextReporter.java:106)
> at
> org.apache.maven.surefire.report.ReporterManager.testFailed(ReporterManager.java:299)
> at
> org.apache.maven.surefire.report.ReporterManager.testFailed(ReporterManager.java:281)
> at
> org.apache.maven.surefire.testng.TestNGReporter.onTestFailure(TestNGReporter.java:97)
> at org.testng.internal.Invoker.runTestListeners(Invoker.java:1164)
> at org.testng.internal.Invoker.runTestListeners(Invoker.java:1149)
> at
> org.testng.internal.Invoker.handleConfigurationFailure(Invoker.java:191)
> at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:170)
> at org.testng.SuiteRunner.privateRun(SuiteRunner.java:236)
> at org.testng.SuiteRunner.run(SuiteRunner.java:145)
> at org.testng.TestNG.createAndRunSuiteRunners(TestNG.java:901)
> at org.testng.TestNG.runSuitesLocally(TestNG.java:863)
> at
> org.apache.maven.surefire.testng.TestNGExecutor.executeTestNG(TestNGExecutor.java:64)
> at
> org.apache.maven.surefire.testng.TestNGXmlTestSuite.execute(TestNGXmlTestSuite.java:75)
> at org.apache.maven.surefire.Surefire.run(Surefire.java:129)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> at
> org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:225)
> at
> org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:747)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MAVENUPLOAD-2312) Please copy over hibernate-entitymanager 3.4.0GA from jboss repo
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Ferguson updated MAVENUPLOAD-2312: -- Attachment: hibernate-entitymanager-3.4.0.GA.pom There seems to be a problem with the POM for hibernate-entitymanager 3.4.0.GA at http://repository.jboss.org/maven2 The POM states that it has a packaging of type 'pom' when it should be 'jar'. Packaging of type pom means that only the POM is downloaded, not the jar file for the component. NB the last version of entitymanager with the correct packaging was 3.3.1.ga Maybe this is behind the reason behind this component not being copied over to Central. I've attached a good POM. It just has the packaging switched from POM to JAR. > Please copy over hibernate-entitymanager 3.4.0GA from jboss repo > > > Key: MAVENUPLOAD-2312 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2312 > Project: Maven Upload Requests > Issue Type: Bug >Reporter: Dan Tran >Assignee: Carlos Sanchez > Attachments: hibernate-entitymanager-3.4.0.GA.pom > > > the jboss repo is at > > http://repository.jboss.com/maven2/org/hibernate/hibernate-entitymanager/3.4.0.GA/ > This is needed to get hibernate3-maven-plugin to pickup the latest hibernate > artifact > Hope it is ok not ot provide the bundle -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SUREFIRE-377) When JUnit and TestNG tests are in same project, only one set gets run
[ http://jira.codehaus.org/browse/SUREFIRE-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159395#action_159395 ] Pawel Poltorak commented on SUREFIRE-377: - Hi, I'm afraid there is more to be done to allow both JUnit and TestNG tests. Changing surefire plugin is the easy part. Surefire uses testng runner to run JUnit tests, which doesn't support JUnit4 tests. Therefore TestNG team would have to change their runner to support JUnit4 Actually, I've made changes to both libraries. If there is someone from surefire team willing to apply my changes I can generate a patch. I've also contacted TestNG team, but they are not 100% sure they want to do junit4 support. > When JUnit and TestNG tests are in same project, only one set gets run > -- > > Key: SUREFIRE-377 > URL: http://jira.codehaus.org/browse/SUREFIRE-377 > Project: Maven Surefire > Issue Type: Bug > Components: TestNG support >Affects Versions: 2.4 >Reporter: Dan Fabulich > Fix For: 2.4 > > Attachments: surefire377.patch, testng-junit-together.zip > > > The attached Maven project has two tests: one JUnit test and one TestNG test. > According to the documentation, in this case TestNG should run both tests. > Run "mvn test". Only the TestNG test will run. If you modify the pom to set > the property "junit=true", only the JUnit test will run. > > org.apache.maven.plugins > maven-surefire-plugin > 2.4-SNAPSHOT > > > > junit > true > > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MERCURY-56) add repository authentication, verification configuration: PGP, checksums
[ http://jira.codehaus.org/browse/MERCURY-56?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Gusakov closed MERCURY-56. --- Resolution: Fixed done > add repository authentication, verification configuration: PGP, checksums > -- > > Key: MERCURY-56 > URL: http://jira.codehaus.org/browse/MERCURY-56 > Project: Mercury > Issue Type: Sub-task >Reporter: Oleg Gusakov >Assignee: Oleg Gusakov > Original Estimate: 2 days > Time Spent: 1 day > Remaining Estimate: 1 day > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MERCURY-50) Implement repository writing functionality
[ http://jira.codehaus.org/browse/MERCURY-50?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Gusakov closed MERCURY-50. --- Resolution: Fixed done > Implement repository writing functionality > -- > > Key: MERCURY-50 > URL: http://jira.codehaus.org/browse/MERCURY-50 > Project: Mercury > Issue Type: Sub-task > Components: Ant tasks >Reporter: Oleg Gusakov >Assignee: Oleg Gusakov > Original Estimate: 2 days > Remaining Estimate: 2 days > > Install / deploy functionality -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MERCURY-49) Implement basic classpath functionality
[ http://jira.codehaus.org/browse/MERCURY-49?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Gusakov closed MERCURY-49. --- Resolution: Fixed done > Implement basic classpath functionality > --- > > Key: MERCURY-49 > URL: http://jira.codehaus.org/browse/MERCURY-49 > Project: Mercury > Issue Type: Sub-task > Components: Ant tasks >Reporter: Oleg Gusakov >Assignee: Oleg Gusakov > Original Estimate: 2 days > Time Spent: 1 day > Remaining Estimate: 1 day > > basics: ability to: > * configure repositories > * declare dependencies > * resolve classpath -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MERCURY-70) documentation site
documentation site -- Key: MERCURY-70 URL: http://jira.codehaus.org/browse/MERCURY-70 Project: Mercury Issue Type: Sub-task Components: Ant tasks Reporter: Oleg Gusakov Assignee: Oleg Gusakov as stated -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRESOURCES-79) are filtered by test filters
[ http://jira.codehaus.org/browse/MRESOURCES-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159403#action_159403 ] Patrick Farrell commented on MRESOURCES-79: --- I am experiencing the same issue and think nodje has proposed what would be an intuitive and consistent solution (from the user perspective). I design my poms to use filtering based on profiles, so, I have a filters-dev.properties, filters-test.properties, etc... However, since I also create tests, I would like to have different props files for test runs within a specific environment, i.e. different log4j or hibernate config file settings that I populate using filtering. I think there should be a ... structure to accommodate the configuration I am describing. > are filtered by test filters > > > Key: MRESOURCES-79 > URL: http://jira.codehaus.org/browse/MRESOURCES-79 > Project: Maven 2.x Resources Plugin > Issue Type: Bug >Affects Versions: 2.3 > Environment: Maven 2.0.9, Java 1.6.0_07 OS_X >Reporter: nodje > Attachments: resources-testcase.zip > > > With the following configuration I assume should get filtered by > src/main/filters/* and by src/test/filters/* : > > src/main/filters/dev.filter.properties > src/test/filters/dev.filter.properties > > > > src/main/resources > true > > > > > src/test/resources > true > > > But all resources files end up being filtered by the src/test/filters/*. > Attached is the simpliest Maven2 proect reproducing this behavior. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
