[jboss-dev-forums] [Design of JBoss Build System] - Re: JBossAS CR1 build plan

[ALRubinger]

"pgier" wrote : Once ejb3 is mavenized it can still be deployed to the legacy repository using the jboss-deploy plugin or manually.  Then the existing build can use the artifacts.

To drive home this point, it's unfortunately more involved than that. :)  I'll try to be concise (and repeat some key points).

Problem 1:
EJB3 depends on AS components, many of which do not have their own lifecycle;we're building off snapshots.

Problem 2:
Even if the AS components had an official release, they're tied to the AS build itself.  So EJB3 depends on AS, which depends on EJB3.  That's the circular dependency.

Problem 3:
Minimal time/resources to address everything in the most clean fashion before CR1.  In tandem with TCK.

So the goals as I see it, in order of priority:
1) Resolve circular dependency issues (cannot cut proper release with status-quo)
2) TCK
3) Cleanliness

I'll map out my out-of-scope Utopian wishlist as a jump-off point for debate and cutting back until we have something manageable for CR1.

* Each AS component owner responsible for their own build
* AS Build policy dictating that artifacts must be deployed to Maven repo
* Each AS component in separate release cycle
* Reorganization of AS in SVN to something like: jbossas/components/componentName/[trunk|branches|tags]
* Creation of new AS Assembly Project to bring in all dependent components and package into distribution (The EJB3 Plugin does this currently)
* Centralized POM tracking current versions of each AS component, to be used both by AS Assembly and outside projects (ie. EJB3)

AFAICT, discussion of artifact names and embedded versions seems minute compared with the overall task of defining how we can resolve the above for CR1.

Carlo's suggestion to treat the existing AS trunk as a unified "component", adding the additional AS Assembly has a lot of merit.  This way we trim the fat of separately componentizing each module and have a well-defined version upon which EJB3 can depend.  The cleanup and reorg can then be shuffled off to post-CR1.

S,
ALR

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

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