[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 commented on JBIDE-25974:
------------------------------------------
merged into master.
> 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] (JBDS-4698) Unresolved requirement: Require-Bundle: org.eclipse.jetty.security
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4698?page=com.atlassian.jira.plugin.... ]
Nick Boldt resolved JBDS-4698.
------------------------------
Fix Version/s: 12.0.0.AM1
Resolution: Duplicate
Dupe of JBIDE-25990
> Unresolved requirement: Require-Bundle: org.eclipse.jetty.security
> ------------------------------------------------------------------
>
> Key: JBDS-4698
> URL: https://issues.jboss.org/browse/JBDS-4698
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build
> Affects Versions: 12.0.0.AM1
> Reporter: Josef Kopriva
> Assignee: Nick Boldt
> Fix For: 12.0.0.AM1
>
>
> There is an error in error log after devstudio:
> {code:java}
> eclipse.buildId=12.0.0.AM1-v20180502-1928-B2382
> 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: -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
> org.eclipse.wst.server.preview
> Error
> Thu May 03 07:33:55 CEST 2018
> FrameworkEvent ERROR
> org.osgi.framework.BundleException: Could not resolve module: org.eclipse.wst.server.preview [776]
> 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"
> 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; 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"
> 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.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"
> 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.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.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"
> 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.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.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.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.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"
> 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}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 1 month
[JBoss JIRA] (JBIDE-25971) Add Red Hat Developers sign up link to CDK New Server wizard
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25971?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-25971:
-------------------------------------
Labels: cdk_server_adapter_wizard (was: )
> Add Red Hat Developers sign up link to CDK New Server wizard
> ------------------------------------------------------------
>
> Key: JBIDE-25971
> URL: https://issues.jboss.org/browse/JBIDE-25971
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: cdk
> Affects Versions: 4.5.3.Final
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Labels: cdk_server_adapter_wizard
> Fix For: 4.6.x
>
> Attachments: new-server-cdk.png
>
>
> While reviewing documentation updates for cdk installation in devstudio, we noticed a thing that is not ideal in the workflow.
> Imagine you don't have an account on developers.redhat.com yet.
> You go to New Server -> CDK 3.2+.
> On the next page, you're supposed to fill out your credentials, but you don't have any. Yes, you could argue that there is a way to get there: If you don't have an account, that probably also means that you don't have a cdk binary either - you need the account to download it. So you need to click Download and install runtime... and that will offer you a link to register. So once cdk is downloaded, you can then add the credentials. But that's pretty cumbersome.
> So I would suggest we add a Register link somewhere - either on the New Server wizard's second page. Or once you click Add.. to add credentials.
> That's issue 1.
> !new-server-cdk.png!
> There are also a few side issues:
> 2. I would suggest you remove the Domain field/dropdown from the wizard. It's always just greyed out. If we ever want to support more of them we can add it back. And when you add the credentials you will see the domain there too, which is enough.
> 3. When you click Download and install runtime..., select a version and then go to the next page, this page is called JBoss.org Credentials - it's actually access.redhat.com credentials, can you change the title?
> 3.a Also, the link for signing up leads to access.redhat.com. Wouldn't it be better to point to developers.redhat.com sign up page? That's what devsuite installer does.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 1 month
[JBoss JIRA] (JBIDE-25971) Add Red Hat Developers sign up link to CDK New Server wizard
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25971?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-25971:
-------------------------------------
Fix Version/s: 4.6.x
(was: 4.6.0.AM1)
> Add Red Hat Developers sign up link to CDK New Server wizard
> ------------------------------------------------------------
>
> Key: JBIDE-25971
> URL: https://issues.jboss.org/browse/JBIDE-25971
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: cdk
> Affects Versions: 4.5.3.Final
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.6.x
>
> Attachments: new-server-cdk.png
>
>
> While reviewing documentation updates for cdk installation in devstudio, we noticed a thing that is not ideal in the workflow.
> Imagine you don't have an account on developers.redhat.com yet.
> You go to New Server -> CDK 3.2+.
> On the next page, you're supposed to fill out your credentials, but you don't have any. Yes, you could argue that there is a way to get there: If you don't have an account, that probably also means that you don't have a cdk binary either - you need the account to download it. So you need to click Download and install runtime... and that will offer you a link to register. So once cdk is downloaded, you can then add the credentials. But that's pretty cumbersome.
> So I would suggest we add a Register link somewhere - either on the New Server wizard's second page. Or once you click Add.. to add credentials.
> That's issue 1.
> !new-server-cdk.png!
> There are also a few side issues:
> 2. I would suggest you remove the Domain field/dropdown from the wizard. It's always just greyed out. If we ever want to support more of them we can add it back. And when you add the credentials you will see the domain there too, which is enough.
> 3. When you click Download and install runtime..., select a version and then go to the next page, this page is called JBoss.org Credentials - it's actually access.redhat.com credentials, can you change the title?
> 3.a Also, the link for signing up leads to access.redhat.com. Wouldn't it be better to point to developers.redhat.com sign up page? That's what devsuite installer does.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 1 month
[JBoss JIRA] (JBIDE-25971) Add Red Hat Developers sign up link to CDK New Server wizard
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25971?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-25971:
-------------------------------------
Fix Version/s: 4.6.0.AM1
> Add Red Hat Developers sign up link to CDK New Server wizard
> ------------------------------------------------------------
>
> Key: JBIDE-25971
> URL: https://issues.jboss.org/browse/JBIDE-25971
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: cdk
> Affects Versions: 4.5.3.Final
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.6.0.AM1
>
> Attachments: new-server-cdk.png
>
>
> While reviewing documentation updates for cdk installation in devstudio, we noticed a thing that is not ideal in the workflow.
> Imagine you don't have an account on developers.redhat.com yet.
> You go to New Server -> CDK 3.2+.
> On the next page, you're supposed to fill out your credentials, but you don't have any. Yes, you could argue that there is a way to get there: If you don't have an account, that probably also means that you don't have a cdk binary either - you need the account to download it. So you need to click Download and install runtime... and that will offer you a link to register. So once cdk is downloaded, you can then add the credentials. But that's pretty cumbersome.
> So I would suggest we add a Register link somewhere - either on the New Server wizard's second page. Or once you click Add.. to add credentials.
> That's issue 1.
> !new-server-cdk.png!
> There are also a few side issues:
> 2. I would suggest you remove the Domain field/dropdown from the wizard. It's always just greyed out. If we ever want to support more of them we can add it back. And when you add the credentials you will see the domain there too, which is enough.
> 3. When you click Download and install runtime..., select a version and then go to the next page, this page is called JBoss.org Credentials - it's actually access.redhat.com credentials, can you change the title?
> 3.a Also, the link for signing up leads to access.redhat.com. Wouldn't it be better to point to developers.redhat.com sign up page? That's what devsuite installer does.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 1 month
[JBoss JIRA] (JBIDE-25971) Add Red Hat Developers sign up link to CDK New Server wizard
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25971?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-25971:
------------------------------------------
merged PR [#619|https://github.com/jbosstools/jbosstools-base/pull/619] as a first fix for this issue. More to come.
{quote}
@adietish this was a side issue in the JIRA:
> 3. When you click Download and install runtime..., select a version and then go to the next page, this page is called JBoss.org
> Credentials - it's actually access.redhat.com credentials, can you change the title?
So it's a valid fix.
But I don't think this is enough to consider the JIRA fixed. I was hoping we could add a link to register somewhere on the New Server dialog.
{quote}
> Add Red Hat Developers sign up link to CDK New Server wizard
> ------------------------------------------------------------
>
> Key: JBIDE-25971
> URL: https://issues.jboss.org/browse/JBIDE-25971
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: cdk
> Affects Versions: 4.5.3.Final
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Attachments: new-server-cdk.png
>
>
> While reviewing documentation updates for cdk installation in devstudio, we noticed a thing that is not ideal in the workflow.
> Imagine you don't have an account on developers.redhat.com yet.
> You go to New Server -> CDK 3.2+.
> On the next page, you're supposed to fill out your credentials, but you don't have any. Yes, you could argue that there is a way to get there: If you don't have an account, that probably also means that you don't have a cdk binary either - you need the account to download it. So you need to click Download and install runtime... and that will offer you a link to register. So once cdk is downloaded, you can then add the credentials. But that's pretty cumbersome.
> So I would suggest we add a Register link somewhere - either on the New Server wizard's second page. Or once you click Add.. to add credentials.
> That's issue 1.
> !new-server-cdk.png!
> There are also a few side issues:
> 2. I would suggest you remove the Domain field/dropdown from the wizard. It's always just greyed out. If we ever want to support more of them we can add it back. And when you add the credentials you will see the domain there too, which is enough.
> 3. When you click Download and install runtime..., select a version and then go to the next page, this page is called JBoss.org Credentials - it's actually access.redhat.com credentials, can you change the title?
> 3.a Also, the link for signing up leads to access.redhat.com. Wouldn't it be better to point to developers.redhat.com sign up page? That's what devsuite installer does.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 1 month