[
https://issues.apache.org/jira/browse/APEXCORE-401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15221835#comment-15221835
]
ASF GitHub Bot commented on APEXCORE-401:
-----------------------------------------
Github user tweise commented on the pull request:
https://github.com/apache/incubator-apex-core/pull/290#issuecomment-204435522
I don't see the need for separate project.
Why not publish it to Maven, it is a central location?
On Fri, Apr 1, 2016 at 8:16 AM, Vlad Rozov <[email protected]> wrote:
> Is it necessary to have a separate artifactId for codestyle and publish it
> to apache maven? Can the same goal be achieved by uploading codestyle
> definition file to a central location? For item 1, should checkstyle
module
> be moved into a separate project?
>
> —
> You are receiving this because you commented.
> Reply to this email directly or view it on GitHub
>
<https://github.com/apache/incubator-apex-core/pull/290#issuecomment-204434631>
>
> Create a separate artifact for checkstyle and other common configurations
> -------------------------------------------------------------------------
>
> Key: APEXCORE-401
> URL: https://issues.apache.org/jira/browse/APEXCORE-401
> Project: Apache Apex Core
> Issue Type: Improvement
> Reporter: Chandni Singh
> Assignee: Chandni Singh
>
> As of now, Apex Core and Apex Malhar have same checkstyle rules. These rules
> are present in a file called apex_checks.xml. There are separate copies of
> these present in both the repositories. Any change to the configuration has
> to be made manually at multiple places.
> We can improve this by creating another artifact which includes such common
> configuration and Apex Malhar can reference it directly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
