Vous avez (1) nouveau message Apple-ID.
by iTunes
Chèr(e) client(e),
Nous vous informe que votre compte arrive à expiration dans moins 48
heures, il es impératif d'effectuer une vérification de vos informations des à
présent, sans quoi votre compte sera détruit. Cliquez simplement sur le lien ci-
dessous et ouvrez un session à l'aide de votre Apple ID et de votre mot de passe. Vérifiez maintenant
Pourquoi ce courrier électronique vous a-t-il été envoyé ?
L'envoi de ce courrier électronique s'applique lorsque la date d'expiration de votre
compte arrive à terme.
Pour plus d'informations, consultez la rubrique Questions et réponses.
Merci,
L'assistance à la clientèle Apple
TM and copyright © 2013 Apple Inc. 1 Infinite Loop, MS 96-DM, Cupertino, CA 95014. Alle Rechte vorbehalten / Informationsservice / Datenschutz / Meine Apple ID
9 years, 9 months
Should we build JBT 4.2 with JDK 7?
by Nick Boldt
Three of the projects in JBoss Tools use JDK 7 for testing: Server,
Webservices, and now Forge 2.
This is accomplished in Jenkins like this:
<jvmOptions>-Xms512m -Xmx1024m -XX:PermSize=128m -XX:MaxPermSize=256m
-Djbosstools.test.jre.5="${NATIVE_TOOLS}${SEP}${JAVA15}"
-Djbosstools.test.jre.6="${NATIVE_TOOLS}${SEP}${JAVA16}"
-Djbosstools.test.jre.7="${NATIVE_TOOLS}${SEP}${JAVA17}"</jvmOptions>
But all the projects still use JDK 6 to compile.
<jdk>java16_default</jdk>
Is that OK? Or is it time to consider moving to JDK 7 for building as
well as running tests?
If this warrants a JIRA, please open one and link to it from here. If
not, discuss why it makes sense to stay with JDK 6 for compilation.
If your project needs JDK 7 to run tests, and is not listed above,
please open a JIRA or fix your _42 and _master jobs directly. If you
can't fix your job (not sure how or don't have permission), email me or
JIRA me and I'll fix your jobs for you.
Cheers,
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
9 years, 9 months
XulRunner & SWT over GTK3
by Mickael Istria
Hi all,
Many of us have identified a major bug leading to Eclipse crash when
using JBT 4.2.0.Alpha1 and Eclipse Luna.
https://issues.jboss.org/browse/JBIDE-16280 ,
https://issues.jboss.org/browse/JBIDE-16308 ,
https://issues.jboss.org/browse/JBIDE-16290 .
Xulrunner binaries we have don't work on GTK3 (which is next Eclipse
default implementation for SWT on Linux). Apparently there is no
xulrunner available which works with GTK3, and anyway, the dependency on
discontinued JavaXPCom seems to show that it's impossible to find a set
of compatible SWT/GTK3/XulRunner/JavaXPCom libraries that can work together.
This makes that currently, we don't have any way to get XulRunner and
VPE working on Linux. They currently crash the workbench, but even if we
workaround that (by checking the gtk version used and avoid invoking
xulrunner when using GTK3) we can't have this feature working.
What do we do from here?
It seems like the recommended way (from old messages on JavaXPCom list)
is to use WebKitGTK+ on Linux instead of xulrunner. For more uniformity,
it would require to get rid of xulrunner for other OS and rely fully on
Webkit and a Java binding such as webkit driver.
Is this a right path to follow? If yes, this should be started very
soon, except if we prefer dropping the whole VPE in favour of something
else.
Cheers,
--
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>
9 years, 9 months
