[
https://issues.apache.org/jira/browse/NIFI-169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14245916#comment-14245916
]
Joseph Witt commented on NIFI-169:
----------------------------------
This is really important topic so you'll find a very receptive group here. Our
most recent discussion:
http://mail-archives.apache.org/mod_mbox/incubator-nifi-dev/201412.mbox/%3CCALJK9a5X6D9T%2BPakKuUFhVX8OptcZB%3DUg9gvT3gfea0mf-mT7w%40mail.gmail.com%3E
and to some extent here:
http://mail-archives.apache.org/mod_mbox/incubator-nifi-dev/201412.mbox/%3CCALJK9a66dNTDdmmhiFG-DVkcDZTn4V7YmwGGLbW8_JeO8pA36w%40mail.gmail.com%3E
The key is figuring out a holistic process that supports effective builds,
releases, CI, and that reflects the project's different release frequencies.
The discussion thus far does suggest there is a good openness for change once
we narrow in on a good path.
> Better overall build process without using a shell script
> ---------------------------------------------------------
>
> Key: NIFI-169
> URL: https://issues.apache.org/jira/browse/NIFI-169
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Tools
> Affects Versions: 0.0.1
> Reporter: Karl Heinz Marbaise
> Fix For: 0.0.1
>
>
> I would suggest to create a better build process which takes advantage of the
> multi module capabilities of Maven and furthermore of multi threading which
> can decrease the build time dramatically.
> Apart from that currently the build process is spreaded over different areas
> which are configured differently (differen plugin versions etc.) which leads
> not in a realiable build process.
> Furthermore this would make integration into a CI environment like Apache
> area simpler.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
