May 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-4359) Two "Spring" folders in "New" wizard

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBDS-4359?page=com.atlassian.jira.plugin.... ] Lukáš Valach commented on JBDS-4359: ------------------------------------ Both "Import Spring Getting Started Content" and "Spring Getting Started Content" are pointing to same dialog, so "Spring Getting Started Content" should be removed. > Two "Spring" folders in "New" wizard > ------------------------------------ > > Key: JBDS-4359 > URL: https://issues.jboss.org/browse/JBDS-4359 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: central > Affects Versions: 10.4.0.AM3 > Environment: Devstudio 10.4.0.AM3-v20170406-1058-B390 (installed form jar installer) > Reporter: Lukáš Valach > Priority: Minor > Fix For: 11.0.0.AM1 > > Attachments: Spring_in_New_wizard_2017-04-11_10-52-33.png > > > I noticed that after installation of "Spring IDE" from Red Hat Central -> Software/Update there are two folders named "Spring" in "New" wizard dialog (File -> New -> Other...). > !Spring_in_New_wizard_2017-04-11_10-52-33.png|thumbnail! > I think that these folders should be merged into one folder. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24388) merge integration stack content into discovery site CI builds

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24388?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24388: ------------------------------- Fix Version/s: 4.4.4.Final 4.5.0.AM1 > merge integration stack content into discovery site CI builds > ------------------------------------------------------------- > > Key: JBIDE-24388 > URL: https://issues.jboss.org/browse/JBIDE-24388 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, central-update, integration-platform > Affects Versions: 4.4.4.Final, 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.4.Final, 4.5.0.AM1 > > > Today, we only merge IS content into the discovery site builds during staging and release. > But since this merge operation is now 100% scripted, we could trigger it for all CI builds too. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24388) merge integration stack content into discovery site CI builds

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24388?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-24388: ---------------------------------- Assignee: Nick Boldt > merge integration stack content into discovery site CI builds > ------------------------------------------------------------- > > Key: JBIDE-24388 > URL: https://issues.jboss.org/browse/JBIDE-24388 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, central-update, integration-platform > Affects Versions: 4.4.4.Final, 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.4.Final, 4.5.0.AM1 > > > Today, we only merge IS content into the discovery site builds during staging and release. > But since this merge operation is now 100% scripted, we could trigger it for all CI builds too. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24388) merge integration stack content into discovery site CI builds

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-24388: ---------------------------------- Summary: merge integration stack content into discovery site CI builds Key: JBIDE-24388 URL: https://issues.jboss.org/browse/JBIDE-24388 Project: Tools (JBoss Tools) Issue Type: Bug Components: build, central-update, integration-platform Affects Versions: 4.4.4.Final, 4.5.0.AM1 Reporter: Nick Boldt Today, we only merge IS content into the discovery site builds during staging and release. But since this merge operation is now 100% scripted, we could trigger it for all CI builds too. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1100) Teiid Designer - remove unnecessary feature pull of org.jboss.tools.foundation.security.linux.feature

by Paul Leacu (JIRA)

Paul Leacu created JBTIS-1100: --------------------------------- Summary: Teiid Designer - remove unnecessary feature pull of org.jboss.tools.foundation.security.linux.feature Key: JBTIS-1100 URL: https://issues.jboss.org/browse/JBTIS-1100 Project: JBoss Tools Integration Stack Issue Type: Task Components: teiid Affects Versions: 10.3.0.GA Reporter: Paul Leacu Assignee: Paul Leacu Fix For: 10.4.0.CR1 The teiid-designer feature is causing the wrong org.jboss.tools.foundation.security.linux.feature to be pulled into the Integration Stack. It's accessible via the IS target platform - just need to remove it from the TD feature.xml. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24256) run cdk with reddeer2

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24256?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-24256: ---------------------------------- Git Pull Request: https://github.com/rawagner/jbosstools-openshift/pull/1, https://github.com/jbosstools/jbosstools-integration-tests/pull/1816 (was: https://github.com/rawagner/jbosstools-openshift/pull/1) > run cdk with reddeer2 > --------------------- > > Key: JBIDE-24256 > URL: https://issues.jboss.org/browse/JBIDE-24256 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: integration-tests > Reporter: Rastislav Wagner > Assignee: Ondrej Dockal > Fix For: 4.4.4.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24387) Implement cleanup methods for OS requirements

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24387?page=com.atlassian.jira.plugi... ] Jan Richter updated JBIDE-24387: -------------------------------- Sprint: devex #131 April 2017 > Implement cleanup methods for OS requirements > --------------------------------------------- > > Key: JBIDE-24387 > URL: https://issues.jboss.org/browse/JBIDE-24387 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: integration-tests > Reporter: Jan Richter > Assignee: Jan Richter > Fix For: 4.4.4.Final > > > Reddeer requirements should be able to clean after themselves. Implement cleanup for OS requirements so it can be used from the annotation rather than afterclass. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24387) Implement cleanup methods for OS requirements

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24387?page=com.atlassian.jira.plugi... ] Jan Richter updated JBIDE-24387: -------------------------------- Project: Tools (JBoss Tools) (was: Red Hat JBoss Developer Studio (devstudio)) Key: JBIDE-24387 (was: JBDS-4374) Docs QE Status: (was: NEW) Component/s: integration-tests (was: integration-tests) (was: openshift) Affects Version/s: (was: 10.4.0.AM3) Fix Version/s: 4.4.4.Final (was: 10.4.0.GA) > Implement cleanup methods for OS requirements > --------------------------------------------- > > Key: JBIDE-24387 > URL: https://issues.jboss.org/browse/JBIDE-24387 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: integration-tests > Reporter: Jan Richter > Assignee: Jan Richter > Fix For: 4.4.4.Final > > > Reddeer requirements should be able to clean after themselves. Implement cleanup for OS requirements so it can be used from the annotation rather than afterclass. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23784) WF 11 / EAP 7.1 Incremental MGMT publishing

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23784?page=com.atlassian.jira.plugi... ] Radim Hopp commented on JBIDE-23784: ------------------------------------ EDIT: Deleting one by one does not work either. Let's say I have three projects deployed. When I try to undeploy one, from the server log it seems that it is stopping all three deployments, removing them and adding&starting them all again. So trying to remove one project results in all projects being redeployed and the one project just disappears from servers view. > WF 11 / EAP 7.1 Incremental MGMT publishing > ------------------------------------------- > > Key: JBIDE-23784 > URL: https://issues.jboss.org/browse/JBIDE-23784 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: server > Reporter: Rob Stryker > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.4.4.Final, 4.5.0.AM2 > > > WF 11 and EAP 7.1 will have support for management deployment in an incremental fashion. > WF 11 nightly builds for the pre-alpha are here: https://developer.jboss.org/thread/224262 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24350) Forge New and Noteworthy for 4.4.4.Final

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24350?page=com.atlassian.jira.plugi... ] George Gastaldi commented on JBIDE-24350: ----------------------------------------- Hi Jeff, yes I'm aware of this :) Thanks for the reminder, but no changes are planned in Forge this far > Forge New and Noteworthy for 4.4.4.Final > ----------------------------------------------------- > > Key: JBIDE-24350 > URL: https://issues.jboss.org/browse/JBIDE-24350 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: forge > Reporter: Jeff MAURY > Assignee: George Gastaldi > Priority: Critical > > George Gastaldi, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Forge 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 Forge, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Forge 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-24345 #comment Create N&N for Forge 4.4.4.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 Forge for this milestone, please *reject* and *close* this issue. > ---- > If there is nothing new or noteworthy for 4.4.4.Final since the AM3 release of Forge, 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.4.4.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.4.4.Final.adoc file, adding: {code}page-include-previous: false{code}. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 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 May 2017