[JBoss JIRA] (JBIDE-26017) Runtime detection table of paths in Preferences is covering checkbox on selected row
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26017?page=com.atlassian.jira.plugi... ]
Ondrej Dockal updated JBIDE-26017:
----------------------------------
Description: Selected row in runtime detection paths table is covering checkbox for Every start option. It is not user friendly when one wants to toggle the checkbox.
> Runtime detection table of paths in Preferences is covering checkbox on selected row
> ------------------------------------------------------------------------------------
>
> Key: JBIDE-26017
> URL: https://issues.jboss.org/browse/JBIDE-26017
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: runtime-detection
> Affects Versions: 4.6.0.AM1
> Environment: Fedora 27
> Reporter: Ondrej Dockal
> Assignee: Rob Stryker
> Priority: Minor
> Attachments: preferences_runtime_detection.png
>
>
> Selected row in runtime detection paths table is covering checkbox for Every start option. It is not user friendly when one wants to toggle the checkbox.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBDS-4703) Auto build is not working for maven project
by Pavol Srna (JIRA)
[ https://issues.jboss.org/browse/JBDS-4703?page=com.atlassian.jira.plugin.... ]
Pavol Srna commented on JBDS-4703:
----------------------------------
I've changed the priority to "Critical". I don't think this is blocker for AM1. But will be for the upcoming milestones.
> Auto build is not working for maven project
> -------------------------------------------
>
> Key: JBDS-4703
> URL: https://issues.jboss.org/browse/JBDS-4703
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: maven
> Affects Versions: 12.0.0.AM1
> Environment: F27, F28, Win10
> Red Hat JBoss Developer Studio
> Version: 12.0.0.AM1
> Build id: AM1-v20180508-1631-B2428
> Build date: 20180508-1631
> Reporter: Josef Kopriva
> Assignee: Nick Boldt
> Priority: Critical
> Fix For: 12.0.0.GA
>
> Attachments: test.zip
>
>
> Auto build is not working.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-25990) FrameworkEvent ERROR
by Josef Kopriva (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25990?page=com.atlassian.jira.plugi... ]
Josef Kopriva commented on JBIDE-25990:
---------------------------------------
There is similar error for livereload:
{code:java}
eclipse.buildId=12.0.0.AM1-v20180508-1631-B2428
java.version=1.8.0_171
java.vendor=Oracle Corporation
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
Framework arguments: -product com.jboss.devstudio.core.product
Command-line arguments: -data file:/home/jkopriva/devstudio_B2428_4/workspace/ -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
org.jboss.tools.livereload.ui
Error
Thu May 10 15:28:33 CEST 2018
FrameworkEvent ERROR
org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.livereload.ui [1131]
Unresolved requirement: Require-Bundle: org.jboss.tools.livereload.core; bundle-version="1.0.0"
-> Bundle-SymbolicName: org.jboss.tools.livereload.core; bundle-version="1.5.1.v20170822-1705"; singleton:="true"
org.jboss.tools.livereload.core [1130]
Unresolved requirement: Require-Bundle: org.apache.aries.spifly.dynamic.bundle; bundle-version="1.0.2"
-> Bundle-SymbolicName: org.apache.aries.spifly.dynamic.bundle; bundle-version="1.0.2"
org.apache.aries.spifly.dynamic.bundle [1121]
No resolution report for the bundle. Unresolved requirement: Require-Bundle: org.eclipse.jetty.websocket.servlet; bundle-version="[9.4.0,9.5.0)"
-> Bundle-SymbolicName: org.eclipse.jetty.websocket.servlet; bundle-version="9.4.8.v20171121"
org.eclipse.jetty.websocket.servlet [1129]
Unresolved requirement: Require-Capability: osgi.serviceloader; filter:="(osgi.serviceloader=org.eclipse.jetty.websocket.servlet.WebSocketServletFactory)"; cardinality:="multiple"
-> Provide-Capability: osgi.serviceloader; osgi.serviceloader="org.eclipse.jetty.websocket.servlet.WebSocketServletFactory"
org.eclipse.jetty.websocket.server [1128]
Unresolved requirement: Require-Capability: osgi.extender; filter:="(osgi.extender=osgi.serviceloader.registrar)"
-> Provide-Capability: osgi.extender; osgi.extender="osgi.serviceloader.registrar"; version:Version="1.0.0"
Unresolved requirement: Import-Package: org.eclipse.jetty.websocket.servlet; version="[9.4.8,9.4.9)"
-> Export-Package: org.eclipse.jetty.websocket.servlet; bundle-symbolic-name="org.eclipse.jetty.websocket.servlet"; bundle-version="9.4.8.v20171121"; version="9.4.8"
Unresolved requirement: Require-Capability: osgi.extender; filter:="(osgi.extender=osgi.serviceloader.processor)"
-> Provide-Capability: osgi.extender; osgi.extender="osgi.serviceloader.processor"; version:Version="1.0.0"
Unresolved requirement: Require-Bundle: org.eclipse.jetty.websocket.server; bundle-version="[9.4.0,9.5.0)"
-> Bundle-SymbolicName: org.eclipse.jetty.websocket.server; bundle-version="9.4.8.v20171121"
Bundle was not resolved because of a uses contraint violation.
org.osgi.service.resolver.ResolutionException: Uses constraint violation. Unable to resolve resource org.apache.aries.spifly.dynamic.bundle [osgi.identity; osgi.identity="org.apache.aries.spifly.dynamic.bundle"; type="osgi.bundle"; version:Version="1.0.2"] because it is exposed to package 'org.objectweb.asm' from resources org.objectweb.asm [osgi.identity; type="osgi.bundle"; version:Version="5.0.1.v201404251740"; osgi.identity="org.objectweb.asm"] and org.objectweb.asm [osgi.identity; type="osgi.bundle"; version:Version="6.0.0.v20170929-1901"; osgi.identity="org.objectweb.asm"] via two dependency chains.
Chain 1:
org.apache.aries.spifly.dynamic.bundle [osgi.identity; osgi.identity="org.apache.aries.spifly.dynamic.bundle"; type="osgi.bundle"; version:Version="1.0.2"]
import: (&(osgi.wiring.package=org.objectweb.asm)(&(version>=5.0.0)(!(version>=6.0.0))))
|
export: osgi.wiring.package: org.objectweb.asm
org.objectweb.asm [osgi.identity; type="osgi.bundle"; version:Version="5.0.1.v201404251740"; osgi.identity="org.objectweb.asm"]
Chain 2:
org.apache.aries.spifly.dynamic.bundle [osgi.identity; osgi.identity="org.apache.aries.spifly.dynamic.bundle"; type="osgi.bundle"; version:Version="1.0.2"]
import: (&(osgi.wiring.package=org.objectweb.asm.commons)(&(version>=5.0.0)(!(version>=6.0.0))))
|
export: osgi.wiring.package=org.objectweb.asm.commons; uses:=org.objectweb.asm
org.objectweb.asm.commons [osgi.identity; osgi.identity="org.objectweb.asm.commons"; type="osgi.bundle"; version:Version="5.0.1.v201404251740"]
import: (osgi.wiring.package=org.objectweb.asm)
|
export: osgi.wiring.package: org.objectweb.asm
org.objectweb.asm [osgi.identity; type="osgi.bundle"; version:Version="6.0.0.v20170929-1901"; osgi.identity="org.objectweb.asm"]
at org.eclipse.osgi.container.Module.start(Module.java:444)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1682)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1661)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1624)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1555)
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)
{code}
> FrameworkEvent ERROR
> --------------------
>
> Key: JBIDE-25990
> URL: https://issues.jboss.org/browse/JBIDE-25990
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server, upstream
> Affects Versions: 4.6.0.AM1
> Reporter: Martin Malina
> Assignee: Nick Boldt
> Fix For: 4.6.0.AM2
>
>
> I installed devstudio 12 nightly [1] today and saw this error in the Error Log view:
> {code}
> FrameworkEvent ERROR
> {code}
> {code}
> org.osgi.framework.BundleException: Could not resolve module: org.eclipse.wst.server.preview [777]
> Unresolved requirement: Require-Bundle: org.eclipse.jetty.servlet; bundle-version="[9.4.7,10.0.0)"
> -> Bundle-SymbolicName: org.eclipse.jetty.servlet; bundle-version="9.4.9.v20180320"
> org.eclipse.jetty.servlet [363]
> Unresolved requirement: Import-Package: org.eclipse.jetty.http; version="[9.4.9,9.4.10)"
> -> Export-Package: org.eclipse.jetty.http; bundle-symbolic-name="org.eclipse.jetty.http"; bundle-version="9.4.9.v20180320"; version="9.4.9"; uses:="org.eclipse.jetty.io,org.eclipse.jetty.util,org.eclipse.jetty.util.component,org.eclipse.jetty.util.log,org.eclipse.jetty.util.resource"
> org.eclipse.jetty.http [355]
> Unresolved requirement: Import-Package: org.eclipse.jetty.io; version="[9.4.9,9.4.10)"
> -> Export-Package: org.eclipse.jetty.io; bundle-symbolic-name="org.eclipse.jetty.io"; bundle-version="9.4.9.v20180320"; version="9.4.9"; uses:="javax.net.ssl,org.eclipse.jetty.util,org.eclipse.jetty.util.annotation,org.eclipse.jetty.util.component,org.eclipse.jetty.util.log,org.eclipse.jetty.util.thread"
> org.eclipse.jetty.io [357]
> Unresolved requirement: Import-Package: org.eclipse.jetty.util.annotation; version="[9.4.9,9.4.10)"
> -> Export-Package: org.eclipse.jetty.util.annotation; bundle-symbolic-name="org.eclipse.jetty.util"; bundle-version="9.4.9.v20180320"; version="9.4.9"
> org.eclipse.jetty.util [365]
> Unresolved requirement: Require-Capability: osgi.serviceloader; filter:="(osgi.serviceloader=org.eclipse.jetty.util.security.CredentialProvider)"; resolution:="optional"; cardinality:="multiple"
> Unresolved requirement: Require-Capability: osgi.extender; filter:="(osgi.extender=osgi.serviceloader.processor)"
> Unresolved requirement: Import-Package: org.eclipse.jetty.util; version="[9.4.9,9.4.10)"
> -> Export-Package: org.eclipse.jetty.util; bundle-symbolic-name="org.eclipse.jetty.util"; bundle-version="9.4.9.v20180320"; version="9.4.9"; uses:="javax.servlet,javax.servlet.http,org.eclipse.jetty.util.annotation,org.eclipse.jetty.util.component,org.eclipse.jetty.util.log,org.eclipse.jetty.util.resource,org.eclipse.jetty.util.thread"
> Unresolved requirement: Import-Package: org.eclipse.jetty.util; version="[9.4.9,9.4.10)"
> -> Export-Package: org.eclipse.jetty.util; bundle-symbolic-name="org.eclipse.jetty.util"; bundle-version="9.4.9.v20180320"; version="9.4.9"; uses:="javax.servlet,javax.servlet.http,org.eclipse.jetty.util.annotation,org.eclipse.jetty.util.component,org.eclipse.jetty.util.log,org.eclipse.jetty.util.resource,org.eclipse.jetty.util.thread"
> Unresolved requirement: Require-Bundle: org.eclipse.jetty.security; bundle-version="[9.4.7,10.0.0)"
> -> Bundle-SymbolicName: org.eclipse.jetty.security; bundle-version="9.4.9.v20180320"
> org.eclipse.jetty.security [359]
> Unresolved requirement: Import-Package: org.eclipse.jetty.http; version="[9.4.9,9.4.10)"
> -> Export-Package: org.eclipse.jetty.http; bundle-symbolic-name="org.eclipse.jetty.http"; bundle-version="9.4.9.v20180320"; version="9.4.9"; uses:="org.eclipse.jetty.io,org.eclipse.jetty.util,org.eclipse.jetty.util.component,org.eclipse.jetty.util.log,org.eclipse.jetty.util.resource"
> Unresolved requirement: Require-Bundle: org.eclipse.jetty.xml; bundle-version="[9.4.7,10.0.0)"
> -> Bundle-SymbolicName: org.eclipse.jetty.xml; bundle-version="9.4.9.v20180320"
> org.eclipse.jetty.xml [368]
> Unresolved requirement: Import-Package: org.eclipse.jetty.util; version="[9.4.9,9.4.10)"
> -> Export-Package: org.eclipse.jetty.util; bundle-symbolic-name="org.eclipse.jetty.util"; bundle-version="9.4.9.v20180320"; version="9.4.9"; uses:="javax.servlet,javax.servlet.http,org.eclipse.jetty.util.annotation,org.eclipse.jetty.util.component,org.eclipse.jetty.util.log,org.eclipse.jetty.util.resource,org.eclipse.jetty.util.thread"
> Unresolved requirement: Require-Bundle: org.eclipse.jetty.io; bundle-version="[9.4.7,10.0.0)"
> -> Bundle-SymbolicName: org.eclipse.jetty.io; bundle-version="9.4.9.v20180320"
> Unresolved requirement: Require-Bundle: org.eclipse.jetty.server; bundle-version="[9.4.7,10.0.0)"
> -> Bundle-SymbolicName: org.eclipse.jetty.server; bundle-version="9.4.9.v20180320"
> org.eclipse.jetty.server [361]
> Unresolved requirement: Import-Package: org.eclipse.jetty.http; version="[9.4.9,9.4.10)"
> -> Export-Package: org.eclipse.jetty.http; bundle-symbolic-name="org.eclipse.jetty.http"; bundle-version="9.4.9.v20180320"; version="9.4.9"; uses:="org.eclipse.jetty.io,org.eclipse.jetty.util,org.eclipse.jetty.util.component,org.eclipse.jetty.util.log,org.eclipse.jetty.util.resource"
> Unresolved requirement: Require-Bundle: org.eclipse.jetty.http; bundle-version="[9.4.7,10.0.0)"
> -> Bundle-SymbolicName: org.eclipse.jetty.http; bundle-version="9.4.9.v20180320"
> Unresolved requirement: Require-Bundle: org.eclipse.jetty.util; bundle-version="[9.4.7,10.0.0)"
> -> Bundle-SymbolicName: org.eclipse.jetty.util; bundle-version="9.4.9.v20180320"
> Unresolved requirement: Require-Bundle: org.eclipse.jetty.webapp; bundle-version="[9.4.7,10.0.0)"
> -> Bundle-SymbolicName: org.eclipse.jetty.webapp; bundle-version="9.4.9.v20180320"
> org.eclipse.jetty.webapp [367]
> Unresolved requirement: Import-Package: org.eclipse.jetty.http; version="[9.4.9,9.4.10)"
> -> Export-Package: org.eclipse.jetty.http; bundle-symbolic-name="org.eclipse.jetty.http"; bundle-version="9.4.9.v20180320"; version="9.4.9"; uses:="org.eclipse.jetty.io,org.eclipse.jetty.util,org.eclipse.jetty.util.component,org.eclipse.jetty.util.log,org.eclipse.jetty.util.resource"
> at org.eclipse.osgi.container.Module.start(Module.java:444)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1682)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1661)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1624)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1555)
> 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)
> {code}
> It's not strictly server tools related, but maybe you can take a look.
> I checked in plain Eclipse Java EE Photon M6 bundle and the error wasn't there.
> [1] devstudio-12.0.0.AM1-v20180502-0411-B2377-installer-standalone.jar
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-26016) javax.websocket is missing from default classpath entries of WildFly 12 Runtime
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26016?page=com.atlassian.jira.plugi... ]
Nick Boldt reassigned JBIDE-26016:
----------------------------------
Assignee: Rob Stryker
> javax.websocket is missing from default classpath entries of WildFly 12 Runtime
> -------------------------------------------------------------------------------
>
> Key: JBIDE-26016
> URL: https://issues.jboss.org/browse/JBIDE-26016
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.5.3.Final
> Environment: Windows 7, Eclipse Oxygen.3a Release (4.7.3a), WildFly 12.0.0. Final
> Reporter: Marco Del Percio
> Assignee: Rob Stryker
> Priority: Minor
> Fix For: 4.6.0.AM2
>
> Attachments: javax.websocket.missing.png
>
>
> When creating a new server instance based on WildFly 12 Runtime, the default classpath entries of such runtime do not include javax.websocket.
> The workaround is to manually amend the default classpath entries for that runtime and add the missing module.
> javax.websocket has always been there by default until WildFly 11 Runtime, I don't see why it shouldn't be there with WildFly 12 Runtime
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-26016) javax.websocket is missing from default classpath entries of WildFly 12 Runtime
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26016?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-26016:
-------------------------------
Fix Version/s: 4.6.0.AM2
> javax.websocket is missing from default classpath entries of WildFly 12 Runtime
> -------------------------------------------------------------------------------
>
> Key: JBIDE-26016
> URL: https://issues.jboss.org/browse/JBIDE-26016
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.5.3.Final
> Environment: Windows 7, Eclipse Oxygen.3a Release (4.7.3a), WildFly 12.0.0. Final
> Reporter: Marco Del Percio
> Assignee: Rob Stryker
> Priority: Minor
> Fix For: 4.6.0.AM2
>
> Attachments: javax.websocket.missing.png
>
>
> When creating a new server instance based on WildFly 12 Runtime, the default classpath entries of such runtime do not include javax.websocket.
> The workaround is to manually amend the default classpath entries for that runtime and add the missing module.
> javax.websocket has always been there by default until WildFly 11 Runtime, I don't see why it shouldn't be there with WildFly 12 Runtime
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBDS-4703) Auto build is not working for maven project
by Josef Kopriva (JIRA)
[ https://issues.jboss.org/browse/JBDS-4703?page=com.atlassian.jira.plugin.... ]
Josef Kopriva edited comment on JBDS-4703 at 5/10/18 8:34 AM:
--------------------------------------------------------------
[~nickboldt][~jeffmaury] I have tried it with Jeff's project, it works as expected. But when I try ITests, project is not rebuilt, [~odockal] have experienced same behavior.
I have also noticed tycho version 0.8.1 is installed, so it could be related?
was (Author: jkopriva):
[~nickboldt][~jeffmaury] I have tried it with Jeff's project, it works as expected. But when I try ITests, project is not rebuilt, [~odockal] have experienced same behavior.
> Auto build is not working for maven project
> -------------------------------------------
>
> Key: JBDS-4703
> URL: https://issues.jboss.org/browse/JBDS-4703
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: maven
> Affects Versions: 12.0.0.AM1
> Environment: F27, F28, Win10
> Red Hat JBoss Developer Studio
> Version: 12.0.0.AM1
> Build id: AM1-v20180508-1631-B2428
> Build date: 20180508-1631
> Reporter: Josef Kopriva
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 12.0.0.GA
>
> Attachments: test.zip
>
>
> Auto build is not working.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBDS-4703) Auto build is not working for maven project
by Josef Kopriva (JIRA)
[ https://issues.jboss.org/browse/JBDS-4703?page=com.atlassian.jira.plugin.... ]
Josef Kopriva commented on JBDS-4703:
-------------------------------------
[~nickboldt][~jeffmaury] I have tried it with Jeff's project, it works as expected. But when I try ITests, project is not rebuilt, [~odockal] have experienced same behavior.
> Auto build is not working for maven project
> -------------------------------------------
>
> Key: JBDS-4703
> URL: https://issues.jboss.org/browse/JBDS-4703
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: maven
> Affects Versions: 12.0.0.AM1
> Environment: F27, F28, Win10
> Red Hat JBoss Developer Studio
> Version: 12.0.0.AM1
> Build id: AM1-v20180508-1631-B2428
> Build date: 20180508-1631
> Reporter: Josef Kopriva
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 12.0.0.GA
>
> Attachments: test.zip
>
>
> Auto build is not working.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months