Encouraged by Bill's recent work getting the EJB3 Core from AS into the ejb3-core Module in Projects, I've done some cleanup of the POMs in there.

My goal is to get all common plugins, build configurations, and dependency versions centralized in the EJB3 Build POM, which acts as parent for the other projects. I've updated the version of the parent build to 0.12.0-SNAPSHOT, and it is now properly heading up the builds of all projects except for ejb3-core and sandbox.

End result should be ultra-slim POMs for each project, and common versions for each dependency as mandated by the parent.

I hope I haven't knocked ejb3-core too out-of-it in the process. This project had been working for Bill, but not building for me for a variety of dependency-related issues. What remains to be done here is:

1) Move all version information into the parent, if not present there already2) Get the build configuration in-line (ie. src/main/java, not src/main)3) Resolve the tests (Bill tells me this is more involved)4) Ensure the dependencies are correct / get compilation going

BTW, I'm thrilled to see us moving off the AS and taking charge of an independent release cycle. My one concern is that the dependencies we define for compilation and tests may not be the same versions placed into the various lib folders of AS and will differ for our end-users at runtime. How can we address/avoid this?

I'm thinking of changing the svn directory structure from trunk/... to .../trunk. So we can have independent release cycles for each component. The only con I see is that we don't have the facility in Jira for version per component.

The versions of components we depend upon are dictated by the AS component matrix. We can't deviate from that, but we can put a wrapper component in between.

"wolfc" wrote:I'm thinking of changing the svn directory structure from trunk/... to .../trunk. So we can have independent release cycles for each component. The only con I see is that we don't have the facility in Jira for version per component.

We could still have independent release cycles, but the component releases would be aside one another in branches/.. and tags/..

We *could* configure JIRA to view each "component" (project in SVN) as its own JIRA Project; though that could be overkill and administrative nightmare (instead of EJB3 Project with X Components, we'd have X Projects to watch over).

"wolfc" wrote:The versions of components we depend upon are dictated by the AS component matrix. We can't deviate from that, but we can put a wrapper component in between.

Link to the AS Component Matrix? Or is this simply represented by the componentrefs in build-thirdparty?