[JBoss JIRA] (JBDS-2825) How do I install Experimental / Extra features into JBDS 7.1.0.Beta1?
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2825?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-2825:
-----------------------------
Description:
Because we forgot to set the default Central site in JBT and JBDS to the Dev Milestone site (/development/, /7.0-development/) users will still see the Central content from the previously-release stable release, JBT 4.1.0.1 / JBDS 7.0.1.
There are two ways to work around this.
1. Install using p2 Install Manager.
a) JBDS / JBDS BYOE users
Help > Install new software > https://devstudio.jboss.com/updates/7.0-development/central/core/
!JBDS-experimental-features-inBeta1.png!
b) Eclipse / JBT users
Help > Install new software > http://download.jboss.org/jbosstools/updates/development/kepler/central/c...
!JBT-experimental-features-inBeta1.png!
2. Adjust your .ini file, so that you can see the new content in Central.
a) JBDS / JBDS BYOE users
change this line to add "-development" in your *studio/jbdevstudio.ini* file:
{code}
-Djboss.discovery.directory.url=https://devstudio.jboss.com/updates/7.0-development/devstudio-directory.xml
{code}
b) Eclipse / JBT users:
add this to your *eclipse.ini* file, on the line after the "-vmargs" line:
{code}
-Djboss.discovery.directory.url=http://download.jboss.org/jbosstools/updates/development/kepler/jbosstools-directory.xml
{code}
was:
Because we forgot to set the default Central site in JBT and JBDS to the Dev Milestone site (/development/, /7.0-development/) users will still see the Central content from the previously-release stable release, JBT 4.1.0.1 / JBDS 7.0.1.
There are two ways to work around this.
1. Install using p2 Install Manager.
a) Eclipse / JBT users
Help > Install new software > http://download.jboss.org/jbosstools/updates/development/kepler/central/c...
b) JBDS / JBDS BYOE users
Help > Install new software > https://devstudio.jboss.com/updates/7.0-development/central/core/
2. Adjust your .ini file, so that you can see the new content in Central.
a) Eclipse / JBT users:
add this to your *eclipse.ini* file, on the line after the "-vmargs" line:
{code}
-Djboss.discovery.directory.url=http://download.jboss.org/jbosstools/updates/development/kepler/jbosstools-directory.xml
{code}
b) JBDS / JBDS BYOE users
change this line to add "-development" in your *studio/jbdevstudio.ini* file:
{code}
-Djboss.discovery.directory.url=https://devstudio.jboss.com/updates/7.0-development/devstudio-directory.xml
{code}
> How do I install Experimental / Extra features into JBDS 7.1.0.Beta1?
> ---------------------------------------------------------------------
>
> Key: JBDS-2825
> URL: https://issues.jboss.org/browse/JBDS-2825
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: documentation, updatesite
> Affects Versions: 7.1.0.Beta1
> Reporter: Nick Boldt
> Assignee: Max Rydahl Andersen
> Attachments: JBDS-experimental-features-inBeta1.png, JBT-experimental-features-inBeta1.png
>
>
> Because we forgot to set the default Central site in JBT and JBDS to the Dev Milestone site (/development/, /7.0-development/) users will still see the Central content from the previously-release stable release, JBT 4.1.0.1 / JBDS 7.0.1.
> There are two ways to work around this.
> 1. Install using p2 Install Manager.
> a) JBDS / JBDS BYOE users
> Help > Install new software > https://devstudio.jboss.com/updates/7.0-development/central/core/
> !JBDS-experimental-features-inBeta1.png!
> b) Eclipse / JBT users
> Help > Install new software > http://download.jboss.org/jbosstools/updates/development/kepler/central/c...
> !JBT-experimental-features-inBeta1.png!
> 2. Adjust your .ini file, so that you can see the new content in Central.
> a) JBDS / JBDS BYOE users
> change this line to add "-development" in your *studio/jbdevstudio.ini* file:
> {code}
> -Djboss.discovery.directory.url=https://devstudio.jboss.com/updates/7.0-development/devstudio-directory.xml
> {code}
> b) Eclipse / JBT users:
> add this to your *eclipse.ini* file, on the line after the "-vmargs" line:
> {code}
> -Djboss.discovery.directory.url=http://download.jboss.org/jbosstools/updates/development/kepler/jbosstools-directory.xml
> {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, 6 months
[JBoss JIRA] (JBDS-2825) How do I install Experimental / Extra features into JBDS 7.1.0.Beta1?
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2825?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-2825:
-----------------------------
Attachment: JBT-experimental-features-inBeta1.png
JBDS-experimental-features-inBeta1.png
> How do I install Experimental / Extra features into JBDS 7.1.0.Beta1?
> ---------------------------------------------------------------------
>
> Key: JBDS-2825
> URL: https://issues.jboss.org/browse/JBDS-2825
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: documentation, updatesite
> Affects Versions: 7.1.0.Beta1
> Reporter: Nick Boldt
> Assignee: Max Rydahl Andersen
> Attachments: JBDS-experimental-features-inBeta1.png, JBT-experimental-features-inBeta1.png
>
>
> Because we forgot to set the default Central site in JBT and JBDS to the Dev Milestone site (/development/, /7.0-development/) users will still see the Central content from the previously-release stable release, JBT 4.1.0.1 / JBDS 7.0.1.
> There are two ways to work around this.
> 1. Install using p2 Install Manager.
> a) Eclipse / JBT users
> Help > Install new software > http://download.jboss.org/jbosstools/updates/development/kepler/central/c...
> b) JBDS / JBDS BYOE users
> Help > Install new software > https://devstudio.jboss.com/updates/7.0-development/central/core/
> 2. Adjust your .ini file, so that you can see the new content in Central.
> a) Eclipse / JBT users:
> add this to your *eclipse.ini* file, on the line after the "-vmargs" line:
> {code}
> -Djboss.discovery.directory.url=http://download.jboss.org/jbosstools/updates/development/kepler/jbosstools-directory.xml
> {code}
> b) JBDS / JBDS BYOE users
> change this line to add "-development" in your *studio/jbdevstudio.ini* file:
> {code}
> -Djboss.discovery.directory.url=https://devstudio.jboss.com/updates/7.0-development/devstudio-directory.xml
> {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, 6 months
[JBoss JIRA] (JBDS-2825) How do I install Experimental / Extra features into JBDS 7.1.0.Beta1?
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2825?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-2825:
-----------------------------
Description:
Because we forgot to set the default Central site in JBT and JBDS to the Dev Milestone site (/development/, /7.0-development/) users will still see the Central content from the previously-release stable release, JBT 4.1.0.1 / JBDS 7.0.1.
There are two ways to work around this.
1. Install using p2 Install Manager.
a) Eclipse / JBT users
Help > Install new software > http://download.jboss.org/jbosstools/updates/development/kepler/central/c...
b) JBDS / JBDS BYOE users
Help > Install new software > https://devstudio.jboss.com/updates/7.0-development/central/core/
2. Adjust your .ini file, so that you can see the new content in Central.
a) Eclipse / JBT users:
add this to your *eclipse.ini* file, on the line after the "-vmargs" line:
{code}
-Djboss.discovery.directory.url=http://download.jboss.org/jbosstools/updates/development/kepler/jbosstools-directory.xml
{code}
b) JBDS / JBDS BYOE users
change this line to add "-development" in your *studio/jbdevstudio.ini* file:
{code}
-Djboss.discovery.directory.url=https://devstudio.jboss.com/updates/7.0-development/devstudio-directory.xml
{code}
was:
Because we forgot to set the default Central site in JBT and JBDS to the Dev Milestone site (/development/, /7.0-development/) users will still see the Central content from the previously-release stable release, JBT 4.1.0.1 / JBDS 7.0.1.
There are two ways to work around this.
1. Adjust your .ini file, so that you can see the new content in Central.
a) Eclipse / JBT users:
add this to your eclipse.ini file, on the line after the "-vmargs" line:
{code}
-Djboss.discovery.directory.url=http://download.jboss.org/jbosstools/updates/development/kepler/jbosstools-directory.xml
{code}
b) JBDS / JBDS BYOE users
change this line to add "-development" in your studio/jbdevstudio.ini file:
{code}
-Djboss.discovery.directory.url=https://devstudio.jboss.com/updates/7.0-development/devstudio-directory.xml
{code}
2. Install using p2 Install Manager.
a) Eclipse / JBT users
Help > Install new software > http://download.jboss.org/jbosstools/updates/development/kepler/central/c...
b) JBDS / JBDS BYOE users
Help > Install new software > https://devstudio.jboss.com/updates/7.0-development/central/core/
> How do I install Experimental / Extra features into JBDS 7.1.0.Beta1?
> ---------------------------------------------------------------------
>
> Key: JBDS-2825
> URL: https://issues.jboss.org/browse/JBDS-2825
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: documentation, updatesite
> Affects Versions: 7.1.0.Beta1
> Reporter: Nick Boldt
> Assignee: Max Rydahl Andersen
> Attachments: JBDS-experimental-features-inBeta1.png, JBT-experimental-features-inBeta1.png
>
>
> Because we forgot to set the default Central site in JBT and JBDS to the Dev Milestone site (/development/, /7.0-development/) users will still see the Central content from the previously-release stable release, JBT 4.1.0.1 / JBDS 7.0.1.
> There are two ways to work around this.
> 1. Install using p2 Install Manager.
> a) Eclipse / JBT users
> Help > Install new software > http://download.jboss.org/jbosstools/updates/development/kepler/central/c...
> b) JBDS / JBDS BYOE users
> Help > Install new software > https://devstudio.jboss.com/updates/7.0-development/central/core/
> 2. Adjust your .ini file, so that you can see the new content in Central.
> a) Eclipse / JBT users:
> add this to your *eclipse.ini* file, on the line after the "-vmargs" line:
> {code}
> -Djboss.discovery.directory.url=http://download.jboss.org/jbosstools/updates/development/kepler/jbosstools-directory.xml
> {code}
> b) JBDS / JBDS BYOE users
> change this line to add "-development" in your *studio/jbdevstudio.ini* file:
> {code}
> -Djboss.discovery.directory.url=https://devstudio.jboss.com/updates/7.0-development/devstudio-directory.xml
> {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, 6 months
[JBoss JIRA] (JBDS-2825) How do I install Experimental / Extra features into JBDS 7.1.0.Beta1?
by Nick Boldt (JIRA)
Nick Boldt created JBDS-2825:
--------------------------------
Summary: How do I install Experimental / Extra features into JBDS 7.1.0.Beta1?
Key: JBDS-2825
URL: https://issues.jboss.org/browse/JBDS-2825
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: documentation, updatesite
Affects Versions: 7.1.0.Beta1
Reporter: Nick Boldt
Assignee: Max Rydahl Andersen
Because we forgot to set the default Central site in JBT and JBDS to the Dev Milestone site (/development/, /7.0-development/) users will still see the Central content from the previously-release stable release, JBT 4.1.0.1 / JBDS 7.0.1.
There are two ways to work around this.
1. Adjust your .ini file, so that you can see the new content in Central.
a) Eclipse / JBT users:
add this to your eclipse.ini file, on the line after the "-vmargs" line:
{code}
-Djboss.discovery.directory.url=http://download.jboss.org/jbosstools/updates/development/kepler/jbosstools-directory.xml
{code}
b) JBDS / JBDS BYOE users
change this line to add "-development" in your studio/jbdevstudio.ini file:
{code}
-Djboss.discovery.directory.url=https://devstudio.jboss.com/updates/7.0-development/devstudio-directory.xml
{code}
2. Install using p2 Install Manager.
a) Eclipse / JBT users
Help > Install new software > http://download.jboss.org/jbosstools/updates/development/kepler/central/c...
b) JBDS / JBDS BYOE users
Help > Install new software > https://devstudio.jboss.com/updates/7.0-development/central/core/
--
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, 6 months
[JBoss JIRA] (JBDS-2729) Add mobile web quickstarts for JBoss Central
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBDS-2729?page=com.atlassian.jira.plugin.... ]
Fred Bricon commented on JBDS-2729:
-----------------------------------
while testing the kitchensink-backbone 2.4.0 final, I found an annoying bug affecting the jquery mobile flavor : blank row added at the top of the member table (JDF-557).
For JBT/JBDS we can either point at the buggy QS or fork it and serve the fixed version out of JBoss Central. WDYT?
> Add mobile web quickstarts for JBoss Central
> --------------------------------------------
>
> Key: JBDS-2729
> URL: https://issues.jboss.org/browse/JBDS-2729
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: aerogear-hybrid, central, requirements
> Reporter: Burr Sutter
> Assignee: Fred Bricon
> Fix For: 7.1.0.GA
>
>
> The mobile web quickstarts being proced on WFK2 side should be included in JBoss 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
12 years, 6 months
[JBoss JIRA] (JBIDE-15295) EAP 6.1 maven repo not recognized for use with Java EE Web Project wizard
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15295?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-15295:
-------------------------------------
We're gonna hard code specific dependency version checks for repos with missing metadata, since we can't use version ranges for those.
> EAP 6.1 maven repo not recognized for use with Java EE Web Project wizard
> -------------------------------------------------------------------------
>
> Key: JBIDE-15295
> URL: https://issues.jboss.org/browse/JBIDE-15295
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven, project-examples
> Affects Versions: 4.1.0.Final
> Reporter: Michelle Murray
> Assignee: Fred Bricon
> Fix For: 4.1.1.CR1
>
> Attachments: Maven_EAP61.png, Maven_warning.png, settings.xml
>
>
> For the Java EE Web Project wizard, the EAP 6.1 maven repo is not recognized as being a JBoss Enterprise Maven repository.
> The project states that it can be used with EAP 6 so I would assume this to include EAP 6.0 and 6.1.
> Attached are:
> * my settings.xml file, with profiles generated by JBDS 'Configure Maven Repositories'
> * screenshot of added EAP 6.1 maven repo
> * Screenshot of enterprise maven repo warning in Java EE Web Project wizard
--
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, 6 months
[JBoss JIRA] (JBIDE-15908) Problem decorator is not removed after error was fixed
by Xavier Coulon (JIRA)
Xavier Coulon created JBIDE-15908:
-------------------------------------
Summary: Problem decorator is not removed after error was fixed
Key: JBIDE-15908
URL: https://issues.jboss.org/browse/JBIDE-15908
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: webservices
Affects Versions: 4.1.1.Beta1
Reporter: Xavier Coulon
Assignee: Xavier Coulon
Fix For: 4.1.1.CR1
Create a JAX-RS validation error such as
{code}
@GET
@Path("/{id}")
public AttendeeRepresentation getAttendee(@PathParam("ide") final int id) {
...
}
{code}
ASSERT: an error decorator appears on the JAX-RS Endpoint in the project explorer.
Fix the problem (change "ide" -> "id")
ASSERT: the error decorator should disappear
FAIL the error decorator remains visible.
--
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, 6 months
[JBoss JIRA] (JBDS-2710) 3rd party certification for JBDS 7.1.0.GA
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2710?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-2710:
-----------------------------
Description:
For JBDS 7.1.0.GA, we need to ensure this list is as current and up to date as possible.
Proposed *new* connectors for JBDS 8.0:
* SpringSource's Quick Search - JBDS-2686 (affects JBDS installer/Central TP) :: *DROPPED FOR 7.1, TBD for 8.0*
*New* connector for JBDS 7.1:
* Mylyn Builds Connector: Hudson/Jenkins org.eclipse.mylyn.hudson.feature 1.1.1.v20130917-0100 - JBDS-2724, JBDS-2752 :: Approved, will be in 7.1.0.Beta1
* m2e-wro4j 1.0.2 connector - JBDS-2577 :: TBD
The current list of connectors in 7.0 *which can be / have been updated* in 7.1 are:
*Beta1*
* atlassian/3.2.1.v20130402 --> 3.2.2.v20130909 - JBIDE-13682, JBDS-2774 :: Approved, will be in 7.1.0.Beta1 (affects JBT/JBDS/Central TP)
* pmd/4.0.0.v20130510-1000 --> 4.0.1 - JBIDE-14902, JBIDE-15353 :: Approved, will be in 7.1.0.Beta1
* testng/6.8.1.20130330_0839/ --> 6.8.6.20130914_0724 - JBDS-2415, JBDS-2800 :: Approved, will be in 7.1.0.Beta1 (affects JBDS installer/Central TP)
*CR1*
* VJET 0.10.0.x --> 0.10.0.201309201624 - JBIDE-14764, JBIDE-15677 (0.10.0.201309201624 will appear in CR1)
* eclipsecs/5.6.0.201209221626 (Removed in JBIDE-14799 due to Kepler incompatibility) --> 5.6.1.201306282206 - JBIDE-15128, JBIDE-15129 (added for CR1)
* springide/3.3.0.201307091516-RELEASE --> 3.4.0.201310051539-RELEASE - JBDS-2690¥, JBDS-2691¥, JBDS-2802, JBDS-2808, JBDS-2719
*CR1 or GA, TBD*
* gwt/3.2.3.v201304260926-rel-r42 --> 3.4.2.v201310081840-rel-r42 or 3.4.2.v201310081834-rel-r43 - JBDS-2486, JBDS-2801 (affects JBT/JBDS/Central TP)
* subclipse/1.8.20_1.7.9.1 --> 1.10_1.8 - JBDS-2485, JBDS-2709
These are currently unchanged since December when we released JBDS 6.0.0:
* findbugs/2.0.2.20121210 - nothing new as of 2013.10.15
Additionally (Target Platform):
* swtbot 2.1.1.201305311053 / junit4 - JBIDE-13843 (included in JBT TP; needed for running UI tests)
** Could move up to 2.1.1.201307101628 or 2.1.2.201310__ if we want... - http://wiki.eclipse.org/SWTBot#Latest_snapshot_build
JBoss Tools Locus (for use with Teiid in JBT-IS/JBDS-IS only):
* mockito/1.9.5 - JBIDE-12971¥ (to be included in JBT Locus 1.0.0 [1,2,3])
* fest-assert/1.4 & fest-util/1.1.6 - JBIDE-12972¥ (to be included in JBT Locus 1.0.1 [1,2,3])
See comments below for latest site URLs.
[1] https://github.com/jbosstools/jbosstools-locus/
[2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-locus.sit...
[3] http://download.jboss.org/jbosstools/updates/nightly/locus/trunk/
¥ - These issues did not block the release of JBDS 7.0.0.GA, and therefore would not block 7.1.0, but might be fixed by upgrading to SpringIDE 3.4.
was:
For JBDS 7.1.0.GA, we need to ensure this list is as current and up to date as possible.
Proposed *new* connectors for JBDS 8.0:
* SpringSource's Quick Search - JBDS-2686 (affects JBDS installer/Central TP) :: *DROPPED FOR 7.1, TBD for 8.0*
*New* connector for JBDS 7.1:
* Mylyn Builds Connector: Hudson/Jenkins org.eclipse.mylyn.hudson.feature 1.1.1.v20130917-0100 - JBDS-2724, JBDS-2752 :: Approved, will be in 7.1.0.Beta1
The current list of connectors in 7.0 *which can be / have been updated* in 7.1 are:
*Beta1*
* atlassian/3.2.1.v20130402 --> 3.2.2.v20130909 - JBIDE-13682, JBDS-2774 :: Approved, will be in 7.1.0.Beta1 (affects JBT/JBDS/Central TP)
* pmd/4.0.0.v20130510-1000 --> 4.0.1 - JBIDE-14902, JBIDE-15353 :: Approved, will be in 7.1.0.Beta1
* testng/6.8.1.20130330_0839/ --> 6.8.6.20130914_0724 - JBDS-2415, JBDS-2800 :: Approved, will be in 7.1.0.Beta1 (affects JBDS installer/Central TP)
*CR1*
* VJET 0.10.0.x --> 0.10.0.201309201624 - JBIDE-14764, JBIDE-15677 (0.10.0.201309201624 will appear in CR1)
* eclipsecs/5.6.0.201209221626 (Removed in JBIDE-14799 due to Kepler incompatibility) --> 5.6.1.201306282206 - JBIDE-15128, JBIDE-15129 (added for CR1)
* springide/3.3.0.201307091516-RELEASE --> 3.4.0.201310051539-RELEASE - JBDS-2690¥, JBDS-2691¥, JBDS-2802, JBDS-2808, JBDS-2719
*CR1 or GA, TBD*
* gwt/3.2.3.v201304260926-rel-r42 --> 3.4.2.v201310081840-rel-r42 or 3.4.2.v201310081834-rel-r43 - JBDS-2486, JBDS-2801 (affects JBT/JBDS/Central TP)
* subclipse/1.8.20_1.7.9.1 --> 1.10_1.8 - JBDS-2485, JBDS-2709
These are currently unchanged since December when we released JBDS 6.0.0:
* findbugs/2.0.2.20121210 - nothing new as of 2013.10.15
Additionally (Target Platform):
* swtbot 2.1.1.201305311053 / junit4 - JBIDE-13843 (included in JBT TP; needed for running UI tests)
** Could move up to 2.1.1.201307101628 or 2.1.2.201310__ if we want... - http://wiki.eclipse.org/SWTBot#Latest_snapshot_build
JBoss Tools Locus (for use with Teiid in JBT-IS/JBDS-IS only):
* mockito/1.9.5 - JBIDE-12971¥ (to be included in JBT Locus 1.0.0 [1,2,3])
* fest-assert/1.4 & fest-util/1.1.6 - JBIDE-12972¥ (to be included in JBT Locus 1.0.1 [1,2,3])
See comments below for latest site URLs.
[1] https://github.com/jbosstools/jbosstools-locus/
[2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-locus.sit...
[3] http://download.jboss.org/jbosstools/updates/nightly/locus/trunk/
¥ - These issues did not block the release of JBDS 7.0.0.GA, and therefore would not block 7.1.0, but might be fixed by upgrading to SpringIDE 3.4.
> 3rd party certification for JBDS 7.1.0.GA
> -----------------------------------------
>
> Key: JBDS-2710
> URL: https://issues.jboss.org/browse/JBDS-2710
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: 3rd-party-certification, 3rd-party-dependencies, requirements
> Affects Versions: 7.0.0.GA
> Reporter: Max Rydahl Andersen
> Assignee: Len DiMaggio
> Priority: Blocker
> Fix For: 7.1.0.GA
>
>
> For JBDS 7.1.0.GA, we need to ensure this list is as current and up to date as possible.
> Proposed *new* connectors for JBDS 8.0:
> * SpringSource's Quick Search - JBDS-2686 (affects JBDS installer/Central TP) :: *DROPPED FOR 7.1, TBD for 8.0*
> *New* connector for JBDS 7.1:
> * Mylyn Builds Connector: Hudson/Jenkins org.eclipse.mylyn.hudson.feature 1.1.1.v20130917-0100 - JBDS-2724, JBDS-2752 :: Approved, will be in 7.1.0.Beta1
> * m2e-wro4j 1.0.2 connector - JBDS-2577 :: TBD
> The current list of connectors in 7.0 *which can be / have been updated* in 7.1 are:
> *Beta1*
> * atlassian/3.2.1.v20130402 --> 3.2.2.v20130909 - JBIDE-13682, JBDS-2774 :: Approved, will be in 7.1.0.Beta1 (affects JBT/JBDS/Central TP)
> * pmd/4.0.0.v20130510-1000 --> 4.0.1 - JBIDE-14902, JBIDE-15353 :: Approved, will be in 7.1.0.Beta1
> * testng/6.8.1.20130330_0839/ --> 6.8.6.20130914_0724 - JBDS-2415, JBDS-2800 :: Approved, will be in 7.1.0.Beta1 (affects JBDS installer/Central TP)
> *CR1*
> * VJET 0.10.0.x --> 0.10.0.201309201624 - JBIDE-14764, JBIDE-15677 (0.10.0.201309201624 will appear in CR1)
> * eclipsecs/5.6.0.201209221626 (Removed in JBIDE-14799 due to Kepler incompatibility) --> 5.6.1.201306282206 - JBIDE-15128, JBIDE-15129 (added for CR1)
> * springide/3.3.0.201307091516-RELEASE --> 3.4.0.201310051539-RELEASE - JBDS-2690¥, JBDS-2691¥, JBDS-2802, JBDS-2808, JBDS-2719
> *CR1 or GA, TBD*
> * gwt/3.2.3.v201304260926-rel-r42 --> 3.4.2.v201310081840-rel-r42 or 3.4.2.v201310081834-rel-r43 - JBDS-2486, JBDS-2801 (affects JBT/JBDS/Central TP)
> * subclipse/1.8.20_1.7.9.1 --> 1.10_1.8 - JBDS-2485, JBDS-2709
> These are currently unchanged since December when we released JBDS 6.0.0:
> * findbugs/2.0.2.20121210 - nothing new as of 2013.10.15
> Additionally (Target Platform):
> * swtbot 2.1.1.201305311053 / junit4 - JBIDE-13843 (included in JBT TP; needed for running UI tests)
> ** Could move up to 2.1.1.201307101628 or 2.1.2.201310__ if we want... - http://wiki.eclipse.org/SWTBot#Latest_snapshot_build
> JBoss Tools Locus (for use with Teiid in JBT-IS/JBDS-IS only):
> * mockito/1.9.5 - JBIDE-12971¥ (to be included in JBT Locus 1.0.0 [1,2,3])
> * fest-assert/1.4 & fest-util/1.1.6 - JBIDE-12972¥ (to be included in JBT Locus 1.0.1 [1,2,3])
> See comments below for latest site URLs.
> [1] https://github.com/jbosstools/jbosstools-locus/
> [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-locus.sit...
> [3] http://download.jboss.org/jbosstools/updates/nightly/locus/trunk/
> ¥ - These issues did not block the release of JBDS 7.0.0.GA, and therefore would not block 7.1.0, but might be fixed by upgrading to SpringIDE 3.4.
--
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, 6 months