[JBoss JIRA] (JBDS-2988) Deleting a team repository - user is not prompted to confirm the deletion
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-2988?page=com.atlassian.jira.plugin.... ]
CDW Engine updated JBDS-2988:
-----------------------------
CDW docs_ack: ?
> Deleting a team repository - user is not prompted to confirm the deletion
> -------------------------------------------------------------------------
>
> Key: JBDS-2988
> URL: https://issues.jboss.org/browse/JBDS-2988
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: upstream
> Affects Versions: 8.0.0.Beta1
> Environment: JBDs 8.1.beta1
> Reporter: Len DiMaggio
> Assignee: Snjezana Peco
> Priority: Critical
> Fix For: 8.0.x
>
>
> When users select a team repository for deletion, the user is not required to confirm the deletion before the repository is actually deleted. A dialog is not presented to the user to confirm the deletion, the deletion is immediate.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBDS-2988) Deleting a team repository - user is not prompted to confirm the deletion
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBDS-2988?page=com.atlassian.jira.plugin.... ]
Snjezana Peco updated JBDS-2988:
--------------------------------
Fix Version/s: 8.0.x
(was: 8.0.0.Beta3)
> Deleting a team repository - user is not prompted to confirm the deletion
> -------------------------------------------------------------------------
>
> Key: JBDS-2988
> URL: https://issues.jboss.org/browse/JBDS-2988
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: upstream
> Affects Versions: 8.0.0.Beta1
> Environment: JBDs 8.1.beta1
> Reporter: Len DiMaggio
> Assignee: Snjezana Peco
> Priority: Critical
> Fix For: 8.0.x
>
>
> When users select a team repository for deletion, the user is not required to confirm the deletion before the repository is actually deleted. A dialog is not presented to the user to confirm the deletion, the deletion is immediate.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-17484) Trying to start a EAP/AS server in JBDS 8.beta2/JBT 420.beta2 raises exception
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17484?page=com.atlassian.jira.plugi... ]
Snjezana Peco updated JBIDE-17484:
----------------------------------
Fix Version/s: 4.2.x
(was: 4.2.0.Beta3)
> Trying to start a EAP/AS server in JBDS 8.beta2/JBT 420.beta2 raises exception
> ------------------------------------------------------------------------------
>
> Key: JBIDE-17484
> URL: https://issues.jboss.org/browse/JBIDE-17484
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server, xulrunner
> Affects Versions: 4.2.0.Beta2
> Environment: RHEL 6.5
> OpenJDK 1.7
> 4.2.0.beta2
> Reporter: Len DiMaggio
> Assignee: Snjezana Peco
> Priority: Critical
> Fix For: 4.2.x
>
>
> Trying to start a EAP/AS server in JBDS 8.beta2/JBT 420.beta2 raises this exception:
> May 29, 2014 3:32:09 PM org.xnio.ChannelListeners invokeChannelListener
> ERROR: A channel event listener threw an exception
> java.security.ProviderException: Could not initialize NSS
> at sun.security.pkcs11.SunPKCS11.<init>(SunPKCS11.java:223)
> at sun.security.pkcs11.SunPKCS11.<init>(SunPKCS11.java:103)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
> at sun.security.jca.ProviderConfig$2.run(ProviderConfig.java:224)
> at sun.security.jca.ProviderConfig$2.run(ProviderConfig.java:206)
> at java.security.AccessController.doPrivileged(Native Method)
> at sun.security.jca.ProviderConfig.doLoadProvider(ProviderConfig.java:206)
> at sun.security.jca.ProviderConfig.getProvider(ProviderConfig.java:187)
> at sun.security.jca.ProviderList.loadAll(ProviderList.java:281)
> at sun.security.jca.ProviderList.removeInvalid(ProviderList.java:298)
> at sun.security.jca.Providers.getFullProviderList(Providers.java:176)
> at java.security.Security.getProviders(Security.java:458)
> at org.xnio.sasl.SaslUtils.getFactories(SaslUtils.java:123)
> at org.xnio.sasl.SaslUtils.getSaslClientFactories(SaslUtils.java:100)
> at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:362)
> at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:227)
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72)
> at org.xnio.channels.TranslatingSuspendableChannel.handleReadable(TranslatingSuspendableChannel.java:189)
> at org.xnio.channels.TranslatingSuspendableChannel$1.handleEvent(TranslatingSuspendableChannel.java:103)
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72)
> at org.xnio.channels.TranslatingSuspendableChannel.handleReadable(TranslatingSuspendableChannel.java:189)
> at org.xnio.ssl.JsseConnectedSslStreamChannel.handleReadable(JsseConnectedSslStreamChannel.java:180)
> at org.xnio.channels.TranslatingSuspendableChannel$1.handleEvent(TranslatingSuspendableChannel.java:103)
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72)
> at org.xnio.nio.NioHandle.run(NioHandle.java:90)
> at org.xnio.nio.WorkerThread.run(WorkerThread.java:187)
> Caused by: java.io.IOException: /jboss/local/JBT/420.beta2/eclipse/plugins/org.mozilla.xulrunner.gtk.linux.x86_64_1.9.2.19pre/xulrunner/libnssutil3.so: version `NSSUTIL_3.13' not found (required by /usr/lib64/libnss3.so)
> at sun.security.pkcs11.Secmod.nssLoadLibrary(Native Method)
> at sun.security.pkcs11.Secmod.initialize(Secmod.java:209)
> at sun.security.pkcs11.SunPKCS11.<init>(SunPKCS11.java:218)
> ... 28 more
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBDS-2956) Spring IDE's associated projects and files cannot be created and many plugins never goes past "Starting"
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBDS-2956?page=com.atlassian.jira.plugin.... ]
Snjezana Peco updated JBDS-2956:
--------------------------------
Fix Version/s: 8.0.x
(was: 8.0.0.Beta3)
> Spring IDE's associated projects and files cannot be created and many plugins never goes past "Starting"
> --------------------------------------------------------------------------------------------------------
>
> Key: JBDS-2956
> URL: https://issues.jboss.org/browse/JBDS-2956
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: 3rd-party-certification
> Affects Versions: 8.0.0.Alpha2
> Environment: 64-bit Fedora 17
> Reporter: Marián Labuda
> Assignee: Snjezana Peco
> Priority: Blocker
> Fix For: 8.0.x
>
> Attachments: jbds800Alpha2report.zip, jbds_part1.png, jbds_part2.png, JBT4.2.0.Alpha2breport.zip, jbt_part1.png, jbt_part2.png, jbt_part3.png, report, spring_projects.png
>
>
> After installing Spring IDE into JBDS 8.0.0.Alpha2 there should be option to create associated projects / examples / files... from menu File - Other - Spring, but there is only item for creation Spring bean configuration file. Others are missing. Tests also JBT 4.2.0.Alpha2 and there was not this issue.
> See attached file.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-17284) OpenJDK seem to have issues with SSL/TLS handshakes when using URLConnection
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17284?page=com.atlassian.jira.plugi... ]
Snjezana Peco updated JBIDE-17284:
----------------------------------
Fix Version/s: 4.2.x
(was: 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
> Assignee: Snjezana Peco
> Priority: Blocker
> Fix For: 4.2.x
>
> Attachments: jbds-via-html5-vpe.png
>
>
> 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.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-17700) Cannot deploy jsf war with eclipse luna and jboss 7.1.x
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17700?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-17700:
---------------------------------------------
Any chance you got some signed jars or signed manifest headers or something in this project ?
> Cannot deploy jsf war with eclipse luna and jboss 7.1.x
> -------------------------------------------------------
>
> Key: JBIDE-17700
> URL: https://issues.jboss.org/browse/JBIDE-17700
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Environment: Win 7, Eclilpse Luna, JBoss Tools (via market place)
> Reporter: Oliver Pfau
> Priority: Critical
>
> When I publish my war to jboss 7.1 the following error occurs:
> An internal error occurred during: "Publishing to JBoss AS 7.1...".
> Could not initialize class de.schlichtherle.io.ArchiveControllers
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-17700) Cannot deploy jsf war with eclipse luna and jboss 7.1.x
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17700?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-17700:
---------------------------------------------
oliver - when you see 0% publishing and its stuck - please try run jstack against the eclipse process and get the stacktrace/threaddump.
We've seen the issue before but never been able to replicate it thus we are very keen on understanding what is going on and finding the cause.
The JBTValidationException looks like a different error unfortunately ;/
> Cannot deploy jsf war with eclipse luna and jboss 7.1.x
> -------------------------------------------------------
>
> Key: JBIDE-17700
> URL: https://issues.jboss.org/browse/JBIDE-17700
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Environment: Win 7, Eclilpse Luna, JBoss Tools (via market place)
> Reporter: Oliver Pfau
> Priority: Critical
>
> When I publish my war to jboss 7.1 the following error occurs:
> An internal error occurred during: "Publishing to JBoss AS 7.1...".
> Could not initialize class de.schlichtherle.io.ArchiveControllers
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-17737) org.jboss.tools.runtime.seam.detector.test.SeamRuntimeDetectionAllTests failure
by Daniel Azarov (JIRA)
Daniel Azarov created JBIDE-17737:
-------------------------------------
Summary: org.jboss.tools.runtime.seam.detector.test.SeamRuntimeDetectionAllTests failure
Key: JBIDE-17737
URL: https://issues.jboss.org/browse/JBIDE-17737
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: seam2
Affects Versions: 4.2.0.Beta3
Reporter: Daniel Azarov
Attachments: org.jboss.tools.runtime.seam.detector.test.SeamRuntimeDetectionAllTests.txt
{code}
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Running org.jboss.tools.runtime.seam.detector.test.SeamRuntimeDetectionAllTests
0
0
Tests run: 8, Failures: 3, Errors: 0, Skipped: 0, Time elapsed: 0.265 sec <<< FAILURE!
Results :
Failed tests: testJBossAs42(org.jboss.tools.runtime.seam.detector.test.SeamRuntimeDetectionTest): expected:<1> but was:<0>
testJBossAs51(org.jboss.tools.runtime.seam.detector.test.SeamRuntimeDetectionTest): expected:<1> but was:<0>
testJBossAs70(org.jboss.tools.runtime.seam.detector.test.SeamRuntimeDetectionTest): expected:<1> but was:<0>
Tests run: 8, Failures: 3, Errors: 0, Skipped: 0
{code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-17737) org.jboss.tools.runtime.seam.detector.test.SeamRuntimeDetectionAllTests failure
by Daniel Azarov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17737?page=com.atlassian.jira.plugi... ]
Daniel Azarov updated JBIDE-17737:
----------------------------------
Attachment: org.jboss.tools.runtime.seam.detector.test.SeamRuntimeDetectionAllTests.txt
> org.jboss.tools.runtime.seam.detector.test.SeamRuntimeDetectionAllTests failure
> --------------------------------------------------------------------------------
>
> Key: JBIDE-17737
> URL: https://issues.jboss.org/browse/JBIDE-17737
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: seam2
> Affects Versions: 4.2.0.Beta3
> Reporter: Daniel Azarov
> Attachments: org.jboss.tools.runtime.seam.detector.test.SeamRuntimeDetectionAllTests.txt
>
>
> {code}
> -------------------------------------------------------
> T E S T S
> -------------------------------------------------------
> Running org.jboss.tools.runtime.seam.detector.test.SeamRuntimeDetectionAllTests
> 0
> 0
> Tests run: 8, Failures: 3, Errors: 0, Skipped: 0, Time elapsed: 0.265 sec <<< FAILURE!
> Results :
> Failed tests: testJBossAs42(org.jboss.tools.runtime.seam.detector.test.SeamRuntimeDetectionTest): expected:<1> but was:<0>
> testJBossAs51(org.jboss.tools.runtime.seam.detector.test.SeamRuntimeDetectionTest): expected:<1> but was:<0>
> testJBossAs70(org.jboss.tools.runtime.seam.detector.test.SeamRuntimeDetectionTest): expected:<1> but was:<0>
> Tests run: 8, Failures: 3, Errors: 0, Skipped: 0
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-17624) (un)checking Early Access while refreshing the connector logs an org.eclipse.swt.SWTException
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17624?page=com.atlassian.jira.plugi... ]
Snjezana Peco commented on JBIDE-17624:
---------------------------------------
The issue happens if you click the "Show Early access" action while the Central editor is refreshing the page.
The issue isn't OS specific. All you need to do is to click the action quickly.
The PR fixes the issue by disabling the "Show Early access" action (as well as "Select All"/"Deselect all" actions) during refreshing.
> (un)checking Early Access while refreshing the connector logs an org.eclipse.swt.SWTException
> ---------------------------------------------------------------------------------------------
>
> Key: JBIDE-17624
> URL: https://issues.jboss.org/browse/JBIDE-17624
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.2.0.Beta2
> Reporter: Fred Bricon
> Assignee: Snjezana Peco
> Priority: Minor
> Fix For: 4.2.0.Beta3
>
>
> In Central > Software/Update page, (un)checking Early Access while refreshing the connector logs the following exception :
> {noformat}
> org.eclipse.swt.SWTException: Graphic is disposed
> at org.eclipse.swt.SWT.error(SWT.java:4441)
> at org.eclipse.swt.SWT.error(SWT.java:4356)
> at org.eclipse.swt.SWT.error(SWT.java:4327)
> at org.eclipse.swt.graphics.Image.getBounds(Image.java:1164)
> at org.eclipse.swt.widgets.Label.computeSize(Label.java:149)
> at org.eclipse.swt.layout.GridData.computeSize(GridData.java:491)
> at org.eclipse.swt.layout.GridLayout.layout(GridLayout.java:221)
> at org.eclipse.swt.layout.GridLayout.computeSize(GridLayout.java:164)
> at org.eclipse.swt.widgets.Composite.computeSize(Composite.java:234)
> at org.eclipse.swt.layout.GridData.computeSize(GridData.java:491)
> at org.eclipse.swt.layout.GridLayout.layout(GridLayout.java:221)
> at org.eclipse.swt.layout.GridLayout.computeSize(GridLayout.java:164)
> at org.eclipse.swt.widgets.Composite.computeSize(Composite.java:234)
> at org.eclipse.swt.layout.GridData.computeSize(GridData.java:491)
> at org.eclipse.swt.layout.GridLayout.layout(GridLayout.java:221)
> at org.eclipse.swt.layout.GridLayout.computeSize(GridLayout.java:164)
> at org.eclipse.swt.widgets.Composite.computeSize(Composite.java:234)
> at org.eclipse.swt.layout.GridData.computeSize(GridData.java:491)
> at org.eclipse.swt.layout.GridLayout.layout(GridLayout.java:221)
> at org.eclipse.swt.layout.GridLayout.layout(GridLayout.java:197)
> at org.eclipse.swt.widgets.Composite.updateLayout(Composite.java:1290)
> at org.eclipse.swt.widgets.Composite.updateLayout(Composite.java:1276)
> at org.eclipse.swt.widgets.Composite.layout(Composite.java:665)
> at org.jboss.tools.central.editors.xpl.DiscoveryViewer.updateFilters(DiscoveryViewer.java:628)
> at org.jboss.tools.central.editors.SoftwarePage.handleEarlyAccessChanged(SoftwarePage.java:536)
> at org.jboss.tools.central.editors.SoftwarePage.access$8(SoftwarePage.java:486)
> at org.jboss.tools.central.editors.SoftwarePage$5.widgetSelected(SoftwarePage.java:229)
> {noformat}
> scrolledContents is checked for disposed state, but the error occurs within layout()
> {code}
> if (this.scrolledContents != null && !this.scrolledContents.isDisposed()) {
> this.scrolledContents.layout(true, true); //crashes here
> ...
> }
> {code}
> I don't know how we can prevent that
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months