August 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-17808) Identify which installed IUs are from Early Access vs. supported/tested versions

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17808?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-17808: ---------------------------------------- [~dgolovin] I'd like to get this merged before code freeze. Can you please review and merge it if you agree? No need to go much into usability details for this iteration, what's more interesting is to review the mechanism. > Identify which installed IUs are from Early Access vs. supported/tested versions > -------------------------------------------------------------------------------- > > Key: JBIDE-17808 > URL: https://issues.jboss.org/browse/JBIDE-17808 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central > Reporter: Nick Boldt > Assignee: Mickael Istria > Labels: documentation > Fix For: 4.2.0.CR1 > > Attachments: JBIDE17808.jpeg > > > [~maxandersen] brought up a good point on a call today: > we have no way from within JBDS of identifying which installed IUs were installed from Early Access vs. those what were installed from Central or another "supported" location. > Thus we need some sort of UI to list installed IUs that are "Early Access". > This could be... (brainstorming now): > * a text file with the list of things installed from Early Access (features and plugins) > * a set of asterisks added to the Help > About dialogs when browsing for installed features / plugins > * a way to filter the plugin view (Help > About) to show only EA content (or exclude it) > * ... ? -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3002) JBDS 7.1.1 installer contains jars signed by GTECyberTrust, which may not be installed on all linux systems

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3002?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3002: -------------------------------- Priority: Blocker (was: Major) > JBDS 7.1.1 installer contains jars signed by GTECyberTrust, which may not be installed on all linux systems > ----------------------------------------------------------------------------------------------------------- > > Key: JBDS-3002 > URL: https://issues.jboss.org/browse/JBDS-3002 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: installer, updatesite > Affects Versions: 7.1.1.GA > Reporter: Max Rydahl Andersen > Assignee: Denis Golovin > Priority: Blocker > Fix For: 8.0.0.CR1 > > > We have jars in JBDS 7.1.1.GA which were signed using GTECyberTrust. Some linux installs do not include this root cert, so when installing, p2 rejects the cert: > {code}One or more certificates rejected. Cannot proceed with installation.{code} > Full details: https://community.jboss.org/message/866868 > *Platform details:* > {code} > Debian Jessie 64 bit > $ uname -a: > Linux Name 3.13-1-amd64 #1 SMP Debian 3.13.7-1 (2014-03-25) x86_64 GNU/Linux > $ java -version > java version "1.7.0_51" > OpenJDK Runtime Environment (IcedTea 2.4.5) (7u51-2.4.5-2) > OpenJDK 64-Bit Server VM (build 24.51-b03, mixed mode) > {code} > Note that Debian 8.0 "Jessie" is not yet released nor has a date for release been announced [0]. The latest stable Debian [1] is 7.4 "Wheezy", released on Feb 8, 2014. [2] The description for "testing" releases like Jessie is "Security updates are irregular and unreliable." [3] So... I don't think we support this OS yet. :) > [0] http://www.debian.org/releases/jessie/ > [1] http://www.debian.org/releases/ > [2] http://www.debian.org/releases/wheezy/ > [3] https://release.debian.org/ > *Steps to repro on the above platform:* > 1. Downloaded jbdevstudio-product-eap-universal-7.1.1.GA-v20140314-2145-B688.jar > 2. Ran java -jar jbdevstudio-product-eap-universal-7.1.1.GA-v20140314-2145-B688.jar stuck to the defaults and clicked thru > 3. Install failed with an error re certificates not being trusted > 4. Log message in ~/jbdevstudio/studio/p2/director/configuration/1396752621141.log as follows: > !ENTRY org.eclipse.equinox.p2.engine 8 0 2014-04-06 08:21:42.061 > !MESSAGE One or more certificates rejected. Cannot proceed with installation. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3012) JBDS 7.1.1 installer contains jars signed by GTECyberTrust, which may not be installed on all linux systems

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3012?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3012: -------------------------------- Fix Version/s: (was: 8.0.0.CR1) > JBDS 7.1.1 installer contains jars signed by GTECyberTrust, which may not be installed on all linux systems > ----------------------------------------------------------------------------------------------------------- > > Key: JBDS-3012 > URL: https://issues.jboss.org/browse/JBDS-3012 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: installer, updatesite > Affects Versions: 7.1.1.GA > Reporter: Max Rydahl Andersen > Assignee: Denis Golovin > Fix For: 7.1.x > > > We have jars in JBDS 7.1.1.GA which were signed using GTECyberTrust. Some linux installs do not include this root cert, so when installing, p2 rejects the cert: > {code}One or more certificates rejected. Cannot proceed with installation.{code} > Full details: https://community.jboss.org/message/866868 > *Platform details:* > {code} > Debian Jessie 64 bit > $ uname -a: > Linux Name 3.13-1-amd64 #1 SMP Debian 3.13.7-1 (2014-03-25) x86_64 GNU/Linux > $ java -version > java version "1.7.0_51" > OpenJDK Runtime Environment (IcedTea 2.4.5) (7u51-2.4.5-2) > OpenJDK 64-Bit Server VM (build 24.51-b03, mixed mode) > {code} > Note that Debian 8.0 "Jessie" is not yet released nor has a date for release been announced [0]. The latest stable Debian [1] is 7.4 "Wheezy", released on Feb 8, 2014. [2] The description for "testing" releases like Jessie is "Security updates are irregular and unreliable." [3] So... I don't think we support this OS yet. :) > [0] http://www.debian.org/releases/jessie/ > [1] http://www.debian.org/releases/ > [2] http://www.debian.org/releases/wheezy/ > [3] https://release.debian.org/ > *Steps to repro on the above platform:* > 1. Downloaded jbdevstudio-product-eap-universal-7.1.1.GA-v20140314-2145-B688.jar > 2. Ran java -jar jbdevstudio-product-eap-universal-7.1.1.GA-v20140314-2145-B688.jar stuck to the defaults and clicked thru > 3. Install failed with an error re certificates not being trusted > 4. Log message in ~/jbdevstudio/studio/p2/director/configuration/1396752621141.log as follows: > !ENTRY org.eclipse.equinox.p2.engine 8 0 2014-04-06 08:21:42.061 > !MESSAGE One or more certificates rejected. Cannot proceed with installation. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3012) JBDS 7.1.1 installer contains jars signed by GTECyberTrust, which may not be installed on all linux systems

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3012?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3012: -------------------------------- Fix Version/s: 7.1.x > JBDS 7.1.1 installer contains jars signed by GTECyberTrust, which may not be installed on all linux systems > ----------------------------------------------------------------------------------------------------------- > > Key: JBDS-3012 > URL: https://issues.jboss.org/browse/JBDS-3012 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: installer, updatesite > Affects Versions: 7.1.1.GA > Reporter: Max Rydahl Andersen > Assignee: Denis Golovin > Fix For: 7.1.x, 8.0.0.CR1 > > > We have jars in JBDS 7.1.1.GA which were signed using GTECyberTrust. Some linux installs do not include this root cert, so when installing, p2 rejects the cert: > {code}One or more certificates rejected. Cannot proceed with installation.{code} > Full details: https://community.jboss.org/message/866868 > *Platform details:* > {code} > Debian Jessie 64 bit > $ uname -a: > Linux Name 3.13-1-amd64 #1 SMP Debian 3.13.7-1 (2014-03-25) x86_64 GNU/Linux > $ java -version > java version "1.7.0_51" > OpenJDK Runtime Environment (IcedTea 2.4.5) (7u51-2.4.5-2) > OpenJDK 64-Bit Server VM (build 24.51-b03, mixed mode) > {code} > Note that Debian 8.0 "Jessie" is not yet released nor has a date for release been announced [0]. The latest stable Debian [1] is 7.4 "Wheezy", released on Feb 8, 2014. [2] The description for "testing" releases like Jessie is "Security updates are irregular and unreliable." [3] So... I don't think we support this OS yet. :) > [0] http://www.debian.org/releases/jessie/ > [1] http://www.debian.org/releases/ > [2] http://www.debian.org/releases/wheezy/ > [3] https://release.debian.org/ > *Steps to repro on the above platform:* > 1. Downloaded jbdevstudio-product-eap-universal-7.1.1.GA-v20140314-2145-B688.jar > 2. Ran java -jar jbdevstudio-product-eap-universal-7.1.1.GA-v20140314-2145-B688.jar stuck to the defaults and clicked thru > 3. Install failed with an error re certificates not being trusted > 4. Log message in ~/jbdevstudio/studio/p2/director/configuration/1396752621141.log as follows: > !ENTRY org.eclipse.equinox.p2.engine 8 0 2014-04-06 08:21:42.061 > !MESSAGE One or more certificates rejected. Cannot proceed with installation. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18131) Split the org.jboss.tools.common.validation plugin in 'core' + 'ui'

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18131?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-18131: ----------------------------------- Fix Version/s: 4.3.x > Split the org.jboss.tools.common.validation plugin in 'core' + 'ui' > ------------------------------------------------------------------- > > Key: JBIDE-18131 > URL: https://issues.jboss.org/browse/JBIDE-18131 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: common/jst/core > Affects Versions: 4.2.0.Beta3 > Reporter: Xavier Coulon > Fix For: 4.3.x > > > IMHO, it would make sense to split the {{org.jboss.tools.common.validation}} plugin in two separate ones: {{core}} + {{ui}}: > - the {{core}} part would deal with performing the validation (based on the WST Validation Framework) > - the {{ui}} part would deal for the preference pages and configuration. > ATM, the CDI validation is performed in the {{org.jboss.tools.cdi.core}} plugin, but this drags a log of _.ui_ dependencies, which is somehow wrong. > OTOH, the JAX-RS validation is performed in the {{org.jboss.tools.ws.jaxrs.ui}} plugin to avoid having _*.ui_ dependencies in the {{org.jboss.tools.ws.jaxrs.core}} plugin, but this is somehow wrong, too (I had to move the {{marker}} declaration in the {{org.jboss.tools.ws.jaxrs.core}} plugin to be able to remove all markers when the JAX-RS support is removed from a project, whatever the way it is removed (nature, facet, etc.) > Can we discuss about that change for JBoss Tools 4.3 ? -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18131) Split the org.jboss.tools.common.validation plugin in 'core' + 'ui'

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18131?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-18131: -------------------------------------- Assignee: Alexey Kazakov > Split the org.jboss.tools.common.validation plugin in 'core' + 'ui' > ------------------------------------------------------------------- > > Key: JBIDE-18131 > URL: https://issues.jboss.org/browse/JBIDE-18131 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: common/jst/core > Affects Versions: 4.2.0.Beta3 > Reporter: Xavier Coulon > Assignee: Alexey Kazakov > Fix For: 4.3.x > > > IMHO, it would make sense to split the {{org.jboss.tools.common.validation}} plugin in two separate ones: {{core}} + {{ui}}: > - the {{core}} part would deal with performing the validation (based on the WST Validation Framework) > - the {{ui}} part would deal for the preference pages and configuration. > ATM, the CDI validation is performed in the {{org.jboss.tools.cdi.core}} plugin, but this drags a log of _.ui_ dependencies, which is somehow wrong. > OTOH, the JAX-RS validation is performed in the {{org.jboss.tools.ws.jaxrs.ui}} plugin to avoid having _*.ui_ dependencies in the {{org.jboss.tools.ws.jaxrs.core}} plugin, but this is somehow wrong, too (I had to move the {{marker}} declaration in the {{org.jboss.tools.ws.jaxrs.core}} plugin to be able to remove all markers when the JAX-RS support is removed from a project, whatever the way it is removed (nature, facet, etc.) > Can we discuss about that change for JBoss Tools 4.3 ? -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17683) When running using Cmd-4 in Eclipse, log the actual forge commands used to an Eclipse console

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17683?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-17683: ------------------------------ Fix Version/s: 4.3.x (was: 4.2.0.CR1) > When running using Cmd-4 in Eclipse, log the actual forge commands used to an Eclipse console > --------------------------------------------------------------------------------------------- > > Key: JBIDE-17683 > URL: https://issues.jboss.org/browse/JBIDE-17683 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: forge > Reporter: Pete Muir > Assignee: George Gastaldi > Priority: Minor > Fix For: 4.3.x > > > It would be great to log all Forge commands that Cmd-4 executes to an eclipse console > Allow this log to be exported to a .fsh file -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16915) Provide help command in Forge2 console

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16915?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-16915: ------------------------------ Fix Version/s: 4.2.x (was: 4.2.0.CR1) > Provide help command in Forge2 console > -------------------------------------- > > Key: JBIDE-16915 > URL: https://issues.jboss.org/browse/JBIDE-16915 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: forge > Affects Versions: 4.2.0.Beta1 > Reporter: Pavol Srna > Assignee: Lincoln Baxter III > Priority: Minor > Fix For: 4.2.x > > > It would be very handy to have some help command available in Forge2 console similar as it is in Forge1. It is very hard especially for new comers to start using forge2 console without any help provided. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18137) Update Thym release on TP

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18137?page=com.atlassian.jira.plugi... ] Gorkem Ercan commented on JBIDE-18137: -------------------------------------- JBIDE-18136 is just reported.. So far I was not able to reproduce it with the snapshot, That is the only one that I can think of that may need a fix for CR1. > Update Thym release on TP > ------------------------- > > Key: JBIDE-18137 > URL: https://issues.jboss.org/browse/JBIDE-18137 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: target-platform, upstream > Affects Versions: 4.2.0.Beta3 > Reporter: Gorkem Ercan > Assignee: Mickael Istria > Priority: Blocker > Fix For: 4.2.0.CR1 > > > *Reason:* Update Eclipse Thym to pickup fixes to JBDS issues > *License and owner:* Eclipse > *Original p2 repo:* http://download.eclipse.org/thym/snapshots > *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/thym/0.1.0-SNAP... > *Sources:* https://github.com/eclipse/thym > *Affected projects:* jbosstools-aerogear > *Include in JBDS:* YES > *Type of dependency:* build > *List of bundles added/removed:* TODO -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14375) Forge should reuse proxy settings from Eclipse

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14375?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-14375: ------------------------------ Fix Version/s: 4.2.x (was: 4.2.0.CR1) > Forge should reuse proxy settings from Eclipse > ---------------------------------------------- > > Key: JBIDE-14375 > URL: https://issues.jboss.org/browse/JBIDE-14375 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: forge > Affects Versions: 4.1.0.Alpha2 > Reporter: George Gastaldi > Assignee: Koen Aers > Fix For: 4.2.x > > > Forge when running in eclipse should use pre-configured eclipse proxy settings. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues August 2014