June 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-9008) WildFly Servlet should provide license data

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-9008?page=com.atlassian.jira.plugin.... ] Brian Stansberry moved WFCORE-3022 to WFLY-9008: ------------------------------------------------ Project: WildFly (was: WildFly Core) Key: WFLY-9008 (was: WFCORE-3022) Component/s: Server (was: Server) Fix Version/s: 11.0.0.Beta1 (was: 3.0.0.Beta28) > WildFly Servlet should provide license data > ------------------------------------------- > > Key: WFLY-9008 > URL: https://issues.jboss.org/browse/WFLY-9008 > Project: WildFly > Issue Type: Task > Components: Server > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 11.0.0.Beta1 > > > The servlet-feature-pack should provide license data in the same manner the "full" feature-pack in does. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3022) WildFly Servlet should provide license data

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-3022: ---------------------------------------- Summary: WildFly Servlet should provide license data Key: WFCORE-3022 URL: https://issues.jboss.org/browse/WFCORE-3022 Project: WildFly Core Issue Type: Task Components: Server Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 3.0.0.Beta28 The core-feature-pack should provide license data in the same manner the "full" feature-pack in WildFly does. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3021) WildFly Core should provide license data

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-3021: ---------------------------------------- Summary: WildFly Core should provide license data Key: WFCORE-3021 URL: https://issues.jboss.org/browse/WFCORE-3021 Project: WildFly Core Issue Type: Task Components: Server Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 3.0.0.Beta28 The core-feature-pack should provide license data in the same manner the "full" feature-pack in WildFly does. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9007) The bin/product.conf and the org.jboss.as.product:<xxx> module should come in via an FP

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-9007?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-9007: ----------------------------------- Fix Version/s: 12.0.0.Alpha1 > The bin/product.conf and the org.jboss.as.product:<xxx> module should come in via an FP > --------------------------------------------------------------------------------------- > > Key: WFLY-9007 > URL: https://issues.jboss.org/browse/WFLY-9007 > Project: WildFly > Issue Type: Task > Components: Server > Reporter: Brian Stansberry > Fix For: 12.0.0.Alpha1 > > > For WFLY-4692 we moved the "product" stuff out of [servlet-]feature-pack and into [servlet-]dist. But this means it doesn't end up in the skinny dist produced by the "[servlet-]build" module. Plus it makes the "dist" a kind of FP of its own. > The stuff in [servlet-]dist/src/distribution should be its own FP. That one *perhaps* depends on the related normal feature-pack. Then build and dist use the new FP in addition to or instead of the regular feature-pack. > So, the regular feature-pack is independently usable, in other dists, but our offiical build/dist, which has our official product module, picks up the new FP. > Whether the new "product" FP depends on the regular feature-pack depends on how we want to use it; i.e. can this bin/product.conf and module be used in some other flavor of dist besides the official one. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3019) The bin/product.conf and the org.jboss.as.product:wildfly-core module should come in via an FP

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3019?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-3019: ------------------------------------- Fix Version/s: 4.0.0.Alpha1 > The bin/product.conf and the org.jboss.as.product:wildfly-core module should come in via an FP > ---------------------------------------------------------------------------------------------- > > Key: WFCORE-3019 > URL: https://issues.jboss.org/browse/WFCORE-3019 > Project: WildFly Core > Issue Type: Task > Components: Server > Reporter: Brian Stansberry > Fix For: 4.0.0.Alpha1 > > > For WFLY-4692 we moved the "product" stuff out of core-feature-pack and into dist. But this means it doesn't end up in the skinny dist produced by the "build" module. Plus it makes the "dist" a kind of FP of its own. > The stuff in dist/src/distribution should be its own FP. That one *perhaps* depends on core-feature-pack. Then build and dist use the new FP in addition to or instead of core-feature-pack. > So, core-feature-pack is independently usable, in other dists, but our offiical build/dist, which has our official product module, picks up the new FP. > Whether the new "product" FP depends on core-feature-pack depends on how we want to use it; i.e. can this bin/product.conf and module be used in some other flavor of dist. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3020) The bin/product.conf and the org.jboss.as.product:<xxx> module should come in via an FP

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3020?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-3020: ------------------------------------- Description: For WFLY-4692 we moved the "product" stuff out of [servlet-]feature-pack and into [servlet-]dist. But this means it doesn't end up in the skinny dist produced by the "[servlet-]build" module. Plus it makes the "dist" a kind of FP of its own. The stuff in [servlet-]dist/src/distribution should be its own FP. That one *perhaps* depends on the related normal feature-pack. Then build and dist use the new FP in addition to or instead of the regular feature-pack. So, the regular feature-pack is independently usable, in other dists, but our offiical build/dist, which has our official product module, picks up the new FP. Whether the new "product" FP depends on the regular feature-pack depends on how we want to use it; i.e. can this bin/product.conf and module be used in some other flavor of dist besides the official one. was: For WFLY-4692 we moved the "product" stuff out of core-feature-pack and into dist. But this means it doesn't end up in the skinny dist produced by the "build" module. Plus it makes the "dist" a kind of FP of its own. The stuff in dist/src/distribution should be its own FP. That one *perhaps* depends on core-feature-pack. Then build and dist use the new FP in addition to or instead of core-feature-pack. So, core-feature-pack is independently usable, in other dists, but our offiical build/dist, which has our official product module, picks up the new FP. Whether the new "product" FP depends on core-feature-pack depends on how we want to use it; i.e. can this bin/product.conf and module be used in some other flavor of dist. > The bin/product.conf and the org.jboss.as.product:<xxx> module should come in via an FP > --------------------------------------------------------------------------------------- > > Key: WFCORE-3020 > URL: https://issues.jboss.org/browse/WFCORE-3020 > Project: WildFly Core > Issue Type: Task > Components: Server > Reporter: Brian Stansberry > > For WFLY-4692 we moved the "product" stuff out of [servlet-]feature-pack and into [servlet-]dist. But this means it doesn't end up in the skinny dist produced by the "[servlet-]build" module. Plus it makes the "dist" a kind of FP of its own. > The stuff in [servlet-]dist/src/distribution should be its own FP. That one *perhaps* depends on the related normal feature-pack. Then build and dist use the new FP in addition to or instead of the regular feature-pack. > So, the regular feature-pack is independently usable, in other dists, but our offiical build/dist, which has our official product module, picks up the new FP. > Whether the new "product" FP depends on the regular feature-pack depends on how we want to use it; i.e. can this bin/product.conf and module be used in some other flavor of dist besides the official one. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9007) The bin/product.conf and the org.jboss.as.product:<xxx> module should come in via an FP

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-9007?page=com.atlassian.jira.plugin.... ] Brian Stansberry moved WFCORE-3020 to WFLY-9007: ------------------------------------------------ Project: WildFly (was: WildFly Core) Key: WFLY-9007 (was: WFCORE-3020) Component/s: Server (was: Server) > The bin/product.conf and the org.jboss.as.product:<xxx> module should come in via an FP > --------------------------------------------------------------------------------------- > > Key: WFLY-9007 > URL: https://issues.jboss.org/browse/WFLY-9007 > Project: WildFly > Issue Type: Task > Components: Server > Reporter: Brian Stansberry > > For WFLY-4692 we moved the "product" stuff out of [servlet-]feature-pack and into [servlet-]dist. But this means it doesn't end up in the skinny dist produced by the "[servlet-]build" module. Plus it makes the "dist" a kind of FP of its own. > The stuff in [servlet-]dist/src/distribution should be its own FP. That one *perhaps* depends on the related normal feature-pack. Then build and dist use the new FP in addition to or instead of the regular feature-pack. > So, the regular feature-pack is independently usable, in other dists, but our offiical build/dist, which has our official product module, picks up the new FP. > Whether the new "product" FP depends on the regular feature-pack depends on how we want to use it; i.e. can this bin/product.conf and module be used in some other flavor of dist besides the official one. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3019) The bin/product.conf and the org.jboss.as.product:wildfly-core module should come in via an FP

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-3019: ---------------------------------------- Summary: The bin/product.conf and the org.jboss.as.product:wildfly-core module should come in via an FP Key: WFCORE-3019 URL: https://issues.jboss.org/browse/WFCORE-3019 Project: WildFly Core Issue Type: Task Components: Server Reporter: Brian Stansberry For WFLY-4692 we moved the "product" stuff out of core-feature-pack and into dist. But this means it doesn't end up in the skinny dist produced by the "build" module. Plus it makes the "dist" a kind of FP of its own. The stuff in dist/src/distribution should be its own FP. That one *perhaps* depends on core-feature-pack. Then build and dist use the new FP in addition to or instead of core-feature-pack. So, core-feature-pack is independently usable, in other dists, but our offiical build/dist, which has our official product module, picks up the new FP. Whether the new "product" FP depends on core-feature-pack depends on how we want to use it; i.e. can this bin/product.conf and module be used in some other flavor of dist. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3020) The bin/product.conf and the org.jboss.as.product:<xxx> module should come in via an FP

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-3020: ---------------------------------------- Summary: The bin/product.conf and the org.jboss.as.product:<xxx> module should come in via an FP Key: WFCORE-3020 URL: https://issues.jboss.org/browse/WFCORE-3020 Project: WildFly Core Issue Type: Task Components: Server Reporter: Brian Stansberry For WFLY-4692 we moved the "product" stuff out of core-feature-pack and into dist. But this means it doesn't end up in the skinny dist produced by the "build" module. Plus it makes the "dist" a kind of FP of its own. The stuff in dist/src/distribution should be its own FP. That one *perhaps* depends on core-feature-pack. Then build and dist use the new FP in addition to or instead of core-feature-pack. So, core-feature-pack is independently usable, in other dists, but our offiical build/dist, which has our official product module, picks up the new FP. Whether the new "product" FP depends on core-feature-pack depends on how we want to use it; i.e. can this bin/product.conf and module be used in some other flavor of dist. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3018) Upgrade XNIO to 3.5.0.CR2

by David Lloyd (JIRA)

David Lloyd created WFCORE-3018: ----------------------------------- Summary: Upgrade XNIO to 3.5.0.CR2 Key: WFCORE-3018 URL: https://issues.jboss.org/browse/WFCORE-3018 Project: WildFly Core Issue Type: Component Upgrade Reporter: David Lloyd Assignee: David Lloyd Fix For: 3.0.0.Beta28 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 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 June 2017