Document development setup for Exhibitor
rokka-n opened this issue · comments
Can somebody explain how this project is supposed to be build?
I wanted to make a simple change in one of the classes, but producing working jar file is next to impossible.
The code on master is now built with Maven. So, normal Maven commands to build the JAR (e.g. mvn clean install). What you do next depends on what kind of artifact you want. If you want the standalone version see here: https://github.com/soabase/exhibitor/wiki/Building-Exhibitor
I wanted to quickly patch the app because it's breakes for "special" aws
regions.
And then discovered that local developmented is not explained well.
Especially for those who are not java developers :)
So details of the local dev cycle is still a puzzle to. Somehow I managed
to build new version.
I found that pom.xml in root folder should have something like
1.5.7-SNAPSHOT, so gradle (or was it mvn?) can produce 1.5.7-SNAPSHOT-.jar
in local .m2 cache.
So then it can be packaged as app in target/exhibitor-1.5.7-SNAPSHOT.jar
Also repo should be checked out as v1.5.6 tag? Not sure, but master and
tagged branches are two different thing.
…On Sun, Mar 12, 2017 at 10:28 AM, Jordan Zimmerman ***@***.*** > wrote:
The code on master is now built with Maven. So, normal Maven commands to
build the JAR (e.g. mvn clean install). What you do next depends on what
kind of artifact you want. If you want the standalone version see here:
https://github.com/soabase/exhibitor/wiki/Building-Exhibitor
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#334 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AENT-pK4TGflQhBZyaVZ6HwmmueAmsxzks5rlCtNgaJpZM4MaZIn>
.
We should probably add a doc explaining how to setup local dev environment in terms of developing Exhibitor itself.