Re: [hibernate-dev] evners compile error in branch 36
by Strong Liu
Sanne,
I guess you're talking search 4?
for search 4, yes, of course it should moved to jdk6, since core 4 now uses jdk6
but the previous was talking about core 3.6 which is jdk 5 compatible
-----------
Strong Liu <stliu(a)hibernate.org>
http://hibernate.org
http://github.com/stliu
On Jun 3, 2011, at 3:48 PM, Sanne Grinovero wrote:
> As extensions such as Envers and Search depend on specific versions of core, and the latter now requires Java6 it seems logic to build them with Java6 as well.
>
> In fact I already upgraded Search to Java6 for the logging annotation processor, updating both docs and wiki, but I realise we didn't really discuss this!
>
> I guess we all agree on this?
>
> Sanne
>
> On 03/giu/2011, at 08:14, Strong Liu <stliu(a)hibernate.org> wrote:
>
>> envers tries to override method in interface, which is not compilable on jdk1.5
>>
>> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.0.2:testCompile (default-testCompile) on project hibernate-envers: Compilation failure
>> [ERROR] /mnt/hudson_workspace/workspace/hibernate-core-branch36/hibernate-envers/src/test/java/org/hibernate/envers/test/entities/StrTestEntityComparator.java:[8,5] method does not override a method from its superclass
>> [ERROR] -> [Help 1]
>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.0.2:testCompile (default-testCompile) on project hibernate-envers: Compilation failure
>> /mnt/hudson_workspace/workspace/hibernate-core-branch36/hibernate-envers/src/test/java/org/hibernate/envers/test/entities/StrTestEntityComparator.java:[8,5] method does not override a method from its superclass
>>
>>
>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:199)
>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148)
>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:140)
>> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
>> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
>> at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
>> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:316)
>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:153)
>> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:451)
>> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:188)
>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:134)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>> at java.lang.reflect.Method.invoke(Method.java:585)
>> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
>> at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
>> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
>> at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
>> Caused by: org.apache.maven.plugin.CompilationFailureException: Compilation failure
>> /mnt/hudson_workspace/workspace/hibernate-core-branch36/hibernate-envers/src/test/java/org/hibernate/envers/test/entities/StrTestEntityComparator.java:[8,5] method does not override a method from its superclass
>>
>>
>> -----------
>> Strong Liu <stliu(a)hibernate.org>
>> http://hibernate.org
>> http://github.com/stliu
>>
>> _______________________________________________
>> hibernate-dev mailing list
>> hibernate-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/hibernate-dev
15 years
Re: [hibernate-dev] evners compile error in branch 36
by Adam Warski
Ah, I thought you could pass some option to javac to compile file with a given source level?
$ javac -help
(...)
-source <release> Provide source compatibility with specified release
(...)
In the pom you can specify the target java version, so the maven compiler plugin could in theory pass that option to javac ;)
Adam
On Jun 3, 2011, at 9:44 AM, Strong Liu wrote:
> well, if you're using jdk6, you won't found it, maven version doesn't matter :D
>
> hibernate 3.6 -- JDK 5
> hibernate 4 -- JDK 6
>
> -----------
> Strong Liu <stliu(a)hibernate.org>
> http://hibernate.org
> http://github.com/stliu
>
> On Jun 3, 2011, at 3:40 PM, Adam Warski wrote:
>
>> Fixed, sorry!
>>
>> I wonder why I didn't get a compile error - I've got maven 3.0.2 and I'm doing a "mvn clean install".
>> Which Maven does the Hudson job use?
>>
>> Adam
>>
>> On Jun 3, 2011, at 9:14 AM, Strong Liu wrote:
>>
>>> envers tries to override method in interface, which is not compilable on jdk1.5
>>>
>>> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.0.2:testCompile (default-testCompile) on project hibernate-envers: Compilation failure
>>>
>>> [ERROR] /mnt/hudson_workspace/workspace/hibernate-core-branch36/hibernate-envers/src/test/java/org/hibernate/envers/test/entities/StrTestEntityComparator.java:[8,5] method does not override a method from its superclass
>>>
>>> [ERROR] -> [Help 1]
>>>
>>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.0.2:testCompile (default-testCompile) on project hibernate-envers: Compilation failure
>>> /mnt/hudson_workspace/workspace/hibernate-core-branch36/hibernate-envers/src/test/java/org/hibernate/envers/test/entities/StrTestEntityComparator.java:[8,5] method does not override a method from its superclass
>>>
>>>
>>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:199)
>>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148)
>>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:140)
>>> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
>>> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
>>> at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
>>> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
>>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:316)
>>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:153)
>>> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:451)
>>> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:188)
>>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:134)
>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>> at java.lang.reflect.Method.invoke(Method.java:585)
>>> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
>>> at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
>>> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
>>> at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
>>> Caused by: org.apache.maven.plugin.CompilationFailureException: Compilation failure
>>> /mnt/hudson_workspace/workspace/hibernate-core-branch36/hibernate-envers/src/test/java/org/hibernate/envers/test/entities/StrTestEntityComparator.java:[8,5] method does not override a method from its superclass
>>>
>>>
>>>
>>> -----------
>>> Strong Liu <stliu(a)hibernate.org>
>>> http://hibernate.org
>>> http://github.com/stliu
>>>
>>
>> --
>> Adam Warski
>> http://www.warski.org
>> http://www.softwaremill.eu
>>
>>
>>
>>
>
>
--
Adam Warski
http://www.warski.org
http://www.softwaremill.eu
15 years
evners compile error in branch 36
by Strong Liu
envers tries to override method in interface, which is not compilable on jdk1.5
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.0.2:testCompile (default-testCompile) on project hibernate-envers: Compilation failure
[ERROR] /mnt/hudson_workspace/workspace/hibernate-core-branch36/hibernate-envers/src/test/java/org/hibernate/envers/test/entities/StrTestEntityComparator.java:[8,5] method does not override a method from its superclass
[ERROR] -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.0.2:testCompile (default-testCompile) on project hibernate-envers: Compilation failure
/mnt/hudson_workspace/workspace/hibernate-core-branch36/hibernate-envers/src/test/java/org/hibernate/envers/test/entities/StrTestEntityComparator.java:[8,5] method does not override a method from its superclass
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:199)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:140)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:316)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:153)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:451)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:188)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:134)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: org.apache.maven.plugin.CompilationFailureException: Compilation failure
/mnt/hudson_workspace/workspace/hibernate-core-branch36/hibernate-envers/src/test/java/org/hibernate/envers/test/entities/StrTestEntityComparator.java:[8,5] method does not override a method from its superclass
-----------
Strong Liu <stliu(a)hibernate.org>
http://hibernate.org
http://github.com/stliu
15 years
Broken ManagedProviderConnectionHelper
by Dmitry Geraskov
Hi, Steve,
I just looked in ManagedProviderConnectionHelper which is used in
SchemaExport, SchemaUpdate, SchemaValidator and it is broken.
It is never creates a connection, and this make impossible to run
SchemaExport, SchemaUpdate, SchemaValidator configured by cfg.
I guess the class is going to be removed, but it is bad it is broken in
the "transitional" preriod.
Dmitry
15 years
Release Connection provider resources
by Dmitry Geraskov
Hey, guys,
in Hibernate 3 you had ConnectionProvider#close() method which releases
all the resources used by the connection provider.
In hibernate 4 ConnectionProvider is a service without this method, but
you have Stoppable interface with stop() method which I guess do this work.
But the problem is I can't use instanceof to determine whether current
connection provider is Stoppable, because internally hibernate uses proxyes.
What is right way to replace old ConnectionProvider#close()?
Dmitry Geraskov
15 years
compile hibernate4 alpha3 using java5
by gioacchinomauri＠libero.it
Hi there,
is it possible to compile hibernate4 using java5 ? I've seen there is some
errors on alpha3 but i don't know if java5 should be supported or not.
To be more specific i got errors on "org.hibernate.build.gradle.inject.
InjectionAction" because it uses an "@Override" annotation against a method
declared in an interface ("org.gradle.api.Action") which is not allowed in
java5 (see here: http://dertompson.com/2008/01/25/override-specification-
changes-in-java-6/).
I posted a similar message on hibernate users forum but i think it's the wrong
place, so sorry for the double question.
Thanks
15 years
discussion about impact of using TransactionSynchronizationRegistry in AS7...
by Scott Marlow
I posted a message on the as7-dev ml
(http://lists.jboss.org/pipermail/jboss-as7-dev/2011-May/002254.html),
about switching to use the TransactionSynchronizationRegistry.
Do any Hibernate projects currently register Transaction synchronization
objects? Do they currently register synchronizations via
TransactionSynchronizationRegistry (TSR)? I already know the answer for
Hibernate 4.0 core (integration code can influence either interface to
be used (TX or TSR)).
I'm trying to get a sense for, what would happen if container managed
(AS7) session beans were registered with the active JTA transaction via
the TSR.
If AS7 switches to use the TSR, I think that Hibernate might need to
ensure that it doesn't attempt to register with the TX too late.
See http://pastie.org/1836698 for an example of what would happen if a
TSR synchronization object is already present and someone tries to
register a TX synchronization after tx.commit has been started.
I cross posted a similar message on Infinispan-dev for input...
Thanks,
Scott
15 years
@hibernate_dev setup and pushing GitHub commit messages
by Emmanuel Bernard
Hi guys,
I've setup @hibernate_dev on Twitter and made GitHub to push commit messages to the account.
If you are interested in the commit messages, just follow this account.
And of course, you can follow @hibernate which is Hibernate team's twitter account (low traffic).
15 years
Re: [hibernate-dev] Fwd: something wrong with our git repo?
by Hardy Ferentschik
On Wed, 01 Jun 2011 10:15:54 +0200, Sanne Grinovero
<sanne.grinovero(a)gmail.com> wrote:
> Some time ago I experienced a similar issue with Hibernate Core's
> repository,
> and solved it by renaming my master, checking out a fresh copy and
> rebasing in my changes from my local copy.
Right. That was the second option. Keep what was on master on GitHub and
rebasing the local changes on top of it.
We did it the other way around, because we thought that most people
would have the state we had locally. So restoring this would create less
issues.
> From what I understood, (when it happened before) it seemed that
> somebody had renamed the master from another branch, but I could have
> messed up differently.
Well, I stay away from renaming master :-)
In the long run I would like us to move Core development to the same
development
style we have in Search and Valiator. Everything is done via pull requests.
Not only would this prevent situation like this one, but it also increases
code awareness, since you see what is happening across the whole code base.
Maybe Search and Validator are a little easier to handle, because we are
less
people working on it, but I think this should not stop us to try a similar
approach on Core.
Maybe not a good time to start right away with this due to the amount of
changes
atm, but maybe once the code settles a little more ...
--Hardy
15 years
published groupIds
by Steve Ebersole
As we discussed in a meeting I think 2 weeks ago, I went ahead and spoke
with Paul about renaming the groupIds we use for publishing. He said he
thought it was fine. He did not foresee any issue with doing that.
--
Steve Ebersole <steve(a)hibernate.org>
http://hibernate.org
15 years
