You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Lars Hofhansl (JIRA)" <ji...@apache.org> on 2014/03/28 07:09:15 UTC
[jira] [Commented] (HBASE-10847) 0.94: drop non-secure builds, make
security the default
[ https://issues.apache.org/jira/browse/HBASE-10847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13950425#comment-13950425 ]
Lars Hofhansl commented on HBASE-10847:
---------------------------------------
Now the question is. Do I just change pom.xml to always include the security files like this:
{code}
+ <execution>
+ <id>add-source</id>
+ <goals>
+ <goal>add-source</goal>
+ </goals>
+ <configuration>
+ <sources>
+ <source>${project.basedir}/security/src/main/java</source>
+ </sources>
+ </configuration>
+ </execution>
{code}
or do I move the security files into place under src? The former is less disruptive, the latter is cleaner.
> 0.94: drop non-secure builds, make security the default
> -------------------------------------------------------
>
> Key: HBASE-10847
> URL: https://issues.apache.org/jira/browse/HBASE-10847
> Project: HBase
> Issue Type: Bug
> Reporter: Lars Hofhansl
> Fix For: 0.94.19
>
>
> I would like to only create a single 0.94 tarball/release that contains the security code - and drop the non-secure tarballs and releases.
> Let's discuss...
--
This message was sent by Atlassian JIRA
(v6.2#6252)