I think we should go more in lines of what Ceylon guys are doing with jboss
modules.
they have created ceylon module repository (herd)
http://modules.ceylon-lang.org/
that hosts jboss modules zipped with .car extension.
ceylon can than load this modules for compile & runtime when needed.
That is much more than what we need but it would still be nice to explore.
Easy thing to do would be to upload our modules to maven repo under
different type, (i.e. module)
this way we could reuse maven repositories as we know them.
But to make this work we would need to write maven plugin that will know
what to do with module once it was downloaded.
--
tomaz
On Wed, Feb 27, 2013 at 3:45 PM, Bill Burke <bburke(a)redhat.com> wrote:
On 2/26/2013 4:23 PM, David M. Lloyd wrote:
> On 02/26/2013 03:19 PM, Fernando Nasser wrote:
>> I probably should mention my motivations...
>>
>> The future generation of RPMs will install the JAR files in a maven
layout, so we just need to point the modules.xml to that location.
>> No more symlinks!
>
> It will be just in time to be obsolete again. TBH I don't think this is
> a smart move at all; Maven isn't the end state for Java build, and it
> makes zero sense for Java distribution other than development/test time.
>
Can you please share with us exactly how using a maven repo makes no
sense? I keep waiting to hear your legendary insight, but instead I'm
just getting a bunch of unsubstantiated claims and some nonsense that
maven repos aren't going to exist in the future...Myself and others have
given some pretty compelling use cases. It would be nice to hear a
counter-argument so we can have a real discussion over this instead of
just excepting your word as gospel.
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev