Re: [DISCUSS] Discuss Release Apache Royale 0.9.4 RC2

[Justin Mclean]

Hi,

Re the modified non binary inclusion of CC BY-SA 3.0 licensed content I’ve 
asked on legal discuss as the resolved answered asks to do. [1]

Thanks,
Justin

1. https://www.apache.org/legal/resolved.html#cc-sa

Re: Lets talk a bit about the release process (was Re: [DISCUSS] Discuss Release Apache Royale 0.9.4 RC2)

[Carlos Rovira]

Hi Om,

(again talking from my no experience in the process), can this be the
problem that make RMs fail on the process? From the external point of a
viewer, this seems more related to scripting/manual issues. Normally Maven
steps are hard to get working, but once you got it, use to work for all
people. It seems to me like a more "industrial" process that should ensure
independence of platform and custom configurations.

Thanks for sharing

Carlos


El jue., 15 nov. 2018 a las 7:36, OmPrakash Muppirala ()
escribió:

> Personally, I am not sure why we are uploading stuff to maven central as
> part of the RC process.  Can we simply bundle the source files and create a
> release candidate?  Folks who want to test maven can run the maven scripts
> locally which would copy stuff to the local .m2 repo instead.
> That way we dont force maven on folks who dont need it.
>
> Thoughts?
>
> Thanks,
> Om
>
>
>
> On Wed, Nov 14, 2018 at 12:54 PM Carlos Rovira 
> wrote:
>
> > Hi Alex,
> >
> > first congrats to reach to this point. After many months is great to
> > finally can release :)
> >
> > I forked the thread to avoid mixing topics and let the discuss thread to
> > just discuss the RC2
> >
> > I'll try RC2 soon, but first I want to talk about the inherent problem. I
> > know we are all here making a huge effort to make Royale work and shine,
> > and be release manager is to spend many hours working in that task, so
> > first I want to express as well a huge recognition to all RMs that tried
> to
> > make this happen before you. I still didn't try to make myself a release,
> > so I'm talking without the knowledge you all guys have, so sorry if I say
> > something inconvenient now, but just want to talk about the elephant in
> the
> > room, so we can improve the process from now own.
> >
> > My perception, from a person that is still outside the release process,
> > still does not have all the knowledge and never was a RM is that the
> > process is not reliable. Again hope nobody feels that talk about this is
> > any kind of attack, just that if we agree on that, we could try to
> improve
> > for the better. Right now seems that only Alex can make a release happen
> > due to his machine configuration. I assume all RMs execute the RM
> > instructions, so the problem is not related to the instructions, but
> seems
> > more to the nature of how we build.
> >
> > So, my question is, what we could change to ensure scripts and process
> are
> > reliable in all machines and doable by any of us?
> > Is the process a mix of maven and ant what is making this so hard to do?
> > Just a comment, could be the nature of ant (more single separated
> scripting
> > based on computer environment config vs structured building based on
> > building framework and servers) a problem?
> >
> > I want to be a RM soon (hope to be available for this task around Feb-Mar
> > 2019), so its clear I still can say a word about the process just start
> > this thread and hoping no one feels this as an attack (since I recognize
> > the huge effort done to reach this point), but just a way to start trying
> > to think with open mind and see that we have at least a thing to solve so
> > any of us can make the same as Alex do
> >
> > Thanks in advance for your thoughts :)
> >
> > Carlos
> >
> >
> >
> >
> >
> > El mié., 14 nov. 2018 a las 19:46, Alex Harui ()
> > escribió:
> >
> > > This is the discussion thread.   RC1 was never put up for vote because
> > > there
> > > were issues with the notice files and build scripts when running from
> the
> > > packages and not the repo.
> > >
> > > Interestingly, the scripts ran just fine for me on my home Windows
> > > computer.
> > > I did not have the problems Om, Piotr, and Yishay had when uploading or
> > > downloading Maven artifacts.  Except when I tried watching videos while
> > > waiting for the scripts to run (the "maven" target takes 2 hours in
> > > Powershell, the "main" target took over an hour).   Then I would see
> > > uploads
> > > "hang".   So I would recommend to any future RMs to try to make sure
> the
> > > network is not otherwise too busy when running these scripts.
> > >
> > > Changes in this RC include:
> > >
> > >
> > >
> > > Thanks,
> > > Alex Harui
> > >
> > >
> >
> > --
> > Carlos Rovira
> > http://about.me/carlosrovira
> >
>


-- 
Carlos Rovira
http://about.me/carlosrovira

Re: Lets talk a bit about the release process (was Re: [DISCUSS] Discuss Release Apache Royale 0.9.4 RC2)

[OmPrakash Muppirala]

Personally, I am not sure why we are uploading stuff to maven central as
part of the RC process.  Can we simply bundle the source files and create a
release candidate?  Folks who want to test maven can run the maven scripts
locally which would copy stuff to the local .m2 repo instead.
That way we dont force maven on folks who dont need it.

Thoughts?

Thanks,
Om



On Wed, Nov 14, 2018 at 12:54 PM Carlos Rovira 
wrote:

> Hi Alex,
>
> first congrats to reach to this point. After many months is great to
> finally can release :)
>
> I forked the thread to avoid mixing topics and let the discuss thread to
> just discuss the RC2
>
> I'll try RC2 soon, but first I want to talk about the inherent problem. I
> know we are all here making a huge effort to make Royale work and shine,
> and be release manager is to spend many hours working in that task, so
> first I want to express as well a huge recognition to all RMs that tried to
> make this happen before you. I still didn't try to make myself a release,
> so I'm talking without the knowledge you all guys have, so sorry if I say
> something inconvenient now, but just want to talk about the elephant in the
> room, so we can improve the process from now own.
>
> My perception, from a person that is still outside the release process,
> still does not have all the knowledge and never was a RM is that the
> process is not reliable. Again hope nobody feels that talk about this is
> any kind of attack, just that if we agree on that, we could try to improve
> for the better. Right now seems that only Alex can make a release happen
> due to his machine configuration. I assume all RMs execute the RM
> instructions, so the problem is not related to the instructions, but seems
> more to the nature of how we build.
>
> So, my question is, what we could change to ensure scripts and process are
> reliable in all machines and doable by any of us?
> Is the process a mix of maven and ant what is making this so hard to do?
> Just a comment, could be the nature of ant (more single separated scripting
> based on computer environment config vs structured building based on
> building framework and servers) a problem?
>
> I want to be a RM soon (hope to be available for this task around Feb-Mar
> 2019), so its clear I still can say a word about the process just start
> this thread and hoping no one feels this as an attack (since I recognize
> the huge effort done to reach this point), but just a way to start trying
> to think with open mind and see that we have at least a thing to solve so
> any of us can make the same as Alex do
>
> Thanks in advance for your thoughts :)
>
> Carlos
>
>
>
>
>
> El mié., 14 nov. 2018 a las 19:46, Alex Harui ()
> escribió:
>
> > This is the discussion thread.   RC1 was never put up for vote because
> > there
> > were issues with the notice files and build scripts when running from the
> > packages and not the repo.
> >
> > Interestingly, the scripts ran just fine for me on my home Windows
> > computer.
> > I did not have the problems Om, Piotr, and Yishay had when uploading or
> > downloading Maven artifacts.  Except when I tried watching videos while
> > waiting for the scripts to run (the "maven" target takes 2 hours in
> > Powershell, the "main" target took over an hour).   Then I would see
> > uploads
> > "hang".   So I would recommend to any future RMs to try to make sure the
> > network is not otherwise too busy when running these scripts.
> >
> > Changes in this RC include:
> >
> >
> >
> > Thanks,
> > Alex Harui
> >
> >
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>

Build failed in Jenkins: royale-asjs_MXTests #139

[apacheroyaleci]

See 


--
[...truncated 2.27 MB...]
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\core\IPanelModel.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\effects\IEffect.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\mx\events\CollectionEventKind.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\core\AllCSSStyles.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\mx\collections\ArrayCollection.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\core\IDataGridModel.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\html\beads\models\DataGridModel.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\utils\IBinaryDataInput.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\reflection\MetaDataDefinition.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\html\beads\ISpinnerView.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\html\beads\SpinnerView.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\core\IViewportModel.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\core\WrappedHTMLElement.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\spark\layouts\supportClasses\DropLocation.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\core\layout\LayoutData.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\mx\collections\errors\CursorError.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\mx\styles\CSSStyleDeclaration.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\core\IItemRendererParent.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\html\beads\DataContainerView.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\reflection\MethodDefinition.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\mx\display\Graphics.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\mx\core\ScrollControlBase.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\mx\controls\listClasses\ListBase.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\binding\WatcherBase.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\core\IImage.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\events\BrowserEvent.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\html\beads\models\PanelModel.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\mx\containers\beads\models\PanelModel.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\core\IPopUp.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\halo\scripts\ButtonTestScript.js
[mxmlc] us

Re: [VOTE] Release Apache Royale 0.9.4 RC2

[Alex Harui]

Because coming in now with possible issues is disruptive to the community.  If 
you want to help us, you would watch the commits.

The source for this text is Wikipedia, which is not a software provider.

I think we're good for now.  If we do another RC for a real reason, we'll pull 
these files as they aren't critical.

-Alex

On 11/14/18, 6:09 PM, "Justin Mclean"  wrote:

Hi,

Text is not media (media as defined in that thread is images, audio or
video) and it's been modified.

Why would I be closely watching the commits when I'm not a committer or PMC
member?

Probably best to continue this in the discussion thread.

Thanks,
Justin

On Thu., 15 Nov. 2018, 12:55 pm Alex Harui  It isn't code, it is text media.
>
> Thanks for trying though.  Remember, you are supposed to be watching the
> commits, not the vote threads.
>
> -Alex
>
> On 11/14/18, 5:47 PM, "Justin Mclean"  wrote:
>
> Hi,
>
> -1 (non-binding)
>
> The release includes CC-SA licensed content [1] which is not
> unmodified media [2].
>
> I know this content [1] was copied from TourDeFlex in the Flex project
> so it may also have an issue. It looks like policy has changed (or been
> clarified) since the last TourDeFlex release in 2014, for instance see the
> discussion here [3] in 2017. Note the draft email in that discussion
> clarifying inclusion of CC licensed content, but I cannot recall if it was
> sent out to all PMCs.
>
> Thanks,
> Justin
>
> 1. ./royale-asjs/examples/mxroyale/tourdeflexmodules/src/apache/
> 2.
> 
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Flegal%2Fresolved.html%23cc-sa&data=02%7C01%7Caharui%40adobe.com%7C5978c8df10824a4fc8f108d64a9f6fb9%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636778445992506299&sdata=d9QTyVLz%2BBNDBg0dVV3sDAUQOIHvZVMpbAq5L5o3f1I%3D&reserved=0
> 3.
> 
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread.html%2F46b628e47e2461834066835ff7d696b2a55e00cf81a98b4daed444f0%40%253Clegal-discuss.apache.org%253E&data=02%7C01%7Caharui%40adobe.com%7C5978c8df10824a4fc8f108d64a9f6fb9%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636778445992516304&sdata=pE58FF9bA55LYOgQAlqlY1PoFZiMI4l98yXEJCwVoWw%3D&reserved=0
>
>

Re: [VOTE] Release Apache Royale 0.9.4 RC2

[Justin Mclean]

Hi,

Text is not media (media as defined in that thread is images, audio or
video) and it's been modified.

Why would I be closely watching the commits when I'm not a committer or PMC
member?

Probably best to continue this in the discussion thread.

Thanks,
Justin

On Thu., 15 Nov. 2018, 12:55 pm Alex Harui  It isn't code, it is text media.
>
> Thanks for trying though.  Remember, you are supposed to be watching the
> commits, not the vote threads.
>
> -Alex
>
> On 11/14/18, 5:47 PM, "Justin Mclean"  wrote:
>
> Hi,
>
> -1 (non-binding)
>
> The release includes CC-SA licensed content [1] which is not
> unmodified media [2].
>
> I know this content [1] was copied from TourDeFlex in the Flex project
> so it may also have an issue. It looks like policy has changed (or been
> clarified) since the last TourDeFlex release in 2014, for instance see the
> discussion here [3] in 2017. Note the draft email in that discussion
> clarifying inclusion of CC licensed content, but I cannot recall if it was
> sent out to all PMCs.
>
> Thanks,
> Justin
>
> 1. ./royale-asjs/examples/mxroyale/tourdeflexmodules/src/apache/
> 2.
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Flegal%2Fresolved.html%23cc-sa&data=02%7C01%7Caharui%40adobe.com%7Cd5290b347b224c81627808d64a9c4924%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636778432440457156&sdata=x1RJCKF5WNuL%2FFgr02NPgDtlZ4fGahROEmm3sK29pbc%3D&reserved=0
> 3.
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread.html%2F46b628e47e2461834066835ff7d696b2a55e00cf81a98b4daed444f0%40%253Clegal-discuss.apache.org%253E&data=02%7C01%7Caharui%40adobe.com%7Cd5290b347b224c81627808d64a9c4924%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636778432440457156&sdata=iaewUj%2BZ4%2F3J8mubTYeASR4jAwIjQIVQSeYFJjcGL%2FY%3D&reserved=0
>
>

Re: [VOTE] Release Apache Royale 0.9.4 RC2

[Alex Harui]

It isn't code, it is text media.

Thanks for trying though.  Remember, you are supposed to be watching the 
commits, not the vote threads.

-Alex

On 11/14/18, 5:47 PM, "Justin Mclean"  wrote:

Hi,

-1 (non-binding)

The release includes CC-SA licensed content [1] which is not unmodified 
media [2].

I know this content [1] was copied from TourDeFlex in the Flex project so 
it may also have an issue. It looks like policy has changed (or been clarified) 
since the last TourDeFlex release in 2014, for instance see the discussion here 
[3] in 2017. Note the draft email in that discussion clarifying inclusion of CC 
licensed content, but I cannot recall if it was sent out to all PMCs.

Thanks,
Justin

1. ./royale-asjs/examples/mxroyale/tourdeflexmodules/src/apache/
2. 
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Flegal%2Fresolved.html%23cc-sa&data=02%7C01%7Caharui%40adobe.com%7Cd5290b347b224c81627808d64a9c4924%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636778432440457156&sdata=x1RJCKF5WNuL%2FFgr02NPgDtlZ4fGahROEmm3sK29pbc%3D&reserved=0
3. 
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread.html%2F46b628e47e2461834066835ff7d696b2a55e00cf81a98b4daed444f0%40%253Clegal-discuss.apache.org%253E&data=02%7C01%7Caharui%40adobe.com%7Cd5290b347b224c81627808d64a9c4924%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636778432440457156&sdata=iaewUj%2BZ4%2F3J8mubTYeASR4jAwIjQIVQSeYFJjcGL%2FY%3D&reserved=0

Re: [VOTE] Release Apache Royale 0.9.4 RC2

[Justin Mclean]

Hi,

-1 (non-binding)

The release includes CC-SA licensed content [1] which is not unmodified media 
[2].

I know this content [1] was copied from TourDeFlex in the Flex project so it 
may also have an issue. It looks like policy has changed (or been clarified) 
since the last TourDeFlex release in 2014, for instance see the discussion here 
[3] in 2017. Note the draft email in that discussion clarifying inclusion of CC 
licensed content, but I cannot recall if it was sent out to all PMCs.

Thanks,
Justin

1. ./royale-asjs/examples/mxroyale/tourdeflexmodules/src/apache/
2. https://www.apache.org/legal/resolved.html#cc-sa
3. 
https://lists.apache.org/thread.html/46b628e47e2461834066835ff7d696b2a55e00cf81a98b4daed444f0@%3Clegal-discuss.apache.org%3E

Build failed in Jenkins: royale-asjs_MXTests #138

[apacheroyaleci]

See 


--
[...truncated 2.27 MB...]
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\core\IPanelModel.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\effects\IEffect.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\mx\events\CollectionEventKind.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\core\AllCSSStyles.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\mx\collections\ArrayCollection.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\core\IDataGridModel.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\html\beads\models\DataGridModel.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\utils\IBinaryDataInput.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\reflection\MetaDataDefinition.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\html\beads\ISpinnerView.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\html\beads\SpinnerView.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\core\IViewportModel.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\core\WrappedHTMLElement.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\spark\layouts\supportClasses\DropLocation.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\core\layout\LayoutData.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\mx\collections\errors\CursorError.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\mx\styles\CSSStyleDeclaration.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\core\IItemRendererParent.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\html\beads\DataContainerView.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\reflection\MethodDefinition.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\mx\display\Graphics.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\mx\core\ScrollControlBase.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\mx\controls\listClasses\ListBase.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\binding\WatcherBase.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\core\IImage.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\events\BrowserEvent.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\html\beads\models\PanelModel.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\mx\containers\beads\models\PanelModel.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\core\IPopUp.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\halo\scripts\ButtonTestScript.js
[mxmlc] us

Build failed in Jenkins: royale-asjs_MXTests #137

[apacheroyaleci]

See 


Changes:

[serkan.tas] removed duplicate definition

[serkan.tas] added TabBar

[serkan.tas] added module class

[serkan.tas] added module class

[noreply] Update spark-royale-manifest.xml

[UKINANFR] Switching from using a new HTTPStatusEvent to a ValueEvent, now with 
the

[serkan.tas] emulation works

[serkan.tas] it was not required

[serkan.tas] removed weak reference

[serkan.tas] removed unnecessary class

[serkan.tas] accidentally deleted, restored

[serkan.tas] Menu class emulated

[greg.dove] Small fix for external model adjustment

--
[...truncated 2.27 MB...]
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\core\IPanelModel.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\effects\IEffect.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\mx\events\CollectionEventKind.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\core\AllCSSStyles.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\mx\collections\ArrayCollection.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\core\IDataGridModel.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\html\beads\models\DataGridModel.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\utils\IBinaryDataInput.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\reflection\MetaDataDefinition.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\html\beads\ISpinnerView.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\html\beads\SpinnerView.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\core\IViewportModel.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\core\WrappedHTMLElement.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\spark\layouts\supportClasses\DropLocation.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\core\layout\LayoutData.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\mx\collections\errors\CursorError.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\mx\styles\CSSStyleDeclaration.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\core\IItemRendererParent.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\html\beads\DataContainerView.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\reflection\MethodDefinition.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\mx\display\Graphics.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\mx\core\ScrollControlBase.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\mx\controls\listClasses\ListBase.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\binding\WatcherBase.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\core\IImage.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\events\BrowserEvent.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\m

Jenkins build is back to normal : royale-asjs_jsonly #1884

[apacheroyaleci]

See 

Build failed in Jenkins: royale-asjs_MXTests #136

[apacheroyaleci]

See 


Changes:

[carlosrovira] some improvements in section and grid layout

[carlosrovira] New Jewel Wizard component

[carlosrovira] Jewel Wizard initial example in JewelExample

--
[...truncated 2.26 MB...]
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\core\IPanelModel.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\effects\IEffect.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\mx\events\CollectionEventKind.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\core\AllCSSStyles.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\mx\collections\ArrayCollection.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\core\IDataGridModel.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\html\beads\models\DataGridModel.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\utils\IBinaryDataInput.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\reflection\MetaDataDefinition.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\html\beads\ISpinnerView.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\html\beads\SpinnerView.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\core\IViewportModel.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\core\WrappedHTMLElement.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\spark\layouts\supportClasses\DropLocation.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\core\layout\LayoutData.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\mx\collections\errors\CursorError.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\mx\styles\CSSStyleDeclaration.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\core\IItemRendererParent.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\html\beads\DataContainerView.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\reflection\MethodDefinition.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\mx\display\Graphics.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\mx\core\ScrollControlBase.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\mx\controls\listClasses\ListBase.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\binding\WatcherBase.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\core\IImage.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\events\BrowserEvent.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\html\beads\models\PanelModel.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\mx\containers\beads\models\PanelModel.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\r

Re: Getting An Emulation Component To Run

[Carlos Rovira]

ok, I must say that always think is just how it works. Didn't try to build
and example without to first build examples. I'll try as I have time and
report

thanks

El mié., 14 nov. 2018 a las 21:41, Piotr Zarzycki (<
piotrzarzyck...@gmail.com>) escribió:

> Carlos,
>
> When I as a user pickup examples and try to build by Maven I shouldn't need
> build myself sources at all Royale framework. All artifacts should be
> downloadable from Maven central - Dev or release. They are available. If
> she is failing doing that, we may have a problem. Remove everything from
> your cache some day and try to build example - If it's not working -
> solution is definitely not building whole repo on it's own.
>
> That's why I have asked.
>
> Thanks,
> Piotr
>
> śr., 14 lis 2018 o 21:30 Carlos Rovira 
> napisał(a):
>
> > Piotr,
> >
> > about why I suggest try to build that, I think Alina is yet in the point
> > where she does't get build Royale compiler, typedefs and framework with
> > maven, so she needs to get that first, then build "examples" folder with
> > "mvn clean install"
> >
> >
> >
> > El mié., 14 nov. 2018 a las 21:27, Carlos Rovira (<
> carlosrov...@apache.org
> > >)
> > escribió:
> >
> > > Hi Piotr,
> > >
> > > I thank after that she needs to run maven on examples folder, that will
> > > build all examples including AMF client and then the server, that uses
> > the
> > > client. One important thing to take into account is that since we have
> > > various RO implementations, the java example has in the pom different
> > > configs that are commented, one for MX RO and one for NET RO. Since
> Alina
> > > wants to try MX RO she needs to comment NET and uncomment MX so maven
> > > overlay that client in the java war.
> > >
> > >
> > >
> > > El mié., 14 nov. 2018 a las 16:26, Piotr Zarzycki (<
> > > piotrzarzyck...@gmail.com>) escribió:
> > >
> > >> Hi Carlos,
> > >>
> > >> Why repository need to be build if we want to build example only ? I'm
> > >> curious why you suggesting that ?
> > >>
> > >> Piotr
> > >>
> > >> śr., 14 lis 2018 o 16:23 Carlos Rovira 
> > >> napisał(a):
> > >>
> > >> > Hi Alina,
> > >> >
> > >> > I have the following script in the folder that parent the three repo
> > >> > (compiler, typedefs and asjs). This script (for Mac but if you use
> > >> windows
> > >> > can adapt easily) updates from git the there repos, then build each
> > repo
> > >> > with maven and build the SDK in the same repo (and before all of
> that
> > >> > cleans ant files in each repo). So I just one execution I have all
> > >> build:
> > >> >
> > >> > #!/bin/bash
> > >> > cd $ROYALE_COMPILER_HOME
> > >> > git pull -v --progress "origin"
> > >> > echo Royale Compiler updated from repo
> > >> >
> > >> > cd $ROYALE_TYPEDEFS_HOME
> > >> > git pull -v --progress "origin"
> > >> > echo Royale TypeDefs  updated from repo
> > >> >
> > >> > cd $ROYALE_HOME
> > >> > git pull -v --progress "origin"
> > >> > echo Royale AsJs  updated from repo
> > >> >
> > >> > #set JAVA_TOOL_OPTIONS=-Dfile.encoding=UTF-8 -Xmx1024m
> > >> > cd $ROYALE_COMPILER_HOME
> > >> > mvn clean install -DskipTests
> > >> > echo Royale Compiler built with Maven
> > >> >
> > >> > cd $ROYALE_TYPEDEFS_HOME
> > >> > ant wipe
> > >> > mvn clean install
> > >> > echo Royale TypeDefs built with Maven
> > >> >
> > >> > cd $ROYALE_HOME
> > >> > ant super-clean
> > >> > mvn clean install -DskipTests
> > >> > #-Drat.skip=true
> > >> > echo Royale AsJs built with Maven
> > >> >
> > >> > ant all -Dbuild.noprompt=true -Drelease.target=true
> > >> > echo Royale SDK built with Ant
> > >> >
> > >> >
> > >> > if this not works for you, you must to check your environment vars
> and
> > >> the
> > >> > rest of configuration to check where things are going wrong.
> > >> >
> > >> > HTH,
> > >> >
> > >> > Carlos
> > >> >
> > >> >
> > >> >
> > >> >
> > >> > El mié., 14 nov. 2018 a las 13:15, Alina Kazi ( >)
> > >> > escribió:
> > >> >
> > >> > > Hi Carlos,
> > >> > >
> > >> > > It's not first time I try to run maven. I run that last year with
> > >> > > successful build.
> > >> > > But after that I started to work using ant.
> > >> > > Now, I need maven to run this example:
> > >> > >
> > >> > >
> > >> >
> > >>
> >
> https://github.com/apache/royale-asjs/tree/develop/examples/amf/SampleAmfWebApp
> > >> > >
> > >> > > Thanks,
> > >> > > Alina
> > >> > >
> > >> > > -Original Message-
> > >> > > From: Carlos Rovira [mailto:carlosrov...@apache.org]
> > >> > > Sent: Wednesday, November 14, 2018 4:46 PM
> > >> > > To: dev@royale.apache.org
> > >> > > Subject: Re: Getting An Emulation Component To Run
> > >> > >
> > >> > > Hi Alina, is the first time you run try maven? until now you was
> > using
> > >> > ant?
> > >> > >
> > >> > >
> > >> > > El mié., 14 nov. 2018 a las 12:24, Alina Kazi (<
> alina.k...@d-bz.com
> > >)
> > >> > > escribió:
> > >> > >
> > >> > > >
> > >> > > > Both of you suggest me to run the existing Apache Royale
> > >> RemoteObject
> > >> > > > Example.
> > >> > > > 

Lets talk a bit about the release process (was Re: [DISCUSS] Discuss Release Apache Royale 0.9.4 RC2)

[Carlos Rovira]

Hi Alex,

first congrats to reach to this point. After many months is great to
finally can release :)

I forked the thread to avoid mixing topics and let the discuss thread to
just discuss the RC2

I'll try RC2 soon, but first I want to talk about the inherent problem. I
know we are all here making a huge effort to make Royale work and shine,
and be release manager is to spend many hours working in that task, so
first I want to express as well a huge recognition to all RMs that tried to
make this happen before you. I still didn't try to make myself a release,
so I'm talking without the knowledge you all guys have, so sorry if I say
something inconvenient now, but just want to talk about the elephant in the
room, so we can improve the process from now own.

My perception, from a person that is still outside the release process,
still does not have all the knowledge and never was a RM is that the
process is not reliable. Again hope nobody feels that talk about this is
any kind of attack, just that if we agree on that, we could try to improve
for the better. Right now seems that only Alex can make a release happen
due to his machine configuration. I assume all RMs execute the RM
instructions, so the problem is not related to the instructions, but seems
more to the nature of how we build.

So, my question is, what we could change to ensure scripts and process are
reliable in all machines and doable by any of us?
Is the process a mix of maven and ant what is making this so hard to do?
Just a comment, could be the nature of ant (more single separated scripting
based on computer environment config vs structured building based on
building framework and servers) a problem?

I want to be a RM soon (hope to be available for this task around Feb-Mar
2019), so its clear I still can say a word about the process just start
this thread and hoping no one feels this as an attack (since I recognize
the huge effort done to reach this point), but just a way to start trying
to think with open mind and see that we have at least a thing to solve so
any of us can make the same as Alex do

Thanks in advance for your thoughts :)

Carlos





El mié., 14 nov. 2018 a las 19:46, Alex Harui ()
escribió:

> This is the discussion thread.   RC1 was never put up for vote because
> there
> were issues with the notice files and build scripts when running from the
> packages and not the repo.
>
> Interestingly, the scripts ran just fine for me on my home Windows
> computer.
> I did not have the problems Om, Piotr, and Yishay had when uploading or
> downloading Maven artifacts.  Except when I tried watching videos while
> waiting for the scripts to run (the "maven" target takes 2 hours in
> Powershell, the "main" target took over an hour).   Then I would see
> uploads
> "hang".   So I would recommend to any future RMs to try to make sure the
> network is not otherwise too busy when running these scripts.
>
> Changes in this RC include:
>
>
>
> Thanks,
> Alex Harui
>
>

-- 
Carlos Rovira
http://about.me/carlosrovira

Re: Getting An Emulation Component To Run

[Piotr Zarzycki]

Carlos,

When I as a user pickup examples and try to build by Maven I shouldn't need
build myself sources at all Royale framework. All artifacts should be
downloadable from Maven central - Dev or release. They are available. If
she is failing doing that, we may have a problem. Remove everything from
your cache some day and try to build example - If it's not working -
solution is definitely not building whole repo on it's own.

That's why I have asked.

Thanks,
Piotr

śr., 14 lis 2018 o 21:30 Carlos Rovira  napisał(a):

> Piotr,
>
> about why I suggest try to build that, I think Alina is yet in the point
> where she does't get build Royale compiler, typedefs and framework with
> maven, so she needs to get that first, then build "examples" folder with
> "mvn clean install"
>
>
>
> El mié., 14 nov. 2018 a las 21:27, Carlos Rovira ( >)
> escribió:
>
> > Hi Piotr,
> >
> > I thank after that she needs to run maven on examples folder, that will
> > build all examples including AMF client and then the server, that uses
> the
> > client. One important thing to take into account is that since we have
> > various RO implementations, the java example has in the pom different
> > configs that are commented, one for MX RO and one for NET RO. Since Alina
> > wants to try MX RO she needs to comment NET and uncomment MX so maven
> > overlay that client in the java war.
> >
> >
> >
> > El mié., 14 nov. 2018 a las 16:26, Piotr Zarzycki (<
> > piotrzarzyck...@gmail.com>) escribió:
> >
> >> Hi Carlos,
> >>
> >> Why repository need to be build if we want to build example only ? I'm
> >> curious why you suggesting that ?
> >>
> >> Piotr
> >>
> >> śr., 14 lis 2018 o 16:23 Carlos Rovira 
> >> napisał(a):
> >>
> >> > Hi Alina,
> >> >
> >> > I have the following script in the folder that parent the three repo
> >> > (compiler, typedefs and asjs). This script (for Mac but if you use
> >> windows
> >> > can adapt easily) updates from git the there repos, then build each
> repo
> >> > with maven and build the SDK in the same repo (and before all of that
> >> > cleans ant files in each repo). So I just one execution I have all
> >> build:
> >> >
> >> > #!/bin/bash
> >> > cd $ROYALE_COMPILER_HOME
> >> > git pull -v --progress "origin"
> >> > echo Royale Compiler updated from repo
> >> >
> >> > cd $ROYALE_TYPEDEFS_HOME
> >> > git pull -v --progress "origin"
> >> > echo Royale TypeDefs  updated from repo
> >> >
> >> > cd $ROYALE_HOME
> >> > git pull -v --progress "origin"
> >> > echo Royale AsJs  updated from repo
> >> >
> >> > #set JAVA_TOOL_OPTIONS=-Dfile.encoding=UTF-8 -Xmx1024m
> >> > cd $ROYALE_COMPILER_HOME
> >> > mvn clean install -DskipTests
> >> > echo Royale Compiler built with Maven
> >> >
> >> > cd $ROYALE_TYPEDEFS_HOME
> >> > ant wipe
> >> > mvn clean install
> >> > echo Royale TypeDefs built with Maven
> >> >
> >> > cd $ROYALE_HOME
> >> > ant super-clean
> >> > mvn clean install -DskipTests
> >> > #-Drat.skip=true
> >> > echo Royale AsJs built with Maven
> >> >
> >> > ant all -Dbuild.noprompt=true -Drelease.target=true
> >> > echo Royale SDK built with Ant
> >> >
> >> >
> >> > if this not works for you, you must to check your environment vars and
> >> the
> >> > rest of configuration to check where things are going wrong.
> >> >
> >> > HTH,
> >> >
> >> > Carlos
> >> >
> >> >
> >> >
> >> >
> >> > El mié., 14 nov. 2018 a las 13:15, Alina Kazi ()
> >> > escribió:
> >> >
> >> > > Hi Carlos,
> >> > >
> >> > > It's not first time I try to run maven. I run that last year with
> >> > > successful build.
> >> > > But after that I started to work using ant.
> >> > > Now, I need maven to run this example:
> >> > >
> >> > >
> >> >
> >>
> https://github.com/apache/royale-asjs/tree/develop/examples/amf/SampleAmfWebApp
> >> > >
> >> > > Thanks,
> >> > > Alina
> >> > >
> >> > > -Original Message-
> >> > > From: Carlos Rovira [mailto:carlosrov...@apache.org]
> >> > > Sent: Wednesday, November 14, 2018 4:46 PM
> >> > > To: dev@royale.apache.org
> >> > > Subject: Re: Getting An Emulation Component To Run
> >> > >
> >> > > Hi Alina, is the first time you run try maven? until now you was
> using
> >> > ant?
> >> > >
> >> > >
> >> > > El mié., 14 nov. 2018 a las 12:24, Alina Kazi ( >)
> >> > > escribió:
> >> > >
> >> > > >
> >> > > > Both of you suggest me to run the existing Apache Royale
> >> RemoteObject
> >> > > > Example.
> >> > > > But We are unable to download dependencies for maven build.
> >> > > > Steps given in below given link are followed:
> >> > > >
> >> https://github.com/apache/royale-asjs/wiki/Build-Apache-Royale-with-Ma
> >> > > > ven Tried to download nightly build but link not working:
> >> > > >
> >> > > >
> >> https://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs
> >> > > > /lastSuccessfulBuild/artifact/out/
> >> > > >
> >> > > > Executing task in folder SampleAmfWebApp :
> >> > > > Error : https://paste.apache.org/JU0N
> >> > > >
> >> > > > Thanks
> >> > > > Alina
> >> > > >
> >> > > > --
> >> > > > 

Re: Getting An Emulation Component To Run

[Carlos Rovira]

Piotr,

about why I suggest try to build that, I think Alina is yet in the point
where she does't get build Royale compiler, typedefs and framework with
maven, so she needs to get that first, then build "examples" folder with
"mvn clean install"



El mié., 14 nov. 2018 a las 21:27, Carlos Rovira ()
escribió:

> Hi Piotr,
>
> I thank after that she needs to run maven on examples folder, that will
> build all examples including AMF client and then the server, that uses the
> client. One important thing to take into account is that since we have
> various RO implementations, the java example has in the pom different
> configs that are commented, one for MX RO and one for NET RO. Since Alina
> wants to try MX RO she needs to comment NET and uncomment MX so maven
> overlay that client in the java war.
>
>
>
> El mié., 14 nov. 2018 a las 16:26, Piotr Zarzycki (<
> piotrzarzyck...@gmail.com>) escribió:
>
>> Hi Carlos,
>>
>> Why repository need to be build if we want to build example only ? I'm
>> curious why you suggesting that ?
>>
>> Piotr
>>
>> śr., 14 lis 2018 o 16:23 Carlos Rovira 
>> napisał(a):
>>
>> > Hi Alina,
>> >
>> > I have the following script in the folder that parent the three repo
>> > (compiler, typedefs and asjs). This script (for Mac but if you use
>> windows
>> > can adapt easily) updates from git the there repos, then build each repo
>> > with maven and build the SDK in the same repo (and before all of that
>> > cleans ant files in each repo). So I just one execution I have all
>> build:
>> >
>> > #!/bin/bash
>> > cd $ROYALE_COMPILER_HOME
>> > git pull -v --progress "origin"
>> > echo Royale Compiler updated from repo
>> >
>> > cd $ROYALE_TYPEDEFS_HOME
>> > git pull -v --progress "origin"
>> > echo Royale TypeDefs  updated from repo
>> >
>> > cd $ROYALE_HOME
>> > git pull -v --progress "origin"
>> > echo Royale AsJs  updated from repo
>> >
>> > #set JAVA_TOOL_OPTIONS=-Dfile.encoding=UTF-8 -Xmx1024m
>> > cd $ROYALE_COMPILER_HOME
>> > mvn clean install -DskipTests
>> > echo Royale Compiler built with Maven
>> >
>> > cd $ROYALE_TYPEDEFS_HOME
>> > ant wipe
>> > mvn clean install
>> > echo Royale TypeDefs built with Maven
>> >
>> > cd $ROYALE_HOME
>> > ant super-clean
>> > mvn clean install -DskipTests
>> > #-Drat.skip=true
>> > echo Royale AsJs built with Maven
>> >
>> > ant all -Dbuild.noprompt=true -Drelease.target=true
>> > echo Royale SDK built with Ant
>> >
>> >
>> > if this not works for you, you must to check your environment vars and
>> the
>> > rest of configuration to check where things are going wrong.
>> >
>> > HTH,
>> >
>> > Carlos
>> >
>> >
>> >
>> >
>> > El mié., 14 nov. 2018 a las 13:15, Alina Kazi ()
>> > escribió:
>> >
>> > > Hi Carlos,
>> > >
>> > > It's not first time I try to run maven. I run that last year with
>> > > successful build.
>> > > But after that I started to work using ant.
>> > > Now, I need maven to run this example:
>> > >
>> > >
>> >
>> https://github.com/apache/royale-asjs/tree/develop/examples/amf/SampleAmfWebApp
>> > >
>> > > Thanks,
>> > > Alina
>> > >
>> > > -Original Message-
>> > > From: Carlos Rovira [mailto:carlosrov...@apache.org]
>> > > Sent: Wednesday, November 14, 2018 4:46 PM
>> > > To: dev@royale.apache.org
>> > > Subject: Re: Getting An Emulation Component To Run
>> > >
>> > > Hi Alina, is the first time you run try maven? until now you was using
>> > ant?
>> > >
>> > >
>> > > El mié., 14 nov. 2018 a las 12:24, Alina Kazi ()
>> > > escribió:
>> > >
>> > > >
>> > > > Both of you suggest me to run the existing Apache Royale
>> RemoteObject
>> > > > Example.
>> > > > But We are unable to download dependencies for maven build.
>> > > > Steps given in below given link are followed:
>> > > >
>> https://github.com/apache/royale-asjs/wiki/Build-Apache-Royale-with-Ma
>> > > > ven Tried to download nightly build but link not working:
>> > > >
>> > > >
>> https://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs
>> > > > /lastSuccessfulBuild/artifact/out/
>> > > >
>> > > > Executing task in folder SampleAmfWebApp :
>> > > > Error : https://paste.apache.org/JU0N
>> > > >
>> > > > Thanks
>> > > > Alina
>> > > >
>> > > > --
>> > > > Carlos Rovira
>> > > > http://about.me/carlosrovira
>> > > >
>> > > >
>> > > >
>> > > >
>> > >
>> > >
>> >
>> > --
>> > Carlos Rovira
>> > http://about.me/carlosrovira
>> >
>>
>>
>> --
>>
>> Piotr Zarzycki
>>
>> Patreon: *https://www.patreon.com/piotrzarzycki
>> *
>>
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
>

-- 
Carlos Rovira
http://about.me/carlosrovira

Re: Getting An Emulation Component To Run

[Carlos Rovira]

Hi Piotr,

I thank after that she needs to run maven on examples folder, that will
build all examples including AMF client and then the server, that uses the
client. One important thing to take into account is that since we have
various RO implementations, the java example has in the pom different
configs that are commented, one for MX RO and one for NET RO. Since Alina
wants to try MX RO she needs to comment NET and uncomment MX so maven
overlay that client in the java war.



El mié., 14 nov. 2018 a las 16:26, Piotr Zarzycki (<
piotrzarzyck...@gmail.com>) escribió:

> Hi Carlos,
>
> Why repository need to be build if we want to build example only ? I'm
> curious why you suggesting that ?
>
> Piotr
>
> śr., 14 lis 2018 o 16:23 Carlos Rovira 
> napisał(a):
>
> > Hi Alina,
> >
> > I have the following script in the folder that parent the three repo
> > (compiler, typedefs and asjs). This script (for Mac but if you use
> windows
> > can adapt easily) updates from git the there repos, then build each repo
> > with maven and build the SDK in the same repo (and before all of that
> > cleans ant files in each repo). So I just one execution I have all build:
> >
> > #!/bin/bash
> > cd $ROYALE_COMPILER_HOME
> > git pull -v --progress "origin"
> > echo Royale Compiler updated from repo
> >
> > cd $ROYALE_TYPEDEFS_HOME
> > git pull -v --progress "origin"
> > echo Royale TypeDefs  updated from repo
> >
> > cd $ROYALE_HOME
> > git pull -v --progress "origin"
> > echo Royale AsJs  updated from repo
> >
> > #set JAVA_TOOL_OPTIONS=-Dfile.encoding=UTF-8 -Xmx1024m
> > cd $ROYALE_COMPILER_HOME
> > mvn clean install -DskipTests
> > echo Royale Compiler built with Maven
> >
> > cd $ROYALE_TYPEDEFS_HOME
> > ant wipe
> > mvn clean install
> > echo Royale TypeDefs built with Maven
> >
> > cd $ROYALE_HOME
> > ant super-clean
> > mvn clean install -DskipTests
> > #-Drat.skip=true
> > echo Royale AsJs built with Maven
> >
> > ant all -Dbuild.noprompt=true -Drelease.target=true
> > echo Royale SDK built with Ant
> >
> >
> > if this not works for you, you must to check your environment vars and
> the
> > rest of configuration to check where things are going wrong.
> >
> > HTH,
> >
> > Carlos
> >
> >
> >
> >
> > El mié., 14 nov. 2018 a las 13:15, Alina Kazi ()
> > escribió:
> >
> > > Hi Carlos,
> > >
> > > It's not first time I try to run maven. I run that last year with
> > > successful build.
> > > But after that I started to work using ant.
> > > Now, I need maven to run this example:
> > >
> > >
> >
> https://github.com/apache/royale-asjs/tree/develop/examples/amf/SampleAmfWebApp
> > >
> > > Thanks,
> > > Alina
> > >
> > > -Original Message-
> > > From: Carlos Rovira [mailto:carlosrov...@apache.org]
> > > Sent: Wednesday, November 14, 2018 4:46 PM
> > > To: dev@royale.apache.org
> > > Subject: Re: Getting An Emulation Component To Run
> > >
> > > Hi Alina, is the first time you run try maven? until now you was using
> > ant?
> > >
> > >
> > > El mié., 14 nov. 2018 a las 12:24, Alina Kazi ()
> > > escribió:
> > >
> > > >
> > > > Both of you suggest me to run the existing Apache Royale RemoteObject
> > > > Example.
> > > > But We are unable to download dependencies for maven build.
> > > > Steps given in below given link are followed:
> > > >
> https://github.com/apache/royale-asjs/wiki/Build-Apache-Royale-with-Ma
> > > > ven Tried to download nightly build but link not working:
> > > >
> > > >
> https://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs
> > > > /lastSuccessfulBuild/artifact/out/
> > > >
> > > > Executing task in folder SampleAmfWebApp :
> > > > Error : https://paste.apache.org/JU0N
> > > >
> > > > Thanks
> > > > Alina
> > > >
> > > > --
> > > > Carlos Rovira
> > > > http://about.me/carlosrovira
> > > >
> > > >
> > > >
> > > >
> > >
> > >
> >
> > --
> > Carlos Rovira
> > http://about.me/carlosrovira
> >
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> *
>


-- 
Carlos Rovira
http://about.me/carlosrovira

Re: [VOTE] Release Apache Royale 0.9.4 RC2

[Alex Harui]

+1
Package 
https://dist.apache.org/repos/dist/dev/royale/0.9.4/rc2/apache-royale-0.9.4-src.tar.gz
Java 1.8
OS: Mac OS X x86_64 10.12.6
Source kit signatures match: y
Source kit builds: y
README is ok: y
RELEASE_NOTES is ok: y
NOTICE is ok: y
LICENSE is ok: y
No unapproved licenses or archives: y
No unapproved binaries: y

Package 
https://dist.apache.org/repos/dist/dev/royale/0.9.4/rc2/binaries/apache-royale-0.9.4-bin-js-swf.tar.gz
Binary kit signatures match: y
NOTICE is ok: y
LICENSE is ok: y
No unapproved licenses or archives in binary package: y
No unapproved binaries in binary package: y

On 11/14/18, 10:46 AM, "Alex Harui"  wrote:

Hi, 

This is vote for the 0.9.4 release of Apache Royale. 

The release candidate can be found here; 

https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Froyale%2F0.9.4%2Frc2%2F&data=02%7C01%7Caharui%40adobe.com%7Ccd9e80a664c64b1e6b6408d64a617b95%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C636778179875922919&sdata=QEJPD0rVFzaXgJ6s71k00eanixC3lYl209SyPwKKuVU%3D&reserved=0
 

Before voting please review the section,'What are the ASF requirements on 
approving a release?', at: 

https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.apache.org%2Fdev%2Frelease.html%23approving-a-release&data=02%7C01%7Caharui%40adobe.com%7Ccd9e80a664c64b1e6b6408d64a617b95%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C636778179875932928&sdata=HKBhzhwTqPK%2Bnr0K6f6xZ2aFWTt1woJGknvVUh5DiRI%3D&reserved=0
 

At a minimum you would be expected to check that: 
- SHA and signed packages are correct 
- README, RELEASE_NOTES, NOTICE and LICENSE files are all fine 
- That the build script completes successfully 
- That you can compile and cross-compile a simple example using the SDK. 

The source package is a combination of the 3 main Royale repos. 

To use the binary package, unzip it into a folder.  The -js package is 
ready-to-use in an IDE or command-line.  If you need SWF output, use the 
-royale package and use Apache Ant to run the InstallAdobeSDKs script via: 
  ant -f InstallAdobeSDKs.xml 

You may also get the binary packages via NPM.  The -js package can be 
installed via: 

npm install

https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Froyale%2F0.9.4%2Frc2%2Fbinaries%2Fapache-roya&data=02%7C01%7Caharui%40adobe.com%7Ccd9e80a664c64b1e6b6408d64a617b95%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C636778179875932928&sdata=nNZ1G6OXn6NADfuphv9eFwFCzND8gP%2B9ndaXNVJAthU%3D&reserved=0
le-0.9.4-bin-js.tar.gz -g 

The full package with SWF support can be installed via: 

npm install

https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Froyale%2F0.9.4%2Frc&data=02%7C01%7Caharui%40adobe.com%7Ccd9e80a664c64b1e6b6408d64a617b95%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C636778179875932928&sdata=u1Q0pVjkFpAi%2BJQ3q9Kp9uF0Y9RUBom1PiDATS3BI6A%3D&reserved=0{rc}/binaries/apache-r
oyale-0.9.4-bin-js-swf.tar.gz -g

Maven artifacts are staged here: 

https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Forgapacheroyale-1025&data=02%7C01%7Caharui%40adobe.com%7Ccd9e80a664c64b1e6b6408d64a617b95%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C636778179875932928&sdata=X%2B4UhG7cT5p%2B%2FORwICilhplHV21atZxIqTY0YfOY%2Fx0%3D&reserved=0
 

Please vote to approve this release: 
+1 Approve the release 
-1 Disapprove the release (please provide specific comments to why) 

This vote will be open for 72 hours or until a result can be called. 

The vote passes if there is: 
- At least 3 +1 votes from the PMC 
- More positive votes than negative votes 

Remember that this is a 'beta-quality' release so I expect there 
will be many bugs found.  IMO the goal is not to try to find and fix bugs 
in the RC, but to make sure we have the packaging right, and enough 
functionality that folks will have some success trying to use it. 

People who are not in PMC are also encouraged to test out the release and 
vote, although their votes will not be binding, they can influence how the 
PMC votes. 

When voting please indicate what OS, IDE, Flash Player version and AIR 
version you tested with. 

For your convenience, there is an ant script that automates the common 
steps to validate a release.  Instead of individually downloading the 
package and signature files, unzipping, etc, you can instead: 
1) create an empty folder, 
2) download into that folder this file: 

https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Froyale%2F0.9.4%2Frc2%2FApproveRoyale.xml&data=02%7C01%7Caharui%40adobe.com%7Ccd9e8

[VOTE] Release Apache Royale 0.9.4 RC2

[Alex Harui]

Hi, 

This is vote for the 0.9.4 release of Apache Royale. 

The release candidate can be found here; 
https://dist.apache.org/repos/dist/dev/royale/0.9.4/rc2/ 

Before voting please review the section,'What are the ASF requirements on 
approving a release?', at: 
http://www.apache.org/dev/release.html#approving-a-release 

At a minimum you would be expected to check that: 
- SHA and signed packages are correct 
- README, RELEASE_NOTES, NOTICE and LICENSE files are all fine 
- That the build script completes successfully 
- That you can compile and cross-compile a simple example using the SDK. 

The source package is a combination of the 3 main Royale repos. 

To use the binary package, unzip it into a folder.  The -js package is 
ready-to-use in an IDE or command-line.  If you need SWF output, use the 
-royale package and use Apache Ant to run the InstallAdobeSDKs script via: 
  ant -f InstallAdobeSDKs.xml 

You may also get the binary packages via NPM.  The -js package can be 
installed via: 

npm install
https://dist.apache.org/repos/dist/dev/royale/0.9.4/rc2/binaries/apache-roya
le-0.9.4-bin-js.tar.gz -g 

The full package with SWF support can be installed via: 

npm install
https://dist.apache.org/repos/dist/dev/royale/0.9.4/rc{rc}/binaries/apache-r
oyale-0.9.4-bin-js-swf.tar.gz -g

Maven artifacts are staged here: 
https://repository.apache.org/content/repositories/orgapacheroyale-1025 

Please vote to approve this release: 
+1 Approve the release 
-1 Disapprove the release (please provide specific comments to why) 

This vote will be open for 72 hours or until a result can be called. 

The vote passes if there is: 
- At least 3 +1 votes from the PMC 
- More positive votes than negative votes 

Remember that this is a 'beta-quality' release so I expect there 
will be many bugs found.  IMO the goal is not to try to find and fix bugs 
in the RC, but to make sure we have the packaging right, and enough 
functionality that folks will have some success trying to use it. 

People who are not in PMC are also encouraged to test out the release and 
vote, although their votes will not be binding, they can influence how the 
PMC votes. 

When voting please indicate what OS, IDE, Flash Player version and AIR 
version you tested with. 

For your convenience, there is an ant script that automates the common 
steps to validate a release.  Instead of individually downloading the 
package and signature files, unzipping, etc, you can instead: 
1) create an empty folder, 
2) download into that folder this file: 
https://dist.apache.org/repos/dist/dev/royale/0.9.4/rc2/ApproveRoyale.xml 
3) run the script: 
   ant -e -f ApproveRoyale.xml -Drelease.version=0.9.4 -Drc=2 
   If you want to test SWF support during the approval, use: 
   ant -e -f ApproveRoyale.xml -Drelease.version=0.9.4 -Drc=2
-Duse-flash=true 

You are not required to use this script, and more testing of the packages 
and build results are always encouraged. 

 

Please put all discussion about this release in the DISCUSSION thread not 
this VOTE thread. 

Thanks, 
Alex Harui 

[DISCUSS] Discuss Release Apache Royale 0.9.4 RC2

[Alex Harui]

This is the discussion thread.   RC1 was never put up for vote because there
were issues with the notice files and build scripts when running from the
packages and not the repo.

Interestingly, the scripts ran just fine for me on my home Windows computer.
I did not have the problems Om, Piotr, and Yishay had when uploading or
downloading Maven artifacts.  Except when I tried watching videos while
waiting for the scripts to run (the "maven" target takes 2 hours in
Powershell, the "main" target took over an hour).   Then I would see uploads
"hang".   So I would recommend to any future RMs to try to make sure the
network is not otherwise too busy when running these scripts.

Changes in this RC include: 

 

Thanks, 
Alex Harui 

Re: Getting An Emulation Component To Run

[Piotr Zarzycki]

Hi Carlos,

Why repository need to be build if we want to build example only ? I'm
curious why you suggesting that ?

Piotr

śr., 14 lis 2018 o 16:23 Carlos Rovira  napisał(a):

> Hi Alina,
>
> I have the following script in the folder that parent the three repo
> (compiler, typedefs and asjs). This script (for Mac but if you use windows
> can adapt easily) updates from git the there repos, then build each repo
> with maven and build the SDK in the same repo (and before all of that
> cleans ant files in each repo). So I just one execution I have all build:
>
> #!/bin/bash
> cd $ROYALE_COMPILER_HOME
> git pull -v --progress "origin"
> echo Royale Compiler updated from repo
>
> cd $ROYALE_TYPEDEFS_HOME
> git pull -v --progress "origin"
> echo Royale TypeDefs  updated from repo
>
> cd $ROYALE_HOME
> git pull -v --progress "origin"
> echo Royale AsJs  updated from repo
>
> #set JAVA_TOOL_OPTIONS=-Dfile.encoding=UTF-8 -Xmx1024m
> cd $ROYALE_COMPILER_HOME
> mvn clean install -DskipTests
> echo Royale Compiler built with Maven
>
> cd $ROYALE_TYPEDEFS_HOME
> ant wipe
> mvn clean install
> echo Royale TypeDefs built with Maven
>
> cd $ROYALE_HOME
> ant super-clean
> mvn clean install -DskipTests
> #-Drat.skip=true
> echo Royale AsJs built with Maven
>
> ant all -Dbuild.noprompt=true -Drelease.target=true
> echo Royale SDK built with Ant
>
>
> if this not works for you, you must to check your environment vars and the
> rest of configuration to check where things are going wrong.
>
> HTH,
>
> Carlos
>
>
>
>
> El mié., 14 nov. 2018 a las 13:15, Alina Kazi ()
> escribió:
>
> > Hi Carlos,
> >
> > It's not first time I try to run maven. I run that last year with
> > successful build.
> > But after that I started to work using ant.
> > Now, I need maven to run this example:
> >
> >
> https://github.com/apache/royale-asjs/tree/develop/examples/amf/SampleAmfWebApp
> >
> > Thanks,
> > Alina
> >
> > -Original Message-
> > From: Carlos Rovira [mailto:carlosrov...@apache.org]
> > Sent: Wednesday, November 14, 2018 4:46 PM
> > To: dev@royale.apache.org
> > Subject: Re: Getting An Emulation Component To Run
> >
> > Hi Alina, is the first time you run try maven? until now you was using
> ant?
> >
> >
> > El mié., 14 nov. 2018 a las 12:24, Alina Kazi ()
> > escribió:
> >
> > >
> > > Both of you suggest me to run the existing Apache Royale RemoteObject
> > > Example.
> > > But We are unable to download dependencies for maven build.
> > > Steps given in below given link are followed:
> > > https://github.com/apache/royale-asjs/wiki/Build-Apache-Royale-with-Ma
> > > ven Tried to download nightly build but link not working:
> > >
> > > https://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs
> > > /lastSuccessfulBuild/artifact/out/
> > >
> > > Executing task in folder SampleAmfWebApp :
> > > Error : https://paste.apache.org/JU0N
> > >
> > > Thanks
> > > Alina
> > >
> > > --
> > > Carlos Rovira
> > > http://about.me/carlosrovira
> > >
> > >
> > >
> > >
> >
> >
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>


-- 

Piotr Zarzycki

Patreon: *https://www.patreon.com/piotrzarzycki
*

Re: Getting An Emulation Component To Run

[Carlos Rovira]

Hi Alina,

I have the following script in the folder that parent the three repo
(compiler, typedefs and asjs). This script (for Mac but if you use windows
can adapt easily) updates from git the there repos, then build each repo
with maven and build the SDK in the same repo (and before all of that
cleans ant files in each repo). So I just one execution I have all build:

#!/bin/bash
cd $ROYALE_COMPILER_HOME
git pull -v --progress "origin"
echo Royale Compiler updated from repo

cd $ROYALE_TYPEDEFS_HOME
git pull -v --progress "origin"
echo Royale TypeDefs  updated from repo

cd $ROYALE_HOME
git pull -v --progress "origin"
echo Royale AsJs  updated from repo

#set JAVA_TOOL_OPTIONS=-Dfile.encoding=UTF-8 -Xmx1024m
cd $ROYALE_COMPILER_HOME
mvn clean install -DskipTests
echo Royale Compiler built with Maven

cd $ROYALE_TYPEDEFS_HOME
ant wipe
mvn clean install
echo Royale TypeDefs built with Maven

cd $ROYALE_HOME
ant super-clean
mvn clean install -DskipTests
#-Drat.skip=true
echo Royale AsJs built with Maven

ant all -Dbuild.noprompt=true -Drelease.target=true
echo Royale SDK built with Ant


if this not works for you, you must to check your environment vars and the
rest of configuration to check where things are going wrong.

HTH,

Carlos




El mié., 14 nov. 2018 a las 13:15, Alina Kazi ()
escribió:

> Hi Carlos,
>
> It's not first time I try to run maven. I run that last year with
> successful build.
> But after that I started to work using ant.
> Now, I need maven to run this example:
>
> https://github.com/apache/royale-asjs/tree/develop/examples/amf/SampleAmfWebApp
>
> Thanks,
> Alina
>
> -Original Message-
> From: Carlos Rovira [mailto:carlosrov...@apache.org]
> Sent: Wednesday, November 14, 2018 4:46 PM
> To: dev@royale.apache.org
> Subject: Re: Getting An Emulation Component To Run
>
> Hi Alina, is the first time you run try maven? until now you was using ant?
>
>
> El mié., 14 nov. 2018 a las 12:24, Alina Kazi ()
> escribió:
>
> >
> > Both of you suggest me to run the existing Apache Royale RemoteObject
> > Example.
> > But We are unable to download dependencies for maven build.
> > Steps given in below given link are followed:
> > https://github.com/apache/royale-asjs/wiki/Build-Apache-Royale-with-Ma
> > ven Tried to download nightly build but link not working:
> >
> > https://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs
> > /lastSuccessfulBuild/artifact/out/
> >
> > Executing task in folder SampleAmfWebApp :
> > Error : https://paste.apache.org/JU0N
> >
> > Thanks
> > Alina
> >
> > --
> > Carlos Rovira
> > http://about.me/carlosrovira
> >
> >
> >
> >
>
>

-- 
Carlos Rovira
http://about.me/carlosrovira

Build failed in Jenkins: royale-asjs_MXTests #135

[apacheroyaleci]

See 


--
[...truncated 2.26 MB...]
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\core\IPanelModel.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\effects\IEffect.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\mx\events\CollectionEventKind.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\core\AllCSSStyles.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\mx\collections\ArrayCollection.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\core\IDataGridModel.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\html\beads\models\DataGridModel.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\utils\IBinaryDataInput.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\reflection\MetaDataDefinition.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\html\beads\ISpinnerView.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\html\beads\SpinnerView.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\core\IViewportModel.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\core\WrappedHTMLElement.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\spark\layouts\supportClasses\DropLocation.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\core\layout\LayoutData.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\mx\collections\errors\CursorError.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\mx\styles\CSSStyleDeclaration.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\core\IItemRendererParent.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\html\beads\DataContainerView.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\reflection\MethodDefinition.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\mx\display\Graphics.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\mx\core\ScrollControlBase.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\mx\controls\listClasses\ListBase.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\binding\WatcherBase.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\core\IImage.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\events\BrowserEvent.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\html\beads\models\PanelModel.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\mx\containers\beads\models\PanelModel.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\core\IPopUp.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\halo\scripts\ButtonTestScript.js
[mxmlc] us

RE: Getting An Emulation Component To Run

[Alina Kazi]

Hi Carlos,

It's not first time I try to run maven. I run that last year with successful 
build.
But after that I started to work using ant. 
Now, I need maven to run this example:
https://github.com/apache/royale-asjs/tree/develop/examples/amf/SampleAmfWebApp

Thanks,
Alina 

-Original Message-
From: Carlos Rovira [mailto:carlosrov...@apache.org] 
Sent: Wednesday, November 14, 2018 4:46 PM
To: dev@royale.apache.org
Subject: Re: Getting An Emulation Component To Run

Hi Alina, is the first time you run try maven? until now you was using ant?


El mié., 14 nov. 2018 a las 12:24, Alina Kazi ()
escribió:

>
> Both of you suggest me to run the existing Apache Royale RemoteObject 
> Example.
> But We are unable to download dependencies for maven build.
> Steps given in below given link are followed:
> https://github.com/apache/royale-asjs/wiki/Build-Apache-Royale-with-Ma
> ven Tried to download nightly build but link not working:
>
> https://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs
> /lastSuccessfulBuild/artifact/out/
>
> Executing task in folder SampleAmfWebApp :
> Error : https://paste.apache.org/JU0N
>
> Thanks
> Alina
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
>
>
>

Re: Getting An Emulation Component To Run

[Carlos Rovira]

Hi Alina, is the first time you run try maven? until now you was using ant?


El mié., 14 nov. 2018 a las 12:24, Alina Kazi ()
escribió:

>
> Both of you suggest me to run the existing Apache Royale RemoteObject
> Example.
> But We are unable to download dependencies for maven build.
> Steps given in below given link are followed:
> https://github.com/apache/royale-asjs/wiki/Build-Apache-Royale-with-Maven
> Tried to download nightly build but link not working:
>
> https://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs/lastSuccessfulBuild/artifact/out/
>
> Executing task in folder SampleAmfWebApp :
> Error : https://paste.apache.org/JU0N
>
> Thanks
> Alina
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
>
>
>

Build failed in Jenkins: royale-asjs_MXTests #134

[apacheroyaleci]

See 


Changes:

[harbs] Added Modal beads with example

[harbs] Flash not perfect, but at least it runs.

--
[...truncated 2.26 MB...]
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\core\IPanelModel.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\effects\IEffect.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\mx\events\CollectionEventKind.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\core\AllCSSStyles.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\mx\collections\ArrayCollection.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\core\IDataGridModel.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\html\beads\models\DataGridModel.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\utils\IBinaryDataInput.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\reflection\MetaDataDefinition.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\html\beads\ISpinnerView.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\html\beads\SpinnerView.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\core\IViewportModel.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\core\WrappedHTMLElement.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\spark\layouts\supportClasses\DropLocation.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\core\layout\LayoutData.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\mx\collections\errors\CursorError.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\mx\styles\CSSStyleDeclaration.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\core\IItemRendererParent.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\html\beads\DataContainerView.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\reflection\MethodDefinition.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\mx\display\Graphics.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\mx\core\ScrollControlBase.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\mx\controls\listClasses\ListBase.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\binding\WatcherBase.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\core\IImage.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\events\BrowserEvent.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\html\beads\models\PanelModel.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\mx\containers\beads\models\PanelModel.js
[mxmlc] using source file: 
c:\jenkins\workspace\royale-asjs_MXTests\mustella\tests\mxtests\basicTests\bin\js-debug\org\apache\royale\core\IPopUp.js
[mxmlc] using source file: 
c:\jenkins\workspace\r