You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Clint Morgan (JIRA)" <ji...@apache.org> on 2008/02/08 18:14:08 UTC
[jira] Created: (HBASE-429) hbase-site.xml is in the hbase jar
hbase-site.xml is in the hbase jar
----------------------------------
Key: HBASE-429
URL: https://issues.apache.org/jira/browse/HBASE-429
Project: Hadoop HBase
Issue Type: Bug
Components: build
Affects Versions: 0.2.0
Reporter: Clint Morgan
Priority: Trivial
Can we get the hbase-site.xml out of there. Seems it should not be there.
In particular this causes a problem with maven, as we have little control over classpath ordering, so our hbase-site.xml is behind the hbase jar.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HBASE-429) hbase-site.xml is in the hbase jar
Posted by "stack (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack updated HBASE-429:
------------------------
Attachment: 429.patch
Remove adding hbase-default.xml to jar
> hbase-site.xml is in the hbase jar
> ----------------------------------
>
> Key: HBASE-429
> URL: https://issues.apache.org/jira/browse/HBASE-429
> Project: Hadoop HBase
> Issue Type: Bug
> Components: build
> Affects Versions: 0.2.0
> Reporter: Clint Morgan
> Priority: Trivial
> Attachments: 429.patch
>
>
> Can we get the hbase-site.xml out of there. Seems it should not be there.
> In particular this causes a problem with maven, as we have little control over classpath ordering, so our hbase-site.xml is behind the hbase jar.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HBASE-429) hbase-site.xml is in the hbase jar
Posted by "stack (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12567134#action_12567134 ]
stack commented on HBASE-429:
-----------------------------
Clint, do you mean hbase-default.xml? (See the patch. In build.xml we only add hbase-default.xml to jar).
> hbase-site.xml is in the hbase jar
> ----------------------------------
>
> Key: HBASE-429
> URL: https://issues.apache.org/jira/browse/HBASE-429
> Project: Hadoop HBase
> Issue Type: Bug
> Components: build
> Affects Versions: 0.2.0
> Reporter: Clint Morgan
> Priority: Trivial
> Attachments: 429.patch
>
>
> Can we get the hbase-site.xml out of there. Seems it should not be there.
> In particular this causes a problem with maven, as we have little control over classpath ordering, so our hbase-site.xml is behind the hbase jar.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (HBASE-429) hbase-site.xml is in the hbase jar
Posted by "Clint Morgan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Clint Morgan resolved HBASE-429.
--------------------------------
Resolution: Invalid
Sorry this was my mistake: I think somehow eclipse had put the hbase-site.xml in my build dir where it was getting picked up. Doing a clean jar, the site.xml is no longer in there.
It was the hbase-site.xml that I did not want. I think it makes sense to have the -default.xml in the jar.
> hbase-site.xml is in the hbase jar
> ----------------------------------
>
> Key: HBASE-429
> URL: https://issues.apache.org/jira/browse/HBASE-429
> Project: Hadoop HBase
> Issue Type: Bug
> Components: build
> Affects Versions: 0.2.0
> Reporter: Clint Morgan
> Priority: Trivial
> Attachments: 429.patch
>
>
> Can we get the hbase-site.xml out of there. Seems it should not be there.
> In particular this causes a problem with maven, as we have little control over classpath ordering, so our hbase-site.xml is behind the hbase jar.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.