On Wed, Jan 10, 2018 at 12:26 AM, Sanne Grinovero <sanne@hibernate.org> wrote:

Hi all,

I'm trying to learn how to make proper use of the
`wildfly-feature-pack-build-maven-plugin` to replace our usage of the
assembly plugin.

We extensively use the module slots, and I need to keep the
"{$module.slot}" as a build parameter.

Just out of curiosity what is the use case for this?

It looks like the Feature Pack plugin is expecting the module.xml
files to be statically committed into the same directory structure as
were they need to end up, but since the slot id needs to be part of
such path, looks like I can't use it? Should I pre-process the module
resources with the assembly plugin?

Yes, at the moment there is no way to handle this. In general in WF we just use the slot main, and we don't vary any part of a module name based on a build parameter.

I was hoping for the feature-pack-build.xml to have a way to define
modules by giving it an identifier (possibly having parameters), point
them to a template xml (optionally filtered), and not having to deal
with the copy-to paths explicitly. It seems odd to have to copy the
jar files and other resources into a matching structure, maybe this
could be automated by the plugin?

You don't have to copy the jar files, the plugin does it automatically. They are laid out the way they are at the moment because it just seemed to be the simplest way to do it at the time. We did not need another layer of indirection as generally each module has its own unique module.xml so if we used a templating approach each template would be unique anyway.

Or perhaps I should look at the whole "feature pack" way of doing
things in a different way; are we supposed to only ever use the "main"
slot in a feature pack, and allow the consumer to override/filter such
ids at provisioning time?

You can use whatever slots you want, but at the moment the assumption is that you will know what those slots are in advance.

Stuart

Thanks,
Sanne
_______________________________________________
wildfly-dev mailing list
wildfly-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev