[JBoss JIRA] (JBIDE-18348) Add support for WildFly 9
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18348?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-18348:
----------------------------------------
Sprint: Sprint #1 April 2015
> Add support for WildFly 9
> -------------------------
>
> Key: JBIDE-18348
> URL: https://issues.jboss.org/browse/JBIDE-18348
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: runtime-detection, server
> Affects Versions: 4.2.0.CR1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.3.0.Alpha2
>
>
> Now that WildFly 9.0.0.Alpha1 is out, we need to make sure it works properly with JBT/JBDS.
> I played with it a little, tried to start/stop, deploy a project and so far I haven't seen any issue.
> Other than the one expected that is - when you add the server, you get a warning that the runtime version doesn't match - it detected 9, but 8 is expected. We need to deal with this somehow.
> Runtime detection doesn't work. It find the server (although with a strange Type of "WILDFLY-FULL"), but doesn't actually add it.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-3235) Missing properties view for servers elements
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-3235?page=com.atlassian.jira.plugin... ]
Max Rydahl Andersen updated JBIDE-3235:
---------------------------------------
Sprint: (was: Sprint #2 April 2015)
> Missing properties view for servers elements
> --------------------------------------------
>
> Key: JBIDE-3235
> URL: https://issues.jboss.org/browse/JBIDE-3235
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Reporter: Max Rydahl Andersen
> Assignee: Max Rydahl Andersen
> Priority: Minor
> Fix For: 3.3.x
>
>
> Before I could directly edit properties for ports in properties view.
> Now I need to right click and choose Change Value and get a non-standard edit in the tree.
> This I could probably live with if I could just double click the value and edit it like in properties view.
> Properties view was though also nice to give other details than just access to edit.
> i.e.. I could copy values to get the value of file names etc. I can't copy elements from the tree and get a textual representation.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-3235) Missing properties view for servers elements
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-3235?page=com.atlassian.jira.plugin... ]
Max Rydahl Andersen updated JBIDE-3235:
---------------------------------------
Sprint: Sprint #2 April 2015 (was: Sprint #1 April 2015)
> Missing properties view for servers elements
> --------------------------------------------
>
> Key: JBIDE-3235
> URL: https://issues.jboss.org/browse/JBIDE-3235
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Reporter: Max Rydahl Andersen
> Assignee: Max Rydahl Andersen
> Priority: Minor
> Fix For: 3.3.x
>
>
> Before I could directly edit properties for ports in properties view.
> Now I need to right click and choose Change Value and get a non-standard edit in the tree.
> This I could probably live with if I could just double click the value and edit it like in properties view.
> Properties view was though also nice to give other details than just access to edit.
> i.e.. I could copy values to get the value of file names etc. I can't copy elements from the tree and get a textual representation.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19585) Mixture of jetty 9 bundles versions in the TP
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19585?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-19585:
----------------------------------------
[~xcoulon] Any objection against this change?
> Mixture of jetty 9 bundles versions in the TP
> ---------------------------------------------
>
> Key: JBIDE-19585
> URL: https://issues.jboss.org/browse/JBIDE-19585
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform
> Affects Versions: 4.3.0.Alpha1
> Reporter: Ilya Buziuk
> Priority: Minor
>
> Basically, here is the list of jetty 9 bundles in the TP:
> 1. org.eclipse.jetty.http_9.2.9.v20150224.jar
> 2. org.eclipse.jetty.continuation_9.2.9.v20150224.jar
> 3. org.eclipse.jetty.http_9.2.9.v20150224.jar
> 4. org.eclipse.jetty.io_9.2.9.v20150224.jar
> 5. org.eclipse.jetty.proxy_9.2.5.v20141112.jar
> 6. org.eclipse.jetty.rewrite_9.2.5.v20141112.jar
> 7. org.eclipse.jetty.security_9.2.9.v20150224.jar
> 8. org.eclipse.jetty.server_9.2.9.v20150224.jar
> 9. org.eclipse.jetty.servlets_9.2.5.v20141112.jar
> 10. org.eclipse.jetty.util_9.2.9.v20150224.jar
> 11. org.eclipse.jetty.websocket.api_9.2.5.v20141112.jar (and other websocket stuff)
> The good news is that CordovaSim and BrowserSim seems to work fine against M6 TP. However, it would be really great to have a single version of bundles to avoid potential breakage.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19585) Mixture of jetty 9 bundles versions in the TP
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19585?page=com.atlassian.jira.plugi... ]
Ilya Buziuk commented on JBIDE-19585:
-------------------------------------
PR was sent - https://github.com/jbosstools/jbosstools-target-platforms/pull/141
There is a build failure for JBDS Unified (Aggregate) Target Platform & JBoss Tools Unified (Aggregate) Target Platform but I guess it's fine for now
> Mixture of jetty 9 bundles versions in the TP
> ---------------------------------------------
>
> Key: JBIDE-19585
> URL: https://issues.jboss.org/browse/JBIDE-19585
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform
> Affects Versions: 4.3.0.Alpha1
> Reporter: Ilya Buziuk
> Priority: Minor
>
> Basically, here is the list of jetty 9 bundles in the TP:
> 1. org.eclipse.jetty.http_9.2.9.v20150224.jar
> 2. org.eclipse.jetty.continuation_9.2.9.v20150224.jar
> 3. org.eclipse.jetty.http_9.2.9.v20150224.jar
> 4. org.eclipse.jetty.io_9.2.9.v20150224.jar
> 5. org.eclipse.jetty.proxy_9.2.5.v20141112.jar
> 6. org.eclipse.jetty.rewrite_9.2.5.v20141112.jar
> 7. org.eclipse.jetty.security_9.2.9.v20150224.jar
> 8. org.eclipse.jetty.server_9.2.9.v20150224.jar
> 9. org.eclipse.jetty.servlets_9.2.5.v20141112.jar
> 10. org.eclipse.jetty.util_9.2.9.v20150224.jar
> 11. org.eclipse.jetty.websocket.api_9.2.5.v20141112.jar (and other websocket stuff)
> The good news is that CordovaSim and BrowserSim seems to work fine against M6 TP. However, it would be really great to have a single version of bundles to avoid potential breakage.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-17591) org.jboss.tools.common.el.core.test fails on Max OS X Mavericks
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17591?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-17591:
----------------------------------------
Sprint: Sprint to Beta3 Release, Sprint #2 April 2015 (was: Sprint to Beta3 Release)
> org.jboss.tools.common.el.core.test fails on Max OS X Mavericks
> ---------------------------------------------------------------
>
> Key: JBIDE-17591
> URL: https://issues.jboss.org/browse/JBIDE-17591
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common/jst/core
> Affects Versions: 4.2.0.Beta2
> Environment: Mac OS X Mavericks
> Reporter: Denis Golovin
> Assignee: Daniel Azarov
> Fix For: 4.3.x
>
> Attachments: org.jboss.tools.common.el.core.test.CommonELAllTests2.txt
>
>
> {code}junit.framework.AssertionFailedError
> at junit.framework.Assert.fail(Assert.java:55)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.Assert.assertNotNull(Assert.java:256)
> at junit.framework.Assert.assertNotNull(Assert.java:248)
> at junit.framework.TestCase.assertNotNull(TestCase.java:417)
> at org.jboss.tools.common.el.core.test.resolver.TypeInfoCollectorTest.testTypeResolution(TypeInfoCollectorTest.java:68)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at junit.framework.TestCase.runBare(TestCase.java:141)
> at junit.framework.TestResult$1.protect(TestResult.java:122)
> at junit.framework.TestResult.runProtected(TestResult.java:142)
> at junit.framework.TestResult.run(TestResult.java:125)
> at junit.framework.TestCase.run(TestCase.java:129)
> at junit.framework.TestSuite.runTest(TestSuite.java:255)
> at junit.framework.TestSuite.run(TestSuite.java:250)
> at junit.framework.TestSuite.runTest(TestSuite.java:255)
> at junit.framework.TestSuite.run(TestSuite.java:250)
> at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:84)
> at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:123)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:104)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:164)
> at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:110)
> at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:175)
> at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:123)
> at org.eclipse.tycho.surefire.osgibooter.OsgiSurefireBooter.run(OsgiSurefireBooter.java:86)
> at org.eclipse.tycho.surefire.osgibooter.HeadlessTestApplication.run(HeadlessTestApplication.java:21)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.eclipse.equinox.internal.app.EclipseAppContainer.callMethodWithException(EclipseAppContainer.java:587)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:198)
> 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:379)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:233)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1438)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19585) Mixture of jetty 9 bundles versions in the TP
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19585?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-19585:
----------------------------------------
New mirror is available at http://download.jboss.org/jbosstools/updates/requirements/jetty/9.2.9.v20... . [~ibuziuk] Do you want to provide the pull request?
> Mixture of jetty 9 bundles versions in the TP
> ---------------------------------------------
>
> Key: JBIDE-19585
> URL: https://issues.jboss.org/browse/JBIDE-19585
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform
> Affects Versions: 4.3.0.Alpha1
> Reporter: Ilya Buziuk
> Priority: Minor
>
> Basically, here is the list of jetty 9 bundles in the TP:
> 1. org.eclipse.jetty.http_9.2.9.v20150224.jar
> 2. org.eclipse.jetty.continuation_9.2.9.v20150224.jar
> 3. org.eclipse.jetty.http_9.2.9.v20150224.jar
> 4. org.eclipse.jetty.io_9.2.9.v20150224.jar
> 5. org.eclipse.jetty.proxy_9.2.5.v20141112.jar
> 6. org.eclipse.jetty.rewrite_9.2.5.v20141112.jar
> 7. org.eclipse.jetty.security_9.2.9.v20150224.jar
> 8. org.eclipse.jetty.server_9.2.9.v20150224.jar
> 9. org.eclipse.jetty.servlets_9.2.5.v20141112.jar
> 10. org.eclipse.jetty.util_9.2.9.v20150224.jar
> 11. org.eclipse.jetty.websocket.api_9.2.5.v20141112.jar (and other websocket stuff)
> The good news is that CordovaSim and BrowserSim seems to work fine against M6 TP. However, it would be really great to have a single version of bundles to avoid potential breakage.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-15714) Dynamic content assist for AngularJS expressions in html files
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15714?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov commented on JBIDE-15714:
------------------------------------------------
[~maxandersen] afaics yes.
All prs are pushed, so marking this issue as resolved
> Dynamic content assist for AngularJS expressions in html files
> --------------------------------------------------------------
>
> Key: JBIDE-15714
> URL: https://issues.jboss.org/browse/JBIDE-15714
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: jsp/jsf/xml/html source editing
> Reporter: Alexey Kazakov
> Assignee: Alexey Kazakov
> Priority: Critical
> Labels: new_and_noteworthy
> Fix For: 4.3.0.Alpha2
>
> Attachments: Diagram.gliffy, firstTime.png, vpe.png, vpe2.gif
>
>
> Dynamic content assist works with projects which are mature enough not to fail in runtime.
> Open any html page with JBoss HTML Editor (AngularJS templates are *not* supported) where some controllers are available and try Ctrl+Space on any {{}}.
> The very first time the message saying the data is loading will be shown (this message will be shown only once per editor):
> !firstTime.png!
> Press enter or Ctrl+Space again to see AngularJS proposals (if available):
> !vpe2.gif!
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years