Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Message-ID: <2685299.1185842272871.JavaMail.jira@brutus>
Date: Mon, 30 Jul 2007 17:37:52 -0700 (PDT)
From: "David Jencks (JIRA)" <jira@apache.org>
To: dev@geronimo.apache.org
Subject: [jira] Closed: (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


     [ https://issues.apache.org/jira/browse/GERONIMO-817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Jencks closed GERONIMO-817.
---------------------------------

    Resolution: Fixed

Gianni fixed this by making the deployer run off a config.xml so you can specify exactly which module jsr88 support gbeans you want.

> deploy-jsr88 module has dependency on openejb
> ---------------------------------------------
>
>                 Key: GERONIMO-817
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-817
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: deployment
>    Affects Versions: 1.0-M4, 1.0-M5
>            Reporter: David Jencks
>             Fix For: Wish List
>
>         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.
-
You can reply to this email to add a comment to the issue online.