March 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (TOOLSDOC-298) 6.0 release notes says it *requires* JDK 6 which is not true since it also works with JDK 7

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-298?page=com.atlassian.jira.plug... ] Michelle Murray commented on TOOLSDOC-298: ------------------------------------------ Available for review on internal docs site: http://documentation-devel.engineering.redhat.com/docs/en-US/JBoss_Develo... > 6.0 release notes says it *requires* JDK 6 which is not true since it also works with JDK 7 > ------------------------------------------------------------------------------------------- > > Key: TOOLSDOC-298 > URL: https://issues.jboss.org/browse/TOOLSDOC-298 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Components: Release Notes > Affects Versions: 4.0.0.Final > Reporter: Max Rydahl Andersen > Assignee: Michelle Murray > Fix For: 4.0.0.Final > > > Was pointed out by [~aileenc] that our release notes say: > "JBoss Developer Studio 6 requires Java Development Kit (JDK) 1.6." > at https://access.redhat.com/knowledge/docs/en-US/JBoss_Developer_Studio/6.0... > That is not exactly correct since it also runs and have been tested on Java 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-298) 6.0 release notes says it *requires* JDK 6 which is not true since it also works with JDK 7

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-298?page=com.atlassian.jira.plug... ] Michelle Murray updated TOOLSDOC-298: ------------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-documentation/pull/43 Applied PR to 4.0.x branch only > 6.0 release notes says it *requires* JDK 6 which is not true since it also works with JDK 7 > ------------------------------------------------------------------------------------------- > > Key: TOOLSDOC-298 > URL: https://issues.jboss.org/browse/TOOLSDOC-298 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Components: Release Notes > Affects Versions: 4.0.0.Final > Reporter: Max Rydahl Andersen > Assignee: Michelle Murray > Fix For: 4.0.0.Final > > > Was pointed out by [~aileenc] that our release notes say: > "JBoss Developer Studio 6 requires Java Development Kit (JDK) 1.6." > at https://access.redhat.com/knowledge/docs/en-US/JBoss_Developer_Studio/6.0... > That is not exactly correct since it also runs and have been tested on Java 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-298) 6.0 release notes says it *requires* JDK 6 which is not true since it also works with JDK 7

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-298?page=com.atlassian.jira.plug... ] Michelle Murray updated TOOLSDOC-298: ------------------------------------- Fix Version/s: 4.0.0.Final Affects Version/s: 4.0.0.Final Affects: Documentation (Ref Guide, User Guide, etc.) > 6.0 release notes says it *requires* JDK 6 which is not true since it also works with JDK 7 > ------------------------------------------------------------------------------------------- > > Key: TOOLSDOC-298 > URL: https://issues.jboss.org/browse/TOOLSDOC-298 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Enhancement > Components: Release Notes > Affects Versions: 4.0.0.Final > Reporter: Max Rydahl Andersen > Assignee: Michelle Murray > Fix For: 4.0.0.Final > > > Was pointed out by [~aileenc] that our release notes say: > "JBoss Developer Studio 6 requires Java Development Kit (JDK) 1.6." > at https://access.redhat.com/knowledge/docs/en-US/JBoss_Developer_Studio/6.0... > That is not exactly correct since it also runs and have been tested on Java 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-298) 6.0 release notes says it *requires* JDK 6 which is not true since it also works with JDK 7

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-298?page=com.atlassian.jira.plug... ] Michelle Murray updated TOOLSDOC-298: ------------------------------------- Issue Type: Bug (was: Enhancement) > 6.0 release notes says it *requires* JDK 6 which is not true since it also works with JDK 7 > ------------------------------------------------------------------------------------------- > > Key: TOOLSDOC-298 > URL: https://issues.jboss.org/browse/TOOLSDOC-298 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Components: Release Notes > Affects Versions: 4.0.0.Final > Reporter: Max Rydahl Andersen > Assignee: Michelle Murray > Fix For: 4.0.0.Final > > > Was pointed out by [~aileenc] that our release notes say: > "JBoss Developer Studio 6 requires Java Development Kit (JDK) 1.6." > at https://access.redhat.com/knowledge/docs/en-US/JBoss_Developer_Studio/6.0... > That is not exactly correct since it also runs and have been tested on Java 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-298) 6.0 release notes says it *requires* JDK 6 which is not true since it also works with JDK 7

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-298?page=com.atlassian.jira.plug... ] Michelle Murray edited comment on TOOLSDOC-298 at 3/13/13 12:16 AM: -------------------------------------------------------------------- Also, in Component Versions the Eclipse version is given as 3.8.1 - this should be Juno (4.2). Noticed at the same time as fixing the above so will fix both in same git branch. was (Author: mmurray): Also, in Component Versions the Eclipse version is given as 3.8.1 - this should be Juno (4.2). > 6.0 release notes says it *requires* JDK 6 which is not true since it also works with JDK 7 > ------------------------------------------------------------------------------------------- > > Key: TOOLSDOC-298 > URL: https://issues.jboss.org/browse/TOOLSDOC-298 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Enhancement > Components: Release Notes > Reporter: Max Rydahl Andersen > Assignee: Michelle Murray > > Was pointed out by [~aileenc] that our release notes say: > "JBoss Developer Studio 6 requires Java Development Kit (JDK) 1.6." > at https://access.redhat.com/knowledge/docs/en-US/JBoss_Developer_Studio/6.0... > That is not exactly correct since it also runs and have been tested on Java 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-298) 6.0 release notes says it *requires* JDK 6 which is not true since it also works with JDK 7

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-298?page=com.atlassian.jira.plug... ] Michelle Murray edited comment on TOOLSDOC-298 at 3/13/13 12:15 AM: -------------------------------------------------------------------- Also, in Component Versions the Eclipse version is given as 3.8.1 - this should be Juno (4.2). was (Author: mmurray): Also, in Component Versions the Eclipse version is given as 3.8.1 - this should be 4.2 (Juno). > 6.0 release notes says it *requires* JDK 6 which is not true since it also works with JDK 7 > ------------------------------------------------------------------------------------------- > > Key: TOOLSDOC-298 > URL: https://issues.jboss.org/browse/TOOLSDOC-298 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Enhancement > Components: Release Notes > Reporter: Max Rydahl Andersen > Assignee: Michelle Murray > > Was pointed out by [~aileenc] that our release notes say: > "JBoss Developer Studio 6 requires Java Development Kit (JDK) 1.6." > at https://access.redhat.com/knowledge/docs/en-US/JBoss_Developer_Studio/6.0... > That is not exactly correct since it also runs and have been tested on Java 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-298) 6.0 release notes says it *requires* JDK 6 which is not true since it also works with JDK 7

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-298?page=com.atlassian.jira.plug... ] Michelle Murray commented on TOOLSDOC-298: ------------------------------------------ Also, in Component Versions the Eclipse version is given as 3.8.1 - this should be 4.2 (Juno). > 6.0 release notes says it *requires* JDK 6 which is not true since it also works with JDK 7 > ------------------------------------------------------------------------------------------- > > Key: TOOLSDOC-298 > URL: https://issues.jboss.org/browse/TOOLSDOC-298 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Enhancement > Components: Release Notes > Reporter: Max Rydahl Andersen > Assignee: Michelle Murray > > Was pointed out by [~aileenc] that our release notes say: > "JBoss Developer Studio 6 requires Java Development Kit (JDK) 1.6." > at https://access.redhat.com/knowledge/docs/en-US/JBoss_Developer_Studio/6.0... > That is not exactly correct since it also runs and have been tested on Java 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-300) Document Release Notes for JBT 4.0.1 & JBDS 6.0.1

by Michelle Murray (JIRA)

Michelle Murray created TOOLSDOC-300: ---------------------------------------- Summary: Document Release Notes for JBT 4.0.1 & JBDS 6.0.1 Key: TOOLSDOC-300 URL: https://issues.jboss.org/browse/TOOLSDOC-300 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Release Notes Affects Versions: 4.0.1 Reporter: Michelle Murray Assignee: Michelle Murray Fix For: 4.0.1 Write release notes document -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13690) Detect future EAP 6 based server like SOA-P

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13690?page=com.atlassian.jira.plugi... ] Michelle Murray updated JBIDE-13690: ------------------------------------ Release Notes Docs Status: Documented as Resolved Issue (was: Not Yet Documented) Writer: mmurray Release Notes Text: Application server directory trees were expected to have a certain structure, which was relied upon for the tooling to recognize and create new application servers. As highlighted by <ulink url="https://issues.jboss.org/jira/browse/JBIDE-13537">JBIDE-13537</ulink>, new releases of application servers do not necessarily conform to the expected directory structure. Consequently, these application servers would not be recognized by the tooling and would require patches to rectify the issues. To make recognition more reliable for future releases of application severs, the recognition methods have been modified to recognize a wider range of possible directory structures, under the provision that the directory structure does not deviate too far from the currently known structures. (was: Cause: The current codebase could not work against unreleased and untested application servers based on EAP. Consequence: A future application server may not be recognized by our tools, making a patch release the only way users could use a new application server. Fix: The fix included Creating recognizers that would most likely work against properly structured application servers of the future. Result: A future application server will most likely be recognized by our tools, so long as it conforms to currently known structures without deviating too far. ) > Detect future EAP 6 based server like SOA-P > ------------------------------------------- > > Key: JBIDE-13690 > URL: https://issues.jboss.org/browse/JBIDE-13690 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: JBossAS/Servers, runtime-detection > Reporter: Max Rydahl Andersen > Assignee: Len DiMaggio > Priority: Blocker > Labels: new_and_noteworthy, respin-a > Fix For: 4.0.1.Final, 4.1.0.Alpha2 > > > To be sure future AS7/EAP 6 based servers such as SOA-P 6 can be detected and started as an EAP 6 we need to provide a fallback for this instead of the currrent hardcoding of eap slots. -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13602) Backport to 4.0.x - Null Java EE Web Project Archetype

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13602?page=com.atlassian.jira.plugi... ] Michelle Murray updated JBIDE-13602: ------------------------------------ Writer: mmurray Release Notes Text: The project wizards in JBoss central are based on Maven archetypes and stacks.yml holds information defining the archetype for each project. Occasionally, stacks.yml would not load correctly and archetype information necessary for building the project would not be available. As a result, the wizard description would show "Project based on the null:null:null Maven archetype" and the project would fail to be created, with the error "Root cause: For artifact null:null:null:pom". The tooling has been modified to ensure stack.yml is always correctly loaded. Consequently, the wizard does not show null in the Maven archetype information and the project is successfully created. (was: Cause: stacks.yml used for driving the archetype based wizards was not always being loaded correctly. Consequence: User would occasionally see error message containing "Root cause: For artifact null:null:null" when running wizards from central or central. Fix: Error handling and ensuring stacks.yml is loaded fully. Result: Archetype based Wizards in central are no longer seeing the "null:null:null" error.) > Backport to 4.0.x - Null Java EE Web Project Archetype > ------------------------------------------------------ > > Key: JBIDE-13602 > URL: https://issues.jboss.org/browse/JBIDE-13602 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven > Affects Versions: 4.0.0.Final > Environment: Windows 7 64b, Eclipse Juno Service Release 1 Build id: 20120920-0800, Java 1.7_07, JBoss Tools 4.0.0.Final > Reporter: Fred Bricon > Assignee: Denis Golovin > Priority: Minor > Labels: maven > Fix For: 4.0.1.Final > > > When trying to create a new Java EE Web Project, the following description is presented: > {quote} > This is your project! It's a sample, deployable Maven 3 project to help you get your foot in the door developing with Java EE 6 on JBoss Enterprise Application Platform 6 or JBoss Application Server 7.1. > This project is setup to allow you to create a compliant Java EE 6 application using JSF 2.0, CDI 1.0, EJB 3.1, JPA 2.0 and Bean Validation 1.0. > Project based on the *null:null:null* Maven archetype > {quote} > If I go forward with the creation of the project, I get the following error message: > {quote} > Failed to create project. > Root cause: For artifact null:null:null:pom : The group id cannot be empty. > {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

13 years, 1 month

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 March 2013