dali-dev http://dev.eclipse.org/mhonarc/lists/dali-dev/maillist.html dali-dev en-us Mon, 21 May 2012 14:40:07 GMT Mon, 21 May 2012 14:40:07 GMT http://blogs.law.harvard.edu/tech/rss MHonArc RSS 2.0 RCFile webmaster@eclipse.org (Webmaster) webmaster@eclipse.org (Webmaster) dali-dev http://www.eclipse.org/eclipse.org-common/themes/Phoenix/images/eclipse_home_header.jpg http://dev.eclipse.org/mhonarc/lists/dali-dev/maillist.html [dali-dev] Dali Weekly Status http://dev.eclipse.org/mhonarc/lists/dali-dev/msg01320.html Last week: All hands focusing on testing and fixing bugs for RC1 Bugs fixed: https://bugs.eclipse.org/bugs/buglist.cgi?bug_file_loc=%20;chfieldto=2012-05-19;query_format=advanced;chfield=resolution;chfieldfrom=2012-05-12;bug_file_loc_type=allwordssubstr;... Last week:
  • All hands focusing on testing and fixing bugs for RC1
Bugs fixed:  https://bugs.eclipse.org/bugs/buglist.cgi?bug_file_loc=%20;chfieldto=2012-05-19;query_format=advanced;chfield=resolution;chfieldfrom=2012-05-12;bug_file_loc_type=allwordssubstr;chfieldvalue=FIXED;classification=WebTools;product=Dali%20JPA%20Tools

Neil ]]> Mon, 21 May 2012 14:30:47 GMT http://dev.eclipse.org/mhonarc/lists/dali-dev/msg01320.html neil.hauge@xxxxxxx (Neil Hauge) [dali-dev] Default for "Discover annotated classes automatically" http://dev.eclipse.org/mhonarc/lists/dali-dev/msg01319.html Hi, guys, seems currently adopters could not change default value for "Discover annotated classes automatically". (Actually it is set on new JPA Project even earlier than user selects platform). You use "runtimeSupportsEjb30()" check, but this is not corre... Hi, guys,
seems currently adopters could not change default value for "Discover annotated classes automatically". (Actually it is set on new JPA Project even earlier than user selects platform). You use "runtimeSupportsEjb30()" check, but this is not correct for Hibernate. Do you think it could be possible to allow adopters to provide different behaviour? (not sure as the defaults in this case should be read after platform selection)

(See https://issues.jboss.org/browse/JBIDE-11187 for details)

Dmitry Geraskov,
Hiberante tools Developer

]]> Fri, 18 May 2012 06:54:12 GMT http://dev.eclipse.org/mhonarc/lists/dali-dev/msg01319.html dgeraskov@xxxxxxx (Dmitry Geraskov) [dali-dev] JPA Diagram Editor component weekly status - week 20, 2012 http://dev.eclipse.org/mhonarc/lists/dali-dev/msg01318.html A summarized status of the JPA Diagram Editor component for week 20, 2012: 379273 - jpa diagram editor code does not compile against graphiti 0.9 release (patch is submitted, but the build fails because of missing graphiti’s dependencies). Best regards,Pet...

A summarized status of the JPA Diagram Editor component for week 20, 2012:

 

  • 379273 - jpa diagram editor code does not compile against graphiti 0.9 release (patch is submitted, but the build fails because of missing graphiti’s dependencies).

 

Best regards,

Petya

 

]]> Wed, 16 May 2012 14:13:46 GMT http://dev.eclipse.org/mhonarc/lists/dali-dev/msg01318.html petya.sabeva@xxxxxxx (Sabeva, Petya) Re: [dali-dev] Dali and Public API changes http://dev.eclipse.org/mhonarc/lists/dali-dev/msg01317.html okey - so I read that as you are doing multiple code streams ? :) okey, so in other words if we want to use/enable the new features in Juno with one code stream we can't - at least not for Dali. Remind me when that is and I'll make all the attempts I can ... >>> How do your own adopters at Oracle do this? > > I think there is a lot of variability on this among the entire adopter community. Some adopters choose to build on top of a specific release train version of Eclipse, without trying to maintain compatibility with other versions within the same code base. Where support for multiple release trains is needed in a particular release, multiple code streams and packages are used. Some adopters have seen this cost as worthwhile for the adoption of rapidly improving and expanding components. okey - so I read that as you are doing multiple code streams ? :) >>> Is there any chance that latest Dali release can run on both 3.7 and 3.8/4.2 and we could do it that way ? > (i.e. depend on Dali M7 from both 3.7 and 3.8 codebases) > > Actually, you could potentially run our latest release (Dali 3.1 - Dec 2011) on both Eclipse 3.7 and 3.8. There is some compatibility code in the 3.1 release to allow Dali clients to use the same code for 3.0 and 3.1. This was done because 3.1 was not based on a new release train, but instead it was based on the same Indigo train. This could not be done with 3.2M7. okey, so in other words if we want to use/enable the new features in Juno with one code stream we can't - at least not for Dali. > All of that said, this has made me think of something that we should be doing. In addition to doing a new and noteworthy that covers end-user functionality, we need a new and noteworthy specifically for Dali adopters. This would be a per milestone summary of the types of changes that will specifically benefit/be of interest to adopters. This would more easily allow adopters to be aware of (and perhaps encourage participation in) some of the larger scale changes to our model. It would go hand in hand with a migration guide to help adopters move to the new code. This would be in addition to the existing weekly status emails. +100 > This also raises the question of what we can do moving forward regarding a public API for Dali. This has been a hot topic of late, and I can assure everyone that this will be a large discussion point for our planning meetings for Dali Kepler. I would guess that some of you will be in attendance to ensure this is discussed. : ) Remind me when that is and I'll make all the attempts I can to be part or have someone be part of it. > This is all a balancing act, and I hope we can find the right point on the scale to ensure that Dali continues to evolve and improve while making sure our adopters can benefit from those improvements. Yes I know its a balancing act and I know how hard it is to encapsulate something as complex as JPA/JAXB behind a stable api. What I hope is that the api for Juno is powerful/good enough to be used as an api for multiple releases and Dali can start doing similar tricks that is done in the platform of having multiple interfaces to avoid breaking existing clients. /max ]]> Tue, 15 May 2012 05:41:30 GMT http://dev.eclipse.org/mhonarc/lists/dali-dev/msg01317.html max.andersen@xxxxxxx (Max Rydahl Andersen) [dali-dev] Dali Weekly Status http://dev.eclipse.org/mhonarc/lists/dali-dev/msg01316.html Last week: All hands focusing on testing and fixing bugs for RC1 Bugs fixed: https://bugs.eclipse.org/bugs/buglist.cgi?bug_file_loc=%20;chfieldto=2012-05-12;query_format=advanced;chfield=resolution;chfieldfrom=2012-05-05;bug_file_loc_type=allwordssubstr;... Last week:
  • All hands focusing on testing and fixing bugs for RC1
Bugs fixed:  https://bugs.eclipse.org/bugs/buglist.cgi?bug_file_loc=%20;chfieldto=2012-05-12;query_format=advanced;chfield=resolution;chfieldfrom=2012-05-05;bug_file_loc_type=allwordssubstr;chfieldvalue=FIXED;classification=WebTools;product=Dali%20JPA%20Tools

Neil
]]> Mon, 14 May 2012 14:37:43 GMT http://dev.eclipse.org/mhonarc/lists/dali-dev/msg01316.html neil.hauge@xxxxxxx (Neil Hauge) [dali-dev] JPA Diagram Editor component weekly status - week 19, 2012 http://dev.eclipse.org/mhonarc/lists/dali-dev/msg01315.html A summarized status of the JPA Diagram Editor component for week 19, 2012: No change since the last week Best regards,Petya

A summarized status of the JPA Diagram Editor component for week 19, 2012:

 

  • No change since the last week

 

Best regards,

Petya

 

]]> Wed, 09 May 2012 14:09:51 GMT http://dev.eclipse.org/mhonarc/lists/dali-dev/msg01315.html petya.sabeva@xxxxxxx (Sabeva, Petya) [dali-dev] provisional API additions in M7 - bug 342171 http://dev.eclipse.org/mhonarc/lists/dali-dev/msg01314.html To fix bug 342171 I am making a few provisional API changes, adding the following methods to context model interfaces. org.eclipse.jpt.jpa.core.context.Entity PrimaryKeyJoinColumn getSpecifiedPrimaryKeyJoinColumn(int index); void convertDefaultPrimaryKeyJ... To fix bug 342171 I am making a few provisional API changes, adding the following methods to context model interfaces.

org.eclipse.jpt.jpa.core.context.Entity
PrimaryKeyJoinColumn getSpecifiedPrimaryKeyJoinColumn(int index);
void convertDefaultPrimaryKeyJoinColumnsToSpecified();
void clearSpecifiedPrimaryKeyJoinColumns();

org.eclipse.jpt.jpa.core.context.JoinColumnRelationshipStrategy
void convertDefaultJoinColumnsToSpecified();
void clearSpecifiedJoinColumns();

org.eclipse.jpt.jpa.core.context.SecondaryTable
PrimaryKeyJoinColumn getSpecifiedPrimaryKeyJoinColumn(int index);
void convertDefaultPrimaryKeyJoinColumnsToSpecified();
void clearSpecifiedPrimaryKeyJoinColumns();

org.eclipse.jpt.jpa.core.context.ReferenceTable
void clearSpecifiedJoinColumns();
The other related provisional API already existed including JoinTable.clearSpecifiedInverseJoinColumns() etc

]]> Wed, 02 May 2012 16:12:35 GMT http://dev.eclipse.org/mhonarc/lists/dali-dev/msg01314.html karen.moore@xxxxxxx (Karen Butzke) [dali-dev] JPA Diagram Editor component weekly status - week 18, 2012 http://dev.eclipse.org/mhonarc/lists/dali-dev/msg01313.html A summarized status of the JPA Diagram Editor component for week 18, 2012: No change since the last week Best regards,Petya

A summarized status of the JPA Diagram Editor component for week 18, 2012:

 

  • No change since the last week

 

Best regards,

Petya

 

]]> Wed, 02 May 2012 13:56:21 GMT http://dev.eclipse.org/mhonarc/lists/dali-dev/msg01313.html petya.sabeva@xxxxxxx (Sabeva, Petya) [dali-dev] Dali Weekly Status http://dev.eclipse.org/mhonarc/lists/dali-dev/msg01312.html This week: Completed work on JAXB UI polish/usability work Completed work on performance and large project support Focus on testing and fixing bugs for M7 Bugs fixed: https://bugs.eclipse.org/bugs/buglist.cgi?bug_file_loc=%20;chfieldto=2012-04-28;query_f... This week:
  • Completed work on JAXB UI polish/usability work
  • Completed work on performance and large project support
  • Focus on testing and fixing bugs for M7
Bugs fixed:  https://bugs.eclipse.org/bugs/buglist.cgi?bug_file_loc=%20;chfieldto=2012-04-28;query_format=advanced;chfield=resolution;chfieldfrom=2012-04-21;bug_file_loc_type=allwordssubstr;chfieldvalue=FIXED;classification=WebTools;product=Dali%20JPA%20Tools ]]> Mon, 30 Apr 2012 14:34:43 GMT http://dev.eclipse.org/mhonarc/lists/dali-dev/msg01312.html neil.hauge@xxxxxxx (Neil Hauge) [dali-dev] bug 367122 minor provisional API change in M7 http://dev.eclipse.org/mhonarc/lists/dali-dev/msg01311.html For bug 367122Â I have made a minor provisional API change from a previous milestone of 3.2. The code is now the same as it was in 3.0 and is unlikely to affect adopters. On the interface JavaPersistentAttribute.JpaContainerDefinition I replaced the metho... For bug 367122Â I have made a minor provisional API change from a previous milestone of 3.2. The code is now the same as it was in 3.0 and is unlikely to affect adopters. On the interface JavaPersistentAttribute.JpaContainerDefinition I replaced the method isAssignableFrom(String) : boolean with getTypeName() : String.

karen
]]> Thu, 26 Apr 2012 01:29:06 GMT http://dev.eclipse.org/mhonarc/lists/dali-dev/msg01311.html karen.moore@xxxxxxx (Karen Butzke)