[jboss-as7-dev] modules backed by a repo part 2

Bill Burke bburke at redhat.com
Tue Mar 5 13:54:47 EST 2013


I've finished the jboss-modules patch to allow maven artifacts as 
resource-roots and added a JBoss AS build target which creates the 
correct module.xml file entries.  Works well.

The problem I'm running into now is native libraries.  Specifically 
JBoss Web.  Currently there is 1 jboss web native artifact, which is a 
jar, that is a zip of all platform specific libraries.  This jar is 
unzipped into the module's lib/ directory.  Doesn't really fit with what 
we want to do.

Would be cool if you could point to a maven artifact directory that 
contained an exploded structure of your native binaries:

org/jboss/as/jbossweb-native/2.0.10.Final/
                                          /win-i686
                                          /win-x86_64
                                          /linux-x86_64
                                          /macosx-x86_64


But, I can't find anything anywhere that maven can download from or 
populate a maven repo with an exploded structure.  I don't know if you 
can manually create directories and files on a nexus repo either or even 
just execute HTTP PUTs on a nexus repo.

So, what I'm going to do for now, is add a <native-artifact> option to 
JBoss-Modules that will unjar the artifact in the artifact's local repo 
directory if it hasn't been already.  Creating a shared local read-only 
repo will require a manual step for native libs unless I can figure 
something else out :(

On 3/1/2013 5:14 PM, David M. Lloyd wrote:
> On 03/01/2013 03:20 PM, Bill Burke wrote:
>> 1) Anybody know why jboss-seam-int-jbossas is copied directly into a
>> bundle/ directory of its module?  And doesn't use <module-def> in the
>> build script?
>>
>> 2) After you'd convert all modules to reference a maven artifact,
>> there's still the bundles and client jars left.  28.7M.  OSGi isn't
>> enabled by default right?  So these bundles aren't needed unless you're
>> doing OSGi?
>>
>> 3) How could our OSGi bundles be supported in this maven repo model?  Is
>> it JBoss OSGi that locates and loads the bundles?
>
> I'll be honest, our provided OSGi bundle set is a mess; they should just
> be plain modules.  It's one thing I want to work on with Thomas for 8 or
> 9...
>

-- 
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com


More information about the jboss-as7-dev mailing list