Its time for the JBoss Community Recognition Awards. I have started
getting together a list of nominations and wanted ask the Hibernate
community for any feedback. So, if there is anyone you would like to
see nominated please send the details, either to me or to the list.
hibernate-commons-annotations 4.0.2.Final was just released. It contains only one fix: https://hibernate.atlassian.net/browse/HCANN-51. The manifest was improved to support usage in OSGi environments.
And that's it! Exciting, eh?
Red Hat Software Engineer, Hibernate
Every once in while I'm noticing actions of JIRA user "Anonymous", e.g.
https://hibernate.atlassian.net/browse/HSEARCH-550 (Anonymous made
the transition from "Open" to "Pull request sent").
Until now I assumed one needs to be logged into JIRA to perform any changes
to an issue.
So I'm wondering whether that assumption was just wrong or whether the
possibility for anonymous actions is actually not intended. In case of the
latter, maybe its caused by the recent migration?
it seems the animal sniffer plugin made it now into the ORM build. Unfortunately, I am seeing this when trying a 'gradlew clean build':
FAILURE: Build failed with an exception.
Build file '/Users/hardy/work/hibernate/git/core/orm-4.0/build.gradle' line: 329
* What went wrong:
Execution failed for task ':hibernate-c3p0:checkJavaApiSignature'.
> Could not resolve all dependencies for configuration ':hibernate-c3p0:animalSniffer'.
> Could not resolve org.codehaus.mojo:animal-sniffer-ant-tasks:1.8.
> Could not resolve org.codehaus.mojo:animal-sniffer-parent:1.8.
> Could not HEAD 'http://repo1.maven.org/maven2/org/codehaus/mojo/animal-sniffer-parent/1.8...'.
> Connection reset
Anything I need to do to get this to work? AFAICS there is no jar in http://repo1.maven.org/maven2/org/codehaus/mojo/animal-sniffer-parent/1.8,
so I am not sure why the build tries to download one.
I am running into some difficulties with writing the release task in the
Gradle build, specifically with the ordering between the various tasks
(e.g., sometimes a jar is built and then clean is run and then Gradle
tries to upload it).
The suggested way around this is to use the mustRunAfter hook (kind of
similar to a dependsOn). But mustRunAfter was only added in 1.6.
Anyone have a problem with upgrading the build to use Gradle 1.6?
I'd like to follow up on the discussion started here. I was asked to
port an existing application to Hana, so my first task was to write a
hibernate dialect for it. I've completed this and so far it is working
nicely in the integration tests for the application. My app is still
using Hibernate 3.3, so that was my starting point, but with a few small
changes it also compiles against the current git master. Is there still
interest in such a dialect? Should I open a jira ticket and submit a
I am working on scripting more of the release steps into the Gradle
build scripts. When it comes to uploading the release bundles to
SourceForge we have a choice to make. I will use rsync since we already
require people doing a release to have it installed because
docs.jboss.org uploads require it.
I can either account for the various SourceForge users in the script, or
we could define a single user in the SourceForge Hibernate project that
is there for uploading release bundles from the build. That upload user
would have just the permissions necessary to upload. We would need,
however, to manage getting keys uploaded to that user. Whereas if we
used our own SourceForge users we'd simply use our own keys.
Personally I'd rather just use our own users and account for the
different usernames in the script (read from ~/.gradle/gradle.settings