<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
There are 2 issues listed on the page which changes the API.<br>
<a class="moz-txt-link-freetext" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=277017">https://bugs.eclipse.org/bugs/show_bug.cgi?id=277017</a><br>
<a class="moz-txt-link-freetext" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=319736">https://bugs.eclipse.org/bugs/show_bug.cgi?id=319736</a><br>
<br>
But not all of the changes are described there. Here are the changes
which impact us:<br>
<br>
<b>Classes which were removed?</b><br>
org.eclipse.jpt.common.utility.model.value.WritablePropertyValueModel;<br>
org.eclipse.jpt.jpa.core.context.java.JavaStructureNodes;<br>
org.eclipse.jpt.jpa.ui.navigator.JpaNavigatorProvider;<br>
org.eclipse.jpt.jpa.core.context.Table.Owner;<br>
org.eclipse.jpt.jpa.core.resource.java.AnnotationContainer;<br>
org.eclipse.jpt.jpa.core.resource.java.JavaResourcePersistentAttribute<br>
org.eclipse.jpt.jpa.ui.structure.JpaStructureProvider<br>
org.eclipse.jpt.jpa.core.resource.java.NamedQueriesAnnotation<br>
org.eclipse.jpt.jpa.core.resource.java.NamedNativeQueriesAnnotation<br>
org.eclipse.jpt.jpa.core.resource.java.AttributeOverridesAnnotation<br>
org.eclipse.jpt.jpa.core.resource.java.AssociationOverridesAnnotation<br>
<br>
<br>
<b>Disappeared/moved/renamed</b><br>
OrmJoinColumn.Owner<br>
JptJpaCorePlugin.rebuildJpaProject(getProject());<br>
JavaPersistentAttribute.getResourcePersistentAttribute()<br>
PersistenceUnit.mappingFileRefsContaining(...)<br>
Persistence.persistenceUnits()<br>
JavaPersistentType.attributes()<br>
JpaJpqlQueryHelper made abstract<br>
JavaGeneratorContainer.Owner<br>
JavaResourceAnnotatedElement.addAnnotation(int, string, string)<br>
PersistentType.allAttributes()<br>
JavaResourceAnnotatedElement.annotations(String, String)<br>
JavaResourceAnnotatedElement.attributes()<br>
and others<br>
<b><br>
Many public package name changes</b><br>
<br>
Note: some of them are listed there, but some not. In the list only
the changes in public packages.<br>
<br>
Dmitry<br>
<br>
16.04.2012 15:40, Max Rydahl Andersen wrote:
<blockquote
cite="mid:E9478BEA-1B42-480F-9074-BD0A8DD270B0@redhat.com"
type="cite">
<pre wrap="">i.e. <a class="moz-txt-link-freetext" href="http://wiki.eclipse.org/New_Help_for_Old_Friends_VII">http://wiki.eclipse.org/New_Help_for_Old_Friends_VII</a> 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:
</pre>
<blockquote type="cite">
<pre wrap="">
</pre>
<blockquote type="cite">
<pre wrap="">16.04.2012 15:21, Max Rydahl Andersen wrote:
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">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?
</pre>
</blockquote>
<pre wrap="">We are looking to try and be compatible.
</pre>
<blockquote type="cite">
<pre wrap="">I had a lot of changes as usual in JPT plugins.
</pre>
</blockquote>
<pre wrap="">Again !? Aren't we able to avoid these ?
</pre>
</blockquote>
<pre wrap="">Yes, they consolidated of the java resource model for JAXB and JPA.
</pre>
</blockquote>
<pre wrap="">
So I assume that means a No ?
And they completely broke all public API or is this just related to their internal API ?
/max
</pre>
<blockquote type="cite">
<pre wrap="">
</pre>
<blockquote type="cite">
<pre wrap="">
Please for now, simply open jiras with problems found and create subtasks/links to <a class="moz-txt-link-freetext" href="https://issues.jboss.org/browse/JBIDE-11549">https://issues.jboss.org/browse/JBIDE-11549</a>
Thank you,
Max
p.s. I removed all the non-relevant mailing lists and just left jbosstools-dev for these specifics.
</pre>
<blockquote type="cite">
<pre wrap="">Dmitry
14.04.2012 18:51, Nick Boldt wrote:
</pre>
<blockquote type="cite">
<pre wrap="">(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]
<a class="moz-txt-link-freetext" href="http://wiki.eclipse.org/Juno/Simultaneous_Release_Plan#Milestones_and_Release_Candidates">http://wiki.eclipse.org/Juno/Simultaneous_Release_Plan#Milestones_and_Release_Candidates</a>
[2]
<a class="moz-txt-link-freetext" href="https://issues.jboss.org/browse/JBIDE-11469?focusedCommentId=12684016#comment-12684016">https://issues.jboss.org/browse/JBIDE-11469?focusedCommentId=12684016#comment-12684016</a>
--
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: <a class="moz-txt-link-freetext" href="https://issues.jboss.org/browse/JBIDE-11469">https://issues.jboss.org/browse/JBIDE-11469</a>
</pre>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">_______________________________________________
jbosstools-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:jbosstools-dev@lists.jboss.org">jbosstools-dev@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/jbosstools-dev">https://lists.jboss.org/mailman/listinfo/jbosstools-dev</a>
</pre>
</blockquote>
<pre wrap="">
_______________________________________________
jbosstools-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:jbosstools-dev@lists.jboss.org">jbosstools-dev@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/jbosstools-dev">https://lists.jboss.org/mailman/listinfo/jbosstools-dev</a>
</pre>
</blockquote>
<pre wrap="">
</pre>
</blockquote>
</body>
</html>