September 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFWIP-196) Operator missing volumes from secrets and config maps

by Martin Choma (Jira)

[ https://issues.jboss.org/browse/WFWIP-196?page=com.atlassian.jira.plugin.... ] Martin Choma updated WFWIP-196: ------------------------------- Summary: Operator missing volumes from secrets and config maps (was: Operator missing volumes from secrets and confgi maps ) > Operator missing volumes from secrets and config maps > ------------------------------------------------------ > > Key: WFWIP-196 > URL: https://issues.jboss.org/browse/WFWIP-196 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Martin Choma > Assignee: Jeff Mesnil > Priority: Blocker > > Operator is missing way of configuring volumes from secets and config maps > - secrets > -- configuring keystore in ssl > -- configuring keystore for jgroups ASYNC encryption in jgroups (DNS_PING, KUBE_PING)) > - config map > -- Microprofile Config and reading properties from ConfigMap > -- running custom CLI script from config map (EAP7-892) -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12300) Convert to Jakarta EE 8 specification APIs

by Marek Kopecky (Jira)

[ https://issues.jboss.org/browse/WFLY-12300?page=com.atlassian.jira.plugin... ] Marek Kopecky commented on WFLY-12300: -------------------------------------- This jira blocks EAP7-1114 RFE, so I increase the priority of this jira to blocker > Convert to Jakarta EE 8 specification APIs > ------------------------------------------ > > Key: WFLY-12300 > URL: https://issues.jboss.org/browse/WFLY-12300 > Project: WildFly > Issue Type: Task > Components: Server > Reporter: Brian Stansberry > Assignee: Scott Marlow > Priority: Blocker > Fix For: 18.0.0.Final > > > This is a top-level task for moving WildFly to specification API artifacts associated with Jakarta EE 8. > The Jakarta EE 8 spec APIs are meant to be fully compatible with their Java EE 8 analogues, so this is not expected to result in runtime behavioral differences. > I don't anticipate code changes specific to this top level task. Instead changes will be associated with other issues linked to this one. > The overall goal is to use API jars that either directly come from the Jakarta EE projects, or that use code closely based on those projects; i.e. that are forks derived from the Jakarta EE code that incorporate jboss.org specific changes and whose maintainers monitor the Jakarta EE projects and bring over needed changes and contribute any relevant jboss.org changes back. > For each JBoss specification API fork that existed in EAP 7.2, a designated owner for that API jar has been determined. The task for each owner consists of: > # Create/update a jboss.org Jakarta fork. > # Track work on that fork via issues in the https://issues.jboss.org/projects/JBEE JIRA project. If there is a high-level issue for that fork, the component owner *should* link it to this issue via a 'relates to' link. > # For the fork, the component owner *must* create a WFLY or WFCORE JIRA to track the change of the WildFly code to use the Jarkarta EE based artifact. That can either be a subtask of this task, or a separate issue linked to this once such that that issue is 'incorporated by' this one. That JIRA should have priority 'Critical' and should have its Fix Version set to 18.0.0.Final or 10.0.0.Final for WFCORE. > Generally, WildFly and WildFly Core do not accept non-Final artifacts into their master branch. For projects that we are forking from the Jakarta EE projects, we are making an exception to this rule: > _Once a Jakarta API project has made a staging release and submitted the specification for formal approval, it is acceptable for the jboss.org fork of that project to produce a CR release based on the code in that staged release and ask that it be incorporated into master._ > _In fact, doing this is strongly encouraged as it allows us to further verify the fork._ > Once the staged release is approved, the component owner *must* as soon as possible (e.g. the next working day) produce a .Final artifact from the fork and submit a component upgrade PR. > For artifacts that will not involve a fork (e.g. JPA), the component owner should plan to file a PR moving to the Jakarta artifact (e.g. jakarta.persistence:jakarta.persistence-api) as soon as the official version after Jakarta is available in maven central (after Jakarta EE 8 final release). > Following are the relevant APIs, organized by the maven GA of the artifact produced by the Jakarta project, along with the 'owner' of that component: > ||API||Owner|| > |jakarta.annotation:jakarta.annotation-api|Yeray Borges| > |jakarta.batch:jakarta.batch-api|Cheng Fang| > |jakarta.ejb:jakarta.ejb-api|Cheng Fang/Tomasz Adamski| > |jakarta.el:jakarta.el-api|Scott Marlow| > |jakarta.enterprise.concurrent:jakarta.enterprise.concurrent-api|Eduardo Martins| > |jakarta.faces:jakarta.faces-api|Farah Juma| > |jakarta.interceptor:jakarta.interceptor-api|Yeray Borges| > |jakarta.jms:jakarta.jms-api|Emmanuel Hugonnet| > |jakarta.management.j2ee:jakarta.management.j2ee-api|Jeff Mesnil| > |jakarta.resource:jakarta.resource-api|Stefano Maestri| > |jakarta.security.auth.message:jakarta.security.auth.message-api|Darran Lofthouse / Farah Juma| > |jakarta.security.jacc:jakarta.security.jacc-api|Darran Lofthouse / Farah Juma| > |jakarta.servlet:jakarta.servlet-api|Flavia Rainone| > |jakarta.servlet.jsp:jakarta.servlet.jsp-api|Flavia Rainone| > |jakarta.transaction:jakarta.transaction-api|Tom Jenkinson| > |jakarta.websocket:jakarta.websocket-all|Flavia Rainone| > |jakarta.ws.rs:jakarta.ws.rs-api|Ron Sigal| > |jakarta.xml.bind:jakarta.xml.bind-api|Jim Ma| > |jakarta.xml.rpc:jakarta.xml.rpc-api|Jim Ma| > |jakarta.xml.soap:jakarta.xml.soap-api|Jim Ma| > |jakarta.xml.ws:jakarta.xml.ws-api|Jim Ma| > -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12300) Convert to Jakarta EE 8 specification APIs

by Marek Kopecky (Jira)

[ https://issues.jboss.org/browse/WFLY-12300?page=com.atlassian.jira.plugin... ] Marek Kopecky updated WFLY-12300: --------------------------------- Priority: Blocker (was: Critical) > Convert to Jakarta EE 8 specification APIs > ------------------------------------------ > > Key: WFLY-12300 > URL: https://issues.jboss.org/browse/WFLY-12300 > Project: WildFly > Issue Type: Task > Components: Server > Reporter: Brian Stansberry > Assignee: Scott Marlow > Priority: Blocker > Fix For: 18.0.0.Final > > > This is a top-level task for moving WildFly to specification API artifacts associated with Jakarta EE 8. > The Jakarta EE 8 spec APIs are meant to be fully compatible with their Java EE 8 analogues, so this is not expected to result in runtime behavioral differences. > I don't anticipate code changes specific to this top level task. Instead changes will be associated with other issues linked to this one. > The overall goal is to use API jars that either directly come from the Jakarta EE projects, or that use code closely based on those projects; i.e. that are forks derived from the Jakarta EE code that incorporate jboss.org specific changes and whose maintainers monitor the Jakarta EE projects and bring over needed changes and contribute any relevant jboss.org changes back. > For each JBoss specification API fork that existed in EAP 7.2, a designated owner for that API jar has been determined. The task for each owner consists of: > # Create/update a jboss.org Jakarta fork. > # Track work on that fork via issues in the https://issues.jboss.org/projects/JBEE JIRA project. If there is a high-level issue for that fork, the component owner *should* link it to this issue via a 'relates to' link. > # For the fork, the component owner *must* create a WFLY or WFCORE JIRA to track the change of the WildFly code to use the Jarkarta EE based artifact. That can either be a subtask of this task, or a separate issue linked to this once such that that issue is 'incorporated by' this one. That JIRA should have priority 'Critical' and should have its Fix Version set to 18.0.0.Final or 10.0.0.Final for WFCORE. > Generally, WildFly and WildFly Core do not accept non-Final artifacts into their master branch. For projects that we are forking from the Jakarta EE projects, we are making an exception to this rule: > _Once a Jakarta API project has made a staging release and submitted the specification for formal approval, it is acceptable for the jboss.org fork of that project to produce a CR release based on the code in that staged release and ask that it be incorporated into master._ > _In fact, doing this is strongly encouraged as it allows us to further verify the fork._ > Once the staged release is approved, the component owner *must* as soon as possible (e.g. the next working day) produce a .Final artifact from the fork and submit a component upgrade PR. > For artifacts that will not involve a fork (e.g. JPA), the component owner should plan to file a PR moving to the Jakarta artifact (e.g. jakarta.persistence:jakarta.persistence-api) as soon as the official version after Jakarta is available in maven central (after Jakarta EE 8 final release). > Following are the relevant APIs, organized by the maven GA of the artifact produced by the Jakarta project, along with the 'owner' of that component: > ||API||Owner|| > |jakarta.annotation:jakarta.annotation-api|Yeray Borges| > |jakarta.batch:jakarta.batch-api|Cheng Fang| > |jakarta.ejb:jakarta.ejb-api|Cheng Fang/Tomasz Adamski| > |jakarta.el:jakarta.el-api|Scott Marlow| > |jakarta.enterprise.concurrent:jakarta.enterprise.concurrent-api|Eduardo Martins| > |jakarta.faces:jakarta.faces-api|Farah Juma| > |jakarta.interceptor:jakarta.interceptor-api|Yeray Borges| > |jakarta.jms:jakarta.jms-api|Emmanuel Hugonnet| > |jakarta.management.j2ee:jakarta.management.j2ee-api|Jeff Mesnil| > |jakarta.resource:jakarta.resource-api|Stefano Maestri| > |jakarta.security.auth.message:jakarta.security.auth.message-api|Darran Lofthouse / Farah Juma| > |jakarta.security.jacc:jakarta.security.jacc-api|Darran Lofthouse / Farah Juma| > |jakarta.servlet:jakarta.servlet-api|Flavia Rainone| > |jakarta.servlet.jsp:jakarta.servlet.jsp-api|Flavia Rainone| > |jakarta.transaction:jakarta.transaction-api|Tom Jenkinson| > |jakarta.websocket:jakarta.websocket-all|Flavia Rainone| > |jakarta.ws.rs:jakarta.ws.rs-api|Ron Sigal| > |jakarta.xml.bind:jakarta.xml.bind-api|Jim Ma| > |jakarta.xml.rpc:jakarta.xml.rpc-api|Jim Ma| > |jakarta.xml.soap:jakarta.xml.soap-api|Jim Ma| > |jakarta.xml.ws:jakarta.xml.ws-api|Jim Ma| > -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12490) Upgrade BOMs and QS due to spec artifacts which groupId/artifactId changed

by Marek Kopecky (Jira)

[ https://issues.jboss.org/browse/WFLY-12490?page=com.atlassian.jira.plugin... ] Marek Kopecky updated WFLY-12490: --------------------------------- Priority: Blocker (was: Major) > Upgrade BOMs and QS due to spec artifacts which groupId/artifactId changed > ---------------------------------------------------------------------------- > > Key: WFLY-12490 > URL: https://issues.jboss.org/browse/WFLY-12490 > Project: WildFly > Issue Type: Sub-task > Components: BOM, Quickstarts > Reporter: Eduardo Martins > Assignee: Eduardo Martins > Priority: Blocker > Fix For: 18.0.0.Final > > > The Jakarta related component upgrades which changed groupId and/or artifactId of spec artifacts should be propagated to BOMs and Quickstarts projects. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12468) Rename BOMs artifactIds with javaee8-* to jakartaee8-*

by Marek Kopecky (Jira)

[ https://issues.jboss.org/browse/WFLY-12468?page=com.atlassian.jira.plugin... ] Marek Kopecky updated WFLY-12468: --------------------------------- Priority: Blocker (was: Major) > Rename BOMs artifactIds with javaee8-* to jakartaee8-* > ------------------------------------------------------ > > Key: WFLY-12468 > URL: https://issues.jboss.org/browse/WFLY-12468 > Project: WildFly > Issue Type: Sub-task > Components: BOM, Quickstarts > Reporter: Eduardo Martins > Assignee: Eduardo Martins > Priority: Blocker > > The following WildFly BOM artifactIds should be renamed to not include javaee, replacing it with jakartaee8: > * wildfly-javaee8 > * wildfly-javaee8-with-tools > Same should be done to the jboss javaee BOMs at https://github.com/jboss/jboss-javaee-specs, what should probably first be forked due to including javaee in its name too (to jboss/jboss-jakartaee-specs?). > Reference to renamed BOMs in Quickstarts project should also be updated. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12511) Update community documentation for Jakarta EE 8

by Marek Kopecky (Jira)

[ https://issues.jboss.org/browse/WFLY-12511?page=com.atlassian.jira.plugin... ] Marek Kopecky updated WFLY-12511: --------------------------------- Priority: Blocker (was: Major) > Update community documentation for Jakarta EE 8 > ----------------------------------------------- > > Key: WFLY-12511 > URL: https://issues.jboss.org/browse/WFLY-12511 > Project: WildFly > Issue Type: Task > Components: Documentation > Reporter: Scott Marlow > Assignee: Scott Marlow > Priority: Blocker > Fix For: 18.0.0.Final > > -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-196) Operator missing volumes from secrets and confgi maps

by Martin Choma (Jira)

[ https://issues.jboss.org/browse/WFWIP-196?page=com.atlassian.jira.plugin.... ] Martin Choma updated WFWIP-196: ------------------------------- Description: Operator is missing way of configuring volumes from secets and config maps - secrets -- configuring keystore in ssl -- configuring keystore for jgroups ASYNC encryption in jgroups (DNS_PING, KUBE_PING)) - config map -- Microprofile Config and reading properties from ConfigMap -- running custom CLI script from config map (EAP7-892) was: Summary: Operator missing volumes from secrets and confgi maps Operator is missing way of configuring volumes from secets and config maps - secrets -- configuring keystore in ssl -- configuring keystore for jgroups ASYNC encryption in jgroups (DNS_PING, KUBE_PING)) - config map -- Microprofile Config and reading properties from ConfigMap -- running custom CLI script from config map (EAP7-892) > Operator missing volumes from secrets and confgi maps > ------------------------------------------------------ > > Key: WFWIP-196 > URL: https://issues.jboss.org/browse/WFWIP-196 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Martin Choma > Assignee: Jeff Mesnil > Priority: Blocker > > Operator is missing way of configuring volumes from secets and config maps > - secrets > -- configuring keystore in ssl > -- configuring keystore for jgroups ASYNC encryption in jgroups (DNS_PING, KUBE_PING)) > - config map > -- Microprofile Config and reading properties from ConfigMap > -- running custom CLI script from config map (EAP7-892) -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-196) Operator missing volumes from secrets and confgi maps

by Martin Choma (Jira)

Martin Choma created WFWIP-196: ---------------------------------- Summary: Operator missing volumes from secrets and confgi maps Key: WFWIP-196 URL: https://issues.jboss.org/browse/WFWIP-196 Project: WildFly WIP Issue Type: Bug Components: OpenShift Reporter: Martin Choma Assignee: Jeff Mesnil Summary: Operator missing volumes from secrets and confgi maps Operator is missing way of configuring volumes from secets and config maps - secrets -- configuring keystore in ssl -- configuring keystore for jgroups ASYNC encryption in jgroups (DNS_PING, KUBE_PING)) - config map -- Microprofile Config and reading properties from ConfigMap -- running custom CLI script from config map (EAP7-892) -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBEE-239) Release JBoss / Jakarta JASPI 2.0.0.Final

by Darran Lofthouse (Jira)

Darran Lofthouse created JBEE-239: ------------------------------------- Summary: Release JBoss / Jakarta JASPI 2.0.0.Final Key: JBEE-239 URL: https://issues.jboss.org/browse/JBEE-239 Project: JBoss Enterprise Spec APIs Issue Type: Task Components: jboss-jaspi-api Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: jboss-jakarta-jaspi-api_spec-2.0.0.Final -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBEE-238) Add license file to JASPI Jar

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/JBEE-238?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse resolved JBEE-238. ----------------------------------- Resolution: Done > Add license file to JASPI Jar > ----------------------------- > > Key: JBEE-238 > URL: https://issues.jboss.org/browse/JBEE-238 > Project: JBoss Enterprise Spec APIs > Issue Type: Task > Components: jboss-jaspi-api > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: jboss-jakarta-jaspi-api_spec-2.0.0.Final > > -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 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 September 2019