Re: [infinispan-dev] infinispan 5.3.0 build issues

2014-05-23 Thread Mohan Dhawan
Hi Dan, Thanks for the reply. Apparently, the .jar was not getting built. Instead, an *-tests.jar.lastUpdated file was being created in the corresponding folder in the repository. Merely, renaming the *.jar.lastUpdated file to *.jar did the trick. However, now I get the following error: [INFO]

Re: [infinispan-dev] On ParserRegistry and classloaders

2014-05-23 Thread Galder Zamarreño
Hey Sanne, I’ve looked at ParserRegistry and not sure I see the changes you are referring to… From what I’ve seen, ParserRegistry has taken class loader in the constructor since the start. I suspect you might be referring to classloader related changes as a result of OSGI integration?

Re: [infinispan-dev] infinispan 5.3.0 build issues

2014-05-23 Thread Radim Vansa
In Maven repository, the *.jar.lastUpdated is no JAR - it's just file with timestamps of last attempt to download the files from external source. The only thing you should do with these files is delete them if you want to reattempt the download again. Radim On 05/23/2014 09:02 AM, Mohan

Re: [infinispan-dev] infinispan 5.3.0 build issues

2014-05-23 Thread Mohan Dhawan
Hi Radim, I did try to delete them but the compilation process kept halting at the same places every time. So, I just renamed the file. I've purged the repository, tried doing a clean install, but still get the errors --- the latest being the org.apache.maven.plugins:maven-surefire-plugin

Re: [infinispan-dev] infinispan 5.3.0 build issues

2014-05-23 Thread Tristan Tarrant
Mohan, first, clear your local maven repo from any Infinispan artifacts (I assume you are using Linux): $ rm -rf $HOME/.m2/repository/org/infinispan now attempt the build again. Please note: tests *must* be built (but you don't need to run them). Therefore you need to add either -DskipTests

[infinispan-dev] Early Access builds for JDK 9 b13, JDK 8u20 b15 and JDK 7u60 b15 are available on java.net

2014-05-23 Thread Rory O'Donnell Oracle, Dublin Ireland
Hi Galder, Early Access builds for JDK 9 b13 https://jdk9.java.net/download/, JDK 8u20 b15 https://jdk8.java.net/download.html and JDK 7u60 b15 https://jdk7.java.net/download.html are available on java.net. As we enter the later phases of development for JDK 7u60 JDK 8u20 , please log any

Re: [infinispan-dev] infinispan 5.3.0 build issues

2014-05-23 Thread Mohan Dhawan
Hi Tristan, I was using -Dmaven.test.skip and the build was failing. Using -Dmaven.test.skip.exec worked just like a charm. Thanks for the help. Regards, mohan On Friday 23 May 2014 01:08 PM, Tristan Tarrant wrote: Mohan, first, clear your local maven repo from any Infinispan artifacts

Re: [infinispan-dev] Early Access builds for JDK 9 b13, JDK 8u20 b15 and JDK 7u60 b15 are available on java.net

2014-05-23 Thread Galder Zamarreño
Hi Rory, Is https://bugs.openjdk.java.net/browse/JDK-8036554 being backported to 7u60? Cheers, On 23 May 2014, at 10:11, Rory O'Donnell Oracle, Dublin Ireland rory.odonn...@oracle.com wrote: Hi Galder, Early Access builds for JDK 9 b13, JDK 8u20 b15 and JDK 7u60 b15 are available on

Re: [infinispan-dev] JPA CacheStore doc

2014-05-23 Thread Dan Berindei
Please open a single JIRA for all of them. On Tue, May 20, 2014 at 10:29 AM, Emmanuel Bernard emman...@hibernate.orgwrote: Hi guys, I was reading http://infinispan.org/docs/7.0.x/user_guide/user_guide.html#_jpa_cache_store I have a few remarks and questions. The links on 7.3. Additional

Re: [infinispan-dev] JPA CacheStore doc

2014-05-23 Thread Emmanuel Bernard
https://issues.jboss.org/browse/ISPN-4320 On 23 May 2014, at 12:47, Dan Berindei dan.berin...@gmail.com wrote: Please open a single JIRA for all of them. On Tue, May 20, 2014 at 10:29 AM, Emmanuel Bernard emman...@hibernate.org wrote: Hi guys, I was reading

Re: [infinispan-dev] On ParserRegistry and classloaders

2014-05-23 Thread Sanne Grinovero
On 23 May 2014 08:03, Galder Zamarreño gal...@redhat.com wrote: Hey Sanne, I’ve looked at ParserRegistry and not sure I see the changes you are referring to… From what I’ve seen, ParserRegistry has taken class loader in the constructor since the start. Yes, and that was good as we've