apache.nifi:nifi-nar-bundles:pom:0.6.0-SNAPSHOT and
> > 'parent.relativePath' points at wrong local POM @ line 19, column 13 ->
> > [Help 2]
> >
> >
> > Any quick advice before I start diggin in?
> >
> > Greetings Uwe
> >
> >
> > > Gese
r-bundles:pom:0.6.0-SNAPSHOT and
> 'parent.relativePath' points at wrong local POM @ line 19, column 13 ->
> [Help 2]
>
>
> Any quick advice before I start diggin in?
>
> Greetings Uwe
>
>
> > Gesendet: Montag, 21. März 2016 um 18:25 Uhr
> > V
dev@nifi.apache.org
> Betreff: Re: Aw: Re: Re: Re: Re: Processor additional documentation
>
> For that pull request I added POMs at each level, you can run mvn install
> from the top bundle and it will build the NAR under the
> nifi-datamelt-nar/target folder.
>
> You ca
t;
> Anything I have to specifically do with maven? And is there documentation
> available?
>
> greetings and thanks for help.
>
> Uwe
>
> > Gesendet: Montag, 21. März 2016 um 14:04 Uhr
> > Von: "Matt Burgess"
> > An: dev@nifi.apache.org
> > Betref
do with maven? And is there documentation
> available?
>
> greetings and thanks for help.
>
> Uwe
>
>> Gesendet: Montag, 21. März 2016 um 14:04 Uhr
>> Von: "Matt Burgess"
>> An: dev@nifi.apache.org
>> Betreff: Re: Re: Re: Re: Processor additiona
available?
greetings and thanks for help.
Uwe
> Gesendet: Montag, 21. März 2016 um 14:04 Uhr
> Von: "Matt Burgess"
> An: dev@nifi.apache.org
> Betreff: Re: Re: Re: Re: Processor additional documentation
>
> Uwe,
>
> The additional details piece appears
oh. github is down...
> Gesendet: Montag, 21. März 2016 um 14:04 Uhr
> Von: "Matt Burgess"
> An: dev@nifi.apache.org
> Betreff: Re: Re: Re: Re: Processor additional documentation
>
> Uwe,
>
> The additional details piece appears to be a result of your &quo
head.
> >
> > Rgds,
> >
> > Uwe
> >
> >> Gesendet: Freitag, 18. März 2016 um 19:14 Uhr
> >> Von: "dan bress"
> >> An: dev@nifi.apache.org
> >> Betreff: Re: Re: Re: Processor additional documentation
> >>
> &g
with a clear head.
>
> Rgds,
>
> Uwe
>
>> Gesendet: Freitag, 18. März 2016 um 19:14 Uhr
>> Von: "dan bress"
>> An: dev@nifi.apache.org
>> Betreff: Re: Re: Re: Processor additional documentation
>>
>> Uwe,
>>No, the index.htm
um 16:18 Uhr
> Von: "Bryan Bende"
> An: dev@nifi.apache.org
> Betreff: Re: Processor additional documentation
> Hi Uwe,
>
> Do you have the additionalDetails.html file in your processors jar project,
> under src/main/resources?
>
> Similar to this:
>
> htt
Uwe,
When I asked this question a few days ago. What you're doing is rolling
your whole processor into a NAR instead of JARing it first, then rolling
the JAR into a NAR. This doesn't work and still won't work when they fix
it (not just for the reason of /additional//Details.html/ because
ther
19:03 Uhr
> Von: "dan bress"
> An: dev@nifi.apache.org
> Betreff: Re: Re: Processor additional documentation
>
> Uwe,
>No its not a problem to have both index.html and additionalDetails.html
> The NiFi framework generates nearly all of the documentation for
: "dan bress"
> > An: dev@nifi.apache.org
> > Betreff: Re: Re: Processor additional documentation
> >
> > Uwe,
> >No its not a problem to have both index.html and
> additionalDetails.html
> > The NiFi framework generates nearly all
16:18 Uhr
Von: "Bryan Bende"
An: dev@nifi.apache.org
Betreff: Re: Processor additional documentation
Hi Uwe,
Do you have the additionalDetails.html file in your processors jar project,
under src/main/resources?
Similar to this:
https://github.com/apache/nifi/tree/master/nifi-nar-bundles
Hi Uwe,
Do you have the additionalDetails.html file in your processors jar project,
under src/main/resources?
Similar to this:
https://github.com/apache/nifi/tree/master/nifi-nar-bundles/nifi-solr-bundle/nifi-solr-processors/src/main/resources
The expected project structure is described here:
ht
ress"
> An: dev@nifi.apache.org
> Betreff: Re: Re: Re: Processor additional documentation
>
> Uwe,
>No, the index.html is generated for you. additionalDetails.html is your
> responsibility only if you feel like the generated index.html doesn't fully
> describe y
16 matches
Mail list logo