Re: [jbosstools-dev] Moving to Eclipse 3.5 drivers
by Max Rydahl Andersen
Hi Kris,
Any follow up on this (I replied back then too ;)
https://jira.jboss.org/jira/browse/JBIDE-4164 is holding back our
migration to Eclipse 3.5.
Snjezana added a patch that makes things compile - need someone to
verify that it actually also works ;)
/max
Kris Verlaenen wrote:
> Max,
>
> One issue we have is that Drools cannot support more than one Eclipse
> version using the same code base. We are dependent on some internal
> eclipse java classes to get the rule debugging working (the Java
> debugging was not really written to be extended / reused, at least not
> when we implemented debugging and I guess the situation is still the
> same), and those internal apis tend to change a little every release.
> I just checked and a few methods were added again. This means we
> would have to maintain two parallel branches, one for Eclipse 3.4 and
> one for 3.5.
>
> Based on the impression that they are targeting Eclipse 3.5 GA end of
> June, I guess the following options are possible:
> 1. after Drools 5.0 GA (supporting Eclipse 3.4.x) this weekend we move
> to Eclipse 3.5.x, all new features implemented for Drools 5.1+ Eclipse
> IDE will be for Eclipse 3.5 only
> 2. after Drools 5.0 GA we keep working on this code base (supporting
> Eclipse 3.4.x) and we branch the last week before Drools 5.1, so at
> that point both Eclipse 3.4 and 3.5 are supported for Drools 5.1,
> after that all new changes are for Eclipse 3.5 only
> 3. after Drools 5.0.GA create a new Eclipse 3.5 code base immediately,
> next to the Eclipse 3.4 code base, and commit all changes to both,
> until we decide the 3.4 branch no longer needs to be kept up-to-date
> with the latest features
>
> Obviously, option 3 requires a lot more work. I'd go for option 2 as
> it has the advantage of being able to support both 3.4 and 3.5 for
> 5.1, but that means we won't be able to migrate to Eclipse 3.5 soon.
>
> On the other hand, the changes required to get this working on Eclipse
> 3.5 are probably pretty minimal, maybe we can write some automatic
> patch script that could automatically patch our Eclipse 3.4 code so it
> supports 3.5, thus removing the need to maintain two separate
> branches? And JBoss Tools trunk could use the patch script and
> include the Eclipse 3.5 version, would that be possible?
>
> Kris
>
> 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 mo-nday I assume everyone is ok with what
>> were decided last week.
>>
>> Thanks,
>> /max
>>> Hi,
>>>
>>> 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
>>> we:
>>>
>>> 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.
>>>
>>> -max
>>> _______________________________________________
>>> jbosstools-dev mailing list
>>> jbosstools-dev(a)lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
15 years, 9 months
Re: [jbosstools-dev] Re: Trunk is now open for Eclipse 3.5 commits
by feng.qian
Thanks!
I have checkout the wtp again, now no issue! But still not know the reason.
Anyway, I can run correctly eclispe3.5 on my machine! ;-)
> Try reinstalling WTP from their update site (or from
> http://download.eclipse.org/releases/galileo/). Here's the list of
> versions I loaded into the Hudson build:
>
> https://jira.jboss.org/jira/browse/JBIDE-4123?focusedCommentId=12462429#a...
>
>
> BIRT 2.5 N (2009/04/14)
> DTP 1.7M7 (04/10)
> EMF 2.5 I (04/14)
> GEF 3.5 I (04/03)
> Eclipse 3.5 post-M6 I build (04/14)
> TPTP 4.6 (04/14)
> WTP 3.1 I (04/09)
> XSD 2.5 I (04/14)
>
> You can download them all from here:
>
> http://repository.jboss.com/eclipse/
>
> Nick
>
> feng.qian wrote:
>> En, it is too puzzling. My enviroment is linux too and Eclipse 3.5M6,
>> WTP 3.1M6.
>>
>>> Eclipse 3.5M6, WTP 3.1M6, the current JBoss Tools trunk on Windows
>>> Eclipse 3.5M6, WTP 3.1M6 on Linux
>>>
>>> Snjeza
>>>
>>>
>>> feng.qian wrote:
>>>> Yes, I have checked the configuration, but I can not find any error
>>>> information and all the plugins are loaded.
>>>> What do you run eclipse on? Windows or Linux?
>>>>> I can create a dynamic web project as well as a Seam project using
>>>>> Eclipse 3.5M6 and WTP 3.1M6.
>>>>> You probably have a problem with your configuration. Check if all
>>>>> required plugins are loaded.
>>>>>
>>>>> Snjeza
>>>>>
>>>>> feng.qian wrote:
>>>>>> Hi Max,
>>>>>>
>>>>>> When I try to create a dynamic web project, a error
>>>>>> occured:java.lang.NoSuchMethodError:
>>>>>> org.eclipse.jst.j2ee.internal.wizard.J2EEComponentFacetCreationWizardPage.createWorkingSetGroupPanel(Lorg/eclipse/swt/widgets/Composite;[Ljava/lang/String;)Lorg/eclipse/ui/dialogs/WorkingSetGroup;
>>>>>>
>>>>>> and can't create it.
>>>>>> I think it is a wtp issue, not our tools. How should we handle it?
>>>>>>
>>>>>> BTW, I use eclipse M6 + wtp3.1M6
>>>>>>
>>>>>> Grid
>>>>>>> Hi,
>>>>>>>
>>>>>>> Nick moved the builds to use Eclipse 3.5 drivers - please commit
>>>>>>> the 3.5 changes needed ASAP so we can get the builds running.
>>>>>>>
>>>>>>> Don't forget to link to the jira or related jiras for
>>>>>>> https://jira.jboss.org/jira/browse/JBIDE-4123 and if you find
>>>>>>> other things that are relevant
>>>>>>> to adjust for changes in Eclipse 3.5 add them (i.e. Use
>>>>>>> Configure menu introduced in Eclipse 3.5 instead of polluting
>>>>>>> the context menu or
>>>>>>> Use Library extension point etc. - hint hint ; )
>>>>>>>
>>>>>>> /max
>>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> jbosstools-dev mailing list
>>>>>> jbosstools-dev(a)lists.jboss.org
>>>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>>>>
>>>>>
>>>>
>>>> _______________________________________________
>>>> jbosstools-dev mailing list
>>>> jbosstools-dev(a)lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>
>>
>
15 years, 9 months
QA Daily report 16 April 2009
by Aliaksey Nis
This is Daily QA report for 16 April 2009.
Tasks performed:
1. Testing of JBossTools-ALL-win32-3.1.0.Alpha1-N200904131201-H99
Free testing.
TPTP documentation research.
2. Issues verification.
https://jira.jboss.org/jira/browse/JBIDE-4144
3. Testcases updates.
Hibernate Tools tescases updates.
4. Issues report.
---
--
Best regards,
Aliaksey mailto:anis@exadel.com
15 years, 9 months
Trunk is now open for Eclipse 3.5 commits
by Max Rydahl Andersen
Hi,
Nick moved the builds to use Eclipse 3.5 drivers - please commit the 3.5
changes needed ASAP so we can get the builds running.
Don't forget to link to the jira or related jiras for
https://jira.jboss.org/jira/browse/JBIDE-4123 and if you find other
things that are relevant
to adjust for changes in Eclipse 3.5 add them (i.e. Use Configure menu
introduced in Eclipse 3.5 instead of polluting the context menu or
Use Library extension point etc. - hint hint ; )
/max
15 years, 9 months
Hudson cleanup (Attempt 1)
by Max Rydahl Andersen
Hi,
I thought I had a good hudson connection today but of course it stopped
working halfway through my "experiment" so
I guess the best thing I can do is let you know up front so you don't
start screaming over "missing" builds.
I went and created a "DevStudio Dormant" hudson group and started adding
"dormant-" to all builds that haven't been used for months.
It worked well until hudson stopped working - when I get a working
connection again I'll continue the cleanup.
Is the "Dormant" split a Good or Bad idea ? The idea is to make the
"primary" group actually list relevant builds.
/max
15 years, 9 months
