September 2013 - jbosstools-issues

[JBoss JIRA] (JBDS-2741) Replace staging & staging.previous (two builds w/ reused URLs) with uniquely timestamped build URLs and auto-regenerated composite*.xml files

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2741?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2741: ----------------------------- CDW devel_ack: + (was: ?) > Replace staging & staging.previous (two builds w/ reused URLs) with uniquely timestamped build URLs and auto-regenerated composite*.xml files > --------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-2741 > URL: https://issues.jboss.org/browse/JBDS-2741 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build, requirements, updatesite > Affects Versions: 7.0.0.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 7.1.0.Alpha2 > > > Be it proposed: > {quote} > that instead of an in-place move which reuses > generic folder names like "staging" and "staging.previous", we > composite build output using unique names like > 2013-08-09_05-05-26-B7222/ or 2013-08-13_10-05-28-B7255 > {quote} > We therefore need: > a) to regenerate the composite site each time there's a new build > published, in order to remove the oldest and add the newest (keeping > only the Nth and N-1rst builds) > (I have a script that might already work for this, or would need > tweaking.) > b) heuristics to determine when an older (N-2, N-3, ... N-z) build is > no longer needed, perhaps simply by assuming no one needs it after > 24hrs? > 24 hours should be more that enough. > c) a cleanup script which can purge all but the builds which are no > more than 1 day old, keeping at all times at least two builds (N and > N-1) > (I have a script that already does this for folders like > http://download.jboss.org/jbosstools/builds/nightly/core/trunk/ but > might need to be tweaked to work for a new pattern of > staging/\$\{JOB_NAME}/<BUILD_ID>/ .) > {quote} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2741) Replace staging & staging.previous (two builds w/ reused URLs) with uniquely timestamped build URLs and auto-regenerated composite*.xml files

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2741?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2741: ----------------------------- Component/s: build > Replace staging & staging.previous (two builds w/ reused URLs) with uniquely timestamped build URLs and auto-regenerated composite*.xml files > --------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-2741 > URL: https://issues.jboss.org/browse/JBDS-2741 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build, requirements, updatesite > Affects Versions: 7.0.0.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 7.1.0.Alpha2 > > > Be it proposed: > {quote} > that instead of an in-place move which reuses > generic folder names like "staging" and "staging.previous", we > composite build output using unique names like > 2013-08-09_05-05-26-B7222/ or 2013-08-13_10-05-28-B7255 > {quote} > We therefore need: > a) to regenerate the composite site each time there's a new build > published, in order to remove the oldest and add the newest (keeping > only the Nth and N-1rst builds) > (I have a script that might already work for this, or would need > tweaking.) > b) heuristics to determine when an older (N-2, N-3, ... N-z) build is > no longer needed, perhaps simply by assuming no one needs it after > 24hrs? > 24 hours should be more that enough. > c) a cleanup script which can purge all but the builds which are no > more than 1 day old, keeping at all times at least two builds (N and > N-1) > (I have a script that already does this for folders like > http://download.jboss.org/jbosstools/builds/nightly/core/trunk/ but > might need to be tweaked to work for a new pattern of > staging/\$\{JOB_NAME}/<BUILD_ID>/ .) > {quote} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2741) Replace staging & staging.previous (two builds w/ reused URLs) with uniquely timestamped build URLs and auto-regenerated composite*.xml files

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-2741?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-2741: ----------------------------- CDW pm_ack: ? (was: +) > Replace staging & staging.previous (two builds w/ reused URLs) with uniquely timestamped build URLs and auto-regenerated composite*.xml files > --------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-2741 > URL: https://issues.jboss.org/browse/JBDS-2741 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build, requirements, updatesite > Affects Versions: 7.0.0.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 7.1.0.Alpha2 > > > Be it proposed: > {quote} > that instead of an in-place move which reuses > generic folder names like "staging" and "staging.previous", we > composite build output using unique names like > 2013-08-09_05-05-26-B7222/ or 2013-08-13_10-05-28-B7255 > {quote} > We therefore need: > a) to regenerate the composite site each time there's a new build > published, in order to remove the oldest and add the newest (keeping > only the Nth and N-1rst builds) > (I have a script that might already work for this, or would need > tweaking.) > b) heuristics to determine when an older (N-2, N-3, ... N-z) build is > no longer needed, perhaps simply by assuming no one needs it after > 24hrs? > 24 hours should be more that enough. > c) a cleanup script which can purge all but the builds which are no > more than 1 day old, keeping at all times at least two builds (N and > N-1) > (I have a script that already does this for folders like > http://download.jboss.org/jbosstools/builds/nightly/core/trunk/ but > might need to be tweaked to work for a new pattern of > staging/\$\{JOB_NAME}/<BUILD_ID>/ .) > {quote} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2729) Add mobile web quickstarts for JBoss Central

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-2729?page=com.atlassian.jira.plugin.... ] Fred Bricon commented on JBDS-2729: ----------------------------------- * should we add *all* quickstarts to central or only a subset (the other subset could be available from the project examples wizard). One concern is : given the current state of Javascript support in Eclipse, we should restrict featured quickstarts to stuff we know Eclipse can handle. * same question as max : community or enterprise? * should we feature quickstarts having dependencies on experimental plugins (e.g. JBT aerogear/cordova integration for instance)? > Add mobile web quickstarts for JBoss Central > -------------------------------------------- > > Key: JBDS-2729 > URL: https://issues.jboss.org/browse/JBDS-2729 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: aerogear-hybrid, central > Reporter: Burr Sutter > > The mobile web quickstarts being proced on WFK2 side should be included in JBoss Central -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2577) JBDS70_0813: [Partial] (Dev) (P1) Support non-minified/minified JS libs

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-2577?page=com.atlassian.jira.plugin.... ] Len DiMaggio updated JBDS-2577: ------------------------------- CDW qa_ack: ? > JBDS70_0813: [Partial] (Dev) (P1) Support non-minified/minified JS libs > ----------------------------------------------------------------------- > > Key: JBDS-2577 > URL: https://issues.jboss.org/browse/JBDS-2577 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: requirements > Reporter: Jiri Pallich > Assignee: Max Rydahl Andersen > Priority: Blocker > > Support non-minified JS libs for Dev, swap in minified JS libs for production (wro4j - maven integration?). > Examples of JS libs: jQuery, jQuery Mobile -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2745) Support installation of Early Access / Experimental / Incubating plugins

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2745?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-2745: ------------------------------------------- [~fbricon] supported/tested are today 100% separated - none of them install same bundles. With experimenta/incubating you are installing new/different versions of the plugins already present. Thats where it gets quircky. > Support installation of Early Access / Experimental / Incubating plugins > ------------------------------------------------------------------------ > > Key: JBDS-2745 > URL: https://issues.jboss.org/browse/JBDS-2745 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: central, requirements > Affects Versions: 7.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Burr Sutter > > It's been suggested that it would be nice to have Central available to install non-GA content. How might this appear? > [~burrsutter], [~maxandersen], are we talking about: > * an additional dialog warning users about untested content? (that might be ignored / blindclicked) > * an additional tab in Central for this type of content (what label would you use?) > * relabelling the content's feature descriptions / titles / copyright / license terms to be clear it's unstable content? (might be ignored) > * some other workflow? > See also JBDS-2068. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2745) Support installation of Early Access / Experimental / Incubating plugins

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-2745?page=com.atlassian.jira.plugin.... ] Fred Bricon updated JBDS-2745: ------------------------------ CDW devel_ack: ? (was: +) > Support installation of Early Access / Experimental / Incubating plugins > ------------------------------------------------------------------------ > > Key: JBDS-2745 > URL: https://issues.jboss.org/browse/JBDS-2745 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: central, requirements > Affects Versions: 7.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Burr Sutter > > It's been suggested that it would be nice to have Central available to install non-GA content. How might this appear? > [~burrsutter], [~maxandersen], are we talking about: > * an additional dialog warning users about untested content? (that might be ignored / blindclicked) > * an additional tab in Central for this type of content (what label would you use?) > * relabelling the content's feature descriptions / titles / copyright / license terms to be clear it's unstable content? (might be ignored) > * some other workflow? > See also JBDS-2068. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2745) Support installation of Early Access / Experimental / Incubating plugins

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-2745?page=com.atlassian.jira.plugin.... ] Fred Bricon commented on JBDS-2745: ----------------------------------- looks doable. We already have "Supported" and "Tested" connectors. Simply add an "Experimental" one+ some UI magic for visual hints and that should do it. > Support installation of Early Access / Experimental / Incubating plugins > ------------------------------------------------------------------------ > > Key: JBDS-2745 > URL: https://issues.jboss.org/browse/JBDS-2745 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: central, requirements > Affects Versions: 7.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Burr Sutter > > It's been suggested that it would be nice to have Central available to install non-GA content. How might this appear? > [~burrsutter], [~maxandersen], are we talking about: > * an additional dialog warning users about untested content? (that might be ignored / blindclicked) > * an additional tab in Central for this type of content (what label would you use?) > * relabelling the content's feature descriptions / titles / copyright / license terms to be clear it's unstable content? (might be ignored) > * some other workflow? > See also JBDS-2068. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2745) Support installation of Early Access / Experimental / Incubating plugins

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-2745?page=com.atlassian.jira.plugin.... ] Fred Bricon updated JBDS-2745: ------------------------------ CDW devel_ack: + (was: ?) Status: New (was: New) > Support installation of Early Access / Experimental / Incubating plugins > ------------------------------------------------------------------------ > > Key: JBDS-2745 > URL: https://issues.jboss.org/browse/JBDS-2745 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: central, requirements > Affects Versions: 7.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Burr Sutter > > It's been suggested that it would be nice to have Central available to install non-GA content. How might this appear? > [~burrsutter], [~maxandersen], are we talking about: > * an additional dialog warning users about untested content? (that might be ignored / blindclicked) > * an additional tab in Central for this type of content (what label would you use?) > * relabelling the content's feature descriptions / titles / copyright / license terms to be clear it's unstable content? (might be ignored) > * some other workflow? > See also JBDS-2068. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15468) Ensure versioning errors (eg., maintenance branch at 3.5.1 while master at 3.5.0) are correctly shown in vwatch results table

by Jiri Peterka (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15468?page=com.atlassian.jira.plugi... ] Jiri Peterka commented on JBIDE-15468: -------------------------------------- Either new build fixed that or new VWatch version improves that, however versions are back. > Ensure versioning errors (eg., maintenance branch at 3.5.1 while master at 3.5.0) are correctly shown in vwatch results table > ----------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-15468 > URL: https://issues.jboss.org/browse/JBIDE-15468 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, qa > Affects Versions: 4.1.1.Alpha1 > Reporter: Nick Boldt > Assignee: Jiri Peterka > Priority: Blocker > Fix For: 4.1.1.Alpha1 > > Attachments: jbide15432_missing_table_cell_tooltip_shows_actual_blocker_problem.png, version-ok.png > > > This screenshot taken from http://download.jboss.org/jbosstools/builds/staging/devstudio.versionwatc... shows that in some cases the table cell is blank when there's a real problem that should be reported, and that the reported problem in the tool tip doesn't match the information shown. > !jbide15432_missing_table_cell_tooltip_shows_actual_blocker_problem.png! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 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 September 2013