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

[Scott M Stark]

In case your not getting build forum emails.

-------- Original Message --------
Subject: [jboss-dev-forums] [Design of JBoss Build System] - JBossAS
CR1	build plan
Date: Fri, 8 Feb 2008 12:45:38 -0500 (EST)
From: scott.stark at jboss.org <do-not-reply at jboss.com>
To: jboss-dev-forums at lists.jboss.org

On today's call we still have confusion about what will be done for the
CR1 build of jbossas, including exporting of artifacts to maven repos
for use by other projects. The main point of confusion is related to how
ejb3 is going to be built. It needs jbossas artifacts in maven repo,
jbossas needs the ejb3 artifacts for the assembly.

The issues to resolve are:
1. What are the jbossas artifacts and how are they being uploaded to a
maven repo as part of the build. One simple issue I already see is that
the names of the artifacts are changed in the existing pom.xml files.
For example in the system project, while the current build produces
jboss-system-client.jar and jboss-system.jar artifacts, the
system/pom.xml  defines jboss-as-system.jar.

We need to get to consistent artifact names in both builds as it affects
classpaths and configuration files, docs.

2. Getting the jbossas build to use maven artifacts. Nothing currently
validates the jbossas maven artifacts. The first step in doing this is
to replace the legacy jbossbuild repo with the maven repo as the source
for the thirdparty contents. How we do this using ivy, maven ant tasks,
etc. needs to be defined and documented, and the existing
build-thirdparty target replaced.

The next step would be to replace the existing project dependencies
(classpaths defined in tools/etc/buildmagic/modules.ent) with the same
type of maven repo references as was done for thirdparty.

At that point the build and testsuite would be based on the exportable
artifacts.

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.


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

Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4127926
_______________________________________________
jboss-dev-forums mailing list
jboss-dev-forums at lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-dev-forums