cussion
>>>>> that
>>>>>>>> took
>>>>>>>>>>>>>> place awhile back on this thread. I'm reviving this older
>>>>>>>> thread
>>>>>>>>> in
>>>>>>>&
d state
> > >>>>>>>>>>>
> > >>>>>>>>>>> The proposal is on the Apache NiFi Wiki [1], so that we
> > >> can all
> > >>>>>>>>>>> collaborate on it or leave comments
gt;>>>>>
> >>>>>>>> wrote:
> >>>>>>>>>>>>
> >>>>>>>>>>>> I am also in favor of splitting the nifi maven project
> >> up into
> >>>>>>>> sma
>>> started
>>>>>>>> work
>>>>>>>>>>>> on a nifi-commons project in which I've extracted out
>> some of
>>>>>> the
>>>>>>>> code
>>>>>>>>>>>>
for splitting
> nifi-framework
> > > > > and
> > > > > > > > > >> nifi-extensions. It also occurs to me that if
> nifi-framework
> > > > and
> > > > > > > > > >> nifi-extensions are being released independently,
> > > > n
gt; > > > > > different
> > > > > > > > >> project and therefore would be easier to code, test, build,
> > > and
> > > > > > > > >> release. However, the level of difficulty will increase for
> > > &g
> > wrote:
> > > > > > > >>>
> > > > > > > >>> I am a strong +1 on the separation and reducing the build
> > time.
> > > > > With
> > > > > > > that in mind, I think the process I brought
gt; > we
> > > > > > would now be consuming core code across multiple
> > > projects/repositories,
> > > > > so
> > > > > > there is even less guarantee the code is coming from “us”.
> > > > > > >>>
>
> > projects/repositories,
> > > > > so
> > > > > > there is even less guarantee the code is coming from “us”.
> > > > > > >>>
> > > > > > >>> [1]
> > > > > >
> >
'could' also split out the 'nifi-api'...",
> NiFi
> > > 2.0
> > > > would
> > > > >>>> also be a good time to look at more clearly defining the
> > separation
> > > > between
> > > > >>>> the UI and the framework. Where n
t; updated independently.
> > > >>>>
> > > >>>> On Thu, May 30, 2019 at 11:39 AM Jeff wrote:
> > > >>>>
> > > >>>>> In the same category of challenges that Peter pointed out, it
> might
> > > be
> > >
>>>>> It's probably always in the direction of the extensions project
> > needing
> > >>>>> something new to be added to the framework project rather than the
> > other
> > >>>>> way around, but it'll be tricky to get that workin
the extension
> project
> >>>>> will use.
> >>>>>
> >>>>> One way might be to make sure that changes to the framework project
> must be
> >>>>> in master before the extensions project can make use of them, but
> th
tension
> project
> >>>>> will use.
> >>>>>
> >>>>> One way might be to make sure that changes to the framework project
> must be
> >>>>> in master before the extensions project can make use of them, but
> th
to make sure that changes to the framework project must
>>>>> be
>>>>> in master before the extensions project can make use of them, but that
>>>>> would require a "default master" build for the framework project which
>>>>> build
t which
> > >> builds master after each commit, and deploys the build artifacts to a
> > >> persistent maven repo that the extension project builds can access. It
> > >> also makes project-spanning change-sets take longer to review and get
> > >> fully
&
; >>
> >>> One more "not awesome" would be that core changes that affect extensions
> >>> will be a little harder to test. If I make a core change that changes the
> >>> signature of an interface/etc... I'll need to do some extra work to make
&g
ll need to do some extra work to make
>>> sure I don't break extensions that use it.
>>>
>>> Still worth it, just one more thing to mention.
>>>
>>> -Original Message-
>>> From: Joe Witt
>>> Sent: Thursday, May 30, 2019 9:
break extensions that use it.
> >
> > Still worth it, just one more thing to mention.
> >
> > -Original Message-
> > From: Joe Witt
> > Sent: Thursday, May 30, 2019 9:19 AM
> > To: dev@nifi.apache.org
> > Subject: [EXT] [discuss] Splitting NiFi fram
don't break extensions that use it.
>
> Still worth it, just one more thing to mention.
>
> -Original Message-
> From: Joe Witt
> Sent: Thursday, May 30, 2019 9:19 AM
> To: dev@nifi.apache.org
> Subject: [EXT] [discuss] Splitting NiFi framework and extension repos and
&
st one more thing to mention.
>
> -Original Message-
> From: Joe Witt
> Sent: Thursday, May 30, 2019 9:19 AM
> To: dev@nifi.apache.org
> Subject: [EXT] [discuss] Splitting NiFi framework and extension repos and
> releases
>
> Team,
>
> We've discussed this a
t one more thing to mention.
-Original Message-
From: Joe Witt
Sent: Thursday, May 30, 2019 9:19 AM
To: dev@nifi.apache.org
Subject: [EXT] [discuss] Splitting NiFi framework and extension repos and
releases
Team,
We've discussed this a bit over the years in various forms but it again s
22 matches
Mail list logo
