January 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3191) Improve the way we switch between development and GA

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3191?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3191: ----------------------------- Fix Version/s: 9.0.0.Alpha1 (was: 8.1.0.GA) > Improve the way we switch between development and GA > ---------------------------------------------------- > > Key: JBDS-3191 > URL: https://issues.jboss.org/browse/JBDS-3191 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: build > Reporter: Mickael Istria > Assignee: Nick Boldt > Fix For: 9.0.0.Alpha1 > > > JBDS-3190 has shown that there are too many changes to perform when willing to create a GA candidate, and it's almost certain that we'll forever forget to change one or some of them when switching between GA and development stream. > We need to improve that. > Changes are necessary in: > * features/com.jboss.devstudio.core/feature/p2.inf > * site/associate.properties > * results/pom.xml > As an alternative, I suggest that the final site be ALWAYS added to the referenced site, even if it's empty. This has no cost for build nor user, and this would simplify a few things here and there. > Also, instead of a p2.inf, we could think a a "startup" extension that would add reference to development site in case qualifier for the feature doesn't contain GA. > The property to the "current site" (GA or development) could be factorized in JBDS parent pom. so that both results/pom.xml and site/pom.xml could use it (instead of associateSites.properties). > CC [~nickboldt] [~maxandersen] -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3191) Improve the way we switch between development and GA

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3191?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3191: ---------------------------------- This depends on JBDS-3208 so I've moved it to 9.0.0.Alpha1. > Improve the way we switch between development and GA > ---------------------------------------------------- > > Key: JBDS-3191 > URL: https://issues.jboss.org/browse/JBDS-3191 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: build > Reporter: Mickael Istria > Assignee: Nick Boldt > Fix For: 9.0.0.Alpha1 > > > JBDS-3190 has shown that there are too many changes to perform when willing to create a GA candidate, and it's almost certain that we'll forever forget to change one or some of them when switching between GA and development stream. > We need to improve that. > Changes are necessary in: > * features/com.jboss.devstudio.core/feature/p2.inf > * site/associate.properties > * results/pom.xml > As an alternative, I suggest that the final site be ALWAYS added to the referenced site, even if it's empty. This has no cost for build nor user, and this would simplify a few things here and there. > Also, instead of a p2.inf, we could think a a "startup" extension that would add reference to development site in case qualifier for the feature doesn't contain GA. > The property to the "current site" (GA or development) could be factorized in JBDS parent pom. so that both results/pom.xml and site/pom.xml could use it (instead of associateSites.properties). > CC [~nickboldt] [~maxandersen] -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3191) Improve the way we switch between development and GA

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3191?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3191: ----------------------------- Target Release: 9.0.0.GA (was: 8.0.1.GA) > Improve the way we switch between development and GA > ---------------------------------------------------- > > Key: JBDS-3191 > URL: https://issues.jboss.org/browse/JBDS-3191 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: build > Reporter: Mickael Istria > Assignee: Nick Boldt > Fix For: 9.0.0.Alpha1 > > > JBDS-3190 has shown that there are too many changes to perform when willing to create a GA candidate, and it's almost certain that we'll forever forget to change one or some of them when switching between GA and development stream. > We need to improve that. > Changes are necessary in: > * features/com.jboss.devstudio.core/feature/p2.inf > * site/associate.properties > * results/pom.xml > As an alternative, I suggest that the final site be ALWAYS added to the referenced site, even if it's empty. This has no cost for build nor user, and this would simplify a few things here and there. > Also, instead of a p2.inf, we could think a a "startup" extension that would add reference to development site in case qualifier for the feature doesn't contain GA. > The property to the "current site" (GA or development) could be factorized in JBDS parent pom. so that both results/pom.xml and site/pom.xml could use it (instead of associateSites.properties). > CC [~nickboldt] [~maxandersen] -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3289) JBoss Central proxy wizards need to recognize early access.

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3289?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-3289: ------------------------------------- attribute or tag still have to be kept in sync, could we just check if wtzard requires EA features to be installed and show the dialog about EA Eanblement? if answer is Yes then Enable Early Access and go forward with installation. That would keep everything the same as it is but make user aware. > JBoss Central proxy wizards need to recognize early access. > ----------------------------------------------------------- > > Key: JBDS-3289 > URL: https://issues.jboss.org/browse/JBDS-3289 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central > Affects Versions: 8.0.2.GA > Reporter: Paul Leacu > Assignee: Fred Bricon > Priority: Blocker > Fix For: 8.0.2.GA > > Attachments: ea1.png > > > Using a JBoss Central proxy wizard that references an early access feature will install that feature correctly even if the "Early Access Enabled" checkbox is unchecked. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18723) Binary deployment from current JBDS state

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18723?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-18723: ------------------------------------------ [~bdecoste] Hey Bill, can you check with your customer if this feature request is still important please? We plan to focus all efforts on the v3 tooling for June and only implement in v2 what's strictly required. > Binary deployment from current JBDS state > ----------------------------------------- > > Key: JBIDE-18723 > URL: https://issues.jboss.org/browse/JBIDE-18723 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.2.0.Final > Reporter: William DeCoste > Fix For: 4.3.x > > > Be able to create a deployment snapshot (tar.gz) from the current JBDS state (war, ear, standalone.xml, markers, etc) without having to download a snapshot from a pre-existing app/gear. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19016) UI Wizards should default Resource<?> UIInput types to support selecting a File OR Directory

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19016?page=com.atlassian.jira.plugi... ] Lincoln Baxter III updated JBIDE-19016: --------------------------------------- Project: Tools (JBoss Tools) (was: Forge) Key: JBIDE-19016 (was: FORGE-2183) Issue Type: Enhancement (was: Feature Request) Affects Version/s: 4.2.1.Final (was: 2.13.0.Final) Component/s: forge (was: UI - Eclipse) (was: UI - IntelliJ IDEA) (was: UI - API) (was: UI - NetBeans) Fix Version/s: (was: 2.x Future) > UI Wizards should default Resource<?> UIInput types to support selecting a File OR Directory > -------------------------------------------------------------------------------------------- > > Key: JBIDE-19016 > URL: https://issues.jboss.org/browse/JBIDE-19016 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: forge > Affects Versions: 4.2.1.Final > Reporter: Lincoln Baxter III > > There is currently no way to hint to the IDE to allow an input to select a file OR directory in Eclipse. I assume this will also be problematic in other IDEs. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18824) Server adapter: Remove replicated start-, stop-, restart-actions, use default actions instead

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18824?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-18824: ------------------------------------- Summary: Server adapter: Remove replicated start-, stop-, restart-actions, use default actions instead (was: Server adapter: Remove replicated actions, use default actions instead) > Server adapter: Remove replicated start-, stop-, restart-actions, use default actions instead > --------------------------------------------------------------------------------------------- > > Key: JBIDE-18824 > URL: https://issues.jboss.org/browse/JBIDE-18824 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.2.1.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.3.x > > Attachments: duplicate-application-actions.png > > > In JBIDE-11903 we added Start and Stop to the Explorer and Server adapter. In the server adapter we already have default items for start, stop and restart. We should remove our items from the OpenShift submenu and use the default actions instead: > !duplicate-application-actions.png! -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15609) versionwatch should ignore when there's a folder & jar which are identical

by Jiri Peterka (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15609?page=com.atlassian.jira.plugi... ] Jiri Peterka updated JBIDE-15609: --------------------------------- Git Pull Request: https://github.com/jbdevstudio/jbdevstudio-qa/pull/10, https://github.com/jbdevstudio/jbdevstudio-qa/pull/11, https://github.com/jbdevstudio/jbdevstudio-qa/pull/31 (was: https://github.com/jbdevstudio/jbdevstudio-qa/pull/10, https://github.com/jbdevstudio/jbdevstudio-qa/pull/11) Deep Jar MD5 archive checking implemented (v0.4), PR sent > versionwatch should ignore when there's a folder & jar which are identical > -------------------------------------------------------------------------- > > Key: JBIDE-15609 > URL: https://issues.jboss.org/browse/JBIDE-15609 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build, qa > Affects Versions: 4.1.1.Alpha2 > Reporter: Nick Boldt > Assignee: Jiri Peterka > Priority: Optional > Fix For: 4.3.0.Alpha1 > > > A while ago I added a facility to jar up feature and plugin folders so they could have their md5 sums compared. > Now, the vwatch tool complains when there's a folder and a jar present. > Two possible solutions to this come to mind: > a) ignore this - do not report as *{color:red}a problem{color}* > b) whenever a folder is jarred up, delete the source folder, so the above condition cannot occur -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3163) change publishing process so that JBDS staging builds go to devstudio.redhat.com instead of www.qa server

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3163?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-3163: -------------------------------------- Fix Version/s: 8.1.0.GA (was: 8.0.2.GA) > change publishing process so that JBDS staging builds go to devstudio.redhat.com instead of www.qa server > --------------------------------------------------------------------------------------------------------- > > Key: JBDS-3163 > URL: https://issues.jboss.org/browse/JBDS-3163 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build > Affects Versions: 8.0.0.CR1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 8.1.0.GA, 9.0.0.Alpha1 > > > To simplify release/publishing process, we ought to start publishing nightlies and builds staged for QE onto devstudio.redhat.com (filemgmt) instead of the internal www.qa box. This will also allow us to use nightly URLs in ide-config.properties. > See https://github.com/jbosstools/jbosstools-download.jboss.org/pull/409/files for a bad solution to this problem. > Better solution is to move that content onto the new filemgmt instance and update promote.sh to push to the new location. > --- > After much discussion it's been decided that: > * we can push only the nightly/staging update sites automatically onto devstudio.redhat.com. > * Installers will remain internal-only until they're released and available on CSP and www.jboss.org -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3163) change publishing process so that JBDS staging builds go to devstudio.redhat.com instead of www.qa server

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3163?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3163: ------------------------------------------- 8.0.2 is minimal - thus moving to 8.1 > change publishing process so that JBDS staging builds go to devstudio.redhat.com instead of www.qa server > --------------------------------------------------------------------------------------------------------- > > Key: JBDS-3163 > URL: https://issues.jboss.org/browse/JBDS-3163 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build > Affects Versions: 8.0.0.CR1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 8.1.0.GA, 9.0.0.Alpha1 > > > To simplify release/publishing process, we ought to start publishing nightlies and builds staged for QE onto devstudio.redhat.com (filemgmt) instead of the internal www.qa box. This will also allow us to use nightly URLs in ide-config.properties. > See https://github.com/jbosstools/jbosstools-download.jboss.org/pull/409/files for a bad solution to this problem. > Better solution is to move that content onto the new filemgmt instance and update promote.sh to push to the new location. > --- > After much discussion it's been decided that: > * we can push only the nightly/staging update sites automatically onto devstudio.redhat.com. > * Installers will remain internal-only until they're released and available on CSP and www.jboss.org -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 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 January 2015