[JBoss JIRA] (JBIDE-12108) BrowserSim is not visible in Quick Access by default when installed individually
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12108?page=com.atlassian.jira.plugi... ]
Ilya Buziuk commented on JBIDE-12108:
-------------------------------------
[~maxandersen], PR was sent - https://github.com/jbosstools/jbosstools-browsersim/pull/64
> BrowserSim is not visible in Quick Access by default when installed individually
> --------------------------------------------------------------------------------
>
> Key: JBIDE-12108
> URL: https://issues.jboss.org/browse/JBIDE-12108
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: browsersim
> Affects Versions: 3.3.0.CR1
> Environment: JBT 3.3.0.CR1b, L64, Ubuntu 12.04
> Reporter: Jiri Peterka
> Assignee: Ilya Buziuk
> Fix For: 4.3.0.Beta1
>
> Attachments: browsersim-enabled.png, customize-perspective.png, enable-browsersim.png, mobile-browser.bmp
>
>
> Unable to access BrowserSIM when installed as single feature from JBT CR1. Additional steps are required. This is confusing for a users. BrowserSIM should be accessible and visible after installation if possible.
> *These additional steps are:*
> # Right click on the Eclipse toolbar→Customize Perspective...:
> !customize-perspective.png!
> # Go to the Command Group Availability tab and select BrowserSim command group:
> !enable-browsersim.png!
> # BrowserSim icon will appear on the toolbar:
> !browsersim-enabled.png!
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-19369) Disposer method doesnt detect Producer field
by Rastislav Wagner (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19369?page=com.atlassian.jira.plugi... ]
Rastislav Wagner closed JBIDE-19369.
------------------------------------
verified in JBDS 9.0.0.Alpha2-v20150420-1747-B24
> Disposer method doesnt detect Producer field
> --------------------------------------------
>
> Key: JBIDE-19369
> URL: https://issues.jboss.org/browse/JBIDE-19369
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi
> Affects Versions: 4.3.0.Alpha1
> Reporter: Rastislav Wagner
> Assignee: Viacheslav Kabanovich
> Fix For: 4.3.0.Alpha2
>
>
> This applies for CDI 1.1 and 1.2 which allows Disposer method to accept Producer field.
> {code}
> public class B1 {
>
> @Produces EntityManager em;
>
> public void test(@Disposes EntityManager em){
> //do smt
> }
> {code}
> This code results in error "There is no producer method declared by the (same) bean class that is assignable to the disposed parameter of a disposer method [JSR-346 §3.5.3]"
> CDI 1.1 and 1.2 allows also producer filed (see section 3.5)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-18772) Include publish.sh in parent pom as versioned maven dependency
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18772?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-18772:
------------------------------------
build-sites and product both use the parent pom, because they inherit a ton of variables from there, including target platform definitions and URLs for upstream projects.
So... you're wrong there. (But you're right about targetplatforms-matrix - it doesn't use the parent pom.)
But as long as this new system employs a profile to fire rsync using default params, I'm *not -1* on using this new mojo approach.
We'll just need to encode all the stuff I have in the Jenkins configs for aggregates, target platforms, discovery, browsersim-standalone, and product builds into <ugly><xml><blocks> instead of `simple shell`, but hey, that's the price of portability. :D
> Include publish.sh in parent pom as versioned maven dependency
> --------------------------------------------------------------
>
> Key: JBIDE-18772
> URL: https://issues.jboss.org/browse/JBIDE-18772
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build
> Reporter: Max Rydahl Andersen
> Assignee: Mickael Istria
> Priority: Critical
> Fix For: 4.3.0.Beta1
>
>
> instead of relying to publish.sh being on master, we should use a versioned publish.sh (or maybe even mojo) that the build then uses.
> suggestion:
> publish.sh (or mojo) gets released to our maven repo, use it in the pom.xml to perform publishing.
> What this helps with is:
> a) can do changes to publish mechanism without affecting every past builds.
> b) more movable build system
> c) isolated testing possible
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-19687) Web Service wizard buttons act strangely if an error occurs creating CXF service
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19687?page=com.atlassian.jira.plugi... ]
Xavier Coulon reassigned JBIDE-19687:
-------------------------------------
Assignee: Brian Fitzpatrick
> Web Service wizard buttons act strangely if an error occurs creating CXF service
> --------------------------------------------------------------------------------
>
> Key: JBIDE-19687
> URL: https://issues.jboss.org/browse/JBIDE-19687
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.3.0.Alpha2
> Environment: Fedora 20 x64, openjdk 1.7.0_75
> Reporter: Jan Richter
> Assignee: Brian Fitzpatrick
>
> Trying to create a bottom up Apache CXF web service. If after the "Apache CXF Wbe Service Java2WS Configuration" step an error occurs, the "back" and "next" buttons stop behaving in the expected fashion.
> So far I've found these cases:
> - The back button will loop through the last 3 pages of the wizard, while pressing "next" on any of these pages will return you to the first page.
> - You can return with the back button, but pressing next will open an error dialog with the same message as the original error.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-19605) Avoid need for multiple javax.servlet
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19605?page=com.atlassian.jira.plugi... ]
Xavier Coulon commented on JBIDE-19605:
---------------------------------------
[~bfitzpat],
can you take a look at this issue ? It's related to the org.jboss.tools.ws.ui bundle.
thanks !
> Avoid need for multiple javax.servlet
> -------------------------------------
>
> Key: JBIDE-19605
> URL: https://issues.jboss.org/browse/JBIDE-19605
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: target-platform, webservices
> Affects Versions: 4.3.0.Alpha2
> Reporter: Mickael Istria
> Assignee: Brian Fitzpatrick
>
> We currently use 2 different version of javax.servlet bundle. We'd rather decide on sticking to 1.
> {code}
> On 04/15/2015 11:56 PM, Nick Boldt wrote:
> > Just wondering if anyone knows WHY we include javax.servlet 3.0.0 and
> > 3.1.0 in JBDS.
> > More importantly... SHOULD we be including both? Or can we just include
> > 3.1.0 and drop 3.0.0?
> I have JBDS installed from installer, which basically ran a p2 director. And I get jetty 3.0.0 and jetty 3.1.0. Than means that while resolving what to installed, p2 has to keep both versions of javax.servlet. That's definitely a sign that our dependency chain currently need both (or p2 wouldn't have installed both).
> So I've tried the ultimate test:
> $ cd jbdevstudio-9.0.0.Alpha2/studio
> $ rm plugins/javax.servlet_3.0.0*
> $ ./jbdevstudio
> And saw
> !ENTRY org.jboss.tools.ws.ui 4 0 2015-04-16 10:35:49.110
> !MESSAGE FrameworkEvent ERROR
> !STACK 0
> org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.ws.ui [967]
> Unresolved requirement: Import-Package: javax.servlet; version="[2.4.0,3.0.0)"
> at org.eclipse.osgi.container.Module.start(Module.java:434)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1582)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1561)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1533)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1476)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
> at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
> at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
> Fun thing is that the javax.servlet_3.0.0 actually exports packages in version 2.6.0, whereas javax.servlet_3.1.0 exports them in version 3.1.0.
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-19605) Avoid need for multiple javax.servlet
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19605?page=com.atlassian.jira.plugi... ]
Xavier Coulon reassigned JBIDE-19605:
-------------------------------------
Assignee: Xavier Coulon
> Avoid need for multiple javax.servlet
> -------------------------------------
>
> Key: JBIDE-19605
> URL: https://issues.jboss.org/browse/JBIDE-19605
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: target-platform, webservices
> Affects Versions: 4.3.0.Alpha2
> Reporter: Mickael Istria
> Assignee: Xavier Coulon
>
> We currently use 2 different version of javax.servlet bundle. We'd rather decide on sticking to 1.
> {code}
> On 04/15/2015 11:56 PM, Nick Boldt wrote:
> > Just wondering if anyone knows WHY we include javax.servlet 3.0.0 and
> > 3.1.0 in JBDS.
> > More importantly... SHOULD we be including both? Or can we just include
> > 3.1.0 and drop 3.0.0?
> I have JBDS installed from installer, which basically ran a p2 director. And I get jetty 3.0.0 and jetty 3.1.0. Than means that while resolving what to installed, p2 has to keep both versions of javax.servlet. That's definitely a sign that our dependency chain currently need both (or p2 wouldn't have installed both).
> So I've tried the ultimate test:
> $ cd jbdevstudio-9.0.0.Alpha2/studio
> $ rm plugins/javax.servlet_3.0.0*
> $ ./jbdevstudio
> And saw
> !ENTRY org.jboss.tools.ws.ui 4 0 2015-04-16 10:35:49.110
> !MESSAGE FrameworkEvent ERROR
> !STACK 0
> org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.ws.ui [967]
> Unresolved requirement: Import-Package: javax.servlet; version="[2.4.0,3.0.0)"
> at org.eclipse.osgi.container.Module.start(Module.java:434)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1582)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1561)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1533)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1476)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
> at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
> at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
> Fun thing is that the javax.servlet_3.0.0 actually exports packages in version 2.6.0, whereas javax.servlet_3.1.0 exports them in version 3.1.0.
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-19605) Avoid need for multiple javax.servlet
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19605?page=com.atlassian.jira.plugi... ]
Xavier Coulon reassigned JBIDE-19605:
-------------------------------------
Assignee: Brian Fitzpatrick (was: Xavier Coulon)
> Avoid need for multiple javax.servlet
> -------------------------------------
>
> Key: JBIDE-19605
> URL: https://issues.jboss.org/browse/JBIDE-19605
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: target-platform, webservices
> Affects Versions: 4.3.0.Alpha2
> Reporter: Mickael Istria
> Assignee: Brian Fitzpatrick
>
> We currently use 2 different version of javax.servlet bundle. We'd rather decide on sticking to 1.
> {code}
> On 04/15/2015 11:56 PM, Nick Boldt wrote:
> > Just wondering if anyone knows WHY we include javax.servlet 3.0.0 and
> > 3.1.0 in JBDS.
> > More importantly... SHOULD we be including both? Or can we just include
> > 3.1.0 and drop 3.0.0?
> I have JBDS installed from installer, which basically ran a p2 director. And I get jetty 3.0.0 and jetty 3.1.0. Than means that while resolving what to installed, p2 has to keep both versions of javax.servlet. That's definitely a sign that our dependency chain currently need both (or p2 wouldn't have installed both).
> So I've tried the ultimate test:
> $ cd jbdevstudio-9.0.0.Alpha2/studio
> $ rm plugins/javax.servlet_3.0.0*
> $ ./jbdevstudio
> And saw
> !ENTRY org.jboss.tools.ws.ui 4 0 2015-04-16 10:35:49.110
> !MESSAGE FrameworkEvent ERROR
> !STACK 0
> org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.ws.ui [967]
> Unresolved requirement: Import-Package: javax.servlet; version="[2.4.0,3.0.0)"
> at org.eclipse.osgi.container.Module.start(Module.java:434)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1582)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1561)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1533)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1476)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
> at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
> at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
> Fun thing is that the javax.servlet_3.0.0 actually exports packages in version 2.6.0, whereas javax.servlet_3.1.0 exports them in version 3.1.0.
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-19699) jpa new entity: java.lang.IllegalArgumentException
by Pavol Srna (JIRA)
Pavol Srna created JBIDE-19699:
----------------------------------
Summary: jpa new entity: java.lang.IllegalArgumentException
Key: JBIDE-19699
URL: https://issues.jboss.org/browse/JBIDE-19699
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: forge
Affects Versions: 4.3.0.Alpha2
Environment: forge 2.16.0
Reporter: Pavol Srna
Fix For: 4.3.0.Beta1
{code}
org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.IllegalArgumentException)
at org.eclipse.swt.SWT.error(SWT.java:4481)
at org.eclipse.swt.SWT.error(SWT.java:4396)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:139)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3997)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3674)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:827)
at org.eclipse.jface.window.Window.open(Window.java:803)
at org.jboss.tools.forge.ui.internal.ext.dialog.WizardDialogHelper.openWizard(WizardDialogHelper.java:210)
at org.jboss.tools.forge.ui.internal.ext.dialog.WizardDialogHelper.openWizard(WizardDialogHelper.java:102)
at org.jboss.tools.forge.ui.internal.ext.dialog.UICommandListDialog$1$1.handleElementSelected(UICommandListDialog.java:233)
at org.jboss.tools.forge.ui.internal.ext.quickaccess.QuickAccessContents.handleSelection(QuickAccessContents.java:322)
at org.jboss.tools.forge.ui.internal.ext.quickaccess.QuickAccessContents.access$0(QuickAccessContents.java:312)
at org.jboss.tools.forge.ui.internal.ext.quickaccess.QuickAccessContents$1.keyPressed(QuickAccessContents.java:343)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:167)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4203)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1467)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1490)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1475)
at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1504)
at org.eclipse.swt.widgets.Text.sendKeyEvent(Text.java:1634)
at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1500)
at org.eclipse.swt.widgets.Text.sendKeyEvent(Text.java:1600)
at org.eclipse.swt.widgets.Control.doCommandBySelector(Control.java:1060)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:5757)
at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method)
at org.eclipse.swt.widgets.Widget.callSuper(Widget.java:221)
at org.eclipse.swt.widgets.Widget.superKeyDown(Widget.java:1908)
at org.eclipse.swt.widgets.Widget.keyDown(Widget.java:1085)
at org.eclipse.swt.widgets.Control.keyDown(Control.java:2406)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:5667)
at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method)
at org.eclipse.swt.widgets.Widget.callSuper(Widget.java:221)
at org.eclipse.swt.widgets.Widget.windowSendEvent(Widget.java:2105)
at org.eclipse.swt.widgets.Shell.windowSendEvent(Shell.java:2337)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:5729)
at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method)
at org.eclipse.swt.widgets.Display.applicationSendEvent(Display.java:5166)
at org.eclipse.swt.widgets.Display.applicationProc(Display.java:5315)
at org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method)
at org.eclipse.swt.internal.cocoa.NSApplication.sendEvent(NSApplication.java:128)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3669)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1112)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:993)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138)
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:380)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:483)
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)
Caused by: java.lang.IllegalArgumentException
at org.jboss.forge.roaster._shade.org.eclipse.jdt.core.dom.AST.newName(AST.java:1938)
at org.jboss.forge.roaster.model.impl.AbstractJavaSource.setPackage(AbstractJavaSource.java:521)
at org.jboss.forge.roaster.model.impl.AbstractJavaSource.setPackage(AbstractJavaSource.java:56)
at org.jboss.forge.addon.parser.java.ui.AbstractJavaSourceCommand.buildJavaSource(AbstractJavaSourceCommand.java:192)
at org.jboss.forge.addon.parser.java.ui.AbstractJavaSourceCommand.classExists(AbstractJavaSourceCommand.java:162)
at org.jboss.forge.addon.parser.java.ui.AbstractJavaSourceCommand.access$100(AbstractJavaSourceCommand.java:58)
at org.jboss.forge.addon.parser.java.ui.AbstractJavaSourceCommand$2.call(AbstractJavaSourceCommand.java:100)
at org.jboss.forge.addon.parser.java.ui.AbstractJavaSourceCommand$2.call(AbstractJavaSourceCommand.java:92)
at org.jboss.forge.furnace.util.Callables.call(Callables.java:43)
at org.jboss.forge.addon.ui.impl.input.AbstractInputComponent.isEnabled(AbstractInputComponent.java:99)
at sun.reflect.GeneratedMethodAccessor319.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:483)
at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor$1.call(ClassLoaderInterceptor.java:87)
at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42)
at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor.invoke(ClassLoaderInterceptor.java:103)
at org.jboss.forge.addon.facets.AbstractFaceted_$$_javassist_73339967-8f00-406f-8f86-d626f933e158.isEnabled(AbstractFaceted_$$_javassist_73339967-8f00-406f-8f86-d626f933e158.java)
at sun.reflect.GeneratedMethodAccessor325.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:483)
at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback$2.call(ClassLoaderAdapterCallback.java:123)
at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42)
at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.invoke(ClassLoaderAdapterCallback.java:96)
at org.jboss.forge.addon.facets.AbstractFaceted_$$_javassist_58de67b1-36c3-4a0d-b29d-b8b860d2a3f0.isEnabled(AbstractFaceted_$$_javassist_58de67b1-36c3-4a0d-b29d-b8b860d2a3f0.java)
at org.jboss.tools.forge.ui.internal.ext.control.ControlBuilder.updateState(ControlBuilder.java:192)
at org.jboss.tools.forge.ui.internal.ext.wizards.ForgeWizardPage.updatePageState(ForgeWizardPage.java:203)
at org.jboss.tools.forge.ui.internal.ext.wizards.ForgeWizardPage.validatePage(ForgeWizardPage.java:237)
at org.jboss.tools.forge.ui.internal.ext.wizards.ForgeWizardPage.access$5(ForgeWizardPage.java:233)
at org.jboss.tools.forge.ui.internal.ext.wizards.ForgeWizardPage$1$1.run(ForgeWizardPage.java:180)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136)
... 60 more
{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-15884) Allow the runBrowserSim command to accept a URL as a parameter
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15884?page=com.atlassian.jira.plugi... ]
Ilya Buziuk commented on JBIDE-15884:
-------------------------------------
[~maxandersen], do you mean 2 commands (with and without vpe prefix) ? yes we can keep both them but the commands will be duplicated in Quick Access I think.
> Allow the runBrowserSim command to accept a URL as a parameter
> --------------------------------------------------------------
>
> Key: JBIDE-15884
> URL: https://issues.jboss.org/browse/JBIDE-15884
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: browsersim
> Affects Versions: 4.1.0.Final
> Reporter: Vineet Reynolds
> Assignee: Ilya Buziuk
> Priority: Minor
> Fix For: 4.3.0.Beta1
>
>
> Apologies for not setting the Affect version; I'm not sure which JBIDE version is affected.
> When creating a cheatsheet in JBDS 7.0.1.GA (for JDF-497), I'm using the {{org.jboss.tools.vpe.browsersim.eclipse.commands.runBrowserSim}} command in the cheatsheet. This launches BrowserSim successfully (when I'm in the correct perspective). However, BrowserSim navigates to about:blank so the cheatsheet requires users to manually key in the URL. It would be nice to have the launch URL specified as a configurable value.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-19654) Application wizard: Opening the wizard on an account without SSH key opens broken wizard
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19654?page=com.atlassian.jira.plugi... ]
Andre Dietisheim reassigned JBIDE-19654:
----------------------------------------
Assignee: Andre Dietisheim (was: Marián Labuda)
> Application wizard: Opening the wizard on an account without SSH key opens broken wizard
> ----------------------------------------------------------------------------------------
>
> Key: JBIDE-19654
> URL: https://issues.jboss.org/browse/JBIDE-19654
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Alpha2
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Labels: application_wizard
> Fix For: 4.3.0.Beta1
>
> Attachments: new_app_wizard.png, prompt-to-upload-keys.png
>
>
> If user is opening a New application wizard from domain (context menu on domain item in OpenShift explorer) or shell menu (File - New - OpenShift Application) and there is no SSH key related to v2 account, the wizard is opened directly and cartridge/quickstart selection is empty
> !new_app_wizard.png!
> There should be at first opened SSH Key wizard/dialog to let the user add a SSH key to the account and then it should proceed to New application wizard (this is how it worked. Currently it's working like this only on New application wizard opened via context menu of a connection).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-19654) Application wizard: Opening the wizard on an account without SSH key opens broken wizard
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19654?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-19654:
-------------------------------------
Fix Version/s: 4.3.0.Beta1
> Application wizard: Opening the wizard on an account without SSH key opens broken wizard
> ----------------------------------------------------------------------------------------
>
> Key: JBIDE-19654
> URL: https://issues.jboss.org/browse/JBIDE-19654
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Alpha2
> Reporter: Marián Labuda
> Assignee: Marián Labuda
> Labels: application_wizard
> Fix For: 4.3.0.Beta1
>
> Attachments: new_app_wizard.png, prompt-to-upload-keys.png
>
>
> If user is opening a New application wizard from domain (context menu on domain item in OpenShift explorer) or shell menu (File - New - OpenShift Application) and there is no SSH key related to v2 account, the wizard is opened directly and cartridge/quickstart selection is empty
> !new_app_wizard.png!
> There should be at first opened SSH Key wizard/dialog to let the user add a SSH key to the account and then it should proceed to New application wizard (this is how it worked. Currently it's working like this only on New application wizard opened via context menu of a connection).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-19654) Application wizard: Opening the wizard on an account without SSH key opens broken wizard
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19654?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-19654:
------------------------------------------
[~mlabuda] ok, thx for verifying. I'll try to look into the code and see if it's possible that the application wizard would not react to timeouting ssh jobs and open up in an invalid state like it is shown in the above screenshot.
> Application wizard: Opening the wizard on an account without SSH key opens broken wizard
> ----------------------------------------------------------------------------------------
>
> Key: JBIDE-19654
> URL: https://issues.jboss.org/browse/JBIDE-19654
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Alpha2
> Reporter: Marián Labuda
> Assignee: Marián Labuda
> Labels: application_wizard
> Fix For: 4.3.0.Beta1
>
> Attachments: new_app_wizard.png, prompt-to-upload-keys.png
>
>
> If user is opening a New application wizard from domain (context menu on domain item in OpenShift explorer) or shell menu (File - New - OpenShift Application) and there is no SSH key related to v2 account, the wizard is opened directly and cartridge/quickstart selection is empty
> !new_app_wizard.png!
> There should be at first opened SSH Key wizard/dialog to let the user add a SSH key to the account and then it should proceed to New application wizard (this is how it worked. Currently it's working like this only on New application wizard opened via context menu of a connection).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-19401) remove Seam & Portlet from JBT 4.3 default install
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19401?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-19401:
---------------------------------------------
[~rhopp] please open separate bug about jboss maven portlet configurator dragging it in. It should basically just be part of the connector now - but seems that was missed.
> remove Seam & Portlet from JBT 4.3 default install
> ---------------------------------------------------
>
> Key: JBIDE-19401
> URL: https://issues.jboss.org/browse/JBIDE-19401
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: portal-gatein, seam2
> Affects Versions: 4.3.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.3.0.Alpha2
>
>
> Recently we removed Seams and Portlet from the default JBDS 9 install. Max said today we should do the same for JBT 4.3.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-19692) Connection wizard: URL history contains only URLs of already existing connections
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19692?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-19692:
-------------------------------------
Fix Version/s: 4.3.0.Beta1
> Connection wizard: URL history contains only URLs of already existing connections
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-19692
> URL: https://issues.jboss.org/browse/JBIDE-19692
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Alpha2
> Reporter: Marián Labuda
> Labels: connection_wizard
> Fix For: 4.3.0.Beta1
>
>
> URL Autocomplete/History feature implemented in JBIDE-19445 allows user to select only URLs of already existing connections (those present in OpenShift explorer view). Once the connection with some URL is removed from OpenShift explorer view, this URL is also removed from combo box of URL history.
> URL autocomplete/history should remember all URL of successfully established connections even after they removal from OpenShift explorer view.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-19691) Change description for AngularJS for Web Tools connector
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19691?page=com.atlassian.jira.plugi... ]
Fred Bricon reassigned JBIDE-19691:
-----------------------------------
Assignee: Nick Boldt
> Change description for AngularJS for Web Tools connector
> --------------------------------------------------------
>
> Key: JBIDE-19691
> URL: https://issues.jboss.org/browse/JBIDE-19691
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.3.0.Alpha2
> Reporter: Alexey Kazakov
> Assignee: Nick Boldt
> Fix For: 4.3.0.Beta1
>
>
> Now it's saying:
> "AngularJS Tooling support for ionic framework".
> This is not correct since we introduced our dynamic content assist for Angular expressions: JBIDE-15714.
> So, it's not about ionic only anymore.
> Let's change it to something like "AngularJS Tooling support providing content assist + ionic framework support".
> The description for the Early Access AngularJS connector is correct.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-15884) Allow the runBrowserSim command to accept a URL as a parameter
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15884?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-15884:
---------------------------------------------
ilya - that is not good. can we not keep both working ? it is not under our control which versions these cheatsheets are opened in.
> Allow the runBrowserSim command to accept a URL as a parameter
> --------------------------------------------------------------
>
> Key: JBIDE-15884
> URL: https://issues.jboss.org/browse/JBIDE-15884
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: browsersim
> Affects Versions: 4.1.0.Final
> Reporter: Vineet Reynolds
> Assignee: Ilya Buziuk
> Priority: Minor
> Fix For: 4.3.0.Beta1
>
>
> Apologies for not setting the Affect version; I'm not sure which JBIDE version is affected.
> When creating a cheatsheet in JBDS 7.0.1.GA (for JDF-497), I'm using the {{org.jboss.tools.vpe.browsersim.eclipse.commands.runBrowserSim}} command in the cheatsheet. This launches BrowserSim successfully (when I'm in the correct perspective). However, BrowserSim navigates to about:blank so the cheatsheet requires users to manually key in the URL. It would be nice to have the launch URL specified as a configurable value.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-19698) Dispatch selection in containers view
by Xavier Coulon (JIRA)
Xavier Coulon created JBIDE-19698:
-------------------------------------
Summary: Dispatch selection in containers view
Key: JBIDE-19698
URL: https://issues.jboss.org/browse/JBIDE-19698
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: docker
Affects Versions: 4.3.0.Alpha2
Reporter: Xavier Coulon
Assignee: Xavier Coulon
Fix For: 4.3.0.Beta1
When the selection changes in the container view, it should be broadcasted so that other views (Docker Explorer and Properties views) can react accordingly.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBDS-3363) Remove Portlet tooling from default JBDS installation
by Radim Hopp (JIRA)
[ https://issues.jboss.org/browse/JBDS-3363?page=com.atlassian.jira.plugin.... ]
Radim Hopp closed JBDS-3363.
----------------------------
I can confirm, that Portlet tooling is not in default installation of JBDS and it is installable via Central in JBDS 9.0.0.Alpha2. Closing.
> Remove Portlet tooling from default JBDS installation
> -----------------------------------------------------
>
> Key: JBDS-3363
> URL: https://issues.jboss.org/browse/JBDS-3363
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: central, installer, requirements
> Affects Versions: 9.0.0.Alpha1
> Reporter: Fred Bricon
> Assignee: Nick Boldt
> Fix For: 9.0.0.Alpha2
>
>
> Portlet tools currently has a hard dependency on Seam, which kinda bothers us with JBDS-3286.
> While severing this dependency is a WIP (JBIDE-19316), another question comes to mind : is portlet still necessary?
> It doesn't seem like a technology we're trying to promote, tooling has been in maintenance mode for months if not years. Is it not time to [let it go|https://www.youtube.com/watch?v=moSFlvxnbgk&t=56s]?
>
> [~burrsutter], [~maxandersen], [~ldimaggio], [~akazakov], [~mmurray], [~snjeza] : WDYT?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBDS-3286) Remove Seam tooling from default JBDS installation
by Radim Hopp (JIRA)
[ https://issues.jboss.org/browse/JBDS-3286?page=com.atlassian.jira.plugin.... ]
Radim Hopp closed JBDS-3286.
----------------------------
I can confirm, that Seam tooling is not in default installation of JBDS and it is installable via Central in JBDS 9.0.0.Alpha2. Closing.
> Remove Seam tooling from default JBDS installation
> --------------------------------------------------
>
> Key: JBDS-3286
> URL: https://issues.jboss.org/browse/JBDS-3286
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: central, installer, requirements, seam
> Affects Versions: 9.0.0.Alpha1
> Reporter: Fred Bricon
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 9.0.0.Alpha2
>
>
> With Seam being pretty much dead and the tools in maintenance mode, I'm opening this issue to discuss whether we should drop Seam from the JBDS installer and only keep it available from JBoss Central (required as part of JBIDE-18922 already).
> [~burrsutter], [~maxandersen], [~ldimaggio], [~akazakov], [~mmurray] : WDYT?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBTIS-418) Cannot install JBDS-IS from downloaded zip into JBDS when offline
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-418?page=com.atlassian.jira.plugin.... ]
Paul Leacu reassigned JBTIS-418:
--------------------------------
Assignee: Paul Leacu
> Cannot install JBDS-IS from downloaded zip into JBDS when offline
> -----------------------------------------------------------------
>
> Key: JBTIS-418
> URL: https://issues.jboss.org/browse/JBTIS-418
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: releng
> Affects Versions: 8.0.0.GA
> Environment: Linux x86_64 Open JDK 7
> JBDS 8.0.0.GA-v20141020-1042-B317
> JBDS IS 8.0.0.GA
> Reporter: Denis Golovin
> Assignee: Paul Leacu
>
> While was testing possible solutions for including JBDS IS into JBDS Installer I realized that there something missing in JBDS or IS zip. Offfline installation into JBDS 8.0.0.GA fails with
> {code}
> Cannot complete the install because one or more required items could not be found.
> Software being installed: JBoss Data Virtualization Development (ModeShape, Teiid Designer) 8.0.0.201502201745 (com.jboss.devstudio.integration-stack.ds.feature.feature.group 8.0.0.201502201745)
> Missing requirement: JBoss Data Virtualization Development (ModeShape, Teiid Designer) 8.0.0.201502201745 (com.jboss.devstudio.integration-stack.ds.feature.feature.group 8.0.0.201502201745) requires 'org.jboss.tools.usage.feature.feature.group 0.0.0' but it could not be found
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-18582) 4 errors while executing offline script
by Radim Hopp (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18582?page=com.atlassian.jira.plugi... ]
Radim Hopp closed JBIDE-18582.
------------------------------
Verified in JBDS 9.0.0.Alpha2
> 4 errors while executing offline script
> ---------------------------------------
>
> Key: JBIDE-18582
> URL: https://issues.jboss.org/browse/JBIDE-18582
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: project-examples
> Affects Versions: 4.2.0.CR2
> Reporter: Rastislav Wagner
> Assignee: Fred Bricon
> Fix For: 4.3.0.Alpha2
>
>
> {code}
> rawagner@rawagner:~/tmp/off$ groovy "/home/rawagner/files/RedHat/JBoss/JBDS/workspace/integration-tests-fork/.metadata/.plugins/org.jboss.tools.project.examples/offline/go_offline_2.0.0.CR2_v20141003_2212_B95.groovy" http://download.jboss.org/jbosstools/examples/project-examples-category-j... http://download.jboss.org/jbosstools/examples/project-examples-jbds80.Bet... http://download.jboss.org/jbosstools/examples/project-examples-shared-4.2... -q -e
> Quiet mode : true
> Descriptors : [http://download.jboss.org/jbosstools/examples/project-examples-category-j..., http://download.jboss.org/jbosstools/examples/project-examples-jbds80.Bet..., http://download.jboss.org/jbosstools/examples/project-examples-shared-4.2...]
> creating offline/.jbosstools/cache
> parsing http://download.jboss.org/jbosstools/examples/project-examples-category-j...
> parsing http://download.jboss.org/jbosstools/examples/project-examples-jbds80.Bet...
> [unzip] Expanding: /home/rawagner/tmp/off/offline/.jbosstools/cache/jbosstools/examples/4.2.0.GA/eap/jboss-helloworld-jms.zip into /home/rawagner/tmp/off/offline/workDir/jboss-helloworld-jms.zip [unzip] Expanding: /home/rawagner/tmp/off/offline/.jbosstools/cache/jbosstools/examples/4.2.0.GA/wfk/jboss-kitchensink-html5-mobile.zip into /home/rawagner/tmp/off/offline/workDir/jboss-kitchensink-html5-mobile.zip
> [unzip] Expanding: /home/rawagner/tmp/off/offline/.jbosstools/cache/jbosstools/examples/4.2.0.GA/eap/jboss-helloworld.zip into /home/rawagner/tmp/off/offline/workDir/jboss-helloworld.zip
> [unzip] Expanding: /home/rawagner/tmp/off/offline/.jbosstools/cache/jbosstools/examples/4.2.0.GA/eap/jboss-numberguess.zip into /home/rawagner/tmp/off/offline/workDir/jboss-numberguess.zip
> [unzip] Expanding: /home/rawagner/tmp/off/offline/.jbosstools/cache/jbosstools/examples/4.2.0.GA/eap/jboss-helloworld-mdb.zip into /home/rawagner/tmp/off/offline/workDir/jboss-helloworld-mdb.zip
> [unzip] Expanding: /home/rawagner/tmp/off/offline/.jbosstools/cache/jbosstools/examples/4.2.0.GA/wfk/jboss-kitchensink-rf.zip into /home/rawagner/tmp/off/offline/workDir/jboss-kitchensink-rf.zip
> [unzip] Expanding: /home/rawagner/tmp/off/offline/.jbosstools/cache/jbosstools/examples/4.2.0.GA/eap/jboss-kitchensink.zip into /home/rawagner/tmp/off/offline/workDir/jboss-kitchensink.zip
> [unzip] Expanding: /home/rawagner/tmp/off/offline/.jbosstools/cache/jbosstools/examples/4.2.0.GA/wfk/jboss-kitchensink-backbone.zip into /home/rawagner/tmp/off/offline/workDir/jboss-kitchensink-backbone.zip
> [unzip] Expanding: /home/rawagner/tmp/off/offline/.jbosstools/cache/jbosstools/examples/4.2.0.GA/wfk/jboss-deltaspike-helloworld-jms.zip into /home/rawagner/tmp/off/offline/workDir/jboss-deltaspike-helloworld-jms.zip
> [unzip] Expanding: /home/rawagner/tmp/off/offline/.jbosstools/cache/jbosstools/examples/4.2.0.GA/eap/jboss-helloworld-rs.zip into /home/rawagner/tmp/off/offline/workDir/jboss-helloworld-rs.zip
> [unzip] Expanding: /home/rawagner/tmp/off/offline/.jbosstools/cache/jbosstools/examples/4.2.0.GA/eap/jboss-greeter.zip into /home/rawagner/tmp/off/offline/workDir/jboss-greeter.zip
> [unzip] Expanding: /home/rawagner/tmp/off/offline/.jbosstools/cache/jbosstools/examples/4.2.0.GA/wfk/jboss-kitchensink-angularjs.zip into /home/rawagner/tmp/off/offline/workDir/jboss-kitchensink-angularjs.zip
> [unzip] Expanding: /home/rawagner/tmp/off/offline/.jbosstools/cache/jbosstools/examples/4.2.0.GA/eap/jboss-jax-rs-client.zip into /home/rawagner/tmp/off/offline/workDir/jboss-jax-rs-client.zip
> [unzip] Expanding: /home/rawagner/tmp/off/offline/.jbosstools/cache/jbosstools/examples/contacts-mobile-basic/0.0.1/contacts-mobile.zip into /home/rawagner/tmp/off/offline/workDir/contacts-mobile.zip
> parsing http://download.jboss.org/jbosstools/examples/project-examples-shared-4.2...
> Building org.jboss.quickstarts.eap:jboss-helloworld-mdb:6.2.0.GA openshift
> [debug] execute contextualize
> Building org.jboss.quickstarts.eap:jboss-jax-rs-client:6.2.0.GA
> Building org.jboss.quickstarts.eap:jboss-helloworld:6.2.0.GA
> Building org.jboss.quickstarts.wfk:jboss-deltaspike-helloworld-jms:2.4.0.Final openshift
> Building org.jboss.quickstarts.wfk:jboss-kitchensink-html5-mobile:2.4.0.Final default,openshift,minify,arq-jbossas-managed
> Building org.jboss.quickstarts.wfk:jboss-kitchensink-html5-mobile:2.4.0.Final arq-jbossas-remote
> Building org.jboss.quickstarts.eap:jboss-numberguess:6.2.0.GA
> Building org.jboss.quickstarts.eap:jboss-kitchensink:6.2.0.GA default,arq-jbossas-managed,openshift
> Building org.jboss.quickstarts.eap:jboss-kitchensink:6.2.0.GA arq-jbossas-remote
> Building org.jboss.quickstarts.wfk:jboss-kitchensink-backbone:2.4.0.Final default,openshift,minify,arq-jbossas-managed,graph
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:2.1:resolve-plugins (resolve-plugins) on project jboss-kitchensink-backbone: Nested: Could not transfer artifact org.fusesource.mvnplugins:maven-graph-plugin:jar:1.0 from/to mvnplugins.fusesource.org (http://mvnplugins.fusesource.org/repo/release): Connection timed out
> [ERROR] org.fusesource.mvnplugins:maven-graph-plugin:maven-plugin:1.0
> [ERROR]
> [ERROR] from the specified remote repositories:
> [ERROR] mvnplugins.fusesource.org (http://mvnplugins.fusesource.org/repo/release, releases=true, snapshots=true),
> [ERROR] redhat-techpreview-all-repository (http://maven.repository.redhat.com/techpreview/all/, releases=true, snapshots=false),
> [ERROR] jboss-public-repository (https://repository.jboss.org/nexus/content/groups/public-jboss/, releases=true, snapshots=false),
> [ERROR] central (http://repo.maven.apache.org/maven2, releases=true, snapshots=false)
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> Result: 1
> Building org.jboss.quickstarts.wfk:jboss-kitchensink-backbone:2.4.0.Final arq-jbossas-remote
> Building org.jboss.quickstarts.eap:jboss-greeter:6.2.0.GA
> Building org.jboss.quickstarts.eap:jboss-helloworld-rs:6.2.0.GA openshift
> Building org.jboss.quickstarts.wfk:jboss-kitchensink-rf:2.4.0.Final default,arq-jbossas-managed,openshift,debug
> Building org.jboss.quickstarts.wfk:jboss-kitchensink-rf:2.4.0.Final arq-jbossas-remote
> Building org.jboss.quickstarts.wfk:jboss-kitchensink-angularjs:2.4.0.Final default,arq-jbossas-managed,openshift
> Building org.jboss.quickstarts.wfk:jboss-kitchensink-angularjs:2.4.0.Final arq-jbossas-remote
> Building org.jboss.quickstarts.eap:jboss-helloworld-jms:6.2.0.GA
> Building org.jboss.tools.example.html5:contacts-mobile-basic-services:0.0.1-SNAPSHOT default,openshift,minify,arq-jbossas-managed
> [ERROR] Failed to execute goal ro.isdc.wro4j:wro4j-maven-plugin:1.4.4:run (default) on project contacts-mobile-basic-services: Exception occured while processing: Exception while loading properties file from /home/rawagner/tmp/off/offline/workDir/contacts-mobile.zip/contacts-mobile-basic-services/src/main/webapp/WEB-INF/wro.properties: /home/rawagner/tmp/off/offline/workDir/contacts-mobile.zip/contacts-mobile-basic-services/src/main/webapp/WEB-INF/wro.properties (No such file or directory) -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> Result: 1
> Building org.jboss.tools.example.html5:contacts-mobile-basic-services:0.0.1-SNAPSHOT arq-jbossas-remote
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-archetype-plugin:2.2:generate (default-cli) on project standalone-pom: The desired archetype does not exist (org.jboss.tools.archetypes:jboss-forge-html5:1.0.0-SNAPSHOT) -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
> Result: 1
> offline/workDir/jboss-forge-html5/myapp.jboss-forge-html5/pom.xml can't be found. Skipping maven build
> Building org.jbosstoolsofflineexamples:my-jboss-javaee6-webapp-archetype:1.0.0-SNAPSHOT default,arq-jbossas-managed,openshift
> Building org.jbosstoolsofflineexamples:my-jboss-javaee6-webapp-archetype:1.0.0-SNAPSHOT arq-jbossas-remote
> Building org.jbosstoolsofflineexamples:my-jboss-javaee6-webapp-archetype:1.0.0-SNAPSHOT default,arq-jbossas-managed,openshift,jboss-product-repository
> Building org.jbosstoolsofflineexamples:my-jboss-javaee6-webapp-archetype:1.0.0-SNAPSHOT arq-jbossas-remote
> Building org.jbosstoolsofflineexamples:my-jboss-javaee6-webapp-blank-archetype:1.0.0-SNAPSHOT default,arq-jbossas-managed,openshift
> Building org.jbosstoolsofflineexamples:my-jboss-javaee6-webapp-blank-archetype:1.0.0-SNAPSHOT arq-jbossas-remote
> Building org.jbosstoolsofflineexamples:my-jboss-javaee6-webapp-blank-archetype:1.0.0-SNAPSHOT default,arq-jbossas-managed,openshift,jboss-product-repository
> Building org.jbosstoolsofflineexamples:my-jboss-javaee6-webapp-blank-archetype:1.0.0-SNAPSHOT arq-jbossas-remote
> Building org.jbosstoolsofflineexamples:my-jboss-javaee6-webapp-ear-archetype:1.0.0-SNAPSHOT
> Building org.jbosstoolsofflineexamples:my-jboss-javaee6-webapp-ear-archetype:1.0.0-SNAPSHOT jboss-product-repository
> Building org.jbosstoolsofflineexamples:my-jboss-javaee6-webapp-ear-blank-archetype:1.0.0-SNAPSHOT
> Building org.jbosstoolsofflineexamples:my-jboss-javaee6-webapp-ear-blank-archetype:1.0.0-SNAPSHOT jboss-product-repository
> Building org.jbosstoolsofflineexamples:my-jboss-html5-mobile-archetype:1.0.0-SNAPSHOT default,openshift,minify,arq-jbossas-managed
> Building org.jbosstoolsofflineexamples:my-jboss-html5-mobile-archetype:1.0.0-SNAPSHOT arq-jbossas-remote
> Building org.jbosstoolsofflineexamples:my-jboss-html5-mobile-archetype:1.0.0-SNAPSHOT default,openshift,minify,arq-jbossas-managed,jboss-product-repository
> Building org.jbosstoolsofflineexamples:my-jboss-html5-mobile-archetype:1.0.0-SNAPSHOT arq-jbossas-remote
> Building org.jbosstoolsofflineexamples:my-jboss-html5-mobile-blank-archetype:1.0.0-SNAPSHOT default,openshift,minify,arq-jbossas-managed,jboss-product-repository
> [ERROR] Failed to execute goal ro.isdc.wro4j:wro4j-maven-plugin:1.4.4:run (default) on project my-jboss-html5-mobile-blank-archetype: Exception occured while processing: Exception while loading properties file from /home/rawagner/tmp/off/offline/workDir/jboss-html5-mobile-blank-archetype/my-jboss-html5-mobile-blank-archetype/src/main/webapp/WEB-INF/wro.properties: /home/rawagner/tmp/off/offline/workDir/jboss-html5-mobile-blank-archetype/my-jboss-html5-mobile-blank-archetype/src/main/webapp/WEB-INF/wro.properties (No such file or directory) -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> Result: 1
> Building org.jbosstoolsofflineexamples:my-jboss-html5-mobile-blank-archetype:1.0.0-SNAPSHOT arq-jbossas-remote
> Building org.jbosstoolsofflineexamples:my-jboss-html5-mobile-archetype:1.0.0-SNAPSHOT default,openshift,minify,arq-jbossas-managed,jboss-product-repository
> Building org.jbosstoolsofflineexamples:my-jboss-html5-mobile-archetype:1.0.0-SNAPSHOT arq-jbossas-remote
> Building org.jbosstoolsofflineexamples:my-jboss-html5-mobile-blank-archetype:1.0.0-SNAPSHOT default,openshift,minify,arq-jbossas-managed,jboss-product-repository
> [ERROR] Failed to execute goal ro.isdc.wro4j:wro4j-maven-plugin:1.4.4:run (default) on project my-jboss-html5-mobile-blank-archetype: Exception occured while processing: Exception while loading properties file from /home/rawagner/tmp/off/offline/workDir/jboss-html5-mobile-blank-archetype/my-jboss-html5-mobile-blank-archetype/src/main/webapp/WEB-INF/wro.properties: /home/rawagner/tmp/off/offline/workDir/jboss-html5-mobile-blank-archetype/my-jboss-html5-mobile-blank-archetype/src/main/webapp/WEB-INF/wro.properties (No such file or directory) -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> Result: 1
> Building org.jbosstoolsofflineexamples:my-jboss-html5-mobile-blank-archetype:1.0.0-SNAPSHOT arq-jbossas-remote
> Building org.jbosstoolsofflineexamples:my-richfaces-archetype-kitchensink:1.0.0-SNAPSHOT default,arq-jbossas-managed,openshift,debug
> Building org.jbosstoolsofflineexamples:my-richfaces-archetype-kitchensink:1.0.0-SNAPSHOT arq-jbossas-remote
> Building org.jbosstoolsofflineexamples:my-richfaces-archetype-kitchensink-enterprise:1.0.0-SNAPSHOT default,arq-jbossas-managed,openshift,debug
> Building org.jbosstoolsofflineexamples:my-richfaces-archetype-kitchensink-enterprise:1.0.0-SNAPSHOT arq-jbossas-remote
> Building org.jbosstoolsofflineexamples:my-richfaces-archetype-kitchensink:1.0.0-SNAPSHOT default,arq-jbossas-managed,openshift,debug,jboss-product-repository
> Building org.jbosstoolsofflineexamples:my-richfaces-archetype-kitchensink:1.0.0-SNAPSHOT arq-jbossas-remote
> Building org.jbosstoolsofflineexamples:my-richfaces-archetype-simpleapp:1.0.0-SNAPSHOT jboss-product-repository
> Building org.jbosstoolsofflineexamples:my-richfaces-archetype-kitchensink:1.0.0-SNAPSHOT default,arq-jbossas-managed,openshift,debug,jboss-product-repository
> Building org.jbosstoolsofflineexamples:my-richfaces-archetype-kitchensink:1.0.0-SNAPSHOT arq-jbossas-remote
> Building org.jbosstoolsofflineexamples:my-richfaces-archetype-simpleapp:1.0.0-SNAPSHOT jboss-product-repository
> Building org.jbosstoolsofflineexamples:my-jboss-spring-mvc-archetype:1.0.0-SNAPSHOT openshift,jboss-product-repository
> Building org.jbosstoolsofflineexamples:my-jboss-spring-mvc-archetype:1.0.0-SNAPSHOT openshift,jboss-product-repository
> Building org.jbosstoolsofflineexamples:my-jboss-errai-kitchensink-archetype:1.0.0-SNAPSHOT default,openshift
> [ERROR] SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
> [ERROR] SLF4J: Defaulting to no-operation (NOP) logger implementation
> [ERROR] SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
> [ERROR] Oct 10, 2014 11:08:24 AM org.hibernate.annotations.common.Version <clinit>
> [ERROR] INFO: HCANN000001: Hibernate Commons Annotations {4.0.1.Final}
> [ERROR] Oct 10, 2014 11:08:24 AM org.hibernate.Version logVersion
> [ERROR] INFO: HHH000412: Hibernate Core {4.1.1}
> [ERROR] Oct 10, 2014 11:08:24 AM org.hibernate.cfg.Environment <clinit>
> [ERROR] INFO: HHH000206: hibernate.properties not found
> [ERROR] Oct 10, 2014 11:08:24 AM org.hibernate.cfg.Environment buildBytecodeProvider
> [ERROR] INFO: HHH000021: Bytecode provider name : javassist
> [ERROR] Oct 10, 2014 11:08:24 AM org.hibernate.ejb.Ejb3Configuration configure
> [ERROR] INFO: HHH000204: Processing PersistenceUnitInfo [
> [ERROR] name: ErraiClientPersistenceUnit
> [ERROR] ...]
> [ERROR] Oct 10, 2014 11:08:25 AM org.hibernate.service.jdbc.connections.internal.ConnectionProviderInitiator initiateService
> [ERROR] WARN: HHH000181: No appropriate connection provider encountered, assuming application will be supplying connections
> [ERROR] Oct 10, 2014 11:08:25 AM org.hibernate.dialect.Dialect <init>
> [ERROR] INFO: HHH000400: Using dialect: org.hibernate.dialect.H2Dialect
> [ERROR] Oct 10, 2014 11:08:25 AM org.hibernate.dialect.H2Dialect <init>
> [ERROR] WARN: HHH000431: Unable to determine H2 database version, certain features may not work
> [ERROR] Oct 10, 2014 11:08:25 AM org.hibernate.engine.jdbc.internal.LobCreatorBuilder useContextualLobCreation
> [ERROR] INFO: HHH000422: Disabling contextual LOB creation as connection was null
> [ERROR] Oct 10, 2014 11:08:25 AM org.hibernate.engine.transaction.internal.TransactionFactoryInitiator initiateService
> [ERROR] INFO: HHH000268: Transaction strategy: org.hibernate.engine.transaction.internal.jdbc.JdbcTransactionFactory
> [ERROR] Oct 10, 2014 11:08:25 AM org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory <init>
> [ERROR] INFO: HHH000397: Using ASTQueryTranslatorFactory
> [ERROR] Oct 10, 2014 11:08:25 AM org.hibernate.ejb.Ejb3Configuration configure
> [ERROR] INFO: HHH000204: Processing PersistenceUnitInfo [
> [ERROR] name: ErraiClientPersistenceUnit
> [ERROR] ...]
> [ERROR] Oct 10, 2014 11:08:25 AM org.hibernate.service.jdbc.connections.internal.ConnectionProviderInitiator initiateService
> [ERROR] WARN: HHH000181: No appropriate connection provider encountered, assuming application will be supplying connections
> [ERROR] Oct 10, 2014 11:08:25 AM org.hibernate.dialect.Dialect <init>
> [ERROR] INFO: HHH000400: Using dialect: org.hibernate.dialect.H2Dialect
> [ERROR] Oct 10, 2014 11:08:25 AM org.hibernate.dialect.H2Dialect <init>
> [ERROR] WARN: HHH000431: Unable to determine H2 database version, certain features may not work
> [ERROR] Oct 10, 2014 11:08:25 AM org.hibernate.engine.jdbc.internal.LobCreatorBuilder useContextualLobCreation
> [ERROR] INFO: HHH000422: Disabling contextual LOB creation as connection was null
> [ERROR] Oct 10, 2014 11:08:25 AM org.hibernate.engine.transaction.internal.TransactionFactoryInitiator initiateService
> [ERROR] INFO: HHH000268: Transaction strategy: org.hibernate.engine.transaction.internal.jdbc.JdbcTransactionFactory
> [ERROR] Oct 10, 2014 11:08:25 AM org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory <init>
> [ERROR] INFO: HHH000397: Using ASTQueryTranslatorFactory
> [ERROR] Oct 10, 2014 11:08:25 AM org.hibernate.ejb.Ejb3Configuration configure
> [ERROR] INFO: HHH000204: Processing PersistenceUnitInfo [
> [ERROR] name: ErraiClientPersistenceUnit
> [ERROR] ...]
> [ERROR] Oct 10, 2014 11:08:25 AM org.hibernate.service.jdbc.connections.internal.ConnectionProviderInitiator initiateService
> [ERROR] WARN: HHH000181: No appropriate connection provider encountered, assuming application will be supplying connections
> [ERROR] Oct 10, 2014 11:08:25 AM org.hibernate.dialect.Dialect <init>
> [ERROR] INFO: HHH000400: Using dialect: org.hibernate.dialect.H2Dialect
> [ERROR] Oct 10, 2014 11:08:25 AM org.hibernate.dialect.H2Dialect <init>
> [ERROR] WARN: HHH000431: Unable to determine H2 database version, certain features may not work
> [ERROR] Oct 10, 2014 11:08:25 AM org.hibernate.engine.jdbc.internal.LobCreatorBuilder useContextualLobCreation
> [ERROR] INFO: HHH000422: Disabling contextual LOB creation as connection was null
> [ERROR] Oct 10, 2014 11:08:25 AM org.hibernate.engine.transaction.internal.TransactionFactoryInitiator initiateService
> [ERROR] INFO: HHH000268: Transaction strategy: org.hibernate.engine.transaction.internal.jdbc.JdbcTransactionFactory
> [ERROR] Oct 10, 2014 11:08:25 AM org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory <init>
> [ERROR] INFO: HHH000397: Using ASTQueryTranslatorFactory
> [ERROR] Oct 10, 2014 11:08:25 AM org.hibernate.ejb.Ejb3Configuration configure
> [ERROR] INFO: HHH000204: Processing PersistenceUnitInfo [
> [ERROR] name: ErraiClientPersistenceUnit
> [ERROR] ...]
> [ERROR] Oct 10, 2014 11:08:25 AM org.hibernate.service.jdbc.connections.internal.ConnectionProviderInitiator initiateService
> [ERROR] WARN: HHH000181: No appropriate connection provider encountered, assuming application will be supplying connections
> [ERROR] Oct 10, 2014 11:08:25 AM org.hibernate.dialect.Dialect <init>
> [ERROR] INFO: HHH000400: Using dialect: org.hibernate.dialect.H2Dialect
> [ERROR] Oct 10, 2014 11:08:25 AM org.hibernate.dialect.H2Dialect <init>
> [ERROR] WARN: HHH000431: Unable to determine H2 database version, certain features may not work
> [ERROR] Oct 10, 2014 11:08:25 AM org.hibernate.engine.jdbc.internal.LobCreatorBuilder useContextualLobCreation
> [ERROR] INFO: HHH000422: Disabling contextual LOB creation as connection was null
> [ERROR] Oct 10, 2014 11:08:25 AM org.hibernate.engine.transaction.internal.TransactionFactoryInitiator initiateService
> [ERROR] INFO: HHH000268: Transaction strategy: org.hibernate.engine.transaction.internal.jdbc.JdbcTransactionFactory
> [ERROR] Oct 10, 2014 11:08:25 AM org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory <init>
> [ERROR] INFO: HHH000397: Using ASTQueryTranslatorFactory
> [ERROR] Oct 10, 2014 11:08:25 AM org.hibernate.ejb.Ejb3Configuration configure
> [ERROR] INFO: HHH000204: Processing PersistenceUnitInfo [
> [ERROR] name: ErraiClientPersistenceUnit
> [ERROR] ...]
> [ERROR] Oct 10, 2014 11:08:25 AM org.hibernate.service.jdbc.connections.internal.ConnectionProviderInitiator initiateService
> [ERROR] WARN: HHH000181: No appropriate connection provider encountered, assuming application will be supplying connections
> [ERROR] Oct 10, 2014 11:08:25 AM org.hibernate.dialect.Dialect <init>
> [ERROR] INFO: HHH000400: Using dialect: org.hibernate.dialect.H2Dialect
> [ERROR] Oct 10, 2014 11:08:25 AM org.hibernate.dialect.H2Dialect <init>
> [ERROR] WARN: HHH000431: Unable to determine H2 database version, certain features may not work
> [ERROR] Oct 10, 2014 11:08:25 AM org.hibernate.engine.jdbc.internal.LobCreatorBuilder useContextualLobCreation
> [ERROR] INFO: HHH000422: Disabling contextual LOB creation as connection was null
> [ERROR] Oct 10, 2014 11:08:25 AM org.hibernate.engine.transaction.internal.TransactionFactoryInitiator initiateService
> [ERROR] INFO: HHH000268: Transaction strategy: org.hibernate.engine.transaction.internal.jdbc.JdbcTransactionFactory
> [ERROR] Oct 10, 2014 11:08:25 AM org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory <init>
> [ERROR] INFO: HHH000397: Using ASTQueryTranslatorFactory
> [ERROR] Oct 10, 2014 11:08:25 AM org.hibernate.ejb.Ejb3Configuration configure
> [ERROR] INFO: HHH000204: Processing PersistenceUnitInfo [
> [ERROR] name: ErraiClientPersistenceUnit
> [ERROR] ...]
> [ERROR] Oct 10, 2014 11:08:25 AM org.hibernate.service.jdbc.connections.internal.ConnectionProviderInitiator initiateService
> [ERROR] WARN: HHH000181: No appropriate connection provider encountered, assuming application will be supplying connections
> [ERROR] Oct 10, 2014 11:08:25 AM org.hibernate.dialect.Dialect <init>
> [ERROR] INFO: HHH000400: Using dialect: org.hibernate.dialect.H2Dialect
> [ERROR] Oct 10, 2014 11:08:25 AM org.hibernate.dialect.H2Dialect <init>
> [ERROR] WARN: HHH000431: Unable to determine H2 database version, certain features may not work
> [ERROR] Oct 10, 2014 11:08:25 AM org.hibernate.engine.jdbc.internal.LobCreatorBuilder useContextualLobCreation
> [ERROR] INFO: HHH000422: Disabling contextual LOB creation as connection was null
> [ERROR] Oct 10, 2014 11:08:25 AM org.hibernate.engine.transaction.internal.TransactionFactoryInitiator initiateService
> [ERROR] INFO: HHH000268: Transaction strategy: org.hibernate.engine.transaction.internal.jdbc.JdbcTransactionFactory
> [ERROR] Oct 10, 2014 11:08:25 AM org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory <init>
> [ERROR] INFO: HHH000397: Using ASTQueryTranslatorFactory
> Building org.jbosstoolsofflineexamples:my-jboss-javaee6-webapp-archetype:1.0.0-SNAPSHOT default,arq-jbossas-managed,openshift
> Building org.jbosstoolsofflineexamples:my-jboss-javaee6-webapp-archetype:1.0.0-SNAPSHOT arq-jbossas-remote
> Building org.jbosstoolsofflineexamples:my-jboss-javaee6-webapp-archetype-enterprise:1.0.0-SNAPSHOT default,arq-jbossas-managed,openshift
> Building org.jbosstoolsofflineexamples:my-jboss-javaee6-webapp-archetype-enterprise:1.0.0-SNAPSHOT arq-jbossas-remote
> Building org.jbosstoolsofflineexamples:my-jboss-javaee6-webapp-blank-archetype:1.0.0-SNAPSHOT default,arq-jbossas-managed,openshift
> Building org.jbosstoolsofflineexamples:my-jboss-javaee6-webapp-blank-archetype:1.0.0-SNAPSHOT arq-jbossas-remote
> Building org.jbosstoolsofflineexamples:my-jboss-javaee6-webapp-blank-archetype-enterprise:1.0.0-SNAPSHOT default,arq-jbossas-managed,openshift
> Building org.jbosstoolsofflineexamples:my-jboss-javaee6-webapp-blank-archetype-enterprise:1.0.0-SNAPSHOT arq-jbossas-remote
> Building org.jbosstoolsofflineexamples:my-jboss-javaee6-webapp-ear-archetype:1.0.0-SNAPSHOT
> Building org.jbosstoolsofflineexamples:my-jboss-javaee6-webapp-ear-blank-archetype:1.0.0-SNAPSHOT
> Building org.jbosstoolsofflineexamples:my-jboss-html5-mobile-archetype:1.0.0-SNAPSHOT default,openshift,minify,arq-jbossas-managed
> Building org.jbosstoolsofflineexamples:my-jboss-html5-mobile-archetype:1.0.0-SNAPSHOT arq-jbossas-remote
> Building org.jbosstoolsofflineexamples:my-jboss-html5-mobile-archetype-enterprise:1.0.0-SNAPSHOT default,openshift,minify,arq-jbossas-managed
> Building org.jbosstoolsofflineexamples:my-jboss-html5-mobile-archetype-enterprise:1.0.0-SNAPSHOT arq-jbossas-remote
> Cleaning up installed artifacts created from archetypes
> Script executed in 30 min, 55 sec with 4 error(s)
> Project offline/workDir/jboss-kitchensink-backbone.zip failed to build
> Project offline/workDir/contacts-mobile.zip/contacts-mobile-basic-services failed to build
> Failed to generate project myapp.jboss-forge-html5 from archetype org.jboss.tools.archetypes:jboss-forge-html5:1.0.0-SNAPSHOT
> Project offline/workDir/jboss-html5-mobile-blank-archetype/my-jboss-html5-mobile-blank-archetype failed to build
> {code}
> Project offline/workDir/jboss-kitchensink-backbone.zip failed to build - reported in JBIDE-18581
> Project offline/workDir/contacts-mobile.zip/contacts-mobile-basic-services failed to build - reported in JBIDE-18579
> Im not sure what to do about the rest:
> Project offline/workDir/jboss-html5-mobile-blank-archetype/my-jboss-html5-mobile-blank-archetype failed to build - wro4j files are missing since its blank archetype so minify profile doesnt work
> Failed to generate project myapp.jboss-forge-html5 from archetype org.jboss.tools.archetypes:jboss-forge-html5:1.0.0-SNAPSHOT - pom.xml can't be found
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-19645) Remove seam 3 features from JBDS, JBT default install; add new connector to Central
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19645?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-19645:
---------------------------------------------
[~akazakov] i'd say we should ask deltaspike team or look up docs on deltaspike to see if there are active replacements.
> Remove seam 3 features from JBDS, JBT default install; add new connector to Central
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-19645
> URL: https://issues.jboss.org/browse/JBIDE-19645
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi-extensions, central, updatesite
> Affects Versions: 4.3.0.Alpha2
> Reporter: Nick Boldt
> Assignee: Alexey Kazakov
> Fix For: 4.3.0.Beta1
>
> Attachments: jbds8alpha2-features-cdi-seam.png, jbds8alpha2-plugins-cdi.png, jbds8alpha2-plugins-seam.png, jbt43alpha2-features-cdi.png, jbt43alpha2-features-seam.png, jbt43alpha2-plugins-cdi.png, jbt43alpha2-plugins-seam-3-and-seam3.png, validation.png
>
>
> Burr has requested we also remove Seam 3. So I've assumed we'll do it the same way we did for Seam 2:
> * remove from CoreTools categories on update sites
> * remove from JBDS core.feature
> * create new connectors in JBT and JBDS Central
> [~burrsutter] [~maxandersen] please confirm this is the path you want taken for all the renaming features with "seam" in their name.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-19401) remove Seam & Portlet from JBT 4.3 default install
by Radim Hopp (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19401?page=com.atlassian.jira.plugi... ]
Radim Hopp commented on JBIDE-19401:
------------------------------------
I thought that idea of this jira was to remove seam 2 & portlets from default install AND create connector for them. As I understood it - When I install everything from "Abridged JBoss Tools" category, Seam 2 & portlets will not be installed. This has not happened, because of dependency of JBoss Maven Portlet Configurator to Portlets and Seam2.
[~maxandersen], [~fbricon] could you please comment?
> remove Seam & Portlet from JBT 4.3 default install
> ---------------------------------------------------
>
> Key: JBIDE-19401
> URL: https://issues.jboss.org/browse/JBIDE-19401
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: portal-gatein, seam2
> Affects Versions: 4.3.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.3.0.Alpha2
>
>
> Recently we removed Seams and Portlet from the default JBDS 9 install. Max said today we should do the same for JBT 4.3.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-19697) org.jboss.tools.runtime.ui.prefs mysteriously appears in Eclipse dir during JBDS BYOE installation
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19697?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-19697:
---------------------------------------
That's what I thought at first too. But I don't have such config inside ~/eclipse:
{code}
$ ls ~/.eclipse
org.eclipse.equinox.security org.eclipse.oomph.p2 org.eclipse.oomph.setup org.eclipse.recommenders
$ find ~/.eclipse -name 'org.jboss.tools.runtime.*.prefs'|wc
0 0 0
{code}
> org.jboss.tools.runtime.ui.prefs mysteriously appears in Eclipse dir during JBDS BYOE installation
> --------------------------------------------------------------------------------------------------
>
> Key: JBIDE-19697
> URL: https://issues.jboss.org/browse/JBIDE-19697
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: runtime-detection
> Affects Versions: 4.3.0.Alpha2
> Reporter: Martin Malina
> Assignee: Snjezana Peco
>
> When I install JBDs 9.0.0.Alpha2 B24 BYOE into new Eclipse Mars M6 and new workspace, during the installation, suddenly the runtime detection config appears inside my Eclipse isntall dir:
> {code}
> $ find Eclipse-runtime-test.app/ -name 'org.jboss.tools.runtime.*.prefs'
> Eclipse-runtime-test.app//Contents/Eclipse/configuration/.settings/org.jboss.tools.runtime.ui.prefs
> {code}
> This is inside the file:
> {code}
> $ find Eclipse-runtime-test.app/ -name 'org.jboss.tools.runtime.*.prefs'|xargs cat
> eclipse.preferences.version=1
> runtimePaths=<?xml version\="1.0" encoding\="UTF-8" standalone\="no"?>\n<runtimePaths version\="2">\n <runtimePath path\="/Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0" scanOnEveryStartup\="false" timestamp\="-1">\n <serverDefinitions>\n <serverDefinition description\="" enabled\="true" location\="/Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0" name\="JBoss EAP 6.3" type\="EAP" version\="6.3">\n <included/>\n </serverDefinition>\n </serverDefinitions>\n </runtimePath>\n</runtimePaths>\n
> {code}
> It contains /Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0 which I use regularly when testing server tooling. But how did this happen?
> I looked for the pref file before I started BYOE installation. Then a bit later, a few minutes into the installation, I checked again and the file is there now.
> Can somebody explain what's going on?
> Note: This happened to me yesterday and it surprised me, but I wasn't sure if it wasn't my mistake somehow. But Max preferred I try again, so I did. And it is happening again now.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-19697) org.jboss.tools.runtime.ui.prefs mysteriously appears in Eclipse dir during JBDS BYOE installation
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19697?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen reassigned JBIDE-19697:
-------------------------------------------
Assignee: Snjezana Peco
> org.jboss.tools.runtime.ui.prefs mysteriously appears in Eclipse dir during JBDS BYOE installation
> --------------------------------------------------------------------------------------------------
>
> Key: JBIDE-19697
> URL: https://issues.jboss.org/browse/JBIDE-19697
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: runtime-detection
> Affects Versions: 4.3.0.Alpha2
> Reporter: Martin Malina
> Assignee: Snjezana Peco
>
> When I install JBDs 9.0.0.Alpha2 B24 BYOE into new Eclipse Mars M6 and new workspace, during the installation, suddenly the runtime detection config appears inside my Eclipse isntall dir:
> {code}
> $ find Eclipse-runtime-test.app/ -name 'org.jboss.tools.runtime.*.prefs'
> Eclipse-runtime-test.app//Contents/Eclipse/configuration/.settings/org.jboss.tools.runtime.ui.prefs
> {code}
> This is inside the file:
> {code}
> $ find Eclipse-runtime-test.app/ -name 'org.jboss.tools.runtime.*.prefs'|xargs cat
> eclipse.preferences.version=1
> runtimePaths=<?xml version\="1.0" encoding\="UTF-8" standalone\="no"?>\n<runtimePaths version\="2">\n <runtimePath path\="/Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0" scanOnEveryStartup\="false" timestamp\="-1">\n <serverDefinitions>\n <serverDefinition description\="" enabled\="true" location\="/Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0" name\="JBoss EAP 6.3" type\="EAP" version\="6.3">\n <included/>\n </serverDefinition>\n </serverDefinitions>\n </runtimePath>\n</runtimePaths>\n
> {code}
> It contains /Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0 which I use regularly when testing server tooling. But how did this happen?
> I looked for the pref file before I started BYOE installation. Then a bit later, a few minutes into the installation, I checked again and the file is there now.
> Can somebody explain what's going on?
> Note: This happened to me yesterday and it surprised me, but I wasn't sure if it wasn't my mistake somehow. But Max preferred I try again, so I did. And it is happening again now.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-19697) org.jboss.tools.runtime.ui.prefs mysteriously appears in Eclipse dir during JBDS BYOE installation
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19697?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-19697:
---------------------------------------------
I would expect the settings would be stored in your ~/.eclipse setting if anything. surprising if its in your local preferences.
[~snjeza] and [~rob.stryker] whats the logic we got currently for storing the runtime location preferences ?
> org.jboss.tools.runtime.ui.prefs mysteriously appears in Eclipse dir during JBDS BYOE installation
> --------------------------------------------------------------------------------------------------
>
> Key: JBIDE-19697
> URL: https://issues.jboss.org/browse/JBIDE-19697
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: runtime-detection
> Affects Versions: 4.3.0.Alpha2
> Reporter: Martin Malina
> Assignee: Snjezana Peco
>
> When I install JBDs 9.0.0.Alpha2 B24 BYOE into new Eclipse Mars M6 and new workspace, during the installation, suddenly the runtime detection config appears inside my Eclipse isntall dir:
> {code}
> $ find Eclipse-runtime-test.app/ -name 'org.jboss.tools.runtime.*.prefs'
> Eclipse-runtime-test.app//Contents/Eclipse/configuration/.settings/org.jboss.tools.runtime.ui.prefs
> {code}
> This is inside the file:
> {code}
> $ find Eclipse-runtime-test.app/ -name 'org.jboss.tools.runtime.*.prefs'|xargs cat
> eclipse.preferences.version=1
> runtimePaths=<?xml version\="1.0" encoding\="UTF-8" standalone\="no"?>\n<runtimePaths version\="2">\n <runtimePath path\="/Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0" scanOnEveryStartup\="false" timestamp\="-1">\n <serverDefinitions>\n <serverDefinition description\="" enabled\="true" location\="/Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0" name\="JBoss EAP 6.3" type\="EAP" version\="6.3">\n <included/>\n </serverDefinition>\n </serverDefinitions>\n </runtimePath>\n</runtimePaths>\n
> {code}
> It contains /Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0 which I use regularly when testing server tooling. But how did this happen?
> I looked for the pref file before I started BYOE installation. Then a bit later, a few minutes into the installation, I checked again and the file is there now.
> Can somebody explain what's going on?
> Note: This happened to me yesterday and it surprised me, but I wasn't sure if it wasn't my mistake somehow. But Max preferred I try again, so I did. And it is happening again now.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-19697) org.jboss.tools.runtime.ui.prefs mysteriously appears in Eclipse dir during JBDS BYOE installation
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19697?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-19697:
----------------------------------------
Component/s: (was: build)
> org.jboss.tools.runtime.ui.prefs mysteriously appears in Eclipse dir during JBDS BYOE installation
> --------------------------------------------------------------------------------------------------
>
> Key: JBIDE-19697
> URL: https://issues.jboss.org/browse/JBIDE-19697
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: runtime-detection
> Affects Versions: 4.3.0.Alpha2
> Reporter: Martin Malina
>
> When I install JBDs 9.0.0.Alpha2 B24 BYOE into new Eclipse Mars M6 and new workspace, during the installation, suddenly the runtime detection config appears inside my Eclipse isntall dir:
> {code}
> $ find Eclipse-runtime-test.app/ -name 'org.jboss.tools.runtime.*.prefs'
> Eclipse-runtime-test.app//Contents/Eclipse/configuration/.settings/org.jboss.tools.runtime.ui.prefs
> {code}
> This is inside the file:
> {code}
> $ find Eclipse-runtime-test.app/ -name 'org.jboss.tools.runtime.*.prefs'|xargs cat
> eclipse.preferences.version=1
> runtimePaths=<?xml version\="1.0" encoding\="UTF-8" standalone\="no"?>\n<runtimePaths version\="2">\n <runtimePath path\="/Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0" scanOnEveryStartup\="false" timestamp\="-1">\n <serverDefinitions>\n <serverDefinition description\="" enabled\="true" location\="/Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0" name\="JBoss EAP 6.3" type\="EAP" version\="6.3">\n <included/>\n </serverDefinition>\n </serverDefinitions>\n </runtimePath>\n</runtimePaths>\n
> {code}
> It contains /Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0 which I use regularly when testing server tooling. But how did this happen?
> I looked for the pref file before I started BYOE installation. Then a bit later, a few minutes into the installation, I checked again and the file is there now.
> Can somebody explain what's going on?
> Note: This happened to me yesterday and it surprised me, but I wasn't sure if it wasn't my mistake somehow. But Max preferred I try again, so I did. And it is happening again now.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-19697) org.jboss.tools.runtime.ui.prefs mysteriously appears in Eclipse dir during JBDS BYOE installation
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19697?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-19697:
---------------------------------------
I wasn't sure what component to use - it's not really about build, but there is no p2 component. And I would assume that this is not specific to JBDS only, so I created the JIRA under JBIDE.
> org.jboss.tools.runtime.ui.prefs mysteriously appears in Eclipse dir during JBDS BYOE installation
> --------------------------------------------------------------------------------------------------
>
> Key: JBIDE-19697
> URL: https://issues.jboss.org/browse/JBIDE-19697
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, runtime-detection
> Affects Versions: 4.3.0.Alpha2
> Reporter: Martin Malina
>
> When I install JBDs 9.0.0.Alpha2 B24 BYOE into new Eclipse Mars M6 and new workspace, during the installation, suddenly the runtime detection config appears inside my Eclipse isntall dir:
> {code}
> $ find Eclipse-runtime-test.app/ -name 'org.jboss.tools.runtime.*.prefs'
> Eclipse-runtime-test.app//Contents/Eclipse/configuration/.settings/org.jboss.tools.runtime.ui.prefs
> {code}
> This is inside the file:
> {code}
> $ find Eclipse-runtime-test.app/ -name 'org.jboss.tools.runtime.*.prefs'|xargs cat
> eclipse.preferences.version=1
> runtimePaths=<?xml version\="1.0" encoding\="UTF-8" standalone\="no"?>\n<runtimePaths version\="2">\n <runtimePath path\="/Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0" scanOnEveryStartup\="false" timestamp\="-1">\n <serverDefinitions>\n <serverDefinition description\="" enabled\="true" location\="/Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0" name\="JBoss EAP 6.3" type\="EAP" version\="6.3">\n <included/>\n </serverDefinition>\n </serverDefinitions>\n </runtimePath>\n</runtimePaths>\n
> {code}
> It contains /Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0 which I use regularly when testing server tooling. But how did this happen?
> I looked for the pref file before I started BYOE installation. Then a bit later, a few minutes into the installation, I checked again and the file is there now.
> Can somebody explain what's going on?
> Note: This happened to me yesterday and it surprised me, but I wasn't sure if it wasn't my mistake somehow. But Max preferred I try again, so I did. And it is happening again now.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-19697) org.jboss.tools.runtime.ui.prefs mysteriously appears in Eclipse dir during JBDS BYOE installation
by Martin Malina (JIRA)
Martin Malina created JBIDE-19697:
-------------------------------------
Summary: org.jboss.tools.runtime.ui.prefs mysteriously appears in Eclipse dir during JBDS BYOE installation
Key: JBIDE-19697
URL: https://issues.jboss.org/browse/JBIDE-19697
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: build, runtime-detection
Affects Versions: 4.3.0.Alpha2
Reporter: Martin Malina
When I install JBDs 9.0.0.Alpha2 B24 BYOE into new Eclipse Mars M6 and new workspace, during the installation, suddenly the runtime detection config appears inside my Eclipse isntall dir:
{code}
$ find Eclipse-runtime-test.app/ -name 'org.jboss.tools.runtime.*.prefs'
Eclipse-runtime-test.app//Contents/Eclipse/configuration/.settings/org.jboss.tools.runtime.ui.prefs
{code}
This is inside the file:
{code}
$ find Eclipse-runtime-test.app/ -name 'org.jboss.tools.runtime.*.prefs'|xargs cat
eclipse.preferences.version=1
runtimePaths=<?xml version\="1.0" encoding\="UTF-8" standalone\="no"?>\n<runtimePaths version\="2">\n <runtimePath path\="/Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0" scanOnEveryStartup\="false" timestamp\="-1">\n <serverDefinitions>\n <serverDefinition description\="" enabled\="true" location\="/Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0" name\="JBoss EAP 6.3" type\="EAP" version\="6.3">\n <included/>\n </serverDefinition>\n </serverDefinitions>\n </runtimePath>\n</runtimePaths>\n
{code}
It contains /Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0 which I use regularly when testing server tooling. But how did this happen?
I looked for the pref file before I started BYOE installation. Then a bit later, a few minutes into the installation, I checked again and the file is there now.
Can somebody explain what's going on?
Note: This happened to me yesterday and it surprised me, but I wasn't sure if it wasn't my mistake somehow. But Max preferred I try again, so I did. And it is happening again now.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-19507) Search and rename participants for Batch Artifacts
by Lucia Jelinkova (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19507?page=com.atlassian.jira.plugi... ]
Lucia Jelinkova commented on JBIDE-19507:
-----------------------------------------
Created JBIDE-19696
> Search and rename participants for Batch Artifacts
> --------------------------------------------------
>
> Key: JBIDE-19507
> URL: https://issues.jboss.org/browse/JBIDE-19507
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: batch
> Reporter: Daniel Azarov
> Assignee: Daniel Azarov
> Labels: new_and_noteworthy
> Fix For: 4.3.0.Alpha2
>
> Attachments: BatchArtifactRename.png, ExceptionRename.png, FieldReference.png, PropertyRename.png, SearchableBatchletReferences.png, SearchableExceptionReferences.png
>
>
> *Search Participant*
> 1. Should be able to find references in job.xml files for Batch Artifact Class IType
> Example:
> During the search for references for class "SearchableBatchlet" like:
> {code}
> package batch;
> import javax.batch.api.BatchProperty;
> import javax.batch.api.Batchlet;
> import javax.inject.Inject;
> import javax.inject.Named;
> @Named
> public class SearchableBatchlet implements Batchlet {
>
> @Inject @BatchProperty(name="secondName") String otherName;
> @Override
> public String process() throws Exception {
> return null;
> }
> @Override
> public void stop() throws Exception {
> }
> }
> {code}
> In the search result should be added references in jbob.xml files like this:
> !SearchableBatchletReferences.png!
> 2. Should be able to find references in job.xml files for Batch Artifact Property IField
> Example:
> During the search for references for field "otherName" of class "SearchableBatchlet" in the search result should be added references in jbob.xml files like this:
> !FieldReference.png!
> 3. Should be able to find references in job.xml files for Exception Class IType
> Example:
> During the search for references for class "SearchableException" like:
> {code}
> package batch;
> public class SearchableException extends Exception{
> private static final long serialVersionUID = 1L;
> }
> {code}
> In the search result should be added references in jbob.xml files like this:
> !SearchableExceptionReferences.png!
> *Rename Participant*
> 1. Should be able to add changes in Batch Artifact Class Rename for references in job.xml files.
> Note: Rename Participant does make sense only for Batch Artifacts which name comes from Java Class Name, not from annotation @Named
> Example:
> During rename of class "SearchableBatchlet" changes for job.xml references should be added in Refactoring:
> !BatchArtifactRename.png!
> 2. Should be able to add changes in Batch Property Rename for references in job.xml files.
> Note: Rename Participant does make sense only for Batch Properties which name comes from Java Field Name, not from annotation @BatchProperty
> Example:
> {code}
> package batch;
> import javax.batch.api.BatchProperty;
> import javax.batch.api.Batchlet;
> import javax.inject.Inject;
> import javax.inject.Named;
> @Named
> public class RenamablePropertyBatchlet implements Batchlet {
>
> @Inject @BatchProperty String otherName;
> @Override
> public String process() throws Exception {
> return null;
> }
> @Override
> public void stop() throws Exception {
> }
> }
> {code}
> During rename of field "otherName" changes for job.xml references should be added in Refactoring:
> !PropertyRename.png!
> 3. Should be able to add changes in Exception Class Rename for references in job.xml files.
> Example:
> During rename of class "SearchableException" changes for job.xml references should be added in Refactoring:
> !ExceptionRename.png!
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-19507) Search and rename participants for Batch Artifacts
by Lucia Jelinkova (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19507?page=com.atlassian.jira.plugi... ]
Lucia Jelinkova closed JBIDE-19507.
-----------------------------------
> Search and rename participants for Batch Artifacts
> --------------------------------------------------
>
> Key: JBIDE-19507
> URL: https://issues.jboss.org/browse/JBIDE-19507
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: batch
> Reporter: Daniel Azarov
> Assignee: Daniel Azarov
> Labels: new_and_noteworthy
> Fix For: 4.3.0.Alpha2
>
> Attachments: BatchArtifactRename.png, ExceptionRename.png, FieldReference.png, PropertyRename.png, SearchableBatchletReferences.png, SearchableExceptionReferences.png
>
>
> *Search Participant*
> 1. Should be able to find references in job.xml files for Batch Artifact Class IType
> Example:
> During the search for references for class "SearchableBatchlet" like:
> {code}
> package batch;
> import javax.batch.api.BatchProperty;
> import javax.batch.api.Batchlet;
> import javax.inject.Inject;
> import javax.inject.Named;
> @Named
> public class SearchableBatchlet implements Batchlet {
>
> @Inject @BatchProperty(name="secondName") String otherName;
> @Override
> public String process() throws Exception {
> return null;
> }
> @Override
> public void stop() throws Exception {
> }
> }
> {code}
> In the search result should be added references in jbob.xml files like this:
> !SearchableBatchletReferences.png!
> 2. Should be able to find references in job.xml files for Batch Artifact Property IField
> Example:
> During the search for references for field "otherName" of class "SearchableBatchlet" in the search result should be added references in jbob.xml files like this:
> !FieldReference.png!
> 3. Should be able to find references in job.xml files for Exception Class IType
> Example:
> During the search for references for class "SearchableException" like:
> {code}
> package batch;
> public class SearchableException extends Exception{
> private static final long serialVersionUID = 1L;
> }
> {code}
> In the search result should be added references in jbob.xml files like this:
> !SearchableExceptionReferences.png!
> *Rename Participant*
> 1. Should be able to add changes in Batch Artifact Class Rename for references in job.xml files.
> Note: Rename Participant does make sense only for Batch Artifacts which name comes from Java Class Name, not from annotation @Named
> Example:
> During rename of class "SearchableBatchlet" changes for job.xml references should be added in Refactoring:
> !BatchArtifactRename.png!
> 2. Should be able to add changes in Batch Property Rename for references in job.xml files.
> Note: Rename Participant does make sense only for Batch Properties which name comes from Java Field Name, not from annotation @BatchProperty
> Example:
> {code}
> package batch;
> import javax.batch.api.BatchProperty;
> import javax.batch.api.Batchlet;
> import javax.inject.Inject;
> import javax.inject.Named;
> @Named
> public class RenamablePropertyBatchlet implements Batchlet {
>
> @Inject @BatchProperty String otherName;
> @Override
> public String process() throws Exception {
> return null;
> }
> @Override
> public void stop() throws Exception {
> }
> }
> {code}
> During rename of field "otherName" changes for job.xml references should be added in Refactoring:
> !PropertyRename.png!
> 3. Should be able to add changes in Exception Class Rename for references in job.xml files.
> Example:
> During rename of class "SearchableException" changes for job.xml references should be added in Refactoring:
> !ExceptionRename.png!
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-19696) Rename of an exception class does not work properly
by Lucia Jelinkova (JIRA)
Lucia Jelinkova created JBIDE-19696:
---------------------------------------
Summary: Rename of an exception class does not work properly
Key: JBIDE-19696
URL: https://issues.jboss.org/browse/JBIDE-19696
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: batch
Affects Versions: 4.3.0.Alpha2
Reporter: Lucia Jelinkova
Priority: Critical
When I try to rename an exception class RenamableException to RenamableException2, I get batch.RenamableException2enamableException in job XML file instead.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-19507) Search and rename participants for Batch Artifacts
by Lucia Jelinkova (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19507?page=com.atlassian.jira.plugi... ]
Lucia Jelinkova commented on JBIDE-19507:
-----------------------------------------
All works fine in JBDS 9.0.0.alpha2 except for renaming exception class. I'll create separate issue for that.
> Search and rename participants for Batch Artifacts
> --------------------------------------------------
>
> Key: JBIDE-19507
> URL: https://issues.jboss.org/browse/JBIDE-19507
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: batch
> Reporter: Daniel Azarov
> Assignee: Daniel Azarov
> Labels: new_and_noteworthy
> Fix For: 4.3.0.Alpha2
>
> Attachments: BatchArtifactRename.png, ExceptionRename.png, FieldReference.png, PropertyRename.png, SearchableBatchletReferences.png, SearchableExceptionReferences.png
>
>
> *Search Participant*
> 1. Should be able to find references in job.xml files for Batch Artifact Class IType
> Example:
> During the search for references for class "SearchableBatchlet" like:
> {code}
> package batch;
> import javax.batch.api.BatchProperty;
> import javax.batch.api.Batchlet;
> import javax.inject.Inject;
> import javax.inject.Named;
> @Named
> public class SearchableBatchlet implements Batchlet {
>
> @Inject @BatchProperty(name="secondName") String otherName;
> @Override
> public String process() throws Exception {
> return null;
> }
> @Override
> public void stop() throws Exception {
> }
> }
> {code}
> In the search result should be added references in jbob.xml files like this:
> !SearchableBatchletReferences.png!
> 2. Should be able to find references in job.xml files for Batch Artifact Property IField
> Example:
> During the search for references for field "otherName" of class "SearchableBatchlet" in the search result should be added references in jbob.xml files like this:
> !FieldReference.png!
> 3. Should be able to find references in job.xml files for Exception Class IType
> Example:
> During the search for references for class "SearchableException" like:
> {code}
> package batch;
> public class SearchableException extends Exception{
> private static final long serialVersionUID = 1L;
> }
> {code}
> In the search result should be added references in jbob.xml files like this:
> !SearchableExceptionReferences.png!
> *Rename Participant*
> 1. Should be able to add changes in Batch Artifact Class Rename for references in job.xml files.
> Note: Rename Participant does make sense only for Batch Artifacts which name comes from Java Class Name, not from annotation @Named
> Example:
> During rename of class "SearchableBatchlet" changes for job.xml references should be added in Refactoring:
> !BatchArtifactRename.png!
> 2. Should be able to add changes in Batch Property Rename for references in job.xml files.
> Note: Rename Participant does make sense only for Batch Properties which name comes from Java Field Name, not from annotation @BatchProperty
> Example:
> {code}
> package batch;
> import javax.batch.api.BatchProperty;
> import javax.batch.api.Batchlet;
> import javax.inject.Inject;
> import javax.inject.Named;
> @Named
> public class RenamablePropertyBatchlet implements Batchlet {
>
> @Inject @BatchProperty String otherName;
> @Override
> public String process() throws Exception {
> return null;
> }
> @Override
> public void stop() throws Exception {
> }
> }
> {code}
> During rename of field "otherName" changes for job.xml references should be added in Refactoring:
> !PropertyRename.png!
> 3. Should be able to add changes in Exception Class Rename for references in job.xml files.
> Example:
> During rename of class "SearchableException" changes for job.xml references should be added in Refactoring:
> !ExceptionRename.png!
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-19271) p2 director install fails because Central site includes an undefined reference to jboss.discovery.earlyaccess.site.url
by Lucia Jelinkova (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19271?page=com.atlassian.jira.plugi... ]
Lucia Jelinkova commented on JBIDE-19271:
-----------------------------------------
[~nickboldt] could we close this issue?
> p2 director install fails because Central site includes an undefined reference to jboss.discovery.earlyaccess.site.url
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-19271
> URL: https://issues.jboss.org/browse/JBIDE-19271
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: arquillian, build
> Affects Versions: 4.3.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Critical
> Fix For: 4.3.0.Alpha1
>
>
> Now that Arquillian is in the Central discovery plugin, but is located on the EA site, the p2 director install test is failing.
> {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-install-p2director.install-tests.matrix_4.3.mars/9/INSTALL_PLAN=http%3A%2F%2Fdownload.jboss.org%2Fjbosstools%2Fupdates%2Fnightly%2Fcore%2F4.3.mars%2F%3Bhttp%3A%2F%2Fdownload.jboss.org%2Fjbosstools%2Fdiscovery%2Fnightly%2Fcore%2F4.3.mars%2Fjbosstools-directory.xml,eclipseBundleVersion=mars.M5,jdk=java1.8,label_exp=%28RHEL7||beaker||jboss-prod%29&&!ia64&&!rhts/console}
> 22:35:15 run.director:
> 22:35:15 [echo] Profile Name: epp.package.jee
> 22:35:15 [echo] Install Path: /mnt/hudson_workspace/workspace/jbosstools-install-p2director.install-tests.matrix_4.3.mars/467eb389/eclipse
> 22:35:15 [echo] Source Sites: http://download.jboss.org/jbosstools/updates/nightly/core/4.3.mars/,http:...
> 22:35:15 [echo] IUS to Install:
> 22:35:15 [echo] com.android.ide.eclipse.adt.feature.feature.group,com.android.ide.eclipse.ddms.feature.feature.group,com.android.ide.eclipse.gldebugger.feature.feature.group,com.android.ide.eclipse.hierarchyviewer.feature.feature.group,com.android.ide.eclipse.traceview.feature.feature.group,com.atlassian.connector.eclipse.feature.group,com.atlassian.connector.eclipse.jira.feature.group,com.atlassian.connector.eclipse.monitor.feature.group,com.collabnet.subversion.merge.feature.feature.group,com.github.sevntu.checkstyle.checks.feature.feature.group,edu.umd.cs.findbugs.plugin.eclipse.feature.group,net.java.dev.jna.feature.group,net.sf.eclipsecs.feature.group,net.sourceforge.pmd.eclipse.feature.group,org.eclipse.egit.feature.group,org.eclipse.egit.mylyn.feature.group,org.eclipse.jgit.feature.group,org.eclipse.jst.server_adapters.feature.feature.group,org.eclipse.jst.server_core.feature.feature.group,org.eclipse.jst.server_ui.feature.feature.group,org.eclipse.jst.server_userdoc.feature.feature.group,org.eclipse.m2e.feature.feature.group,org.eclipse.m2e.wtp.feature.feature.group,org.eclipse.m2e.wtp.jaxrs.feature.feature.group,org.eclipse.m2e.wtp.jpa.feature.feature.group,org.eclipse.m2e.wtp.jsf.feature.feature.group,org.eclipse.mylyn.bugzilla_feature.feature.group,org.eclipse.mylyn.commons.feature.group,org.eclipse.mylyn.context_feature.feature.group,org.eclipse.mylyn_feature.feature.group,org.eclipse.mylyn.git.feature.group,org.eclipse.mylyn.github.feature.feature.group,org.eclipse.mylyn.hudson.feature.group,org.eclipse.mylyn.ide_feature.feature.group,org.eclipse.mylyn.java_feature.feature.group,org.eclipse.mylyn.pde_feature.feature.group,org.eclipse.mylyn.team_feature.feature.group,org.eclipse.mylyn.versions.feature.group,org.jboss.ide.eclipse.as.feature.feature.group,org.jboss.tools.aerogear.thym.feature.feature.group,org.jboss.tools.arquillian.feature.feature.group,org.jboss.tools.common.mylyn.feature.feature.group,org.jboss.tools.feedhenry.feature.feature.group,org.jboss.tools.forge.feature.feature.group,org.jboss.tools.forge.m2e.feature.feature.group,org.jboss.tools.jst.angularjs.feature.feature.group,org.jboss.tools.jst.jsdt.feature.feature.group,org.jboss.tools.livereload.feature.feature.group,org.jboss.tools.m2e.wro4j.feature.feature.group,org.jboss.tools.maven.apt.feature.feature.group,org.jboss.tools.maven.cdi.feature.feature.group,org.jboss.tools.maven.feature.feature.group,org.jboss.tools.maven.hibernate.feature.feature.group,org.jboss.tools.maven.jbosspackaging.feature.feature.group,org.jboss.tools.maven.portlet.feature.feature.group,org.jboss.tools.maven.seam.feature.feature.group,org.jboss.tools.openshift.egit.integration.feature.feature.group,org.jboss.tools.openshift.express.feature.feature.group,org.jboss.tools.project.examples.seam.feature.feature.group,org.jboss.tools.runtime.seam.detector.feature.feature.group,org.jboss.tools.seam.feature.feature.group,org.jboss.tools.vpe.browsersim.feature.feature.group,org.jboss.tools.vpe.cordovasim.feature.feature.group,org.sonatype.m2e.egit.feature.feature.group,org.springframework.ide.eclipse.ajdt.feature.feature.group,org.springframework.ide.eclipse.aop.feature.feature.group,org.springframework.ide.eclipse.autowire.feature.feature.group,org.springframework.ide.eclipse.batch.feature.feature.group,org.springframework.ide.eclipse.data.feature.feature.group,org.springframework.ide.eclipse.feature.feature.group,org.springframework.ide.eclipse.integration.feature.feature.group,org.springframework.ide.eclipse.maven.feature.feature.group,org.springframework.ide.eclipse.mylyn.feature.feature.group,org.springframework.ide.eclipse.osgi.feature.feature.group,org.springframework.ide.eclipse.security.feature.feature.group,org.springframework.ide.eclipse.webflow.feature.feature.group,org.springsource.ide.eclipse.commons.feature.group,org.testng.eclipse.feature.group,org.tigris.subversion.clientadapter.feature.feature.group,org.tigris.subversion.clientadapter.svnkit.feature.feature.group,org.tigris.subversion.subclipse.feature.group,org.tigris.subversion.subclipse.graph.feature.feature.group,org.tigris.subversion.subclipse.mylyn.feature.group,org.tmatesoft.svnkit.feature.group,org.zeroturnaround.eclipse.feature.feature.group,org.zeroturnaround.eclipse.m2e.feature.feature.group,org.zeroturnaround.eclipse.wtp.feature.feature.group
> 22:35:33 [p2.dir] java.lang.IllegalArgumentException: Location must be absolute: $%7Bjboss.discovery.earlyaccess.site.url%7D
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-14782) Add ShrinkWrap Archive file location validation
by Lucia Jelinkova (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14782?page=com.atlassian.jira.plugi... ]
Lucia Jelinkova closed JBIDE-14782.
-----------------------------------
> Add ShrinkWrap Archive file location validation
> -----------------------------------------------
>
> Key: JBIDE-14782
> URL: https://issues.jboss.org/browse/JBIDE-14782
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: arquillian
> Reporter: Aslak Knutsen
> Assignee: Snjezana Peco
> Labels: new_and_noteworthy
> Fix For: 4.3.0.Alpha1
>
>
> *Given*
> A Deployment method
> *When*
> {code}
> war.addAsManifestResource(X, "beans.xml")
> ear.addAsManifestResource(X, "beans.xml")
> war.addAsManifestResource(X, "persistence.xml")
> {code}
> *Then*
> Warn that known EE descriptor files are in the wrong location
> Some mapping on top of my head:
> WebArchive
> {code}
> web.xml -> /WEB-INF/
> web-fragment.xml -> Not supported ?
> beans.xml -> /WEB-INF/
> persistence.xml -> /WEB-INF/classes/META-INF/
> ejb-jar.xml -> /WEB-INF/classes/META-INF/
> {code}
> JavaArchive
> {code}
> web.xml -> Not supported
> web-fragment.xml -> /META-INF/
> beans.xml -> /META-INF/
> persistence.xml -> /META-INF/
> ejb-jar.xml -> /META-INF/
> {code}
> EnterpriseArchive
> {code}
> beans.xml -> Not supported
> persistence.xml -> Not supported
> ejb-jar.xml -> Not supported
> application.xml -> /META-INF/
> {code}
> One common mistake is using addAsManifestResource on WebArchives. A quickfix / suggestion would be to use addAsWebInfResource for the files located in /WEB-INF/
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-14782) Add ShrinkWrap Archive file location validation
by Lucia Jelinkova (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14782?page=com.atlassian.jira.plugi... ]
Lucia Jelinkova commented on JBIDE-14782:
-----------------------------------------
Remaining issues will be solved in JBIDE-19349
> Add ShrinkWrap Archive file location validation
> -----------------------------------------------
>
> Key: JBIDE-14782
> URL: https://issues.jboss.org/browse/JBIDE-14782
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: arquillian
> Reporter: Aslak Knutsen
> Assignee: Snjezana Peco
> Labels: new_and_noteworthy
> Fix For: 4.3.0.Alpha1
>
>
> *Given*
> A Deployment method
> *When*
> {code}
> war.addAsManifestResource(X, "beans.xml")
> ear.addAsManifestResource(X, "beans.xml")
> war.addAsManifestResource(X, "persistence.xml")
> {code}
> *Then*
> Warn that known EE descriptor files are in the wrong location
> Some mapping on top of my head:
> WebArchive
> {code}
> web.xml -> /WEB-INF/
> web-fragment.xml -> Not supported ?
> beans.xml -> /WEB-INF/
> persistence.xml -> /WEB-INF/classes/META-INF/
> ejb-jar.xml -> /WEB-INF/classes/META-INF/
> {code}
> JavaArchive
> {code}
> web.xml -> Not supported
> web-fragment.xml -> /META-INF/
> beans.xml -> /META-INF/
> persistence.xml -> /META-INF/
> ejb-jar.xml -> /META-INF/
> {code}
> EnterpriseArchive
> {code}
> beans.xml -> Not supported
> persistence.xml -> Not supported
> ejb-jar.xml -> Not supported
> application.xml -> /META-INF/
> {code}
> One common mistake is using addAsManifestResource on WebArchives. A quickfix / suggestion would be to use addAsWebInfResource for the files located in /WEB-INF/
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-18587) Error when opening a java file that is not in the project build path
by Lucia Jelinkova (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18587?page=com.atlassian.jira.plugi... ]
Lucia Jelinkova commented on JBIDE-18587:
-----------------------------------------
I cannot reproduce the issue on older releases and I do not have 4.2.0.CR1 installed. However, when I open java file that is not on the classpath on the JBDS 9.0.0.alpha2 I do no see any error in error log. So assuming it is fixed and closing the issue.
> Error when opening a java file that is not in the project build path
> --------------------------------------------------------------------
>
> Key: JBIDE-18587
> URL: https://issues.jboss.org/browse/JBIDE-18587
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: arquillian
> Affects Versions: 4.2.0.CR1
> Reporter: Xavier Coulon
> Assignee: Snjezana Peco
> Fix For: 4.3.0.Alpha2
>
>
> I had the following error in the Error Logs when opening a Java file that was not in the build path:
> {code}
> Java Model Exception: Java Model Status [src/test/generated/com/sample [in sample is not on its project's build path]
> at org.eclipse.jdt.internal.core.JavaElement.newJavaModelException(JavaElement.java:544)
> at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:247)
> at org.eclipse.jdt.internal.core.Openable.openAncestors(Openable.java:505)
> at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:241)
> at org.eclipse.jdt.internal.core.Openable.openAncestors(Openable.java:505)
> at org.eclipse.jdt.internal.core.CompilationUnit.openAncestors(CompilationUnit.java:1173)
> at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:241)
> at org.eclipse.jdt.internal.core.JavaElement.openWhenClosed(JavaElement.java:557)
> at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:294)
> at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:280)
> at org.eclipse.jdt.internal.core.JavaElement.getChildren(JavaElement.java:235)
> at org.eclipse.jdt.internal.core.JavaElement.getChildrenOfType(JavaElement.java:249)
> at org.eclipse.jdt.internal.core.CompilationUnit.getTypes(CompilationUnit.java:920)
> at org.eclipse.jdt.internal.core.CompilationUnit.getAllTypes(CompilationUnit.java:605)
> at org.jboss.tools.arquillian.ui.internal.commands.ArquillianPropertyTester.test(ArquillianPropertyTester.java:53)
> at org.eclipse.core.internal.expressions.Property.test(Property.java:58)
> at org.eclipse.core.internal.expressions.TestExpression.evaluate(TestExpression.java:99)
> at org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53)
> at org.eclipse.core.internal.expressions.AdaptExpression.evaluate(AdaptExpression.java:106)
> at org.eclipse.core.internal.expressions.CompositeExpression.evaluateOr(CompositeExpression.java:68)
> at org.eclipse.core.internal.expressions.OrExpression.evaluate(OrExpression.java:21)
> at org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53)
> at org.eclipse.core.internal.expressions.IterateExpression.evaluate(IterateExpression.java:189)
> at org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53)
> at org.eclipse.core.internal.expressions.WithExpression.evaluate(WithExpression.java:72)
> at org.eclipse.e4.ui.internal.workbench.ContributionsAnalyzer.isVisible(ContributionsAnalyzer.java:256)
> at org.eclipse.e4.ui.workbench.renderers.swt.ContributionRecord.computeVisibility(ContributionRecord.java:166)
> at org.eclipse.e4.ui.workbench.renderers.swt.ContributionRecord.updateVisibility(ContributionRecord.java:96)
> at org.eclipse.e4.ui.workbench.renderers.swt.MenuManagerRendererFilter.updateElementVisibility(MenuManagerRendererFilter.java:188)
> at org.eclipse.e4.ui.workbench.renderers.swt.MenuManagerRendererFilter.updateElementVisibility(MenuManagerRendererFilter.java:199)
> at org.eclipse.ui.internal.WorkbenchWindow$8.run(WorkbenchWindow.java:699)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3983)
> at org.eclipse.swt.widgets.Display.observerProc(Display.java:3573)
> at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method)
> at org.eclipse.swt.widgets.Display.applicationNextEventMatchingMask(Display.java:4989)
> at org.eclipse.swt.widgets.Display.applicationProc(Display.java:5367)
> at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method)
> at org.eclipse.swt.widgets.Widget.callSuper(Widget.java:221)
> at org.eclipse.swt.widgets.Widget.mouseDownSuper(Widget.java:1101)
> at org.eclipse.swt.widgets.Tree.mouseDownSuper(Tree.java:2044)
> at org.eclipse.swt.widgets.Widget.mouseDown(Widget.java:1093)
> at org.eclipse.swt.widgets.Control.mouseDown(Control.java:2563)
> at org.eclipse.swt.widgets.Tree.mouseDown(Tree.java:2012)
> at org.eclipse.swt.widgets.Display.windowProc(Display.java:5627)
> at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method)
> at org.eclipse.swt.widgets.Widget.callSuper(Widget.java:221)
> at org.eclipse.swt.widgets.Widget.windowSendEvent(Widget.java:2105)
> at org.eclipse.swt.widgets.Shell.windowSendEvent(Shell.java:2329)
> at org.eclipse.swt.widgets.Display.windowProc(Display.java:5691)
> at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method)
> at org.eclipse.swt.widgets.Display.applicationSendEvent(Display.java:5128)
> at org.eclipse.swt.widgets.Display.applicationProc(Display.java:5277)
> at org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method)
> at org.eclipse.swt.internal.cocoa.NSApplication.sendEvent(NSApplication.java:128)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3655)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151)
> 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.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:380)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:484)
> 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)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-18587) Error when opening a java file that is not in the project build path
by Lucia Jelinkova (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18587?page=com.atlassian.jira.plugi... ]
Lucia Jelinkova closed JBIDE-18587.
-----------------------------------
> Error when opening a java file that is not in the project build path
> --------------------------------------------------------------------
>
> Key: JBIDE-18587
> URL: https://issues.jboss.org/browse/JBIDE-18587
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: arquillian
> Affects Versions: 4.2.0.CR1
> Reporter: Xavier Coulon
> Assignee: Snjezana Peco
> Fix For: 4.3.0.Alpha2
>
>
> I had the following error in the Error Logs when opening a Java file that was not in the build path:
> {code}
> Java Model Exception: Java Model Status [src/test/generated/com/sample [in sample is not on its project's build path]
> at org.eclipse.jdt.internal.core.JavaElement.newJavaModelException(JavaElement.java:544)
> at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:247)
> at org.eclipse.jdt.internal.core.Openable.openAncestors(Openable.java:505)
> at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:241)
> at org.eclipse.jdt.internal.core.Openable.openAncestors(Openable.java:505)
> at org.eclipse.jdt.internal.core.CompilationUnit.openAncestors(CompilationUnit.java:1173)
> at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:241)
> at org.eclipse.jdt.internal.core.JavaElement.openWhenClosed(JavaElement.java:557)
> at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:294)
> at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:280)
> at org.eclipse.jdt.internal.core.JavaElement.getChildren(JavaElement.java:235)
> at org.eclipse.jdt.internal.core.JavaElement.getChildrenOfType(JavaElement.java:249)
> at org.eclipse.jdt.internal.core.CompilationUnit.getTypes(CompilationUnit.java:920)
> at org.eclipse.jdt.internal.core.CompilationUnit.getAllTypes(CompilationUnit.java:605)
> at org.jboss.tools.arquillian.ui.internal.commands.ArquillianPropertyTester.test(ArquillianPropertyTester.java:53)
> at org.eclipse.core.internal.expressions.Property.test(Property.java:58)
> at org.eclipse.core.internal.expressions.TestExpression.evaluate(TestExpression.java:99)
> at org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53)
> at org.eclipse.core.internal.expressions.AdaptExpression.evaluate(AdaptExpression.java:106)
> at org.eclipse.core.internal.expressions.CompositeExpression.evaluateOr(CompositeExpression.java:68)
> at org.eclipse.core.internal.expressions.OrExpression.evaluate(OrExpression.java:21)
> at org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53)
> at org.eclipse.core.internal.expressions.IterateExpression.evaluate(IterateExpression.java:189)
> at org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53)
> at org.eclipse.core.internal.expressions.WithExpression.evaluate(WithExpression.java:72)
> at org.eclipse.e4.ui.internal.workbench.ContributionsAnalyzer.isVisible(ContributionsAnalyzer.java:256)
> at org.eclipse.e4.ui.workbench.renderers.swt.ContributionRecord.computeVisibility(ContributionRecord.java:166)
> at org.eclipse.e4.ui.workbench.renderers.swt.ContributionRecord.updateVisibility(ContributionRecord.java:96)
> at org.eclipse.e4.ui.workbench.renderers.swt.MenuManagerRendererFilter.updateElementVisibility(MenuManagerRendererFilter.java:188)
> at org.eclipse.e4.ui.workbench.renderers.swt.MenuManagerRendererFilter.updateElementVisibility(MenuManagerRendererFilter.java:199)
> at org.eclipse.ui.internal.WorkbenchWindow$8.run(WorkbenchWindow.java:699)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3983)
> at org.eclipse.swt.widgets.Display.observerProc(Display.java:3573)
> at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method)
> at org.eclipse.swt.widgets.Display.applicationNextEventMatchingMask(Display.java:4989)
> at org.eclipse.swt.widgets.Display.applicationProc(Display.java:5367)
> at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method)
> at org.eclipse.swt.widgets.Widget.callSuper(Widget.java:221)
> at org.eclipse.swt.widgets.Widget.mouseDownSuper(Widget.java:1101)
> at org.eclipse.swt.widgets.Tree.mouseDownSuper(Tree.java:2044)
> at org.eclipse.swt.widgets.Widget.mouseDown(Widget.java:1093)
> at org.eclipse.swt.widgets.Control.mouseDown(Control.java:2563)
> at org.eclipse.swt.widgets.Tree.mouseDown(Tree.java:2012)
> at org.eclipse.swt.widgets.Display.windowProc(Display.java:5627)
> at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method)
> at org.eclipse.swt.widgets.Widget.callSuper(Widget.java:221)
> at org.eclipse.swt.widgets.Widget.windowSendEvent(Widget.java:2105)
> at org.eclipse.swt.widgets.Shell.windowSendEvent(Shell.java:2329)
> at org.eclipse.swt.widgets.Display.windowProc(Display.java:5691)
> at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method)
> at org.eclipse.swt.widgets.Display.applicationSendEvent(Display.java:5128)
> at org.eclipse.swt.widgets.Display.applicationProc(Display.java:5277)
> at org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method)
> at org.eclipse.swt.internal.cocoa.NSApplication.sendEvent(NSApplication.java:128)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3655)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151)
> 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.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:380)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:484)
> 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)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-19645) Remove seam 3 features from JBDS, JBT default install; add new connector to Central
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19645?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-19645:
---------------------------------------------
[~nickboldt] yes and again - the updatessite stuff is not what Burr called visible.
And that is listed in extensions under preferences I also do not consider very visible.
Use of Java 1 is more visible than that and that is also not something we support.
> Remove seam 3 features from JBDS, JBT default install; add new connector to Central
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-19645
> URL: https://issues.jboss.org/browse/JBIDE-19645
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi-extensions, central, updatesite
> Affects Versions: 4.3.0.Alpha2
> Reporter: Nick Boldt
> Assignee: Alexey Kazakov
> Fix For: 4.3.0.Beta1
>
> Attachments: jbds8alpha2-features-cdi-seam.png, jbds8alpha2-plugins-cdi.png, jbds8alpha2-plugins-seam.png, jbt43alpha2-features-cdi.png, jbt43alpha2-features-seam.png, jbt43alpha2-plugins-cdi.png, jbt43alpha2-plugins-seam-3-and-seam3.png, validation.png
>
>
> Burr has requested we also remove Seam 3. So I've assumed we'll do it the same way we did for Seam 2:
> * remove from CoreTools categories on update sites
> * remove from JBDS core.feature
> * create new connectors in JBT and JBDS Central
> [~burrsutter] [~maxandersen] please confirm this is the path you want taken for all the renaming features with "seam" in their name.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-15884) Allow the runBrowserSim command to accept a URL as a parameter
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15884?page=com.atlassian.jira.plugi... ]
Ilya Buziuk commented on JBIDE-15884:
-------------------------------------
[~vineet.reynolds], usage of the command:
{code}
<command
required="false"
serialization="org.jboss.tools.browsersim.eclipse.commands.runBrowserSimforCheatsheet(ur..."/>
{code}
Also want to give a heads up. I guess, cheatsheets which use browsersim command are broken for now, due to the fact that while refactoring redundant *vpe* name prefix was removed from plugins, packages, and commands declaration. If you point me to the repos where browsersim is used for cheatsheets I would provide PRs with fixes.
> Allow the runBrowserSim command to accept a URL as a parameter
> --------------------------------------------------------------
>
> Key: JBIDE-15884
> URL: https://issues.jboss.org/browse/JBIDE-15884
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: browsersim
> Affects Versions: 4.1.0.Final
> Reporter: Vineet Reynolds
> Assignee: Ilya Buziuk
> Priority: Minor
> Fix For: 4.3.0.Beta1
>
>
> Apologies for not setting the Affect version; I'm not sure which JBIDE version is affected.
> When creating a cheatsheet in JBDS 7.0.1.GA (for JDF-497), I'm using the {{org.jboss.tools.vpe.browsersim.eclipse.commands.runBrowserSim}} command in the cheatsheet. This launches BrowserSim successfully (when I'm in the correct perspective). However, BrowserSim navigates to about:blank so the cheatsheet requires users to manually key in the URL. It would be nice to have the launch URL specified as a configurable value.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-18772) Include publish.sh in parent pom as versioned maven dependency
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18772?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-18772:
---------------------------------------------
the above examples are the minority and most of these does *not* make sense to share the same root parent jbosstools pom.
So I think we are comparing apple and oranges here and these are examples we should look at cleaning up/splitting out since we have over time added to much entangled info into that one single jbosstools parent pom.
> Include publish.sh in parent pom as versioned maven dependency
> --------------------------------------------------------------
>
> Key: JBIDE-18772
> URL: https://issues.jboss.org/browse/JBIDE-18772
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build
> Reporter: Max Rydahl Andersen
> Assignee: Mickael Istria
> Priority: Critical
> Fix For: 4.3.0.Beta1
>
>
> instead of relying to publish.sh being on master, we should use a versioned publish.sh (or maybe even mojo) that the build then uses.
> suggestion:
> publish.sh (or mojo) gets released to our maven repo, use it in the pom.xml to perform publishing.
> What this helps with is:
> a) can do changes to publish mechanism without affecting every past builds.
> b) more movable build system
> c) isolated testing possible
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-19343) integration tests do not fetch their required runtimes if not present in the cache folder
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19343?page=com.atlassian.jira.plugi... ]
Mickael Istria closed JBIDE-19343.
----------------------------------
Yes, let's close it.
I'm not sure the applied patch is 100% perfect for the use-case, but it's not something that is easy to fixed on our side, as it's more because of Maven not allowing boolean expressions.
> integration tests do not fetch their required runtimes if not present in the cache folder
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-19343
> URL: https://issues.jboss.org/browse/JBIDE-19343
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: arquillian, build, server
> Affects Versions: 4.2.3.Beta1, 4.3.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Mickael Istria
> Priority: Minor
> Fix For: 4.3.0.Alpha2
>
>
> There's a problem w/ integration tests not properly bootstrapping (downloading) their runtimes if not present in the cache folder (see jbosstools-dev thread: http://lists.jboss.org/pipermail/jbosstools-dev/2015-February/009770.html )
> Looks like default maven lifecycle causes the pre-integration-test phase to fire, which is fine when we plan to run tests.
> There are a number of such phase bindings in this test:
> https://github.com/jbosstools/jbosstools-server/blob/jbosstools-4.2.x/as/...
> And I think this step can be skipped w/ *-DskipTests*.
> But the bigger problem is... why won't Jenkins fetch missing deps when they're not in the cache folder?
> Here are some console log snipped from builds 119 - 123:
> {code}
> 11:38:04 [ERROR] Failed to execute goal com.googlecode.maven-download-plugin:maven-download-plugin:1.1.0:wget (install-eap-6.1.0) on project org.jboss.tools.as.test.core: IO Error: /home/hudson/static_build_env/jbds/download-cache/jboss-eap-6.1.1.zip (No such file or directory) -> [Help 1]
> 13:29:23 [ERROR] Failed to execute goal com.googlecode.maven-download-plugin:maven-download-plugin:1.1.0:wget (install-wildfly-8.0.0.Beta1) on project org.jboss.tools.as.test.core: IO Error: /home/hudson/static_build_env/jbds/download-cache/wildfly-8.0.0.Beta1.zip (No such file or directory) -> [Help 1]
> 16:15:15 [ERROR] Failed to execute goal com.googlecode.maven-download-plugin:maven-download-plugin:1.1.0:wget (install-tomcat6) on project org.jboss.tools.wtp.runtimes.tomcat.tests: IO Error: /home/hudson/static_build_env/jbds/download-cache/apache-tomcat-6.0.39.zip (No such file or directory) -> [Help 1]
> {code} -- https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-server_4....
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-18987) [VIsual Preview] IllegalArgumentException: Path must include project and resource name: /favicon.ico
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18987?page=com.atlassian.jira.plugi... ]
Vlado Pakan closed JBIDE-18987.
-------------------------------
Verified with JBDS 9.0.0.Alpha2-v20150421-1151-B25
> [VIsual Preview] IllegalArgumentException: Path must include project and resource name: /favicon.ico
> ----------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18987
> URL: https://issues.jboss.org/browse/JBIDE-18987
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: visual-page-editor-core
> Affects Versions: 4.2.1.Final
> Environment: Ubuntu Linux x86_64
> OpenJDK 7
> SWT_GTK3=1
> Reporter: Denis Golovin
> Assignee: Konstantin Marmalyukov
> Priority: Minor
> Fix For: 4.3.0.Alpha2
>
>
> {code}Exception in thread "Thread-902" java.lang.IllegalArgumentException: Path must include project and resource name: /favicon.ico
> at org.eclipse.core.runtime.Assert.isLegal(Assert.java:63)
> at org.eclipse.core.internal.resources.Workspace.newResource(Workspace.java:2137)
> at org.eclipse.core.internal.resources.Container.getFile(Container.java:208)
> at org.jboss.tools.vpe.preview.core.transform.VpvController.getResource(VpvController.java:54)
> at org.jboss.tools.vpe.preview.core.server.VpvSocketProcessor.processRequest(VpvSocketProcessor.java:83)
> at org.jboss.tools.vpe.preview.core.server.VpvSocketProcessor.run(VpvSocketProcessor.java:68)
> at java.lang.Thread.run(Thread.java:745)
> Exception in thread "Thread-905" java.lang.IllegalArgumentException: Path must include project and resource name: /favicon.ico
> at org.eclipse.core.runtime.Assert.isLegal(Assert.java:63)
> at org.eclipse.core.internal.resources.Workspace.newResource(Workspace.java:2137)
> at org.eclipse.core.internal.resources.Container.getFile(Container.java:208)
> at org.jboss.tools.vpe.preview.core.transform.VpvController.getResource(VpvController.java:54)
> at org.jboss.tools.vpe.preview.core.server.VpvSocketProcessor.processRequest(VpvSocketProcessor.java:83)
> at org.jboss.tools.vpe.preview.core.server.VpvSocketProcessor.run(VpvSocketProcessor.java:68)
> at java.lang.Thread.run(Thread.java:745)
> Exception in thread "Thread-919" java.lang.IllegalArgumentException: Path must include project and resource name: /favicon.ico
> at org.eclipse.core.runtime.Assert.isLegal(Assert.java:63)
> at org.eclipse.core.internal.resources.Workspace.newResource(Workspace.java:2137)
> at org.eclipse.core.internal.resources.Container.getFile(Container.java:208)
> at org.jboss.tools.vpe.preview.core.transform.VpvController.getResource(VpvController.java:54)
> at org.jboss.tools.vpe.preview.core.server.VpvSocketProcessor.processRequest(VpvSocketProcessor.java:83)
> at org.jboss.tools.vpe.preview.core.server.VpvSocketProcessor.run(VpvSocketProcessor.java:68)
> at java.lang.Thread.run(Thread.java:745){code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-14610) Design http://download.jboss.org/jbosstools structure
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14610?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-14610:
---------------------------------------------
https://issues.jboss.org/browse/JBIDE-18236 is the issue we got about how best find builds etc. for modules.
> Design http://download.jboss.org/jbosstools structure
> -----------------------------------------------------
>
> Key: JBIDE-14610
> URL: https://issues.jboss.org/browse/JBIDE-14610
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: build, updatesite
> Affects Versions: 4.1.0.Beta1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 4.3.0.Beta1
>
>
> We have several types of objects which names should be presented in site stucture:
> # Project: jbosstools
> # Project Version: 4.1.0.Beta2,4.1.0.CR1, 4.1.0.Final
> # Subproject: core, soatools
> # Module: base, javaee, central, freemarker and etc.
> # Distribution Type: updates|builds
> # Bits Type: stable|development|nightly
> # Targeted Eclipse: indigo|juno|kepler
> # You name it ...
> Now we mostly use following patterns to publish nightly bits, but not always and not for every project:
> # aggregated update sites: $\{Project Name\}/updates/$\{Bits Type\}/$\{Subproject Name\}/$\{Targeted Eclipse\}
> # jbosstools modules composite nightly update sites are in $\{Project Name\}/builds/staging and it has no structure
> # jbosstools modules builds are published to $\{Project Name\}/builds/$\{Bits Type\} and it seems strategy of publishing is always being changed here, there is folder that match subcomponent name 'core' that was updated last time in February and 'trunk' folder that contains recent bits
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-13372) improve usability of jiralint emails
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13372?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-13372:
----------------------------------------
Fix Version/s: 4.2.0.Final
(was: 4.2.x)
> improve usability of jiralint emails
> ------------------------------------
>
> Key: JBIDE-13372
> URL: https://issues.jboss.org/browse/JBIDE-13372
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build
> Affects Versions: 4.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Minor
> Fix For: 4.2.0.Final
>
>
> Could these be reformatted to list the names of the offenders at the top of the email, so we don't have to waste time scanning to see whose name is associated w/ the incorrectly versioned jiras?
> Better, can they simply be sent to the people who've set bad fixVersions, rather than the whole list? The only person who needs to see the email below is Snjezana.
> {code}
> -------- Original Message --------
> Subject: Weekly jira sanity check - jbosstools-jiralint - Build # 138 - Still Unstable!
> Date: Sun, 13 Jan 2013 00:01:28 -0500 (EST)
> From: ci-builds(a)redhat.com
> To: external-exadel-list(a)redhat.com
> This is the weekly check for jira problems.
> Please fix the issues outlined below if there are any. Thank you!
> jbosstools-jiralint - Build # 138 - Still Unstable:
> Check console output at http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-jiralint/138/ to view the results.
> 1 tests 1 failure(s) / -2
> 1 tests failed.
> FAILED: ToolsIllegalFixVersion.ToolsIllegalFixVersion.JBIDE-13332_snjeza
> Error Message:
> https://jira.jboss.org/browse/JBIDE-13332 (last update: 22 days, 10:21:51.551414) -> Issue have been resolved with an illegal fix version, i.e. an .x version, LATER or no fix version at all. This means it will not be shown in the right release notes so neither developers or users can see where things happend. Please adjust the issue so it correctly states the proper fix version! Thank you! See http://bit.ly/aTUeGq for how to track down right fix versions.
> Stack Trace:
> JBIDE-13332: Update list of quickstarts to be consistent with current goals(https://jira.jboss.org/browse/JBIDE-13332)
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-17297) JBoss Central crashes and brings down JBDS 8 Beta 1
by Radim Hopp (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17297?page=com.atlassian.jira.plugi... ]
Radim Hopp closed JBIDE-17297.
------------------------------
I can confirm, that upgrading bluejeans to latest version does fix this issue. Closing.
> JBoss Central crashes and brings down JBDS 8 Beta 1
> ---------------------------------------------------
>
> Key: JBIDE-17297
> URL: https://issues.jboss.org/browse/JBIDE-17297
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, upstream
> Affects Versions: 4.2.0.Beta1
> Environment: JBDS 8 Beta1, Fedora 20, multiple JVMs - Oracle JDK 8 (1.8.0_05), Oracle JDK 7 (1.7.0_55)
> Reporter: Vineet Reynolds
> Assignee: Snjezana Peco
> Priority: Critical
> Fix For: 4.2.3.Final, 4.3.0.Alpha2
>
>
> I encounter crashes in JBDS 8 Beta 1, when JBDS Central is loaded.
> The following stack trace was recorded:
> {noformat}
> !MESSAGE Cannot load bundle com.jboss.jbds.central.discovery_8.0.0.Beta1_v20140408_2329_B102.jar_115481158031680986.jar from url /home/vreynolds/workspaces/JBDS8Workspaces/WFK/.metadata/.plugins/org.jboss.tools.central/proxyWizards/1400494422919/com.jboss.jbds.central.discovery_8.0.0.Beta1_v20140408_2329_B102.jar_115481158031680986.jar: zip file is empty
> !STACK 0
> java.util.zip.ZipException: zip file is empty
> at java.util.zip.ZipFile.open(Native Method)
> at java.util.zip.ZipFile.<init>(ZipFile.java:220)
> at java.util.zip.ZipFile.<init>(ZipFile.java:150)
> at java.util.jar.JarFile.<init>(JarFile.java:166)
> at java.util.jar.JarFile.<init>(JarFile.java:130)
> at org.jboss.tools.project.examples.internal.discovery.xpl.DiscoveryRegistryStrategy.processBundle(DiscoveryRegistryStrategy.java:137)
> at org.jboss.tools.project.examples.internal.discovery.xpl.DiscoveryRegistryStrategy.processBundles(DiscoveryRegistryStrategy.java:126)
> at org.jboss.tools.project.examples.internal.discovery.xpl.DiscoveryRegistryStrategy.onStart(DiscoveryRegistryStrategy.java:78)
> at org.eclipse.core.internal.registry.ExtensionRegistry.<init>(ExtensionRegistry.java:725)
> at org.jboss.tools.project.examples.internal.discovery.xpl.ExternalBundleDiscoveryStrategy.performDiscovery(ExternalBundleDiscoveryStrategy.java:125)
> at org.jboss.tools.project.examples.internal.discovery.ChainedDiscoveryStrategy.performDiscovery(ChainedDiscoveryStrategy.java:62)
> at org.eclipse.mylyn.internal.discovery.core.model.ConnectorDiscovery.performDiscovery(ConnectorDiscovery.java:114)
> at org.jboss.tools.central.internal.discovery.wizards.ProxyWizardManager.loadWizards(ProxyWizardManager.java:101)
> at org.jboss.tools.central.internal.discovery.wizards.ProxyWizardManager.getProxyWizards(ProxyWizardManager.java:121)
> at org.jboss.tools.central.editors.GettingStartedPage.getProxyWizards(GettingStartedPage.java:555)
> at org.jboss.tools.central.editors.GettingStartedPage.access$11(GettingStartedPage.java:553)
> at org.jboss.tools.central.editors.GettingStartedPage$5.run(GettingStartedPage.java:511)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> !SESSION 2014-05-19 15:45:30.045 -----------------------------------------------
> {noformat}
> To recover from this, I needed to be quick enough to uncheck the "load on startup" checkbox to disable JBoss Central. Re-opening JBoss Central at any other point in time causes the crash to be reproducible.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBDS-3345) Errors when starting FSW 6.0.0.GA from JBDS 8.0.2.GA with JDK 1.8
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-3345?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBDS-3345:
-------------------------------------------
my question is more why FSW needs this when everything else seem to work just fine ?
I would consider it bad practice if we need to start messing with the PATH
> Errors when starting FSW 6.0.0.GA from JBDS 8.0.2.GA with JDK 1.8
> -----------------------------------------------------------------
>
> Key: JBDS-3345
> URL: https://issues.jboss.org/browse/JBDS-3345
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: server
> Affects Versions: 8.0.2.GA
> Environment: Fedora 21 x86_64
> JBDS 8.0.2.GA with Oracle JDK 1.8.0_25 and Oracle JDK 1.7.0_71
> Reporter: Andrej Podhradsky
> Priority: Critical
> Attachments: compiler.png, console.png, errors.txt, error_log.txt, installed_jre.png, runtime_jre.png, server.log
>
>
> FSW 6.0.0.GA supports java 6 and 7, so if we want to run this server on JBDS 8 with jdk 8 we need to add another jdk to the JBDS, e.g. jdk 7. But this doesn't work, see errors in the attached file.
> Moreover, we are not able to stop the server from IDE, the process is still alive and we have to kill it manually.
> Note that this happens only when we install JBDS 8.0.2 with jdk 8, if we install it with jdk 7 the server works fine.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-19453) Remote host information does not fit in the server editor
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19453?page=com.atlassian.jira.plugi... ]
Martin Malina updated JBIDE-19453:
----------------------------------
Attachment: server-editor-2.png
Here's a screenshot of the current situation (as of JBDS 9.0.0.Alpha2 BYOE):
!server-editor-2.png!
I tried making my Eclipse window bigger and reopening, but it didn't help.
> Remote host information does not fit in the server editor
> ---------------------------------------------------------
>
> Key: JBIDE-19453
> URL: https://issues.jboss.org/browse/JBIDE-19453
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.3.Beta1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.3.0.Beta1
>
> Attachments: remote-runtime-does-not-fit.png, server-editor-2.png
>
>
> Today I noticed this. When I set up a remote server and then open it in the Server editor, the part under Server Behavior where it shows the remote host configuration (e.g. Remote Server Home) does not fix - it needs more space to the right, but it's hidden and there is no way to scroll to view it.
> !remote-runtime-does-not-fit.png!
> The same problem applies to both JBDS 8.1.0.Beta1 and JBDS 9.0.0.Alpha1. So you may want to clone this for 4.3.x.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-19453) Remote host information does not fit in the server editor
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19453?page=com.atlassian.jira.plugi... ]
Martin Malina updated JBIDE-19453:
----------------------------------
Fix Version/s: 4.3.0.Beta1
(was: 4.3.0.Alpha2)
> Remote host information does not fit in the server editor
> ---------------------------------------------------------
>
> Key: JBIDE-19453
> URL: https://issues.jboss.org/browse/JBIDE-19453
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.3.Beta1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.3.0.Beta1
>
> Attachments: remote-runtime-does-not-fit.png
>
>
> Today I noticed this. When I set up a remote server and then open it in the Server editor, the part under Server Behavior where it shows the remote host configuration (e.g. Remote Server Home) does not fix - it needs more space to the right, but it's hidden and there is no way to scroll to view it.
> !remote-runtime-does-not-fit.png!
> The same problem applies to both JBDS 8.1.0.Beta1 and JBDS 9.0.0.Alpha1. So you may want to clone this for 4.3.x.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-18055) NullPionterException in VPE Preview Editor initialization
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18055?page=com.atlassian.jira.plugi... ]
Vlado Pakan closed JBIDE-18055.
-------------------------------
Verified with JBDS 9.0.0.Alpha2-v20150421-1151-B25
> NullPionterException in VPE Preview Editor initialization
> ---------------------------------------------------------
>
> Key: JBIDE-18055
> URL: https://issues.jboss.org/browse/JBIDE-18055
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: visual-page-editor-core
> Affects Versions: 4.2.0.Beta3
> Reporter: Denis Golovin
> Assignee: Konstantin Marmalyukov
> Priority: Minor
> Fix For: 4.3.0.Alpha2
>
>
> Exception below can happen sometimes in case re-sizing visual preview part while preview server serving the editor is not started yet.
> {code}java.lang.NullPointerException
> at org.jboss.tools.vpe.preview.core.server.VpvServer.getPort(VpvServer.java:66)
> at org.jboss.tools.vpe.preview.editor.VpvEditor.formRequestToServer(VpvEditor.java:503)
> at org.jboss.tools.vpe.preview.editor.VpvEditor.reload(VpvEditor.java:494)
> at org.jboss.tools.vpe.preview.editor.VpvEditorPart.updateVisualEditorVisibility(VpvEditorPart.java:769)
> at org.jboss.tools.vpe.preview.editor.VpvEditorPart$5.controlResized(VpvEditorPart.java:386)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:235)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4486)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1412)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1393)
> at org.eclipse.swt.widgets.Control.setBounds(Control.java:1042)
> at org.eclipse.swt.widgets.Composite.setBounds(Composite.java:1435)
> at org.eclipse.swt.widgets.Control.setBounds(Control.java:851)
> at org.eclipse.swt.custom.SashForm.onDragSash(SashForm.java:288)
> at org.eclipse.swt.custom.SashForm$1.handleEvent(SashForm.java:90)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4486)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1412)
> at org.eclipse.swt.widgets.Widget.sendSelectionEvent(Widget.java:1526)
> at org.eclipse.swt.widgets.Sash.gtk_motion_notify_event(Sash.java:396)
> at org.eclipse.swt.widgets.Widget.windowProc(Widget.java:2104)
> at org.eclipse.swt.widgets.Control.windowProc(Control.java:5510)
> at org.eclipse.swt.widgets.Display.windowProc(Display.java:4700)
> at org.eclipse.swt.internal.gtk.OS._gtk_main_do_event(Native Method)
> at org.eclipse.swt.internal.gtk.OS.gtk_main_do_event(OS.java:9074)
> at org.eclipse.swt.widgets.Display.eventProc(Display.java:1253)
> at org.eclipse.swt.internal.gtk.OS._g_main_context_iteration(Native Method)
> at org.eclipse.swt.internal.gtk.OS.g_main_context_iteration(OS.java:2473)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3439)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151)
> 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.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:606)
> 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)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-19359) JSF or HTML5 Support: preferences enhancements
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19359?page=com.atlassian.jira.plugi... ]
Vlado Pakan closed JBIDE-19359.
-------------------------------
Verified with JBDS 9.0.0.Alpha2-v20150421-1151-B25
> JSF or HTML5 Support: preferences enhancements
> ----------------------------------------------
>
> Key: JBIDE-19359
> URL: https://issues.jboss.org/browse/JBIDE-19359
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: visual-page-editor-core
> Affects Versions: 4.3.0.Alpha1
> Reporter: Konstantin Marmalyukov
> Assignee: Konstantin Marmalyukov
> Fix For: 4.3.0.Alpha2
>
>
> 2. VPE Preference page should contain checkbox with choice: "Always ask" otherwise user will never be able to get dialog asking to choose between JSF and HTML5 support once he will check check box "Do not show this message again"
> 4. With GTK3 "Visual Editor Browser Engine" group within VPE prefrences page is hidden it would be more user friendly just disable it and add some label why it's disabled?.The same way as selecting of GTK for BrowserSim/CordovaSim works.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-18977) JBoss HTML Editor pollutes log with NullPointerExceptions
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18977?page=com.atlassian.jira.plugi... ]
Vlado Pakan closed JBIDE-18977.
-------------------------------
Verified with JBDS 9.0.0.Alpha2-v20150421-1151-B25
> JBoss HTML Editor pollutes log with NullPointerExceptions
> ---------------------------------------------------------
>
> Key: JBIDE-18977
> URL: https://issues.jboss.org/browse/JBIDE-18977
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: visual-page-editor-core
> Reporter: Denis Golovin
> Assignee: Konstantin Marmalyukov
> Fix For: 4.3.0.Alpha2
>
>
> {code}java.lang.NullPointerException
> at org.jboss.tools.vpe.preview.editor.VpvEditor$10.documentChanged(VpvEditor.java:671)
> at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument._fireDocumentChanged(BasicStructuredDocument.java:460)
> at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.fireStructuredDocumentEvent(BasicStructuredDocument.java:1184)
> at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.internalReplaceText(BasicStructuredDocument.java:1964)
> at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.replaceText(BasicStructuredDocument.java:2423)
> at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.replaceText(BasicStructuredDocument.java:2408)
> at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.access$2(JobSafeStructuredDocument.java:1)
> at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument$3.run(JobSafeStructuredDocument.java:141)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.wst.sse.ui.EditorExecutionContext.execute(EditorExecutionContext.java:149)
> at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.replaceText(JobSafeStructuredDocument.java:144)
> at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.replace(BasicStructuredDocument.java:2368)
> at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.access$0(JobSafeStructuredDocument.java:1)
> at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument$1.run(JobSafeStructuredDocument.java:103)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.wst.sse.ui.EditorExecutionContext.execute(EditorExecutionContext.java:149)
> at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.replace(JobSafeStructuredDocument.java:106)
> at org.eclipse.jface.text.projection.ProjectionTextStore.replace(ProjectionTextStore.java:111)
> at org.eclipse.jface.text.AbstractDocument.replace(AbstractDocument.java:1184)
> at org.eclipse.jface.text.AbstractDocument.replace(AbstractDocument.java:1210)
> at org.eclipse.jface.text.projection.ProjectionDocument.replace(ProjectionDocument.java:629)
> at org.eclipse.jface.text.DefaultDocumentAdapter.replaceTextRange(DefaultDocumentAdapter.java:248)
> at org.eclipse.swt.custom.StyledText.modifyContent(StyledText.java:7268)
> at org.eclipse.swt.custom.StyledText.sendKeyEvent(StyledText.java:8111)
> at org.eclipse.swt.custom.StyledText.doBackspace(StyledText.java:2285)
> at org.eclipse.swt.custom.StyledText.invokeAction(StyledText.java:7058)
> at org.eclipse.swt.custom.StyledText.handleKey(StyledText.java:5959)
> at org.eclipse.swt.custom.StyledText.handleKeyDown(StyledText.java:5986)
> at org.eclipse.swt.custom.StyledText$7.handleEvent(StyledText.java:5663)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4454)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1412)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1397)
> at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1424)
> at org.eclipse.swt.widgets.Widget.gtk_key_press_event(Widget.java:824)
> at org.eclipse.swt.widgets.Control.gtk_key_press_event(Control.java:3272)
> at org.eclipse.swt.widgets.Composite.gtk_key_press_event(Composite.java:769)
> at org.eclipse.swt.widgets.Widget.windowProc(Widget.java:2098)
> at org.eclipse.swt.widgets.Control.windowProc(Control.java:5513)
> at org.eclipse.swt.widgets.Display.windowProc(Display.java:4668)
> at org.eclipse.swt.internal.gtk.OS._gtk_main_do_event(Native Method)
> at org.eclipse.swt.internal.gtk.OS.gtk_main_do_event(OS.java:9106)
> at org.eclipse.swt.widgets.Display.eventProc(Display.java:1253)
> at org.eclipse.swt.internal.gtk.OS._g_main_context_iteration(Native Method)
> at org.eclipse.swt.internal.gtk.OS.g_main_context_iteration(OS.java:2477)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3407)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151)
> 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.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:380)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
> 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:606)
> 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)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-19350) Deployment/transfer operations cannot be canceled
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19350?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-19350.
---------------------------------
This has been verified already, closing.
> Deployment/transfer operations cannot be canceled
> -------------------------------------------------
>
> Key: JBIDE-19350
> URL: https://issues.jboss.org/browse/JBIDE-19350
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.3.0.Alpha1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.3.0.Alpha2
>
> Attachments: remote-publishing-stuck.png
>
>
> I tried deploying an ear with a nested utility project to a remote EAP 6.3 server with the management profile and it got stuck during publishing (10 %).
> I used the project from JBIDE-19043 - see "Steps to Reproduce".
> !remote-publishing-stuck.png!
> I wanted to get a more general use case before reporting this, but I'm still stuck at canceling of the publish task, so I decided to write this JIRA before killing off Eclipse - that is btw a serious problem as well - that you can't cancel the task.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-18907) Improve handling of inaccessible remote server [mgmt]
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18907?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-18907.
---------------------------------
> Improve handling of inaccessible remote server [mgmt]
> -----------------------------------------------------
>
> Key: JBIDE-18907
> URL: https://issues.jboss.org/browse/JBIDE-18907
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.1.CR1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.3.0.Alpha1
>
> Attachments: remote-connection-error.png
>
>
> With JBIDE-18513, it is now possible to set up a server that does not require any runtime at all (local or remote). The server setup is: remote, management operations, externally managed, no local runtime.
> When I tried it today, I started the server on the remote machine and then marked the server in eclipse as started. Then I wanted to deploy a project and got an error:
> !remote-connection-error.png!
> The underlying error is:
> {code}
> !ENTRY org.jboss.ide.eclipse.as.core 4 0 2014-12-09 13:37:52.037
> !MESSAGE JBossTools is unable to verify that the server is up and responsive.
> !STACK 0
> org.jboss.ide.eclipse.as.management.core.JBoss7ManangerException: java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://MARVIN:9990. The connection timed out
> at org.jboss.ide.eclipse.as.internal.management.wildfly8.Wildfly8Manager.execute(Wildfly8Manager.java:333)
> at org.jboss.ide.eclipse.as.internal.management.wildfly8.Wildfly8Manager.getServerState(Wildfly8Manager.java:263)
> at org.jboss.ide.eclipse.as.internal.management.wildfly8.Wildfly8ManagerService.getServerState(Wildfly8ManagerService.java:142)
> at org.jboss.ide.eclipse.as.management.core.JBoss7ManagerServiceProxy.getServerState(JBoss7ManagerServiceProxy.java:71)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.ManagementPublishController.isRunning(ManagementPublishController.java:113)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.ManagementPublishController.canPublishInternal(ManagementPublishController.java:136)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.ManagementPublishController.publishStart(ManagementPublishController.java:152)
> at org.jboss.tools.as.core.server.controllable.internal.DeployableServerBehavior.publishStart(DeployableServerBehavior.java:104)
> at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:942)
> at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:774)
> at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:3157)
> at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:345)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> Caused by: java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://MARVIN:9990. The connection timed out
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:129)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:71)
> at org.jboss.ide.eclipse.as.internal.management.wildfly8.Wildfly8Manager.execute(Wildfly8Manager.java:322)
> ... 12 more
> Caused by: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://MARVIN:9990. The connection timed out
> at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:120)
> at org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:256)
> at org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:70)
> at org.jboss.as.protocol.mgmt.FutureManagementChannel$Establishing.getChannel(FutureManagementChannel.java:204)
> at org.jboss.as.controller.client.impl.RemotingModelControllerClient.getOrCreateChannel(RemotingModelControllerClient.java:148)
> at org.jboss.as.controller.client.impl.RemotingModelControllerClient$1.getChannel(RemotingModelControllerClient.java:67)
> at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:117)
> at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:92)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:236)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:141)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:127)
> ... 14 more
> {code}
> It turned out that I forgot to setup the management port when I started the server on the server - I needed to add {code}-Djboss.bind.address.management=marvin{code}. With this it worked.
> My suggestion is that the tooling could check if the connection can be established when you press Start on the server.
> But it's just a suggestion - feel free to dismiss this idea ;)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-18907) Improve handling of inaccessible remote server [mgmt]
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18907?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-18907:
---------------------------------------
I just tried it now and what I don't like too much about it is that it will show Starting until time out is reached. I understand that this is because it works the same way as when the EAP server is actually started by the tooling - the time out is to ensure that the server has enough time to get started. This would be not really needed - when you click Start, you will typically have the server already started, so it might make more sense to get and error immediately if the poller can't reach the server.
But I guess it's good enough.
Once I started the server with the management port exposed, it worked as expected and I could deploy a module.
Verified in JBDS 9.0.0.Alpha2 B24 BYOE. Closing.
> Improve handling of inaccessible remote server [mgmt]
> -----------------------------------------------------
>
> Key: JBIDE-18907
> URL: https://issues.jboss.org/browse/JBIDE-18907
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.1.CR1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.3.0.Alpha1
>
> Attachments: remote-connection-error.png
>
>
> With JBIDE-18513, it is now possible to set up a server that does not require any runtime at all (local or remote). The server setup is: remote, management operations, externally managed, no local runtime.
> When I tried it today, I started the server on the remote machine and then marked the server in eclipse as started. Then I wanted to deploy a project and got an error:
> !remote-connection-error.png!
> The underlying error is:
> {code}
> !ENTRY org.jboss.ide.eclipse.as.core 4 0 2014-12-09 13:37:52.037
> !MESSAGE JBossTools is unable to verify that the server is up and responsive.
> !STACK 0
> org.jboss.ide.eclipse.as.management.core.JBoss7ManangerException: java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://MARVIN:9990. The connection timed out
> at org.jboss.ide.eclipse.as.internal.management.wildfly8.Wildfly8Manager.execute(Wildfly8Manager.java:333)
> at org.jboss.ide.eclipse.as.internal.management.wildfly8.Wildfly8Manager.getServerState(Wildfly8Manager.java:263)
> at org.jboss.ide.eclipse.as.internal.management.wildfly8.Wildfly8ManagerService.getServerState(Wildfly8ManagerService.java:142)
> at org.jboss.ide.eclipse.as.management.core.JBoss7ManagerServiceProxy.getServerState(JBoss7ManagerServiceProxy.java:71)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.ManagementPublishController.isRunning(ManagementPublishController.java:113)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.ManagementPublishController.canPublishInternal(ManagementPublishController.java:136)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.ManagementPublishController.publishStart(ManagementPublishController.java:152)
> at org.jboss.tools.as.core.server.controllable.internal.DeployableServerBehavior.publishStart(DeployableServerBehavior.java:104)
> at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:942)
> at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:774)
> at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:3157)
> at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:345)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> Caused by: java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://MARVIN:9990. The connection timed out
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:129)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:71)
> at org.jboss.ide.eclipse.as.internal.management.wildfly8.Wildfly8Manager.execute(Wildfly8Manager.java:322)
> ... 12 more
> Caused by: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://MARVIN:9990. The connection timed out
> at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:120)
> at org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:256)
> at org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:70)
> at org.jboss.as.protocol.mgmt.FutureManagementChannel$Establishing.getChannel(FutureManagementChannel.java:204)
> at org.jboss.as.controller.client.impl.RemotingModelControllerClient.getOrCreateChannel(RemotingModelControllerClient.java:148)
> at org.jboss.as.controller.client.impl.RemotingModelControllerClient$1.getChannel(RemotingModelControllerClient.java:67)
> at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:117)
> at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:92)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:236)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:141)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:127)
> ... 14 more
> {code}
> It turned out that I forgot to setup the management port when I started the server on the server - I needed to add {code}-Djboss.bind.address.management=marvin{code}. With this it worked.
> My suggestion is that the tooling could check if the connection can be established when you press Start on the server.
> But it's just a suggestion - feel free to dismiss this idea ;)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-19324) Arquillian core freezes Eclipse startup
by Lucia Jelinkova (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19324?page=com.atlassian.jira.plugi... ]
Lucia Jelinkova closed JBIDE-19324.
-----------------------------------
Verified JBDS 9.0.0.alpha2
> Arquillian core freezes Eclipse startup
> ---------------------------------------
>
> Key: JBIDE-19324
> URL: https://issues.jboss.org/browse/JBIDE-19324
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: arquillian, upstream
> Affects Versions: 4.3.0.Alpha1
> Reporter: Lucia Jelinkova
> Assignee: Snjezana Peco
> Priority: Blocker
> Fix For: 4.3.0.Alpha2
>
> Attachments: dump.txt, restart.ogv
>
>
> When I have arquillian.xml with at least one container defined and I open it with Arquillian editor and restart Eclipse, the Eclipse wont start and it freezes on loading arquillian core plugin (see screencast).
> I am also attaching thread dump (thanks to [~rhopp])
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-19508) Compile failed in org.jboss.tools.jmx.ui and org.jboss.tools.jmx.jvmmonitor.tools
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19508?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-19508.
---------------------------------
Seems to be fine in jenkins now. Closing.
> Compile failed in org.jboss.tools.jmx.ui and org.jboss.tools.jmx.jvmmonitor.tools
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-19508
> URL: https://issues.jboss.org/browse/JBIDE-19508
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.3.0.Alpha2
> Reporter: Nick Boldt
> Assignee: Rob Stryker
> Fix For: 4.3.0.Alpha2
>
>
> {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_Master/job/jbosstools-server_master/715/console}
> 00:02:37.945 [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.22.0:compile (default-compile) on project org.jboss.tools.jmx.ui: Compilation failure: Compilation failure:
> 00:02:37.946 [ERROR] /mnt/hudson_workspace/workspace/jbosstools-server_master/sources/jmx/plugins/org.jboss.tools.jmx.ui/src/org/jboss/tools/jmx/ui/internal/actions/ConnectDebuggerAction.java:[45]
> 00:02:37.947 [ERROR] return RemoteDebugActivator.isRemoteDebuggerConnected(wrapper.getDebugHost(), wrapper.getDebugPort());
> 00:02:37.947 [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^
> 00:02:37.947 [ERROR] The method isRemoteDebuggerConnected(String, int) is undefined for the type RemoteDebugActivator
> 00:02:37.948 [ERROR] /mnt/hudson_workspace/workspace/jbosstools-server_master/sources/jmx/plugins/org.jboss.tools.jmx.ui/src/org/jboss/tools/jmx/ui/internal/actions/ConnectDebuggerAction.java:[62]
> 00:02:37.948 [ERROR] ILaunchConfiguration config = RemoteDebugActivator.createOrGetDefaultLaunchConfiguration(
> 00:02:37.949 [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> 00:02:37.949 [ERROR] The method createOrGetDefaultLaunchConfiguration(String, String, IJavaProject, IJavaProject[]) is undefined for the type RemoteDebugActivator
> 00:02:37.949 [ERROR] /mnt/hudson_workspace/workspace/jbosstools-server_master/sources/jmx/plugins/org.jboss.tools.jmx.ui/src/org/jboss/tools/jmx/ui/internal/views/navigator/ActionProvider.java:[121]
> 00:02:37.950 [ERROR] if( RemoteDebugActivator.isRemoteDebuggerConnected(debuggable.getDebugHost(), debuggable.getDebugPort())) {
> 00:02:37.951 [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^
> 00:02:37.951 [ERROR] The method isRemoteDebuggerConnected(String, int) is undefined for the type RemoteDebugActivator
> 00:02:37.951 [ERROR] /mnt/hudson_workspace/workspace/jbosstools-server_master/sources/jmx/plugins/org.jboss.tools.jmx.ui/src/org/jboss/tools/jmx/ui/internal/actions/DisconnectDebuggerAction.java:[35]
> 00:02:37.952 [ERROR] return RemoteDebugActivator.isRemoteDebuggerConnected(wrapper.getDebugHost(), wrapper.getDebugPort());
> 00:02:37.952 [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^
> 00:02:37.953 [ERROR] The method isRemoteDebuggerConnected(String, int) is undefined for the type RemoteDebugActivator
> 00:02:37.953 [ERROR] /mnt/hudson_workspace/workspace/jbosstools-server_master/sources/jmx/plugins/org.jboss.tools.jmx.ui/src/org/jboss/tools/jmx/ui/internal/actions/DisconnectDebuggerAction.java:[39]
> 00:02:37.954 [ERROR] ILaunch l = RemoteDebugActivator.getExistingRemoteDebugLaunch(con.getDebugHost(), con.getDebugPort());
> 00:02:37.954 [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> 00:02:37.955 [ERROR] The method getExistingRemoteDebugLaunch(String, int) is undefined for the type RemoteDebugActivator
> 00:02:37.955 [ERROR] 5 problems (5 errors)
> 00:02:37.955 [ERROR] -> [Help 1]{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-19343) integration tests do not fetch their required runtimes if not present in the cache folder
by Lucia Jelinkova (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19343?page=com.atlassian.jira.plugi... ]
Lucia Jelinkova commented on JBIDE-19343:
-----------------------------------------
[~mickael_istria] Is it all fixed? Can we close this issue?
> integration tests do not fetch their required runtimes if not present in the cache folder
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-19343
> URL: https://issues.jboss.org/browse/JBIDE-19343
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: arquillian, build, server
> Affects Versions: 4.2.3.Beta1, 4.3.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Mickael Istria
> Priority: Minor
> Fix For: 4.3.0.Alpha2
>
>
> There's a problem w/ integration tests not properly bootstrapping (downloading) their runtimes if not present in the cache folder (see jbosstools-dev thread: http://lists.jboss.org/pipermail/jbosstools-dev/2015-February/009770.html )
> Looks like default maven lifecycle causes the pre-integration-test phase to fire, which is fine when we plan to run tests.
> There are a number of such phase bindings in this test:
> https://github.com/jbosstools/jbosstools-server/blob/jbosstools-4.2.x/as/...
> And I think this step can be skipped w/ *-DskipTests*.
> But the bigger problem is... why won't Jenkins fetch missing deps when they're not in the cache folder?
> Here are some console log snipped from builds 119 - 123:
> {code}
> 11:38:04 [ERROR] Failed to execute goal com.googlecode.maven-download-plugin:maven-download-plugin:1.1.0:wget (install-eap-6.1.0) on project org.jboss.tools.as.test.core: IO Error: /home/hudson/static_build_env/jbds/download-cache/jboss-eap-6.1.1.zip (No such file or directory) -> [Help 1]
> 13:29:23 [ERROR] Failed to execute goal com.googlecode.maven-download-plugin:maven-download-plugin:1.1.0:wget (install-wildfly-8.0.0.Beta1) on project org.jboss.tools.as.test.core: IO Error: /home/hudson/static_build_env/jbds/download-cache/wildfly-8.0.0.Beta1.zip (No such file or directory) -> [Help 1]
> 16:15:15 [ERROR] Failed to execute goal com.googlecode.maven-download-plugin:maven-download-plugin:1.1.0:wget (install-tomcat6) on project org.jboss.tools.wtp.runtimes.tomcat.tests: IO Error: /home/hudson/static_build_env/jbds/download-cache/apache-tomcat-6.0.39.zip (No such file or directory) -> [Help 1]
> {code} -- https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-server_4....
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-19267) OpenOns for batch artifacts
by Lucia Jelinkova (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19267?page=com.atlassian.jira.plugi... ]
Lucia Jelinkova commented on JBIDE-19267:
-----------------------------------------
[~scabanovich] Very nice description and test case.
> OpenOns for batch artifacts
> ---------------------------
>
> Key: JBIDE-19267
> URL: https://issues.jboss.org/browse/JBIDE-19267
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: batch
> Reporter: Alexey Kazakov
> Assignee: Daniel Azarov
> Labels: new_and_noteworthy
> Fix For: 4.3.0.Alpha2
>
>
> 1. Attribute \@ref - open java class.
> a) Collection<IBatchArtifact> a = IBatchProject.getArtifacts(String name); where %name% is the attribute value.
> b)IType t = IBatchArtifact.getType();
> It is an error if the collection has more than one element, but open-on may show list of options.
> 2. Attribute \@next - open \@id by value. Look only among siblings of owner element of \@next.
> 3. Attribute \@to - open @id by value. Look only among children of the grandparent of the owner element of @to.
> 4. Attribute \@restart - open @id by value. Look only among children of root element <job>.
> 5. Attribute properties/property/\@name - open java field.
> a) Take parent of properties element and take its \@ref attribute.
> b) Collection<IBatchArtifact> a = IBatchProject.getArtifacts(String name); where %name% is the attribute \@ref value.
> c) IBatchProperty p = IBatchArtifact.getProperty(String name); where %name% is the attribute \@name value.
> d) IField f = IBatchProperty.getFiled();
> *Test case*:
> EXECUTE:
> 1. Import project jbosstools-javaee/batch/itests/org.jboss.tools.batch.core.itest/projects/BatchTestProject
> 2. Open file /src/META-INF/batch-jobs/job-openon-1.xml in Batch Job Configuration Editor and switch to tab "Source"
> 3. Press Ctrl and click mouse to "batchlet1" in batchlet node
> ASSERT:
> Java Class "batch.MyBatchlet" opened in Java Editor (1. of Description)
> 4. Press Ctrl and click mouse to "myBatchletStep2" in node "<step id="myBatchletStep1" next="myBatchletStep2">"
> ASSERT:
> Node "<step id="myBatchletStep2">" selected in Batch Job Configuration Editor (2. of Description)
> 5. Same for attributes "to" and "restart" (3. and 4. of Description)
> 6. Press Ctrl and click mouse to "worktime" in node "<property name="worktime" value="#{jobProperties[%aaa%]}"/>"
> ASSERT:
> Java Class "batch.MyBatchlet" opened in Java Editor and Java Field "time" selected. (5. of Description)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-19267) OpenOns for batch artifacts
by Lucia Jelinkova (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19267?page=com.atlassian.jira.plugi... ]
Lucia Jelinkova closed JBIDE-19267.
-----------------------------------
Verified JBDS 9.0.0.alpha2
> OpenOns for batch artifacts
> ---------------------------
>
> Key: JBIDE-19267
> URL: https://issues.jboss.org/browse/JBIDE-19267
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: batch
> Reporter: Alexey Kazakov
> Assignee: Daniel Azarov
> Labels: new_and_noteworthy
> Fix For: 4.3.0.Alpha2
>
>
> 1. Attribute \@ref - open java class.
> a) Collection<IBatchArtifact> a = IBatchProject.getArtifacts(String name); where %name% is the attribute value.
> b)IType t = IBatchArtifact.getType();
> It is an error if the collection has more than one element, but open-on may show list of options.
> 2. Attribute \@next - open \@id by value. Look only among siblings of owner element of \@next.
> 3. Attribute \@to - open @id by value. Look only among children of the grandparent of the owner element of @to.
> 4. Attribute \@restart - open @id by value. Look only among children of root element <job>.
> 5. Attribute properties/property/\@name - open java field.
> a) Take parent of properties element and take its \@ref attribute.
> b) Collection<IBatchArtifact> a = IBatchProject.getArtifacts(String name); where %name% is the attribute \@ref value.
> c) IBatchProperty p = IBatchArtifact.getProperty(String name); where %name% is the attribute \@name value.
> d) IField f = IBatchProperty.getFiled();
> *Test case*:
> EXECUTE:
> 1. Import project jbosstools-javaee/batch/itests/org.jboss.tools.batch.core.itest/projects/BatchTestProject
> 2. Open file /src/META-INF/batch-jobs/job-openon-1.xml in Batch Job Configuration Editor and switch to tab "Source"
> 3. Press Ctrl and click mouse to "batchlet1" in batchlet node
> ASSERT:
> Java Class "batch.MyBatchlet" opened in Java Editor (1. of Description)
> 4. Press Ctrl and click mouse to "myBatchletStep2" in node "<step id="myBatchletStep1" next="myBatchletStep2">"
> ASSERT:
> Node "<step id="myBatchletStep2">" selected in Batch Job Configuration Editor (2. of Description)
> 5. Same for attributes "to" and "restart" (3. and 4. of Description)
> 6. Press Ctrl and click mouse to "worktime" in node "<property name="worktime" value="#{jobProperties[%aaa%]}"/>"
> ASSERT:
> Java Class "batch.MyBatchlet" opened in Java Editor and Java Field "time" selected. (5. of Description)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-19637) Runtime download not working from New Server dialog
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19637?page=com.atlassian.jira.plugi... ]
Martin Malina updated JBIDE-19637:
----------------------------------
Fix Version/s: 4.3.0.Beta1
(was: 4.3.0.Alpha2)
> Runtime download not working from New Server dialog
> ---------------------------------------------------
>
> Key: JBIDE-19637
> URL: https://issues.jboss.org/browse/JBIDE-19637
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.3.0.Alpha2
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.3.0.Beta1
>
>
> When you go through Servers view -> New Server -> EAP 6.1 -> New Runtime and then click "Download and install runtime...", it won't do anything.
> If you go through Preferences -> Server -> Runtime Environments -> Add -> EAP 6.1+ and then click the Download button, it will work.
> This issue applies to both JBDS 8.1.0.GA and JBoss Tools 4.3.0.Alpha2 testing build, but I doubt we will be able to fix this for 4.2.x.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-19637) Runtime download not working from New Server dialog
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19637?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-19637:
---------------------------------------
I just tried as you suggested and it won't help.
One thing I'd like to note though: When I tried this with Pavol on linux the other day, I saw that it took a second before the link was clickable - it waited for the background job to finish if I understand it correctly.
In my case, I can't see any such thing. When I go through Preferences, it seems to work immediately. If I go through Servers, it will still look like a link (blue, underlined), but clicking it does nothing.
There is nothing in the workspace log, but perhaps I could try debug mode of Eclipse and then maybe your code will log something? Let me know.
> Runtime download not working from New Server dialog
> ---------------------------------------------------
>
> Key: JBIDE-19637
> URL: https://issues.jboss.org/browse/JBIDE-19637
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.3.0.Alpha2
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.3.0.Beta1
>
>
> When you go through Servers view -> New Server -> EAP 6.1 -> New Runtime and then click "Download and install runtime...", it won't do anything.
> If you go through Preferences -> Server -> Runtime Environments -> Add -> EAP 6.1+ and then click the Download button, it will work.
> This issue applies to both JBDS 8.1.0.GA and JBoss Tools 4.3.0.Alpha2 testing build, but I doubt we will be able to fix this for 4.2.x.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-19539) Create and use Mars M6 target-platform
by Rastislav Wagner (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19539?page=com.atlassian.jira.plugi... ]
Rastislav Wagner closed JBIDE-19539.
------------------------------------
verified in JBDS9.0.0.Alpha2-v20150420-1747-B24
> Create and use Mars M6 target-platform
> --------------------------------------
>
> Key: JBIDE-19539
> URL: https://issues.jboss.org/browse/JBIDE-19539
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: target-platform
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Priority: Critical
> Fix For: 4.3.0.Alpha2
>
>
> Mars M6 was released and contains interesting changes (in Platform UI), important version updates (EGit 4.0 and TM 4.0).
> We need to start using it ASAP to leverage new functionalities and adapt to the most important changes.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBDS-3345) Errors when starting FSW 6.0.0.GA from JBDS 8.0.2.GA with JDK 1.8
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBDS-3345?page=com.atlassian.jira.plugin.... ]
Andrej Podhradsky edited comment on JBDS-3345 at 4/23/15 4:14 AM:
------------------------------------------------------------------
Note that the above script works perfectly only if we add the following to the top of the script (on unix-based system)
{code}
export PATH=/opt/java/jdk1.7.0_75/bin:$PATH
{code}
It seems that the server somewhere calls {{java ...}} so the JDK is taken from {{PATH}}.
So, my question is: Should JBDS set the PATH with the appropriate JDK for the whole execution?
was (Author: apodhrad):
Note that the above script works perfectly only if we add the following to the top of the script (on unix-based system)
{code}
export PATH=/opt/java/jdk1.7.0_75/bin:$PATH
{code}
It seems that the server somewhere calls [[java ...]] so the JDK is taken from [[PATH]].
So, my question is: Should JBDS set the PATH with the appropriate JDK for the whole execution?
> Errors when starting FSW 6.0.0.GA from JBDS 8.0.2.GA with JDK 1.8
> -----------------------------------------------------------------
>
> Key: JBDS-3345
> URL: https://issues.jboss.org/browse/JBDS-3345
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: server
> Affects Versions: 8.0.2.GA
> Environment: Fedora 21 x86_64
> JBDS 8.0.2.GA with Oracle JDK 1.8.0_25 and Oracle JDK 1.7.0_71
> Reporter: Andrej Podhradsky
> Priority: Critical
> Attachments: compiler.png, console.png, errors.txt, error_log.txt, installed_jre.png, runtime_jre.png, server.log
>
>
> FSW 6.0.0.GA supports java 6 and 7, so if we want to run this server on JBDS 8 with jdk 8 we need to add another jdk to the JBDS, e.g. jdk 7. But this doesn't work, see errors in the attached file.
> Moreover, we are not able to stop the server from IDE, the process is still alive and we have to kill it manually.
> Note that this happens only when we install JBDS 8.0.2 with jdk 8, if we install it with jdk 7 the server works fine.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years