Re: Release Step 003 Succeeded

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

Re: Release Step 003 Succeeded

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 >>

Re: Release Step 003 Succeeded

> 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

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 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

Re: Release Step 003 Succeeded

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

Re: Release Step 003 Succeeded

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

Re: Release Step 003 Succeeded

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

Re: Release Step 003 Succeeded

t;> >>>> Hi Harbs, >>>> >>>> Are you running the maven build directly/manually? Or is this triggered >>> by an IDE or Ant script? >>>> Cause I usually run most of my builds in IntelliJ and there I simply >>> select the JDK

Re: Release Step 003 Succeeded

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 >>> >>>

Re: Release Step 003 Succeeded

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 >&

Re: Release Step 003 Succeeded

it and sticking the bin 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: > >

Re: Release Step 003 Succeeded

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

Re: Release Step 003 Succeeded

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

Re: Release Step 003 Succeeded

; > > > 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

Re: Release Step 003 Succeeded

> > > 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. >

Re: Release Step 003 Succeeded

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: > >>>>>>

Re: Release Step 003 Succeeded

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

Re: Release Step 003 Succeeded

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

Re: Release Step 003 Succeeded

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: &

Re: Release Step 003 Succeeded

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

Re: Release Step 003 Succeeded

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

Re: Release Step 003 Succeeded

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

Re: Release Step 003 Succeeded

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 > >>> > >&

Re: Release Step 003 Succeeded

s of the network configuration of >>> the build machine changed. You need to pass >>> >>> -Dcom.adobe.systemIdsForWhichTheTermsOfTheAdobeLicenseAgreementAreAccepted=b57aca16 >>> >>> To the build job >>> >>> Chris >>> >>>

Re: Release Step 003 Succeeded

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

Re: Release Step 003 Succeeded

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

Re: Release Step 003 Succeeded

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

Re: Release Step 003 Succeeded

> configuration of the build machine changed. You need to pass > > > > > -Dcom.adobe.systemIdsForWhichTheTermsOfTheAdobeLicenseAgreementAreAccepted=b57aca16 > > > > To the build job > > > > Chris > > > > > > Von: Harbs > > Datum: Donnerstag,

Re: Release Step 003 Succeeded

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

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 such as a CI server build, alternatively to