ACTION REQUIRED: Prevent your component from installing in Luna (if it's incompatible w/ Luna APIs) :: JBIDE-16082
by Nick Boldt
TL;DR:
If your component:
* has to change in the *master branch* in order to *compile with* or
*install to* Eclipse 4.4 (Luna)
You must:
* ensure that in BOTH the *4.1.x and 4.1.1.x branches* it will NOT be
*installable* into Luna. See JBIDE-16082.
Please make this change in time for the CR1a respin (by EOD, Friday Nov 22).
----
Details:
In JBIDE-15639, a number of components have been shown to not compile w/
Luna: Server, Arquillian, Hibernate, Forge.
These components must therefore be updated in master branch (for JBT 4.2
/ JBDS 8.0) to be compilable w/ Luna (Eclipse 4.4). This ongoing work
needs to be done by next week's code freeze.
But the converse should be true, too: if the code must change in master
to *compile* with Luna, then the Kepler-based release should *probably*
not be *installable* into Luna either. Component leads, you're the
experts for your own code.
If you agree, then please adjust one or more MANIFEST.MF files to set an
upper bound limit on a Bundle-Require, which will prevent your component
from being installed into Luna.
Here's an example of how to *verify you've prevented your component from
installing into Luna*:
https://issues.jboss.org/browse/JBIDE-16081
If you disagree with the above, because your component depends on
*nothing that changed between Kepler and Luna*, then you can reject the
appropriate JIRA for your project:
Forge: https://issues.jboss.org/browse/JBIDE-16083
Hibernate: https://issues.jboss.org/browse/JBIDE-16084
Server: https://issues.jboss.org/browse/JBIDE-16085
Arquillian: https://issues.jboss.org/browse/JBIDE-16086
If I've missed adding your component - and you feel your 4.1.x component
should ALSO not be installable to Luna - please create a subtask under
this JIRA:
https://issues.jboss.org/browse/JBIDE-16082
If you discover that your component *cannot be compiled w/ Luna* - and
it's not already reported - please add a subtask or linked issue to this
JIRA:
https://issues.jboss.org/browse/JBIDE-15639
Any questions, please don't hesitate to ask here, JIRA, IRC, or twitter.
N
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
12 years, 3 months
Linux users, please start using Eclipse 4.4.M3
by Mickael Istria
Hi all,
Eclipse 4.4.M3 has been released last week. It contains a big (good)
change for Linux users: implementation of SWT against GTK3 instead of
GTK2. This is mostly perfect, but there are still a few glitches (this
required a lot of changes, so even the most careful developers could
miss some things).
It would be helpful if you could start using this 4.4.M3 as an IDE for
JBT/JBDS and report any bug you notice to
https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Platform . The
sooner they get fixed in Eclipse, the less bad surprise and pain we'll
have for JBoss Tools and JBoss Developer Studio.
FYI, this change was implemented and is maintained by the Eclipse Fedora
team at Red Hat, and the 4.40.Alpha1-SNAPSHOT will soon use this new
implementation of SWT.
Last point to convince you: Eclipse looks nicer with GTK3 than it does
with GTK2 ;)
--
Mickael Istria
Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
My blog <http://mickaelistria.wordpress.com> - My Tweets
<http://twitter.com/mickaelistria>
12 years, 3 months
ACTION REQUIRED: Upcoming code freeze for JBoss Tools 4.2 Alpha1 :: Thursday, November 28
by Nick Boldt
I know we're barely half way through the testing cycle for JBT
4.1.1.CR1, but in order to be able to get a first Alpha for JBT 4.2 out
by year's end, we need to start looking at building JBT 4.2 on Luna ASAP.
To that end, Mickael will be producing a new Luna M3 target platform
this week - watch for that email w/ instructions. You can of course use
the current Luna M2 target platform if you're eager.
The goal is to test building your projects w/ Luna, so that if you're a
project who tends to be broken every year by upstream API changes in
platform or WTP (eg., hibernate tools), you can find those problems and
fix them ASAP. Or if necessary, report problems upstream.
If all goes to plan, the hope is to have a JBT 4.2.0.Alpha1 build by the
first week of December.
Stay tuned!
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
12 years, 3 months
ACTION REQUIRED: N&N for CR1/GA
by Max Rydahl Andersen
Hey,
N&N main jira been created at https://issues.jboss.org/browse/JBIDE-15981
I believe most would just be a reject/close since nothing changed but I know
a few plugins added a few features to handled things based on QE and testing feedback.
Michelle (doc) is requesting we get these in as quickly as possible so she can be aware
of anything that can affect the last work on the docs.
Thanks,
Max
12 years, 3 months
Action Required: Don't change the IDE look/behavior ahead of 7.1.0/4.1.1 GA
by Michelle Murray
In preparation for GA, I am beginning the arduous task of verifying the text and graphics in the JBDS/JBT guides. This will take approximately 40 hours. It involves checking that the installer and IDE looks and behaves as I have documented and updating any inconsistencies that didn't get flagged in JIRAs or N&N (e.g., icon changes, menu item name changes, extra wizard fields).
So DON'T CHANGE ANYTHING. F rom this point forwards, please refrain from making unnecessary changes to the IDE look/behavior for 7.1.0/4.1.1. If you absolutely have to make a look/behavior change, please contact me directly to alert me to the fact that you are changing something so I can identify any documentation impacts.
I believe there will be very few, if any, IDE look/behavior changes between now and GA since we are at CR1 and in the final bug fixing phase.
I'm aware that the following is an IDE look/behavior change not in the current CR1 build:
* https://issues.jboss.org/browse/JBDS-2821
Thanks for your cooperation,
Michelle
12 years, 3 months
On just updating description in jira...
by Max Rydahl Andersen
Am I the only one that find it extremely hard to follow when we are updating the description instead of simply use comments or subtasks
to provided updates ?
I was looking through jira notifications and I have ~80 changes to JBDS-2710 and each delta lists everything...
Does it show up better for you all ?
Isn't there a better way to track this ? (like a subtask pr. component and if globally relevant add comment to the aggregator ?)
Then you the emails will just contain the actual relevant change and the progress (done or not done) can be seen in the subtask overview ?
Note, i've seen this happen with other jiras too but JBDS-2710 is just the "biggest" one.
/max
----- Forwarded message from "Nick Boldt (JIRA)" <jira-events(a)lists.jboss.org> -----
>From: "Nick Boldt (JIRA)" <jira-events(a)lists.jboss.org>
>To: manderse(a)redhat.com
>Date: Thu, 14 Nov 2013 16:00:08 -0500 (EST)
>Subject: [JBoss JIRA] (JBDS-2710) 3rd party certification for JBDS 7.1.0.GA
Tags: inbox
>
>
> [ 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* 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.
>
> 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
>* 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.
>
>
>
>> 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
----- End forwarded message -----
12 years, 3 months
Running Maven tests against a pre-existing RCP application
by Mickael Istria
Hi all,
With Tycho 0.19.0, we could fix the long-standing issue JBIDE-13869.
This will allow you to run your test with Maven against an RCP
application which is available in your filesystem.
You can do it by simply running for example:
$ cd tests/my.test.bundle
$ mvn clean verify -Dtest.profileName=epp.package.jee
-Dtest.installPath=/home/me/eclipse-4.4.M2
If test.installPath is not set, you get the default surefire behaviour
which is to generate a simple minimal installation to run the tests in
target/work.
More info about the profileName can be found in
http://wiki.eclipse.org/Tycho/Testing_with_Surefire#p2Installed_on_provis...
. This works on any RCP application that relies on p2 (in case you want
to test JBoss Tools inside Websphere Studio ;).
We've configured it so that by default, it is JBDS-friendly and set the
jbds profileName. So to test on JBDS, you can simply use:
$ mvn clean verify
-Dtest.installPath=/home/me/jbdevstudio-8.0.0.Alpha1-SNAPSHOT/studio
Except a few exception, other surefire parameters, such as the very cool
debugPort parameter, can be used together with this mechanism.
Enjoy!
--
Mickael Istria
Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
My blog <http://mickaelistria.wordpress.com> - My Tweets
<http://twitter.com/mickaelistria>
12 years, 4 months