[JBoss JIRA] (JBIDE-17272) Compilation error in org.jboss.tools.common.jdt.debug
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17272?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-17272:
------------------------------------------
The referenced class is an internal class in the sun jdk (at least that's how I read the fully qualified class name). Is it wise to reference such a class in our tooling?
> Compilation error in org.jboss.tools.common.jdt.debug
> -----------------------------------------------------
>
> Key: JBIDE-17272
> URL: https://issues.jboss.org/browse/JBIDE-17272
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common/jst/core
> Affects Versions: 4.2.0.Beta2
> Reporter: Andre Dietisheim
> Assignee: Snjezana Peco
> Fix For: 4.2.0.Beta2
>
> Attachments: DebugLaunchConfigurationListener.png, RemoteDebugActivator.png
>
>
> I have compilation errors in org.jboss.tools.common.jdt.debug.DebugLaunchConfigurationListener
> {code}
> The type com.sun.jdi.connect.Connector$Argument cannot be resolved. It is indirectly referenced from required .class files
> {code}
> !DebugLaunchConfigurationListener.png!
> !RemoteDebugActivator.png!
> DebugLaunchConfigurationListener is apparently referencing internal jdk classes which are not available in linux jdk (?)
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months
[JBoss JIRA] (JBIDE-17471) "Computing connector status" error when installing from central right after start
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17471?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-17471.
---------------------------------
I'm closing this one as I created another JIRA here: JBIDE-17496
Looking at the description, it looks like it's the same. But there is some progress. Before respin-a, hitting the refresh button and then installing something could produce errors. Also, with respin-a, I don't get any errors in subsequent tries on a given installation - it can only be reproduced on a brand new installation.
> "Computing connector status" error when installing from central right after start
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-17471
> URL: https://issues.jboss.org/browse/JBIDE-17471
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.2.0.Beta2
> Environment: JBDS 8.0.0.Beta2 B104
> Reporter: Martin Malina
> Assignee: Fred Bricon
> Priority: Critical
> Labels: respin-a
> Fix For: 4.2.0.Beta2
>
>
> I understand this might overlap with JBIDE-17463 ("Computing connector status" error when closing Central after changing availability Early Access), but it's a bit different.
> If I try to install anything from Central right after JBDS start, the install dialog gets open, but a few seconds later, I get may Computing connector status errors. If I click Details, I can see they are all NPEs.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months
[JBoss JIRA] (JBIDE-17477) Remember to skip application creation in JAX-RS Wizard
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17477?page=com.atlassian.jira.plugi... ]
Xavier Coulon reassigned JBIDE-17477:
-------------------------------------
Assignee: Xavier Coulon
> Remember to skip application creation in JAX-RS Wizard
> ------------------------------------------------------
>
> Key: JBIDE-17477
> URL: https://issues.jboss.org/browse/JBIDE-17477
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: webservices
> Affects Versions: 4.2.0.Beta2
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Fix For: 4.2.0.Beta3
>
>
> The JAX-RS Resource creation wizard provides a page to create a JAX-RS Application in the project if none was found, but the user may want to skip this step if she plans to deploy her application in a non JEE6/7 environment - which would require a custom configuration (e.g.: a servlet dispatcher) to activate and use the JAX-RS resources.
> The wizard should remember that choice, so the user would not have to explicitly skip this step for each new JAX-RS resource she wants to create.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months
[JBoss JIRA] (JBIDE-17284) OpenJDK seem to have issues with SSL/TLS handshakes when using URLConnection
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17284?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-17284:
-------------------------------------
Fix Version/s: 4.2.0.Beta3
> OpenJDK seem to have issues with SSL/TLS handshakes when using URLConnection
> ----------------------------------------------------------------------------
>
> Key: JBIDE-17284
> URL: https://issues.jboss.org/browse/JBIDE-17284
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common/jst/core, openshift, upstream
> Reporter: Max Rydahl Andersen
> Priority: Critical
> Fix For: 4.2.0.Beta3
>
>
> We've received multiple reports about instant crashes of users running JBoss Tools and Developer Studio.
> The common issue is that it happens when they use OpenJDK vm, not Oracle.
> The crash log normally contains something similar to:
> Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
> j sun.security.pkcs11.wrapper.PKCS11.C_CreateObject(J[Lsun/security/pkcs11/wrapper/CK_ATTRIBUTE;)J+0
> j sun.security.pkcs11.P11ECKeyFactory.generatePublic(Ljava/security/spec/ECPoint;Ljava/security/spec/ECParameterSpec;)Ljava/security/PublicKey;+170
> j sun.security.pkcs11.P11ECKeyFactory.engineGeneratePublic(Ljava/security/spec/KeySpec;)Ljava/security/PublicKey;+80
> j java.security.KeyFactory.generatePublic(Ljava/security/spec/KeySpec;)Ljava/security/PublicKey;+25
> j sun.security.ssl.HandshakeMessage$ECDH_ServerKeyExchange.<init>(Lsun/security/ssl/HandshakeInStream;Ljava/security/PublicKey;[B[BLjava/util/Collection;Lsun/security/ssl/ProtocolVersion;)V+228
> Opening this bug to collect and use a key issue for hunting down the cause.
> Note: This issue is *not* specific to JBoss Tools as far as I can see, but it does affect us since we lookup a file located behind https url at key times which seem to trigger the crash.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months
[JBoss JIRA] (JBIDE-17496) Central installation fails if done right after Eclipse start
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17496?page=com.atlassian.jira.plugi... ]
Martin Malina updated JBIDE-17496:
----------------------------------
Priority: Critical (was: Major)
> Central installation fails if done right after Eclipse start
> ------------------------------------------------------------
>
> Key: JBIDE-17496
> URL: https://issues.jboss.org/browse/JBIDE-17496
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.2.0.Beta2
> Environment: JBDS 8.0.0.Beta2a B106
> Reporter: Martin Malina
> Priority: Critical
> Attachments: connector-error.png, problems-occurred.png
>
>
> When you try to install something from Central as soon as JBDS starts for the first time, you can get errors.
> I can reproduce some sort of errors every time, but only on a completely fresh install of JBDS/JBT (no central repo data cached).
> It looks like there is a race condition.
> Several times when I tried to install Findbugs, I got:
> {quote}
> The following connectors are not available: FindBugs
> Proceed with the installation anyways?
> {quote}
> Followed by the Computing connector errors with NPEs familiar from JBIDE-17471
> !connector-error.png!
> If I proceed anyway, the install dialog is empty.
> If I click that I don't want to install, I get this:
> {code}
> Problems occurred while performing installation: The following connectors are not available: FindBugs (id=edu.umd.cs.findbugs.plugin.eclipse.feature.group, site=https://devstudio.jboss.com/updates/8.0-staging/central/core/)
> The following connectors are not available: FindBugs (id=edu.umd.cs.findbugs.plugin.eclipse.feature.group, site=https://devstudio.jboss.com/updates/8.0-staging/central/core/)
> {code}
> !problems-occurred.png!
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months
[JBoss JIRA] (JBIDE-17496) Central installation fails if done right after Eclipse start
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17496?page=com.atlassian.jira.plugi... ]
Martin Malina updated JBIDE-17496:
----------------------------------
Description:
When you try to install something from Central as soon as JBDS starts for the first time, you can get errors.
I can reproduce some sort of errors every time, but only on a completely fresh install of JBDS/JBT (no central repo data cached).
It looks like there is a race condition.
Several times when I tried to install Findbugs, I got:
{quote}
The following connectors are not available: FindBugs
Proceed with the installation anyways?
{quote}
Followed by the Computing connector errors with NPEs familiar from JBIDE-17471
!connector-error.png!
If I proceed anyway, the install dialog is empty.
If I click that I don't want to install, I get this:
{code}
Problems occurred while performing installation: The following connectors are not available: FindBugs (id=edu.umd.cs.findbugs.plugin.eclipse.feature.group, site=https://devstudio.jboss.com/updates/8.0-staging/central/core/)
The following connectors are not available: FindBugs (id=edu.umd.cs.findbugs.plugin.eclipse.feature.group, site=https://devstudio.jboss.com/updates/8.0-staging/central/core/)
{code}
!problems-occurred.png!
was:
When you try to install something from Central as soon as JBDS starts for the first time, you can get errors.
I can reproduce some sort of errors every time, but only on a completely fresh install of JBDS/JBT (no central repo data cached).
It looks like there is a race condition.
Several times when I tried to install Findbugs, I got:
{quote}
The following connectors are not available: FindBugs
Proceed with the installation anyways?
{quote}
Followed by the Computing connector errors with NPEs familiar from JBIDE-17471
!connector-error.png!
If I proceed anyway, the install dialog is empty.
If I click that I don't want to install, I get this:
{code}
Problems occurred while performing installation: The following connectors are not available: FindBugs (id=edu.umd.cs.findbugs.plugin.eclipse.feature.group, site=https://devstudio.jboss.com/updates/8.0-staging/central/core/)
The following connectors are not available: FindBugs (id=edu.umd.cs.findbugs.plugin.eclipse.feature.group, site=https://devstudio.jboss.com/updates/8.0-staging/central/core/)
{code}
> Central installation fails if done right after Eclipse start
> ------------------------------------------------------------
>
> Key: JBIDE-17496
> URL: https://issues.jboss.org/browse/JBIDE-17496
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.2.0.Beta2
> Environment: JBDS 8.0.0.Beta2a B106
> Reporter: Martin Malina
> Attachments: connector-error.png, problems-occurred.png
>
>
> When you try to install something from Central as soon as JBDS starts for the first time, you can get errors.
> I can reproduce some sort of errors every time, but only on a completely fresh install of JBDS/JBT (no central repo data cached).
> It looks like there is a race condition.
> Several times when I tried to install Findbugs, I got:
> {quote}
> The following connectors are not available: FindBugs
> Proceed with the installation anyways?
> {quote}
> Followed by the Computing connector errors with NPEs familiar from JBIDE-17471
> !connector-error.png!
> If I proceed anyway, the install dialog is empty.
> If I click that I don't want to install, I get this:
> {code}
> Problems occurred while performing installation: The following connectors are not available: FindBugs (id=edu.umd.cs.findbugs.plugin.eclipse.feature.group, site=https://devstudio.jboss.com/updates/8.0-staging/central/core/)
> The following connectors are not available: FindBugs (id=edu.umd.cs.findbugs.plugin.eclipse.feature.group, site=https://devstudio.jboss.com/updates/8.0-staging/central/core/)
> {code}
> !problems-occurred.png!
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months
[JBoss JIRA] (JBIDE-17496) Central installation fails if done right after Eclipse start
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17496?page=com.atlassian.jira.plugi... ]
Martin Malina updated JBIDE-17496:
----------------------------------
Description:
When you try to install something from Central as soon as JBDS starts for the first time, you can get errors.
I can reproduce some sort of errors every time, but only on a completely fresh install of JBDS/JBT (no central repo data cached).
It looks like there is a race condition.
Several times when I tried to install Findbugs, I got:
{quote}
The following connectors are not available: FindBugs
Proceed with the installation anyways?
{quote}
Followed by the Computing connector errors with NPEs familiar from JBIDE-17471
!connector-error.png!
If I proceed anyway, the install dialog is empty.
If I click that I don't want to install, I get this:
{code}
Problems occurred while performing installation: The following connectors are not available: FindBugs (id=edu.umd.cs.findbugs.plugin.eclipse.feature.group, site=https://devstudio.jboss.com/updates/8.0-staging/central/core/)
The following connectors are not available: FindBugs (id=edu.umd.cs.findbugs.plugin.eclipse.feature.group, site=https://devstudio.jboss.com/updates/8.0-staging/central/core/)
{code}
was:
When you try to install something from Central as soon as JBDS starts for the first time, you can get errors.
I can reproduce some sort of errors every time, but only on a completely fresh install of JBDS/JBT (no central repo data cached).
It looks like there is a race condition.
Several times when I tried to install Findbugs, I got:
{quote}
The following connectors are not available: FindBugs
Proceed with the installation anyways?
{quote}
Followed by the Computing connector errors with NPEs familiar from JBIDE-17471
!connector-error.png!
If I proceed anyway, the install dialog is empty.
Another time I got a different error.
> Central installation fails if done right after Eclipse start
> ------------------------------------------------------------
>
> Key: JBIDE-17496
> URL: https://issues.jboss.org/browse/JBIDE-17496
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.2.0.Beta2
> Environment: JBDS 8.0.0.Beta2a B106
> Reporter: Martin Malina
> Attachments: connector-error.png, problems-occurred.png
>
>
> When you try to install something from Central as soon as JBDS starts for the first time, you can get errors.
> I can reproduce some sort of errors every time, but only on a completely fresh install of JBDS/JBT (no central repo data cached).
> It looks like there is a race condition.
> Several times when I tried to install Findbugs, I got:
> {quote}
> The following connectors are not available: FindBugs
> Proceed with the installation anyways?
> {quote}
> Followed by the Computing connector errors with NPEs familiar from JBIDE-17471
> !connector-error.png!
> If I proceed anyway, the install dialog is empty.
> If I click that I don't want to install, I get this:
> {code}
> Problems occurred while performing installation: The following connectors are not available: FindBugs (id=edu.umd.cs.findbugs.plugin.eclipse.feature.group, site=https://devstudio.jboss.com/updates/8.0-staging/central/core/)
> The following connectors are not available: FindBugs (id=edu.umd.cs.findbugs.plugin.eclipse.feature.group, site=https://devstudio.jboss.com/updates/8.0-staging/central/core/)
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months
[JBoss JIRA] (JBIDE-17496) Central installation fails if done right after Eclipse start
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17496?page=com.atlassian.jira.plugi... ]
Martin Malina updated JBIDE-17496:
----------------------------------
Attachment: problems-occurred.png
> Central installation fails if done right after Eclipse start
> ------------------------------------------------------------
>
> Key: JBIDE-17496
> URL: https://issues.jboss.org/browse/JBIDE-17496
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.2.0.Beta2
> Environment: JBDS 8.0.0.Beta2a B106
> Reporter: Martin Malina
> Attachments: connector-error.png, problems-occurred.png
>
>
> When you try to install something from Central as soon as JBDS starts for the first time, you can get errors.
> I can reproduce some sort of errors every time, but only on a completely fresh install of JBDS/JBT (no central repo data cached).
> It looks like there is a race condition.
> Several times when I tried to install Findbugs, I got:
> {quote}
> The following connectors are not available: FindBugs
> Proceed with the installation anyways?
> {quote}
> Followed by the Computing connector errors with NPEs familiar from JBIDE-17471
> !connector-error.png!
> If I proceed anyway, the install dialog is empty.
> If I click that I don't want to install, I get this:
> {code}
> Problems occurred while performing installation: The following connectors are not available: FindBugs (id=edu.umd.cs.findbugs.plugin.eclipse.feature.group, site=https://devstudio.jboss.com/updates/8.0-staging/central/core/)
> The following connectors are not available: FindBugs (id=edu.umd.cs.findbugs.plugin.eclipse.feature.group, site=https://devstudio.jboss.com/updates/8.0-staging/central/core/)
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months
[JBoss JIRA] (JBIDE-17496) Central installation fails if done right after Eclipse start
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17496?page=com.atlassian.jira.plugi... ]
Martin Malina updated JBIDE-17496:
----------------------------------
Steps to Reproduce:
1. Have a fresh install of JBDS/JBT (clean workspace alone is not enough - this bug cannot be reproduced once the central metadata have been cached)
2. Start JBDS with a clean workspace
3. Go straight to Central -> Software and try to install something, e.g. FindBugs
4. Wait and within a minute you will get errors
was:
1. Have a fresh install of JBDS/JBT (clean workspace alone is not enough - this bug cannot be reproduced once the central metadata have been cached)
2. Start JBDS with a clean workspace
3. Go straight to Central -> Software and try to install something, e.g. FindBugs
4. You will get errors
> Central installation fails if done right after Eclipse start
> ------------------------------------------------------------
>
> Key: JBIDE-17496
> URL: https://issues.jboss.org/browse/JBIDE-17496
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.2.0.Beta2
> Environment: JBDS 8.0.0.Beta2a B106
> Reporter: Martin Malina
> Attachments: connector-error.png
>
>
> When you try to install something from Central as soon as JBDS starts for the first time, you can get errors.
> I can reproduce some sort of errors every time, but only on a completely fresh install of JBDS/JBT (no central repo data cached).
> It looks like there is a race condition.
> Several times when I tried to install Findbugs, I got:
> {quote}
> The following connectors are not available: FindBugs
> Proceed with the installation anyways?
> {quote}
> Followed by the Computing connector errors with NPEs familiar from JBIDE-17471
> !connector-error.png!
> If I proceed anyway, the install dialog is empty.
> Another time I got a different error.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months
[JBoss JIRA] (JBIDE-16375) Allow to extend Central extensions catalog with "Early Access" stuff
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16375?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-16375:
----------------------------------------
[~rhopp] You can create a sandbox to test it. See my comment here from April 10th.
However, it may be worth waiting for JBIDE-17318 to test it, since it would allow you to validate everything at once.
> Allow to extend Central extensions catalog with "Early Access" stuff
> --------------------------------------------------------------------
>
> Key: JBIDE-16375
> URL: https://issues.jboss.org/browse/JBIDE-16375
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: central, discovery
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Fix For: 4.2.0.Beta2
>
>
> In order to make it easier for people to consume some "Beta" extensions from JBT or JBDS release (such as installing a Beta of JBT-IS on top of a JBT release), it would make sense to have Central allow users to select some catalogs in a UI entry such as "Include Experimental stuff" to show additional catalog entries.
> Either this could be a single catalog with the experimental content being annotated, or it could be 2 (or more catalogs) which have different quality levels.
> The Central UI will need to give feedback on the quality level for a given entry ("supported" or "experimental" or ...).
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months