On Oct 21, 2009, at 2:21 PM, Jerome Dochez wrote:
> I have spent the entire morning mopping after various QL failures,
> after my last checkin, QL just turned blue
> http://gf-hudson.sfbay.sun.com/hudson/job/gf-trunk-build-continuous/2920/
>
> whoever breaks it again today (or the next few days) without a
> reasonable excuse will have to fix the next QL failures for the next
> 3 days.
>
> Jerome
>
> PS : oh and this does not apply to me, since I have already
> accumulated enough good karma...
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>
I just checked in the ORB work, after testing it MULTIPLE TIMES quite
carefully, and
all tests passed. Now I see that the job went red on my revision
(33096), with the following
in the console:
[INFO] The PluginDescriptor for the plugin Plugin
[com.sun.enterprise:hk2-maven-plugin] was not found.
[INFO]
------------------------------------------------------------------------
[INFO] Trace
java.lang.IllegalStateException: The PluginDescriptor for the plugin
Plugin [com.sun.enterprise:hk2-maven-plugin] was not found.
at
org
.apache
.maven.plugin.DefaultPluginManager.addPlugin(DefaultPluginManager.java:
325)
at
org
.apache
.maven
.plugin
.DefaultPluginManager.verifyVersionedPlugin(DefaultPluginManager.java:
212)
at
org
.apache
.maven
.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:176)
at
org
.apache
.maven
.lifecycle
.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:
1274)
at
org
.apache
.maven
.lifecycle
.DefaultLifecycleExecutor
.findArtifactTypeHandlers(DefaultLifecycleExecutor.java:1193)
at
org
.apache
.maven
.lifecycle
.DefaultLifecycleExecutor.findExtensions(DefaultLifecycleExecutor.java:
177)
at
org
.apache
.maven
.lifecycle
.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140)
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: 8 seconds
[INFO] Finished at: Wed Oct 21 14:19:58 PDT 2009
[INFO] Final Memory: 4M/281M
[INFO]
------------------------------------------------------------------------
Archiving artifacts
Recording test results
Sending e-mails to: terena.chinnfujii_at_sun.com jane.young_at_sun.com ming.zhang_at_sun.com
sherry.shen_at_sun.com kcavanaugh_at_dev.java.net jdlee_at_dev.java.net
Build was marked for publishing on
http://hudson.glassfish.org/
Finished: FAILURE
What does THAT mean? I have no idea what failed, how to fix it, or how
(or if) it is related to my commit.
If I can run all of the tests before I check in, and then have this
happen, what good is the Hudson job?
Ken.