>From the royale-compiler repo:
1. Run:
ant -f releasesteps.xml Release_Step_003 -Drelease.version=0.9.9
This will download the artifacts then unzip and compile the source artifact.
2. Validate that the compiled artifacts match the downloaded artifacts.
3. If they do, then run ant -f
>From the royale-compiler repo:
1. Run:
ant -f releasesteps.xml Release_Step_003 -Drelease.version=0.9.9
This will download the artifacts then unzip and compile the source artifact.
2. Validate that the compiled artifacts match the downloaded artifacts.
3. If they do, then run ant -f
>From the royale-compiler repo:
1. Run:
ant -f releasesteps.xml Release_Step_003 -Drelease.version=0.9.9
This will download the artifacts then unzip and compile the source artifact.
2. Validate that the compiled artifacts match the downloaded artifacts.
3. If they do, then run ant -f
>From the royale-compiler repo:
1. Run:
ant -f releasesteps.xml Release_Step_003 -Drelease.version=0.9.9
This will download the artifacts then unzip and compile the source artifact.
2. Validate that the compiled artifacts match the downloaded artifacts.
3. If they do, then run ant -f
>From the royale-compiler repo:
1. Run:
ant -f releasesteps.xml Release_Step_003 -Drelease.version=0.9.9
This will download the artifacts then unzip and compile the source artifact.
2. Validate that the compiled artifacts match the downloaded artifacts.
3. If they do, then run ant -f
>From the royale-compiler repo:
1. Run:
ant -f releasesteps.xml Release_Step_003 -Drelease.version=0.9.8
This will download the artifacts then unzip and compile the source artifact.
2. Validate that the compiled artifacts match the downloaded artifacts.
3. If they do, then run ant -f
>From the royale-compiler repo:
1. Run:
ant -f releasesteps.xml Release_Step_003 -Drelease.version=0.9.8
This will download the artifacts then unzip and compile the source artifact.
2. Validate that the compiled artifacts match the downloaded artifacts.
3. If they do, then run ant -f
>From the royale-compiler repo:
1. Run:
ant -f releasesteps.xml Release_Step_003 -Drelease.version=0.9.8
This will download the artifacts then unzip and compile the source artifact.
2. Validate that the compiled artifacts match the downloaded artifacts.
3. If they do, then run ant -f
>From the royale-compiler repo:
1. Run:
ant -f releasesteps.xml Release_Step_003 -Drelease.version=0.9.8
This will download the artifacts then unzip and compile the source artifact.
2. Validate that the compiled artifacts match the downloaded artifacts.
3. If they do, then run ant -f
>From the royale-compiler repo:
1. Run:
ant -f releasesteps.xml Release_Step_003 -Drelease.version=0.9.8
This will download the artifacts then unzip and compile the source artifact.
2. Validate that the compiled artifacts match the downloaded artifacts.
3. If they do, then run ant -f
>From the royale-compiler repo:
1. Run:
ant -f releasesteps.xml Release_Step_003 -Drelease.version=0.9.8
This will download the artifacts then unzip and compile the source artifact.
2. Validate that the compiled artifacts match the downloaded artifacts.
3. If they do, then run ant -f
>From the royale-compiler repo:
1. Run:
ant -f releasesteps.xml Release_Step_003 -Drelease.version=0.9.8
This will download the artifacts then unzip and compile the source artifact.
2. Validate that the compiled artifacts match the downloaded artifacts.
3. If they do, then run ant -f
>From the royale-compiler repo:
1. Run:
ant -f releasesteps.xml Release_Step_003 -Drelease.version=0.9.8
This will download the artifacts then unzip and compile the source artifact.
2. Validate that the compiled artifacts match the downloaded artifacts.
3. If they do, then run ant -f
>From the royale-compiler repo:
1. Run:
ant -f releasesteps.xml Release_Step_003 -Drelease.version=0.9.8
This will download the artifacts then unzip and compile the source artifact.
2. Validate that the compiled artifacts match the downloaded artifacts.
3. If they do, then run ant -f
eased tests and therefore needs a dependency to the playerglobal.
>>
>> Chris
>>
>>
>>
>> Von: Harbs
>> Datum: Freitag, 4. Dezember 2020 um 11:18
>> An: dev@royale.apache.org
>> Betreff: Re: Release
le with or without swf, it’s just that “with-swf” turns on all Flash
>> released tests and therefore needs a dependency to the playerglobal.
>>
>> Chris
>>
>>
>>
>> Von: Harbs
>> Datum: Freitag, 4. Dezember 2020 um 11:18
>>
> Datum: Freitag, 4. Dezember 2020 um 11:18
> An: dev@royale.apache.org
> Betreff: Re: Release Step 003 Succeeded
> OK. Progress.
>
> I got reproducible build of two jars, but I’m getting a failure on
> flex-compiler-oem.
>
> My build has this in the
to the playerglobal.
Chris
Von: Harbs
Datum: Freitag, 4. Dezember 2020 um 11:18
An: dev@royale.apache.org
Betreff: Re: Release Step 003 Succeeded
OK. Progress.
I got reproducible build of two jars, but I’m getting a failure on
flex-compiler-oem.
My build has this in the DEPENDENCIES file which is missing
OK. Progress.
I got reproducible build of two jars, but I’m getting a failure on
flex-compiler-oem.
My build has this in the DEPENDENCIES file which is missing in the CI build:
- playerglobal com.adobe.flash.framework:playerglobal:swc:20.0
Any clues as to why?
> On Nov 26, 2020, at 9:16
ts work anymore.
>
> In that case we’ll have real problems with being able to do a full build
> on new machines.
>
> Chris
>
>
> Von: Harbs
> Datum: Freitag, 4. Dezember 2020 um 10:27
> An: Apache Royale Development
> Betreff: Re: Release Step 003 Succeeded
> In runn
we’ll have real problems with being able to do a full build on new
machines.
Chris
Von: Harbs
Datum: Freitag, 4. Dezember 2020 um 10:27
An: Apache Royale Development
Betreff: Re: Release Step 003 Succeeded
In running the script on Windows I ran into the same Flash problem.
It seems like I you
eem to
>> not like this setting. I particularly remember the plugins for antlr2, 3 and
>> 4 don’t really like taking control of the line.separators.
>>
>> So right now, an “easy fix” would be to only do releases on Windows
>> machines. But I know that’s not a gr
arators.
>
> So right now, an “easy fix” would be to only do releases on Windows
machines. But I know that’s not a great solution.
>
> Chris
>
>
>
>
> Von: Alex Harui
> Datum: Mittwoch, 2. Dezember 2020 um 20:29
> An: d
twoch, 2. Dezember 2020 um 20:29
> An: dev@royale.apache.org
> Betreff: Re: Release Step 003 Succeeded
> A Jar is a zip. Check the dates of the .class files that are zipped into the
> jar. We are using a tool that should set the dates correctly, but maybe it
> isn't working.
>
, an “easy fix” would be to only do releases on Windows machines.
But I know that’s not a great solution.
Chris
Von: Alex Harui
Datum: Mittwoch, 2. Dezember 2020 um 20:29
An: dev@royale.apache.org
Betreff: Re: Release Step 003 Succeeded
A Jar is a zip. Check the dates of the .class files
script?
>>> Cause I usually run most of my builds in IntelliJ and there I simply
>> select the JDK and it sort of magically gets selected (I don’t have
>> JAVA_HOME set explicitly either)
>>>
>>> Chris
>>>
>>>
JDK and it sort of magically gets selected (I don’t have
>> JAVA_HOME set explicitly either)
>>>
>>> Chris
>>>
>>>
>>>
>>> Von: Harbs
>>> Datum: Dienstag, 1. Dezember 2020 um 19:28
>>> An: dev@royale.apache.org
>&
wrapper. So when using this we shouldn’t be required to
> attribute anything in our LICENSE or NOTICE files.
>
> Chris
>
>
> Von: Christofer Dutz
> Datum: Mittwoch, 2. Dezember 2020 um 13:32
> An: dev@royale.apache.org
> Betreff: AW: Release Step 003 Succeeded
> H
is triggered
> by an IDE or Ant script?
> > Cause I usually run most of my builds in IntelliJ and there I simply
> select the JDK and it sort of magically gets selected (I don’t have
> JAVA_HOME set explicitly either)
> >
> > Chris
> >
> >
> >
> > Von: Harbs
. Dezember 2020 um 13:32
An: dev@royale.apache.org
Betreff: AW: Release Step 003 Succeeded
Hi Harbs,
let me guess … you installed Maven via homebrew?
That would explain this behavior. I would expect the homebrew maven
installation to be directly tied to that particular Java version.
I think I never
directory on the path.
Chris
Von: Harbs
Datum: Mittwoch, 2. Dezember 2020 um 13:09
An: dev@royale.apache.org
Betreff: Re: Release Step 003 Succeeded
DIrectly.
Well, things get more and more interesting:
brew uninstall openjdk
Error: Refusing to uninstall /usr/local/Cellar/openjdk/13.0.2+8_2
gets selected (I don’t have JAVA_HOME set
> explicitly either)
>
> Chris
>
>
>
> Von: Harbs
> Datum: Dienstag, 1. Dezember 2020 um 19:28
> An: dev@royale.apache.org
> Betreff: Re: Release Step 003 Succeeded
> echo $JAVA_HOME returns an empty string, so I
: Harbs
Datum: Dienstag, 1. Dezember 2020 um 19:28
An: dev@royale.apache.org
Betreff: Re: Release Step 003 Succeeded
echo $JAVA_HOME returns an empty string, so I really don’t think JAVA_HOME is
playing a role. It could be MacBrew uses a symlink which Maven places as higher
priority than my system
; >
> > Von: Harbs mailto:harbs.li...@gmail.com>>
> > Datum: Dienstag, 1. Dezember 2020 um 13:45
> > An: dev@royale.apache.org <mailto:dev@royale.apache.org> <
> dev@royale.apache.org <mailto:dev@royale.apache.org>>
> > Betreff: Re: Release Step 003 Suc
>
>
> Von: Harbs mailto:harbs.li...@gmail.com>>
> Datum: Dienstag, 1. Dezember 2020 um 13:45
> An: dev@royale.apache.org <mailto:dev@royale.apache.org>
> mailto:dev@royale.apache.org>>
> Betreff: Re: Release Step 003 Succeeded
> I did some research.
>
@royale.apache.org
Betreff: Re: Release Step 003 Succeeded
I did some research.
I have Java 1.8 installed, but I also have openjdk 13 installed using MacBrew.
A fresh build of Maven (mvn clean install) on a fresh copy of the compiler repo
also seems to use version 13.
I guess I can probably
t;>>>
> >>>>> I don’t know why that would be. I’m on the release branch.
> >>>>>
> >>>>>> On Nov 27, 2020, at 1:03 AM, Alex Harui <mailto:aha...@adobe.com.INVALID>>
> >>>> wrote:
> >>>>>>
clean
>>>> install", it should allow you to type a response and then that machine
>>>> should be ok to use after that.
>>>>>>
>>>>>> -Alex
>>>>>>
>>>>>> On 11/26/20, 1:46 PM, "Harbs" >&g
ifacts on my machine?
>>>>>
>>>>>> On Nov 26, 2020, at 11:18 PM, Christofer Dutz <
>>> christofer.d...@c-ware.de> wrote:
>>>>>>
>>>>>> I can tell you what’s going on here.
>>>>>&g
?
And not necessarily all Java SDKs have to be in the same location … I for
example use sdkman to switch them and that puts them in a totally different
location.
Chris
Von: Harbs
Datum: Montag, 30. November 2020 um 11:05
An: dev@royale.apache.org
Betreff: Re: Release Step 003 Succeeded
Java version seems
n to the ant script
>>> doesn’t help.
>>>>>
>>>>> How would I manually get the Adobe artifacts on my machine?
>>>>>
>>>>>> On Nov 26, 2020, at 11:18 PM, Christofer Dutz <
>>> christofer.d...@c-ware.de> wrote:
&
26
An: dev@royale.apache.org
Betreff: Re: Release Step 003 Succeeded
The "snapshot" in the script output should just be checking if the release is
for jburg-types as well as the main jars (which it isn't).
The main pom.xml should not be using -SNAPSHOT for jburg-types and build-tools.
It see
Adobe artifacts on my machine?
>>>>
>>>>> On Nov 26, 2020, at 11:18 PM, Christofer Dutz <
>> christofer.d...@c-ware.de> wrote:
>>>>>
>>>>> I can tell you what’s going on here.
>>>>>
>>>>> You are building on a system where the Ad
How would I manually get the Adobe artifacts on my machine?
>>>>
>>>>> On Nov 26, 2020, at 11:18 PM, Christofer Dutz <
>> christofer.d...@c-ware.de> wrote:
>>>>>
>>>>> I can tell you what’s going on here.
>>>>>
>>>>> You are buildin
er (AKA maven extension I built to make non maven
> artifacts available as Maven artifacts) is kicking in. It expects a user to
> accept the license terms. It seems the MAC address of the network
> configuration of the build machine changed. You need to pass
> >>>
> >&
s of the network configuration of
>>> the build machine changed. You need to pass
>>>
>>> -Dcom.adobe.systemIdsForWhichTheTermsOfTheAdobeLicenseAgreementAreAccepted=b57aca16
>>>
>>> To the build job
>>>
>>> Chris
>>>
>>>
the
>> license terms. It seems the MAC address of the network configuration of the
>> build machine changed. You need to pass
>>
>> -Dcom.adobe.systemIdsForWhichTheTermsOfTheAdobeLicenseAgreementAreAccepted=b57aca16
>>
>> To the build job
>>
>> Ch
Hi Harbs,
If you want to, try to ping me when you try it the next time and I could try
assisting you via Zoom.
Chris
Von: Harbs
Datum: Freitag, 27. November 2020 um 11:07
An: Apache Royale Development
Betreff: Re: Release Step 003 Succeeded
It didn’t work for me…
I don’t know what Maven
the
>> license terms. It seems the MAC address of the network configuration of the
>> build machine changed. You need to pass
>>
>> -Dcom.adobe.systemIdsForWhichTheTermsOfTheAdobeLicenseAgreementAreAccepted=b57aca16
>>
>> To the build job
>>
>> Chris
>>
>>
>> Von: Harbs
>> Datu
uild machine changed. You need to pass
>
>
-Dcom.adobe.systemIdsForWhichTheTermsOfTheAdobeLicenseAgreementAreAccepted=b57aca16
>
> To the build job
>
> Chris
>
>
> Von: Harbs
> Datum: Donnerstag, 26. November 2020 um 21:53
> An: A
> configuration of the build machine changed. You need to pass
> >
> >
> -Dcom.adobe.systemIdsForWhichTheTermsOfTheAdobeLicenseAgreementAreAccepted=b57aca16
> >
> > To the build job
> >
> > Chris
> >
> >
> > Von: Harbs
> > Datum: Donnerstag,
configuration of the
> build machine changed. You need to pass
>
> -Dcom.adobe.systemIdsForWhichTheTermsOfTheAdobeLicenseAgreementAreAccepted=b57aca16
>
> To the build job
>
> Chris
>
>
> Von: Harbs
> Datum: Donnerstag, 26. November 2020 um 21:53
> An: Ap
Development
Betreff: Re: Release Step 003 Succeeded
I don’t get it. I’m getting an endless loop of:
[exec] The Adobe SDK license agreement applies to the Adobe Flash Player
playerglobal.swc. Do you want to install the Adobe Flash Player
playerglobal.swc?
[exec] (In a non-interactive build
I don’t get it. I’m getting an endless loop of:
[exec] The Adobe SDK license agreement applies to the Adobe Flash Player
playerglobal.swc. Do you want to install the Adobe Flash Player
playerglobal.swc?
[exec] (In a non-interactive build such as a CI server build,
alternatively to
>From the royale-compiler repo:
1. Run:
ant -f releasesteps.xml Release_Step_003 -Drelease.version=0.9.8
This will download the artifacts then unzip and compile the source artifact.
2. Validate that the compiled artifacts match the downloaded artifacts.
3. If they do, then run ant -f
Folder 1.2.1 created. Login to CI server. Change directory to
C:\jenkins\workspace\Royale_Compiler_Build_Tools_Release_Step_003 and run 'svn
commit -m "add version folder" -- username='. You will need your svn username
and password.
>From the royale-compiler repo:
1. Run:
ant -f releasesteps.xml Release_Step_003 -Drelease.version=0.9.7
This will download the artifacts then unzip and compile the source artifact.
2. Validate that the compiled artifacts match the downloaded artifacts.
3. If they do, then run ant -f
>From the royale-compiler repo:
1. Run:
ant -f releasesteps.xml Release_Step_003 -Drelease.version=0.9.7
This will download the artifacts then unzip and compile the source artifact.
2. Validate that the compiled artifacts match the downloaded artifacts.
3. If they do, then run ant -f
>From the royale-compiler repo:
1. Run:
ant -f releasesteps.xml Release_Step_003 -Drelease.version=0.9.7
This will download the artifacts then unzip and compile the source artifact.
2. Validate that the compiled artifacts match the downloaded artifacts.
3. If they do, then run ant -f
>From the royale-compiler repo:
1. Run:
ant -f releasesteps.xml Release_Step_003 -Drelease.version=0.9.7
This will download the artifacts then unzip and compile the source artifact.
2. Validate that the compiled artifacts match the downloaded artifacts.
3. If they do, then run ant -f
>From the royale-compiler repo:
1. Run:
ant -f releasesteps.xml Release_Step_003 -Drelease.version=0.9.7
This will download the artifacts then unzip and compile the source artifact.
2. Validate that the compiled artifacts match the downloaded artifacts.
3. If they do, then run ant -f
>From the royale-compiler repo:
1. Run:
ant -f releasesteps.xml Release_Step_003 -Drelease.version=0.9.7
This will download the artifacts then unzip and compile the source artifact.
2. Validate that the compiled artifacts match the downloaded artifacts.
3. If they do, then run ant -f
>From the royale-compiler repo:
1. Run:
ant -f releasesteps.xml Release_Step_003 -Drelease.version=0.9.7
This will download the artifacts then unzip and compile the source artifact.
2. Validate that the compiled artifacts match the downloaded artifacts.
3. If they do, then run ant -f
, April 13, 2020 10:15:59 PM
To: dev@royale.apache.org
Subject: Re: Royale Compiler Build Tools Release Step 003 Succeeded
The one from today looks ok. The one you quoted was from my practice runs over
the weekend which I fixed.
That folder does exist so step 003's message is correct. I think Step
v@royale.apache.org>
Subject: Royale Compiler Build Tools Release Step 003 Succeeded
ERROR: File 'email.txt' does not exist
ale Compiler Build Tools Release Step 003 Succeeded
ERROR: File 'email.txt' does not exist
Folder 1.2.0 already exists. Continue to next step.
>From the royale-compiler repo:
1. If you are releasing the utils jars (compiler-jburg-types and
compiler-build-tools) - you have set in previous step for mentioned projects
version ex. 1.1.0 not snapshot, run:
ant -f releasesteps.xml Release_Step_003 -Dutils=true -Drelease.version=0.9.7
Folder 1.2.0 already exists. Continue to next step.
>From the royale-compiler repo:
1. If you are releasing the utils jars (compiler-jburg-types and
compiler-build-tools) - you have set in previous step for mentioned projects
version ex. 1.1.0 not snapshot, run:
ant -f releasesteps.xml Release_Step_003 -Dutils=true -Drelease.version=0.9.7
>From the royale-compiler repo:
1. If you are releasing the utils jars (compiler-jburg-types and
compiler-build-tools) - you have set in previous step for mentioned projects
version ex. 1.1.0 not snapshot, run:
ant -f releasesteps.xml Release_Step_003 -Dutils=true -Drelease.version=0.9.7
>From the royale-compiler repo:
1. If you are releasing the utils jars (compiler-jburg-types and
compiler-build-tools) - you have set in previous step for mentioned projects
version ex. 1.1.0 not snapshot, run:
ant -f releasesteps.xml Release_Step_003 -Dutils=true -Drelease.version=0.9.7
>From the royale-compiler repo:
1. If you are releasing the utils jars (compiler-jburg-types and
compiler-build-tools) - you have set in previous step for mentioned projects
version ex. 1.1.0 not snapshot, run:
ant -f releasesteps.xml Release_Step_003 -Dutils=true -Drelease.version=0.9.7
>From the royale-compiler repo:
1. If you are releasing the utils jars (compiler-jburg-types and
compiler-build-tools) - you have set in previous step for mentioned projects
version ex. 1.1.0 not snapshot, run:
ant -f releasesteps.xml Release_Step_003 -Dutils=true -Drelease.version=0.9.7
>From the royale-compiler repo:
1. If you are releasing the utils jars (compiler-jburg-types and
compiler-build-tools) - you have set in previous step for mentioned projects
version ex. 1.1.0 not snapshot, run:
ant -f releasesteps.xml Release_Step_003 -Dutils=true -Drelease.version=0.9.7
>From the royale-compiler repo:
1. If you are releasing the utils jars (compiler-jburg-types and
compiler-build-tools) - you have set in previous step for mentioned projects
version ex. 1.1.0 not snapshot, run:
ant -f releasesteps.xml Release_Step_003 -Dutils=true -Drelease.version=0.9.7
>From the royale-compiler repo:
1. If you are releasing the utils jars (compiler-jburg-types and
compiler-build-tools) - you have set in previous step for mentioned projects
version ex. 1.1.0 not snapshot, run:
ant -f releasesteps.xml Release_Step_003 -Dutils=true -Drelease.version=0.9.7
>From the royale-compiler repo:
1. If you are releasing the utils jars (compiler-jburg-types and
compiler-build-tools) - you have set in previous step for mentioned projects
version ex. 1.1.0 not snapshot, run:
ant -f releasesteps.xml Release_Step_003 -Dutils=true -Drelease.version=0.9.7
>From the royale-compiler repo:
1. If you are releasing the utils jars (compiler-jburg-types and
compiler-build-tools) - you have set in previous step for mentioned projects
version ex. 1.1.0 not snapshot, run:
ant -f releasesteps.xml Release_Step_003 -Dutils=true -Drelease.version=0.9.7
>From the royale-compiler repo:
1. If you are releasing the utils jars (compiler-jburg-types and
compiler-build-tools) - you have set in previous step for mentioned projects
version ex. 1.1.0 not snapshot, Run:
ant -f releasesteps.xml Release_Step_003 -Dutils=true -Drelease.version=0.9.6
>From the royale-compiler repo:
1. If you are releasing the utils jars (compiler-jburg-types and
compiler-build-tools) - you have set in previous step for mentioned projects
version ex. 1.1.0 not snapshot, Run:
ant -f releasesteps.xml Release_Step_003 -Dutils=true -Drelease.version=0.9.6
>From the royale-compiler repo:
1. If you are releasing the utils jars (compiler-jburg-types and
compiler-build-tools) - you have set in previous step for mentioned projects
version ex. 1.1.0 not snapshot, Run:
ant -f releasesteps.xml Release_Step_003 -Dutils=true -Drelease.version=0.9.6
>From the royale-compiler repo:
1. If you are releasing the utils jars (compiler-jburg-types and
compiler-build-tools) - you have set in previous step for mentioned projects
version ex. 1.1.0 not snapshot, Run:
ant -f releasesteps.xml Release_Step_003 -Dutils=true -Drelease.version=0.9.6
>From the royale-compiler repo:
1. If you are releasing the utils jars (compiler-jburg-types and
compiler-build-tools) - you have set in previous step for mentioned projects
version ex. 1.1.0 not snapshot, Run:
ant -f releasesteps.xml Release_Step_003 -Dutils=true -Drelease.version=0.9.6
>From the royale-compiler repo:
1. If you are releasing the utils jars (compiler-jburg-types and
compiler-build-tools) - you have set in previous step for mentioned projects
version ex. 1.1.0 not snapshot, Run:
ant -f releasesteps.xml Release_Step_003 -Dutils=true -Drelease.version=0.9.6
>From the royale-compiler repo:
1. If you are releasing the utils jars (compiler-jburg-types and
compiler-build-tools) - you have set in previous step for mentioned projects
version ex. 1.1.0 not snapshot, Run:
ant -f releasesteps.xml Release_Step_003 -Dutils=true -Drelease.version=0.9.6
>From the royale-compiler repo:
1. If you are releasing the utils jars (compiler-jburg-types and
compiler-build-tools), Run:
ant -f releasesteps.xml Release_Step_003 -Dutils=true -Drelease.version=0.9.6
Otherwise, Run:
ant -f releasesteps.xml Release_Step_003 -Drelease.version=0.9.6
This will
>From the royale-compiler repo:
1. If you are releasing the utils jars (compiler-jburg-types and
compiler-build-tools), Run:
ant -f releasesteps.xml Release_Step_003 -Dutils=true -Drelease.version=0.9.6
Otherwise, Run:
ant -f releasesteps.xml Release_Step_003 -Drelease.version=0.9.6
This will
>From the royale-compiler repo:
1. If you are releasing the utils jars (compiler-jburg-types and
compiler-build-tools), Run:
ant -f releasesteps.xml Release_Step_003 -Dutils=true -Drelease.version=0.9.6
Otherwise, Run:
ant -f releasesteps.xml Release_Step_003 -Drelease.version=0.9.6
This will
>From the royale-compiler repo:
1. If you are releasing the utils jars (compiler-jburg-types and
compiler-build-tools), Run:
ant -f releasesteps.xml Release_Step_003 -Dutils=true -Drelease.version=0.9.6
Otherwise, Run:
ant -f releasesteps.xml Release_Step_003 -Drelease.version=0.9.6
This will
>From the royale-compiler repo:
1. If you are releasing the utils jars (compiler-jburg-types and
compiler-build-tools), Run:
ant -f releasesteps.xml Release_Step_003 -Dutils=true -Drelease.version=0.9.6
Otherwise, Run:
ant -f releasesteps.xml Release_Step_003 -Drelease.version=0.9.6
This will
>From the royale-compiler repo:
1. If you are releasing the utils jars (compiler-jburg-types and
compiler-build-tools), Run:
ant -f releasesteps.xml Release_Step_003 -Dutils=true -Drelease.version=0.9.6
Otherwise, Run:
ant -f releasesteps.xml Release_Step_003 -Drelease.version=0.9.6
This will
>From the royale-compiler repo:
1. If you are releasing the utils jars (compiler-jburg-types and
compiler-build-tools), Run:
ant -f releasesteps.xml Release_Step_003 -Dutils=true -Drelease.version=0.9.6
Otherwise, Run:
ant -f releasesteps.xml Release_Step_003 -Drelease.version=0.9.6
This will
0. From the royale-compiler repo:
1. If you are releasing the utils jars (compiler-jburg-types and
compiler-build-tools), Run:
ant -f releasesteps.xml Release_Step_003 -Dutils=true -Drelease.version=0.9.6
Otherwise, Run:
ant -f releasesteps.xml Release_Step_003 -Drelease.version=0.9.6
This
1. If you are releasing the utils jars (compiler-jburg-types and
compiler-build-tools), Run:
ant -f releasesteps.xml Release_Step_003 -Dutils=true -Drelease.version=0.9.6
Otherwise, Run:
ant -f releasesteps.xml Release_Step_003 -Drelease.version=0.9.6
This will download the artifacts then
1. If you are releasing the utils jars (compiler-jburg-types and
compiler-build-tools), Run:
ant -f releasesteps.xml Release_Step_003 -Dutils=true -Drelease.version=0.9.6
Otherwise, Run:
ant -f releasesteps.xml Release_Step_003 -Drelease.version=0.9.6
This will download the artifacts then
1. If you are releasing the utils jars (compiler-jburg-types and
compiler-build-tools), Run:
ant -f releasesteps.xml Release_Step_003 -Dutils=true -Drelease.version=0.9.6
Otherwise, Run:
ant -f releasesteps.xml Release_Step_003 -Drelease.version=0.9.6
This will download the artifacts then
1. If you are releasing the utils jars (compiler-jburg-types and
compiler-build-tools), Run:
ant -f releasesteps.xml Release_Step_003 -Dutils=true -Drelease.version=0.9.6
Otherwise, Run:
ant -f releasesteps.xml Release_Step_003 -Drelease.version=0.9.6
This will download the artifacts then
1. If you are releasing the utils jars (compiler-jburg-types and
compiler-build-tools), Run:
ant -f releasesteps.xml Release_Step_003 -Dutils=true -Drelease.version=0.9.6
Otherwise, Run:
ant -f releasesteps.xml Release_Step_003 -Drelease.version=0.9.6
This will download the artifacts then
1. Run ant -f releasesteps.xml Release_Step_003 -Drelease.version=0.9.6
This will download the artifacts then unzip and compile the source artifact.
2. Validate that the compiled artifacts match the downloaded artifacts.
3. If they do, then run ant -f releasesteps.xml Release_Step_003_Sign
1 - 100 of 102 matches
Mail list logo
