[
https://issues.apache.org/jira/browse/APEXCORE-323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15124991#comment-15124991
]
ASF GitHub Bot commented on APEXCORE-323:
-----------------------------------------
Github user tweise commented on the pull request:
https://github.com/apache/incubator-apex-core/pull/217#issuecomment-177260582
For us, these archives are opaque, the IDEs can stick into it whatever and
I'm not in favor of extracting and checking the generated files into this
source tree. I can see how potentially it is useful to diff what was changed by
whom if the files are generated in a stable manner, but there is more work that
needs to be done. For the user, the archive should be readily available.
My suggestion is to instead move the archive files into a space excluded
from source archiving and rat check for this release. We can work on removing
them from this tree later, potentially putting them into a separate branch and
pointing the README to the github location, from where the user can download
and import. I also think that they logically don't belong here, given they
apply across versions and -core and -malhar.
> IDE styles included as binaries in source release
> -------------------------------------------------
>
> Key: APEXCORE-323
> URL: https://issues.apache.org/jira/browse/APEXCORE-323
> Project: Apache Apex Core
> Issue Type: Bug
> Affects Versions: 3.3.0
> Reporter: Pramod Immaneni
> Assignee: Pramod Immaneni
> Priority: Blocker
>
> Currently the intellij and netbeans styles are being included in the source
> as a binary archive. Change this to include non-binary files in the source
> and possible create the archive on build.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
