December 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-1192) Deprecate permgen attributes in the management model

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-1192: ---------------------------------------- Summary: Deprecate permgen attributes in the management model Key: WFCORE-1192 URL: https://issues.jboss.org/browse/WFCORE-1192 Project: WildFly Core Issue Type: Bug Components: Domain Management Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 2.0.5.Final The permgen size attributes no longer do anything in a core 2.0 or later server, as we require JDK 8 and our code ignores these if JDK 8 or later is running. So we should deprecate the config elements and log a message if they are used. Part of the parent task for the management model itself. I'll do this in 2.0.5 because I don't mind tweaking the API in a micro just to add deprecation information. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1154) Deprecate permgen attributes in host and server config level jvm settings

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1154?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1154: ------------------------------------- Issue Type: Bug (was: Task) > Deprecate permgen attributes in host and server config level jvm settings > ------------------------------------------------------------------------- > > Key: WFCORE-1154 > URL: https://issues.jboss.org/browse/WFCORE-1154 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Brian Stansberry > Fix For: 3.0.0.Alpha1 > > > The permgen size attributes no longer do anything in a core 2.0 or later server, as we require JDK 8 and our code ignores these if JDK 8 or later is running. So we should deprecate the config elements and log a message if they are used, and add deprecation text in the xsd. > I considered only deprecating these attributes if they appear in the host=* tree, and not doing the ones for domain-wide resources, since those could be used for legacy slaves running JDK < 8. But I think the distinction isn't worth the effort. First, these things are deprecated in all cases in the sense that they may go away in some future release. And second, all that happens is an INFO message is logged, and the chances that message may help some JDK 8 user offsets the chance that a JDK < 8 user would be annoyed by some spurious INFO logging. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1191) Deprecate permgen attributes in the management model

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1191?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1191: ------------------------------------- Description: The permgen size attributes no longer do anything in a core 2.0 or later server, as we require JDK 8 and our code ignores these if JDK 8 or later is running. So we should deprecate the config elements and log a message if they are used. Part of the parent task for the management model itself. I'll do this in 2.0.5 because I don't mind tweaking the API in a micro just to add deprecation information. was:Part of the parent task for the management model itself. I'll do this in 2.0.5 because I don't mind tweaking the API in a micro just to add deprecation information. > Deprecate permgen attributes in the management model > ---------------------------------------------------- > > Key: WFCORE-1191 > URL: https://issues.jboss.org/browse/WFCORE-1191 > Project: WildFly Core > Issue Type: Sub-task > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 2.0.5.Final > > > The permgen size attributes no longer do anything in a core 2.0 or later server, as we require JDK 8 and our code ignores these if JDK 8 or later is running. So we should deprecate the config elements and log a message if they are used. > Part of the parent task for the management model itself. I'll do this in 2.0.5 because I don't mind tweaking the API in a micro just to add deprecation information. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1191) Deprecate permgen attributes in the management model

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1191?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1191: ------------------------------------- Parent: (was: WFCORE-1154) Issue Type: Bug (was: Sub-task) > Deprecate permgen attributes in the management model > ---------------------------------------------------- > > Key: WFCORE-1191 > URL: https://issues.jboss.org/browse/WFCORE-1191 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 2.0.5.Final > > > The permgen size attributes no longer do anything in a core 2.0 or later server, as we require JDK 8 and our code ignores these if JDK 8 or later is running. So we should deprecate the config elements and log a message if they are used. > Part of the parent task for the management model itself. I'll do this in 2.0.5 because I don't mind tweaking the API in a micro just to add deprecation information. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1191) Deprecate permgen attributes in the management model

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-1191: ---------------------------------------- Summary: Deprecate permgen attributes in the management model Key: WFCORE-1191 URL: https://issues.jboss.org/browse/WFCORE-1191 Project: WildFly Core Issue Type: Sub-task Components: Domain Management Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 2.0.5.Final Part of the parent task for the management model itself. I'll do this in 2.0.5 because I don't mind tweaking the API in a micro just to add deprecation information. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1190) Deprecate permgen attributes in the xsd

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-1190: ---------------------------------------- Summary: Deprecate permgen attributes in the xsd Key: WFCORE-1190 URL: https://issues.jboss.org/browse/WFCORE-1190 Project: WildFly Core Issue Type: Sub-task Components: Domain Management Reporter: Brian Stansberry Fix For: 3.0.0.Alpha1 Part of the parent task related to changing the xsd. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[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)

10 years, 7 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)

10 years, 7 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)

10 years, 7 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)

10 years, 7 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2015