December 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-21162) cannot decide to only save username

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21162?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-21162. --------------------------------- Verified in jboss-devstudio-9.1.0.Beta1-v20151212-0638-B189-installer-standalone.jar > cannot decide to only save username > ----------------------------------- > > Key: JBIDE-21162 > URL: https://issues.jboss.org/browse/JBIDE-21162 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > with the new credentials I seem to be *forced* to store my password for things like the CDK server adapter. > I should be able to use credentials that just ask me when it is needed and not persist across workspace sessions. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21299) EL Knowledge Base Problem with PrimeFaces functions

by Andrei Ivanov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21299?page=com.atlassian.jira.plugi... ] Andrei Ivanov commented on JBIDE-21299: --------------------------------------- Thank you :) I guess I'll open one too for unrecognized methods on enums > EL Knowledge Base Problem with PrimeFaces functions > --------------------------------------------------- > > Key: JBIDE-21299 > URL: https://issues.jboss.org/browse/JBIDE-21299 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsf > Affects Versions: 4.3.0.Final > Environment: Eclipse Mars.1 (4.5.1), Primefaces 5.x > Reporter: Andrei Ivanov > Assignee: Viacheslav Kabanovich > Priority: Minor > Fix For: 4.3.1.Beta2, 4.4.0.Alpha1 > > > The PrimeFaces functions are not recognized: > {noformat} > "ifAnyGranted" cannot be resolved > "ifGranted" cannot be resolved > "remoteUser" cannot be resolved > {noformat} > These are defined in {{org.primefaces.util.SecurityUtils}} and {{primefaces-5.3.jar/META-INF/primefaces-p.taglib.xml}}. > {code:xml} > <html xmlns="http://www.w3.org/1999/xhtml" > xmlns:ui="http://xmlns.jcp.org/jsf/facelets" > xmlns:h="http://xmlns.jcp.org/jsf/html" > xmlns:f="http://xmlns.jcp.org/jsf/core" > xmlns:c="http://xmlns.jcp.org/jsp/jstl/core" > xmlns:p="http://primefaces.org/ui"> > #{p:ifAnyGranted('ROLE_USER, ROLE_ADMIN')} > #{p:ifGranted('ROLE_ADMIN')} > #{p:remoteUser()} > </html> > {code} > Similar to JBIDE-12317 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21170) Virtualbox could not be found by CDK adapter

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21170?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-21170: --------------------------------------- Thanks for the sum up. For linux and mac at least, couldn't we have a predefined PATH that we use? Of course it's not 100% fool proof, but that should work for 99.9% of users. The tricky part here is if they have vagrant installed as part of home brew or macports - I'm not sure what home brew uses, but macports use /opt/local/bin/ which is not even there if you don't have it installed. But on the other hand, it shouldn't be a problem to include a non-existent path. > Virtualbox could not be found by CDK adapter > -------------------------------------------- > > Key: JBIDE-21170 > URL: https://issues.jboss.org/browse/JBIDE-21170 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Martin Malina > Assignee: Rob Stryker > > After I set up a CDK server adapter and fixed the wrong path to vagrant in the launch config, I then started the server adapter and got this: > Server CDK Server Adapter at localhost failed to start. > Console: > {code} > The provider 'virtualbox' that was requested to back the machine > 'default' is reporting that it isn't usable on this system. The > reason is shown below: > Vagrant could not detect VirtualBox! Make sure VirtualBox is properly installed. > Vagrant uses the `VBoxManage` binary that ships with VirtualBox, and requires > this to be available on the PATH. If VirtualBox is installed, please find the > `VBoxManage` binary and add it to the PATH environmental variable. > {code} > Along with this, there was an Unhandled event loop exception in the error view: > {code} > org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.NullPointerException) > at org.eclipse.swt.SWT.error(SWT.java:4491) > at org.eclipse.swt.SWT.error(SWT.java:4406) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:138) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4024) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3700) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018) > 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:139) > 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:520) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608) > at org.eclipse.equinox.launcher.Main.run(Main.java:1515) > Caused by: java.lang.NullPointerException > at org.jboss.tools.central.editors.GettingStartedHtmlPage.updateEarlyAccess(GettingStartedHtmlPage.java:359) > at org.jboss.tools.central.editors.GettingStartedHtmlPage.access$14(GettingStartedHtmlPage.java:342) > at org.jboss.tools.central.editors.GettingStartedHtmlPage$6$1.run(GettingStartedHtmlPage.java:327) > at org.eclipse.ui.internal.UILockListener.doPendingWork(UILockListener.java:162) > at org.eclipse.ui.internal.UISynchronizer$3.run(UISynchronizer.java:154) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) > ... 23 more > {code} > In the command line, VBoxManage is accessible and it is located in /usr/local/bin/ and on my PATH. > Max suggested I could try to start Eclipse from command line instead of double-clicking in Finder (which is the normal way to do it on Mac) and that helped. > So for some reason when you start Eclipse using Eclipse.app from Finder, the PATH is incorrect. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21299) EL Knowledge Base Problem with PrimeFaces functions

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21299?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-21299: ----------------------------------- Fix Version/s: 4.3.1.Beta2 4.4.0.Alpha1 (was: 4.4.x) > EL Knowledge Base Problem with PrimeFaces functions > --------------------------------------------------- > > Key: JBIDE-21299 > URL: https://issues.jboss.org/browse/JBIDE-21299 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsf > Affects Versions: 4.3.0.Final > Environment: Eclipse Mars.1 (4.5.1), Primefaces 5.x > Reporter: Andrei Ivanov > Assignee: Viacheslav Kabanovich > Priority: Minor > Fix For: 4.3.1.Beta2, 4.4.0.Alpha1 > > > The PrimeFaces functions are not recognized: > {noformat} > "ifAnyGranted" cannot be resolved > "ifGranted" cannot be resolved > "remoteUser" cannot be resolved > {noformat} > These are defined in {{org.primefaces.util.SecurityUtils}} and {{primefaces-5.3.jar/META-INF/primefaces-p.taglib.xml}}. > {code:xml} > <html xmlns="http://www.w3.org/1999/xhtml" > xmlns:ui="http://xmlns.jcp.org/jsf/facelets" > xmlns:h="http://xmlns.jcp.org/jsf/html" > xmlns:f="http://xmlns.jcp.org/jsf/core" > xmlns:c="http://xmlns.jcp.org/jsp/jstl/core" > xmlns:p="http://primefaces.org/ui"> > #{p:ifAnyGranted('ROLE_USER, ROLE_ADMIN')} > #{p:ifGranted('ROLE_ADMIN')} > #{p:remoteUser()} > </html> > {code} > Similar to JBIDE-12317 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21299) EL Knowledge Base Problem with PrimeFaces functions

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21299?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-21299: ----------------------------------------------- Pull request is sent. I will open a separate issue for not providing functions in content assist after the first ':' in the case {code} #{p: #{p:f} {code} > EL Knowledge Base Problem with PrimeFaces functions > --------------------------------------------------- > > Key: JBIDE-21299 > URL: https://issues.jboss.org/browse/JBIDE-21299 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsf > Affects Versions: 4.3.0.Final > Environment: Eclipse Mars.1 (4.5.1), Primefaces 5.x > Reporter: Andrei Ivanov > Assignee: Viacheslav Kabanovich > Priority: Minor > Fix For: 4.4.x > > > The PrimeFaces functions are not recognized: > {noformat} > "ifAnyGranted" cannot be resolved > "ifGranted" cannot be resolved > "remoteUser" cannot be resolved > {noformat} > These are defined in {{org.primefaces.util.SecurityUtils}} and {{primefaces-5.3.jar/META-INF/primefaces-p.taglib.xml}}. > {code:xml} > <html xmlns="http://www.w3.org/1999/xhtml" > xmlns:ui="http://xmlns.jcp.org/jsf/facelets" > xmlns:h="http://xmlns.jcp.org/jsf/html" > xmlns:f="http://xmlns.jcp.org/jsf/core" > xmlns:c="http://xmlns.jcp.org/jsp/jstl/core" > xmlns:p="http://primefaces.org/ui"> > #{p:ifAnyGranted('ROLE_USER, ROLE_ADMIN')} > #{p:ifGranted('ROLE_ADMIN')} > #{p:remoteUser()} > </html> > {code} > Similar to JBIDE-12317 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21320) Cannot see Wildfly 9.0.2 server plugin in Eclipse Mars

by Gopinadha Swamy Upadhyayula (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21320?page=com.atlassian.jira.plugi... ] Gopinadha Swamy Upadhyayula commented on JBIDE-21320: ----------------------------------------------------- Hi Fred, I have uninstalled(deleted) the eclipse mars along with wildfly & reinstalled them both again. And it started working. I am now able to see the wildfly server when trying to add a server. The only one change i did was pointing to the jre(C:\Program Files\Java\jre1.8.0_66) instead of jdk(C:\Program Files\Java\jdk1.8.0_25) folder while trying to install Jboss tools. Does that make any difference? Thanks, Gopi > Cannot see Wildfly 9.0.2 server plugin in Eclipse Mars > ------------------------------------------------------ > > Key: JBIDE-21320 > URL: https://issues.jboss.org/browse/JBIDE-21320 > Project: Tools (JBoss Tools) > Issue Type: Bug > Affects Versions: 4.3.0.Final > Environment: Windows 8 (64 bis OS), Wildfly 9.0.2 Final, JBoss Tools 4.3.0 Final, JDK 1.8.0_66 > Reporter: Gopinadha Swamy Upadhyayula > > I have Eclipse Mars pointing to jdk 1.8.0_66 in Windows 8 (64 bit OS). I have downloaded Wildfly 9.0.2 Final. When trying to download JBoss Tools 4.3.0 Final (from eclipse market place within IDE by searching), i am getting the below error. I continued with the installation multiple times. But, when i try to add the server, i cannot see it listed. I uninstalled & tried to install it again. The issue remains the same. Is there a bug? If so, is there a fix to it? > Warning: You are installing software that contains unsigned content. The authenticity or validity of this software cannot be established. Do you want to continue with the installation? > C:\Users\vaas\.p2\pool\plugins\minimal-json_0.9.2.jar > C:\Users\vaas\.p2\pool\plugins\minimatch.java_1.0.0.jar > C:\Users\vaas\.p2\pool\plugins\org.apache.aries.spifly.dynamic.bundle_1.0.2.jar > C:\Users\vaas\.p2\pool\plugins\org.apache.aries.util_1.1.1.jar > C:\Users\vaas\.p2\pool\plugins\org.eclipse.e4.ui.importer_0.1.0.v20150703-1722.jar > C:\Users\vaas\.p2\pool\plugins\org.eclipse.e4.ui.importer.java_0.1.0.v20150701-1130.jar > C:\Users\vaas\.p2\pool\plugins\org.eclipse.e4.ui.importer.pde_0.1.0.v20150703-1722.jar > C:\Users\vaas\.p2\pool\plugins\org.eclipse.wst.jsdt.ui.importer_0.0.1.v201503301926.jar > C:\Users\vaas\.p2\pool\plugins\org.hibernate.eclipse_5.0.0.Final-v20150924-2221-B39 > C:\Users\vaas\.p2\pool\plugins\org.hibernate.eclipse.console_5.0.0.Final-v20150924-2221-B39 > C:\Users\vaas\.p2\pool\features\org.hibernate.eclipse.feature_5.0.0.Final-v20150924-2221-B39 > C:\Users\vaas\.p2\pool\plugins\org.hibernate.eclipse.help_5.0.0.Final-v20150924-2221-B39 > C:\Users\vaas\.p2\pool\plugins\org.hibernate.eclipse.jdt.ui_5.0.0.Final-v20150924-2221-B39.jar > C:\Users\vaas\.p2\pool\plugins\org.hibernate.eclipse.mapper_5.0.0.Final-v20150924-2221-B39 > C:\Users\vaas\.p2\pool\plugins\org.jboss.ide.eclipse.archives.core_3.6.0.Final-v20150924-2222-B46 > C:\Users\vaas\.p2\pool\features\org.jboss.ide.eclipse.archives.feature_3.6.0.Final-v20150924-2222-B46 > C:\Users\vaas\.p2\pool\plugins\org.jboss.ide.eclipse.archives.jdt.integration_3.6.0.Final-v20150924-2222-B46.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.ide.eclipse.archives.ui_3.6.0.Final-v20150924-2222-B46.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.ide.eclipse.archives.webtools_3.1.0.Final-v20150924-2222-B46.jar > C:\Users\vaas\.p2\pool\features\org.jboss.ide.eclipse.as.archives.integration.feature_3.1.0.Final-v20150924-2222-B46 > C:\Users\vaas\.p2\pool\plugins\org.jboss.ide.eclipse.as.classpath.core_3.1.0.Final-v20150924-2222-B46.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.ide.eclipse.as.classpath.ui_3.1.0.Final-v20150924-2222-B46.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.ide.eclipse.as.core_3.1.0.Final-v20150924-2222-B46.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.ide.eclipse.as.dmr_3.1.0.Final-v20150924-2222-B46.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.ide.eclipse.as.doc.user_3.1.0.Final-v20150924-2222-B46.jar > C:\Users\vaas\.p2\pool\features\org.jboss.ide.eclipse.as.feature_3.1.0.Final-v20150924-2222-B46 > C:\Users\vaas\.p2\pool\plugins\org.jboss.ide.eclipse.as.jmx.integration_3.1.0.Final-v20150924-2222-B46.jar > C:\Users\vaas\.p2\pool\features\org.jboss.ide.eclipse.as.jmx.integration.feature_3.1.0.Final-v20150924-2222-B46 > C:\Users\vaas\.p2\pool\plugins\org.jboss.ide.eclipse.as.management.as7_3.1.0.Final-v20150924-2222-B46.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.ide.eclipse.as.management.core_3.1.0.Final-v20150924-2222-B46.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.ide.eclipse.as.management.wildfly9_3.1.0.Final-v20150924-2222-B46.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.ide.eclipse.as.rse.core_3.1.0.Final-v20150924-2222-B46.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.ide.eclipse.as.rse.ui_3.1.0.Final-v20150924-2222-B46.jar > C:\Users\vaas\.p2\pool\features\org.jboss.ide.eclipse.as.server.rse.integration.feature_3.1.0.Final-v20150924-2222-B46 > C:\Users\vaas\.p2\pool\features\org.jboss.ide.eclipse.as.serverAdapter.wtp.feature_3.1.0.Final-v20150924-2222-B46 > C:\Users\vaas\.p2\pool\plugins\org.jboss.ide.eclipse.as.ui_3.1.0.Final-v20150924-2222-B46.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.ide.eclipse.as.ui.mbeans_3.1.0.Final-v20150924-2222-B46.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.ide.eclipse.as.wtp.core_3.1.0.Final-v20150924-2222-B46.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.ide.eclipse.as.wtp.ui_3.1.0.Final-v20150924-2222-B46.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.ide.eclipse.freemarker_1.5.0.Final-v20150924-2221-B20.jar > C:\Users\vaas\.p2\pool\features\org.jboss.ide.eclipse.freemarker.feature_1.5.0.Final-v20150924-2221-B20 > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.aesh.core_2.0.0.Final-v20150924-2221-B39.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.aesh.runtime_2.0.0.Final-v20150924-2221-B39.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.aesh.ui_2.0.0.Final-v20150924-2221-B39.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.archives.scanner_3.6.0.Final-v20150924-2222-B46.jar > C:\Users\vaas\.p2\pool\features\org.jboss.tools.archives.scanner.feature_3.6.0.Final-v20150924-2222-B46 > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.as.catalog_3.1.0.Final-v20150924-2222-B46.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.as.runtimes.integration_3.1.0.Final-v20150924-2222-B46.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.batch.core_1.7.0.Final-v20150925-0003-B31.jar > C:\Users\vaas\.p2\pool\features\org.jboss.tools.batch.feature_1.7.0.Final-v20150925-0003-B31 > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.batch.ui_1.7.0.Final-v20150925-0003-B31.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.browsersim.browser_3.7.0.Final-v20150924-2250-B40.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.browsersim.debugger_3.7.0.Final-v20150924-2250-B40.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.browsersim.eclipse_3.7.0.Final-v20150924-2250-B40.jar > C:\Users\vaas\.p2\pool\features\org.jboss.tools.browsersim.feature_3.7.0.Final-v20150924-2250-B40 > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.browsersim.javafx.mock_3.7.0.Final-v20150924-2250-B40.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.browsersim.ui_3.7.0.Final-v20150924-2250-B40.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.cdi.core_1.7.0.Final-v20150925-0003-B31.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.cdi.deltaspike.core_1.7.0.Final-v20150925-0003-B31.jar > C:\Users\vaas\.p2\pool\features\org.jboss.tools.cdi.deltaspike.feature_1.7.0.Final-v20150925-0003-B31 > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.cdi.extension.core_1.7.0.Final-v20150925-0003-B31.jar > C:\Users\vaas\.p2\pool\features\org.jboss.tools.cdi.feature_1.7.0.Final-v20150925-0003-B31 > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.cdi.seam.config.core_1.7.0.Final-v20150925-0003-B31.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.cdi.seam.config.ui_1.7.0.Final-v20150925-0003-B31.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.cdi.seam.core_1.7.0.Final-v20150925-0003-B31.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.cdi.seam.faces.core_1.7.0.Final-v20150925-0003-B31.jar > C:\Users\vaas\.p2\pool\features\org.jboss.tools.cdi.seam.feature_1.7.0.Final-v20150925-0003-B31 > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.cdi.seam.solder.core_1.7.0.Final-v20150925-0003-B31.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.cdi.seam.text.ext_1.7.0.Final-v20150925-0003-B31.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.cdi.text.ext_1.7.0.Final-v20150925-0003-B31.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.cdi.ui_1.7.0.Final-v20150925-0003-B31.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.cdi.xml_1.7.0.Final-v20150925-0003-B31.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.cdi.xml.ui_1.7.0.Final-v20150925-0003-B31.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.central_2.0.0.Final-v20151001-1531-B45 > C:\Users\vaas\.p2\pool\features\org.jboss.tools.central.easymport.feature_0.1.0.Final-v20151001-1531-B45 > C:\Users\vaas\.p2\pool\features\org.jboss.tools.central.feature_2.0.0.Final-v20151001-1531-B45 > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.common_3.7.0.Final-v20150924-2213-B38.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.common.core_3.7.0.Final-v20150924-2213-B38.jar > C:\Users\vaas\.p2\pool\features\org.jboss.tools.common.core.feature_3.7.0.Final-v20150924-2213-B38 > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.common.el.core_3.7.0.Final-v20150924-2213-B38.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.common.el.ui_3.7.0.Final-v20150924-2213-B38.jar > C:\Users\vaas\.p2\pool\features\org.jboss.tools.common.feature_3.7.0.Final-v20150924-2213-B38 > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.common.gef_3.7.0.Final-v20150924-2213-B38 > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.common.jdt_3.7.0.Final-v20150924-2213-B38.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.common.jdt.debug_3.7.0.Final-v20150924-2213-B38.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.common.jdt.debug.ui_3.7.0.Final-v20150924-2213-B38.jar > C:\Users\vaas\.p2\pool\features\org.jboss.tools.common.jdt.feature_3.7.0.Final-v20150924-2213-B38 > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.common.jdt.ui_3.7.0.Final-v20150924-2213-B38.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.common.model_3.7.0.Final-v20150924-2213-B38 > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.common.model.ui_3.7.0.Final-v20150924-2213-B38 > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.common.model.ui.capabilities_3.7.0.Final-v20150924-2213-B38.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.common.projecttemplates_3.7.0.Final-v20150924-2213-B38 > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.common.resref.core_3.7.0.Final-v20150924-2213-B38.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.common.resref.ui_3.7.0.Final-v20150924-2213-B38.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.common.text.ext_3.7.0.Final-v20150924-2213-B38.jar > C:\Users\vaas\.p2\pool\features\org.jboss.tools.common.text.ext.feature_3.7.0.Final-v20150924-2213-B38 > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.common.text.xml_3.7.0.Final-v20150924-2213-B38.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.common.ui_3.7.0.Final-v20150924-2213-B38.jar > C:\Users\vaas\.p2\pool\features\org.jboss.tools.common.ui.feature_3.7.0.Final-v20150924-2213-B38 > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.common.validation_3.7.0.Final-v20150924-2213-B38.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.common.verification_3.7.0.Final-v20150924-2213-B38.jar > C:\Users\vaas\.p2\pool\features\org.jboss.tools.common.verification.feature_3.7.0.Final-v20150924-2213-B38 > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.common.verification.ui_3.7.0.Final-v20150924-2213-B38.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.community.central_2.0.0.Final-v20151001-1531-B45.jar > C:\Users\vaas\.p2\pool\features\org.jboss.tools.community.central.feature_2.0.0.Final-v20151001-1531-B45 > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.community.project.examples_3.0.0.Final-v20151001-1531-B45.jar > C:\Users\vaas\.p2\pool\features\org.jboss.tools.community.project.examples.feature_3.0.0.Final-v20151001-1531-B45 > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.discovery.core_1.0.0.Final-v20151001-1531-B45.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.forge.core_2.0.0.Final-v20150924-2221-B39.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.forge.core.ext_2.0.0.Final-v20150924-2221-B39.jar > C:\Users\vaas\.p2\pool\features\org.jboss.tools.forge.ext.feature_2.0.0.Final-v20150924-2221-B39 > C:\Users\vaas\.p2\pool\features\org.jboss.tools.forge.feature_2.0.0.Final-v20150924-2221-B39 > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.forge.m2e_2.0.0.Final-v20150924-2221-B39.jar > C:\Users\vaas\.p2\pool\features\org.jboss.tools.forge.m2e.feature_2.0.0.Final-v20150924-2221-B39 > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.forge.runtime_2.0.0.Final-v20150924-2221-B39 > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.forge.runtime.ext_2.0.0.Final-v20150924-2221-B39 > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.forge.ui_2.0.0.Final-v20150924-2221-B39.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.forge.ui.ext_2.0.0.Final-v20150924-2221-B39.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.forge.ui.notifications_2.0.0.Final-v20150924-2221-B39.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.foundation.checkup_1.2.0.Final-v20150924-2213-B38.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.foundation.core_1.2.0.Final-v20150924-2213-B38.jar > C:\Users\vaas\.p2\pool\features\org.jboss.tools.foundation.feature_1.2.0.Final-v20150924-2213-B38 > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.foundation.help.ui_1.2.0.Final-v20150924-2213-B38.jar > C:\Users\vaas\.p2\pool\features\org.jboss.tools.foundation.security.linux.feature_1.2.0.Final-v20150924-2213-B38 > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.foundation.ui_1.2.0.Final-v20150924-2213-B38.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.hibernate.jpt.core_5.0.0.Final-v20150924-2221-B39.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.hibernate.jpt.ui_5.0.0.Final-v20150924-2221-B39.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.hibernate.libs.antlr.v_2_7_7_5.0.0.Final-v20150924-2221-B39.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.hibernate.libs.bsh.v_2_0_b4_5.0.0.Final-v20150924-2221-B39.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.hibernate.libs.dom4j.v_1_6_1_5.0.0.Final-v20150924-2221-B39.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.hibernate.libs.freemarker.v_2_3_8_5.0.0.Final-v20150924-2221-B39.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.hibernate.libs.jtidy.v_r8-20060801_5.0.0.Final-v20150924-2221-B39.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.hibernate.runtime.common_5.0.0.Final-v20150924-2221-B39.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.hibernate.runtime.spi_5.0.0.Final-v20150924-2221-B39.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.hibernate.runtime.v_3_5_5.0.0.Final-v20150924-2221-B39.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.hibernate.runtime.v_3_6_5.0.0.Final-v20150924-2221-B39.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.hibernate.runtime.v_4_0_5.0.0.Final-v20150924-2221-B39 > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.hibernate.runtime.v_4_3_5.0.0.Final-v20150924-2221-B39.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.hibernate.ui_5.0.0.Final-v20150924-2221-B39 > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.hibernate.xml_5.0.0.Final-v20150924-2221-B39.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.hibernate.xml.ui_5.0.0.Final-v20150924-2221-B39.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.jmx.core_1.7.0.Final-v20150924-2222-B46.jar > C:\Users\vaas\.p2\pool\features\org.jboss.tools.jmx.feature_1.7.0.Final-v20150924-2222-B46 > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.jmx.jvmmonitor.core_1.7.0.Final-v20150924-2222-B46.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.jmx.jvmmonitor.tools_1.7.0.Final-v20150924-2222-B46.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.jmx.jvmmonitor.ui_1.7.0.Final-v20150924-2222-B46.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.jmx.local_1.7.0.Final-v20150924-2222-B46.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.jmx.ui_1.7.0.Final-v20150924-2222-B46.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.jsf_3.7.0.Final-v20150925-0003-B31.jar > C:\Users\vaas\.p2\pool\features\org.jboss.tools.jsf.feature_3.7.0.Final-v20150925-0003-B31 > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.jsf.text.ext_3.7.0.Final-v20150925-0003-B31.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.jsf.text.ext.facelets_3.7.0.Final-v20150925-0003-B31.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.jsf.text.ext.richfaces_3.7.0.Final-v20150925-0003-B31.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.jsf.ui_3.7.0.Final-v20150925-0003-B31.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.jsf.verification_3.7.0.Final-v20150925-0003-B31.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.jsf.vpe.ajax4jsf_3.7.0.Final-v20150925-0003-B31 > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.jsf.vpe.facelets_3.7.0.Final-v20150925-0003-B31 > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.jsf.vpe.jbpm_3.7.0.Final-v20150925-0003-B31.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.jsf.vpe.jsf_3.7.0.Final-v20150925-0003-B31.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.jsf.vpe.jstl_3.7.0.Final-v20150925-0003-B31.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.jsf.vpe.myfaces_3.7.0.Final-v20150925-0003-B31 > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.jsf.vpe.richfaces_3.7.0.Final-v20150925-0003-B31 > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.jst.angularjs_3.7.0.Final-v20150924-2233-B43.jar > C:\Users\vaas\.p2\pool\features\org.jboss.tools.jst.angularjs.feature_3.7.0.Final-v20150924-2233-B43 > C:\Users\vaas\.p2\pool\features\org.jboss.tools.jst.feature_3.7.0.Final-v20150924-2233-B43 > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.jst.jsdt_3.7.0.Final-v20150924-2233-B43.jar > C:\Users\vaas\.p2\pool\features\org.jboss.tools.jst.jsdt.feature_3.7.0.Final-v20150924-2233-B43 > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.jst.web_3.7.0.Final-v20150924-2233-B43.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.jst.web.kb_3.7.0.Final-v20150924-2233-B43 > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.jst.web.ui_3.7.0.Final-v20150924-2233-B43.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.livereload.core_1.3.0.Final-v20150924-2332-B40.jar > C:\Users\vaas\.p2\pool\features\org.jboss.tools.livereload.feature_1.3.0.Final-v20150924-2332-B40 > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.livereload.ui_1.3.0.Final-v20150924-2332-B40.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.maven.apt.core_1.1.1.201411262015.jar > C:\Users\vaas\.p2\pool\features\org.jboss.tools.maven.apt.feature_1.1.1.201411262015 > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.maven.apt.ui_1.1.1.201411262015.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.maven.cdi_1.7.0.Final-v20151001-1531-B45.jar > C:\Users\vaas\.p2\pool\features\org.jboss.tools.maven.cdi.feature_1.7.0.Final-v20151001-1531-B45 > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.maven.conversion.ui_1.7.0.Final-v20151001-1531-B45.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.maven.core_1.7.0.Final-v20151001-1531-B45.jar > C:\Users\vaas\.p2\pool\features\org.jboss.tools.maven.feature_1.7.0.Final-v20151001-1531-B45 > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.maven.hibernate_1.7.0.Final-v20151001-1531-B45.jar > C:\Users\vaas\.p2\pool\features\org.jboss.tools.maven.hibernate.feature_1.7.0.Final-v20151001-1531-B45 > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.maven.jbosspackaging_1.7.0.Final-v20151001-1531-B45.jar > C:\Users\vaas\.p2\pool\features\org.jboss.tools.maven.jbosspackaging.feature_1.7.0.Final-v20151001-1531-B45 > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.maven.jdt_1.7.0.Final-v20151001-1531-B45.jar > C:\Users\vaas\.p2\pool\features\org.jboss.tools.maven.jdt.feature_1.7.0.Final-v20151001-1531-B45 > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.maven.project.examples_3.0.0.Final-v20151001-1531-B45.jar > C:\Users\vaas\.p2\pool\features\org.jboss.tools.maven.project.examples.feature_3.0.0.Final-v20151001-1531-B45 > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.maven.sourcelookup.core_1.7.0.Final-v20151001-1531-B45.jar > C:\Users\vaas\.p2\pool\features\org.jboss.tools.maven.sourcelookup.feature_1.7.0.Final-v20151001-1531-B45 > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.maven.sourcelookup.ui_1.7.0.Final-v20151001-1531-B45.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.maven.ui_1.7.0.Final-v20151001-1531-B45.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.openshift.common.core_3.0.0.Final-v20151002-2059-B50.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.openshift.common.ui_3.0.0.Final-v20151002-2059-B50.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.openshift.egit.core_3.0.0.Final-v20151002-2059-B50.jar > C:\Users\vaas\.p2\pool\features\org.jboss.tools.openshift.egit.integration.feature_3.0.0.Final-v20151002-2059-B50 > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.openshift.egit.ui_3.0.0.Final-v20151002-2059-B50.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.openshift.express.client_3.0.0.Final-v20151002-2059-B50.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.openshift.express.core_3.0.0.Final-v20151002-2059-B50.jar > C:\Users\vaas\.p2\pool\features\org.jboss.tools.openshift.express.feature_3.0.0.Final-v20151002-2059-B50 > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.openshift.express.ui_3.0.0.Final-v20151002-2059-B50.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.playground.easymport.jee_1.0.0.Final-v20150925-1225-B24.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.playground.easymport.maven_1.0.0.Final-v20150925-1225-B24.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.project.examples_3.0.0.Final-v20151001-1531-B45.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.project.examples.cheatsheet_3.0.0.Final-v20151001-1531-B45.jar > C:\Users\vaas\.p2\pool\features\org.jboss.tools.project.examples.feature_3.0.0.Final-v20151001-1531-B45 > C:\Users\vaas\.p2\pool\features\org.jboss.tools.richfaces.feature_3.7.0.Final-v20150925-0003-B31 > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.runtime.core_3.1.0.Final-v20150924-2213-B38.jar > C:\Users\vaas\.p2\pool\features\org.jboss.tools.runtime.core.feature_3.1.0.Final-v20150924-2213-B38 > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.runtime.seam.detector_3.7.0.Final-v20150925-0003-B31.jar > C:\Users\vaas\.p2\pool\features\org.jboss.tools.runtime.seam.detector.feature_3.7.0.Final-v20150925-0003-B31 > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.runtime.ui_3.1.0.Final-v20150924-2213-B38.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.seam.core_3.7.0.Final-v20150925-0003-B31.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.seam.pages.xml_3.7.0.Final-v20150925-0003-B31.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.seam.xml_3.7.0.Final-v20150925-0003-B31.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.stacks.core_1.2.0.Final-v20150924-2213-B38.jar > C:\Users\vaas\.p2\pool\features\org.jboss.tools.stacks.core.feature_1.2.0.Final-v20150924-2213-B38 > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.usage_2.1.0.Final-v20150924-2213-B38.jar > C:\Users\vaas\.p2\pool\features\org.jboss.tools.usage.feature_2.1.0.Final-v20150924-2213-B38 > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.vpe_3.7.0.Final-v20150924-2224-B45 > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.vpe.docbook_3.7.0.Final-v20150924-2224-B45 > C:\Users\vaas\.p2\pool\features\org.jboss.tools.vpe.feature_3.7.0.Final-v20150924-2224-B45 > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.vpe.html_3.7.0.Final-v20150924-2224-B45 > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.vpe.jsp_3.7.0.Final-v20150924-2224-B45 > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.vpe.preview_3.7.0.Final-v20150924-2224-B45.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.vpe.preview.core_3.7.0.Final-v20150924-2224-B45.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.vpe.preview.editor_3.7.0.Final-v20150924-2224-B45.jar > C:\Users\vaas\.p2\pool\features\org.jboss.tools.vpe.preview.feature_3.7.0.Final-v20150924-2224-B45 > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.vpe.resref_3.7.0.Final-v20150924-2224-B45.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.vpe.spring_3.7.0.Final-v20150924-2224-B45.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.vpe.ui.palette_3.7.0.Final-v20150924-2224-B45.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.vpe.xulrunner_3.7.0.Final-v20150924-2224-B45.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.websockets.core_1.8.0.Final-v20150924-2334-B31.jar > C:\Users\vaas\.p2\pool\features\org.jboss.tools.websockets.feature_1.8.0.Final-v20150924-2334-B31 > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.websockets.ui_1.8.0.Final-v20150924-2334-B31.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.ws.core_1.8.0.Final-v20150924-2334-B31.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.ws.creation.core_1.8.0.Final-v20150924-2334-B31.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.ws.creation.ui_1.8.0.Final-v20150924-2334-B31.jar > C:\Users\vaas\.p2\pool\features\org.jboss.tools.ws.feature_1.8.0.Final-v20150924-2334-B31 > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.ws.jaxrs.core_1.8.0.Final-v20150924-2334-B31.jar > C:\Users\vaas\.p2\pool\features\org.jboss.tools.ws.jaxrs.feature_1.8.0.Final-v20150924-2334-B31 > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.ws.jaxrs.ui_1.8.0.Final-v20150924-2334-B31.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.ws.ui_1.8.0.Final-v20150924-2334-B31.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.ws.wise.ui_1.8.0.Final-v20150924-2334-B31.jar > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.wtp.runtimes.tomcat_1.3.0.Final-v20150924-2222-B46.jar > C:\Users\vaas\.p2\pool\features\org.jboss.tools.wtp.runtimes.tomcat.feature_1.3.0.Final-v20150924-2222-B46 > C:\Users\vaas\.p2\pool\plugins\org.jboss.tools.xulrunner.initializer_3.7.0.Final-v20150924-2224-B45.jar > C:\Users\vaas\.p2\pool\plugins\org.mozilla.xpcom_1.9.2.16 > C:\Users\vaas\.p2\pool\plugins\org.sonatype.m2e.egit_0.14.0.201504071521.jar > C:\Users\vaas\.p2\pool\features\org.sonatype.m2e.egit.feature_0.14.0.201504071521 > C:\Users\vaas\.p2\pool\plugins\tern.core_1.0.0.201508302102.jar > C:\Users\vaas\.p2\pool\plugins\tern.eclipse_1.0.0.201508302102.jar > C:\Users\vaas\.p2\pool\plugins\tern.eclipse.ide.core_1.0.0.201508302102.jar > C:\Users\vaas\.p2\pool\plugins\tern.eclipse.ide.jsdt.core_1.0.0.201508302102.jar > C:\Users\vaas\.p2\pool\plugins\tern.eclipse.ide.jsdt.ui_1.0.0.201508302102.jar > C:\Users\vaas\.p2\pool\plugins\tern.eclipse.ide.server.nodejs.core_1.0.0.201508302102.jar > C:\Users\vaas\.p2\pool\plugins\tern.eclipse.ide.server.nodejs.embed.win32.win32.x86_64_1.0.0.201508302102 > C:\Users\vaas\.p2\pool\plugins\tern.eclipse.ide.server.nodejs.ui_1.0.0.201508302102.jar > C:\Users\vaas\.p2\pool\plugins\tern.eclipse.ide.tools.core_1.0.0.201508302102.jar > C:\Users\vaas\.p2\pool\plugins\tern.eclipse.ide.tools.ui_1.0.0.201508302102.jar > C:\Users\vaas\.p2\pool\plugins\tern.eclipse.ide.ui_1.0.0.201508302102.jar > C:\Users\vaas\.p2\pool\plugins\tern.server.nodejs_1.0.0.201508302102.jar > C:\Users\vaas\.p2\pool\plugins\ternjs_1.0.0.201508302102 > Thanks! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20761) Support editing Build Configuration parameters

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20761?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-20761: ----------------------------------------------- For editing properties, package org.jboss.tools.openshift.internal.ui.property has already property sources (e.g. BuildConfigPropertySource) that bind openshift model objects to property view. Any number of properties may be added, just since they operate on remote objects they have to be supported by com.openshift.restclient.model interface. > Support editing Build Configuration parameters > ---------------------------------------------- > > Key: JBIDE-20761 > URL: https://issues.jboss.org/browse/JBIDE-20761 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Assignee: Fred Bricon > Labels: new_and_noteworthy > Fix For: 4.3.1.Beta1 > > > As a developer I want to be able to update the git url used in my existing OpenShift application buildconfig to use a different repository than what the default template used so I can publish my own changes to OS > Pre-Req: > - An application is deployed on OpenShift, using git for its source repository > Goal: > - Modify the git source url used to build and redeploy the application > Build Config parameters should be editable from either the Properties view (but how exactly?) or another mechanism from OpenShift Explorer (TBD) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20761) Support editing Build Configuration parameters

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20761?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-20761: ----------------------------------------------- 2. Saved is not the editor content, but a handle by which editor input may be restored. Editor input in this case contains connection and resource, so saved may be data that can create (or request earlier created) connection and name of the resource. Yes, resource may be removed on server by that time, but the same may be told about any file on a local disk, if some Java file is open in Java editor, and Eclipse is closed, the file may be deleted before Eclipse is reopened and editor input will fail to restore the file - no much difference with a resource disappearing on server. 3. My concern is that the default editor is called if it is set for .json without a fallback for a case of failure of that unknown editor. We cannot be sure what editor a user may have set to be default for .json. That editor may be expecting some specific instance of editor input object and fail on what is provided. As it is, then json will not be opened at all, neither fancy nor plain text. However, if it is just temporal, till the expected contribution to jsdt, and that editor is going to be hardcoded to be opened, then no problem. > Support editing Build Configuration parameters > ---------------------------------------------- > > Key: JBIDE-20761 > URL: https://issues.jboss.org/browse/JBIDE-20761 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Assignee: Fred Bricon > Labels: new_and_noteworthy > Fix For: 4.3.1.Beta1 > > > As a developer I want to be able to update the git url used in my existing OpenShift application buildconfig to use a different repository than what the default template used so I can publish my own changes to OS > Pre-Req: > - An application is deployed on OpenShift, using git for its source repository > Goal: > - Modify the git source url used to build and redeploy the application > Build Config parameters should be editable from either the Properties view (but how exactly?) or another mechanism from OpenShift Explorer (TBD) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20761) Support editing Build Configuration parameters

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20761?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-20761: ------------------------------------- 1- was fixed 2- I don't feel the need to persist the editor state locally, as it might go stale (the source is on the server) upon workbench restart. 3- whatever JSON editor you have installed will be used to open the json payload. We're waiting for the Angelo's json editor to be contributed to JSDT, but you can test it with whatever editor you find on the marketplace right now: !http://content.screencast.com/users/fbricon/folders/Jing/media/47d0831e-8a0e-4f97-8c86-abb493f1dd5c/00000251.png|width=650! What I'd like to see next is a way to edit individual properties from the properties view directly, without going through using the text/json editor > Support editing Build Configuration parameters > ---------------------------------------------- > > Key: JBIDE-20761 > URL: https://issues.jboss.org/browse/JBIDE-20761 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Assignee: Fred Bricon > Labels: new_and_noteworthy > Fix For: 4.3.1.Beta1 > > > As a developer I want to be able to update the git url used in my existing OpenShift application buildconfig to use a different repository than what the default template used so I can publish my own changes to OS > Pre-Req: > - An application is deployed on OpenShift, using git for its source repository > Goal: > - Modify the git source url used to build and redeploy the application > Build Config parameters should be editable from either the Properties view (but how exactly?) or another mechanism from OpenShift Explorer (TBD) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20761) Support editing Build Configuration parameters

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20761?page=com.atlassian.jira.plugi... ] Fred Bricon edited comment on JBIDE-20761 at 12/14/15 7:01 PM: --------------------------------------------------------------- 1- was fixed 2- I don't feel the need to persist the editor state locally, as it might go stale (the source is on the server) upon workbench restart. 3- whatever JSON editor you have installed will be used to open the json payload. We're waiting for Angelo's json editor to be contributed to JSDT, but you can test it with whatever editor you find on the marketplace right now: !http://content.screencast.com/users/fbricon/folders/Jing/media/47d0831e-8a0e-4f97-8c86-abb493f1dd5c/00000251.png|width=650! What I'd like to see next is a way to edit individual properties from the properties view directly, without going through using the text/json editor was (Author: fbricon): 1- was fixed 2- I don't feel the need to persist the editor state locally, as it might go stale (the source is on the server) upon workbench restart. 3- whatever JSON editor you have installed will be used to open the json payload. We're waiting for the Angelo's json editor to be contributed to JSDT, but you can test it with whatever editor you find on the marketplace right now: !http://content.screencast.com/users/fbricon/folders/Jing/media/47d0831e-8a0e-4f97-8c86-abb493f1dd5c/00000251.png|width=650! What I'd like to see next is a way to edit individual properties from the properties view directly, without going through using the text/json editor > Support editing Build Configuration parameters > ---------------------------------------------- > > Key: JBIDE-20761 > URL: https://issues.jboss.org/browse/JBIDE-20761 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Assignee: Fred Bricon > Labels: new_and_noteworthy > Fix For: 4.3.1.Beta1 > > > As a developer I want to be able to update the git url used in my existing OpenShift application buildconfig to use a different repository than what the default template used so I can publish my own changes to OS > Pre-Req: > - An application is deployed on OpenShift, using git for its source repository > Goal: > - Modify the git source url used to build and redeploy the application > Build Config parameters should be editable from either the Properties view (but how exactly?) or another mechanism from OpenShift Explorer (TBD) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues December 2015