[JBoss JIRA] (TOOLSDOC-325) Incorrect supported JDK matrix
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-325?page=com.atlassian.jira.plug... ]
Martin Malina closed TOOLSDOC-325.
----------------------------------
Closing this JIRA.
> Incorrect supported JDK matrix
> ------------------------------
>
> Key: TOOLSDOC-325
> URL: https://issues.jboss.org/browse/TOOLSDOC-325
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Installation Guide
> Affects Versions: 4.1.0
> Reporter: Pavol Srna
> Assignee: Martin Malina
> Fix For: 4.1.0
>
>
> Hi Michelle,
> the Supported Combinations of Operating Systems and Java Developer Kits seems to be wrong. We don't support Fedora 16,17 - instead we support f18,f19.
> We also dropped ubuntu 11.10 and added Ubuntu 13.
> For all supported *linux* distros we support openJDK and OracleJDK 1.6 and 1.7.
--
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, 3 months
[JBoss JIRA] (TOOLSDOC-325) Incorrect supported JDK matrix
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-325?page=com.atlassian.jira.plug... ]
Martin Malina resolved TOOLSDOC-325.
------------------------------------
Resolution: Done
Sorry for the delay. You were right, I was probably looking at an older version - the information is correct on the links you provided (although [2] is a dead link, but I found the right one).
So this JIRA is done.
> Incorrect supported JDK matrix
> ------------------------------
>
> Key: TOOLSDOC-325
> URL: https://issues.jboss.org/browse/TOOLSDOC-325
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Installation Guide
> Affects Versions: 4.1.0
> Reporter: Pavol Srna
> Assignee: Martin Malina
> Fix For: 4.1.0
>
>
> Hi Michelle,
> the Supported Combinations of Operating Systems and Java Developer Kits seems to be wrong. We don't support Fedora 16,17 - instead we support f18,f19.
> We also dropped ubuntu 11.10 and added Ubuntu 13.
> For all supported *linux* distros we support openJDK and OracleJDK 1.6 and 1.7.
--
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, 3 months
[JBoss JIRA] (JBTIS-121) Failed to read artifact descriptor for org.jboss.sp when creating a Jboss app via JBoss Tool
by nan wei (JIRA)
[ https://issues.jboss.org/browse/JBTIS-121?page=com.atlassian.jira.plugin.... ]
nan wei updated JBTIS-121:
--------------------------
Attachment: pom.xml.PNG
> Failed to read artifact descriptor for org.jboss.sp when creating a Jboss app via JBoss Tool
> --------------------------------------------------------------------------------------------
>
> Key: JBTIS-121
> URL: https://issues.jboss.org/browse/JBTIS-121
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 4.1.0.Final
> Environment: Window7(Windows7_x64.qcow2) Git-1.8.3-preview2013.6.1 jdk-7u25-windows-x64
> Reporter: nan wei
> Priority: Trivial
> Fix For: 4.1.0.Final
>
> Attachments: pom.xml.PNG
>
>
> Title:Failed to read artifact descriptor for org.jboss.sp when creating a Jboss app via JBoss Tool.
> Description of problem:
> When creating a Jboss app via JBoss Tool on Windows, the app will be created successfully, but a cross mark is appearing on the pom.xml in the project and return the error:
> ArtifactDescriptorException:Failed to read artifact descriptor for org.jboss.sp(Click for details)
> This issue does not happened on Fedora18, if a Jboss app is created in Jboss Tools on Fedroa18 , there is no such error presentation, it is created successfully.
> Version:
> JBossTools-4.1.0.final
> Eclipse Standard 4.3
> OpenShift Enterprise 1.2.1/2013-07-29.3
> Window7
> How reproducible:
> always
> Steps to Reproduce:
> 1. Create a jboss app via JBoss Tools
> Type: jbosseap-6.0 or jbossews-1.0 or jbossews-2.0
> Actual results:
> Cross mark is appearing on the pom.xml in the project and return the error
> ArtifactDescriptorException:Failed to read artifact descriptor for org.jboss.sp(Click for details)
> Expected results:
> There is no such error description.
> Additional info:
--
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, 3 months
[JBoss JIRA] (JBTIS-121) Failed to read artifact descriptor for org.jboss.sp when creating a Jboss app via JBoss Tool
by nan wei (JIRA)
[ https://issues.jboss.org/browse/JBTIS-121?page=com.atlassian.jira.plugin.... ]
nan wei updated JBTIS-121:
--------------------------
Environment: Window7(Windows7_x64.qcow2) Git-1.8.3-preview2013.6.1 jdk-7u25-windows-x64 (was: Window7)
> Failed to read artifact descriptor for org.jboss.sp when creating a Jboss app via JBoss Tool
> --------------------------------------------------------------------------------------------
>
> Key: JBTIS-121
> URL: https://issues.jboss.org/browse/JBTIS-121
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 4.1.0.Final
> Environment: Window7(Windows7_x64.qcow2) Git-1.8.3-preview2013.6.1 jdk-7u25-windows-x64
> Reporter: nan wei
> Priority: Trivial
> Fix For: 4.1.0.Final
>
> Attachments: pom.xml.PNG
>
>
> Title:Failed to read artifact descriptor for org.jboss.sp when creating a Jboss app via JBoss Tool.
> Description of problem:
> When creating a Jboss app via JBoss Tool on Windows, the app will be created successfully, but a cross mark is appearing on the pom.xml in the project and return the error:
> ArtifactDescriptorException:Failed to read artifact descriptor for org.jboss.sp(Click for details)
> This issue does not happened on Fedora18, if a Jboss app is created in Jboss Tools on Fedroa18 , there is no such error presentation, it is created successfully.
> Version:
> JBossTools-4.1.0.final
> Eclipse Standard 4.3
> OpenShift Enterprise 1.2.1/2013-07-29.3
> Window7
> How reproducible:
> always
> Steps to Reproduce:
> 1. Create a jboss app via JBoss Tools
> Type: jbosseap-6.0 or jbossews-1.0 or jbossews-2.0
> Actual results:
> Cross mark is appearing on the pom.xml in the project and return the error
> ArtifactDescriptorException:Failed to read artifact descriptor for org.jboss.sp(Click for details)
> Expected results:
> There is no such error description.
> Additional info:
--
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, 3 months
[JBoss JIRA] (JBTIS-121) Failed to read artifact descriptor for org.jboss.sp when creating a Jboss app via JBoss Tool
by nan wei (JIRA)
nan wei created JBTIS-121:
-----------------------------
Summary: Failed to read artifact descriptor for org.jboss.sp when creating a Jboss app via JBoss Tool
Key: JBTIS-121
URL: https://issues.jboss.org/browse/JBTIS-121
Project: JBoss Tools Integration Stack
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 4.1.0.Final
Environment: Window7
Reporter: nan wei
Priority: Trivial
Fix For: 4.1.0.Final
Title:Failed to read artifact descriptor for org.jboss.sp when creating a Jboss app via JBoss Tool.
Description of problem:
When creating a Jboss app via JBoss Tool on Windows, the app will be created successfully, but a cross mark is appearing on the pom.xml in the project and return the error:
ArtifactDescriptorException:Failed to read artifact descriptor for org.jboss.sp(Click for details)
This issue does not happened on Fedora18, if a Jboss app is created in Jboss Tools on Fedroa18 , there is no such error presentation, it is created successfully.
Version:
JBossTools-4.1.0.final
Eclipse Standard 4.3
OpenShift Enterprise 1.2.1/2013-07-29.3
Window7
How reproducible:
always
Steps to Reproduce:
1. Create a jboss app via JBoss Tools
Type: jbosseap-6.0 or jbossews-1.0 or jbossews-2.0
Actual results:
Cross mark is appearing on the pom.xml in the project and return the error
ArtifactDescriptorException:Failed to read artifact descriptor for org.jboss.sp(Click for details)
Expected results:
There is no such error description.
Additional info:
--
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, 3 months
[JBoss JIRA] (TOOLSDOC-348) Installation Guide 7.0.0 - add screen captures
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-348?page=com.atlassian.jira.plug... ]
Michelle Murray commented on TOOLSDOC-348:
------------------------------------------
Typos fixed too:
* Procedure 3.2. Install from Eclipse Marketplace = Ensure the *JBoss* Developer Studio (Kepler) check box is selected and click *Next*. (> Red Hat JBoss, > 'Confirm >')
* Procedure 6.2. Uninstall from Eclipse Marketplace = Ensure the *JBoss* Developer Studio (Kepler) check box is selected and click Finish. (> Red Hat JBoss)
And add extra step - one for click confirm and one for click finish
* Procedure 4.1. Set up Runtime Detection = Click Window→Preferences, expand JBoss Tools and select *JBoss Tools Runtime Detection*. (> JBoss Runtime Detection)
> Installation Guide 7.0.0 - add screen captures
> ----------------------------------------------
>
> Key: TOOLSDOC-348
> URL: https://issues.jboss.org/browse/TOOLSDOC-348
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Sub-task
> Security Level: Public(Everyone can see)
> Components: Installation Guide
> Affects Versions: 4.1.0
> Reporter: Michelle Murray
> Assignee: Michelle Murray
> Fix For: 4.1.0
>
>
--
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, 3 months