August 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-2623) Create target platform for mirrored parts of Central / 3rd Party Extras

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2623?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-2623: ------------------------------------------- This is behind the scene work. Makes verification/maintanence of our builds easier. > Create target platform for mirrored parts of Central / 3rd Party Extras > ----------------------------------------------------------------------- > > Key: JBDS-2623 > URL: https://issues.jboss.org/browse/JBDS-2623 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: 3rdPartyCertification, 3rdPartyDependencies, Central, updatesite, Upstream > Affects Versions: 7.0.0.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 7.1.x > > > As discussed in JBDS-2486 ( https://issues.jboss.org/browse/JBDS-2486?focusedCommentId=12770186&page=... ) we need to produce a target file for use with Central. > Goal here would be to build the Extras site (used by Central) as a TP update site rather than a composite of mirrors, which would provide us with a manifest of exactly which versions of these duped IUs were to be contained in the Extras site. If something bad happens, we can add duplicate versions of IUs to the TP and know exactly why we include both Jetty 8.1.3 and 8.1.9 (for example) or two different spins of WindowBuilder. This would mean it wouldn't matter if we filtered content out of the mirrors, because we'd be handling the filtering in a single place (extras.target) rather than multiple build.xml files. > In future, we would: > * mirror the individual upstream projects into /updates/requirements/<project> [on dl.jb.org] > * mirror the individual upstream projects into /updates/requirements/<project> [on www.qa] > * produce an aggregate of the stuff that Central needs, and publish that instead of the composite [on dl.jb.org] > * produce an aggregate of the stuff that Central needs, and publish that instead of the composite [on www.qa] > * produce an aggregate of the stuff that Central needs, and publish that instead of the composite [on ds.jb.com] > * add a whole new aggregate for old + new content -- 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

10 years, 9 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 Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBDS-2741?page=com.atlassian.jira.plugin.... ] Michelle Murray commented on JBDS-2741: --------------------------------------- [Docs] No impact on docs > 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: updatesite > Affects Versions: 7.0.0.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 7.1.0.Alpha1 > > > 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2736) Split Web and Mobile Development on JBoss Central

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBDS-2736?page=com.atlassian.jira.plugin.... ] Michelle Murray commented on JBDS-2736: --------------------------------------- [Docs] This will require a change to screen capture(s) in User Guide - Central chapter > Split Web and Mobile Development on JBoss 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) > Reporter: Burr Sutter > > 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2740) Support multiple namespaces in OpenShift

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2740?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-2740: ------------------------------------------- which api versions is this supported in ? docs ? > Support multiple namespaces in OpenShift > ---------------------------------------- > > Key: JBDS-2740 > URL: https://issues.jboss.org/browse/JBDS-2740 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Reporter: Andy Goldstein > Assignee: Andre Dietisheim > Labels: openshift > > OpenShift will soon add support for a user to have access to multiple namespaces. This includes: > - a user creates and owns multiple namespaces > - a user has permission to work with a domain owned by another user (with differing permission levels) -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2730) Faster download of updatesite content via akamai

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBDS-2730?page=com.atlassian.jira.plugin.... ] Michelle Murray commented on JBDS-2730: --------------------------------------- Docs Q: I am assuming this will not change what users have to do. Please correct me if I am wrong. > Faster download of updatesite content via akamai > ------------------------------------------------ > > Key: JBDS-2730 > URL: https://issues.jboss.org/browse/JBDS-2730 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Burr Sutter > > The updatesite used by marketplace should be behind akamai for smoother/faster download. > Investigate using akamai/download.jboss.org backed storage. -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2457) Mirror stable content on Akamai

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBDS-2457?page=com.atlassian.jira.plugin.... ] Michelle Murray edited comment on JBDS-2457 at 8/30/13 12:01 AM: ----------------------------------------------------------------- Docs Q: I am assuming this will not change what users have to do. Please correct me if I am wrong. was (Author: mmurray): Docs Q: I am assuming this will have no impact on users. Please correct me if I am wrong. > Mirror stable content on Akamai > ------------------------------- > > Key: JBDS-2457 > URL: https://issues.jboss.org/browse/JBDS-2457 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: updatesite > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 7.1.0.Alpha1 > > > In order to improve installation time (for both end-users and internal build/test usage), we should use Akamai on the stable folders if devstudio downloas site. -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2732) Add usage tracking for installs from JBDS central

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBDS-2732?page=com.atlassian.jira.plugin.... ] Michelle Murray commented on JBDS-2732: --------------------------------------- [Docs] This will need documenting in: Installation Guide Docs Q: On first JBDS start, users are prompted about usage statistics collection. Will that be the only prompt if this is implemented? Will the wording of the prompt be changed? Or will this require another prompt? > 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) > 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2727) Cheatsheets for JBoss Central archetypes

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBDS-2727?page=com.atlassian.jira.plugin.... ] Michelle Murray commented on JBDS-2727: --------------------------------------- [Docs] This will need documenting in: User Guide - Central chapter (and if for Java EE archetype then also Getting Started Guide) Docs Q: I assume this is the type of cheat sheet that opens in the cheat sheet tab rather than solely a README. Please correct me if I'm wrong. > Cheatsheets for JBoss Central archetypes > ---------------------------------------- > > Key: JBDS-2727 > URL: https://issues.jboss.org/browse/JBDS-2727 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Burr Sutter > > Our archetypes should have cheatsheets when imported/opened into eclipse. > Priority > 1) HTML5 - cheatsheet should focus the end-user's attention on index.html, editable in the VPE, with the jQuery Mobile Palette, it should also describe LiveReload setup and BrowserSim > 2) Java EE Web - cheatsheet should focus the end-user's attention on index.xhtml, editable in the VPE, with the JSF/RichFaces Palette. It should describe the JPA Member.java, the relationship between MemberController.java and index.xhtml, the purpose of MemberResourceRESTService.java and JaxRsActivator.java > Basically walk the user through the flow of events (from the UI to the backend) in the application > 3) RichFaces - cheatsheet should focus the end-user's attention on index.xhtml, editable in the VPE, with the JSF/RichFaces Palette. It should also describe resources/components/memberForm.xhtml and its use of <rich:validator/> and that tag's relationship with the JPA beanvalidations -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2726) Property Sheet with groupings for html elements

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBDS-2726?page=com.atlassian.jira.plugin.... ] Michelle Murray commented on JBDS-2726: --------------------------------------- [Docs] This will need documenting in: User Guide -Mobile Web Tools chapter This may also require changes to a handful of screen captures of the properties tab. Docs Q: What do the properties listed in the properties tab relate to? For JBIDE-14591 screen captures, I assume in an open html file you just click on a html/jQuery element, such as page or panel, and then the properties of that element are listed in the properties tab. > Property Sheet with groupings for html elements > ----------------------------------------------- > > Key: JBDS-2726 > URL: https://issues.jboss.org/browse/JBDS-2726 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Requirements > Reporter: Burr Sutter > > Currently the property view is a long list of properties, no grouping, no ordering. > Makes it tricky to use for quick editing, forcing users to manually edit the elements. > Would be nice to have at least some basic grouping in the properties view. -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2725) Essential but trivial bugfixes/updates to individual plugins

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBDS-2725?page=com.atlassian.jira.plugin.... ] Michelle Murray commented on JBDS-2725: --------------------------------------- [Docs] Any bug fixes will be documented as appropriate. > Essential but trivial bugfixes/updates to individual plugins > ------------------------------------------------------------ > > Key: JBDS-2725 > URL: https://issues.jboss.org/browse/JBDS-2725 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: integration > Reporter: Max Rydahl Andersen > > We should include essential but trivial fixes for the bugs in plugins that have been found by 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

10 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues August 2013