[jboss-dev-forums] [Design of EJB 3.0] - Re: EJB3 Mavenization / Build System Cleanup

[ALRubinger]

"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?

S,
ALR

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

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