8:18 a.m.
Hi Mickael and Nick,
We've been having a problem with running our bot tests on OS X with java 1.7. This is
what we get:
java.awt.AWTException: headless environment
To overcome this, we need to add this property to the tycho surefire argLine:
-Dawt.toolkit=sun.lwawt.macosx.LWCToolkit
The question is how to do it?
We tried this:
<profiles>
<profile>
<id>mac17</id>
<activation>
<os>
<family>mac</family>
</os>
<jdk>1.7</jdk>
</activation>
<properties>
<systemProperties>-Dawt.toolkit=sun.lwawt.macosx.LWCToolkit</systemProperties>
</properties>
</profile>
But the problem is that maven uses OR with multiple conditions instead of AND (there has
been an open bug report for this for a couple of years).
Do you have any idea how to overcome this? Of course you can always manually enable such
profile, but that's not really an option if you want to run a matrix job in Jenkins.
Also, if we find a solution for this, could we add it to the parent pom?
Thanks,
Martin
--
Martin Malina
JBoss QA Engineer
Red Hat Czech s.r.o.
Purkynova 99
612 45 Brno, Czech Republic
Tel.: +420 532 294 265
8:33 a.m.
Perhaps we could use https://github.com/kpiwko/el-profile-activator-extension
but not sure if we want to rely on something like that ;)
-Martin
On 15. 11. 2012, at 15:18, Martin Malina <mmalina(a)redhat.com> wrote:
Hi Mickael and Nick,
We've been having a problem with running our bot tests on OS X with java 1.7. This is
what we get:
java.awt.AWTException: headless environment
To overcome this, we need to add this property to the tycho surefire argLine:
-Dawt.toolkit=sun.lwawt.macosx.LWCToolkit
The question is how to do it?
We tried this:
<profiles>
<profile>
<id>mac17</id>
<activation>
<os>
<family>mac</family>
</os>
<jdk>1.7</jdk>
</activation>
<properties>
<systemProperties>-Dawt.toolkit=sun.lwawt.macosx.LWCToolkit</systemProperties>
</properties>
</profile>
But the problem is that maven uses OR with multiple conditions instead of AND (there has
been an open bug report for this for a couple of years).
Do you have any idea how to overcome this? Of course you can always manually enable such
profile, but that's not really an option if you want to run a matrix job in Jenkins.
Also, if we find a solution for this, could we add it to the parent pom?
Thanks,
Martin
--
Martin Malina
JBoss QA Engineer
Red Hat Czech s.r.o.
Purkynova 99
612 45 Brno, Czech Republic
Tel.: +420 532 294 265
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
--
Martin Malina
JBoss QA Engineer
Red Hat Czech s.r.o.
Purkynova 99
612 45 Brno, Czech Republic
Tel.: +420 532 294 265
10:04 a.m.
On 11/15/2012 03:18 PM, Martin Malina wrote:
Hi Mickael and Nick,
Hi,
We've been having a problem with running our bot tests on OS X with
java 1.7. This is what we get:
java.awt.AWTException: headless environment
To overcome this, we need to add this property to the tycho surefire
argLine: -Dawt.toolkit=sun.lwawt.macosx.LWCToolki
I hate Mac, they are the worst
thing that happened to Java developers, I
still don't understand why so many Java developers use them... That said ;)
Is this property set by default on Mac when using Eclipse? Are there
some success stories of Eclipse on OSX with Java 1.7 ?
It could be an upstream issue.
Also, I'd rather not using some complex and immature Expression Language
extension in the parent pom. We already have a lot of things to improve
with the way we build, using such a not-standard thing sounds like
shooting in our own feet.
If we can't find a better way, this will be yet-another-profile-for-OSX
in the pom.xml.
--
Mickael Istria
Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
My blog <http://mickaelistria.wordpress.com> - My Tweets
<http://twitter.com/mickaelistria>
10:10 a.m.
On 15. 11. 2012, at 17:04, Mickael Istria <mistria(a)redhat.com> wrote:
On 11/15/2012 03:18 PM, Martin Malina wrote:
> Hi Mickael and Nick,
Hi,
>
> We've been having a problem with running our bot tests on OS X with java 1.7.
This is what we get:
> java.awt.AWTException: headless environment
> To overcome this, we need to add this property to the tycho surefire argLine:
-Dawt.toolkit=sun.lwawt.macosx.LWCToolki
I hate Mac, they are the worst thing that happened to Java developers, I still don't
understand why so many Java developers use them... That said ;)
Yeah… :)
Is this property set by default on Mac when using Eclipse? Are there
some success stories of Eclipse on OSX with Java 1.7 ?
I'll have to check. Will let you know. But this is a OracleJDK-only class, so
definitely it's not used when using AppleJDK.
It could be an upstream issue.
Also, I'd rather not using some complex and immature Expression Language extension in
the parent pom. We already have a lot of things to improve with the way we build, using
such a not-standard thing sounds like shooting in our own feet.
Yeah, it's a
no-go anyway since the plugin requires putting some jars into $MAVEN_HOME/lib/ext which
you can't expect everybody to do.
If we can't find a better way, this will be
yet-another-profile-for-OSX in the pom.xml.
How do you mean? That's the problem - there is no way to do this - if you use the
profile definition above it will be added on Mac OR when java is 1.7, that is simply wrong
- it would be active on Mac with java 1.6 and that would fail.
-Martin
10:15 a.m.
On 11/15/2012 05:10 PM, Martin Malina wrote:
Is this property set by default on Mac when using Eclipse? Are there
some success stories of Eclipse on OSX with Java 1.7 ?
I'll have to check. Will let you know. But this is a OracleJDK-only
class, so definitely it's not used when using AppleJDK.
Thanks
How do you mean? That's the problem - there is no way to do this
- if
you use the profile definition above it will be added on Mac OR when
java is 1.7, that is simply wrong - it would be active on Mac with
java 1.6 and that would fail.
If we can't find a way to write an activation
expression that works,
then macosx users with Oracle JDK will have to specify the profile
enablement by themselves.
--
Mickael Istria
Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
My blog <http://mickaelistria.wordpress.com> - My Tweets
<http://twitter.com/mickaelistria>
2:49 a.m.
> We've been having a problem with running our bot tests on OS
X with java 1.7. This is what we get:
> java.awt.AWTException: headless environment
> To overcome this, we need to add this property to the tycho surefire argLine:
-Dawt.toolkit=sun.lwawt.macosx.LWCToolki
I hate Mac, they are the worst thing that happened to Java developers, I still don't
understand why so many Java developers use them... That said ;)
Yes, Oracle fucked it up, and Maven fucks it up even worse in this case...i.e. why on
*earth* would anyone have profile enablement be based on an "or".
Is this property set by default on Mac when using Eclipse? Are there
some success stories of Eclipse on OSX with Java 1.7 ?
It could be an upstream issue.
yeah - I'm curious about this - where did you find out sun.lwawt.macosx.LWCToolkit
would solve it ? is this swtbot being weird ?
note I google this and found we apparently have code that messes with this in our tests
?!
http://lists.jboss.org/pipermail/jbosstools-commits/2012-September/041589...
so this is not a new issue?
What is the full stacktrace of that error about "headless environment" ?
Also, I'd rather not using some complex and immature Expression
Language extension in the parent pom. We already have a lot of things to improve with the
way we build, using such a not-standard thing sounds like shooting in our own feet.
me neither - that requires custom extension install on every developer desk.
If we can't find a better way, this will be
yet-another-profile-for-OSX in the pom.xml.
seems like it yes - a severe limitation on how maven works ;(
/max
6:48 a.m.
On 16. 11. 2012, at 9:49, Max Rydahl Andersen <max.andersen(a)redhat.com> wrote:
>> We've been having a problem with running our bot tests on
OS X with java 1.7. This is what we get:
>> java.awt.AWTException: headless environment
>> To overcome this, we need to add this property to the tycho surefire argLine:
-Dawt.toolkit=sun.lwawt.macosx.LWCToolki
> I hate Mac, they are the worst thing that happened to Java developers, I still
don't understand why so many Java developers use them... That said ;)
Yes, Oracle fucked it up, and Maven fucks it up even worse in this case...i.e. why on
*earth* would anyone have profile enablement be based on an "or".
> Is this property set by default on Mac when using Eclipse? Are there some success
stories of Eclipse on OSX with Java 1.7 ?
> It could be an upstream issue.
>
yeah - I'm curious about this - where did you find out sun.lwawt.macosx.LWCToolkit
would solve it ? is this swtbot being weird ?
SWT bot is using awt under the hood for something - simulating keyboard pressing I think.
Lucia found out about the fix so I don't know how. And she's on maternity leave,
so she won't tell us :)
note I google this and found we apparently have code that messes with this in our tests
?!
http://lists.jboss.org/pipermail/jbosstools-commits/2012-September/041589...
so this is not a new issue?
Yes, it is not a new issue. But I didn't know about the hack in bot ext that is
supposed to deal with this. And our dummy test where I was debugging this doesn't use
bot ext (Jirka just submitted a pull request changing this test to use ReqAwareSuite from
bot ext so that should fix it).
What is the full stacktrace of that error about "headless environment" ?
Strangely enough when I tried this on my own MacBook the property was set correctly and
the test ran fine.
For AppleJDK the property is: awt.toolkit=apple.awt.CToolkit
For OracleJDK it is: awt.toolkit=sun.lwawt.macosx.LWCToolkit
So there must be something wrong with the jenkins slaves that they set the property
incorrectly for OracleJDK1.7 on Mac.
But anyway, it seems for now we will try to solve this with the hack in bot ext (or fixing
the slaves if we can determine how it happens).
The exception when this happens is this:
Error Message
java.awt.AWTException: headless environment
Stacktrace
java.lang.RuntimeException: java.awt.AWTException: headless environment
at
org.eclipse.swtbot.swt.finder.keyboard.AWTKeyboardStrategy.<init>(AWTKeyboardStrategy.java:39)
at
org.eclipse.swtbot.swt.finder.keyboard.KeyboardFactory.getAWTKeyboard(KeyboardFactory.java:103)
at
org.eclipse.swtbot.swt.finder.keyboard.KeyboardFactory.getDefaultKeyboard(KeyboardFactory.java:80)
at
org.eclipse.swtbot.swt.finder.widgets.AbstractSWTBot.keyboard(AbstractSWTBot.java:837)
at
org.eclipse.swtbot.swt.finder.widgets.AbstractSWTBot.pressShortcut(AbstractSWTBot.java:853)
at org.jboss.tools.dummy.ui.bot.test.DummyTest.dummyTest(DummyTest.java:38)
at org.jboss.tools.dummy.ui.bot.test.DummyTest.hundredTimes(DummyTest.java:54)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42)
at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222)
at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:30)
at org.junit.runners.ParentRunner.run(ParentRunner.java:300)
at
org.eclipse.swtbot.swt.finder.junit.SWTBotJunit4ClassRunner.run(SWTBotJunit4ClassRunner.java:54)
at org.junit.runners.Suite.runChild(Suite.java:128)
at org.junit.runners.Suite.runChild(Suite.java:24)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222)
at org.junit.runners.ParentRunner.run(ParentRunner.java:300)
at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53)
at
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:123)
at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:104)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at
org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:164)
at
org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:110)
at
org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:175)
at
org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:123)
at
org.eclipse.tycho.surefire.osgibooter.OsgiSurefireBooter.run(OsgiSurefireBooter.java:85)
at
org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication.runTests(AbstractUITestApplication.java:44)
at org.eclipse.ui.internal.testing.WorkbenchTestable$1.run(WorkbenchTestable.java:71)
at java.lang.Thread.run(Thread.java:722)
Caused by: java.awt.AWTException: headless environment
at java.awt.Robot.<init>(Robot.java:94)
at
org.eclipse.swtbot.swt.finder.keyboard.AWTKeyboardStrategy.<init>(AWTKeyboardStrategy.java:37)
... 49 more
Thanks,
Martin
7:08 p.m.
> yeah - I'm curious about this - where did you find out
sun.lwawt.macosx.LWCToolkit would solve it ? is this swtbot being weird ?
SWT bot is using awt under the hood for something - simulating keyboard pressing I think.
Lucia found out about the fix so I don't know how. And she's on maternity leave,
so she won't tell us :)
:)
> note I google this and found we apparently have code that messes
with this in our tests ?!
>
> http://lists.jboss.org/pipermail/jbosstools-commits/2012-September/041589...
>
> so this is not a new issue?
Yes, it is not a new issue. But I didn't know about the hack in bot ext that is
supposed to deal with this. And our dummy test where I was debugging this doesn't use
bot ext (Jirka just submitted a pull request changing this test to use ReqAwareSuite from
bot ext so that should fix it).
okey - so no need to change parent pom for now ?
> What is the full stacktrace of that error about "headless
environment" ?
Strangely enough when I tried this on my own MacBook the property was set correctly and
the test ran fine.
For AppleJDK the property is: awt.toolkit=apple.awt.CToolkit
For OracleJDK it is: awt.toolkit=sun.lwawt.macosx.LWCToolkit
So there must be something wrong with the jenkins slaves that they set the property
incorrectly for OracleJDK1.7 on Mac.
okey.
But anyway, it seems for now we will try to solve this with the hack
in bot ext (or fixing the slaves if we can determine how it happens).
cool.
The exception when this happens is this:
Error Message
java.awt.AWTException: headless environment
Stacktrace
java.lang.RuntimeException: java.awt.AWTException: headless environment
at
org.eclipse.swtbot.swt.finder.keyboard.AWTKeyboardStrategy.<init>(AWTKeyboardStrategy.java:39)
at
org.eclipse.swtbot.swt.finder.keyboard.KeyboardFactory.getAWTKeyboard(KeyboardFactory.java:103)
weird it thinks you are in headless mode - any chance this is called "too soon"
and AWT is not fully started yet ?
/max
1:08 a.m.
On 11/16/2012 01:48 PM, Martin Malina wrote:
SWT bot is using awt under the hood for something - simulating
keyboard pressing I think. Lucia found out about the fix so I don't
know how. And she's on maternity leave, so she won't tell us :)
Please see
http://wiki.eclipse.org/SWTBot/Keyboard_Layouts#Keyboard_strategies
By default, SWTBot uses the AWTKeyboardStrategy IIRC. This can be
overriden to use the SWTKeyboardStrategy.
AWT's Robot is also used when it comes to perform some drag'n'drop
operations.
--
Mickael Istria
Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
My blog <http://mickaelistria.wordpress.com> - My Tweets
<http://twitter.com/mickaelistria>
4435
days inactive
4439
days old
jbosstools-dev@lists.jboss.org
8 comments
3 participants
participants (3)
-
Martin Malina -
Max Rydahl Andersen -
Mickael Istria