Re: [hibernate-dev] [hibernate-announce] Hibernate 3.5.0-Beta-3 release
Yeah! I've just noticed one glitch (except the NPE I managed to add ;) ). The Version numbers in the logs are not updated for annotations and entity manager. We should add them to the release procedure. Or simply remove them now that ANN and HEM are part of Core. The only drawback I see is that HEM runs before Core but I guess we could trigger the call to the static version display from HEM to Core. On 14 janv. 2010, at 06:28, Steve Ebersole wrote: JPA support is coming along nicely! See the highlights and links to all the goodies at http://in.relation.to/Bloggers/Hibernate350Beta3Release -- Steve Ebersole st...@hibernate.org Hibernate.org ___ hibernate-announce mailing list hibernate-annou...@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-announce ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] [hibernate-announce] Hibernate 3.5.0-Beta-3 release
I think we could do the same with the version string as we do in Validator ( and maybe Search, not sure ). There we read the version string from the MANIFEST file. The nice things about this is that the version in the MANIFEST is dynamically created during the build. Generally there are quite a few things we can do in the build configuration for annotations and entitymanager. The plugin configuration should be better synced with the parent pom and there are quite a few obsolete docbook resources checked in. Maybe the whole docbook stuff should be moved into the documentation directory. I will try to sort a few of these things out for the next release. --Hardy On Thu, 14 Jan 2010 07:34:50 -0300, Emmanuel Bernard emman...@hibernate.org wrote: Yeah! I've just noticed one glitch (except the NPE I managed to add ;) ). The Version numbers in the logs are not updated for annotations and entity manager. We should add them to the release procedure. Or simply remove them now that ANN and HEM are part of Core. The only drawback I see is that HEM runs before Core but I guess we could trigger the call to the static version display from HEM to Core. ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] [hibernate-announce] Hibernate 3.5.0-Beta-3 release
On Thu, 2010-01-14 at 10:17 -0300, Hardy Ferentschik wrote: I think we could do the same with the version string as we do in Validator ( and maybe Search, not sure ). There we read the version string from the MANIFEST file. The nice things about this is that the version in the MANIFEST is dynamically created during the build. We do this with core as well in terms of dynamic. We use that bytecode injjection maven plugin i wrote. Generally there are quite a few things we can do in the build configuration for annotations and entitymanager. The plugin configuration should be better synced with the parent pom and there are quite a few obsolete docbook resources checked in. Maybe the whole docbook stuff should be moved into the documentation directory. We have this unclean problem even in core: http://fisheye.jboss.org/browse/Hibernate/core/trunk/documentation/manual/old and others. I had just been waiting till we get around to actually concolidating all the docs to go through that all at once. Feel free to do it or piece of it now though. -- Steve Ebersole st...@hibernate.org Hibernate.org ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] [hibernate-announce] Hibernate 3.5.0-Beta-3 release
On 01/14/2010 05:34 AM, Emmanuel Bernard wrote: Or simply remove them now that ANN and HEM are part of Core. The only drawback I see is that HEM runs before Core but I guess we could trigger the call to the static version display from HEM to Core. They're still separate jars though, right? If so, I'd prefer to leave the version info there so that we can rule out mismatched distros by looking at logging. -CB ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] [hibernate-announce] Hibernate 3.5.0-Beta-3 release
I agree. As long as they are separate jars it makes sense to have different version strings. It makes it easier to detect if someone has library problems, eg an old annotations jar in a shared server lib. However, we should align the version string creation with whatever happens in Core, even if this means that we increase the chance getting more unreproducible build problems using Steve's magic plugin. --Hardy On Thu, 14 Jan 2010 11:57:58 -0300, Chris Bredesen cbrede...@redhat.com wrote: On 01/14/2010 05:34 AM, Emmanuel Bernard wrote: Or simply remove them now that ANN and HEM are part of Core. The only drawback I see is that HEM runs before Core but I guess we could trigger the call to the static version display from HEM to Core. They're still separate jars though, right? If so, I'd prefer to leave the version info there so that we can rule out mismatched distros by looking at logging. ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] [hibernate-announce] Hibernate 3.5.0-Beta-3 release
Good point. On Thu, 2010-01-14 at 09:57 -0500, Chris Bredesen wrote: On 01/14/2010 05:34 AM, Emmanuel Bernard wrote: Or simply remove them now that ANN and HEM are part of Core. The only drawback I see is that HEM runs before Core but I guess we could trigger the call to the static version display from HEM to Core. They're still separate jars though, right? If so, I'd prefer to leave the version info there so that we can rule out mismatched distros by looking at logging. -CB ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev -- Steve Ebersole st...@hibernate.org Hibernate.org ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] [hibernate-announce] Hibernate 3.5.0-Beta-3 release
On Thu, 2010-01-14 at 13:06 -0300, Hardy Ferentschik wrote: However, we should align the version string creation with whatever happens in Core, I agree even if this means that we increase the chance getting more unreproducible build problems using Steve's magic plugin. Btw when was the last time you saw any error from this? I'd have to imagine it was, oh i don't know, approximately 36 days ago... http://opensource.atlassian.com/projects/hibernate/browse/HHH-4625 :) -- Steve Ebersole st...@hibernate.org Hibernate.org ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] [hibernate-announce] Hibernate 3.5.0-Beta-3 release
That's right. I was already wondering why it stopped failing. I was always hoping that it would happen so that I could bug you :) Now you destroyed my hopes. On Thu, 14 Jan 2010 14:52:14 -0300, Steve Ebersole st...@hibernate.org wrote: even if this means that we increase the chance getting more unreproducible build problems using Steve's magic plugin. Btw when was the last time you saw any error from this? I'd have to imagine it was, oh i don't know, approximately 36 days ago... http://opensource.atlassian.com/projects/hibernate/browse/HHH-4625 :) ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
