The only thing I don't like is the module name
'jboss-as-product-config', because it has no 1:1 relationship with a
'product'. It is more a 'distro' config, but I don't like that either.
How about 'jboss-as-version-config'?
For Fedora we would assume a different identity as well, unless we can
get the full AS functionality up and running. This I doubt, because
there are two requirements which contradict AS requirements:
- must use only latest version (so no Hibernate 3 for example)
- must use only FOSS (vs should use only FOSS)
Carlo
PS. Personally I think we should have the Hibernate 3 option in Fedora,
but that would entail a different packaging strategy.
On 12/13/2011 12:19 AM, Paul Gier wrote:
I started working on a way to modularize the product name and version
in
the startup/shutdown logs of AS7 [1][2]. There is a new module called
"product" which contains the product name and version. However this
approach doesn't seem good to me because the "host-controller",
"process-controller", and "server" modules all now have dependencies
on
this new module.
Ideally, I want to set this up so that there is sort of a placeholder
product name/version used during the build or these modules, but then
this can be overridden by the product module later in the build. Anyone
have suggestions about how to do this?
Thanks!
[
1]https://github.com/pgier/jboss-as/commits/AS7-1807
[
2]https://issues.jboss.org/browse/AS7-1807
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev