December 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-3454) The wildfly-core-dist does not produce an archive with the correct contents

by James Perkins (JIRA)

James Perkins created WFCORE-3454: ------------------------------------- Summary: The wildfly-core-dist does not produce an archive with the correct contents Key: WFCORE-3454 URL: https://issues.jboss.org/browse/WFCORE-3454 Project: WildFly Core Issue Type: Bug Reporter: James Perkins Assignee: James Perkins The {{assembly.xml}} in the {{wildfly-core-dist}} module produces a zip file with only the source contents. This results in an unusable distribution. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 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 commented on WFCORE-3019: ------------------------------------------ [~jamezp] Yeah, maybe a separate jira would be better. We release alphas frequently and if the dist is broken we should get that corrected ASAP. Does full have the same problem? If not does https://github.com/wildfly/wildfly/pull/10689 introduce that problem? > 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 > Assignee: James Perkins > Fix For: 4.0.0.Alpha5 > > > 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.5.0#75005)

8 years, 7 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 James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3019?page=com.atlassian.jira.plugi... ] James Perkins edited comment on WFCORE-3019 at 12/11/17 6:14 PM: ----------------------------------------------------------------- [~brian.stansberry] Okay will do. As of now the {{wildfly-dist-$version.zip}} only contains the {{bin/product.conf}} and the single product module. I was going to file a JIRA for that, but then found this and thought maybe we should fix it all at once. The fix for that issue is very simple and if we just want to fix that I can file a separate JIRA and do that. was (Author: jamezp): Okay will do. As of now the {{wildfly-dist-$version.zip}} only contains the {{bin/product.conf}} and the single product module. I was going to file a JIRA for that, but then found this and thought maybe we should fix it all at once. The fix for that issue is very simple and if we just want to fix that I can file a separate JIRA and do that. > 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 > Assignee: James Perkins > Fix For: 4.0.0.Alpha5 > > > 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.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7524) Add Hibernate-Spatial to WildFly Feature Pack

by Dennis Gesker (JIRA)

[ https://issues.jboss.org/browse/WFLY-7524?page=com.atlassian.jira.plugin.... ] Dennis Gesker commented on WFLY-7524: ------------------------------------- Thanks for taking a look at this ticket [Sanne Grinovero|https://issues.jboss.org/secure/ViewProfile.jspa?name=sannegrin...] I'm not sure I've done a project in the past couple years that didn't have some kind of spatial element to it so I'd love to see the dependencies in WildFly. But, it would be great if spatial was included in the feature pack even if it results in a larger war/ear -- so even it not included with the server. But, you are right and I can see where some might cringe at those parts/extras that are part of the Hibernate project being included by default. What typically been done in the past when a product that provides a standards compliant capability (JPA in this case) has a useful functionality beyond the standard? Or, put another way, I'll gladly go with the flow based on how this "kind" of thing has been resolved in the past. So my 1, 2, 3 of the options you presented would be: * We could simply include all missing dependencies into WildFly * We can enhance the feature packs which we release with each release of Hibernate ORM * We could have the hibernate-orm module depend on an optional "spatial extensions" module w/o including it, and publish the missing module as a drop-in feature pack to be downloaded separately I absolutely don't want to make any waves. And, I am grateful to even have attention on this item because I use these features/libs quite a bit. Thank you SO much for even considering WFLY-7523 and WFLY-7524 Dennis > Add Hibernate-Spatial to WildFly Feature Pack > --------------------------------------------- > > Key: WFLY-7524 > URL: https://issues.jboss.org/browse/WFLY-7524 > Project: WildFly > Issue Type: Feature Request > Affects Versions: 11.0.0.Final, 12.0.0.Alpha1 > Environment: Linux / OpenJDK 8 / Wildfly 11.0.0.Final > Reporter: Dennis Gesker > Assignee: Jason Greene > Labels: wildfly-feature-pack > > If possible kindly add jars need to make use of hibernate-spatial to WildFly-Feature-Pack > org.hibernate:hibernate-spatial > org.geolatte:geolatte-geom > com.vividsolutions:jts-parent > BTW, thank you for this package. It saves a HUGE amount of time with dependencies. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 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 James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3019?page=com.atlassian.jira.plugi... ] James Perkins commented on WFCORE-3019: --------------------------------------- Okay will do. As of now the {{wildfly-dist-$version.zip}} only contains the {{bin/product.conf}} and the single product module. I was going to file a JIRA for that, but then found this and thought maybe we should fix it all at once. The fix for that issue is very simple and if we just want to fix that I can file a separate JIRA and do that. > 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 > Assignee: James Perkins > Fix For: 4.0.0.Alpha5 > > > 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.5.0#75005)

8 years, 7 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 commented on WFCORE-3019: ------------------------------------------ [~jamezp] It's probably good to check with [~aloubyansky] on this one (and WFLY-9007). What I describe here sounds like it would be more in line with how the new provisioning would want things done but he may some thoughts or could at least benefit as an FYI. > 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 > Assignee: James Perkins > Fix For: 4.0.0.Alpha5 > > > 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.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9436) Test suite misses any sort of smoke test for JSR-77 management bean availability

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-9436?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-9436: ----------------------------------- Issue Type: Enhancement (was: Bug) > Test suite misses any sort of smoke test for JSR-77 management bean availability > -------------------------------------------------------------------------------- > > Key: WFLY-9436 > URL: https://issues.jboss.org/browse/WFLY-9436 > Project: WildFly > Issue Type: Enhancement > Components: Test Suite > Reporter: Michal Jurc > Assignee: Jozef Cibik > Fix For: 12.0.0.Alpha1 > > > There is no test case present to check for availability of JSR-77 MEJBs. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 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 James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3019?page=com.atlassian.jira.plugi... ] James Perkins commented on WFCORE-3019: --------------------------------------- I realize this probably isn't urgent, but I noticed today the dist doesn't produce the correct contents in it's zip. While that itself is a simple fix, it seems reasonable just to fix this all at once. > 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 > Assignee: James Perkins > Fix For: 4.0.0.Alpha5 > > > 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.5.0#75005)

8 years, 7 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 James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3019?page=com.atlassian.jira.plugi... ] James Perkins reassigned WFCORE-3019: ------------------------------------- Assignee: James Perkins > 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 > Assignee: James Perkins > Fix For: 4.0.0.Alpha5 > > > 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.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7524) Add Hibernate-Spatial to WildFly Feature Pack

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/WFLY-7524?page=com.atlassian.jira.plugin.... ] Sanne Grinovero commented on WFLY-7524: --------------------------------------- Hi [~gesker], I would be happy to help, but could you clarify what it is you're after? I see various options: * We could have the {{hibernate-orm}} module depend on an optional "spatial extensions" module w/o including it, and publish the missing module as a drop-in feature pack to be downloaded separately. * We could simply include all missing dependencies into WildFly (although I suspect some people might not like that) * We can enhance the feature packs which we release with each release of Hibernate ORM. See also: https://docs.jboss.org/hibernate/orm/5.2/topical/html_single/wildfly/Wild... > Add Hibernate-Spatial to WildFly Feature Pack > --------------------------------------------- > > Key: WFLY-7524 > URL: https://issues.jboss.org/browse/WFLY-7524 > Project: WildFly > Issue Type: Feature Request > Affects Versions: 11.0.0.Final, 12.0.0.Alpha1 > Environment: Linux / OpenJDK 8 / Wildfly 11.0.0.Final > Reporter: Dennis Gesker > Assignee: Jason Greene > Labels: wildfly-feature-pack > > If possible kindly add jars need to make use of hibernate-spatial to WildFly-Feature-Pack > org.hibernate:hibernate-spatial > org.geolatte:geolatte-geom > com.vividsolutions:jts-parent > BTW, thank you for this package. It saves a HUGE amount of time with dependencies. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

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