Closed rrutt closed 11 years ago
mboudreau
commented
11 years ago Hm, that would be a good idea. I think it should be in the Main repository. I think creating a standalone build profile with a Main class that starts the process would be a good way to start. Please merge your changes into the main branch, but I would prefer that you use the profile name "standalone" and not "exejar".
Cheers.
lloydaduke
commented
11 years ago As far as I can tell this hasn't made its way into the main repository? If it hasn't, are you guys using this as a development DB? If so, how are you starting both Alternator and the development server? I have got it working for testing and, it works very well. Thank you for the contributions.
rrutt
commented
11 years ago With the recent fixes/enhancements by 'ehoule' and 'sashee' I have been waiting to merge my "standalone' executable JAR version into a new Pull Request. I can get that ready for submission to this main repository in the next week or two. I still need to merge the latest enhancements from this repository into my 'rrutt' repository and then change the Maven profile name to "standalone" instead of "exejar".
rrutt
commented
11 years ago The latest version of the standalone executable JAR profile is available in my forked repository in this branch:
https://github.com/rrutt/Alternator/tree/standalone-executable-jar
This includes the merged latest revisions from the current 'master' branch of this primary repository. The Maven profile name is now 'standalone' as requested.
There is another pending Pull Request from 'sashee'. Once that is approved and merged into the 'master' branch, I will merge it into my 'standalone-executable-jar' branch, run all tests, and submit a new Pull Request.
mboudreau
commented
11 years ago Alright, will pull in changes then. On 2013-03-23 3:07 PM, "Rick Rutt" notifications@github.com wrote:
The latest version of the standalone executable JAR profile is available in my forked repository in this branch:
https://github.com/rrutt/Alternator/tree/standalone-executable-jar
This includes the merged latest revisions from the current 'master' branch of this primary repository.
There is another pending Pull Request from 'sashee'. Once that is approved and merged into the 'master' branch, I will merge it into my 'standalone-executable-jar' branch, run all tests, and submit a new Pull Request.
— Reply to this email directly or view it on GitHubhttps://github.com/mboudreau/Alternator/issues/51#issuecomment-15331432 .
rrutt
commented
11 years ago I didn't intend to "rush" the merge of the prior Pull Request, but I appreciate the fast action.
My new Pull Request, which includes a pre-merge from the most recent 'master' branch has been submitted:
https://github.com/mboudreau/Alternator/pull/57
I ran the full Maven test suites and all tests pass.
In my forked repository I have a branch that includes an optional Maven profile to build an executable JAR file for running Alternator as a standalone process. This allows access from non-Java client applications under development. For more information see the ReadMe notes on my branch:
https://github.com/rrutt/Alternator/tree/executable-jar#readme
The resulting executable JAR contains all third-party dependencies so it is 15 MB. This is the reason an optional Maven profile is used to build it. The normal build omits this larger artifact.
Is this feature something that should be submitted into the main repository? If not, I am willing to keep it up-to-date as a branch in my forked repository.