July 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-25736) deprecate features from JBoss Tools with low usage / low development

by Daniel Platz (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25736?page=com.atlassian.jira.plugi... ] Daniel Platz commented on JBIDE-25736: -------------------------------------- also just noticed depracation of livereload after doing fresh install of photon. to me this is a core tools for effective JSF development under Eclipse. For plain HTML5 development, there are alternatives like browsersync so it is not a big problem. But for JSF, removing this feature will really hurt productivity. > deprecate features from JBoss Tools with low usage / low development > -------------------------------------------------------------------- > > Key: JBIDE-25736 > URL: https://issues.jboss.org/browse/JBIDE-25736 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid, browsersim, build, cdi, forge, jsf, livereload, portal-gatein, seam2, webservices > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.3.Final > > Attachments: Screenshot 2018-03-02 14.51.03.png > > > This issue is to consider *deprecating* the following parts of JBoss Tools. Suggest we mark them deprecated in feature.properties, and add/update connectors in Central to be similarly marked. > * jbosstools-portlet > * jbosstools-aerogear > * jbosstools-browsersim > * jbosstools-livereload > * {color:red}-jbosstools-webservices-{color} > * {color:red}-jbosstools-javaee-{color} > * {color:red}-jbosstools-forge-{color} > These projects could be *removed*, since they were deprecated some time ago: > * jbosstools-freemarker > * jbosstools-arquillian > For supporting arguments, see this doc (RH only, sorry): > https://docs.google.com/spreadsheets/d/1PTep1KGK2DVbmaWGwQOPhtbSsyROL_PY6... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26107) Docker New and Noteworthy for 4.6.0.Final

by Jeff Johnston (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26107?page=com.atlassian.jira.plugi... ] Jeff Johnston closed JBIDE-26107. --------------------------------- Resolution: Rejected > Docker New and Noteworthy for 4.6.0.Final > ----------------------------------------------------- > > Key: JBIDE-26107 > URL: https://issues.jboss.org/browse/JBIDE-26107 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: docker > Reporter: Jeff MAURY > Assignee: Jeff Johnston > Priority: Critical > Labels: task > Fix For: 4.6.0.Final > > > Jeff Johnston, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Docker JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for Docker, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Docker by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form... {code}JBIDE-26102 #comment Create N&N for Docker 4.6.0.Final #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for Docker for this milestone, please *reject* and *close* this issue. > ---- > If there is nothing new or noteworthy for 4.6.0.Final since the AM3 release of Docker, please *reject* and *close* this issue. The final N&N page will be aggregated from all previous N&N documents. > If you want to _add a comment to the final document_ then submit a PR to create a separate <component>-news-4.6.0.Final.adoc file here: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. > However, if you want to _replace all previous N&Ns by a *new* document_, then submit a PR to create a *new* <component>-news-4.6.0.Final.adoc file, adding: {code}page-include-previous: false{code}. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18654) run jdeps on our jars to see how dependent we are on api that might go away in Java 9, 10, 11

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18654?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-18654: ------------------------------------ I've started adding JDK 10 and 11 test jobs here: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > run jdeps on our jars to see how dependent we are on api that might go away in Java 9, 10, 11 > --------------------------------------------------------------------------------------------- > > Key: JBIDE-18654 > URL: https://issues.jboss.org/browse/JBIDE-18654 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.2.0.Final > Reporter: Max Rydahl Andersen > Assignee: Jeff MAURY > Fix For: 4.9.0.AM1 > > > Java 9 JDK team have been pinging various teams to check if they got depedency on API that is scheduled to disappear in Java 9. > There is a tool called jdeps that we can use to check for this using the -jdkinternals flag. > https://wiki.openjdk.java.net/display/JDK8/Java+Dependency+Analysis+Tool > The sooner the better we get this done as it is feedback to the Java 9 team. > If we can we should try run it on *all* jars, even eclipse ones to see what will be affected - but first of all jboss tools plugins. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25553) Cannot create Hibernate Console Configuration for projects with java 9

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25553?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-25553: ------------------------------------ Before closing, we need to verify the steps to repro no longer produce a problem: {quote} 1. Create project with java 9 2. try to create hibernate console configuration -> Error says "Classpath must be set or restored to default" 3. switch to Classpath tab, select User Entries -> Add Projects... button is disabled and java 9 project cannot be added. {quote} Might be worth testing JDK 10 and 11 EA too. > Cannot create Hibernate Console Configuration for projects with java 9 > ---------------------------------------------------------------------- > > Key: JBIDE-25553 > URL: https://issues.jboss.org/browse/JBIDE-25553 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.5.2.AM2 > Reporter: Rastislav Wagner > Assignee: Rastislav Wagner > Priority: Critical > Fix For: 4.6.0.Final > > Attachments: hibernate-jdk9.png > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25553) Cannot create Hibernate Console Configuration for projects with java 9

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25553?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-25553: ---------------------------------- Assignee: Rastislav Wagner (was: Koen Aers) > Cannot create Hibernate Console Configuration for projects with java 9 > ---------------------------------------------------------------------- > > Key: JBIDE-25553 > URL: https://issues.jboss.org/browse/JBIDE-25553 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.5.2.AM2 > Reporter: Rastislav Wagner > Assignee: Rastislav Wagner > Priority: Critical > Fix For: 4.6.0.Final > > Attachments: hibernate-jdk9.png > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4714) For JBDS 12.9.0.AM1: Prepare for 4.9.0.AM1 / 12.9.0.AM1 [installer]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4714?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4714: ---------------------------------- bump up to parent pom version = 4.9.0.AM1-SNAPSHOT > For JBDS 12.9.0.AM1: Prepare for 4.9.0.AM1 / 12.9.0.AM1 [installer] > ------------------------------------------------------------------- > > Key: JBDS-4714 > URL: https://issues.jboss.org/browse/JBDS-4714 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: installer > Reporter: Nick Boldt > Assignee: Jeff MAURY > Priority: Blocker > Labels: task > Fix For: 12.9.0.AM1 > > > For JBDS 12.9.0.AM1 [installer]: Please perform the following tasks: > > 1. Check out your existing *{color:orange}master{color}* branch: > > {code} > git checkout master > {code} > > 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.9.0.AM1-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.9.0.AM1-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.9.0.AM1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > > 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > > > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.80.1.Final > > {code} > mvn clean verify -Dtpc.version=4.80.1.Final > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.80.1.Final > > {code} > mvn clean verify -Dtpc.version=4.80.1.Final > {code} > > 5. Close (do not resolve) this JIRA when done. > > 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. > > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for installer task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4714) For JBDS 12.9.0.AM1: Prepare for 4.9.0.AM1 / 12.9.0.AM1 [installer]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4714?page=com.atlassian.jira.plugin.... ] Nick Boldt closed JBDS-4714. ---------------------------- Resolution: Done > For JBDS 12.9.0.AM1: Prepare for 4.9.0.AM1 / 12.9.0.AM1 [installer] > ------------------------------------------------------------------- > > Key: JBDS-4714 > URL: https://issues.jboss.org/browse/JBDS-4714 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: installer > Reporter: Nick Boldt > Assignee: Jeff MAURY > Priority: Blocker > Labels: task > Fix For: 12.9.0.AM1 > > > For JBDS 12.9.0.AM1 [installer]: Please perform the following tasks: > > 1. Check out your existing *{color:orange}master{color}* branch: > > {code} > git checkout master > {code} > > 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.9.0.AM1-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.9.0.AM1-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.9.0.AM1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > > 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > > > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.80.1.Final > > {code} > mvn clean verify -Dtpc.version=4.80.1.Final > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.80.1.Final > > {code} > mvn clean verify -Dtpc.version=4.80.1.Final > {code} > > 5. Close (do not resolve) this JIRA when done. > > 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. > > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for installer task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26134) For JBIDE 4.6.0.Final: Prepare for 4.6.0.Final / 12.0.0.GA [integration-tests]

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26134?page=com.atlassian.jira.plugi... ] Pavol Srna closed JBIDE-26134. ------------------------------ Resolution: Done > For JBIDE 4.6.0.Final: Prepare for 4.6.0.Final / 12.0.0.GA [integration-tests] > ------------------------------------------------------------------------------ > > Key: JBIDE-26134 > URL: https://issues.jboss.org/browse/JBIDE-26134 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests > Reporter: Nick Boldt > Assignee: Pavol Srna > Priority: Blocker > Labels: task > Fix For: 4.6.0.Final > > > For JBIDE 4.6.0.Final [integration-tests]: Please perform the following tasks: > > 1. Check out your existing *{color:orange}master{color}* branch: > > {code} > git checkout master > {code} > > 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.6.0.Final-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.6.0.Final-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.6.0.Final-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > > 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > > > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.80.0.Final-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.80.0.Final-SNAPSHOT > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.80.0.Final-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.80.0.Final-SNAPSHOT > {code} > > 5. Close (do not resolve) this JIRA when done. > > 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. > > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for integration-tests task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4696) Cannot install org.sonatype.tycho

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBDS-4696?page=com.atlassian.jira.plugin.... ] Josef Kopriva closed JBDS-4696. ------------------------------- Closing. I was not able to reproduce this. Thx [~nickboldt]. Verified in: Red Hat Developer Studio Version: 12.0.0.GA Build id: GA-v20180710-1916-B2972 Build date: 20180710-1916 > Cannot install org.sonatype.tycho > --------------------------------- > > Key: JBDS-4696 > URL: https://issues.jboss.org/browse/JBDS-4696 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: target-platform > Affects Versions: 12.0.0.AM1 > Environment: Red Hat JBoss Developer Studio > Version: 12.0.0.AM1 > Build id: AM1-v20180502-0411-B2377 > Build date: 20180502-0411 > Reporter: Josef Kopriva > Assignee: Josef Kopriva > Priority: Critical > Labels: releasework > Fix For: 12.0.0.GA > > Attachments: 4696_01.png, 4696_02.png, 4696_03.png, 4696_03b.png > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3871) installer credentials misleading/incomplete information.

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3871?page=com.atlassian.jira.plugin.... ] Denis Golovin closed JBDS-3871. ------------------------------- Resolution: Won't Fix DevSuite Installer is discontinued, closing as Won't Fix > installer credentials misleading/incomplete information. > -------------------------------------------------------- > > Key: JBDS-3871 > URL: https://issues.jboss.org/browse/JBDS-3871 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 9.1.0.Beta1 > Environment: Win 7/64 bit > Reporter: Robert Terzi > Assignee: Denis Golovin > Priority: Minor > Labels: ui > Fix For: 12.9.0.AM1 > > Attachments: screenshot-1.png > > > There are several problems a with the information on the platform installer's login screen: > # "Your developers.redhat.com credentials" is misleading, Should probably be "Your Red Hat username" to be consistent with RHDeveloper registration process. > # The register link points to the login page, not the register page. > # Registering on RHDevelopers isn't sufficient. (A registered user gets " Terms and Conditions for CDK have not been signed." > # There should probably be a link to a page on RHDev with more info/FAQ about credentials, the registration process, and obtaining a (no-cost) subscription. > The platform installer description of the credentials to use are misleading. Currently it says " Try it now by providing your developers.redhat.com credentials to get access." > Users can log into RHDevelopers via other accounts (github, linkedin, stack overflow, etc. using OAUTH). They can not log into access.redhat.com (the customer portal) or other Red Hat sites with their developer.redhat.com "credentials". > During registration on RHDevelopers, a simple developers account is created. (Note: At this point, a Red Hat username hasn't been created yet. > Currently, when the user clicks a download link that goes through RHDev download manager, their account is "upgraded", which creates a Red Hat user than can be used to log into RHCP. Terms & conditions are presented. A no-cost RHEL Developer suite subscription is added to the user's Red Hat account. > Their Red Hat username and password which could be different from the RHDeveloper credentials. They will need their Red Hat username for the CDK box to attach to their subscription. Without it the CDK box won't start up correctly as it can't download software. > Some of this is covered for external users in the No-cost RHEL Dev. Suite FAQ. http://developers.redhat.com/articles/no-cost-rhel-faq/ We might need to do a version of that for CDK and JBDS platform installer.. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 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 July 2018