[JBoss JIRA] (JBIDE-25974) CDK 3.4 runtime detection failing
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25974?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-25974:
-------------------------------------
Description:
Runtime detection doesn't work for 3.4.0 with the whitelist. A regex would be better
steps:
# EXE: Preferences > JBoss Runtime Detection > Download
# ASSERT: List of available runtimes shows up, containing CDK 3.4.0
# EXEC: Choose "CDK 3.4.0" & hit "Next"
# EXEC: next page: provide credentials & hit "Next"
# EXEC: next page: accept the terms & hit "Next"
# EXEC: next page: use the suggested defaults, make sure that "Install folder" is a separate folder (ex. freshly created ~/cdk/) & hit "Finish"
# ASSERT: wait for the download to finish
Result:
The download wont detect the new CDK 3.4.0 that you just downloaded
!image-2018-05-07-17-59-59-316.png!
was:Runtime detection doesn't work for 3.4.0 with the whitelist. A regex would be better
Attachment: image-2018-05-07-17-59-59-316.png
> CDK 3.4 runtime detection failing
> ---------------------------------
>
> Key: JBIDE-25974
> URL: https://issues.jboss.org/browse/JBIDE-25974
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: 4.6.0.AM1
>
> Attachments: image-2018-05-07-17-59-59-316.png
>
>
> Runtime detection doesn't work for 3.4.0 with the whitelist. A regex would be better
> steps:
> # EXE: Preferences > JBoss Runtime Detection > Download
> # ASSERT: List of available runtimes shows up, containing CDK 3.4.0
> # EXEC: Choose "CDK 3.4.0" & hit "Next"
> # EXEC: next page: provide credentials & hit "Next"
> # EXEC: next page: accept the terms & hit "Next"
> # EXEC: next page: use the suggested defaults, make sure that "Install folder" is a separate folder (ex. freshly created ~/cdk/) & hit "Finish"
> # ASSERT: wait for the download to finish
> Result:
> The download wont detect the new CDK 3.4.0 that you just downloaded
> !image-2018-05-07-17-59-59-316.png!
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 1 month
[JBoss JIRA] (JBIDE-25990) FrameworkEvent ERROR
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25990?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-25990:
-------------------------------
Fix Version/s: 4.6.0.AM2
> 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)
6 years, 1 month
[JBoss JIRA] (JBIDE-25553) Cannot create Hibernate Console Configuration for projects with java 9
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25553?page=com.atlassian.jira.plugi... ]
Koen Aers commented on JBIDE-25553:
-----------------------------------
The problem is solved with the limitation that the workbench should be started using Java 9. If the workbench is started with Java 8 it will still be possible to create a Java 9 project and create a Hibernate Console Configuration and even a Hibernate Code Generation Configuration for it that can generate classes but trying to open the console configuration for the newly generated classes will result in a Java version error because the classes have been compiled with the Java 9 runtime and the Console Configuration class loader tries to load them with Java 8.
I think this is an acceptable limitation as it has always been present. To solve this limitation (and to use the projects class loader instead of the platform's class loader) would mean considerable work and I am not sure if there is enough benefit to warrant the work.
I welcome your comments.
> Cannot create Hibernate Console Configuration for projects with java 9
> ----------------------------------------------------------------------
>
> Key: JBIDE-25553
> URL: https://issues.jboss.org/browse/JBIDE-25553
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Affects Versions: 4.5.2.AM2
> Reporter: Rastislav Wagner
> Assignee: Koen Aers
> Priority: Critical
> Fix For: 4.6.0.AM1
>
>
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 1 month