Provided this gets into the next product version, the impact on the
sustaining pipeline seems to be none or minimal. I don't see the dist/
or build/ modules being used in any special way, we rely on the
testsuite to know by itself where to find the installation. We would
just need to spread the word, so people know where those modules went.
(And the new structure would be more sensible.)
Tomas
On Mon, 2024-12-02 at 12:06 -0600, Brian Stansberry wrote:
I'm curious what impact it would have on people if the build and
dist
modules were moved under galleon-pack and the ee-build and ee-dist
modules were moved under ee-galleon-pack.
Internal to the WF build any other modules that look for those
locations should be relying on a maven property, so in theory it
could be easy to tweak that property. But there might be a problem
with other automation external to the build (e.g. github actions)
that make assumptions about the location of those modules.
I'm asking this as part of some brainstorming about how to organize
the code base to better reflect the different variants of WF we
produce. Currently the build and dist for WFP are located under the
same dir 'preview' as the bits that produce the WFP feature pack and
channel. Unlike the various modules that produce java artifacts (e.g.
subsystems), the dist modules are tightly bound to the FP that
produces them, so grouping them makes some sense.
NBD; I'm just brainstorming.
--
Brian Stansberry
Principal Architect, Red Hat JBoss EAP
WildFly Project Lead
He/Him/His
_______________________________________________
wildfly-dev mailing list -- wildfly-dev(a)lists.jboss.org
To unsubscribe send an email to wildfly-dev-leave(a)lists.jboss.org
Privacy Statement:
https://www.redhat.com/en/about/privacy-policy
List Archives:
https://lists.jboss.org/archives/list/wildfly-dev@lists.jboss.org/message...