If you update from 3.2.x branch you will get a big chunk of changed directories from my last commit: http://fisheye.jboss.org/changelog/JBossTools?cs=31632
For some reason we again had a bunch of plugins where the svn:ignore was not set and then using eclipse
and svn (without svn plugin install) becomes a nightmare since it starts copying .svn folders and doing diffs becomes a nightmare.
p.s. took me about 2 hours to get that commit in (svn back and forth to be completely in sync) - in the mean time I did 2 pull git requests on and many testruns
on hibernate tools core. we really need to move to git and get our modules selfcontained!
Not sure why it was ever in our source tree but I just removed "thirdparty" since it makes import into eclipse impossible
and the README says "can be safely deleted".
Done in context of JBIDE-9034
Let me know if it somehow affects you and the README by any chance was wrong.
(I haven't looked at trunk yet - will do that later if it is still in there when i get to it)
AS 7 Final is planned to be done end of June, and so is Eclipse Indigo (3.7) meaning
getting a 3.3.0.M2 out in the planned timeframe - we had set 3.3.0.M2 currently planned to be released on 22nd
(same day as AS 7 and Eclipse 3.7 is going out)
Currently Jira has 148 issues open for this release - and almost none on the future releases.
I'm sure you don't all expect to do all 148 issues for M2 and then do nothing for M3, Beta1, Beta2 and CR1.
Could you *please* go over your assigned and component issues and state which ones you are going
to do for M2 and which you are moving of to later ?
That would make it possible to actually see what needs to be done for the release much easier for everyone.
When you do this please remember that 3.3.0.M2 has the primary goals of:
* Running on Eclipse 3.7 final release (i.e. the maven/m2e is currently broken)
* Work with AS 7 (start/stop/debug/run/deploy)
* Not suck
Thus if you are about to do major rework of some components and don't feel you can have it ready in
a not-suck state please do your work in a branch and merge it back to trunk *after* M2.
And those issues that does that are perfect candidates to have their jira fix version updated to M3.
You know the drill ;)
We are still fighting for getting a build for 3.3.0.M1 but that shouldn't prevent anyone from preparing
the whats new and noteworthy for 3.3.0.M1.
I've created https://issues.jboss.org/browse/JBIDE-8886 as usual with each component owner
as subtask owner.
If you component does have changes then add content to trunk/documentation/whatsnew and
add your component to index.html.
If your component does not have any changes then please *reject* the issue don't just resolve it.
About time we got the Forge component in its own category.
Created forge component, lead being Koen Aers.
Koen, please move any forge issues you got into that component - thanks! :)
Sorry for any confusion around the M1 milestone builds for JBDS 4.1/JBoss Tools 3.2.1. We seem to be back on track for the moment as we chug towards the next milestone, CR1 - which happens on 20-MAY-2011. Yes, that date is soon folks. We're on the 10th, that means we have 10 days to get a ton of work done.
Unfortunately, we've not made as much progress whittling down the bug lists as I would have liked.
==JBDS 4.1/JBoss Tools 3.2.1 Bug Status==
In the JBIDE bugs, we have 53 in this list: https://issues.jboss.org/secure/IssueNavigator.jspa?mode=hide&reset=true&...
Those 53 include 4 blockers, 7 critical bugs, 32 major bugs, and 10 minor bugs.
For the JBDS bugs, we're down to 10: https://issues.jboss.org/secure/IssueNavigator.jspa?mode=hide&reset=true&...
That list includes 1 critical, 8 majors, and a minor.
There's no way we're going to knock off 63 bugs in less than two weeks. But at a minimum, we need to knock off the blockers and criticals before CR1 goes out the door.
**Beyond that, it seems it's time for another triage pass to see which Majors really need to make it into this release. Any Major that is going to make it into CR1 needs to be bumped to Critical. Anything that's Major or Minor will then be pushed off to the JBoss Tools 3.3/JBDS 5 release after CR1 goes out the door.
Obviously the bugs aren't squashing themselves. :(
Koen, I know jBPM 3 maintenance is a low priority, but eleven bugs
==No Target Milestone lists for JBDS & JBoss Tools==
On another note that's not JBDS 4.1-specific, we also are gathering a huge number of bugs with no target milestone in the JBIDE and JBDS lists.
JBIDE has 81 bugs with no target milestone: https://issues.jboss.org/secure/IssueNavigator.jspa?mode=hide&requestId=1...
And JBDS has 54 bugs with no target milestone: https://issues.jboss.org/secure/IssueNavigator.jspa?mode=hide&requestId=1...
**Can we make a pass through these and distribute them? Any that we need to know about for JBDS 4.1/JBT 3.2.1 should be targeted for the correct milestones...
Thanks folks for any and all help with this release! The quicker we can get JBDS 4.1 done the more time we'll have for JBDS 5. :)
Brian Fitzpatrick (aka "Fitz")
Senior Software Engineer, SOA-P
JBoss by Red Hat