helix-ui is written in node.js and it does not publish any Jar or other
artifact along with our release, that is why we did not find this issue in
our release process.  Our release script did not bump the version in
helix-ui submodule pom file.  Let us fix the script and regenerate our
release candidate.

Lei

On Tue, Jan 30, 2018 at 9:51 PM kishore g <[email protected]> wrote:

> How come we did not catch this as part of the release? Lei, is helix-front
> included as part of release profile in pom.
>
> On Tue, Jan 30, 2018 at 9:01 PM, Bo Liu <[email protected]> wrote:
>
>> looks like we just need to change the parent version from 0.6.10-SNAPSHOT
>> to 0.8.0.
>>
>> On Tue, Jan 30, 2018 at 8:50 PM, Bo Liu <[email protected]> wrote:
>>
>>> Hi There,
>>>
>>> I am trying to build helix-front UI by following the instructions on
>>> https://helix.apache.org/0.8.0-docs/tutorial_ui.html
>>> However, I got the following error when running the "../build" step. Any
>>> input?
>>>
>>> [INFO] Scanning for projects...
>>>
>>> [ERROR] The build could not read 1 project -> [Help 1]
>>>
>>> [ERROR]
>>>
>>> [ERROR]   The project org.apache.helix:helix-front:0.6.10-SNAPSHOT
>>> (/tmp/helix/helix-front/pom.xml) has 1 error
>>>
>>> [ERROR]     Non-resolvable parent POM: Could not find artifact
>>> org.apache.helix:helix:pom:0.6.10-SNAPSHOT and 'parent.relativePath' points
>>> at wrong local POM @ line 21, column 11 -> [Help 2]
>>>
>>> [ERROR]
>>>
>>> [ERROR] To see the full stack trace of the errors, re-run Maven with the
>>> -e switch.
>>>
>>> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>>>
>>> [ERROR]
>>>
>>> [ERROR] For more information about the errors and possible solutions,
>>> please read the following articles:
>>>
>>> [ERROR] [Help 1]
>>> http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
>>>
>>> [ERROR] [Help 2]
>>> http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException
>>>
>>>
>>>
>>>
>>> --
>>> Best regards,
>>> Bo
>>>
>>>
>>
>>
>> --
>> Best regards,
>> Bo
>>
>>
>

Reply via email to