[jira] [Commented] (ATLAS-2668) Add OMAG Server to distribution
[ https://issues.apache.org/jira/browse/ATLAS-2668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16473412#comment-16473412 ] Nigel Jones commented on ATLAS-2668: Updated patch to match review board > Add OMAG Server to distribution > --- > > Key: ATLAS-2668 > URL: https://issues.apache.org/jira/browse/ATLAS-2668 > Project: Atlas > Issue Type: Improvement >Reporter: Nigel Jones >Assignee: Nigel Jones >Priority: Major > Attachments: ATLAS-2668e.patch > > > The standalone Open Metadata server is built under omag-server. > However it is not incorporated into the distribution files (*.gz), and needs > careful attention to the classpath to work (ie launch from within IntelliJ) > The intent of this Jira is > * have OMAG server available 'out of the box' in a binary distribution so > that users can easily launch it without having to check classpaths or run in > an odd environment > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-2668) Add OMAG Server to distribution
[ https://issues.apache.org/jira/browse/ATLAS-2668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16470631#comment-16470631 ] Nigel Jones commented on ATLAS-2668: Now added to distribution assemblies. Assembly includes main jar file & a new README.md which just documents how to launch OMAG Server After patch installed new files are created: ie 17:18 $ ls README.md omag-server-1.0.0-SNAPSHOT.jar ✔ ~/src/atlas/distro/target/apache-atlas-1.0.0-SNAPSHOT-omag-server/omag-server-1.0.0-SNAPSHOT [master ↑·1|…1⚑ 3] This mirrors the scheme used for other packages A subsequent Jira could consider adding specific launch/terminate scripts for the omag server. Looking at the atlas scripts these make use of some common python libs which manages atlas config - in python (easier for platform independence) so suggest defer for now to consider what the requirements are. This Jira does make it easier to launch OMAG server with default settings. > Add OMAG Server to distribution > --- > > Key: ATLAS-2668 > URL: https://issues.apache.org/jira/browse/ATLAS-2668 > Project: Atlas > Issue Type: Improvement >Reporter: Nigel Jones >Assignee: Nigel Jones >Priority: Major > Attachments: ATLAS-2668.patch > > > The standalone Open Metadata server is built under omag-server. > However it is not incorporated into the distribution files (*.gz), and needs > careful attention to the classpath to work (ie launch from within IntelliJ) > The intent of this Jira is > * have OMAG server available 'out of the box' in a binary distribution so > that users can easily launch it without having to check classpaths or run in > an odd environment > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-2668) Add OMAG Server to distribution
[ https://issues.apache.org/jira/browse/ATLAS-2668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16470379#comment-16470379 ] Nigel Jones commented on ATLAS-2668: Originally used the following pom.xml fragment which has worked before... but for other standalone apps. It doesn't work for spring, so I will use the spring framework version, but adding here as a useful note on making a standalone app with dependencies and main class identified org.apache.maven.plugins maven-shade-plugin 3.1.1 false package shade org.apache.atlas.omag.application.OMAGApplication In this case I'll use org.springframework.boot spring-boot-maven-plugin 1.5.10.RELEASE repackage This fragment will build a standalone jar, so we can now do: ✔ ~/src/atlas/omag-server/target [master|✚ 1⚑ 3] 14:07 $ ls classes maven-shared-archive-resources original-omag-server-1.0.0-SNAPSHOT.jar generated-sources maven-status rat.txt maven-archiver omag-server-1.0.0-SNAPSHOT.jar test-classes ✔ ~/src/atlas/omag-server/target [master|✚ 1⚑ 3] 14:07 $ java -jar ./omag-server-1.0.0-SNAPSHOT.jar . _ __ _ _ /\\ / ___'_ __ _ _(_)_ __ __ _ \ \ \ \ ( ( )\___ | '_ | '_| | '_ \/ _` | \ \ \ \ \\/ ___)| |_)| | | | | || (_| | ) ) ) ) ' || .__|_| |_|_| |_\__, | / / / / =|_|==|___/=/_/_/_/ :: Spring Boot :: (v1.0.0-SNAPSHOT) 2018-05-10 14:07:12.047 INFO 36215 --- [ main] o.a.a.omag.application.OMAGApplication : Starting OMAGApplication v1.0.0-SNAPSHOT on nigels-mbp.hursley.uk.ibm.com with PID 36215 (/Users/jonesn/IdeaProjects/atlas/omag-server/target/omag-server-1.0.0-SNAPSHOT.jar started by jonesn in /Users/jonesn/IdeaProjects/atlas/omag-server/target) 2018-05-10 14:07:12.050 INFO 36215 --- [ main] o.a.a.omag.application.OMAGApplication : No active profile set, falling back to default profiles: default etc ... That's build done. Next part - place somewhere in distribution... > Add OMAG Server to distribution > --- > > Key: ATLAS-2668 > URL: https://issues.apache.org/jira/browse/ATLAS-2668 > Project: Atlas > Issue Type: Improvement >Reporter: Nigel Jones >Assignee: Nigel Jones >Priority: Major > > The standalone Open Metadata server is built under omag-server. > However it is not incorporated into the distribution files (*.gz), and needs > careful attention to the classpath to work (ie launch from within IntelliJ) > The intent of this Jira is > * have OMAG server available 'out of the box' in a binary distribution so > that users can easily launch it without having to check classpaths or run in > an odd environment > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
