date:20190623

Build failed in Jenkins: royale-asjs_MXTests #889

2019-06-23 Thread Apache Royale CI Server

See 


--
[...truncated 2.34 MB...]
[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file:

Build failed in Jenkins: royale-typedefs #1407

2019-06-23 Thread Apache Royale CI Server

See 


--
Started by upstream project "royale-compiler" build number 918
originally caused by:
 Started by an SCM change
[EnvInject] - Loading node environment variables.
Building on master in workspace 

 > git.exe rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git.exe config remote.origin.url 
 > https://github.com/apache/royale-typedefs.git # timeout=10
Fetching upstream changes from https://github.com/apache/royale-typedefs.git
 > git.exe --version # timeout=10
 > git.exe fetch --tags --progress 
 > https://github.com/apache/royale-typedefs.git 
 > +refs/heads/*:refs/remotes/origin/*
 > git.exe rev-parse "refs/remotes/origin/develop^{commit}" # timeout=10
 > git.exe rev-parse "refs/remotes/origin/origin/develop^{commit}" # timeout=10
Checking out Revision 2077d49bf4f5f15506dc411af53730d92ffc2008 
(refs/remotes/origin/develop)
 > git.exe config core.sparsecheckout # timeout=10
 > git.exe checkout -f 2077d49bf4f5f15506dc411af53730d92ffc2008
Commit message: "try to fix build"
 > git.exe rev-list --no-walk 2077d49bf4f5f15506dc411af53730d92ffc2008 # 
 > timeout=10
[royale-typedefs] $ cmd.exe /C "C:\apache\apache-ant-1.9.9\bin\ant.bat main && 
exit %%ERRORLEVEL%%"
Buildfile: 


main:
 [echo] swc-date is 06/24/19 04:16 +

download:
 [echo] 


BUILD FAILED
:58:
 The following error occurred while executing this line:
:91:
 src 
'
 doesn't exist.

Total time: 0 seconds
Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8 -Xms384m -Xmx1g 
Build step 'Invoke Ant' marked build as failure

Build failed in Jenkins: royale-asjs_MXTests #888

2019-06-23 Thread Apache Royale CI Server

See 


Changes:

[greg.dove] Updates to XML and XMLList, with new manual tests. Resolves an issue

--
[...truncated 2.34 MB...]
[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc]

Re: XML Problem with ignoreWhiteSpace=false

2019-06-23 Thread Greg Dove

Yishay, a few other issues became apparent as I worked on that. So I added
tests for them and fixed them also.

I can confirm that a lot of the older implementation was failing in many of
the tests, because I reverted to the older implementation locally and
checked against the same tests (which run in parallel with swf). So I do
know that this represents progress.
But what I cannot know is if there are other things that do not work after
these changes outside of the current test coverage (which is why it is
essential to enhance that coverage over time).
However I also have no desire to cause many sudden changes needed in your
project that we could let you manage more gradually if this is causing a
problem, because I have a feeling that you and Harbs are the main users of
XML at the moment.
If you are still encountering problems after my latest changes then we
could revert the XML project to how it was before all my recent changes and
I could move everything to a branch.
I haven't done that to date simply because in terms of what I can see in
the tests so far, I can only consider it to be progress in terms of getting
the implementation closer (than it was before) to the original as3
XML/XMList. But as I said... that is only as good as the test coverage.
Anyhow, let me know what you think... I have fingers crossed that the
latest changes should address things for you.
Greg

On Mon, Jun 24, 2019 at 12:35 AM Greg Dove  wrote:

> Hi Yishay, thanks for the new details. That's another bug. I have a local
> fix for that now, and new tests to cover this and more variations of the
> document level parsing.
> It's late for me now, so I will check everything thoroughly and push the
> fix in my morning.
>
>
>
> On Sun, Jun 23, 2019 at 9:57 PM Yishay Weiss 
> wrote:
>
>> Hi Greg,
>>
>> I’m still having issues with xml that were not there before. Can you see
>> why this [1] app, where my.xml is [2] is giving me an exception [3]?
>>
>>
>>
>> [1] https://paste.apache.org/ld1L
>> [2] https://paste.apache.org/d6VX
>> [3] https://paste.apache.org/qpub
>>
>> Yishay
>>
>

Re: 0.9.6 Release

2019-06-23 Thread Piotr Zarzycki

Great! Let me study this tomorrow and see how far I can go.

Thank you!

niedz., 23 cze 2019 o 18:22 Alex Harui 
napisał(a):

> Hi Piotr,
>
> I'm sure it doesn't contain everything.  That's part of this exercise:  to
> see what else needs to be modified in that wiki page or in the scripts and
> Jenkins jobs so it works for you as well as me and thus, hopefully others.
>
> Thanks for trying it out,
> -Alex
>
> On 6/23/19, 6:54 AM, "Piotr Zarzycki"  wrote:
>
> Hi Alex,
>
> Instruction here [1] contains everything what I need to know in order
> to
> make RC1 ? I'm going to start trying tomorrow my time.
>
> [1]
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fwiki%2FRelease-Manager-Notesdata=02%7C01%7Caharui%40adobe.com%7C3a700a9ad7414ecc249f08d6f7e24ffa%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636968948736458102sdata=j8LpE1uMhgEvjsA5CviAGVhve9VZHuZmZGcBt0fQ0JY%3Dreserved=0
>
> Thanks,
> Piotr
>
> wt., 18 cze 2019 o 07:51 Piotr Zarzycki 
> napisał(a):
>
> > Hi Alex,
> >
> > Thank you! I will be working in release next week, so if anyone have
> > anything to add there is some time.
> >
> > Thanks,
> > Piotr
> >
> > On Tue, Jun 18, 2019, 7:28 AM Alex Harui 
> wrote:
> >
> >> Mx tests are working locally for me with this last change to
> >> ListItemRenderer.
> >>
> >> So, the question for everyone is:  is there anything else we want
> to put
> >> in before trying to cut a release?
> >>
> >> We might need to change the ASDoc app after Greg's last change.  We
> might
> >> want to bang on ASDoc for a bit and see if anything major needs
> fixing
> >> before cutting a release.
> >>
> >> The only other thing I thought of was trying to upgrade Selenium so
> we
> >> can use a recent FireFox version.  Right now we are stuck way back
> on FF47,
> >> but I've also heard that more recent FF versions are less friendly
> to
> >> Flash, so you have to use some other browser to test Flash.  That's
> ok for
> >> building the Royale SDK since the Flash tests are run in
> >> FlashPlayerDebugger and the JS tests are run in a browser like FF.
> >>
> >> I'm tempted to say we should punt the inject_html in modules
> problem to
> >> the next release.
> >>
> >> I will be adding more details to
> >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fwiki%2FRelease-Manager-Notesdata=02%7C01%7Caharui%40adobe.com%7C3a700a9ad7414ecc249f08d6f7e24ffa%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636968948736458102sdata=j8LpE1uMhgEvjsA5CviAGVhve9VZHuZmZGcBt0fQ0JY%3Dreserved=0
> >> But there should be enough there to get an RC out for vote.
> >>
> >> Thanks,
> >> -Alex
> >>
> >> On 6/17/19, 11:06 AM, "Alex Harui" 
> wrote:
> >>
> >> I just saw ASDoc work well enough for me to start with
> >> mx.binding.BindabilityInfo and switch to mx.charts.AxisRenderer.
> >>
> >> There might be JSON parsing issues with other classes.  Run the
> >> bin/js-debug version, check the console if things don't load and
> see what
> >> file failed to load and why.
> >>
> >> I will take a look at MXTests next.
> >>
> >> -Alex
> >>
> >> On 6/17/19, 8:08 AM, "Alex Harui" 
> wrote:
> >>
> >> ASDoc is not fully working for me.  I've been working on
> that the
> >> past several days.  It took quite a while to fix the JSON output
> from new
> >> and interesting ASDoc patterns.  I'm now looking into failures due
> to
> >> changes in coercion rules in the JS output.  ASDoc was trying to
> save time
> >> by using plain objects that were isomorphic to a class instead of
> actual
> >> class instances.
> >>
> >> MXTests are failing on the CI server and probably locally
> but I
> >> haven't gotten that far.
> >>
> >> I would think we want these things to work, but you are the
> RM so
> >> it is up to you.  Volunteers are welcome to help with these and
> other tasks.
> >>
> >> -Alex
> >>
> >> On 6/17/19, 12:44 AM, "Piotr Zarzycki" <
> piotrzarzyck...@gmail.com>
> >> wrote:
> >>
> >> Hi Alex,
> >>
> >> I don't see any answer here - can I start with trying
> your
> >> instruction and
> >> start release ?
> >>
> >> Thanks,
> >> Piotr
> >>
> >> śr., 12 cze 2019 o 10:12 Carlos Rovira <
> >> carlosrov...@apache.org> napisał(a):
> >>
> >> > Hi Alex,
> >> > just build from scratch right now and seems maven and
> ant
> >> was ok
> >> >
> >> > El mié., 12 jun. 2019 a las 10:02, Alex Harui
> >> ()
> >> > escribió:

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

2019-06-23 Thread Apache Royale CI Server

See

Re: [royale-asjs] branch develop updated: Adding a resizable load inicator.

2019-06-23 Thread Alex Harui

I made some changes so it more closely matches how we handle other MIT licenses.

-Alex

On 6/20/19, 10:31 PM, "Alex Harui"  wrote:

Ok,  I missed that, but there is sort of a template we should follow.  See 
the other MIT Licenses in LICENSE.

Which SVG files did you use in the LoadIndicators?  IMO, a comment in the 
source file indicating that the SVG content is third-party is worth doing.

Thanks,
-Alex

On 6/19/19, 12:27 AM, "Yishay Weiss"  wrote:

I changed that in



a45f3638697492642ee93c60e74f8995dfcf79a9



Thanks.






From: Alex Harui 
Sent: Wednesday, June 19, 2019 9:20:47 AM
To: dev@royale.apache.org; comm...@royale.apache.org
Subject: Re: [royale-asjs] branch develop updated: Adding a resizable 
load inicator.

Yishay,

Are you still using 3rd party load indicators?  If so, I think the MIT 
License attribution is actually supposed to go in LICENSE not NOTICE.  See

https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.apache.org%2Fdev%2Flicensing-howto.html%23permissive-depsdata=02%7C01%7Caharui%40adobe.com%7Cf0a55bd39def4e6335b408d6f609c647%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636966919182957620sdata=4iSHek584Vv84EczlpVEEKdrMyfYzwE4LpAia8bDqL0%3Dreserved=0

Thanks,
-Alex

On 6/18/19, 10:18 PM, "yish...@apache.org"  wrote:

This is an automated email from the ASF dual-hosted git repository.

yishayw pushed a commit to branch develop
in repository 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitbox.apache.org%2Frepos%2Fasf%2Froyale-asjs.gitdata=02%7C01%7Caharui%40adobe.com%7Cf0a55bd39def4e6335b408d6f609c647%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636966919182957620sdata=rVPh0WESrQHg%2FKOXiWCq9xsjWiFdZFb9F4ndr2tl1N4%3Dreserved=0


The following commit(s) were added to refs/heads/develop by this 
push:
 new 9c2d5ca  Adding a resizable load inicator.
9c2d5ca is described below

commit 9c2d5ca53ef0c67950ff76753f5f2834568de90a
Author: DESKTOP-RH4S838\Yishay 
AuthorDate: Wed Jun 19 08:16:50 2019 +0300

Adding a resizable load inicator.
---
 .../Basic/src/main/resources/basic-manifest.xml|  1 +
 .../apache/royale/html/beads/DisableLoaderBead.as  |  6 +-
 .../html/beads/ShrinkableDisableLoaderBead.as  | 87 
++
 3 files changed, 91 insertions(+), 3 deletions(-)

diff --git 
a/frameworks/projects/Basic/src/main/resources/basic-manifest.xml 
b/frameworks/projects/Basic/src/main/resources/basic-manifest.xml
index a2239a7..284cf5c 100644
--- 
a/frameworks/projects/Basic/src/main/resources/basic-manifest.xml
+++ 
b/frameworks/projects/Basic/src/main/resources/basic-manifest.xml
@@ -161,6 +161,7 @@
 
 
 
+
 
 
 
diff --git 
a/frameworks/projects/Basic/src/main/royale/org/apache/royale/html/beads/DisableLoaderBead.as
 
b/frameworks/projects/Basic/src/main/royale/org/apache/royale/html/beads/DisableLoaderBead.as
index a233bdf..19ef75b 100644
--- 
a/frameworks/projects/Basic/src/main/royale/org/apache/royale/html/beads/DisableLoaderBead.as
+++ 
b/frameworks/projects/Basic/src/main/royale/org/apache/royale/html/beads/DisableLoaderBead.as
@@ -56,8 +56,8 @@ package org.apache.royale.html.beads
 {
 }

-   private var _strand:IStrand;
-   private var _loader:IUIBase;
+   protected var _strand:IStrand;
+   protected var _loader:IUIBase;

 /**
  *  @copy org.apache.royale.core.IBead#strand
@@ -85,7 +85,7 @@ package org.apache.royale.html.beads
 /**
  * @royaleignorecoercion org.apache.royale.core.IUIBase
  */
-   private function get host():IUIBase
+   protected function get host():IUIBase
 {
 return _strand as IUIBase;
 }
diff --git 
a/frameworks/projects/Basic/src/main/royale/org/apache/royale/html/beads/ShrinkableDisableLoaderBead.as
 
b/frameworks/projects/Basic/src/main/royale/org/apache/royale/html/beads/ShrinkableDisableLoaderBead.as
new file mode 100644

Re: 0.9.6 Release

2019-06-23 Thread Alex Harui

Hi Piotr,

I'm sure it doesn't contain everything.  That's part of this exercise:  to see 
what else needs to be modified in that wiki page or in the scripts and Jenkins 
jobs so it works for you as well as me and thus, hopefully others.

Thanks for trying it out,
-Alex

On 6/23/19, 6:54 AM, "Piotr Zarzycki"  wrote:

Hi Alex,

Instruction here [1] contains everything what I need to know in order to
make RC1 ? I'm going to start trying tomorrow my time.

[1] 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fwiki%2FRelease-Manager-Notesdata=02%7C01%7Caharui%40adobe.com%7C3a700a9ad7414ecc249f08d6f7e24ffa%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636968948736458102sdata=j8LpE1uMhgEvjsA5CviAGVhve9VZHuZmZGcBt0fQ0JY%3Dreserved=0

Thanks,
Piotr

wt., 18 cze 2019 o 07:51 Piotr Zarzycki 
napisał(a):

> Hi Alex,
>
> Thank you! I will be working in release next week, so if anyone have
> anything to add there is some time.
>
> Thanks,
> Piotr
>
> On Tue, Jun 18, 2019, 7:28 AM Alex Harui  wrote:
>
>> Mx tests are working locally for me with this last change to
>> ListItemRenderer.
>>
>> So, the question for everyone is:  is there anything else we want to put
>> in before trying to cut a release?
>>
>> We might need to change the ASDoc app after Greg's last change.  We might
>> want to bang on ASDoc for a bit and see if anything major needs fixing
>> before cutting a release.
>>
>> The only other thing I thought of was trying to upgrade Selenium so we
>> can use a recent FireFox version.  Right now we are stuck way back on 
FF47,
>> but I've also heard that more recent FF versions are less friendly to
>> Flash, so you have to use some other browser to test Flash.  That's ok 
for
>> building the Royale SDK since the Flash tests are run in
>> FlashPlayerDebugger and the JS tests are run in a browser like FF.
>>
>> I'm tempted to say we should punt the inject_html in modules problem to
>> the next release.
>>
>> I will be adding more details to
>> 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fwiki%2FRelease-Manager-Notesdata=02%7C01%7Caharui%40adobe.com%7C3a700a9ad7414ecc249f08d6f7e24ffa%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636968948736458102sdata=j8LpE1uMhgEvjsA5CviAGVhve9VZHuZmZGcBt0fQ0JY%3Dreserved=0
>> But there should be enough there to get an RC out for vote.
>>
>> Thanks,
>> -Alex
>>
>> On 6/17/19, 11:06 AM, "Alex Harui"  wrote:
>>
>> I just saw ASDoc work well enough for me to start with
>> mx.binding.BindabilityInfo and switch to mx.charts.AxisRenderer.
>>
>> There might be JSON parsing issues with other classes.  Run the
>> bin/js-debug version, check the console if things don't load and see what
>> file failed to load and why.
>>
>> I will take a look at MXTests next.
>>
>> -Alex
>>
>> On 6/17/19, 8:08 AM, "Alex Harui"  wrote:
>>
>> ASDoc is not fully working for me.  I've been working on that the
>> past several days.  It took quite a while to fix the JSON output from new
>> and interesting ASDoc patterns.  I'm now looking into failures due to
>> changes in coercion rules in the JS output.  ASDoc was trying to save 
time
>> by using plain objects that were isomorphic to a class instead of actual
>> class instances.
>>
>> MXTests are failing on the CI server and probably locally but I
>> haven't gotten that far.
>>
>> I would think we want these things to work, but you are the RM so
>> it is up to you.  Volunteers are welcome to help with these and other 
tasks.
>>
>> -Alex
>>
>> On 6/17/19, 12:44 AM, "Piotr Zarzycki" 

>> wrote:
>>
>> Hi Alex,
>>
>> I don't see any answer here - can I start with trying your
>> instruction and
>> start release ?
>>
>> Thanks,
>> Piotr
>>
>> śr., 12 cze 2019 o 10:12 Carlos Rovira <
>> carlosrov...@apache.org> napisał(a):
>>
>> > Hi Alex,
>> > just build from scratch right now and seems maven and ant
>> was ok
>> >
>> > El mié., 12 jun. 2019 a las 10:02, Alex Harui
>> ()
>> > escribió:
>> >
>> > > The merge is complete, and the main builds seem to be
>> successful, except
>> > > for Maven on royale-asjs which was failing before the
>> merge.
>> > >
>> > > I'm still catching up on other things, but I think there
>> are some bugs we
>> > > need to fix before cutting

Re: 0.9.6 Release

2019-06-23 Thread Piotr Zarzycki

Hi Alex,

Instruction here [1] contains everything what I need to know in order to
make RC1 ? I'm going to start trying tomorrow my time.

[1] https://github.com/apache/royale-asjs/wiki/Release-Manager-Notes

Thanks,
Piotr

wt., 18 cze 2019 o 07:51 Piotr Zarzycki 
napisał(a):

> Hi Alex,
>
> Thank you! I will be working in release next week, so if anyone have
> anything to add there is some time.
>
> Thanks,
> Piotr
>
> On Tue, Jun 18, 2019, 7:28 AM Alex Harui  wrote:
>
>> Mx tests are working locally for me with this last change to
>> ListItemRenderer.
>>
>> So, the question for everyone is:  is there anything else we want to put
>> in before trying to cut a release?
>>
>> We might need to change the ASDoc app after Greg's last change.  We might
>> want to bang on ASDoc for a bit and see if anything major needs fixing
>> before cutting a release.
>>
>> The only other thing I thought of was trying to upgrade Selenium so we
>> can use a recent FireFox version.  Right now we are stuck way back on FF47,
>> but I've also heard that more recent FF versions are less friendly to
>> Flash, so you have to use some other browser to test Flash.  That's ok for
>> building the Royale SDK since the Flash tests are run in
>> FlashPlayerDebugger and the JS tests are run in a browser like FF.
>>
>> I'm tempted to say we should punt the inject_html in modules problem to
>> the next release.
>>
>> I will be adding more details to
>> https://github.com/apache/royale-asjs/wiki/Release-Manager-Notes
>> But there should be enough there to get an RC out for vote.
>>
>> Thanks,
>> -Alex
>>
>> On 6/17/19, 11:06 AM, "Alex Harui"  wrote:
>>
>> I just saw ASDoc work well enough for me to start with
>> mx.binding.BindabilityInfo and switch to mx.charts.AxisRenderer.
>>
>> There might be JSON parsing issues with other classes.  Run the
>> bin/js-debug version, check the console if things don't load and see what
>> file failed to load and why.
>>
>> I will take a look at MXTests next.
>>
>> -Alex
>>
>> On 6/17/19, 8:08 AM, "Alex Harui"  wrote:
>>
>> ASDoc is not fully working for me.  I've been working on that the
>> past several days.  It took quite a while to fix the JSON output from new
>> and interesting ASDoc patterns.  I'm now looking into failures due to
>> changes in coercion rules in the JS output.  ASDoc was trying to save time
>> by using plain objects that were isomorphic to a class instead of actual
>> class instances.
>>
>> MXTests are failing on the CI server and probably locally but I
>> haven't gotten that far.
>>
>> I would think we want these things to work, but you are the RM so
>> it is up to you.  Volunteers are welcome to help with these and other tasks.
>>
>> -Alex
>>
>> On 6/17/19, 12:44 AM, "Piotr Zarzycki" 
>> wrote:
>>
>> Hi Alex,
>>
>> I don't see any answer here - can I start with trying your
>> instruction and
>> start release ?
>>
>> Thanks,
>> Piotr
>>
>> śr., 12 cze 2019 o 10:12 Carlos Rovira <
>> carlosrov...@apache.org> napisał(a):
>>
>> > Hi Alex,
>> > just build from scratch right now and seems maven and ant
>> was ok
>> >
>> > El mié., 12 jun. 2019 a las 10:02, Alex Harui
>> ()
>> > escribió:
>> >
>> > > The merge is complete, and the main builds seem to be
>> successful, except
>> > > for Maven on royale-asjs which was failing before the
>> merge.
>> > >
>> > > I'm still catching up on other things, but I think there
>> are some bugs we
>> > > need to fix before cutting the release?  I think ASDoc
>> may not be fully
>> > > working?  What else?
>> > >
>> > > -Alex
>> > >
>> > > On 6/10/19, 11:05 AM, "Piotr Zarzycki" <
>> piotrzarzyck...@gmail.com>
>> > wrote:
>> > >
>> > > Hi Alex,
>> > >
>> > > Many thanks for that! I will try to be RM. I will
>> have some dedicated
>> > > time
>> > > for that. I will wait for your instruction and merge
>> to develop.
>> > >
>> > > Thanks,
>> > > Piotr
>> > >
>> > >
>> > > On Mon, Jun 10, 2019, 7:31 PM Alex Harui
>> 
>> > > wrote:
>> > >
>> > > > Well, that turned out to be much more
>> time-consuming than I
>> > > expected, but
>> > > > we can now create identical release artifacts on
>> Mac and Win.  I am
>> > > hopeful
>> > > > this effort will pay off not only now in having
>> other folks
>> > generate
>> > > > releases, but also in the future if signed binaries
>> become a
>> > > requirement.
>> > > >
>>

Re: XML Problem with ignoreWhiteSpace=false

2019-06-23 Thread Greg Dove

Hi Yishay, thanks for the new details. That's another bug. I have a local
fix for that now, and new tests to cover this and more variations of the
document level parsing.
It's late for me now, so I will check everything thoroughly and push the
fix in my morning.

On Sun, Jun 23, 2019 at 9:57 PM Yishay Weiss  wrote:

> Hi Greg,
>
> I’m still having issues with xml that were not there before. Can you see
> why this [1] app, where my.xml is [2] is giving me an exception [3]?
>
>
>
> [1] https://paste.apache.org/ld1L
> [2] https://paste.apache.org/d6VX
> [3] https://paste.apache.org/qpub
>
> Yishay
>

XML Problem with ignoreWhiteSpace=false

2019-06-23 Thread Yishay Weiss

Hi Greg,

I’m still having issues with xml that were not there before. Can you see why 
this [1] app, where my.xml is [2] is giving me an exception [3]?



[1] https://paste.apache.org/ld1L
[2] https://paste.apache.org/d6VX
[3] https://paste.apache.org/qpub

Yishay