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

[wolfc]

"pgier" wrote : "scott.stark at jboss.org" wrote : 
  |   | 3. How is ejb3/jbossas going to be built with ejb3 as a separate project, that depends on jbossas artifacts. Logically jbossas/ejb3 are a collection of dependent projects. How this translates into a build procedure from tagged codebases is what needs to be defined for CR1. We won't have jbossas completely mavenized by that point, so how a reproducible build results is the question.
  |   | 
  |   | 4. Related to 3, do we need to restructure the jbossas project, including breaking it up into separate svn projects to support the creation of jbossas artifacts and the jbossas release assembly.
  |   | 
  | 
  | 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.
This is not the problem, the problem is the circular dependency.
"pgier" wrote : Maybe Andrew can provide some input on this since he is working on the EJB3 mavenization now.
Alternative strategy: let's demote jbossas/trunk to being a component. We remove jbossas/trunk/ejb3 and build & tag it as CR1. Now the repository contains all jboss-as-components at CR1. EJB 3 builds & tags as CR1, repository has jboss-ejb3-components. Then we take a new project with whatever name we come up with. Which is an assembly of jboss-as-components, jboss-ejb3-plugin, jboss-ws-plugin etc with a complete integration test suite. That new project will be the JBoss AS community edition. (Then EAP is either another project like this or another version of the same project. SOA-P will be another one (either sucking in EAP or AS-Community).)
I think we tackle 3 & 4 with 1 stone then (shouldn't there be a bird in there somewhere).

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

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