You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@empire-db.apache.org by "Francis De Brabandere (JIRA)" <em...@incubator.apache.org> on 2011/01/24 17:43:46 UTC
[jira] Created: (EMPIREDB-98) Split off the xml configuration
mechanim to an optional module
Split off the xml configuration mechanim to an optional module
--------------------------------------------------------------
Key: EMPIREDB-98
URL: https://issues.apache.org/jira/browse/EMPIREDB-98
Project: Empire-DB
Issue Type: Improvement
Components: Core
Affects Versions: empire-db-2.0.7-incubating
Reporter: Francis De Brabandere
Assignee: Francis De Brabandere
Priority: Minor
Fix For: empire-db-2.1.0-incubating
This is somewhat related to the removal of the log4j dependency as the config module is the only place directly linking to log4j.
Also the xml configuration is in fact optional.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (EMPIREDB-98) Split off the xml configuration
mechanism to an optional module
Posted by "Francis De Brabandere (JIRA)" <em...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/EMPIREDB-98?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Francis De Brabandere updated EMPIREDB-98:
------------------------------------------
Summary: Split off the xml configuration mechanism to an optional module (was: Split off the xml configuration mechanim to an optional module)
> Split off the xml configuration mechanism to an optional module
> ---------------------------------------------------------------
>
> Key: EMPIREDB-98
> URL: https://issues.apache.org/jira/browse/EMPIREDB-98
> Project: Empire-DB
> Issue Type: Improvement
> Components: Core
> Affects Versions: empire-db-2.0.7-incubating
> Reporter: Francis De Brabandere
> Assignee: Francis De Brabandere
> Priority: Minor
> Fix For: empire-db-2.1.0-incubating
>
>
> This is somewhat related to the removal of the log4j dependency as the config module is the only place directly linking to log4j.
> Also the xml configuration is in fact optional.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Reopened: (EMPIREDB-98) Split off the xml configuration
mechanism to an optional module
Posted by "Francis De Brabandere (JIRA)" <em...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/EMPIREDB-98?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Francis De Brabandere reopened EMPIREDB-98:
-------------------------------------------
reopen as I reverted the commit
> Split off the xml configuration mechanism to an optional module
> ---------------------------------------------------------------
>
> Key: EMPIREDB-98
> URL: https://issues.apache.org/jira/browse/EMPIREDB-98
> Project: Empire-DB
> Issue Type: Improvement
> Components: Core
> Affects Versions: empire-db-2.0.7-incubating
> Reporter: Francis De Brabandere
> Assignee: Francis De Brabandere
> Priority: Minor
> Fix For: empire-db-2.1.0-incubating
>
>
> This is somewhat related to the removal of the log4j dependency as the config module is the only place directly linking to log4j.
> Also the xml configuration is in fact optional.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (EMPIREDB-98) Split off the xml configuration
mechanism to an optional module
Posted by "Francis De Brabandere (JIRA)" <em...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/EMPIREDB-98?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Francis De Brabandere closed EMPIREDB-98.
-----------------------------------------
Resolution: Won't Fix
wrong solution for the log4j problem
> Split off the xml configuration mechanism to an optional module
> ---------------------------------------------------------------
>
> Key: EMPIREDB-98
> URL: https://issues.apache.org/jira/browse/EMPIREDB-98
> Project: Empire-DB
> Issue Type: Improvement
> Components: Core
> Affects Versions: empire-db-2.0.7-incubating
> Reporter: Francis De Brabandere
> Assignee: Francis De Brabandere
> Priority: Minor
> Fix For: empire-db-2.1.0-incubating
>
>
> This is somewhat related to the removal of the log4j dependency as the config module is the only place directly linking to log4j.
> Also the xml configuration is in fact optional.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (EMPIREDB-98) Split off the xml configuration
mechanism to an optional module
Posted by "Francis De Brabandere (JIRA)" <em...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/EMPIREDB-98?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Francis De Brabandere resolved EMPIREDB-98.
-------------------------------------------
Resolution: Fixed
All done, we might want to revisit this before making the release
> Split off the xml configuration mechanism to an optional module
> ---------------------------------------------------------------
>
> Key: EMPIREDB-98
> URL: https://issues.apache.org/jira/browse/EMPIREDB-98
> Project: Empire-DB
> Issue Type: Improvement
> Components: Core
> Affects Versions: empire-db-2.0.7-incubating
> Reporter: Francis De Brabandere
> Assignee: Francis De Brabandere
> Priority: Minor
> Fix For: empire-db-2.1.0-incubating
>
>
> This is somewhat related to the removal of the log4j dependency as the config module is the only place directly linking to log4j.
> Also the xml configuration is in fact optional.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (EMPIREDB-98) Split off the xml configuration
mechanism to an optional module
Posted by "Francis De Brabandere (JIRA)" <em...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/EMPIREDB-98?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Francis De Brabandere updated EMPIREDB-98:
------------------------------------------
Fix Version/s: (was: empire-db-2.1.0-incubating)
> Split off the xml configuration mechanism to an optional module
> ---------------------------------------------------------------
>
> Key: EMPIREDB-98
> URL: https://issues.apache.org/jira/browse/EMPIREDB-98
> Project: Empire-DB
> Issue Type: Improvement
> Components: Core
> Affects Versions: empire-db-2.0.7-incubating
> Reporter: Francis De Brabandere
> Assignee: Francis De Brabandere
> Priority: Minor
>
> This is somewhat related to the removal of the log4j dependency as the config module is the only place directly linking to log4j.
> Also the xml configuration is in fact optional.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.