September 2013 - jbosstools-issues

[JBoss JIRA] (JBDS-1609) Installer should check system prerequisites and warn user if they are not fullfilled

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBDS-1609?page=com.atlassian.jira.plugin.... ] Michelle Murray updated JBDS-1609: ---------------------------------- Affects: Documentation (Ref Guide, User Guide, etc.) > Installer should check system prerequisites and warn user if they are not fullfilled > ------------------------------------------------------------------------------------ > > Key: JBDS-1609 > URL: https://issues.jboss.org/browse/JBDS-1609 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: installer > Affects Versions: 4.0.0.GA > Reporter: Jiri Peterka > Assignee: Denis Golovin > Priority: Critical > Fix For: 7.1.x > > > To prevent insufficient machine parameters or setting installer should do basic check for some parameters like: > - memory amount > - maximum open file limit > - maximum thread count limit > - internet connection > - others reasonable criteria should be added here > If these criteria aren't met, installer should display add warning page before further installation saying that requirements aren't satisfied and tools may not work properly. Reason for this is that sometimes JBDS is used in very strict environment (typically training rooms, universities, etc where many system resources are limited or blocked) but user isn't warned and after install user can see after that lots of runtime errors and got bad feeling about the tool. This should be avoided and user should be at least warn that he is running JBDS in inappropriate environment. -- 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-2065) Installer doesn't let add locations to detect runtimes if started with -DTRACE=TRUE

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBDS-2065?page=com.atlassian.jira.plugin.... ] Michelle Murray updated JBDS-2065: ---------------------------------- Affects: Documentation (Ref Guide, User Guide, etc.) > Installer doesn't let add locations to detect runtimes if started with -DTRACE=TRUE > ----------------------------------------------------------------------------------- > > Key: JBDS-2065 > URL: https://issues.jboss.org/browse/JBDS-2065 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: installer, upstream > Affects Versions: 5.0.0.M5 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 7.1.x > > Attachments: Screen Shot 2012-03-09 at 10.05.17.jpg > > -- 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-1591) JBDS Installer as a Native Mac OS X Application

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBDS-1591?page=com.atlassian.jira.plugin.... ] Michelle Murray updated JBDS-1591: ---------------------------------- Affects: Documentation (Ref Guide, User Guide, etc.) > JBDS Installer as a Native Mac OS X Application > ----------------------------------------------- > > Key: JBDS-1591 > URL: https://issues.jboss.org/browse/JBDS-1591 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: installer > Affects Versions: 4.0.0.GA > Environment: Mac OS X > Reporter: Martin Malina > Assignee: Denis Golovin > Priority: Minor > Fix For: 7.1.x > > > This is an enhancement for your consideration. Feel free to reject it. > Currently, all the installers of JBDS for Mac OS X and other platforms are just plain jar files which you launch either with "java -jar" or by double clicking if the OS supports this. > When you launch the jar, the icon that appears in the Dock is just a default app icon. It would be possible to bundle the installer on the Mac so that it would be a native Mac OS X app called e.g. "JBDS 4 Installer.app". > The instructions on how to achieve this are described here: > http://java.sun.com/developer/technicalArticles/JavaLP/JavaToMac3/ > I just tried it and it's easy. > I think it would be easy to implement this in the building process. The benefit would be an installer with our custom icon in the Dock and also on the installer itself - i.e. in Finder. -- 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-2757) Remove java 6 requirement of EAP from installer

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBDS-2757?page=com.atlassian.jira.plugin.... ] Michelle Murray updated JBDS-2757: ---------------------------------- Affects: Documentation (Ref Guide, User Guide, etc.) > Remove java 6 requirement of EAP from installer > ----------------------------------------------- > > Key: JBDS-2757 > URL: https://issues.jboss.org/browse/JBDS-2757 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: installer > Affects Versions: 7.1.0.Alpha1 > Environment: OS X Mountain Lion > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 7.1.0.Alpha2 > > Attachments: ins-step-4.png, ins-step-5.png > > > There are two strings I would like removed from the installer: > Step 4 > Please note that JBoss EAP 6 requires Java 6 or higher. > !ins-step-4.png! > Step 5 > (Java 6 is required to run JBoss EAP 6) > !ins-step-5.png! > I think this was added when we still supported running of JBDS with Java 5, but now that JBDS needs Java 6 I think it's not needed to point this out explicitly. > Also, in Step 4 there's this: > JBoss Developer Studio works with Java 6 and has been tested with OpenJDK, Oracle and Apple JDK. > - Here I would add Java 7 to the mix - we test that too. > And last, EAP should be Red Hat JBoss Enterprise Application Platform (in Step 5). -- 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-2712) Typo in installer: Ok > OK

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBDS-2712?page=com.atlassian.jira.plugin.... ] Michelle Murray updated JBDS-2712: ---------------------------------- Affects: Documentation (Ref Guide, User Guide, etc.) > Typo in installer: Ok > OK > -------------------------- > > Key: JBDS-2712 > URL: https://issues.jboss.org/browse/JBDS-2712 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 7.0.0.GA > Reporter: Michelle Murray > Assignee: Denis Golovin > Fix For: 7.1.0.Alpha2 > > Attachments: Installer_Ok1.png, Installer_Ok2.png > > > In step 5 of the installer (Select Platforms and Servers), two child windows have 'Ok', which should be 'OK'. > 1. At step 5, click Add. > 2. Click Browse. > 3. Select location and click *Ok*. > 4. Click *Ok* to close the Add Location window. > Screen captures attached. -- 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-2555) JBDS70_0315, JBDS70_0413: [Commit] (Dev) (P2) Offline - JBDS Update Site Zip

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBDS-2555?page=com.atlassian.jira.plugin.... ] Michelle Murray updated JBDS-2555: ---------------------------------- Affects: Documentation (Ref Guide, User Guide, etc.) > JBDS70_0315, JBDS70_0413: [Commit] (Dev) (P2) Offline - JBDS Update Site Zip > ---------------------------------------------------------------------------- > > Key: JBDS-2555 > URL: https://issues.jboss.org/browse/JBDS-2555 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: central, updatesite > Reporter: Jiri Pallich > Fix For: 7.1.0.Alpha2 > > > Offline Usage of JBoss Central (Customers without or very slow Internet access) > On-line once, then off-line - aka a user demo/instructional class - the testLocal cache is usable/complete after one on-line install. Provide a script that pre-caches everything for an instructor/demo'er in the field (online once, then offline). > Related to: https://issues.jboss.org/browse/JBDS-2535 -- 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-2678) add EAP 6.1.1 to JBDS 7.1.0 installer

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBDS-2678?page=com.atlassian.jira.plugin.... ] Michelle Murray updated JBDS-2678: ---------------------------------- Affects: Documentation (Ref Guide, User Guide, etc.) > add EAP 6.1.1 to JBDS 7.1.0 installer > ------------------------------------- > > Key: JBDS-2678 > URL: https://issues.jboss.org/browse/JBDS-2678 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: installer, requirements > Affects Versions: 7.0.0.GA > Reporter: Nick Boldt > Assignee: Len DiMaggio > Fix For: 7.1.0.Alpha1, 7.1.0.Alpha2 > > > EAP 6.1.1 is supposed to be out in September, so we should update the installers to include the new version at that time. -- 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-2763) REBRANDING: should JBDS 7.1 installer window be labelled "Red Hat JBoss Developer Studio" instead of "JBoss Developer Studio" ? Should jar file & feature names change too?

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBDS-2763?page=com.atlassian.jira.plugin.... ] Michelle Murray updated JBDS-2763: ---------------------------------- Affects: Documentation (Ref Guide, User Guide, etc.) > REBRANDING: should JBDS 7.1 installer window be labelled "Red Hat JBoss Developer Studio" instead of "JBoss Developer Studio" ? Should jar file & feature names change too? > --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-2763 > URL: https://issues.jboss.org/browse/JBDS-2763 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build, installer > Affects Versions: 7.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Max Rydahl Andersen > Attachments: 2763_3_places.png, 2763_cmdline.png > > > Wondering if it's time to rebrand JBDS 7.1 so that its installer window is labelled "Red Hat JBoss Developer Studio" instead of "JBoss Developer Studio" ? > !https://issues.jboss.org/secure/attachment/12364502/12364502_ins-step-5.png! > Should we also rename the jbdevstudio-**.jar files to rhjbdevstudio-**.jar? > What about features like com.jboss.jbds.product.feature, which currently appear as "JBoss Developer Studio (Core Features)" when installed. Should that too move to "Red Hat JBoss Developer Studio (Core Features)" ? -- 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] (TOOLSDOC-390) Update book versions for 7.1/4.2

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-390?page=com.atlassian.jira.plug... ] Michelle Murray commented on TOOLSDOC-390: ------------------------------------------ Done for all core books except User Guide: https://github.com/jbosstools/jbosstools-documentation/pull/178 > Update book versions for 7.1/4.2 > -------------------------------- > > Key: TOOLSDOC-390 > URL: https://issues.jboss.org/browse/TOOLSDOC-390 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Security Level: Public(Everyone can see) > Components: General documentation issues > Affects Versions: 4.1.0 > Reporter: Michelle Murray > Assignee: Michelle Murray > Fix For: 4.1.0 > > > Update Book_Info.xml & Revision History with 7.1. > Update pom.xml with 4.2.0 > Also incorporate TOOLSDOC-313 (moving doc version out of master.xml and into pom.xml). -- 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-2623) Create target platform for mirrored parts of Central / 3rd Party Extras

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2623?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-2623: ---------------------------------- Reasons for the change are discussed in the PR: https://github.com/jbosstools/jbosstools-discovery/pull/36#commitcomment-... Meanwhile, I've got two new jobs for two new Central TP builds: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-centralta... https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-centralta... Which produce content in here: http://download.jboss.org/jbosstools/targetplatforms/jbtcentraltarget/ So only thing left to do now is to migrate from this URL convention: http://download.jboss.org/jbosstools/updates/kepler/extras/ to this one: http://download.jboss.org/jbosstools/targetplatforms/jbtcentraltarget/kep... > 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: 3rd-party-certification, 3rd-party-dependencies, central, requirements, updatesite, upstream > Affects Versions: 7.0.0.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 7.1.x > > Attachments: 2623-manual-hack.png, 2623-p2browser-shows-datanucleus-missing.png, 2623-remove-and-regen.png > > > 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

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