Hi Scott,

I build and run it locally, it works fine.
But I did not do more test. I just open the ui and checked the jolt
processor.
Tommorow I'll  deploy on server and use it.
I hope it will work.
If there are any other problems about the ui, I'll post it here.

Thanks for you help.

On Wed, Nov 15, 2017 at 5:29 PM, Scott Aslan <scottyas...@gmail.com> wrote:

> Does the web app work now as well?
>
> On Wed, Nov 15, 2017 at 11:29 AM, Scott Aslan <scottyas...@gmail.com>
> wrote:
>
>> ./node/yarn/bin/yarn install?
>>
>> Sorry, I am not familiar with yarn but what I am trying to get you to do
>> is run the yarn that is installed by the frontend-maven-plugin...but if
>> adding the missing dependencies in the packge.json fixed the issue that is
>> good news!
>>
>> On Wed, Nov 15, 2017 at 11:14 AM, Lou Tian <tian.lou....@gmail.com>
>> wrote:
>>
>>> Hi Scott,
>>>
>>> The command in step 2 is not working.
>>>  bash: ./node/yarn: is a directory
>>>
>>> I manually add the missing dependencies on package.json then build nifi,
>>> it works.
>>> I think this would be a solution?
>>>
>>>
>>>
>>> On Wed, Nov 15, 2017 at 4:57 PM, Scott Aslan <scottyas...@gmail.com>
>>> wrote:
>>>
>>>> This is only a guess: It looks like a few modules the angular material
>>>> depend upon are not being downloaded.
>>>>
>>>> Try this:
>>>>
>>>>    1. cd <nifi-install-dir>/nifi/nifi-nar-bundles/nifi-framework-bund
>>>>    le/nifi-framework/nifi-web/nifi-web-ui/target/frontend-worki
>>>>    ng-directory
>>>>    2. ./node/yarn install
>>>>
>>>> Let's see if that runs successfully or not....
>>>>
>>>> On Wed, Nov 15, 2017 at 10:34 AM, Lou Tian <tian.lou....@gmail.com>
>>>> wrote:
>>>>
>>>>> Hi Scott,
>>>>>
>>>>> I changed it to yarn, the build is success.
>>>>> But when I try to run the nifi, the ui is empty (only a background, no
>>>>> other components).
>>>>> It's missing some angular peer dependencies: angular-min.js,
>>>>> angular-messges.min.js, angular-aria.min.js and angular-animate.min.js
>>>>> In Jenkins build, there are some warnings:
>>>>>
>>>>> *14:09:02* [INFO] yarn install v0.27.5*14:09:02* [ERROR] warning 
>>>>> package.json: No license field*14:09:02* [INFO] info No lockfile 
>>>>> found.*14:09:02* [ERROR] warning apache-nifi: No license field*14:09:02* 
>>>>> [INFO] [1/4] Resolving packages...*14:09:03* [INFO] [2/4] Fetching 
>>>>> packages...*14:09:05* [INFO] [3/4] Linking dependencies...*14:09:05* 
>>>>> [ERROR] warning "angular-material@1.0.8" has unmet peer dependency 
>>>>> "angular@>=1.3 <1.6".*14:09:05* [ERROR] warning "angular-material@1.0.8" 
>>>>> has unmet peer dependency "angular-animate@>=1.3 <1.6".*14:09:05* [ERROR] 
>>>>> warning "angular-material@1.0.8" has unmet peer dependency 
>>>>> "angular-aria@>=1.3 <1.6".*14:09:05* [ERROR] warning 
>>>>> "angular-material@1.0.8" has unmet peer dependency 
>>>>> "angular-messages@>=1.3 <1.6".*14:09:05* [ERROR] warning 
>>>>> "angular-material@1.0.8" has unmet peer dependency "angular-mocks@>=1.3 
>>>>> <1.6".*14:09:05* [ERROR] warning "angular-material@1.0.8" has unmet peer 
>>>>> dependency "angular-sanitize@>=1.3 <1.6".*14:09:07* [INFO] [4/4] Building 
>>>>> fresh packages...*14:09:08* [INFO] success Saved lockfile.*14:09:08* 
>>>>> [INFO] Done in 5.37s.
>>>>>
>>>>>
>>>>> Kind Regards,
>>>>> Tian
>>>>>
>>>>>
>>>>> On Wed, Nov 15, 2017 at 4:08 PM, Scott Aslan <scottyas...@gmail.com>
>>>>> wrote:
>>>>>
>>>>>> Hello,
>>>>>>
>>>>>> Yarn should only be downloading the client side dependencies at build
>>>>>> time so I think what you are proposing will work just fine. You will need
>>>>>> to update the web-ui pom to install and run yarn instead of npm but the
>>>>>> package.json is already there and should work.
>>>>>>
>>>>>> -Scott Aslan
>>>>>>
>>>>>> On Wed, Nov 15, 2017 at 5:41 AM, Lou Tian <tian.lou....@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> We are building the NIFI from the source code.
>>>>>>> In the web-ui module, can we use yarn instead of npm?
>>>>>>> Will the yarn have side effect in nifi?
>>>>>>>
>>>>>>> Little background: We need to download all of those stuff use
>>>>>>> internal artifactory without proxy.
>>>>>>> And the npm install do not support non-proxy hosts according to here(
>>>>>>> https://github.com/eirslett/frontend-maven-plugin#proxy-settings).
>>>>>>>
>>>>>>> Thanks for your reply.
>>>>>>> --
>>>>>>> Kind Regards,
>>>>>>> Tian Lou
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Kind Regards,
>>>>>
>>>>> Tian Lou
>>>>>
>>>>>
>>>>
>>>
>>>
>>> --
>>> Kind Regards,
>>>
>>> Tian Lou
>>>
>>>
>>
>


-- 
Kind Regards,

Tian Lou

Reply via email to