It might be more reliable to locally cache the maven resources
(otherwise maven becomes your single point of failure). I wouldn't want
to see an entire cluster halt, just because maven crashed.
Its also not weird to boot/deploy from a version control system either.
Although, the weird thing is when you make direct changes to the cached
application jars, instead of through maven or version control. That
should be avoided but it might not be bad for debugging (drop in a quick
debug jar and later replace with production bits from maven/source
control).
On Tue, 2010-04-06 at 11:14 +0200, Heiko Braun wrote:
it's not weird at all. That's where a few maven repository
managers make the real money:
deployment based on declarative dependency sets.
Iirc think jfrog is one of them.
/heiko
On Apr 1, 2010, at 11:19 PM, Bill Burke wrote:
> instead of the way our JBoss AS distribution is structure now, why not
> introduce the idea of maven-based booting and deployment?
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development