Re: UMSBuilderV2: build any UMS branch
Posted: Sat Oct 04, 2014 11:50 pm
Quick question: is there any way to build an specific version of UMS via UMSbuilder? (ie tag 4.1.3-WindowsLinux-Java8 or up to commit 1338a57)
Thx, Wolf
Thx, Wolf
A short text to describe your forum
https://www.universalmediaserver.com/forum/
https://www.universalmediaserver.com/forum/viewtopic.php?t=1782
Create the buildx.bat (disclaimer: untested ) below in your UMSBuilder directory:Wolfgan wrote:is there any way to build an specific version of UMS via UMSbuilder? (ie tag 4.1.3-WindowsLinux-Java8 or up to commit 1338a57)
and run it from a command window in your UMSBuilder directory like so:@echo off
:: usage: buildx <tag or commit>
:: requirements:
:: --- msysgit should be in your system path.
:: --- the target branch should be up to date (i.e. build it once before running this)
for /d %%d in ("%CD%\JDK*") do set JAVA_HOME=%%d
for /d %%d in ("%CD%\Maven*") do set M2_HOME=%%d
set PATH=%M2_HOME%\bin;%JAVA_HOME%\bin;%PATH%
cd UniversalMediaServer
git checkout %1
mvn package
git checkout master
Code: Select all
buildx 1338a57
Code: Select all
buildx 4.1.3-WindowsLinux-Java8
Wolf, I'm assuming you're looking for the jars in UniversalMediaServer\target\? If that's not the problem then it's probably my bad for reeling this off the top of my head . I'll roll it into the buildv2 properly with error checking, etc, as you suggest.Wolfgan wrote:somehow it seems to build a different .jar
Yes, I'm looking for the resulting file at the folder you mentioned. UMSbuilder produces 2 jar files, one small (~4MB) and a bigger one with dependencies (~22MB) which is the one I use for manual launch and testing. Somehow this bigger jar is the one that buildx doesn't output.infidel wrote:Wolf, I'm assuming you're looking for the jars in UniversalMediaServer\target\? If that's not the problem then it's probably my bad for reeling this off the top of my head . I'll roll it into the buildv2 properly with error checking, etc, as you suggest.Wolfgan wrote:somehow it seems to build a different .jar
Mainly I didn't want to write support for user text input (batch files are primitive beasts, one needs to write all this stuff from scratch). I realize this interferes with double-click startup convenience, though .Wolfgan wrote:You opted for passing the intended commit # as a command line argument, any reason for not to be requested as part of the interactive menu process?
It should have also created compiled .class files in your target\classes folder. It's for use with a 'dev' setup, where you run ums straight from these raw compiled files and skip the time-consuming jar and exe stages.Wolfgan wrote:What's the difference between ... the new compile option? it just generated an extra.nsh file in my target folder, but nothing else