(2012-04-13 13:32:29) ldimaggi_: nboldt, bfitzpat stupid question - Juno is 4.2 - what's 3.8? (2012-04-13 13:32:43) bfitzpat: also Juno (2012-04-13 13:33:02) bfitzpat: 3.8 and 4.2 are both Juno, but 4.2 is the main version and 3.8 is the 3.x stream version (2012-04-13 13:34:10) bfitzpat: 3.x is on its way out eventually (2012-04-13 13:34:44) ldimaggi_: bfitzpat, got it - so - we need to test.............both - and 3.7 to I think ;-) 13:35 (2012-04-13 13:35:16) bfitzpat: yeah, well... we don't really have a 4.2 ready build yet so far as I know (2012-04-13 13:35:26) bfitzpat: though Nick is pushing to test some early stuff (2012-04-13 13:36:23) ldimaggi_: bfitzpat, that's why I asked ;-) -- Since 4.2 is already at M6 [1], the window of opportunity to discover what (if anything) in JBDS won't run on it is nearly closed. After M7 (Star Wars Day*) only hold-the-presses, stop-ship issues will be CONSIDERED, much less fixed. Sure, we can report issues against upstream later on and they'll get fixed (maybe) in SR1 (September 2012) or SR2 (February 2013) but ideally, JBDS 5 would run OOTB on Eclipse 4.2/3.8 as well as 3.7, without our needing to patch stuff in Eclipse or WTP (like we have had to do in past years, particularly re: SWT or equinox). Ideally, we'd be able to have the same JBDS 5 bits working on BOTH Eclipse 3.7.2 and 4.2/3.8. So, to that end, we need to start testing builds [2] and installs of JBDS 5 on the new Juno platform as well as the existing Indigo one. [1] http://wiki.eclipse.org/Juno/Simultaneous_Release_Plan#Milestones_and_Rel... [2] https://issues.jboss.org/browse/JBIDE-11469?focusedCommentId=12684016#com... -- As to the question of 3.8 vs. 4.2, 3.x is the old stream which is being (eventually) phased out. 4.2 includes a compatibility layer so that in theory anything 3.x-dependent can run on 4.2 as well. The TP I built includes the 4.2 bits (which in turn include much of the 3.8 site too). My fond hope is that I won't need to include any additional 3.8-level plugins beyond what's already in the Juno or Eclipse 4.2 sites. -- More info& links: https://issues.jboss.org/browse/JBIDE-11469

> What are the plans to make commits for Eclipse Juno possible? Are we going to have a branch for it or will migrate trunk soon? We are looking to try and be compatible. > I had a lot of changes as usual in JPT plugins. Again !? Aren't we able to avoid these ?

Please for now, simply open jiras with problems found and create subtasks/links to https://issues.jboss.org/browse/JBIDE-11549 Thank you, Max p.s. I removed all the non-relevant mailing lists and just left jbosstools-dev for these specifics. > Dmitry > > 14.04.2012 18:51, Nick Boldt wrote: >> (2012-04-13 13:32:29) ldimaggi_: nboldt, bfitzpat stupid question - Juno >> is 4.2 - what's 3.8? >> (2012-04-13 13:32:43) bfitzpat: also Juno >> (2012-04-13 13:33:02) bfitzpat: 3.8 and 4.2 are both Juno, but 4.2 is >> the main version and 3.8 is the 3.x stream version >> (2012-04-13 13:34:10) bfitzpat: 3.x is on its way out eventually >> (2012-04-13 13:34:44) ldimaggi_: bfitzpat, got it - so - we need to >> test.............both - and 3.7 to I think ;-) >> 13:35 >> (2012-04-13 13:35:16) bfitzpat: yeah, well... we don't really have a 4.2 >> ready build yet so far as I know >> (2012-04-13 13:35:26) bfitzpat: though Nick is pushing to test some >> early stuff >> (2012-04-13 13:36:23) ldimaggi_: bfitzpat, that's why I asked ;-) >> >> -- >> >> Since 4.2 is already at M6 [1], the window of opportunity to discover >> what (if anything) in JBDS won't run on it is nearly closed. After M7 >> (Star Wars Day*) only hold-the-presses, stop-ship issues will be >> CONSIDERED, much less fixed. >> >> Sure, we can report issues against upstream later on and they'll get >> fixed (maybe) in SR1 (September 2012) or SR2 (February 2013) but >> ideally, JBDS 5 would run OOTB on Eclipse 4.2/3.8 as well as 3.7, >> without our needing to patch stuff in Eclipse or WTP (like we have had >> to do in past years, particularly re: SWT or equinox). Ideally, we'd be >> able to have the same JBDS 5 bits working on BOTH Eclipse 3.7.2 and 4.2/3.8. >> >> So, to that end, we need to start testing builds [2] and installs of >> JBDS 5 on the new Juno platform as well as the existing Indigo one. >> >> [1] >> http://wiki.eclipse.org/Juno/Simultaneous_Release_Plan#Milestones_and_Rel... >> >> [2] >> https://issues.jboss.org/browse/JBIDE-11469?focusedCommentId=12684016#com... >> >> -- >> >> As to the question of 3.8 vs. 4.2, 3.x is the old stream which is being >> (eventually) phased out. 4.2 includes a compatibility layer so that in >> theory anything 3.x-dependent can run on 4.2 as well. The TP I built >> includes the 4.2 bits (which in turn include much of the 3.8 site too). >> My fond hope is that I won't need to include any additional 3.8-level >> plugins beyond what's already in the Juno or Eclipse 4.2 sites. >> >> -- >> >> More info& links: https://issues.jboss.org/browse/JBIDE-11469 >> >>

> 16.04.2012 15:21, Max Rydahl Andersen wrote: >>> What are the plans to make commits for Eclipse Juno possible? Are we going to have a branch for it or will migrate trunk soon? >> We are looking to try and be compatible. >> >>> I had a lot of changes as usual in JPT plugins. >> Again !? Aren't we able to avoid these ? > Yes, they consolidated of the java resource model for JAXB and JPA. So I assume that means a No ? And they completely broke all public API or is this just related to their internal API ? /max > > >> >> Please for now, simply open jiras with problems found and create subtasks/links to https://issues.jboss.org/browse/JBIDE-11549 >> >> Thank you, >> Max >> >> p.s. I removed all the non-relevant mailing lists and just left jbosstools-dev for these specifics. >> >>> Dmitry >>> >>> 14.04.2012 18:51, Nick Boldt wrote: >>>> (2012-04-13 13:32:29) ldimaggi_: nboldt, bfitzpat stupid question - Juno >>>> is 4.2 - what's 3.8? >>>> (2012-04-13 13:32:43) bfitzpat: also Juno >>>> (2012-04-13 13:33:02) bfitzpat: 3.8 and 4.2 are both Juno, but 4.2 is >>>> the main version and 3.8 is the 3.x stream version >>>> (2012-04-13 13:34:10) bfitzpat: 3.x is on its way out eventually >>>> (2012-04-13 13:34:44) ldimaggi_: bfitzpat, got it - so - we need to >>>> test.............both - and 3.7 to I think ;-) >>>> 13:35 >>>> (2012-04-13 13:35:16) bfitzpat: yeah, well... we don't really have a 4.2 >>>> ready build yet so far as I know >>>> (2012-04-13 13:35:26) bfitzpat: though Nick is pushing to test some >>>> early stuff >>>> (2012-04-13 13:36:23) ldimaggi_: bfitzpat, that's why I asked ;-) >>>> >>>> -- >>>> >>>> Since 4.2 is already at M6 [1], the window of opportunity to discover >>>> what (if anything) in JBDS won't run on it is nearly closed. After M7 >>>> (Star Wars Day*) only hold-the-presses, stop-ship issues will be >>>> CONSIDERED, much less fixed. >>>> >>>> Sure, we can report issues against upstream later on and they'll get >>>> fixed (maybe) in SR1 (September 2012) or SR2 (February 2013) but >>>> ideally, JBDS 5 would run OOTB on Eclipse 4.2/3.8 as well as 3.7, >>>> without our needing to patch stuff in Eclipse or WTP (like we have had >>>> to do in past years, particularly re: SWT or equinox). Ideally, we'd be >>>> able to have the same JBDS 5 bits working on BOTH Eclipse 3.7.2 and 4.2/3.8. >>>> >>>> So, to that end, we need to start testing builds [2] and installs of >>>> JBDS 5 on the new Juno platform as well as the existing Indigo one. >>>> >>>> [1] >>>> http://wiki.eclipse.org/Juno/Simultaneous_Release_Plan#Milestones_and_Rel... >>>> >>>> [2] >>>> https://issues.jboss.org/browse/JBIDE-11469?focusedCommentId=12684016#com... >>>> >>>> -- >>>> >>>> As to the question of 3.8 vs. 4.2, 3.x is the old stream which is being >>>> (eventually) phased out. 4.2 includes a compatibility layer so that in >>>> theory anything 3.x-dependent can run on 4.2 as well. The TP I built >>>> includes the 4.2 bits (which in turn include much of the 3.8 site too). >>>> My fond hope is that I won't need to include any additional 3.8-level >>>> plugins beyond what's already in the Juno or Eclipse 4.2 sites. >>>> >>>> -- >>>> >>>> More info& links: https://issues.jboss.org/browse/JBIDE-11469 >>>> >>>> > _______________________________________________ > 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

There are 2 issues listed on the page which changes the API. https://bugs.eclipse.org/bugs/show_bug.cgi?id=277017 https://bugs.eclipse.org/bugs/show_bug.cgi?id=319736 But not all of the changes are described there. Here are the changes which impact us: Classes which were removed? org.eclipse.jpt.common.utility.model.value.WritablePropertyValueModel; org.eclipse.jpt.jpa.core.context.java.JavaStructureNodes; org.eclipse.jpt.jpa.ui.navigator.JpaNavigatorProvider; org.eclipse.jpt.jpa.core.context.Table.Owner; org.eclipse.jpt.jpa.core.resource.java.AnnotationContainer; org.eclipse.jpt.jpa.core.resource.java.JavaResourcePersistentAttribute org.eclipse.jpt.jpa.ui.structure.JpaStructureProvider org.eclipse.jpt.jpa.core.resource.java.NamedQueriesAnnotation org.eclipse.jpt.jpa.core.resource.java.NamedNativeQueriesAnnotation org.eclipse.jpt.jpa.core.resource.java.AttributeOverridesAnnotation org.eclipse.jpt.jpa.core.resource.java.AssociationOverridesAnnotation Disappeared/moved/renamed OrmJoinColumn.Owner JptJpaCorePlugin.rebuildJpaProject(getProject()); JavaPersistentAttribute.getResourcePersistentAttribute() PersistenceUnit.mappingFileRefsContaining(...) Persistence.persistenceUnits() JavaPersistentType.attributes() JpaJpqlQueryHelper made abstract JavaGeneratorContainer.Owner JavaResourceAnnotatedElement.addAnnotation(int, string, string) PersistentType.allAttributes() JavaResourceAnnotatedElement.annotations(String, String) JavaResourceAnnotatedElement.attributes() and others Many public package name changes Note: some of them are listed there, but some not. In the list only the changes in public packages. Dmitry 16.04.2012 15:40, Max Rydahl Andersen wrote: > i.e. http://wiki.eclipse.org/New_Help_for_Old_Friends_VII > mentions nothing of this so if this is anywhere near public API we should raise this ASAP! > > /max > > On Apr 16, 2012, at 14:37 , Max Rydahl Andersen wrote: > > >>> 16.04.2012 15:21, Max Rydahl Andersen wrote: >>> >>>>> What are the plans to make commits for Eclipse Juno possible? Are we going to have a branch for it or will migrate trunk soon? >>>>> >>>> We are looking to try and be compatible. >>>> >>>> >>>>> I had a lot of changes as usual in JPT plugins. >>>>> >>>> Again !? Aren't we able to avoid these ? >>>> >>> Yes, they consolidated of the java resource model for JAXB and JPA. >>> >> So I assume that means a No ? >> >> And they completely broke all public API or is this just related to their internal API ? >> >> /max >> >>> >>>> Please for now, simply open jiras with problems found and create subtasks/links to https://issues.jboss.org/browse/JBIDE-11549 >>>> >>>> >>>> Thank you, >>>> Max >>>> >>>> p.s. I removed all the non-relevant mailing lists and just left jbosstools-dev for these specifics. >>>> >>>> >>>>> Dmitry >>>>> >>>>> 14.04.2012 18:51, Nick Boldt wrote: >>>>> >>>>>> (2012-04-13 13:32:29) ldimaggi_: nboldt, bfitzpat stupid question - Juno >>>>>> is 4.2 - what's 3.8? >>>>>> (2012-04-13 13:32:43) bfitzpat: also Juno >>>>>> (2012-04-13 13:33:02) bfitzpat: 3.8 and 4.2 are both Juno, but 4.2 is >>>>>> the main version and 3.8 is the 3.x stream version >>>>>> (2012-04-13 13:34:10) bfitzpat: 3.x is on its way out eventually >>>>>> (2012-04-13 13:34:44) ldimaggi_: bfitzpat, got it - so - we need to >>>>>> test.............both - and 3.7 to I think ;-) >>>>>> 13:35 >>>>>> (2012-04-13 13:35:16) bfitzpat: yeah, well... we don't really have a 4.2 >>>>>> ready build yet so far as I know >>>>>> (2012-04-13 13:35:26) bfitzpat: though Nick is pushing to test some >>>>>> early stuff >>>>>> (2012-04-13 13:36:23) ldimaggi_: bfitzpat, that's why I asked ;-) >>>>>> >>>>>> -- >>>>>> >>>>>> Since 4.2 is already at M6 [1], the window of opportunity to discover >>>>>> what (if anything) in JBDS won't run on it is nearly closed. After M7 >>>>>> (Star Wars Day*) only hold-the-presses, stop-ship issues will be >>>>>> CONSIDERED, much less fixed. >>>>>> >>>>>> Sure, we can report issues against upstream later on and they'll get >>>>>> fixed (maybe) in SR1 (September 2012) or SR2 (February 2013) but >>>>>> ideally, JBDS 5 would run OOTB on Eclipse 4.2/3.8 as well as 3.7, >>>>>> without our needing to patch stuff in Eclipse or WTP (like we have had >>>>>> to do in past years, particularly re: SWT or equinox). Ideally, we'd be >>>>>> able to have the same JBDS 5 bits working on BOTH Eclipse 3.7.2 and 4.2/3.8. >>>>>> >>>>>> So, to that end, we need to start testing builds [2] and installs of >>>>>> JBDS 5 on the new Juno platform as well as the existing Indigo one. >>>>>> >>>>>> [1] >>>>>> >>>>>> http://wiki.eclipse.org/Juno/Simultaneous_Release_Plan#Milestones_and_Rel... >>>>>> >>>>>> >>>>>> [2] >>>>>> >>>>>> https://issues.jboss.org/browse/JBIDE-11469?focusedCommentId=12684016#com... >>>>>> >>>>>> >>>>>> -- >>>>>> >>>>>> As to the question of 3.8 vs. 4.2, 3.x is the old stream which is being >>>>>> (eventually) phased out. 4.2 includes a compatibility layer so that in >>>>>> theory anything 3.x-dependent can run on 4.2 as well. The TP I built >>>>>> includes the 4.2 bits (which in turn include much of the 3.8 site too). >>>>>> My fond hope is that I won't need to include any additional 3.8-level >>>>>> plugins beyond what's already in the Juno or Eclipse 4.2 sites. >>>>>> >>>>>> -- >>>>>> >>>>>> More info& links: >>>>>> https://issues.jboss.org/browse/JBIDE-11469 >>>>>> >>>>>> >>>>>> >>>>>> >>> _______________________________________________ >>> 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

common features version changed from 1.0.0 to 1.2.0 jpt.jpa features version changed from 3.0.0 to 3.2.0 16.04.2012 16:48, Max Rydahl Andersen написал: > what is the version bump change they did from indigo to juno ? > > /max > > On Apr 16, 2012, at 15:35 , Dmitry Geraskov wrote: > >> There are 2 issues listed on the page which changes the API. >> https://bugs.eclipse.org/bugs/show_bug.cgi?id=277017 >> https://bugs.eclipse.org/bugs/show_bug.cgi?id=319736 >> >> But not all of the changes are described there. Here are the changes which impact us: >> >> Classes which were removed? >> org.eclipse.jpt.common.utility.model.value.WritablePropertyValueModel; >> org.eclipse.jpt.jpa.core.context.java.JavaStructureNodes; >> org.eclipse.jpt.jpa.ui.navigator.JpaNavigatorProvider; >> org.eclipse.jpt.jpa.core.context.Table.Owner; >> org.eclipse.jpt.jpa.core.resource.java.AnnotationContainer; >> org.eclipse.jpt.jpa.core.resource.java.JavaResourcePersistentAttribute >> org.eclipse.jpt.jpa.ui.structure.JpaStructureProvider >> org.eclipse.jpt.jpa.core.resource.java.NamedQueriesAnnotation >> org.eclipse.jpt.jpa.core.resource.java.NamedNativeQueriesAnnotation >> org.eclipse.jpt.jpa.core.resource.java.AttributeOverridesAnnotation >> org.eclipse.jpt.jpa.core.resource.java.AssociationOverridesAnnotation >> >> >> Disappeared/moved/renamed >> OrmJoinColumn.Owner >> JptJpaCorePlugin.rebuildJpaProject(getProject()); >> JavaPersistentAttribute.getResourcePersistentAttribute() >> PersistenceUnit.mappingFileRefsContaining(...) >> Persistence.persistenceUnits() >> JavaPersistentType.attributes() >> JpaJpqlQueryHelper made abstract >> JavaGeneratorContainer.Owner >> JavaResourceAnnotatedElement.addAnnotation(int, string, string) >> PersistentType.allAttributes() >> JavaResourceAnnotatedElement.annotations(String, String) >> JavaResourceAnnotatedElement.attributes() >> and others >> >> Many public package name changes >> >> Note: some of them are listed there, but some not. In the list only the changes in public packages. >> >> Dmitry >> >> 16.04.2012 15:40, Max Rydahl Andersen wrote: >>> i.e. http://wiki.eclipse.org/New_Help_for_Old_Friends_VII >>> mentions nothing of this so if this is anywhere near public API we should raise this ASAP! >>> >>> /max >>> >>> On Apr 16, 2012, at 14:37 , Max Rydahl Andersen wrote: >>> >>> >>>>> 16.04.2012 15:21, Max Rydahl Andersen wrote: >>>>> >>>>>>> What are the plans to make commits for Eclipse Juno possible? Are we going to have a branch for it or will migrate trunk soon? >>>>>>> >>>>>> We are looking to try and be compatible. >>>>>> >>>>>> >>>>>>> I had a lot of changes as usual in JPT plugins. >>>>>>> >>>>>> Again !? Aren't we able to avoid these ? >>>>>> >>>>> Yes, they consolidated of the java resource model for JAXB and JPA. >>>>> >>>> So I assume that means a No ? >>>> >>>> And they completely broke all public API or is this just related to their internal API ? >>>> >>>> /max >>>> >>>>>> Please for now, simply open jiras with problems found and create subtasks/links to https://issues.jboss.org/browse/JBIDE-11549 >>>>>> >>>>>> >>>>>> Thank you, >>>>>> Max >>>>>> >>>>>> p.s. I removed all the non-relevant mailing lists and just left jbosstools-dev for these specifics. >>>>>> >>>>>> >>>>>>> Dmitry >>>>>>> >>>>>>> 14.04.2012 18:51, Nick Boldt wrote: >>>>>>> >>>>>>>> (2012-04-13 13:32:29) ldimaggi_: nboldt, bfitzpat stupid question - Juno >>>>>>>> is 4.2 - what's 3.8? >>>>>>>> (2012-04-13 13:32:43) bfitzpat: also Juno >>>>>>>> (2012-04-13 13:33:02) bfitzpat: 3.8 and 4.2 are both Juno, but 4.2 is >>>>>>>> the main version and 3.8 is the 3.x stream version >>>>>>>> (2012-04-13 13:34:10) bfitzpat: 3.x is on its way out eventually >>>>>>>> (2012-04-13 13:34:44) ldimaggi_: bfitzpat, got it - so - we need to >>>>>>>> test.............both - and 3.7 to I think ;-) >>>>>>>> 13:35 >>>>>>>> (2012-04-13 13:35:16) bfitzpat: yeah, well... we don't really have a 4.2 >>>>>>>> ready build yet so far as I know >>>>>>>> (2012-04-13 13:35:26) bfitzpat: though Nick is pushing to test some >>>>>>>> early stuff >>>>>>>> (2012-04-13 13:36:23) ldimaggi_: bfitzpat, that's why I asked ;-) >>>>>>>> >>>>>>>> -- >>>>>>>> >>>>>>>> Since 4.2 is already at M6 [1], the window of opportunity to discover >>>>>>>> what (if anything) in JBDS won't run on it is nearly closed. After M7 >>>>>>>> (Star Wars Day*) only hold-the-presses, stop-ship issues will be >>>>>>>> CONSIDERED, much less fixed. >>>>>>>> >>>>>>>> Sure, we can report issues against upstream later on and they'll get >>>>>>>> fixed (maybe) in SR1 (September 2012) or SR2 (February 2013) but >>>>>>>> ideally, JBDS 5 would run OOTB on Eclipse 4.2/3.8 as well as 3.7, >>>>>>>> without our needing to patch stuff in Eclipse or WTP (like we have had >>>>>>>> to do in past years, particularly re: SWT or equinox). Ideally, we'd be >>>>>>>> able to have the same JBDS 5 bits working on BOTH Eclipse 3.7.2 and 4.2/3.8. >>>>>>>> >>>>>>>> So, to that end, we need to start testing builds [2] and installs of >>>>>>>> JBDS 5 on the new Juno platform as well as the existing Indigo one. >>>>>>>> >>>>>>>> [1] >>>>>>>> >>>>>>>> http://wiki.eclipse.org/Juno/Simultaneous_Release_Plan#Milestones_and_Rel... >>>>>>>> >>>>>>>> >>>>>>>> [2] >>>>>>>> >>>>>>>> https://issues.jboss.org/browse/JBIDE-11469?focusedCommentId=12684016#com... >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> >>>>>>>> As to the question of 3.8 vs. 4.2, 3.x is the old stream which is being >>>>>>>> (eventually) phased out. 4.2 includes a compatibility layer so that in >>>>>>>> theory anything 3.x-dependent can run on 4.2 as well. The TP I built >>>>>>>> includes the 4.2 bits (which in turn include much of the 3.8 site too). >>>>>>>> My fond hope is that I won't need to include any additional 3.8-level >>>>>>>> plugins beyond what's already in the Juno or Eclipse 4.2 sites. >>>>>>>> >>>>>>>> -- >>>>>>>> >>>>>>>> More info& links: >>>>>>>> https://issues.jboss.org/browse/JBIDE-11469 >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>> _______________________________________________ >>>>> 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