M5 spin status :: no aggregate or JBDS installers available yet; many bot and non-UI test failures, plus one inter-build compilation failure
by Nick Boldt
Since turning on the stable branch jobs, here's what's borked...
https://issues.jboss.org/browse/JBIDE-10349
Still trying to get a clean stable_branch aggregate build (and then JBT
builds too) - last time the aggregate failed due to missing Central,
OTDT, and OpenShift (hadn't spun clean yet).
---
Details:
- hibernate : test failure in org.hibernate.eclipse.console.test
- jbpm : test failure in org.jboss.tools.jbpm.convert.test
- jsf : test failure in org.jboss.tools.jsf.vpe.jsf.test
- maven : 15 bot test failures (same failures in trunk) ... should these
just be turned off and only run locally / manually?
- struts : COMPILE FAILED - upstream bits missing? "The import
org.jboss.tools.jst.web.validation cannot be resolved."
---
There are also a few jobs for which the latest build failed, but at
least we have one good build since branching. This suggests we're having
some stability issues w/ a few Jenkins slaves, but at least we're
getting clean spins when the server is quiet(er).
= archives : aborted build? [Dec 4 ok]
= birt : failed to find usage bits (poor timing between builds) [Dec 4 ok]
= seam : no more locks failure [Dec 4 ok]
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
2 weeks, 3 days
Re: [jbosstools-dev] Download Manager URL for EAP 6.3
by Rafael Benevides
From Jboss.org it uses
http://www.jboss.org/download-manager/file/jboss-eap-6.3.0.GA-installer.jar
but from stacks.yaml for EAP 6.2 it have the following URL:
http://www.jboss.org/download-manager/jdf/content/origin/files/sha256/62/...
I'm adding the jbosstools-dev list because it seems that the
download-manager URL have to be different for JBDS .
The URL was discussed on the thread "$0 subscription downloads - Stacks
integration with download manager"
Em 8/29/14, 10:23, Pete Muir escreveu:
> Look on the EAP download page on jboss.org.
>
> On 29 Aug 2014, at 14:22, Rafael Benevides <benevides(a)redhat.com> wrote:
>
>> Hi all,
>>
>> I'm updating stacks.yaml with EAP 6.3 BOMs and Runtimes.
>>
>> How can I get informed about the proper download-manager URL for EAP 6.3.
>>
>> Thanks
>>
>> --
>>
>> Rafael Benevides | Senior Software Engineer
>> JBoss Developer
>> M: +55-61-9269-6576
>>
>> <{a8aabf3a-4467-4e37-9bc5-48b1d7b494a2}_LATAM_RedHat.jpg>
>>
>> Better technology. Faster innovation. Powered by community collaboration.
>> See how it works at www.redhat.com
>>
>> <linkedin.png> <youtube.png>
11 years, 5 months
Re: [jbosstools-dev] [Soa-tools-list] JBTIS: Managment of External Components
by Max Rydahl Andersen
(adding jbosstools-dev to this since think it applies to both soa and
core)
> I think this could also apply to the BPEL component as well, but I
> don't remember if we create a feature around that in JBT or if we pull
> the feature from Eclipse.
So i'm open to suggestions on how to improve this but lets not go change
the TP process on a whim just yet.
We have recently got similar challenge in jbosstools core recently with
Eclipse Thym which is receiving more often updates than in past.
For now we have added an exemption to allow TP updates to be smoother
see
https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/targ...
(basically if just update to existing TP units owned by a project we
know/control the full TP process update is not required)
Now, back to the reason why we have them as TP entries as opposed to
other components is a few:
a) to make sure we have a download.jboss.org mirror since eclipse
mirrors are unreliable/slower (especially for people outside US)
b) it is to ensure we are not just using the "master"/nightly builds of
external dependencies
c) it is to ensure we do not drag in transitive dependencies from
eclipse.org component updatesites which (at least in the past) have had
lots of updatesite references to mix of p2 sites that resulted in
duplicated dependencies and/or wrong/non-deterministic p2 resolution
(because the updatessites
was one of a or b)
d) the eclipse.org parts tend to participate in the eclipse release
train - thus (for simplicity) using them via TP makes it easier to track
e) finally it is there to ensure we don't see a drift in multiple
modules adding different versions into their dependency/build chain.
(For core that is less likely since we have jbosstools parent pom to at
least centralize where the various updatesites are located, but jbtis is
much more spread out...hence a TP seem more relevant?)
So that is the reasons...now ...does the bpmn2 and bpel parts receive
many active updates that makes it non-feasible just including updates
via the "normal" TP update process ?
..and/or are there some hidden burdens in this that might not be visible
?
/max
>
> ----- Original Message -----
>>
>> +1!
>>
>> reducing the TP complexity is certainly a good idea - can we get a
>> show of
>> virtual hands who in IS component land actually pulls the BPMN2
>> modeler
>> from the JBTIS TP??
>>
>> --paull
>>
>>
>>
>> ----- Original Message -----
>>> From: "Rob Cernich" <rcernich(a)redhat.com>
>>> To: "soa-tools-list" <soa-tools-list(a)redhat.com>
>>> Sent: Wednesday, August 27, 2014 3:13:31 PM
>>> Subject: [Soa-tools-list] JBTIS: Managment of External Components
>>>
>>> Hey all,
>>>
>>> The recent update of BPMN2 modeller caused me to think about the way
>>> we
>>> handle components that come from external sources. To me, it makes
>>> sense
>>> if
>>> we treat these components the same way we treat our internal
>>> components.
>>> If
>>> we were to do that, these components would no longer be part of the
>>> JBTIS
>>> target platform and would instead be part of the features list
>>> described in
>>> the jbosstools and devstudio modules.
>>>
>>> In my opinion, this is a better way to treat these types of
>>> dependencies as
>>> they are components in their own right (i.e. no different than
>>> SwitchYard
>>> or
>>> Teiid, e.g.). If they are also dependencies used by other
>>> components, they
>>> would need to be managed by those other components using the same
>>> mechanism
>>> used to reference other internal component dependencies (e.g. SAVARA
>>> and
>>> SwitchYard). (SwitchYard actually references the BPMN2 repository
>>> directly
>>> specifically to avoid circularities within the tp/repo chain; i.e.
>>> SwitchYard does not require the TP be updated in order to update
>>> BPMN2
>>> modeller).
>>>
>>> Just an idea.
>>>
>>> Rob
>>>
>>> _______________________________________________
>>> Soa-tools-list mailing list
>>> Soa-tools-list(a)redhat.com
>>> https://www.redhat.com/mailman/listinfo/soa-tools-list
>>>
>>
>
> _______________________________________________
> Soa-tools-list mailing list
> Soa-tools-list(a)redhat.com
> https://www.redhat.com/mailman/listinfo/soa-tools-list
/max
http://about.me/maxandersen
11 years, 6 months
Please test AngularJS Eclipse 0.5.0-SNAPSHOT
by Angelo zerr
Hi all,
I have done a big refactoring for AngularJS Eclipse 0.5.0-SNAPSHOT to
support highlight inside HTML and JSP (or other editor) and custom markup
interpolation by removing my custom DOM Document for Angular. Now I use
standard DOM SSE Document (So I have remove the AngularJS too).
You can see those features at
https://github.com/angelozerr/angularjs-eclipse/wiki/New-and-Noteworthy-0...
Before cleaning my code by removing the custm DOM Document for Angular (for
the moment I have marked the code as deprecated), I would like to know if
some people could test AngularJS Eclipse 0.5.0-SNAPSHOT (check that
highlight, completion, hover, hyperlink works inside angular expression
inside HTML and JSP).
Many thank's for your help.
Hope you will like this new features.
Regard's Angelo
11 years, 6 months
Fwd: [m2e-dev] any swt/gtk experts around?
by Fred Bricon
---------- Message transféré ----------
De : "Igor Fedorenko" <igor(a)ifedorenko.com>
Date : 29 août 2014 09:32
Objet : [m2e-dev] any swt/gtk experts around?
À : "Maven Integration for Eclipse developers mailing list" <
m2e-dev(a)eclipse.org>
Cc :
Few m2e tests started to fail recently on our CI system. These
particular tests require Eclipse Workbench, which apparently fails to
start due to some SWT/GTK misconfiguration. The same tests pass on my
OSX laptop and Linux desktop, so the problem must be with our CI system,
which runs centos 6.5, btw.
The CI system has GTK2 libraries installed, but forcing SWT_GTK3=0 does
not make any difference.
I see the exception below when I enable SWT debug log, but this does not
tell me anything.
Has anyone seen this kind of problem before? Any suggestions how to
troubleshoot this further?
java.lang.Error
at org.eclipse.swt.graphics.Device.logProc(Device.java:755)
at org.eclipse.swt.internal.gtk.OS._gtk_container_add(Native Method)
at org.eclipse.swt.internal.gtk.OS.gtk_container_add(OS.java:7142)
at org.eclipse.swt.widgets.Composite.createHandle(
Composite.java:317)
at org.eclipse.swt.widgets.Shell.createHandle(Shell.java:727)
at org.eclipse.swt.widgets.Widget.createWidget(Widget.java:422)
at org.eclipse.swt.widgets.Control.createWidget(Control.java:666)
at org.eclipse.swt.widgets.Scrollable.createWidget(
Scrollable.java:153)
at org.eclipse.swt.widgets.Decorations.createWidget(
Decorations.java:245)
at org.eclipse.swt.widgets.Shell.<init>(Shell.java:282)
at org.eclipse.swt.widgets.Shell.<init>(Shell.java:360)
at org.eclipse.ui.internal.quickaccess.SearchField.
createWidget(SearchField.java:201)
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.eclipse.e4.core.internal.di.MethodRequestor.execute(
MethodRequestor.java:55)
at org.eclipse.e4.core.internal.di.InjectorImpl.
processAnnotated(InjectorImpl.java:888)
at org.eclipse.e4.core.internal.di.InjectorImpl.inject(
InjectorImpl.java:120)
at org.eclipse.e4.core.internal.di.InjectorImpl.internalMake(
InjectorImpl.java:337)
at org.eclipse.e4.core.internal.di.InjectorImpl.make(
InjectorImpl.java:271)
at org.eclipse.e4.core.contexts.ContextInjectionFactory.make(
ContextInjectionFactory.java:186)
at org.eclipse.e4.ui.internal.workbench.
ReflectionContributionFactory.createFromBundle(
ReflectionContributionFactory.java:107)
at org.eclipse.e4.ui.internal.workbench.
ReflectionContributionFactory.doCreate(ReflectionContributionFactory.
java:73)
at org.eclipse.e4.ui.internal.workbench.
ReflectionContributionFactory.create(ReflectionContributionFactory.java:50)
at org.eclipse.e4.ui.workbench.renderers.swt.ToolControlRenderer.
createWidget(ToolControlRenderer.java:108)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.
createWidget(PartRenderingEngine.java:983)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.
safeCreateGui(PartRenderingEngine.java:662)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.
safeCreateGui(PartRenderingEngine.java:766)
at org.eclipse.e4.ui.internal.workbench.swt.
PartRenderingEngine.access$2(PartRenderingEngine.java:737)
at org.eclipse.e4.ui.internal.workbench.swt.
PartRenderingEngine$7.run(PartRenderingEngine.java:731)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.e4.ui.internal.workbench.swt.
PartRenderingEngine.createGui(PartRenderingEngine.java:715)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.
handleEvent(PartRenderingEngine.java:289)
at org.eclipse.e4.ui.services.internal.events.UIEventHandler$1.run(
UIEventHandler.java:40)
at org.eclipse.swt.widgets.Synchronizer.syncExec(
Synchronizer.java:187)
at org.eclipse.ui.internal.UISynchronizer.syncExec(
UISynchronizer.java:156)
at org.eclipse.swt.widgets.Display.syncExec(Display.java:4622)
at org.eclipse.e4.ui.internal.workbench.swt.E4Application$1.
syncExec(E4Application.java:218)
at org.eclipse.e4.ui.services.internal.events.
UIEventHandler.handleEvent(UIEventHandler.java:36)
at org.eclipse.equinox.internal.event.EventHandlerWrapper.
handleEvent(EventHandlerWrapper.java:197)
at org.eclipse.equinox.internal.event.EventHandlerTracker.
dispatchEvent(EventHandlerTracker.java:197)
at org.eclipse.equinox.internal.event.EventHandlerTracker.
dispatchEvent(EventHandlerTracker.java:1)
at org.eclipse.osgi.framework.eventmgr.EventManager.
dispatchEvent(EventManager.java:230)
at org.eclipse.osgi.framework.eventmgr.ListenerQueue.
dispatchEventSynchronous(ListenerQueue.java:148)
at org.eclipse.equinox.internal.event.EventAdminImpl.
dispatchEvent(EventAdminImpl.java:135)
at org.eclipse.equinox.internal.event.EventAdminImpl.
sendEvent(EventAdminImpl.java:78)
at org.eclipse.equinox.internal.event.EventComponent.
sendEvent(EventComponent.java:39)
at org.eclipse.e4.ui.services.internal.events.EventBroker.
send(EventBroker.java:81)
at org.eclipse.e4.ui.internal.workbench.UIEventPublisher.
notifyChanged(UIEventPublisher.java:59)
at org.eclipse.emf.common.notify.impl.BasicNotifierImpl.
eNotify(BasicNotifierImpl.java:374)
at org.eclipse.emf.ecore.util.EcoreEList.dispatchNotification(
EcoreEList.java:249)
at org.eclipse.emf.common.notify.impl.NotifyingListImpl.
addUnique(NotifyingListImpl.java:356)
at org.eclipse.emf.common.util.AbstractEList.add(
AbstractEList.java:341)
at org.eclipse.e4.ui.internal.workbench.ContributionsAnalyzer.
processAddition(ContributionsAnalyzer.java:369)
at org.eclipse.e4.ui.workbench.renderers.swt.TrimBarRenderer.
addTrimContributions(TrimBarRenderer.java:194)
at org.eclipse.e4.ui.workbench.renderers.swt.TrimBarRenderer.
processContents(TrimBarRenderer.java:166)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.
safeCreateGui(PartRenderingEngine.java:674)
at org.eclipse.e4.ui.internal.workbench.swt.
PartRenderingEngine$6.run(PartRenderingEngine.java:547)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.e4.ui.internal.workbench.swt.
PartRenderingEngine.createGui(PartRenderingEngine.java:531)
at org.eclipse.e4.ui.workbench.renderers.swt.WBWRenderer.
processContents(WBWRenderer.java:687)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.
safeCreateGui(PartRenderingEngine.java:674)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.
safeCreateGui(PartRenderingEngine.java:766)
at org.eclipse.e4.ui.internal.workbench.swt.
PartRenderingEngine.access$2(PartRenderingEngine.java:737)
at org.eclipse.e4.ui.internal.workbench.swt.
PartRenderingEngine$7.run(PartRenderingEngine.java:731)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.e4.ui.internal.workbench.swt.
PartRenderingEngine.createGui(PartRenderingEngine.java:715)
at org.eclipse.e4.ui.internal.workbench.swt.
PartRenderingEngine$9.run(PartRenderingEngine.java:1074)
at org.eclipse.core.databinding.observable.Realm.
runWithDefault(Realm.java:332)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(
PartRenderingEngine.java:1032)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.
createAndRunUI(E4Workbench.java:148)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636)
at org.eclipse.core.databinding.observable.Realm.
runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(
Workbench.java:579)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(
PlatformUI.java:150)
at org.eclipse.ui.internal.ide.application.IDEApplication.
start(IDEApplication.java:135)
at org.eclipse.tycho.surefire.osgibooter.UITestApplication.
runApplication(UITestApplication.java:31)
at org.eclipse.tycho.surefire.osgibooter.
AbstractUITestApplication.run(AbstractUITestApplication.java:115)
at org.eclipse.tycho.surefire.osgibooter.UITestApplication.
start(UITestApplication.java:37)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(
EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.
runApplication(EclipseAppLauncher.java:134)
at org.eclipse.core.runtime.internal.adaptor.
EclipseAppLauncher.start(EclipseAppLauncher.java:104)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(
EclipseStarter.java:382)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(
EclipseStarter.java:236)
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.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
at org.eclipse.equinox.launcher.Main.main(Main.java:1438)
--
Regards,
Igor
_______________________________________________
m2e-dev mailing list
m2e-dev(a)eclipse.org
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/m2e-dev
11 years, 6 months
