[
https://issues.apache.org/jira/browse/TEZ-3470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15602787#comment-15602787
]
Sreenath Somarajapuram edited comment on TEZ-3470 at 10/25/16 12:12 AM:
------------------------------------------------------------------------
bq. I ran this with a "mvn clean test". Looks like a good reason to fix the
issue of temp data not be added into target/ at some point. Mind filing a bug
for this? I think the yarn folks recently addressed as part of their UI
redesign.
- Have created https://issues.apache.org/jira/browse/TEZ-3489 for clean build.
The dependencies/temp data were not removed for decreasing the build time.
-- In YARN they don't build the UI with normal build. -Pyarn-ui must be used,
and thats taking around 2 to 3 minutes each time.
-- In Tez UI, a warm build takes around 20sec while a cold build takes near to
3.5 minutes.
bq. 3.1.0 came out in Oct 2013. I think we can change our builds to need 3.1.0
as a min dependency for master if this is blocking the conversion.
- Shall we bump the version as part of this ticket. Looks like TEZ-2560 changes
can also be reverted with that.
bq. What does frontend-maven-plugin impact apart from the build of the webapp?
- frontend-maven-plugin is used only for UI build.
bq. If not now, when would be a good time to bump to v1.1?
- As it was 9 days old wasn't sure if its safe. Considering its used only for
the UI shall I make 1.1 the default version.
bq. Additionally, is this only needed for phantomjs or will this apply to any
dependency where the version is changed?
- For normal version change its not required, old will be replaced by the new.
- We have to use -PcleanUICache, as we are not just changing the version but
the package name also. It was phantomjs, but now its phantomjs-prebuilt. So on
npm install you would have both phantomjs (from old installs) and
phantomjs-prebuilt.
Following is what the creators of phantomjs npm package have to tell about the
change.
{code}
Pre-2.0, this package was published to NPM as phantomjs. We changed the name to
phantomjs-prebuilt at the request of PhantomJS team.
{code}
was (Author: sreenath):
bq. I ran this with a "mvn clean test". Looks like a good reason to fix the
issue of temp data not be added into target/ at some point. Mind filing a bug
for this? I think the yarn folks recently addressed as part of their UI
redesign.
- Have created https://issues.apache.org/jira/browse/TEZ-for for clean build.
The dependencies/temp data were not removed for decreasing the build time.
-- In YARN they don't build the UI with normal build. -Pyarn-ui must be used,
and thats taking around 2 to 3 minutes each time.
-- In Tez UI, a warm build takes around 20sec while a cold build takes near to
3.5 minutes.
bq. 3.1.0 came out in Oct 2013. I think we can change our builds to need 3.1.0
as a min dependency for master if this is blocking the conversion.
- Shall we bump the version as part of this ticket. Looks like TEZ-2560 changes
can also be reverted with that.
bq. What does frontend-maven-plugin impact apart from the build of the webapp?
- frontend-maven-plugin is used only for UI build.
bq. If not now, when would be a good time to bump to v1.1?
- As it was 9 days old wasn't sure if its safe. Considering its used only for
the UI shall I make 1.1 the default version.
bq. Additionally, is this only needed for phantomjs or will this apply to any
dependency where the version is changed?
- For normal version change its not required, old will be replaced by the new.
- We have to use -PcleanUICache, as we are not just changing the version but
the package name also. It was phantomjs, but now its phantomjs-prebuilt. So on
npm install you would have both phantomjs (from old installs) and
phantomjs-prebuilt.
Following is what the creators of phantomjs npm package have to tell about the
change.
{code}
Pre-2.0, this package was published to NPM as phantomjs. We changed the name to
phantomjs-prebuilt at the request of PhantomJS team.
{code}
> Tez UI: Make the build work in IBM PPC
> --------------------------------------
>
> Key: TEZ-3470
> URL: https://issues.apache.org/jira/browse/TEZ-3470
> Project: Apache Tez
> Issue Type: Bug
> Affects Versions: 0.8.3
> Reporter: Sreenath Somarajapuram
> Assignee: Sreenath Somarajapuram
> Labels: TezUI
> Attachments: TEZ-3470.1.patch, TEZ-3470.2.patch, TEZ-3470.wip.1.patch
>
>
> Current versions of frontend-maven-plugin, node & npm used by the build is
> not functioning as expected in IBM PPC. Following version works, and the
> build must be changed to used the same in a PPC.
> - frontend-maven-plugin : v1.1
> - node : v5.7.0
> - npm : 3.6.0
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
