December 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-1189) Fix Oracle JVM version comparison for new JDK 9 version schema

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1189?page=com.atlassian.jira.plugi... ] James Perkins reassigned WFCORE-1189: ------------------------------------- Assignee: Brian Stansberry (was: James Perkins) > Fix Oracle JVM version comparison for new JDK 9 version schema > -------------------------------------------------------------- > > Key: WFCORE-1189 > URL: https://issues.jboss.org/browse/WFCORE-1189 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: James Perkins > Assignee: Brian Stansberry > > JDK 9 is going to use a [new version schema|https://blogs.oracle.com/java-platform-group/entry/a_new_jdk_9_ver...] based on [JEP-223|http://openjdk.java.net/jeps/223]. The current {{JvmOptionsBuilderFactory}} would return version 7 if a the {{java.specification.version}} system property returned {{9.0.0}}. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1189) Fix Oracle JVM version comparison for new JDK 9 version schema

by James Perkins (JIRA)

James Perkins created WFCORE-1189: ------------------------------------- Summary: Fix Oracle JVM version comparison for new JDK 9 version schema Key: WFCORE-1189 URL: https://issues.jboss.org/browse/WFCORE-1189 Project: WildFly Core Issue Type: Bug Components: Domain Management Reporter: James Perkins Assignee: James Perkins JDK 9 is going to use a [new version schema|https://blogs.oracle.com/java-platform-group/entry/a_new_jdk_9_ver...] based on [JEP-223|http://openjdk.java.net/jeps/223]. The current {{JvmOptionsBuilderFactory}} would return version 7 if a the {{java.specification.version}} system property returned {{9.0.0}}. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-459) javassist should be exported to Hibernate (native) applications

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-459?page=com.atlassian.jira.plugin.s... ] Scott Marlow updated WFLY-459: ------------------------------ Summary: javassist should be exported to Hibernate (native) applications (was: javassist should be exported to JPA/Hibernate (native) applications) > javassist should be exported to Hibernate (native) applications > --------------------------------------------------------------- > > Key: WFLY-459 > URL: https://issues.jboss.org/browse/WFLY-459 > Project: WildFly > Issue Type: Task > Components: JPA / Hibernate > Reporter: Scott Marlow > Assignee: Scott Marlow > Fix For: 10.0.0.CR5 > > > Originally this jira was to stop exporting the javassist module to JPA deployments but it turns out that is fine to do. In addition, native Hibernate applications that depend on Hibernate, should also get the javassist dependency. > # native Hibernate applications will get the javassist dependency via the application dependency on org.hibernate. > # container managed JPA applications will get the javassist dependency via org.jboss.as.jpa.processor.JPADependencyProcessor (JPA deployer). > # container managed JPA applications that embed their own copy of Hibernate jars will also get the javassist dependency via org.jboss.as.jpa.processor.JPADependencyProcessor (JPA deployer). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-459) javassist should also be exported to Hibernate (native) applications

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-459?page=com.atlassian.jira.plugin.s... ] Scott Marlow updated WFLY-459: ------------------------------ Summary: javassist should also be exported to Hibernate (native) applications (was: javassist should be exported to Hibernate (native) applications) > javassist should also be exported to Hibernate (native) applications > -------------------------------------------------------------------- > > Key: WFLY-459 > URL: https://issues.jboss.org/browse/WFLY-459 > Project: WildFly > Issue Type: Task > Components: JPA / Hibernate > Reporter: Scott Marlow > Assignee: Scott Marlow > Fix For: 10.0.0.CR5 > > > Originally this jira was to stop exporting the javassist module to JPA deployments but it turns out that is fine to do. In addition, native Hibernate applications that depend on Hibernate, should also get the javassist dependency. > # native Hibernate applications will get the javassist dependency via the application dependency on org.hibernate. > # container managed JPA applications will get the javassist dependency via org.jboss.as.jpa.processor.JPADependencyProcessor (JPA deployer). > # container managed JPA applications that embed their own copy of Hibernate jars will also get the javassist dependency via org.jboss.as.jpa.processor.JPADependencyProcessor (JPA deployer). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-459) javassist should be exported to JPA/Hibernate (native) applications

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-459?page=com.atlassian.jira.plugin.s... ] Scott Marlow commented on WFLY-459: ----------------------------------- renamed jira to reflect that it is fine for the JPA deployer to export the javassist dependency to applications. Also, Hibernate native applications will get the javassist dependency via the org.hibernate module (now changed to export javassist). > javassist should be exported to JPA/Hibernate (native) applications > ------------------------------------------------------------------- > > Key: WFLY-459 > URL: https://issues.jboss.org/browse/WFLY-459 > Project: WildFly > Issue Type: Task > Components: JPA / Hibernate > Reporter: Scott Marlow > Assignee: Scott Marlow > Fix For: 10.0.0.CR5 > > > Originally this jira was to stop exporting the javassist module to JPA deployments but it turns out that is fine to do. In addition, native Hibernate applications that depend on Hibernate, should also get the javassist dependency. > # native Hibernate applications will get the javassist dependency via the application dependency on org.hibernate. > # container managed JPA applications will get the javassist dependency via org.jboss.as.jpa.processor.JPADependencyProcessor (JPA deployer). > # container managed JPA applications that embed their own copy of Hibernate jars will also get the javassist dependency via org.jboss.as.jpa.processor.JPADependencyProcessor (JPA deployer). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-459) javassist should be exported to JPA/Hibernate (native) applications

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-459?page=com.atlassian.jira.plugin.s... ] Scott Marlow updated WFLY-459: ------------------------------ Summary: javassist should be exported to JPA/Hibernate (native) applications (was: javassist should be exported to JPA/Hibernate applications) > javassist should be exported to JPA/Hibernate (native) applications > ------------------------------------------------------------------- > > Key: WFLY-459 > URL: https://issues.jboss.org/browse/WFLY-459 > Project: WildFly > Issue Type: Task > Components: JPA / Hibernate > Reporter: Scott Marlow > Assignee: Scott Marlow > Fix For: 10.0.0.CR5 > > > Originally this jira was to stop exporting the javassist module to JPA deployments but it turns out that is fine to do. In addition, native Hibernate applications that depend on Hibernate, should also get the javassist dependency. > # native Hibernate applications will get the javassist dependency via the application dependency on org.hibernate. > # container managed JPA applications will get the javassist dependency via org.jboss.as.jpa.processor.JPADependencyProcessor (JPA deployer). > # container managed JPA applications that embed their own copy of Hibernate jars will also get the javassist dependency via org.jboss.as.jpa.processor.JPADependencyProcessor (JPA deployer). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-459) javassist should be exported to container managed JPA + Hibernate native applications

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-459?page=com.atlassian.jira.plugin.s... ] Scott Marlow updated WFLY-459: ------------------------------ Summary: javassist should be exported to container managed JPA + Hibernate native applications (was: correct JPA dependency injection (stop injecting javassist)) > javassist should be exported to container managed JPA + Hibernate native applications > ------------------------------------------------------------------------------------- > > Key: WFLY-459 > URL: https://issues.jboss.org/browse/WFLY-459 > Project: WildFly > Issue Type: Task > Components: JPA / Hibernate > Reporter: Scott Marlow > Assignee: Scott Marlow > Fix For: 10.0.0.CR5 > > > Originally this jira was to stop exporting the javassist module to JPA deployments but it turns out that is fine to do. In addition, native Hibernate applications that depend on Hibernate, should also get the javassist dependency. > # native Hibernate applications will get the javassist dependency via the application dependency on org.hibernate. > # container managed JPA applications will get the javassist dependency via org.jboss.as.jpa.processor.JPADependencyProcessor (JPA deployer). > # container managed JPA applications that embed their own copy of Hibernate jars will also get the javassist dependency via org.jboss.as.jpa.processor.JPADependencyProcessor (JPA deployer). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-459) javassist should be exported to JPA/Hibernate applications

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-459?page=com.atlassian.jira.plugin.s... ] Scott Marlow updated WFLY-459: ------------------------------ Summary: javassist should be exported to JPA/Hibernate applications (was: javassist should be exported to container managed JPA + Hibernate native applications) > javassist should be exported to JPA/Hibernate applications > ---------------------------------------------------------- > > Key: WFLY-459 > URL: https://issues.jboss.org/browse/WFLY-459 > Project: WildFly > Issue Type: Task > Components: JPA / Hibernate > Reporter: Scott Marlow > Assignee: Scott Marlow > Fix For: 10.0.0.CR5 > > > Originally this jira was to stop exporting the javassist module to JPA deployments but it turns out that is fine to do. In addition, native Hibernate applications that depend on Hibernate, should also get the javassist dependency. > # native Hibernate applications will get the javassist dependency via the application dependency on org.hibernate. > # container managed JPA applications will get the javassist dependency via org.jboss.as.jpa.processor.JPADependencyProcessor (JPA deployer). > # container managed JPA applications that embed their own copy of Hibernate jars will also get the javassist dependency via org.jboss.as.jpa.processor.JPADependencyProcessor (JPA deployer). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-459) correct JPA dependency injection (stop injecting javassist)

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-459?page=com.atlassian.jira.plugin.s... ] Scott Marlow updated WFLY-459: ------------------------------ Description: Originally this jira was to stop exporting the javassist module to JPA deployments but it turns out that is fine to do. In addition, native Hibernate applications that depend on Hibernate, should also get the javassist dependency. # native Hibernate applications will get the javassist dependency via the application dependency on org.hibernate. # container managed JPA applications will get the javassist dependency via org.jboss.as.jpa.processor.JPADependencyProcessor (JPA deployer). # container managed JPA applications that embed their own copy of Hibernate jars will also get the javassist dependency via org.jboss.as.jpa.processor.JPADependencyProcessor (JPA deployer). was:Originally this jira was to stop exporting the javassist module to JPA deployments but it turns out that is fine to do. In addition, native Hibernate applications that depend on Hibernate, should also get the javassist dependency. > correct JPA dependency injection (stop injecting javassist) > ----------------------------------------------------------- > > Key: WFLY-459 > URL: https://issues.jboss.org/browse/WFLY-459 > Project: WildFly > Issue Type: Task > Components: JPA / Hibernate > Reporter: Scott Marlow > Assignee: Scott Marlow > Fix For: 10.0.0.CR5 > > > Originally this jira was to stop exporting the javassist module to JPA deployments but it turns out that is fine to do. In addition, native Hibernate applications that depend on Hibernate, should also get the javassist dependency. > # native Hibernate applications will get the javassist dependency via the application dependency on org.hibernate. > # container managed JPA applications will get the javassist dependency via org.jboss.as.jpa.processor.JPADependencyProcessor (JPA deployer). > # container managed JPA applications that embed their own copy of Hibernate jars will also get the javassist dependency via org.jboss.as.jpa.processor.JPADependencyProcessor (JPA deployer). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-459) correct JPA dependency injection (stop injecting javassist)

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-459?page=com.atlassian.jira.plugin.s... ] Scott Marlow updated WFLY-459: ------------------------------ Description: Originally this jira was to stop exporting the javassist module to JPA deployments but it turns out that is fine to do. In addition, native Hibernate applications that depend on Hibernate, should also get the javassist dependency. (was: Rather than export the javassist dependency, see if we can change javassist to generate proxies for the application classes which aren't on the hibernate module class path.) > correct JPA dependency injection (stop injecting javassist) > ----------------------------------------------------------- > > Key: WFLY-459 > URL: https://issues.jboss.org/browse/WFLY-459 > Project: WildFly > Issue Type: Task > Components: JPA / Hibernate > Reporter: Scott Marlow > Assignee: Scott Marlow > Fix For: 10.0.0.CR5 > > > Originally this jira was to stop exporting the javassist module to JPA deployments but it turns out that is fine to do. In addition, native Hibernate applications that depend on Hibernate, should also get the javassist dependency. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2015