Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Message-ID: <1806550693.1127655650761.JavaMail.jira@ajax.apache.org>
Date: Sun, 25 Sep 2005 15:40:50 +0200 (CEST)
From: "Aaron Mulder (JIRA)" <dev@geronimo.apache.org>
To: dev@geronimo.apache.org
Subject: [jira] Commented: (GERONIMO-817) deploy-jsr88 module has dependency
 on openejb
In-Reply-To: <99625803.1122364038153.JavaMail.jira@ajax.apache.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

    [ http://issues.apache.org/jira/browse/GERONIMO-817?page=comments#action_12330426 ] 

Aaron Mulder commented on GERONIMO-817:
---------------------------------------

Well, this probably doesn't need to be a blocker for now.  But we do need some solution other than hardcoding.  For example, now that you've changed the Jetty and Tomcat DDs to be different again, how is a deploy tool to know what to use?

> deploy-jsr88 module has dependency on openejb
> ---------------------------------------------
>
>          Key: GERONIMO-817
>          URL: http://issues.apache.org/jira/browse/GERONIMO-817
>      Project: Geronimo
>         Type: Bug
>   Components: deployment
>     Versions: 1.0-M4, 1.0-M5
>     Reporter: David Jencks
>     Assignee: Aaron Mulder
>     Priority: Blocker
>      Fix For: 1.0-M5
>  Attachments: nobuilderdependencies
>
> Apparently in an attempt to support dconfig beans, the deploy-jsr88 module grew dependencies on several builder modules including openejb builder.  This is a totally non-extensible archtecture and prevents building geronimo and openejb in any semblance of a reasonable order.  I think that some kind of registration scheme might be plausible but the current hard-coded dependencies to specific builder implementations are not acceptable.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira