[JBoss JIRA] (JBDS-3566) include AERI in JBDS
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3566?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-3566:
----------------------------------
We might be able to set up an AERI discovery/reporting site on devstudio.redhat.com, but I'm not sure how. I've sent mail to recommenders-dev(a)eclipse.org to ask, and cc:'d Max, Len, and Martin.
> include AERI in JBDS
> --------------------
>
> Key: JBDS-3566
> URL: https://issues.jboss.org/browse/JBDS-3566
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: build, target-platform
> Affects Versions: 9.1.0.Beta1, 10.0.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Attachments: error-prefs-jbds.png, error-prefs-jbt.png, error-reporting.png
>
>
> Include required bundles for AERI in JBDS. Details TBD.
> Maybe need these?
> {code}
> org.eclipse.epp.logging.aeri.feature_1.0.1.v20150913-0716
> org.eclipse.epp.logging.aeri.ide_1.0.1.v20150913-0657.jar
> org.eclipse.epp.logging.aeri.ui_1.0.1.v20150913-0716.jar
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21601) p2director install should support excluding IUs like platform fragments and executables
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21601?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-21601:
-------------------------------
Fix Version/s: 4.3.1.CR1
4.4.0.Alpha1
> p2director install should support excluding IUs like platform fragments and executables
> ---------------------------------------------------------------------------------------
>
> Key: JBIDE-21601
> URL: https://issues.jboss.org/browse/JBIDE-21601
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.3.1.CR1, 4.4.0.Alpha1
>
>
> p2director install test should exclude things like executable.feature.group and org.eclipse.equinox.launcher.*
> {code}
> 01:27:34 [p2.dir] Cannot complete the install because of a conflicting dependency.
> 01:27:34 [p2.dir] Software being installed: Eclipse Platform Launcher Executables 3.6.200.v20151113-1733 (org.eclipse.equinox.executable.feature.group 3.6.200.v20151113-1733)
> 01:27:34 [p2.dir] Software currently installed: Eclipse IDE for Java EE Developers 4.6.0.20151218-1543 (epp.package.jee 4.6.0.20151218-1543)
> 01:27:34 [p2.dir] Only one of the following can be installed at once:
> 01:27:34 [p2.dir] Equinox Launcher Linux X86 Fragment 1.1.300.v20151013-1129 (org.eclipse.equinox.launcher.gtk.linux.x86 1.1.300.v20151013-1129)
> 01:27:34 [p2.dir] Equinox Launcher Linux X86 Fragment 1.1.300.v20160105-0945 (org.eclipse.equinox.launcher.gtk.linux.x86 1.1.300.v20160105-0945)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBTIS-546) JBTIS TP - resync with latest JBDS TP
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-546?page=com.atlassian.jira.plugin.... ]
Paul Leacu closed JBTIS-546.
----------------------------
Fix Version/s: 4.3.1.Beta1-TP
Resolution: Done
Sync'd w/ latest TP.
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.3.1.Be...
This has updated jaxb/ locus and uses the 4.52.0.Beta2-SNAPSHOT JBT TP.
https://github.com/jbosstools/jbosstools-integration-stack/commit/73f1e77...
> JBTIS TP - resync with latest JBDS TP
> -------------------------------------
>
> Key: JBTIS-546
> URL: https://issues.jboss.org/browse/JBTIS-546
> Project: JBoss Tools Integration Stack
> Issue Type: Feature Request
> Components: target-platform
> Affects Versions: 4.3.1.Beta1-TP
> Reporter: Paul Leacu
> Assignee: Paul Leacu
> Fix For: 4.3.1.Beta1-TP
>
>
> *Reason:* resync with 4.50.2.Beta2-SNAPSHOT Mars jbosstools TP and locus
> *Project page/sources:*
> *Version:*
> *License and owner:* EPL
> *Original p2 repo:*
> *JBoss mirror:*
> *Include Sources:* Yes
> *Affected JBoss Tools components:* JBDSIS
> *Include in JBDS:* Yes (JBDSIS)
> *Type of dependency:* distribution
> *List of bundles added/removed:*
> {code}
> < org.eclipse.bpel.common.wsdl.source [1.0.5.Final]
> < org.eclipse.bpel.feature.source.feature.jar [1.0.5.Final]
> < org.eclipse.bpel.common.ui [1.0.5.Final]
> < org.eclipse.bpel.apache.ode.runtime [1.0.5.Final]
> < org.eclipse.bpel.common.feature.feature.jar [1.0.5.Final]
> < org.eclipse.bpel.apache.ode.deploy.model [1.0.5.Final]
> < org.eclipse.bpel.ui [1.0.5.Final]
> < org.eclipse.bpel.model [1.0.5.Final]
> < org.eclipse.bpel.cheatsheet [1.0.5.Final]
> < org.eclipse.bpel.wsil.model [1.0.5.Final]
> < org.eclipse.bpel.apache.ode.runtime.feature.feature.jar [1.0.5.Final]
> < org.eclipse.bpel.help.source [1.0.5.Final]
> < org.eclipse.bpel.runtimes.source [1.0.5.Final]
> < org.eclipse.bpel.apache.ode.runtime.feature.source.feature.group [1.0.5.Final]
> < org.eclipse.bpel.help [1.0.5.Final]
> < org.eclipse.bpel.xpath10.source [1.0.5.Final]
> < org.eclipse.bpel.common.feature.source.feature.group [1.0.5.Final]
> < org.eclipse.bpel.validator [1.0.5.Final]
> < org.eclipse.bpel.validator.source [1.0.5.Final]
> < org.eclipse.bpel.feature.feature.group [1.0.5.Final]
> < org.eclipse.bpel.apache.ode.deploy.ui.source [1.0.5.Final]
> < org.eclipse.bpel.feature.feature.jar [1.0.5.Final]
> < org.eclipse.bpel.common.feature.source.feature.jar [1.0.5.Final]
> < org.eclipse.bpel.runtimes [1.0.5.Final]
> < org.eclipse.bpel.common.wsdl [1.0.5.Final]
> < org.eclipse.bpel.common.model.source [1.0.5.Final]
> < org.eclipse.bpel.apache.ode.deploy.ui [1.0.5.Final]
> < org.eclipse.bpel.xpath10 [1.0.5.Final]
> < org.eclipse.bpel.common.model [1.0.5.Final]
> < org.eclipse.bpel.cheatsheet.source [1.0.5.Final]
> < org.eclipse.bpel.common.feature.feature.group [1.0.5.Final]
> < org.eclipse.bpel.ui.source [1.0.5.Final]
> < org.eclipse.bpel.common.ui.source [1.0.5.Final]
> < org.eclipse.bpel.apache.ode.deploy.model.source [1.0.5.Final]
> < org.eclipse.bpel.feature.source.feature.group [1.0.5.Final]
> < org.eclipse.bpel.apache.ode.runtime.source [1.0.5.Final]
> < org.eclipse.bpel.model.source [1.0.5.Final]
> < org.eclipse.bpel.apache.ode.runtime.feature.source.feature.jar [1.0.5.Final]
> < org.eclipse.bpel.apache.ode.runtime.feature.feature.group [1.0.5.Final]
> < org.eclipse.bpel.wsil.model.source [1.0.5.Final]
> > org.eclipse.bpel.xpath10 [1.0.5.Final-v20160115-1558]
> > org.eclipse.bpel.runtimes [1.0.5.Final-v20160115-1558]
> > org.eclipse.bpel.apache.ode.runtime.source [1.0.5.Final-v20160115-1558]
> > org.eclipse.bpel.common.feature.source.feature.jar [1.0.5.Final-v20160115-1558]
> > org.eclipse.bpel.runtimes.source [1.0.5.Final-v20160115-1558]
> > org.eclipse.bpel.wsil.model [1.0.5.Final-v20160115-1558]
> > org.eclipse.bpel.wsil.model.source [1.0.5.Final-v20160115-1558]
> > org.eclipse.bpel.validator [1.0.5.Final-v20160115-1558]
> > org.eclipse.bpel.ui [1.0.5.Final-v20160115-1558]
> > org.eclipse.bpel.common.model.source [1.0.5.Final-v20160115-1558]
> > org.eclipse.bpel.common.wsdl.source [1.0.5.Final-v20160115-1558]
> > org.eclipse.bpel.xpath10.source [1.0.5.Final-v20160115-1558]
> > org.eclipse.bpel.apache.ode.deploy.ui [1.0.5.Final-v20160115-1558]
> > org.eclipse.bpel.apache.ode.deploy.ui.source [1.0.5.Final-v20160115-1558]
> > org.eclipse.bpel.feature.feature.jar [1.0.5.Final-v20160115-1558]
> > org.eclipse.bpel.cheatsheet [1.0.5.Final-v20160115-1558]
> > org.eclipse.bpel.common.ui.source [1.0.5.Final-v20160115-1558]
> > org.eclipse.bpel.common.ui [1.0.5.Final-v20160115-1558]
> > org.eclipse.bpel.common.feature.feature.jar [1.0.5.Final-v20160115-1558]
> > org.eclipse.bpel.help [1.0.5.Final-v20160115-1558]
> > org.eclipse.bpel.apache.ode.runtime.feature.source.feature.group [1.0.5.Final-v20160115-1558]
> > org.eclipse.bpel.feature.feature.group [1.0.5.Final-v20160115-1558]
> > org.eclipse.bpel.ui.source [1.0.5.Final-v20160115-1558]
> > org.eclipse.bpel.feature.source.feature.jar [1.0.5.Final-v20160115-1558]
> > org.eclipse.bpel.apache.ode.runtime.feature.feature.jar [1.0.5.Final-v20160115-1558]
> > org.eclipse.bpel.help.source [1.0.5.Final-v20160115-1558]
> > org.eclipse.bpel.apache.ode.runtime.feature.feature.group [1.0.5.Final-v20160115-1558]
> > org.eclipse.bpel.common.feature.source.feature.group [1.0.5.Final-v20160115-1558]
> > org.eclipse.bpel.model.source [1.0.5.Final-v20160115-1558]
> > org.eclipse.bpel.apache.ode.runtime.feature.source.feature.jar [1.0.5.Final-v20160115-1558]
> > org.eclipse.bpel.validator.source [1.0.5.Final-v20160115-1558]
> > org.eclipse.bpel.apache.ode.runtime [1.0.5.Final-v20160115-1558]
> > org.eclipse.bpel.common.wsdl [1.0.5.Final-v20160115-1558]
> > org.eclipse.bpel.apache.ode.deploy.model.source [1.0.5.Final-v20160115-1558]
> > org.eclipse.bpel.feature.source.feature.group [1.0.5.Final-v20160115-1558]
> > org.eclipse.bpel.common.feature.feature.group [1.0.5.Final-v20160115-1558]
> > org.eclipse.bpel.cheatsheet.source [1.0.5.Final-v20160115-1558]
> > org.eclipse.bpel.common.model [1.0.5.Final-v20160115-1558]
> > org.eclipse.bpel.apache.ode.deploy.model [1.0.5.Final-v20160115-1558]
> > org.eclipse.bpel.model [1.0.5.Final-v20160115-1558]
> === Summary ===
> file:///home/pleacu/git-clone/jbosstools-integration-stack.orig/target-platform/target/target-platform.target.repo contains 40 unique IUs
> file:///home/pleacu/git-clone/jbosstools-integration-stack/target-platform/target/target-platform.target.repo contains 40 unique IUs
> < org.eclipse.m2e.editor.xml [1.6.2.20150902-0002]
> < org.eclipse.m2e.scm [1.6.2.20150902-0002]
> < org.eclipse.m2e.tests.common [1.6.2.20150902-0002]
> < org.eclipse.uml2.uml.feature.jar [5.1.0.v20150906-1225]
> < org.eclipse.m2e.feature.feature.group [1.6.2.20150902-0002]
> < org.eclipse.uml2.common.feature.jar [2.1.0.v20150906-1225]
> < org.eclipse.uml2.common.edit.feature.jar [2.1.0.v20150906-1225]
> < org.eclipse.m2e.jdt.ui [1.6.2.20150902-0002]
> < org.eclipse.m2e.maven.runtime.slf4j.simple [1.6.2.20150902-0001]
> < org.eclipse.uml2.uml.edit.feature.group [5.1.1.v20150906-1225]
> < org.eclipse.m2e.maven.runtime [1.6.2.20150902-0001]
> < org.eclipse.m2e.core [1.6.2.20150902-0002]
> < org.maven.ide.eclipse [1.6.2.20150902-0002]
> < org.eclipse.uml2.types [2.0.0.v20150906-1225]
> < org.eclipse.m2e.archetype.common [1.6.2.20150902-0001]
> < org.eclipse.uml2.uml.editor [5.1.0.v20150906-1225]
> < org.eclipse.m2e.feature.feature.jar [1.6.2.20150902-0002]
> < org.eclipse.m2e.discovery [1.6.2.20150902-0002]
> < org.eclipse.uml2.uml [5.1.0.v20150906-1225]
> < org.eclipse.m2e.profiles.ui [1.6.2.20150902-0002]
> < org.eclipse.uml2.uml.feature.group [5.1.0.v20150906-1225]
> < org.eclipse.m2e.editor [1.6.2.20150902-0002]
> < org.eclipse.m2e.maven.indexer [1.6.2.20150902-0001]
> < org.eclipse.m2e.profiles.core [1.6.2.20150902-0002]
> < org.eclipse.uml2.common [2.1.0.v20150906-1225]
> < org.eclipse.m2e.lifecyclemapping.defaults [1.6.2.20150902-0002]
> < org.eclipse.uml2.uml.resources [5.1.0.v20150906-1225]
> < org.eclipse.m2e.jdt [1.6.2.20150902-0002]
> < org.eclipse.m2e.refactoring [1.6.2.20150902-0002]
> < org.eclipse.uml2.uml.ecore.exporter [3.0.0.v20150906-1225]
> < org.eclipse.uml2.codegen.ecore.ui.feature.group [2.1.0.v20150906-1225]
> < org.eclipse.uml2.common.feature.group [2.1.0.v20150906-1225]
> < org.eclipse.m2e.launching [1.6.2.20150902-0002]
> < org.jboss.tools.locus.jsonschema2pojo.jsonschema2pojo-core [0.4.13.v20150709-1710]
> < org.apache.ant [1.9.4.v201504302020]
> < org.eclipse.uml2.codegen.ecore.ui [2.1.0.v20150906-1225]
> < org.eclipse.uml2 [5.0.0.v20150906-1225]
> < org.eclipse.m2e.model.edit [1.6.2.20150902-0002]
> < org.eclipse.uml2.ant [1.0.0.v20150906-1225]
> < org.eclipse.m2e.core.ui [1.6.2.20150902-0002]
> < org.eclipse.uml2.codegen.ecore [2.1.0.v20150906-1225]
> < org.eclipse.uml2.uml.edit.feature.jar [5.1.1.v20150906-1225]
> < org.eclipse.uml2.uml.ecore.importer [3.0.0.v20150906-1225]
> < org.eclipse.uml2.codegen.ecore.ui.feature.jar [2.1.0.v20150906-1225]
> < org.eclipse.uml2.common.edit [2.1.0.v20150906-1225]
> < org.eclipse.uml2.feature.group [5.1.1.v20150906-1225]
> < org.eclipse.m2e.workspace.cli [0.3.1]
> < org.eclipse.uml2.uml.edit [5.1.1.v20150906-1225]
> < org.eclipse.uml2.uml.profile.standard [1.0.100.v20150906-1225]
> < org.eclipse.uml2.uml.validation [5.0.0.v20150906-1225]
> < org.eclipse.uml2.feature.jar [5.1.1.v20150906-1225]
> < org.eclipse.uml2.common.edit.feature.group [2.1.0.v20150906-1225]
> > org.apache.ant [1.9.6.v201510161327]
> > org.eclipse.uml2.uml.validation [5.0.0.v20160118-1129]
> > org.eclipse.uml2.uml.ecore.exporter [3.0.0.v20160118-1129]
> > org.eclipse.uml2.uml.profile.standard [1.0.100.v20160118-1129]
> > org.eclipse.uml2.uml.ecore.importer [3.0.2.v20160118-1129]
> > org.jboss.tools.locus.jaxb-core [2.2.7.v20160125-1950]
> > org.eclipse.uml2.common.edit.feature.group [2.1.0.v20160118-1129]
> > org.eclipse.uml2.uml.edit [5.1.1.v20160118-1129]
> > org.eclipse.uml2.uml [5.1.2.v20160118-1129]
> > org.eclipse.uml2.feature.jar [5.1.2.v20160118-1129]
> > org.eclipse.uml2.common.feature.group [2.1.0.v20160118-1129]
> > org.eclipse.uml2.common.edit.feature.jar [2.1.0.v20160118-1129]
> > org.eclipse.uml2.uml.feature.group [5.1.2.v20160118-1129]
> > org.eclipse.uml2.feature.group [5.1.2.v20160118-1129]
> > org.jboss.tools.locus.jaxb-xjc [2.2.7.v20160125-1950]
> > org.eclipse.uml2.ant [1.0.0.v20160118-1129]
> > org.eclipse.uml2.uml.edit.feature.group [5.1.1.v20160118-1129]
> > org.eclipse.uml2 [5.0.0.v20160118-1129]
> > org.jboss.tools.locus.jsonschema2pojo.jsonschema2pojo-core [0.4.13.v20160122-1745]
> > org.eclipse.uml2.codegen.ecore [2.1.2.v20160118-1129]
> > org.eclipse.uml2.uml.feature.jar [5.1.2.v20160118-1129]
> > org.eclipse.uml2.types [2.0.0.v20160118-1129]
> > org.eclipse.uml2.common.edit [2.1.0.v20160118-1129]
> > org.eclipse.uml2.common.feature.jar [2.1.0.v20160118-1129]
> > org.eclipse.uml2.codegen.ecore.ui.feature.jar [2.1.2.v20160118-1129]
> > org.eclipse.uml2.uml.resources [5.1.0.v20160118-1129]
> > org.eclipse.uml2.uml.edit.feature.jar [5.1.1.v20160118-1129]
> > org.eclipse.uml2.codegen.ecore.ui.feature.group [2.1.2.v20160118-1129]
> > org.eclipse.uml2.uml.editor [5.1.0.v20160118-1129]
> > org.eclipse.uml2.common [2.1.0.v20160118-1129]
> > org.jboss.tools.locus.jaxb-impl [2.2.7.v20160113-1915]
> > org.eclipse.uml2.codegen.ecore.ui [2.1.0.v20160118-1129]
> === Summary ===
> file:///home/pleacu/git-clone/jbosstools-integration-stack.orig/target-platform/target/target-platform-ea.target.repo contains 52 unique IUs
> file:///home/pleacu/git-clone/jbosstools-integration-stack/target-platform/target/target-platform-ea.target.repo contains 32 unique IUs
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-20587) IClient calls are executed in UI thread
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20587?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-20587:
------------------------------------------
[~rawagner] do you have concrete pointers? We're trying hard NOT to have remoting executed in the UI thread, so this would definitely be a unintended flaw.
> IClient calls are executed in UI thread
> ---------------------------------------
>
> Key: JBIDE-20587
> URL: https://issues.jboss.org/browse/JBIDE-20587
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Beta2
> Reporter: Rastislav Wagner
> Assignee: Jeff Cantrill
> Priority: Critical
> Fix For: 4.3.1.CR1
>
>
> org.jboss.tools.openshift.core.connection.Connection is using UI thread while executing calls to IClient. Some of these calls may take longer time (for example getting logs) thus should not be running in UI thread.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBDS-3579) Fuse archetype catalog cannot be added with JBDS 9
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBDS-3579?page=com.atlassian.jira.plugin.... ]
Fred Bricon updated JBDS-3579:
------------------------------
Fix Version/s: 10.0.0.Alpha1
> Fuse archetype catalog cannot be added with JBDS 9
> --------------------------------------------------
>
> Key: JBDS-3579
> URL: https://issues.jboss.org/browse/JBDS-3579
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: maven
> Affects Versions: 9.0.0.GA
> Reporter: Keith Babo
> Assignee: Fred Bricon
> Fix For: 10.0.0.Alpha1
>
>
> When adding the Fuse Integration Services archetype catalog to JBDS 9, the IDE reports that the catalog is empty. This works in Eclipse and I've heard reports that it also works in earlier versions of JBDS (although I have not confirmed this personally).
> Archetype catalog in question:
> https://repo.fusesource.com/nexus/content/groups/public/io/fabric8/archet...
> Steps to reproduce:
> - Preferences -> Maven -> Archetypes -> Add Remote Catalog
> - Add URL above for Catalog File
> - Click Verify ... and you get the message "Remote catalog is empty"
> - Click Finish and try to use the catalog from the New Maven Project wizard and the message is "No archetypes available for this catalog."
> Impact here is that Fuse customers looking to use Fuse on OpenShift cannot use JBDS to create new projects using our Maven archetypes (the primary means of getting started).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21529) Properties view: Columns of OpenShift resources in tabbed properties are too wide
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21529?page=com.atlassian.jira.plugi... ]
Jeff Cantrill reassigned JBIDE-21529:
-------------------------------------
Assignee: Viacheslav Kabanovich
Resolution: Done
Merged into master, cherry-picked into 4.3.x
> Properties view: Columns of OpenShift resources in tabbed properties are too wide
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-21529
> URL: https://issues.jboss.org/browse/JBIDE-21529
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Marián Labuda
> Assignee: Viacheslav Kabanovich
> Labels: properties
> Fix For: 4.3.1.CR1
>
>
> In new tabbed properties overview of OpenShift resources there is a table listing selected OpenShift resource, e.g. pods, builds etc. Columns in this table are too wide by default and their width exceed few times content of the column. It makes necessary to scroll or resize columns, what make it less user friendly. Columns could fit more to length of content of the column by default.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21589) JBDS crash sometimes when opening Show in Console on a project
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21589?page=com.atlassian.jira.plugi... ]
Marián Labuda commented on JBIDE-21589:
---------------------------------------
Unfortunately, today I was not so lucky to reproduce this issue in any way (several times tried showing in console, javadoc view, autocompletion. I have bluejeans installed so its highly probable that is the cause of those crashes.
> JBDS crash sometimes when opening Show in Console on a project
> --------------------------------------------------------------
>
> Key: JBIDE-21589
> URL: https://issues.jboss.org/browse/JBIDE-21589
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Environment: Fedora 22
> openjdk 8.0_71-b15
> Reporter: Marián Labuda
> Priority: Critical
> Labels: openshift_v3
> Attachments: log.txt
>
>
> Crash log
> {code}
> #
> # A fatal error has been detected by the Java Runtime Environment:
> #
> # SIGSEGV (0xb) at pc=0x00007f0cfe0bbcaf, pid=13526, tid=139697620236032
> #
> # JRE version: OpenJDK Runtime Environment (8.0_71-b15) (build 1.8.0_71-b15)
> # Java VM: OpenJDK 64-Bit Server VM (25.71-b15 mixed mode linux-amd64 compressed oops)
> # Problematic frame:
> # C [libwebkitgtk-3.0.so.0+0x47bcaf]
> #
> # Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
> #
> # An error report file with more information is saved as:
> # /home/mlabuda/testing/jbds/910Beta2stable/hs_err_pid13526.log
> #
> # If you would like to submit a bug report, please visit:
> # http://bugreport.java.com/bugreport/crash.jsp
> # The crash happened outside the Java Virtual Machine in native code.
> # See problematic frame for where to report the bug.
> #
> {code}
> For more thread dump see attached log.txt
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21476) Credential Composite not working when user overrides password for single-use
by Radim Hopp (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21476?page=com.atlassian.jira.plugi... ]
Radim Hopp closed JBIDE-21476.
------------------------------
Verified in JBDS 9.0.0.Beta2a. Closing.
> Credential Composite not working when user overrides password for single-use
> ----------------------------------------------------------------------------
>
> Key: JBIDE-21476
> URL: https://issues.jboss.org/browse/JBIDE-21476
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common/jst/core, runtime-detection
> Affects Versions: 4.3.1.Beta2
> Environment: JBDS 9.1.0.Beta2 nightly (17.1.2016)
> Reporter: Radim Hopp
> Assignee: Rob Stryker
> Labels: respin-a
> Fix For: 4.3.1.Beta2
>
>
> When selecting Username on TaskWizardPage in DownloadRuntimesWizard, password is pre-fileld, when selected username has password set. However changing this password has no effect.
> I think that best solution is to have password textbox enabled only when username does not have password configured in credentials framework.
> On auth fail, message (probably with link to Credentials preferences) should be displayed to show user where is the correct place for changing that password.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21607) "Show In -> Browsersim" on EJB module should be disabled
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21607?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov reassigned JBIDE-21607:
----------------------------------------------
Assignee: Konstantin Marmalyukov
> "Show In -> Browsersim" on EJB module should be disabled
> --------------------------------------------------------
>
> Key: JBIDE-21607
> URL: https://issues.jboss.org/browse/JBIDE-21607
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: browsersim
> Affects Versions: 4.3.1.Beta2
> Reporter: Martin Malina
> Assignee: Konstantin Marmalyukov
> Fix For: 4.4.0.Alpha1
>
>
> This is a followup of JBIDE-21138 . When you deploy an ejb module, all the items in Server View under Show in are enabled, but they don't do anything. They should be disabled.
> Rob did his part for Show in Server, but he says separate JIRAs are needed in other components.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month