November 2017 - jbosstools-issues

[JBoss JIRA] (JBIDE-25387) Missing coretests bundles on stable update site

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25387?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-25387: ------------------------------- Fix Version/s: 4.5.2.AM1 (was: 4.5.1.Final) > Missing coretests bundles on stable update site > ----------------------------------------------- > > Key: JBIDE-25387 > URL: https://issues.jboss.org/browse/JBIDE-25387 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: updatesite > Affects Versions: 4.5.1.Final > Reporter: Andrej Podhradsky > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.5.2.AM1 > > Attachments: coretests.png > > > The following update site > http://download.jboss.org/jbosstools/oxygen/stable/updates/coretests/ > is missing all coretests bundles. Note that the composite files define folder '4.5.1.Final' but no such folder exists. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25387) Missing coretests bundles on stable update site

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25387?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-25387: ------------------------------------ I believe I've fixed this [0] and the job [1] now has an extra option to re-run it based on development or stable content, rather than staging. This allows us to regen the composite update sites, including the discovery sites, when [~pleacu] releases a new IS update and forgets to copy thew jars into BOTH /stable/ and /development/. [0] https://github.com/jbdevstudio/jbdevstudio-ci/commit/9c6a82cc929c6b05e6da... [1] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > Missing coretests bundles on stable update site > ----------------------------------------------- > > Key: JBIDE-25387 > URL: https://issues.jboss.org/browse/JBIDE-25387 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: updatesite > Affects Versions: 4.5.1.Final > Reporter: Andrej Podhradsky > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.5.2.AM2 > > Attachments: coretests.png > > > The following update site > http://download.jboss.org/jbosstools/oxygen/stable/updates/coretests/ > is missing all coretests bundles. Note that the composite files define folder '4.5.1.Final' but no such folder exists. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25427) update target platform & Central to Oxygen.2

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25427?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-25427 at 11/17/17 10:03 AM: --------------------------------------------------------------- When installing 11.2.0.AM1 against Oxygen.2.RC1 (20171116-1726_eclipse-jee-oxygen-2-rc1-linux.gtk.x86_64.tar.gz), I get remediation errors, requiring that code recommenders be removed before devstudio can be installed. Need to solve this limitation (probably by updating TP to Oxygen.2 versions of recommenders). !ds11.2.0.AM1-remediation-remove-code-recommenders-Oxygen.2-install.png|thumbnail! It's also possible to end up with devstudio 11.1 installed instead of 11.2, or almost none of JBoss Tools, if you pick the wrong remediation solutions: !ds11.2.0.AM1-remediation.png|thumbnail! !jbt4.5.2.AM1-remediation.png|thumbnail! was (Author: nickboldt): When installing 11.2.0.AM1 against Oxygen.2.RC1 (20171116-1726_eclipse-jee-oxygen-2-rc1-linux.gtk.x86_64.tar.gz), I get remediation errors, requiring that code recommenders be removed before devstudio can be installed. Need to solve this limitation (probably by updating TP to Oxygen.2 versions of recommenders). !ds11.2.0.AM1-remediation-remove-code-recommenders-Oxygen.2-install.png|thumbnail! > update target platform & Central to Oxygen.2 > -------------------------------------------- > > Key: JBIDE-25427 > URL: https://issues.jboss.org/browse/JBIDE-25427 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.5.2.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.2.AM2 > > Attachments: ds11.2.0.AM1-remediation-remove-code-recommenders-Oxygen.2-install.png, ds11.2.0.AM1-remediation.png, jbt4.5.2.AM1-remediation.png > > > Switch to the latest Oxygen.2, including Jetty 9.4.7 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25427) update target platform & Central to Oxygen.2

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25427?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-25427: ------------------------------- Attachment: jbt4.5.2.AM1-remediation.png ds11.2.0.AM1-remediation.png > update target platform & Central to Oxygen.2 > -------------------------------------------- > > Key: JBIDE-25427 > URL: https://issues.jboss.org/browse/JBIDE-25427 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.5.2.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.2.AM2 > > Attachments: ds11.2.0.AM1-remediation-remove-code-recommenders-Oxygen.2-install.png, ds11.2.0.AM1-remediation.png, jbt4.5.2.AM1-remediation.png > > > Switch to the latest Oxygen.2, including Jetty 9.4.7 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25427) update target platform & Central to Oxygen.2

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25427?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-25427: ------------------------------------ When installing 11.2.0.AM1 against Oxygen.2.RC1 (20171116-1726_eclipse-jee-oxygen-2-rc1-linux.gtk.x86_64.tar.gz), I get remediation errors, requiring that code recommenders be removed before devstudio can be installed. Need to solve this limitation (probably by updating TP to Oxygen.2 versions of recommenders). !ds11.2.0.AM1-remediation-remove-code-recommenders-Oxygen.2-install.png|thumbnail! > update target platform & Central to Oxygen.2 > -------------------------------------------- > > Key: JBIDE-25427 > URL: https://issues.jboss.org/browse/JBIDE-25427 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.5.2.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.2.AM2 > > Attachments: ds11.2.0.AM1-remediation-remove-code-recommenders-Oxygen.2-install.png > > > Switch to the latest Oxygen.2, including Jetty 9.4.7 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25427) update target platform & Central to Oxygen.2

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25427?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-25427: ------------------------------- Attachment: ds11.2.0.AM1-remediation-remove-code-recommenders-Oxygen.2-install.png > update target platform & Central to Oxygen.2 > -------------------------------------------- > > Key: JBIDE-25427 > URL: https://issues.jboss.org/browse/JBIDE-25427 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.5.2.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.2.AM2 > > Attachments: ds11.2.0.AM1-remediation-remove-code-recommenders-Oxygen.2-install.png > > > Switch to the latest Oxygen.2, including Jetty 9.4.7 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4627) Unable to create a SQL server connection in new JPA project

by shailendra singh (JIRA)

shailendra singh created JBDS-4627: -------------------------------------- Summary: Unable to create a SQL server connection in new JPA project Key: JBDS-4627 URL: https://issues.jboss.org/browse/JBDS-4627 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Bug Affects Versions: 11.1.0.GA Reporter: shailendra singh Attachments: JPAProject.png Unable to create a SQL server connection in new jpa project. Its not allowing to update the properties. Attached screenshot, properties are missing. This happens when we select SQL server version >= 2012 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25333) Base New and Noteworthy for 4.5.2.AM1

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25333?page=com.atlassian.jira.plugi... ] Jeff MAURY closed JBIDE-25333. ------------------------------ Resolution: Rejected > Base New and Noteworthy for 4.5.2.AM1 > --------------------------------------------------- > > Key: JBIDE-25333 > URL: https://issues.jboss.org/browse/JBIDE-25333 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: common, foundation, usage > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Critical > Labels: task > Fix For: 4.5.2.AM1 > > > Jeff MAURY, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Base 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 Base, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Base 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-25323 #comment Create N&N for Base 4.5.2.AM1 #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 Base for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4553) Get ready for Java 9

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBDS-4553?page=com.atlassian.jira.plugin.... ] Jeff MAURY updated JBDS-4553: ----------------------------- Fix Version/s: 11.2.0.GA (was: 11.2.0.AM1) > Get ready for Java 9 > -------------------- > > Key: JBDS-4553 > URL: https://issues.jboss.org/browse/JBDS-4553 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Epic > Components: installer, platform-installer > Affects Versions: 11.1.0.AM2 > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Labels: installer, java9 > Fix For: 11.2.0.GA > > > When 11.1 will be out, Java9 will also be out. The installer refuses to accept Java9 JVM when JBDS is installed. Shouldn't we accept them now ? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25100) freemarker plugin Maven built fails due to outdated versions

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25100?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-25100: ---------------------------------- Assignee: Jeff MAURY > freemarker plugin Maven built fails due to outdated versions > ------------------------------------------------------------ > > Key: JBIDE-25100 > URL: https://issues.jboss.org/browse/JBIDE-25100 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: freemarker > Reporter: Daniel Dekany > Assignee: Jeff MAURY > Fix For: 4.5.2.AM1 > > > I have check out the master from Git, but couldn't build it. Not sure how (if at all) it succeeds on you build server. Anyway, these are the things I have changed to fix it (will send PR soon): > * Changed org.jboss.tools:parent:4.5.0.AM2-SNAPSHOT to 4.5.1.AM3-SNAPSHOT. (Otherwise it tried to download https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo..., which is HTTP 404. BTW, it still issues several warnings for not being able to retrieve the metadata, also directory of artifacts, like https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... give HTTP 500.) > > * Increased project version from 1.5.300 to 1.5.301 (or else Tycho said org.jboss.ide.eclipse.freemarker: Only qualifier changed for (o > rg.jboss.ide.eclipse.freemarker/1.5.300.v20170925-1612). "Expected to have bigger x.y.z than what is available in baseline (1.5.300.v20161214-1103)") -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 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 November 2017