Lol, I can't seem to explain it properly. Take maven/ant/config files out of the equation it doesn't matter for this example. This has to do with getting some identifying information into the official SDK releases. We don't want to pass variables as an SDK user. We want the official SDK to already come packaged with a version number or a build number or a build date...
Here's the scenario that I would love to see happen: 1. SDK user downloads official Royale SDK release and never modifies it. 2. SDK User compiles their app using official SDK and references an official SDK property that contains the SDK identifier already built in it. Meaning I should be able to code complete off of the SDK and find something that already exists and could return me an official identifier. -Mark K -----Original Message----- From: Carlos Rovira [mailto:[email protected]] Sent: Monday, April 29, 2019 1:14 PM To: [email protected] Subject: [Non-DoD Source] Re: Version property (was: Let's bump Royale version to 1.0) ok, we do the following in maven for other needs so this will be valid for you too: in your maven properties. <royale.framework.version>0.9.6-OR-WHATEVER</royale.framework.version> <plugin> <groupId>org.apache.royale.compiler</groupId> <artifactId>royale-maven-plugin</artifactId> <extensions>true</extensions> <configuration> ... <defines> <property> <name>BUILD::royaleVersion</name> <value>'"${royale.framework.version}"'</value> </property> ... </defines> ... defines can be done in ANT, asconfigc, config.xml.... Then in AS3 or MXML /** * ROYALE VERSION NUMBER */ private static var _royaleVersion :String = BUILD::royaleVersion; So now you can use in any place you want HTH Carlos
