[JBoss JIRA] (JBDS-3328) generate/edit jboss modules content for easily deployment/config of jdbc driver
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-3328?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen reassigned JBDS-3328:
-----------------------------------------
Assignee: Alexey Kazakov (was: Max Rydahl Andersen)
> generate/edit jboss modules content for easily deployment/config of jdbc driver
> -------------------------------------------------------------------------------
>
> Key: JBDS-3328
> URL: https://issues.jboss.org/browse/JBDS-3328
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Enhancement
> Components: server
> Reporter: Max Rydahl Andersen
> Assignee: Alexey Kazakov
> Fix For: 9.0.0.Beta1
>
>
> in EAP7-56 its asked:
> "I can easily generate and deploy a JBoss Module from existing jars including JDBC Drivers and shared libraries. (Tooling to automatically generate module.xml and related artifacts by scanning classes from a library jar file, or pom.xml if provided e.g real life use case: creating modules for JDBC Type 4 Drivers )"
> this would be nice to have and linked with our datasource wizards.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBDS-3377) Random "not responding" message when installing from central
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-3377?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen updated JBDS-3377:
--------------------------------------
Fix Version/s: 9.0.0.Beta1
> Random "not responding" message when installing from central
> ------------------------------------------------------------
>
> Key: JBDS-3377
> URL: https://issues.jboss.org/browse/JBDS-3377
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: central, ui/branding
> Affects Versions: 8.1.0.CR1
> Environment: Fedora 20 64-bit, OpenJDK 1.7.0_75
> Reporter: Jan Richter
> Assignee: Mickael Istria
> Priority: Minor
> Fix For: 9.0.0.Beta1
>
>
> Trying to install all from central sometimes causes the "not responding" dialog to pop up while the "Calculating Dependencies" dialog is active. The app is still responding when the dialog opens though.
> I cannot find a particular pattern to this, it looks completely random.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBDS-3377) Random "not responding" message when installing from central
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-3377?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen reassigned JBDS-3377:
-----------------------------------------
Assignee: Mickael Istria
> Random "not responding" message when installing from central
> ------------------------------------------------------------
>
> Key: JBDS-3377
> URL: https://issues.jboss.org/browse/JBDS-3377
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: central, ui/branding
> Affects Versions: 8.1.0.CR1
> Environment: Fedora 20 64-bit, OpenJDK 1.7.0_75
> Reporter: Jan Richter
> Assignee: Mickael Istria
> Priority: Minor
> Fix For: 9.0.0.Beta1
>
>
> Trying to install all from central sometimes causes the "not responding" dialog to pop up while the "Calculating Dependencies" dialog is active. The app is still responding when the dialog opens though.
> I cannot find a particular pattern to this, it looks completely random.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-15291) xulrunner under 64bit Linux produce "NSSUTIL_3.13 not found" and blocks marketplace, m2e connector discovery ...
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15291?page=com.atlassian.jira.plugi... ]
Ilya Buziuk closed JBIDE-15291.
-------------------------------
Resolution: Cannot Reproduce Bug
> xulrunner under 64bit Linux produce "NSSUTIL_3.13 not found" and blocks marketplace, m2e connector discovery ...
> ------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-15291
> URL: https://issues.jboss.org/browse/JBIDE-15291
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: visual-page-editor-core, xulrunner
> Affects Versions: 4.1.0.Final
> Environment: Linux 3.8.13-gentoo #1 SMP Sun Jun 23 23:34:36 CEST 2013 x86_64 Intel(R) Core(TM) i7-2720QM CPU @ 2.20GHz GenuineIntel GNU/Linux
> IcedTea JDK 7.2.4.1
> eclipse-standard-kepler-R-linux-gtk-x86_64.tar.gz
> Reporter: Jochen Buchholz
> Assignee: Ilya Buziuk
> Priority: Critical
> Fix For: 4.3.x
>
> Attachments: .log, click-on-jbosscentral-button.png, frozen-marketplace.png, gentoo.png, internal-error1.png, m2e-connectors.png
>
>
> I installed the eclipse standard kepler and go to market place. I choose JBoss developer studio 7.0.0 GA and install it via marketplace. After the restart I choose File->Import->Maven->"checkout Maven Projects from SCM" and click on the "Find out more SCM connectors in the m2e Marketplace. I got the error: "Failed to discover all connectors."
> I cant Use the Marketplace anymore, because he is frozen while load the content.
> In the error log I found this line:
> Caused by: java.io.IOException: /mnt/usb/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)
> like in the old issue JBIDE-10628 reported also by me
> Developer Studio is unusable under 64bit Linux.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-15291) xulrunner under 64bit Linux produce "NSSUTIL_3.13 not found" and blocks marketplace, m2e connector discovery ...
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15291?page=com.atlassian.jira.plugi... ]
Ilya Buziuk commented on JBIDE-15291:
-------------------------------------
Not able to reproduce the issue on RHEL 7 x64 against OpenJDK 1.7.0_79. Works fine against both gtk 2 & gtk 3.
Closing as cannot reproduce. Please, feel free to reopen if you still facing the issue.
> xulrunner under 64bit Linux produce "NSSUTIL_3.13 not found" and blocks marketplace, m2e connector discovery ...
> ------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-15291
> URL: https://issues.jboss.org/browse/JBIDE-15291
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: visual-page-editor-core, xulrunner
> Affects Versions: 4.1.0.Final
> Environment: Linux 3.8.13-gentoo #1 SMP Sun Jun 23 23:34:36 CEST 2013 x86_64 Intel(R) Core(TM) i7-2720QM CPU @ 2.20GHz GenuineIntel GNU/Linux
> IcedTea JDK 7.2.4.1
> eclipse-standard-kepler-R-linux-gtk-x86_64.tar.gz
> Reporter: Jochen Buchholz
> Assignee: Ilya Buziuk
> Priority: Critical
> Fix For: 4.3.x
>
> Attachments: .log, click-on-jbosscentral-button.png, frozen-marketplace.png, gentoo.png, internal-error1.png, m2e-connectors.png
>
>
> I installed the eclipse standard kepler and go to market place. I choose JBoss developer studio 7.0.0 GA and install it via marketplace. After the restart I choose File->Import->Maven->"checkout Maven Projects from SCM" and click on the "Find out more SCM connectors in the m2e Marketplace. I got the error: "Failed to discover all connectors."
> I cant Use the Marketplace anymore, because he is frozen while load the content.
> In the error log I found this line:
> Caused by: java.io.IOException: /mnt/usb/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)
> like in the old issue JBIDE-10628 reported also by me
> Developer Studio is unusable under 64bit Linux.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-18772) Include publish.sh in parent pom as versioned maven dependency
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18772?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-18772:
---------------------------------------------
[~mickael_istria] maybe put that in separate issue instead of letting this stay open ?
[~nickboldt] your examples still tells me that we dont have cleaned up our publishing if we need so many different steps but that is separate from this jira.
only question I got left is how can I use this publish.sh and have it work on completely different system - i.e my local running servers for testing ? which parameters shuold I set ?
> Include publish.sh in parent pom as versioned maven dependency
> --------------------------------------------------------------
>
> Key: JBIDE-18772
> URL: https://issues.jboss.org/browse/JBIDE-18772
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build
> Reporter: Max Rydahl Andersen
> Assignee: Mickael Istria
> Priority: Critical
> Fix For: 4.3.0.Beta1
>
> Attachments: jbds-publish-to-snapshots.png
>
>
> instead of relying to publish.sh being on master, we should use a versioned publish.sh (or maybe even mojo) that the build then uses.
> suggestion:
> publish.sh (or mojo) gets released to our maven repo, use it in the pom.xml to perform publishing.
> What this helps with is:
> a) can do changes to publish mechanism without affecting every past builds.
> b) more movable build system
> c) isolated testing possible
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-17284) OpenJDK seem to have issues with SSL/TLS handshakes when using URLConnection
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17284?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen closed JBIDE-17284.
---------------------------------------
Resolution: Cannot Reproduce Bug
after several attempts we can not reproduce this.
It might have been an issue in past space and time but seems java vm's and OS's have been updated since and we are not hitting this issue anymore.
If anyone are able to reproduce it please provide exact OS, java and steps to reproduce. Thanks!
> 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: upstream, xulrunner
> Affects Versions: 4.2.0.Final
> Reporter: Max Rydahl Andersen
> Assignee: Ilya Buziuk
> Priority: Blocker
> Fix For: 4.3.0.Beta1
>
> Attachments: jbds-via-html5-vpe.png, 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.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-19291) "Unable to execute early startup code ..." exception after starup.
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19291?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-19291:
---------------------------------------
So that means we will see the fix in Beta1 or later depending on when it gets to a new version of Mars that we will use, right? So let's see in Beta1.
> "Unable to execute early startup code ..." exception after starup.
> ------------------------------------------------------------------
>
> Key: JBIDE-19291
> URL: https://issues.jboss.org/browse/JBIDE-19291
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.3.0.Alpha1
> Environment: JBDS 9.0.0.Alpha1
> Reporter: Radim Hopp
> Assignee: Rob Stryker
> Fix For: 4.3.0.Beta1
>
>
> After startup in error log there is this error:
> {noformat:title=Unable to execute early startup code for the org.eclipse.ui.IStartup extension contributed by the 'org.jboss.ide.eclipse.as.ui' plug-in.}
> org.eclipse.core.runtime.CoreException: Executable extension definition for "class" not found.
> at org.eclipse.core.internal.registry.ConfigurationElement.throwException(ConfigurationElement.java:62)
> at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:222)
> at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:55)
> at org.eclipse.ui.internal.WorkbenchPlugin$1.run(WorkbenchPlugin.java:293)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:52)
> at org.eclipse.ui.internal.WorkbenchPlugin.createExtension(WorkbenchPlugin.java:288)
> at org.eclipse.ui.internal.EarlyStartupRunnable.getExecutableExtension(EarlyStartupRunnable.java:102)
> at org.eclipse.ui.internal.EarlyStartupRunnable.run(EarlyStartupRunnable.java:54)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.Workbench$56.run(Workbench.java:2801)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months