[JBoss JIRA] (JBIDE-16910) Three items in our tp cannot be installed into clean luna m6
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16910?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-16910:
-------------------------------------
> What I don't understand is why doesn't the target-platform-validation see this missing dependency? In general, it should and used to fail when something is transitively missing... (in this case com.thoughtworks.xstream).
I would suggest this is the issue you try to solve ;) If you could solve that and make transitive deps error appropriately, then issues like the one I posted will disappear ;)
I don't need this in the re-spin at all, but, I don't know what may be broken by NOT including it. My use-case is a dev-only one, but I file it not usually for my benefit but rather to help you guys spot potentially more critical issues. So, its up to you all whether the changes you made need to make respin-b or not. But *I* don't really need them.
> Three items in our tp cannot be installed into clean luna m6
> ------------------------------------------------------------
>
> Key: JBIDE-16910
> URL: https://issues.jboss.org/browse/JBIDE-16910
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform
> Affects Versions: 4.2.0.Beta1
> Reporter: Rob Stryker
> Assignee: Nick Boldt
> Fix For: 4.2.0.Beta2
>
> Attachments: bugForNick.png
>
>
> cd jbosstools-target-platforms
> git checkout 4.40.x
> mvn clean verify -Dmirror-target-to-repo.includeSources=true
> cd ~/apps/eclipse
> mkdir lunam6
> cd lunam6
> // acquire tar gz file
> tar xvzf (filename for luna m6)
> cd eclipse
> ./eclipse
> Help -> Install new software
> Select "local", point to jbosstools-target-platforms/jbosstools/multiple/target/jbosstools-multiple.target.repo/
> Wait for it to calculate what can or cannot be installed. See 3 items that cannot be installed (See screenshot)
> Error:
> {code}
> Cannot complete the install because one or more required items could not be found.
> Software being installed: Atlassian Connector for Eclipse Usage Monitoring 3.2.2.v20130909 (com.atlassian.connector.eclipse.monitor.feature.group 3.2.2.v20130909)
> Missing requirement: Atlassian Connector for Eclipse Usage Data Collector 3.2.2.v20130909 (com.atlassian.connector.eclipse.monitor.core 3.2.2.v20130909) requires 'bundle com.thoughtworks.xstream 0.0.0' but it could not be found
> Cannot satisfy dependency:
> From: Atlassian Connector for Eclipse Usage Monitoring 3.2.2.v20130909 (com.atlassian.connector.eclipse.monitor.feature.group 3.2.2.v20130909)
> To: com.atlassian.connector.eclipse.monitor.core [3.2.2.v20130909]
> {code}
--
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
[JBoss JIRA] (JBIDE-16868) Resizing of Cordova Plugin Discovery dialog doesn't work
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16868?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-16868:
-----------------------------------------------
List for Registry tab contains 186 elements, each presented by 5 controls, so that during resize about 1000 controls should be rezised and updated. That is done by standard swt methods Composite.updateLayout(), Control.setBounds(), etc in ui thread.
I see a possible solution in limiting the number of displayed items and adding control
'Show *** items of 186 available." where *** is an input field set initially to 10.
After filter (Find input) is applied, the number of available items is updated to the actual value.
> Resizing of Cordova Plugin Discovery dialog doesn't work
> --------------------------------------------------------
>
> Key: JBIDE-16868
> URL: https://issues.jboss.org/browse/JBIDE-16868
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.2.0.Beta1
> Environment: JBDS 8.0.0.Beta1-v20140323-1410-B78 Linux
> Reporter: Vlado Pakan
> Assignee: Denis Golovin
> Fix For: 4.2.0.Beta2
>
>
> Resizing of this dialog is very slow or doesn't work at all.
> Try to resize it by mouse cursor for bigger distance and dialog is resized only a little and it takes too much 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
[JBoss JIRA] (JBDS-2859) Include information on EAP version in installer
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-2859?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-2859:
--------------------------------
CDW qa_ack: + (was: ?)
> Include information on EAP version in installer
> -----------------------------------------------
>
> Key: JBDS-2859
> URL: https://issues.jboss.org/browse/JBDS-2859
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: installer
> Affects Versions: 7.1.0.CR1
> Reporter: Martin Malina
> Assignee: Denis Golovin
> Fix For: 8.0.0.CR1
>
> Attachments: step-6.png, summary-eap-version-fixed.png
>
>
> I find it hard for users to find out which version of EAP they are installing with JBDS. The installer has no mention of it. At least in the installer summary (Step 6 of 9) we could include this information.
> !step-6.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
[JBoss JIRA] (JBDS-2859) Include information on EAP version in installer
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-2859?page=com.atlassian.jira.plugin.... ]
CDW Engine updated JBDS-2859:
-----------------------------
CDW release: + (was: ?)
> Include information on EAP version in installer
> -----------------------------------------------
>
> Key: JBDS-2859
> URL: https://issues.jboss.org/browse/JBDS-2859
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: installer
> Affects Versions: 7.1.0.CR1
> Reporter: Martin Malina
> Assignee: Denis Golovin
> Fix For: 8.0.0.CR1
>
> Attachments: step-6.png, summary-eap-version-fixed.png
>
>
> I find it hard for users to find out which version of EAP they are installing with JBDS. The installer has no mention of it. At least in the installer summary (Step 6 of 9) we could include this information.
> !step-6.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
[JBoss JIRA] (JBDS-2859) Include information on EAP version in installer
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-2859?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-2859:
--------------------------------
CDW devel_ack: + (was: ?)
> Include information on EAP version in installer
> -----------------------------------------------
>
> Key: JBDS-2859
> URL: https://issues.jboss.org/browse/JBDS-2859
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: installer
> Affects Versions: 7.1.0.CR1
> Reporter: Martin Malina
> Assignee: Denis Golovin
> Fix For: 8.0.0.CR1
>
> Attachments: step-6.png, summary-eap-version-fixed.png
>
>
> I find it hard for users to find out which version of EAP they are installing with JBDS. The installer has no mention of it. At least in the installer summary (Step 6 of 9) we could include this information.
> !step-6.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
[JBoss JIRA] (TOOLSDOC-451) Update explicit Kepler text and figs references in docs for 8.0 (Luna)
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-451?page=com.atlassian.jira.plug... ]
Michelle Murray commented on TOOLSDOC-451:
------------------------------------------
[~sdorfiel], most of these should be covered by TOOLSDOC-449. So there may not be much to do here before marking the jira as done.
> Update explicit Kepler text and figs references in docs for 8.0 (Luna)
> ----------------------------------------------------------------------
>
> Key: TOOLSDOC-451
> URL: https://issues.jboss.org/browse/TOOLSDOC-451
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Getting Started Guide, Installation Guide, Migration Guide, User Guide
> Reporter: Michelle Murray
> Assignee: Suz Dorfield
> Fix For: 4.2.0.Beta1
>
> Original Estimate: 4 hours
> Time Spent: 35 minutes
> Remaining Estimate: 3 hours, 25 minutes
>
> _Text_
> *Installation Guide*
> * 2.2 Supported Operating Systems and Architectures
> * 3.3 Install JBoss Developer Studio BYOE
> * 5.2 Upgrade from JBoss Developer Studio 6.x and Earlier
> * 5.3 Upgrade from JBoss Developer Studio 7.0
> * 6.3 Uninstall JBoss Developer Studio BYOE
> *Getting Started Guide*
> --
> *Migration Guide*
> * 2.2 Upgrade from JBoss Developer Studio 6.x and Earlier (shared with Install)
> * 2.3 Upgrade from JBoss Developer Studio 7.0 (shared with Install)* 3.1 Change the Version of Eclipse Being Used with JBoss Developer Studio BYOE
> *User Guide*
> --
> _Figs_
> *Installation Guide*
> * Fig 3.6 Ininstall JBoss Developer Studio BYOE via Eclipse Marketplace
> * Fig 3.7 Confirm Selected Features Window
> * Fig 6.2 Uninstall JBoss Developer Studio via Eclipse Marketplace
> * Fig 6.3 Confirm Selected Features Window
> *Getting Started Guide*
> --
> *Migration Guide*
> --
> *User Guide*
> --
--
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
[JBoss JIRA] (TOOLSDOC-449) Update explicit 7.1 text and figs references in docs for 8.0
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-449?page=com.atlassian.jira.plug... ]
Michelle Murray updated TOOLSDOC-449:
-------------------------------------
Description:
_Text_
*Installation Guide*
2.2 Supported Operating Systems and Architectures
2.3 Computer Memory
2.4 Compatible Java Developer Kits
3.2 Install JBoss Developer Studio
3.3 Install JBoss Developer Studio BYOE
5.2 Upgrade from JBoss Developer Studio 6.x and Earlier
5.3 Upgrade from JBoss Developer Studio 7.0
B.1 Build the Universal Installer from Source
*Getting Started Guide*
2.1 About Getting Started
3.1 Installation Assumptions
3.2 Install JBoss Developer Studio (shared with Install)
4.3 Tutorial Assumptions
*Migration Guide*
2.2 Upgrade from JBoss Developer Studio 6.x and Earlier (shared with Install)
2.3 Upgrade from JBoss Developer Studio 7.0 (shared with Install)
3.1 Change the Version of Eclipse Being Used with JBoss Developer Studio BYOE
*User Guide*
--
_Figures_
*Installation Guide*
3.2 Installation Step 3: Select Target Folder
3.3 Installation Step 4: Select Java VM
3.4 Add Location Window for Runtime Detection (should be EAP6.2.2)
3.5 Installation Step 7: Installation Progress in Finished State
3.6 Install JBoss Developer Studio BYOE via Eclipse Marketplace
3.7 Confirm Selected Features Window
3.10 Work from an Online Website
3.11 Work from a Local Copy of the Update .zip file
3.12 Available Software Window Listing JBoss Developer Studio 7.x - Bring Your Own Eclipse
4.4 One New Application Server Found by Runtime Detection (should be EAP6.2.2)
6.2 Uninstall JBoss Developer Studio via Eclipse Marketplace
6.3 Confirm Selected Features Window
*Getting Started Guide*
3.2 Installation Step 3: Select Target Folder (shared with Install)
3.3 Installation Step 4: Select Java VM (shared with Install)
3.4 Installation Step 7: Installation Progress in Finished State (shared with Install)
5.2. Add Maven Repository Window (should be EAP6.2.2)
5.4. JBoss Enterprise Application Platform 6.x Found by Runtime Detection (should be EAP6.2.2)
5.5. JBoss Enterprise Application Platform 6.x Server Listed in Servers View (should be EAP6.2.2)
5.7. JBoss Enterprise Application Platform 6.x Selected as Target Runtime in Java EE Web Project Wizard (should be EAP6.2.2)
*Migration Guide*
--
*User Guide*
2.5 JBoss Buzz
2.23 Work from a Local Copy of the JBoss Central .zip File
was:
_Text_
*Installation Guide*
2.2 Supported Operating Systems and Architectures
2.3 Computer Memory
2.4 Compatible Java Developer Kits
3.2 Install JBoss Developer Studio
3.3 Install JBoss Developer Studio BYOE
5.2 Upgrade from JBoss Developer Studio 6.x and Earlier
5.3 Upgrade from JBoss Developer Studio 7.0
B.1 Build the Universal Installer from Source
*Getting Started Guide*
2.1 About Getting Started
3.1 Installation Assumptions
3.2 Install JBoss Developer Studio (shared with Install)
4.3 Tutorial Assumptions
*Migration Guide*
2.2 Upgrade from JBoss Developer Studio 6.x and Earlier (shared with Install)
2.3 Upgrade from JBoss Developer Studio 7.0 (shared with Install)
3.1 Change the Version of Eclipse Being Used with JBoss Developer Studio BYOE
*User Guide*
--
_Figures_
*Installation Guide*
3.2 Installation Step 3: Select Target Folder
3.3 Installation Step 4: Select Java VM
3.4 Add Location Window for Runtime Detection (should be EAP6.2.2)
3.5 Installation Step 7: Installation Progress in Finished State
3.6 Install JBoss Developer Studio BYOE via Eclipse Marketplace
3.7 Confirm Selected Features Window
3.10 Work from an Online Website
3.11 Work from a Local Copy of the Update .zip file
3.12 Available Software Window Listing JBoss Developer Studio 7.x - Bring Your Own Eclipse
4.4 One New Application Server Found by Runtime Detection (should be EAP6.2.2)
6.2 Uninstall JBoss Developer Studio via Eclipse Marketplace
6.3 Confirm Selected Features Window
*Getting Started Guide*
3.2 Installation Step 3: Select Target Folder (shared with Install)
3.3 Installation Step 4: Select Java VM (shared with Install)
3.4 Installation Step 7: Installation Progress in Finished State (shared with Install)
5.2. Add Maven Repository Window
5.4. JBoss Enterprise Application Platform 6.x Found by Runtime Detection (should be EAP6.2.2)
5.5. JBoss Enterprise Application Platform 6.x Server Listed in Servers View (should be EAP6.2.2)
5.7. JBoss Enterprise Application Platform 6.x Selected as Target Runtime in Java EE Web Project Wizard (should be EAP6.2.2)
*Migration Guide*
--
*User Guide*
2.5 JBoss Buzz
2.23 Work from a Local Copy of the JBoss Central .zip File
> Update explicit 7.1 text and figs references in docs for 8.0
> ------------------------------------------------------------
>
> Key: TOOLSDOC-449
> URL: https://issues.jboss.org/browse/TOOLSDOC-449
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Getting Started Guide, Installation Guide, Migration Guide, User Guide
> Reporter: Michelle Murray
> Assignee: Suz Dorfield
> Fix For: 4.2.0.Beta1
>
> Original Estimate: 1 day, 30 minutes
> Time Spent: 40 minutes
> Remaining Estimate: 7 hours, 50 minutes
>
> _Text_
> *Installation Guide*
> 2.2 Supported Operating Systems and Architectures
> 2.3 Computer Memory
> 2.4 Compatible Java Developer Kits
> 3.2 Install JBoss Developer Studio
> 3.3 Install JBoss Developer Studio BYOE
> 5.2 Upgrade from JBoss Developer Studio 6.x and Earlier
> 5.3 Upgrade from JBoss Developer Studio 7.0
> B.1 Build the Universal Installer from Source
> *Getting Started Guide*
> 2.1 About Getting Started
> 3.1 Installation Assumptions
> 3.2 Install JBoss Developer Studio (shared with Install)
> 4.3 Tutorial Assumptions
> *Migration Guide*
> 2.2 Upgrade from JBoss Developer Studio 6.x and Earlier (shared with Install)
> 2.3 Upgrade from JBoss Developer Studio 7.0 (shared with Install)
> 3.1 Change the Version of Eclipse Being Used with JBoss Developer Studio BYOE
> *User Guide*
> --
> _Figures_
> *Installation Guide*
> 3.2 Installation Step 3: Select Target Folder
> 3.3 Installation Step 4: Select Java VM
> 3.4 Add Location Window for Runtime Detection (should be EAP6.2.2)
> 3.5 Installation Step 7: Installation Progress in Finished State
> 3.6 Install JBoss Developer Studio BYOE via Eclipse Marketplace
> 3.7 Confirm Selected Features Window
> 3.10 Work from an Online Website
> 3.11 Work from a Local Copy of the Update .zip file
> 3.12 Available Software Window Listing JBoss Developer Studio 7.x - Bring Your Own Eclipse
> 4.4 One New Application Server Found by Runtime Detection (should be EAP6.2.2)
> 6.2 Uninstall JBoss Developer Studio via Eclipse Marketplace
> 6.3 Confirm Selected Features Window
> *Getting Started Guide*
> 3.2 Installation Step 3: Select Target Folder (shared with Install)
> 3.3 Installation Step 4: Select Java VM (shared with Install)
> 3.4 Installation Step 7: Installation Progress in Finished State (shared with Install)
> 5.2. Add Maven Repository Window (should be EAP6.2.2)
> 5.4. JBoss Enterprise Application Platform 6.x Found by Runtime Detection (should be EAP6.2.2)
> 5.5. JBoss Enterprise Application Platform 6.x Server Listed in Servers View (should be EAP6.2.2)
> 5.7. JBoss Enterprise Application Platform 6.x Selected as Target Runtime in Java EE Web Project Wizard (should be EAP6.2.2)
> *Migration Guide*
> --
> *User Guide*
> 2.5 JBoss Buzz
> 2.23 Work from a Local Copy of the JBoss Central .zip File
--
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
[JBoss JIRA] (TOOLSDOC-449) Update explicit 7.1 text and figs references in docs for 8.0
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-449?page=com.atlassian.jira.plug... ]
Michelle Murray updated TOOLSDOC-449:
-------------------------------------
Description:
_Text_
*Installation Guide*
2.2 Supported Operating Systems and Architectures
2.3 Computer Memory
2.4 Compatible Java Developer Kits
3.2 Install JBoss Developer Studio
3.3 Install JBoss Developer Studio BYOE
5.2 Upgrade from JBoss Developer Studio 6.x and Earlier
5.3 Upgrade from JBoss Developer Studio 7.0
B.1 Build the Universal Installer from Source
*Getting Started Guide*
2.1 About Getting Started
3.1 Installation Assumptions
3.2 Install JBoss Developer Studio (shared with Install)
4.3 Tutorial Assumptions
*Migration Guide*
2.2 Upgrade from JBoss Developer Studio 6.x and Earlier (shared with Install)
2.3 Upgrade from JBoss Developer Studio 7.0 (shared with Install)
3.1 Change the Version of Eclipse Being Used with JBoss Developer Studio BYOE
*User Guide*
--
_Figures_
*Installation Guide*
3.2 Installation Step 3: Select Target Folder
3.3 Installation Step 4: Select Java VM
3.4 Add Location Window for Runtime Detection (should be EAP6.2.2)
3.5 Installation Step 7: Installation Progress in Finished State
3.6 Install JBoss Developer Studio BYOE via Eclipse Marketplace
3.7 Confirm Selected Features Window
3.10 Work from an Online Website
3.11 Work from a Local Copy of the Update .zip file
3.12 Available Software Window Listing JBoss Developer Studio 7.x - Bring Your Own Eclipse
4.4 One New Application Server Found by Runtime Detection (should be EAP6.2.2)
6.2 Uninstall JBoss Developer Studio via Eclipse Marketplace
6.3 Confirm Selected Features Window
*Getting Started Guide*
3.2 Installation Step 3: Select Target Folder (shared with Install)
3.3 Installation Step 4: Select Java VM (shared with Install)
3.4 Installation Step 7: Installation Progress in Finished State (shared with Install)
5.2. Add Maven Repository Window
5.4. JBoss Enterprise Application Platform 6.x Found by Runtime Detection (should be EAP6.2.2)
5.5. JBoss Enterprise Application Platform 6.x Server Listed in Servers View (should be EAP6.2.2)
5.7. JBoss Enterprise Application Platform 6.x Selected as Target Runtime in Java EE Web Project Wizard (should be EAP6.2.2)
*Migration Guide*
--
*User Guide*
2.5 JBoss Buzz
2.23 Work from a Local Copy of the JBoss Central .zip File
was:
_Text_
*Installation Guide*
2.2 Supported Operating Systems and Architectures
2.3 Computer Memory
2.4 Compatible Java Developer Kits
3.2 Install JBoss Developer Studio
3.3 Install JBoss Developer Studio BYOE
5.2 Upgrade from JBoss Developer Studio 6.x and Earlier
5.3 Upgrade from JBoss Developer Studio 7.0
B.1 Build the Universal Installer from Source
*Getting Started Guide*
2.1 About Getting Started
3.1 Installation Assumptions
3.2 Install JBoss Developer Studio (shared with Install)
4.3 Tutorial Assumptions
*Migration Guide*
2.2 Upgrade from JBoss Developer Studio 6.x and Earlier (shared with Install)
2.3 Upgrade from JBoss Developer Studio 7.0 (shared with Install)
3.1 Change the Version of Eclipse Being Used with JBoss Developer Studio BYOE
*User Guide*
--
_Figures_
*Installation Guide*
3.2 Installation Step 3: Select Target Folder
3.3 Installation Step 4: Select Java VM
3.5 Installation Step 7: Installation Progress in Finished State
3.6 Install JBoss Developer Studio BYOE via Eclipse Marketplace
3.7 Confirm Selected Features Window
3.10 Work from an Online Website
3.11 Work from a Local Copy of the Update .zip file
3.12 Availalble Software Window Listing JBoss Developer Studio 7.x - Bring Your Own Eclipse
*Getting Started Guide*
3.2 Installation Step 3: Select Target Folder (shared with Install)
3.3 Installation Step 4: Select Java VM (shared with Install)
3.4 Installation Step 7: Installation Progress in Finished State (shared with Install)
*Migration Guide*
--
*User Guide*
2.4 JBoss Buzz
2.22 Work from a Local Copy of the JBoss Central .zip File
> Update explicit 7.1 text and figs references in docs for 8.0
> ------------------------------------------------------------
>
> Key: TOOLSDOC-449
> URL: https://issues.jboss.org/browse/TOOLSDOC-449
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Getting Started Guide, Installation Guide, Migration Guide, User Guide
> Reporter: Michelle Murray
> Assignee: Suz Dorfield
> Fix For: 4.2.0.Beta1
>
> Original Estimate: 1 day, 30 minutes
> Time Spent: 40 minutes
> Remaining Estimate: 7 hours, 50 minutes
>
> _Text_
> *Installation Guide*
> 2.2 Supported Operating Systems and Architectures
> 2.3 Computer Memory
> 2.4 Compatible Java Developer Kits
> 3.2 Install JBoss Developer Studio
> 3.3 Install JBoss Developer Studio BYOE
> 5.2 Upgrade from JBoss Developer Studio 6.x and Earlier
> 5.3 Upgrade from JBoss Developer Studio 7.0
> B.1 Build the Universal Installer from Source
> *Getting Started Guide*
> 2.1 About Getting Started
> 3.1 Installation Assumptions
> 3.2 Install JBoss Developer Studio (shared with Install)
> 4.3 Tutorial Assumptions
> *Migration Guide*
> 2.2 Upgrade from JBoss Developer Studio 6.x and Earlier (shared with Install)
> 2.3 Upgrade from JBoss Developer Studio 7.0 (shared with Install)
> 3.1 Change the Version of Eclipse Being Used with JBoss Developer Studio BYOE
> *User Guide*
> --
> _Figures_
> *Installation Guide*
> 3.2 Installation Step 3: Select Target Folder
> 3.3 Installation Step 4: Select Java VM
> 3.4 Add Location Window for Runtime Detection (should be EAP6.2.2)
> 3.5 Installation Step 7: Installation Progress in Finished State
> 3.6 Install JBoss Developer Studio BYOE via Eclipse Marketplace
> 3.7 Confirm Selected Features Window
> 3.10 Work from an Online Website
> 3.11 Work from a Local Copy of the Update .zip file
> 3.12 Available Software Window Listing JBoss Developer Studio 7.x - Bring Your Own Eclipse
> 4.4 One New Application Server Found by Runtime Detection (should be EAP6.2.2)
> 6.2 Uninstall JBoss Developer Studio via Eclipse Marketplace
> 6.3 Confirm Selected Features Window
> *Getting Started Guide*
> 3.2 Installation Step 3: Select Target Folder (shared with Install)
> 3.3 Installation Step 4: Select Java VM (shared with Install)
> 3.4 Installation Step 7: Installation Progress in Finished State (shared with Install)
> 5.2. Add Maven Repository Window
> 5.4. JBoss Enterprise Application Platform 6.x Found by Runtime Detection (should be EAP6.2.2)
> 5.5. JBoss Enterprise Application Platform 6.x Server Listed in Servers View (should be EAP6.2.2)
> 5.7. JBoss Enterprise Application Platform 6.x Selected as Target Runtime in Java EE Web Project Wizard (should be EAP6.2.2)
> *Migration Guide*
> --
> *User Guide*
> 2.5 JBoss Buzz
> 2.23 Work from a Local Copy of the JBoss Central .zip File
--
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