[jira] [Commented] (ATLAS-163) New Trait UI (Tag)
[ https://issues.apache.org/jira/browse/ATLAS-163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14948898#comment-14948898 ] Vishal Kadam commented on ATLAS-163: Yes, ATLAS-163-v1.patch is latest patch. We will make sure once file is attached comment is also added for better communication. > New Trait UI (Tag) > -- > > Key: ATLAS-163 > URL: https://issues.apache.org/jira/browse/ATLAS-163 > Project: Atlas > Issue Type: Improvement >Affects Versions: 0.6-incubating >Reporter: Erik Bergenholtz >Assignee: Darshan Kumar >Priority: Critical > Labels: patch-available > Fix For: 0.6-incubating > > Attachments: ATLAS-163-v0.patch, ATLAS-163-v1.patch, TagDefinition.png > > > Atlas needs a UI to create new Tag definitions. > See attached screen-shots. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-188) Provide Ability to Add Tag to Entity
[ https://issues.apache.org/jira/browse/ATLAS-188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14948900#comment-14948900 ] Vishal Kadam commented on ATLAS-188: Patch ATLAS-188.v1.patch is added > Provide Ability to Add Tag to Entity > > > Key: ATLAS-188 > URL: https://issues.apache.org/jira/browse/ATLAS-188 > Project: Atlas > Issue Type: Task >Affects Versions: 0.6-incubating >Reporter: Erik Bergenholtz >Assignee: Sanjay Patel >Priority: Critical > Fix For: 0.6-incubating > > Attachments: ATLAS-188.v1.patch > > > Atlas UI needs to provide the ability to add a tag to an existing entity (see > attached mocks). > User Story: > - User Searches for an entity (i.e. hive_table) from the main search screen > - User identifies an entity that will get a tag associated with it > - The user selects 'Add Tag' from the detailed entity screen and fills out > the necessary fields based on the tag definition. > - The tag is attached to the Entity -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-163) New Trait UI (Tag)
[ https://issues.apache.org/jira/browse/ATLAS-163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14948938#comment-14948938 ] Vishal Kadam commented on ATLAS-163: Thanks Suma. > New Trait UI (Tag) > -- > > Key: ATLAS-163 > URL: https://issues.apache.org/jira/browse/ATLAS-163 > Project: Atlas > Issue Type: Improvement >Affects Versions: 0.6-incubating >Reporter: Erik Bergenholtz >Assignee: Darshan Kumar >Priority: Critical > Labels: patch-available > Fix For: 0.6-incubating > > Attachments: ATLAS-163-v0.patch, ATLAS-163-v1.patch, TagDefinition.png > > > Atlas needs a UI to create new Tag definitions. > See attached screen-shots. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-188) Provide Ability to Add Tag to Entity
[ https://issues.apache.org/jira/browse/ATLAS-188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14940730#comment-14940730 ] Vishal Kadam commented on ATLAS-188: Adding dependency on 163 to avoid conflicts. Will attach patch for same shortly. > Provide Ability to Add Tag to Entity > > > Key: ATLAS-188 > URL: https://issues.apache.org/jira/browse/ATLAS-188 > Project: Atlas > Issue Type: Task >Affects Versions: 0.6-incubating >Reporter: Erik Bergenholtz >Assignee: Sanjay Patel >Priority: Critical > Fix For: 0.6-incubating > > > Atlas UI needs to provide the ability to add a tag to an existing entity (see > attached mocks). > User Story: > - User Searches for an entity (i.e. hive_table) from the main search screen > - User identifies an entity that will get a tag associated with it > - The user selects 'Add Tag' from the detailed entity screen and fills out > the necessary fields based on the tag definition. > - The tag is attached to the Entity -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-159) UI generated files should be target
[ https://issues.apache.org/jira/browse/ATLAS-159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14936285#comment-14936285 ] Vishal Kadam commented on ATLAS-159: [~shwethags] we will take a look at these and will send updated patch. > UI generated files should be target > --- > > Key: ATLAS-159 > URL: https://issues.apache.org/jira/browse/ATLAS-159 > Project: Atlas > Issue Type: Bug >Reporter: Shwetha G S >Assignee: Sanjay Patel >Priority: Blocker > Attachments: ATLAS-159.v1.patch > > > All the downloaded/generated files(like folders lib, node, node_modules etc) > from UI plugins should be in target so that mvn clean can clean up these > files. Build is broken because of this: > https://builds.apache.org/job/apache-atlas-nightly/72/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-159) UI generated files should be target
[ https://issues.apache.org/jira/browse/ATLAS-159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14746603#comment-14746603 ] Vishal Kadam commented on ATLAS-159: [~shwethags], we will take a look into intermittent failure. Regarding adding making dashboard as maven module, what kind of package you would like to have it? I will recommend to have *war* and then use war overlay in webapp. > UI generated files should be target > --- > > Key: ATLAS-159 > URL: https://issues.apache.org/jira/browse/ATLAS-159 > Project: Atlas > Issue Type: Bug >Reporter: Shwetha G S >Assignee: Sanjay Patel >Priority: Blocker > > All the downloaded/generated files(like folders lib, node, node_modules etc) > from UI plugins should be in target so that mvn clean can clean up these > files. Build is broken because of this: > https://builds.apache.org/job/apache-atlas-nightly/72/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-159) UI generated files should be target
[ https://issues.apache.org/jira/browse/ATLAS-159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14744821#comment-14744821 ] Vishal Kadam commented on ATLAS-159: If final goal is to add all this files under war generate by webapp, then isn't it good to have it under same umbrella? Otherwise it will create unnecessary module dependency. > UI generated files should be target > --- > > Key: ATLAS-159 > URL: https://issues.apache.org/jira/browse/ATLAS-159 > Project: Atlas > Issue Type: Bug >Reporter: Shwetha G S >Assignee: Sanjay Patel >Priority: Blocker > > All the downloaded/generated files(like folders lib, node, node_modules etc) > from UI plugins should be in target so that mvn clean can clean up these > files. Build is broken because of this: > https://builds.apache.org/job/apache-atlas-nightly/72/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-159) UI generated files should be target
[ https://issues.apache.org/jira/browse/ATLAS-159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14743968#comment-14743968 ] Vishal Kadam commented on ATLAS-159: Should we move content of dashboard to https://github.com/apache/incubator-atlas/tree/master/webapp/src/main/webapp and then use target folder of webapp for all runtime dependencies like lib, node, node_module & bower related folder? > UI generated files should be target > --- > > Key: ATLAS-159 > URL: https://issues.apache.org/jira/browse/ATLAS-159 > Project: Atlas > Issue Type: Bug >Reporter: Shwetha G S >Priority: Blocker > > All the downloaded/generated files(like folders lib, node, node_modules etc) > from UI plugins should be in target so that mvn clean can clean up these > files. Build is broken because of this: > https://builds.apache.org/job/apache-atlas-nightly/72/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (ATLAS-110) UI: Lineage should be clickable
[ https://issues.apache.org/jira/browse/ATLAS-110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14740077#comment-14740077 ] Vishal Kadam edited comment on ATLAS-110 at 9/11/15 3:06 AM: - To avoid merge conflicts apply ATLAS-110 after ATLAS-112. Will send the updated patch for same. was (Author: vkadam): To avoid merge conflits apply ATLAS-110 after ATLAS-112. Will send the updated patch for same. > UI: Lineage should be clickable > --- > > Key: ATLAS-110 > URL: https://issues.apache.org/jira/browse/ATLAS-110 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.6-incubating >Reporter: Erik Bergenholtz >Assignee: Vishal Kadam > Fix For: 0.6-incubating > > Attachments: ATLAS-110.patch > > > It should be possible to drill down on lineage. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-110) UI: Lineage should be clickable
[ https://issues.apache.org/jira/browse/ATLAS-110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14740077#comment-14740077 ] Vishal Kadam commented on ATLAS-110: To avoid merge conflits apply ATLAS-110 after ATLAS-112. Will send the updated patch for same. > UI: Lineage should be clickable > --- > > Key: ATLAS-110 > URL: https://issues.apache.org/jira/browse/ATLAS-110 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.6-incubating >Reporter: Erik Bergenholtz >Assignee: Vishal Kadam > Fix For: 0.6-incubating > > Attachments: ATLAS-110.patch > > > It should be possible to drill down on lineage. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ATLAS-152) TimeStamp fields not showing the details tab
Vishal Kadam created ATLAS-152: -- Summary: TimeStamp fields not showing the details tab Key: ATLAS-152 URL: https://issues.apache.org/jira/browse/ATLAS-152 Project: Atlas Issue Type: Bug Reporter: Vishal Kadam Assignee: Vishal Kadam Priority: Minor Fix For: 0.6-incubating Currently, frontend-maven-plugin doesn't work without internet. Can we use https://github.com/allegro/grunt-maven-plugin to support offline builds? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (ATLAS-113) Add an About Dialog to Apache Atlas UI with version number
[
https://issues.apache.org/jira/browse/ATLAS-113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14740112#comment-14740112
]
Vishal Kadam edited comment on ATLAS-113 at 9/11/15 3:51 AM:
-
About dialog code is deployed and tested on
http://162.212.133.190:3129/#!/search
Update patch (ATLAS-113.v1.patch) is submitted
was (Author: vkadam):
About dialog code is deployed and tested on
http://162.212.133.190:3129/#!/search
> Add an About Dialog to Apache Atlas UI with version number
> ---
>
> Key: ATLAS-113
> URL: https://issues.apache.org/jira/browse/ATLAS-113
> Project: Atlas
> Issue Type: Improvement
>Reporter: Rohit
>Assignee: Vishal Kadam
> Fix For: 0.6-incubating
>
> Attachments: ATLAS-113.patch, ATLAS-113.v1.patch, Apache Atlas
> 2015-08-27 08-54-19.jpg
>
>
> The Atlas UI should provide a way to display the version information for
> Atlas:
> The API used to fetch the version:
> /api/atlas/admin/version
> Response:
> {
> Version: "0.6-incubating-SNAPSHOT-rrelease",
> Name: "apache-atlas",
> Description: "Metadata Management and Data Governance Platform over Hadoop"
> }
> The version and description should be displayed similar to Ambari:
> https://monosnap.com/file/C91M7gbGmU59RMUlj7M9hcKKvsnGwf
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (ATLAS-111) UI: Create Help Link
[ https://issues.apache.org/jira/browse/ATLAS-111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Kadam reassigned ATLAS-111: -- Assignee: Vishal Kadam (was: Rohit) > UI: Create Help Link > > > Key: ATLAS-111 > URL: https://issues.apache.org/jira/browse/ATLAS-111 > Project: Atlas > Issue Type: New Feature >Reporter: Erik Bergenholtz >Assignee: Vishal Kadam > Fix For: 0.6-incubating > > Attachments: ATLAS-111.v1.patch > > > Create a help link for ATLAS that links to this document > https://cwiki.apache.org/confluence/display/ATLAS/Atlas+Home -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-152) TimeStamp fields not showing the details tab
[ https://issues.apache.org/jira/browse/ATLAS-152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Kadam updated ATLAS-152: --- Attachment: ATLAS-152.v1.patch This code is deployed and tested on http://162.212.133.190:3112/#!/details/82f8172b-9a22-4aeb-81da-c1ee7ad61c1b Patch file name ATLAS-152.v1.patch > TimeStamp fields not showing the details tab > - > > Key: ATLAS-152 > URL: https://issues.apache.org/jira/browse/ATLAS-152 > Project: Atlas > Issue Type: Bug >Reporter: Vishal Kadam >Assignee: Vishal Kadam >Priority: Minor > Fix For: 0.6-incubating > > Attachments: ATLAS-152.v1.patch > > > TimeStamp fields not showing the details tab. Please investigate root cause > and fix. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-113) Add an About Dialog to Apache Atlas UI with version number
[
https://issues.apache.org/jira/browse/ATLAS-113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vishal Kadam updated ATLAS-113:
---
Attachment: ATLAS-113.v1.patch
About dialog code is deployed and tested on
http://162.212.133.190:3129/#!/search
> Add an About Dialog to Apache Atlas UI with version number
> ---
>
> Key: ATLAS-113
> URL: https://issues.apache.org/jira/browse/ATLAS-113
> Project: Atlas
> Issue Type: Improvement
>Reporter: Rohit
>Assignee: Vishal Kadam
> Fix For: 0.6-incubating
>
> Attachments: ATLAS-113.patch, ATLAS-113.v1.patch, Apache Atlas
> 2015-08-27 08-54-19.jpg
>
>
> The Atlas UI should provide a way to display the version information for
> Atlas:
> The API used to fetch the version:
> /api/atlas/admin/version
> Response:
> {
> Version: "0.6-incubating-SNAPSHOT-rrelease",
> Name: "apache-atlas",
> Description: "Metadata Management and Data Governance Platform over Hadoop"
> }
> The version and description should be displayed similar to Ambari:
> https://monosnap.com/file/C91M7gbGmU59RMUlj7M9hcKKvsnGwf
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ATLAS-109) Remove v2 Folder
[ https://issues.apache.org/jira/browse/ATLAS-109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Kadam updated ATLAS-109: --- Attachment: ATLAS-109.v2.patch Update patch according to changes in ATLAS-90 > Remove v2 Folder > > > Key: ATLAS-109 > URL: https://issues.apache.org/jira/browse/ATLAS-109 > Project: Atlas > Issue Type: Task >Affects Versions: 0.6-incubating >Reporter: Erik Bergenholtz >Assignee: Vishal Kadam > Fix For: 0.6-incubating > > Attachments: ATLAS-109.patch, ATLAS-109.v2.patch > > > Remove v2 folder from atlas and update all the preferences related that. move > all the code from v2 folder to dashboard. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-90) Support offline builds
[ https://issues.apache.org/jira/browse/ATLAS-90?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Kadam updated ATLAS-90: -- Attachment: ATLAS-90.v2.patch Moved bower temporary location to webapp/target. For offline support mvn clean should not be used. > Support offline builds > -- > > Key: ATLAS-90 > URL: https://issues.apache.org/jira/browse/ATLAS-90 > Project: Atlas > Issue Type: Bug >Reporter: Shwetha G S >Assignee: Vishal Kadam >Priority: Minor > Fix For: 0.6-incubating > > Attachments: ATLAS-90.v1.patch, ATLAS-90.v2.patch > > > Currently, frontend-maven-plugin doesn't work without internet. Can we use > https://github.com/allegro/grunt-maven-plugin to support offline builds? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (ATLAS-90) Support offline builds
[ https://issues.apache.org/jira/browse/ATLAS-90?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14736061#comment-14736061 ] Vishal Kadam edited comment on ATLAS-90 at 9/9/15 3:10 AM: --- Attaching old version (ATLAS-90.v1.patch) for reference was (Author: vkadam): Attaching old version (v1) for reference > Support offline builds > -- > > Key: ATLAS-90 > URL: https://issues.apache.org/jira/browse/ATLAS-90 > Project: Atlas > Issue Type: Bug >Reporter: Shwetha G S >Assignee: Vishal Kadam >Priority: Minor > Fix For: 0.6-incubating > > Attachments: ATLAS-90.v1.patch, ATLAS-90.v2.patch > > > Currently, frontend-maven-plugin doesn't work without internet. Can we use > https://github.com/allegro/grunt-maven-plugin to support offline builds? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-90) Support offline builds
[ https://issues.apache.org/jira/browse/ATLAS-90?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Kadam updated ATLAS-90: -- Attachment: ATLAS-90.v1.patch Attaching old version (v1) for reference > Support offline builds > -- > > Key: ATLAS-90 > URL: https://issues.apache.org/jira/browse/ATLAS-90 > Project: Atlas > Issue Type: Bug >Reporter: Shwetha G S >Assignee: Vishal Kadam >Priority: Minor > Fix For: 0.6-incubating > > Attachments: ATLAS-90.v1.patch > > > Currently, frontend-maven-plugin doesn't work without internet. Can we use > https://github.com/allegro/grunt-maven-plugin to support offline builds? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-90) Support offline builds
[ https://issues.apache.org/jira/browse/ATLAS-90?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14721899#comment-14721899 ] Vishal Kadam commented on ATLAS-90: --- Yes. Support offline builds -- Key: ATLAS-90 URL: https://issues.apache.org/jira/browse/ATLAS-90 Project: Atlas Issue Type: Bug Reporter: Shwetha G S Assignee: Vishal Kadam Priority: Minor Fix For: 0.6-incubating Attachments: 6.patch.txt, ATLAS-90-full.patch, ATLAS-90.patch Currently, frontend-maven-plugin doesn't work without internet. Can we use https://github.com/allegro/grunt-maven-plugin to support offline builds? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-110) UI: Lineage should be clickable
[ https://issues.apache.org/jira/browse/ATLAS-110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14718060#comment-14718060 ] Vishal Kadam commented on ATLAS-110: Yes, its tested and running on http://162.212.133.190:3137/#!/details/82f8172b-9a22-4aeb-81da-c1ee7ad61c1b (Input tab) UI: Lineage should be clickable --- Key: ATLAS-110 URL: https://issues.apache.org/jira/browse/ATLAS-110 Project: Atlas Issue Type: Bug Affects Versions: 0.6-incubating Reporter: Erik Bergenholtz Assignee: Vishal Kadam Fix For: 0.6-incubating Attachments: ATLAS-110.patch It should be possible to drill down on lineage. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-109) Remove v2 Folder
[ https://issues.apache.org/jira/browse/ATLAS-109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14718057#comment-14718057 ] Vishal Kadam commented on ATLAS-109: Thanks for adding blocked link, I almost for Jira its been a long time I used it ;) And yes it has been tested. Remove v2 Folder Key: ATLAS-109 URL: https://issues.apache.org/jira/browse/ATLAS-109 Project: Atlas Issue Type: Task Affects Versions: 0.6-incubating Reporter: Erik Bergenholtz Assignee: Erik Bergenholtz Fix For: 0.6-incubating Attachments: ATLAS-109.patch Remove v2 folder from atlas and update all the preferences related that. move all the code from v2 folder to dashboard. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-90) Support offline builds
[ https://issues.apache.org/jira/browse/ATLAS-90?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Kadam updated ATLAS-90: -- Attachment: ATLAS-90.patch Formatting done for pom.xml Support offline builds -- Key: ATLAS-90 URL: https://issues.apache.org/jira/browse/ATLAS-90 Project: Atlas Issue Type: Bug Reporter: Shwetha G S Assignee: Vishal Kadam Priority: Minor Fix For: 0.6-incubating Attachments: 6.patch.txt, ATLAS-90.patch Currently, frontend-maven-plugin doesn't work without internet. Can we use https://github.com/allegro/grunt-maven-plugin to support offline builds? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-113) Add an About Dialog to Apache Atlas UI with version number
[
https://issues.apache.org/jira/browse/ATLAS-113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vishal Kadam updated ATLAS-113:
---
Attachment: ATLAS-113.patch
Add an About Dialog to Apache Atlas UI with version number
---
Key: ATLAS-113
URL: https://issues.apache.org/jira/browse/ATLAS-113
Project: Atlas
Issue Type: Improvement
Reporter: Rohit
Assignee: Vishal Kadam
Attachments: ATLAS-113.patch
The Atlas UI should provide a way to display the version information for
Atlas:
The API used to fetch the version:
/api/atlas/admin/version
Response:
{
Version: 0.6-incubating-SNAPSHOT-rrelease,
Name: apache-atlas,
Description: Metadata Management and Data Governance Platform over Hadoop
}
The version and description should be displayed similar to Ambari:
https://monosnap.com/file/C91M7gbGmU59RMUlj7M9hcKKvsnGwf
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ATLAS-110) UI: Lineage should be clickable
[ https://issues.apache.org/jira/browse/ATLAS-110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Kadam updated ATLAS-110: --- Attachment: ATLAS-110.patch UI: Lineage should be clickable --- Key: ATLAS-110 URL: https://issues.apache.org/jira/browse/ATLAS-110 Project: Atlas Issue Type: Bug Affects Versions: 0.6-incubating Reporter: Erik Bergenholtz Assignee: Vishal Kadam Fix For: 0.6-incubating Attachments: ATLAS-110.patch It should be possible to drill down on lineage. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-109) Remove v2 Folder
[ https://issues.apache.org/jira/browse/ATLAS-109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Kadam updated ATLAS-109: --- Attachment: ATLAS-109.patch Patch for removing v2 folder completely and adding its content to dashboard folder. Remove v2 Folder Key: ATLAS-109 URL: https://issues.apache.org/jira/browse/ATLAS-109 Project: Atlas Issue Type: Task Affects Versions: 0.6-incubating Reporter: Erik Bergenholtz Assignee: Erik Bergenholtz Fix For: 0.6-incubating Attachments: ATLAS-109.patch Remove v2 folder from atlas and update all the preferences related that. move all the code from v2 folder to dashboard. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-90) Support offline builds
[ https://issues.apache.org/jira/browse/ATLAS-90?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Kadam updated ATLAS-90: -- Attachment: 6.patch.txt Patch for offline build support Support offline builds -- Key: ATLAS-90 URL: https://issues.apache.org/jira/browse/ATLAS-90 Project: Atlas Issue Type: Bug Reporter: Shwetha G S Priority: Minor Fix For: 0.6-incubating Attachments: 5.patch.txt, 6.patch.txt Currently, frontend-maven-plugin doesn't work without internet. Can we use https://github.com/allegro/grunt-maven-plugin to support offline builds? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ATLAS-121) Unable to build on fresh stack
Vishal Kadam created ATLAS-121: -- Summary: Unable to build on fresh stack Key: ATLAS-121 URL: https://issues.apache.org/jira/browse/ATLAS-121 Project: Atlas Issue Type: Bug Reporter: Vishal Kadam On fresh checkout or doing `mvn clean` before `mvn clean install` fails the build process with following error. Its failing because assembly is looking for a file incubator-atlas/webapp/target/atlas-webapp-0.6-incubating-SNAPSHOT.war which does not exists first time or after mvn clean. OK [INFO] [INFO] --- maven-site-plugin:3.2:attach-descriptor (attach-descriptor) @ apache-atlas --- [INFO] [INFO] --- maven-assembly-plugin:2.2.1:single (default) @ apache-atlas --- [INFO] Reading assembly descriptor: src/main/assemblies/standalone-package.xml [INFO] Reading assembly descriptor: src/main/assemblies/src-package.xml [INFO] [INFO] Reactor Summary: [INFO] [INFO] apache-atlas ... FAILURE [ 4.786 s] [INFO] Apache Atlas Typesystem SKIPPED [INFO] Apache Atlas Client SKIPPED [INFO] Apache Atlas Notification .. SKIPPED [INFO] Apache Atlas Repository SKIPPED [INFO] Apache Atlas Web Application ... SKIPPED [INFO] Apache Atlas Documentation . SKIPPED [INFO] Apache Atlas Hive Bridge ... SKIPPED [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 5.587 s [INFO] Finished at: 2015-08-21T23:32:01-04:00 [INFO] Final Memory: 26M/981M [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-assembly-plugin:2.2.1:single (default) on project apache-atlas: Failed to create assembly: Error adding file to archive: /hortonworks/incubator-atlas/webapp/target/atlas-webapp-0.6-incubating-SNAPSHOT.war isn't a file. - [Help 1] [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/MojoExecutionException -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-90) Support offline builds
[ https://issues.apache.org/jira/browse/ATLAS-90?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14706173#comment-14706173 ] Vishal Kadam commented on ATLAS-90: --- @Venkat, thanks for info. But I am not able to assign this ticket to myself. I guess I have only read access on this project. Support offline builds -- Key: ATLAS-90 URL: https://issues.apache.org/jira/browse/ATLAS-90 Project: Atlas Issue Type: Bug Reporter: Shwetha G S Priority: Minor Fix For: 0.6-incubating Attachments: 5.patch.txt Currently, frontend-maven-plugin doesn't work without internet. Can we use https://github.com/allegro/grunt-maven-plugin to support offline builds? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-90) Support offline builds
[ https://issues.apache.org/jira/browse/ATLAS-90?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Kadam updated ATLAS-90: -- Attachment: 5.patch.txt Patch for offline support. Pull request for same is also available under https://github.com/apache/incubator-atlas/pull/5 Support offline builds -- Key: ATLAS-90 URL: https://issues.apache.org/jira/browse/ATLAS-90 Project: Atlas Issue Type: Bug Reporter: Shwetha G S Priority: Minor Attachments: 5.patch.txt Currently, frontend-maven-plugin doesn't work without internet. Can we use https://github.com/allegro/grunt-maven-plugin to support offline builds? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
