[jboss-dev-forums] [Design of JBoss Build System] - Re: Improvements

[ALRubinger]

I'm looking into what it'll take to restrict a Maven deployment to snapshots that are available remotely, and with static version numbers.

"epbernard" wrote : I think the right level for a CI / Snapshot use is to define the targeted branch (say 3.3 for Hibernate Core) at the Jboss AS level. From here, the snapshot build of JBoss AS should get the latest published snapshot for that release (ideally it should get it from SVN, I don't see why we should have to manually push a snapshot out).

Interesting, presently we have no mapping between SCM location and libs.

So the logic could become:

1) I depend on http://anonsvn.jboss.org/whatever/
2) If SNAPSHOT location, checkout and build from source.  If a release, use a cached lib available in repository.jboss.org

A brief look into Maven sources reveals that this kind of thing strikes at the heart of a largely unpluggable/unmodular dependency resolution core, so this isn't as trivial as extending/enhancing a plugin.

For instance, the Maven Dependency Plugin is really a hook, it doesn't actually perform any resolution as the name implies.

S,
ALR

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4172085#4172085

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4172085