-
1. Re: JBossIDE WTP 1.0 upgrade
maxandersen Nov 22, 2005 11:30 AM (in response to mculpepper)i dont see the benefit of branching to do this - what should be the purpose ?
-
2. Re: JBossIDE WTP 1.0 upgrade
mculpepper Nov 22, 2005 11:33 AM (in response to mculpepper)Again, for the nightly builds to continue building against HEAD uninterrupted until we can merge at a later time when everything is compatible at once.
At any rate, this was only a suggestion, but it might bring woes to our users who are using the nightlies .. -
3. Re: JBossIDE WTP 1.0 upgrade
maxandersen Nov 25, 2005 7:35 AM (in response to mculpepper)i plan on performing migration of the hibernatetools to M9 in the next week. I'll not do HEAD commit before I know how big a challange this stuff will become.
I'll keep you posted.
Besides the nighlty build is just the tool that can be used to make this migration easier/faster/better since we get validation that it can/cannot be built.
Do you guys have time to do M9 migration for your respective parts ? -
4. Re: JBossIDE WTP 1.0 upgrade
maxandersen Nov 27, 2005 9:20 AM (in response to mculpepper)Darryl Miles have posted a patch for hibernatetools at http://opensource2.atlassian.com/projects/hibernate/browse/HBX-498
Ill use that as a basis for my adaption.
Let me know what your plans are for the other parts of JBoss IDE ? -
5. Re: JBossIDE WTP 1.0 upgrade
mculpepper Nov 29, 2005 8:44 AM (in response to mculpepper)The "core" part of the IDE is only concerned with WTP integration, as we aren't extending any of WTP (yet).
If there are any plugin ID changes, they will need to be changed in the feature.xml, but other than that I don't foresee anything needing testing other than integration testing (which will commence soon) -
6. Re: JBossIDE WTP 1.0 upgrade
maxandersen Nov 29, 2005 8:51 AM (in response to mculpepper)well changing the id's is probably also the hardest part to test since it require a clinical clean setup to not mess up their id resolve logic ;)