August 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24708) Hibernate New and Noteworthy for 4.5.0.Final

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24708?page=com.atlassian.jira.plugi... ] Jeff MAURY closed JBIDE-24708. ------------------------------ Resolution: Done > Hibernate New and Noteworthy for 4.5.0.Final > ----------------------------------------------------- > > Key: JBIDE-24708 > URL: https://issues.jboss.org/browse/JBIDE-24708 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: hibernate > Reporter: Jeff MAURY > Assignee: Koen Aers > Priority: Critical > Fix For: 4.5.0.Final > > > Koen Aers, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Hibernate 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 Hibernate, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Hibernate 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-24706 #comment Create N&N for Hibernate 4.5.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 Hibernate for this milestone, please *reject* and *close* this issue. > ---- > If there is nothing new or noteworthy for 4.5.0.Final since the AM3 release of Hibernate, 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.5.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.5.0.Final.adoc file, adding: {code}page-include-previous: false{code}. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24802) Connection wizard: Lots of unnecessary errors in Error Log when filling oc location, Finish enabled even if oc location empty

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24802?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24802: ------------------------------------- Summary: Connection wizard: Lots of unnecessary errors in Error Log when filling oc location, Finish enabled even if oc location empty (was: Connection wizard: Lots of unnecessary errors in Error Log when filling oc location) > Connection wizard: Lots of unnecessary errors in Error Log when filling oc location, Finish enabled even if oc location empty > ----------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-24802 > URL: https://issues.jboss.org/browse/JBIDE-24802 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.0.Final > Reporter: Radim Hopp > Assignee: Rob Stryker > Priority: Minor > Labels: connection_wizard, openshift_v3 > Fix For: 4.5.x > > Attachments: Spectacle.F10835.png > > > On-the-fly validation of "oc location" field in ConnectionWizardPage puts lot of errors into error log. I think that the on the fly validation should not be so agressive. > !Spectacle.F10835.png! > And another thing: Is there any reason why Finish is enabled even when there is not valid value in oc location field? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24802) Connection wizard: Lots of unnecessary errors in Error Log when filling oc location

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24802?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24802: ------------------------------------- Labels: connection_wizard openshift_v3 (was: ) > Connection wizard: Lots of unnecessary errors in Error Log when filling oc location > ----------------------------------------------------------------------------------- > > Key: JBIDE-24802 > URL: https://issues.jboss.org/browse/JBIDE-24802 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.0.Final > Reporter: Radim Hopp > Assignee: Rob Stryker > Priority: Minor > Labels: connection_wizard, openshift_v3 > Fix For: 4.5.x > > Attachments: Spectacle.F10835.png > > > On-the-fly validation of "oc location" field in ConnectionWizardPage puts lot of errors into error log. I think that the on the fly validation should not be so agressive. > !Spectacle.F10835.png! > And another thing: Is there any reason why Finish is enabled even when there is not valid value in oc location field? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24802) Lots of unnecessary errors in Error Log when filling oc location in ConnectionWizard

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24802?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24802: ------------------------------------- Fix Version/s: 4.5.x > Lots of unnecessary errors in Error Log when filling oc location in ConnectionWizard > ------------------------------------------------------------------------------------ > > Key: JBIDE-24802 > URL: https://issues.jboss.org/browse/JBIDE-24802 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.0.Final > Reporter: Radim Hopp > Priority: Minor > Labels: connection_wizard, openshift_v3 > Fix For: 4.5.x > > Attachments: Spectacle.F10835.png > > > On-the-fly validation of "oc location" field in ConnectionWizardPage puts lot of errors into error log. I think that the on the fly validation should not be so agressive. > !Spectacle.F10835.png! > And another thing: Is there any reason why Finish is enabled even when there is not valid value in oc location field? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24802) Lots of unnecessary errors in Error Log when filling oc location in ConnectionWizard

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24802?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-24802: ---------------------------------------- Assignee: Rob Stryker > Lots of unnecessary errors in Error Log when filling oc location in ConnectionWizard > ------------------------------------------------------------------------------------ > > Key: JBIDE-24802 > URL: https://issues.jboss.org/browse/JBIDE-24802 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.0.Final > Reporter: Radim Hopp > Assignee: Rob Stryker > Priority: Minor > Labels: connection_wizard, openshift_v3 > Fix For: 4.5.x > > Attachments: Spectacle.F10835.png > > > On-the-fly validation of "oc location" field in ConnectionWizardPage puts lot of errors into error log. I think that the on the fly validation should not be so agressive. > !Spectacle.F10835.png! > And another thing: Is there any reason why Finish is enabled even when there is not valid value in oc location field? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24802) Connection wizard: Lots of unnecessary errors in Error Log when filling oc location

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24802?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24802: ------------------------------------- Summary: Connection wizard: Lots of unnecessary errors in Error Log when filling oc location (was: Lots of unnecessary errors in Error Log when filling oc location in ConnectionWizard) > Connection wizard: Lots of unnecessary errors in Error Log when filling oc location > ----------------------------------------------------------------------------------- > > Key: JBIDE-24802 > URL: https://issues.jboss.org/browse/JBIDE-24802 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.0.Final > Reporter: Radim Hopp > Assignee: Rob Stryker > Priority: Minor > Labels: connection_wizard, openshift_v3 > Fix For: 4.5.x > > Attachments: Spectacle.F10835.png > > > On-the-fly validation of "oc location" field in ConnectionWizardPage puts lot of errors into error log. I think that the on the fly validation should not be so agressive. > !Spectacle.F10835.png! > And another thing: Is there any reason why Finish is enabled even when there is not valid value in oc location field? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24746) Move Integration Stack-based Target Platform to JBoss Tools-based Target Platform for SAP Tooling

by Tomáš Sedmík (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24746?page=com.atlassian.jira.plugi... ] Tomáš Sedmík closed JBIDE-24746. -------------------------------- verified - 4.5.0.Final > Move Integration Stack-based Target Platform to JBoss Tools-based Target Platform for SAP Tooling > ------------------------------------------------------------------------------------------------- > > Key: JBIDE-24746 > URL: https://issues.jboss.org/browse/JBIDE-24746 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: fusetools-extras > Reporter: Aurélien Pupier > Assignee: Aurélien Pupier > Priority: Blocker > Fix For: 4.5.0.Final > > > the SAP Tooling still contains Integration Stack Target Platform bits -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24690) For JBIDE 4.5.0.Final: Prepare for 4.5.0.Final / 11.0.0.GA [fusetools-extras]

by Tomáš Sedmík (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24690?page=com.atlassian.jira.plugi... ] Tomáš Sedmík closed JBIDE-24690. -------------------------------- verified - 4.5.0.Final > For JBIDE 4.5.0.Final: Prepare for 4.5.0.Final / 11.0.0.GA [fusetools-extras] > ----------------------------------------------------------------------------- > > Key: JBIDE-24690 > URL: https://issues.jboss.org/browse/JBIDE-24690 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: fusetools-extras > Reporter: Nick Boldt > Assignee: Aurélien Pupier > Priority: Blocker > Labels: task > Fix For: 4.5.0.Final > > > For JBIDE 4.5.0.Final [fusetools-extras]: 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.5.0.Final-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.5.0.Final-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.5.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.70.0.AM1-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.70.0.AM1-SNAPSHOT > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.70.0.AM1-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.70.0.AM1-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 fusetools-extras task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24289) Update JBoss Tools features page to better promote Fuse Tooling (not in Integration Stack anymore)

by Tomáš Sedmík (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24289?page=com.atlassian.jira.plugi... ] Tomáš Sedmík closed JBIDE-24289. -------------------------------- verified > Update JBoss Tools features page to better promote Fuse Tooling (not in Integration Stack anymore) > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-24289 > URL: https://issues.jboss.org/browse/JBIDE-24289 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: fusetools, website > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Lars Heinemann > Fix For: 4.5.0.Final > > > Once Fuse Tooling is in JBT, we'll have to update http://tools.jboss.org/features/index.html to reflect that fact. > See https://github.com/jbosstools/jbosstools-website/blob/master/features/apa... for source of the page to update. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24703) Remove Integration Stack related target platform from Fuse Tooling codebase

by Tomáš Sedmík (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24703?page=com.atlassian.jira.plugi... ] Tomáš Sedmík closed JBIDE-24703. -------------------------------- verified > Remove Integration Stack related target platform from Fuse Tooling codebase > --------------------------------------------------------------------------- > > Key: JBIDE-24703 > URL: https://issues.jboss.org/browse/JBIDE-24703 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: fusetools > Reporter: Aurélien Pupier > Assignee: Aurélien Pupier > Fix For: 4.5.0.Final > > > The Tp ued when being in Integration Stack is still available in the source code. it is using SNAPSHOT values and is blocking the correct build of FINAL-SNAPSHOT version -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 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 2017