September 2013 - jbosstools-issues

[JBoss JIRA] (JBDS-2731) Add basic content assist for data-ng-* and ng-* attribute elements and static values (if any)

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-2731?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-2731: ----------------------------- CDW release: + (was: ?) > Add basic content assist for data-ng-* and ng-* attribute elements and static values (if any) > --------------------------------------------------------------------------------------------- > > Key: JBDS-2731 > URL: https://issues.jboss.org/browse/JBDS-2731 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: requirements, visual-page-editor-core > Reporter: Max Rydahl Andersen > > We can't fix eclipse validation markers of ng-app in Kepler but we can at least make it easier to write them by adding content assist for them as done for jquery data. > It won't include dynamic content though - that will have to wait for next major release. -- 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-2731) Add basic content assist for data-ng-* and ng-* attribute elements and static values (if any)

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-2731?page=com.atlassian.jira.plugin.... ] Len DiMaggio updated JBDS-2731: ------------------------------- CDW qa_ack: + (was: ?) > Add basic content assist for data-ng-* and ng-* attribute elements and static values (if any) > --------------------------------------------------------------------------------------------- > > Key: JBDS-2731 > URL: https://issues.jboss.org/browse/JBDS-2731 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: requirements, visual-page-editor-core > Reporter: Max Rydahl Andersen > > We can't fix eclipse validation markers of ng-app in Kepler but we can at least make it easier to write them by adding content assist for them as done for jquery data. > It won't include dynamic content though - that will have to wait for next major release. -- 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-2733) Make Cordova tooling and CordovaSim available from software/update tab

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-2733?page=com.atlassian.jira.plugin.... ] Len DiMaggio updated JBDS-2733: ------------------------------- CDW qa_ack: + > Make Cordova tooling and CordovaSim available from software/update tab > ----------------------------------------------------------------------- > > Key: JBDS-2733 > URL: https://issues.jboss.org/browse/JBDS-2733 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: aerogear-hybrid, requirements > Reporter: Burr Sutter > Assignee: Nick Boldt > > Cordova should be available from JBDS, but it is not fully supported tech yet thus should be included/marked as a Technology Preview -- 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-2732) Add usage tracking for installs from JBDS central

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-2732?page=com.atlassian.jira.plugin.... ] Len DiMaggio updated JBDS-2732: ------------------------------- CDW qa_ack: + (was: ?) > Add usage tracking for installs from JBDS central > ------------------------------------------------- > > Key: JBDS-2732 > URL: https://issues.jboss.org/browse/JBDS-2732 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: requirements, usage > Reporter: Max Rydahl Andersen > > It would be interesting to know which connectors/plugins gets installed from 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-2734) Forge 2 in JBDS

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-2734?page=com.atlassian.jira.plugin.... ] Len DiMaggio updated JBDS-2734: ------------------------------- CDW qa_ack: + > Forge 2 in JBDS > --------------- > > Key: JBDS-2734 > URL: https://issues.jboss.org/browse/JBDS-2734 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: forge, requirements > Reporter: Burr Sutter > > Is Forge 2 ready to be included in JBDS ? -- 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-2736) Split Web and Mobile Development into 2 categories in JBT & JBDS Central

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-2736?page=com.atlassian.jira.plugin.... ] Len DiMaggio updated JBDS-2736: ------------------------------- CDW qa_ack: + > Split Web and Mobile Development into 2 categories in JBT & JBDS Central > ------------------------------------------------------------------------ > > Key: JBDS-2736 > URL: https://issues.jboss.org/browse/JBDS-2736 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: discovery, requirements > Reporter: Burr Sutter > Assignee: Nick Boldt > > http://screencast.com/t/7vsajdz9o > Now that Cordova tools have been proposed, we need to split Web & Mobile into there own categories on the Software/Update tab. -- 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-2735) Ensure the Forge 1 wizards work well

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-2735?page=com.atlassian.jira.plugin.... ] Len DiMaggio updated JBDS-2735: ------------------------------- CDW qa_ack: + Assignee: Len DiMaggio > Ensure the Forge 1 wizards work well > ------------------------------------ > > Key: JBDS-2735 > URL: https://issues.jboss.org/browse/JBDS-2735 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: forge, requirements > Reporter: Burr Sutter > Assignee: Len DiMaggio > -- 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-2748) Fix bugs in 7.0 documentation

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-2748?page=com.atlassian.jira.plugin.... ] Len DiMaggio updated JBDS-2748: ------------------------------- CDW qa_ack: + (was: ?) > Fix bugs in 7.0 documentation > ----------------------------- > > Key: JBDS-2748 > URL: https://issues.jboss.org/browse/JBDS-2748 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: documentation, requirements > Reporter: Michelle Murray > Assignee: Michelle Murray > > We should include essential but trivial fixes for the bugs in docs that have been found by docs/QE/users. > All those should be linked to this jira. -- 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 Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-2741?page=com.atlassian.jira.plugin.... ] Len DiMaggio updated JBDS-2741: ------------------------------- CDW qa_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-2749) Update screen captures in docs that explicitly reference JBDS 7.0

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-2749?page=com.atlassian.jira.plugin.... ] Len DiMaggio updated JBDS-2749: ------------------------------- CDW qa_ack: + > Update screen captures in docs that explicitly reference JBDS 7.0 > ----------------------------------------------------------------- > > Key: JBDS-2749 > URL: https://issues.jboss.org/browse/JBDS-2749 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: documentation, requirements > Reporter: Michelle Murray > Assignee: Michelle Murray > > Screen captures that will need updating for 7.1 docs > *Installation Guide* > * Figure 3.1. JBoss Developer Studio Downloads Listed on the Customer Portal > * Figure 3.2. Installation Step 3: Select Target Folder > * Figure 3.3. Installation Step 4: Select Java VM > * Figure 3.5. Installation Step 7: Installation Progress in Finished State > * Figure 3.6. Install JBoss Developer Studio BYOE via Eclipse Marketplace > * Figure 3.7. Confirm Selected Features Window > * Figure 3.10. Work from an Online Website > * Figure 3.11. work from a Local Copy of the Update .zip File > * Figure 3.12. Available Software Window Listing JBoss Developer Studio 7.0 - Bring Your Own Eclipse > * Figure 6.2. Uninstall JBoss Developer Studio via Eclipse Marketplace > * Figure 6.3. Confirm Selected Features Window > *Migration Guide* > * Figure 3.1. jbdevstudio.ini File Open in a Text Editor > *Getting Started Guide* (all Fig. shared with Installation Guide) > * Figure 3.1. JBoss Developer Studio Downloads Listed on the Customer Portal > * Figure 3.2. Installation Step 3: Select Target Folder > * Figure 3.3. Installation Step 4: Select Java VM > * Figure 3.5. Installation Step 7: Installation Progress in Finished State > *User Guide* > * Figure 2.4. JBoss Buzz > * Figure 2.22. Set Cheat Sheet Behavior in Project Examples Pane of Preferences Window -- 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