[jboss-as7-dev] Automatically generate AS7 module.xml files from maven poms?

[David M. Lloyd]

The module.xml files are in build because build is what assembles the 
runtime environment.  The individual module builds are for the most part 
independent of any specific runtime environment.  It doesn't make sense 
to push the environment-specific bits into an environment-agnostic project.

On 01/03/2011 08:49 AM, Carlo de Wolf wrote:
> What I also find weird is that the module.xml is in build.
> Why not in the maven module needing that module.xml?
>
> Carlo
>
> On 12/17/2010 12:47 PM, David Bosschaert wrote:
>> Hi all,
>>
>> Today I was looking at a module.xml somewhere down
>>
>> http://github.com/jbossas/jboss-as/blob/master/build/src/main/resources/modules
>> and found out that a problem I was facing was caused by a dependency in
>> there being out of sync with the dependencies of the pom that defines
>> the original module.
>>
>> So I was thinking, since there is a 1-1 mapping between the poms and
>> modules would it make sense to automatically generate the module.xml
>> files from the poms rather then having them in git. I realize that there
>> is extra information in some cases that needs to go into the module.xml
>> file but that information could be added to the pom in some form [1].
>> Otherwise this might become a bit of a maintenance nightmare IMHO...
>>
>> Or is this already happening somewhere in a way that I'm not aware of?
>>
>> Cheers,
>>
>> David
>>
>> [1] The maven-bundle-plugin does something similar for OSGi bundles:
>> http://felix.apache.org/site/apache-felix-maven-bundle-plugin-bnd.html
>> _______________________________________________
>> jboss-as7-dev mailing list
>> jboss-as7-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev


-- 
- DML