Target Platform Updates :: It's Time To Test Indigo SR2!
by Nick Boldt
With Xmas just around the corner, holiday shutdowns coming, and Indigo
SR2 being released February 24 2012 [1], the runway to get fixes into
Eclipse, WTP, DTP, BIRT, RSE, Mylyn, etc. is increasingly short.
[1] http://wiki.eclipse.org/Indigo/Simultaneous_Release_Plan#SR2
Based on their RC schedule, and how hard it is to get fixes done during
the RC cycle, I would say the hard deadline for ANYTHING to be fixed in
Eclipse.org upstream bits is *January 13*, which means you need to get
bugs filed, if necessary, at least a week or two before that.
To that end, I'd like to have people start testing their builds locally
w/ the latest Eclipse Indigo [2] bits.
[2] http://download.eclipse.org/releases/maintenance/
In the next few days, I'll put together a new composite requirements
site [3] and TP [4] using these updated versions so it'll be easier to
test w/o being restricted by Eclipse.org mirrors.
[3] http://download.jboss.org/jbosstools/updates/indigo/SR1/,
http://download.jboss.org/jbosstools/updates/indigo/extras/SR1a/
[4] http://download.jboss.org/jbosstools/updates/target-platform_3.3.indigo/
---
As a reminder, should you feel you need something added to (or updated
in) the TP or reqs composite sites to facilitate building, running,
installing, or testing any part of JBoss Tools (or Developer Studio),
PLEASE ASK FIRST via direct email, mailing list, or JIRA.
We recently found a new requirement on a JDT patch feature, which I
erroneously added to the TP assuming that it should have been there. I
tend to assume any new requirements are added intentionally, but we need
to ensure we're properly communicating so that accidental dependencies
aren't added and cause build issues.
---
For reference, here are the latest updates to the TP over the last
month, based on svn log data:
11/28: remove org.eclipse.objectteams.otdt.core.patch
11/25: add org.eclipse.objectteams.otdt.core.patch
11/23: BPEL updated from 0.5 to 0.8
11/07: Mylyn/JIRA added (JBIDE-9351, JBIDE-10094)
10/27: Mylyn
10/26: Mylyn eGit connector (JBDS-1904)
10/25: apache.commons.io 2.0.1 added
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
12 years, 11 months
Fwd: Hibernate multi-version support
by Max Rydahl Andersen
This should go to jbosstools-dev
Begin forwarded message:
> From: Dmitry Geraskov <dgeraskov(a)exadel.com>
> Subject: Hibernate multi-version support
> Date: November 30, 2011 24:16:13 GMT+01:00
> Cc: max.andersen(a)redhat.com, dgolovin(a)exadel.com
>
> Hey, guys,
>
> please be aware,
> we are going to commit to trunk merged version of our hibernate multi-version implementation(the original branch is /branches/hibernate-multiversion2).
> Locally we have fixed all problems with tests, but we need to check hudson results for the trunk build, hibernatetools component build and dependent components builds, for ex seam.
>
> Dmitry
/max
http://about.me/maxandersen
13 years
Re: [jbosstools-dev] wrong .project location in bpel
by Max Rydahl Andersen
> Yeah sorry Max, this was checked in by mistake.
>
No worries. thanks for confirming :)
p.s. I added in jbosstools-dev@ so the thread is visible to others and the archives.
/max
> ----- Original Message -----
>> Hey Bob,
>>
>> couldn't figure out why I didn't see the new bpel stuff when
>> importing jbosstools/trunk.
>>
>> Turned out you committed a .project file for it called
>> org.eclipse.bpel-trunk when the bpel merge occurred.
>>
>> I *assume* that is an error since eclipse won't import it together
>> with the other plugins.
>>
>> Thus I removed it to make it visible on import of projects.
>>
>> there doesn't seem to be any other eclipse project metadata in there
>> so looks like an error.
>>
>> Let me know if there were some magic reason for it being there I
>> missed ?
>>
>> /max
>> http://about.me/maxandersen
>>
>>
>>
>>
/max
http://about.me/maxandersen
13 years
About resource leaks issues on JBIDE-10221
by Max Rydahl Andersen
Hi Viatli,
Thanks for running sleak on parts of jboss tools and reporting it in https://issues.jboss.org/browse/JBIDE-10221
and subissues.
But please, could you avoid opening issues with nothing but a source line and not pointing out where the problem
is nor, how severe it is nor what the suggested solution is.
I've set the fix version to Beta1 to look at them, but please if you got more info on those bugs with no info beyond a code line
please add or close them.
/max
http://about.me/maxandersen
13 years
