On 03-04-2009 01:50, Denis Golovin wrote:
I've added new issue for that
Anyone can add subtask/comment into it with spec what should be done
to make that happened.
Yes! We did that last year too, see
A subtask per each overall issue to track it.
Snjezana's comments on JBIDE-4123 are good too - great to know if we are
breaking 3.4.x or not.
I updated the jira with pointers to the known migration docs out there.
Max Rydahl Andersen wrote:
> Let me rephrase this:
> I would like to get confirmation from the following that upgrading to
> Eclipse 3.5 is ok for you (these are the persons/teams not present at
> the tools meeting where we discussed this):
> Snjezana Peco - Portlets, project examples ?
> Kris V. - Drools ?
> Alexey K. - JSF, Seam etc. ?
> Anyone else with objections or concerns are of course also welcome to
> speak up!
> If I don't get a reply by monday I assume everyone is ok with what
> were decided last week.
>> At EclipseCon/Tools meeting last week we discussed the necessity of
>> moving the 3.1/trunk work onto Eclipse 3.5 M builds as soon as
>> possible so
>> 1) Can get any fixes/changes into Eclipse that we need/want before
>> they API freeze (in a month or so)
>> 2) Develop on a platform that will actually be supported by Eclipse
>> (Eclipse 3.4 won't get more fixes in)
>> Could you please let me know if you have any problems/issues with
>> this happening ?
>> i.e. JBoss Tools 3.0.x will still require Eclipse 3.4, it is just
>> for trunk/upcoming major releases we will be moving.
>> jbosstools-dev mailing list
> jbosstools-dev mailing list