The fix goes like this:
if ( filePart.startsWith( "/" ) || new File(url.getFile()).isAbsolute() ) {
// the URL is already an absolute form
return url;
}
The reason why it works on Linux/Macs is that absolute paths start with "/".
With this fix works on Windows too, but I wonder if we shoul
I've created a pull request implements option A) (creates comparators
for PrimitiveByteArrayTypeDescriptor,
PrimitiveCharacterArrayTypeDescriptor, ByteArrayTypeDescriptor, and
CharacterArrayTypeDescriptor.
I'm still not sure if it makes sense to have a comparators for arrays.
Steve, please take a
Hi,
I managed to find what caused this test to start failing. The reason is
this commit:
Commit: 5c77f279afaecb505f7a22bfa05c172b493096bd [5c77f27]
Parents: 8670b4211e
Author: Steve Ebersole
Date: Tuesday, January 12, 2016 11:21:54 PM
Commit Date: Tuesday, January 12, 2016 11:22:19 PM
Labels: HE
A PAR is just an archive with a META-INF/persistence.xml file in it. The
JPA spec does cover this. The extension is irrelevant.
On Wed, Mar 9, 2016 at 4:08 PM Sanne Grinovero wrote:
> I remember JBoss had "HAR" deployments to package Hibernate models and
> PU definitions.. as far as I know thi
I remember JBoss had "HAR" deployments to package Hibernate models and
PU definitions.. as far as I know this was a JBoss only thing, it
wouldn't surprise me if other app servers experimented with similar
non-standardized archives.
https://docs.jboss.org/jbossas/jboss4guide/r3/html/ch13.html
On 9
Hi,
The part is backslashes comes from the absolute path set by Gradle when
supplying the module OS folder.
The right part containing slashes is the one set in persistence.xml.
I'll try to replace backslashes with slashes and see how it goes.
I was curious if people use the jar-file with absolute
We usually strive on having functionalities work on both Java EE and
Java SE.
you example though shows a mix of forward and backslash in your
, is that expected ?
Emmanuel
On Wed 2016-03-09 17:05, Vlad Mihalcea wrote:
> Hi,
>
> I have two tests in the PackagedEntityManagerTest unit test that fai
Hi,
I have two tests in the PackagedEntityManagerTest unit test that fail on my
machine, but work just fine for everybody else.
It could be an OS thing or not, but during the check, I found hat we are
testing against an use case that is not found in the JPA spec.
The testExternalJar() creates an
