[JBoss JIRA] (JBIDE-16132) XCode library search path is not set properly
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16132?page=com.atlassian.jira.plugi... ]
Gorkem Ercan resolved JBIDE-16132.
----------------------------------
Resolution: Done
> XCode library search path is not set properly
> ---------------------------------------------
>
> Key: JBIDE-16132
> URL: https://issues.jboss.org/browse/JBIDE-16132
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.1.1.CR1
> Reporter: Gorkem Ercan
> Assignee: Gorkem Ercan
> Priority: Critical
> Labels: respin-b
> Fix For: 4.1.1.CR1
>
>
> If a Cordova plugin adds a custom framework as a dependency for iOS the project fails to run and the exported XCode project does not compile.
> This is because the iOS project generator does not set the library search paths properly for custom frameworks.
> Aerogear Push Plugin now uses such a framework.
--
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
10 years, 5 months
[JBoss JIRA] (JBIDE-16093) NPEs when compiling wildfly codebase
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16093?page=com.atlassian.jira.plugi... ]
Snjezana Peco commented on JBIDE-16093:
---------------------------------------
The PR has been applied to the 4.1.1.x branch too.
> NPEs when compiling wildfly codebase
> ------------------------------------
>
> Key: JBIDE-16093
> URL: https://issues.jboss.org/browse/JBIDE-16093
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: testing-tools
> Affects Versions: 4.1.1.CR1
> Reporter: Andre Dietisheim
> Assignee: Max Rydahl Andersen
> Priority: Critical
> Labels: respin-b
> Fix For: 4.1.1.CR1, 4.2.0.Alpha1
>
> Attachments: .log, npes-building-wildfly-2.png, npes-building-wildfly.png
>
>
> When having arquillian org.jboss.tools.arquillian.core_1.0.5.CR1-v20131116-1823-B79 installed and building the wildfly workspace I run into several NPEs caused by arquillian.
> !npes-building-wildfly.png!
> !npes-building-wildfly-2.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
10 years, 5 months
[JBoss JIRA] (JBIDE-16093) NPEs when compiling wildfly codebase
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16093?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-16093 at 11/29/13 1:04 PM:
--------------------------------------------------------------
[~snjeza]:
The 4.1.x branch is for 4.1.2 builds that will start in February.
The 4.1.1.x branch is for 4.1.1.CR1 -> 4.1.1.Final builds that are going on now.
You must push this into the 4.1.1.x branch if you want it fixed in 4.1.1.Final.
was (Author: nickboldt):
4.1.x branch is for 4.1.2 builds that will start in February.
4.1.1.x branch is for 4.1.1.CR1 -> 4.1.1.Final builds that are going on now.
You must push this into the 4.1.1.x branch if you want it fixed in 4.1.1.Final.
> NPEs when compiling wildfly codebase
> ------------------------------------
>
> Key: JBIDE-16093
> URL: https://issues.jboss.org/browse/JBIDE-16093
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: testing-tools
> Affects Versions: 4.1.1.CR1
> Reporter: Andre Dietisheim
> Assignee: Max Rydahl Andersen
> Priority: Critical
> Labels: respin-b
> Fix For: 4.1.1.CR1, 4.2.0.Alpha1
>
> Attachments: .log, npes-building-wildfly-2.png, npes-building-wildfly.png
>
>
> When having arquillian org.jboss.tools.arquillian.core_1.0.5.CR1-v20131116-1823-B79 installed and building the wildfly workspace I run into several NPEs caused by arquillian.
> !npes-building-wildfly.png!
> !npes-building-wildfly-2.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
10 years, 5 months
[JBoss JIRA] (JBIDE-16093) NPEs when compiling wildfly codebase
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16093?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-16093:
------------------------------------
4.1.x branch is for 4.1.2 builds that will start in February.
4.1.1.x branch is for 4.1.1.CR1 -> 4.1.1.Final builds that are going on now.
You must push this into the 4.1.1.x branch if you want it fixed in 4.1.1.Final.
> NPEs when compiling wildfly codebase
> ------------------------------------
>
> Key: JBIDE-16093
> URL: https://issues.jboss.org/browse/JBIDE-16093
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: testing-tools
> Affects Versions: 4.1.1.CR1
> Reporter: Andre Dietisheim
> Assignee: Max Rydahl Andersen
> Priority: Critical
> Labels: respin-b
> Fix For: 4.1.1.CR1, 4.2.0.Alpha1
>
> Attachments: .log, npes-building-wildfly-2.png, npes-building-wildfly.png
>
>
> When having arquillian org.jboss.tools.arquillian.core_1.0.5.CR1-v20131116-1823-B79 installed and building the wildfly workspace I run into several NPEs caused by arquillian.
> !npes-building-wildfly.png!
> !npes-building-wildfly-2.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
10 years, 5 months
[JBoss JIRA] (JBIDE-16161) Tycho tests require org.eclipse.osgi.compatibility.state fragment on Luna
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16161?page=com.atlassian.jira.plugi... ]
Mickael Istria edited comment on JBIDE-16161 at 11/29/13 1:00 PM:
------------------------------------------------------------------
See https://bugs.eclipse.org/bugs/show_bug.cgi?id=417429 , CompatibilityEditor should not depend on PlatformAdmin in the future. I guess your help on this issue on Platform side would be welcome.
So that means that hopefully, by 4.4.M4, this fragment won't be necessary any more, and will slowly disappear.
But until then the only workaround is to add the <dependency> to tycho-surefire-plugin as you suggested. But since some tests are working fine without it, and as you said, it's not easy to understand why a test is failing, I prefer avoiding enabling it by default and have it only added to the relevant surefire executions where it is necessary. It will be easier to figure out which tests actually require it.
I'll send a mail to jbosstools-dev to ask people who have failing tests to try with this bundle.
was (Author: mickael_istria):
See https://bugs.eclipse.org/bugs/show_bug.cgi?id=417429 , CompatibilityEditor should not depend on PlatformAdmin in the future. I guess your help on this issue on Platform side would be welcome.
So that means that hopefully, by 4.4.M4, this fragment won't be necessary any more, and will slowly disappear.
But until then the only workaround is to add the <dependency> to tycho-surefire-plugin as you suggestion. But since some tests are working fine without it, and as you said, it's not easy to understand why a test is failing, I prefer avoiding enabling it by default and have it only added to the relevant surefire executions where it is necessary. It will be easier to figure out which tests actually require it.
I'll send a mail to jbosstools-dev to ask people who have failing tests to try with this bundle.
> Tycho tests require org.eclipse.osgi.compatibility.state fragment on Luna
> -------------------------------------------------------------------------
>
> Key: JBIDE-16161
> URL: https://issues.jboss.org/browse/JBIDE-16161
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.2.0.Alpha1
> Reporter: Snjezana Peco
> Assignee: Mickael Istria
>
> Since Tycho requires the PlatformAdmin service, we have to add the org.eclipse.osgi.compatibility.state fragment to tycho-surefire-plugin.
> The easiest way is to add the org.eclipse.e4.rcp feature to the main build.
--
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
10 years, 5 months
[JBoss JIRA] (JBIDE-16161) Tycho tests require org.eclipse.osgi.compatibility.state fragment on Luna
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16161?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-16161:
----------------------------------------
See https://bugs.eclipse.org/bugs/show_bug.cgi?id=417429 , CompatibilityEditor should not depend on PlatformAdmin in the future. I guess your help on this issue on Platform side would be welcome.
So that means that hopefully, by 4.4.M4, this fragment won't be necessary any more, and will slowly disappear.
But until then the only workaround is to add the <dependency> to tycho-surefire-plugin as you suggestion. But since some tests are working fine without it, and as you said, it's not easy to understand why a test is failing, I prefer avoiding enabling it by default and have it only added to the relevant surefire executions where it is necessary. It will be easier to figure out which tests actually require it.
I'll send a mail to jbosstools-dev to ask people who have failing tests to try with this bundle.
> Tycho tests require org.eclipse.osgi.compatibility.state fragment on Luna
> -------------------------------------------------------------------------
>
> Key: JBIDE-16161
> URL: https://issues.jboss.org/browse/JBIDE-16161
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.2.0.Alpha1
> Reporter: Snjezana Peco
> Assignee: Mickael Istria
>
> Since Tycho requires the PlatformAdmin service, we have to add the org.eclipse.osgi.compatibility.state fragment to tycho-surefire-plugin.
> The easiest way is to add the org.eclipse.e4.rcp feature to the main build.
--
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
10 years, 5 months
[JBoss JIRA] (JBIDE-16161) Tycho tests require org.eclipse.osgi.compatibility.state fragment on Luna
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16161?page=com.atlassian.jira.plugi... ]
Snjezana Peco commented on JBIDE-16161:
---------------------------------------
{quote}
I agree, but I feel it's better to look for the more sustainable solution (Wiring API) instead of the easiest one.
{quote}
I think, we can't easily fix the issue in the tests since it can happen in some plugin that is used by a test (many JBT plugins use CompatibilityEditor that requires the compatibility fragment, for instance).
In this moment, the easiest way to fix the issue is to add the compatibility fragment. That can be done by adding the o.e.e4.rcp feature or by some other way. Any other solution would require a lot of changes in the JBT tests and plugins.
{quote}
See for example https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
{quote}
Openshift probably uses an older version of the server (and base) component since those components aren't built.
The compatibility fragment can be added to particular tests. However, it is not easy to determine whether a test fails due to the missing compatibility fragment or for some other reason.
> Tycho tests require org.eclipse.osgi.compatibility.state fragment on Luna
> -------------------------------------------------------------------------
>
> Key: JBIDE-16161
> URL: https://issues.jboss.org/browse/JBIDE-16161
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.2.0.Alpha1
> Reporter: Snjezana Peco
> Assignee: Mickael Istria
>
> Since Tycho requires the PlatformAdmin service, we have to add the org.eclipse.osgi.compatibility.state fragment to tycho-surefire-plugin.
> The easiest way is to add the org.eclipse.e4.rcp feature to the main build.
--
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
10 years, 5 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 commented on JBDS-2710:
----------------------------------
Current set of 3rd Party inclusions in JBoss Central / JBT TP / JBDS TP for JBDS 7.1.0.CR1, as of 2013.11.21:
*New* for JBDS 7.1.0.CR1:
* 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 :: Approved for 7.1.0.CR1
*Updated* in JBDS 7.1.0.CR1:
* atlassian/3.2.2.v20130909 - JBIDE-13682, JBDS-2774
* pmd/4.0.1 - JBIDE-14902, JBIDE-15353
* testng/6.8.6.20130914_0724 - JBDS-2415, JBDS-2800 (included in JBDS installer)
* VJET/0.10.0.201309201624 (Experimental / Incubating) - JBIDE-14764, JBIDE-15677
* eclipsecs/5.6.1.201306282206 - JBIDE-15128, JBIDE-15129
* springide/3.4.0.201310051539-RELEASE - JBDS-2690, JBDS-2691, JBDS-2802, JBDS-2808, JBDS-2719
* gwt/3.4.2.v201310081834-rel-r43 - JBDS-2486, JBDS-2801
* Subclipse/SVNKit 1.10_1.8 - JBDS-2709 *{color:green}NEW!{color}* - added to new Central TP version 4.31.0.Final-SNAPSHOT
*Unchanged* in JBDS 7.1.0.CR1 (as in JBDS 7.0.0):
* findbugs/2.0.2.20121210 - nightly builds of 2.0.3 are available but no new release as of 2013.11.21
*Deferred / NOT in JBDS 7.1.0.CR1*
* SpringSource's Quick Search - JBDS-2686 (affects JBDS installer/Central TP) :: DROPPED FOR 7.1, TBD for 8.0
> 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* connectors 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 :: Approved for 7.1.0.CR1
> 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
> * gwt/3.2.3.v201304260926-rel-r42 --> 3.4.2.v201310081834-rel-*r43 ONLY* - JBDS-2486, JBDS-2801 (affects JBT/JBDS/Central TP)
> *CR1 or GA, TBD*
> * 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
10 years, 5 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 edited comment on JBDS-2710 at 11/29/13 12:01 PM:
-------------------------------------------------------------
Current set of 3rd Party inclusions in JBoss Central / JBT TP / JBDS TP for JBDS 7.1.0.CR1, as of 2013.11.29:
*New* for JBDS 7.1.0.CR1:
* 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 :: Approved for 7.1.0.CR1
*Updated* in JBDS 7.1.0.CR1:
* atlassian/3.2.2.v20130909 - JBIDE-13682, JBDS-2774
* pmd/4.0.1 - JBIDE-14902, JBIDE-15353
* testng/6.8.6.20130914_0724 - JBDS-2415, JBDS-2800 (included in JBDS installer)
* VJET/0.10.0.201309201624 (Experimental / Incubating) - JBIDE-14764, JBIDE-15677
* eclipsecs/5.6.1.201306282206 - JBIDE-15128, JBIDE-15129
* springide/3.4.0.201310051539-RELEASE - JBDS-2690, JBDS-2691, JBDS-2802, JBDS-2808, JBDS-2719
* gwt/3.4.2.v201310081834-rel-r43 - JBDS-2486, JBDS-2801
* Subclipse/SVNKit 1.10_1.8 - JBDS-2709 *{color:green}NEW!{color}* - added to new Central TP version 4.31.0.Final-SNAPSHOT
*Unchanged* in JBDS 7.1.0.CR1 (as in JBDS 7.0.0):
* findbugs/2.0.2.20121210 - nightly builds of 2.0.3 are available but no new release as of 2013.11.21
*Deferred / NOT in JBDS 7.1.0.CR1*
* SpringSource's Quick Search - JBDS-2686 (affects JBDS installer/Central TP) :: DROPPED FOR 7.1, TBD for 8.0
was (Author: nickboldt):
Current set of 3rd Party inclusions in JBoss Central / JBT TP / JBDS TP for JBDS 7.1.0.CR1, as of 2013.11.21:
*New* for JBDS 7.1.0.CR1:
* 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 :: Approved for 7.1.0.CR1
*Updated* in JBDS 7.1.0.CR1:
* atlassian/3.2.2.v20130909 - JBIDE-13682, JBDS-2774
* pmd/4.0.1 - JBIDE-14902, JBIDE-15353
* testng/6.8.6.20130914_0724 - JBDS-2415, JBDS-2800 (included in JBDS installer)
* VJET/0.10.0.201309201624 (Experimental / Incubating) - JBIDE-14764, JBIDE-15677
* eclipsecs/5.6.1.201306282206 - JBIDE-15128, JBIDE-15129
* springide/3.4.0.201310051539-RELEASE - JBDS-2690, JBDS-2691, JBDS-2802, JBDS-2808, JBDS-2719
* gwt/3.4.2.v201310081834-rel-r43 - JBDS-2486, JBDS-2801
* Subclipse/SVNKit 1.10_1.8 - JBDS-2709 *{color:green}NEW!{color}* - added to new Central TP version 4.31.0.Final-SNAPSHOT
*Unchanged* in JBDS 7.1.0.CR1 (as in JBDS 7.0.0):
* findbugs/2.0.2.20121210 - nightly builds of 2.0.3 are available but no new release as of 2013.11.21
*Deferred / NOT in JBDS 7.1.0.CR1*
* SpringSource's Quick Search - JBDS-2686 (affects JBDS installer/Central TP) :: DROPPED FOR 7.1, TBD for 8.0
> 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* connectors 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 :: Approved for 7.1.0.CR1
> 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
> * gwt/3.2.3.v201304260926-rel-r42 --> 3.4.2.v201310081834-rel-*r43 ONLY* - JBDS-2486, JBDS-2801 (affects JBT/JBDS/Central TP)
> *CR1 or GA, TBD*
> * 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
10 years, 5 months