testing with browserstack. IE11 bad surprise

[Carlos Rovira]

Hi,

since I'm on Mac I was blind to Microsoft browsers.
I was testing mainly with Chrome (since is the most used) and Safari (since
is what I use to use).
I have installed Firefox, but I was not testing in a day by day basis.
Never used Opera and Yandex since I doesn't think as relevant

For me Browserstack is mostly to test IE11 and Edge, and I found that while
Edge has some issues (and Firefox too), both can be fixed for Jewel

But the surprise was IE11 this browser is not even near of what it
should show, so taking into account that IE is facing its extinction I
don't think I should
put hours in make that browser work at all. For me IE is the piece of
software we should help to be death and buried, since if it's not capable
of rendering
just a simple button right without lots of hacks, don't want to imagine
what other horrors it deserve to us in this journey.

It's clear that today IE11 has still an important demographic, but in a
year I expect to be cut in favor of Edge that is the MS bet for the future.
For me it's not aceptable to need lots of work for only one browser (an
version), when users have Chrome, Firefox, Opera, Safari and Yandex and
even more

To see what I refer I think you should take a test of JewelExample in
different browsers. All behaves more or less the same. I see some issues in
Edge and Firefox
to fix, but if you see the example in IE11 you will literally cry...

So what do you think?

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

Re: testing with browserstack. IE11 bad surprise

[Alex Harui]

IMO, we need Royale to work on IE11.  It does not mean that Jewel must
work on IE11, but it would be nice if some theme did, other than Basic.

It turns out that my colleagues can't be sure of their data since IE was
mostly being used for intranet apps in large enterprises, but I think IE
is being kept around for those large enterprises who are leveraging the
"plug-in" capabilities of IE.  And I believe that Royale can be attractive
to those enterprises.

There is a difference between browsers that folks use for browsing the web
and the app that is used in a mission critical app for the front end.  I
think MS is saying to use Edge for the first case, but IE is going to be
around for many more years for the second case.

Does MDL and Bootstrap work on IE?  If so, if you can spend a day figuring
out why IE11 doesn't work and come up with a simpler variant that does
work, I think that would benefit Royale.

My 2 cents,
-Alex

On 4/7/18, 12:42 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira"
 wrote:

>Hi,
>
>since I'm on Mac I was blind to Microsoft browsers.
>I was testing mainly with Chrome (since is the most used) and Safari
>(since
>is what I use to use).
>I have installed Firefox, but I was not testing in a day by day basis.
>Never used Opera and Yandex since I doesn't think as relevant
>
>For me Browserstack is mostly to test IE11 and Edge, and I found that
>while
>Edge has some issues (and Firefox too), both can be fixed for Jewel
>
>But the surprise was IE11 this browser is not even near of what it
>should show, so taking into account that IE is facing its extinction I
>don't think I should
>put hours in make that browser work at all. For me IE is the piece of
>software we should help to be death and buried, since if it's not capable
>of rendering
>just a simple button right without lots of hacks, don't want to imagine
>what other horrors it deserve to us in this journey.
>
>It's clear that today IE11 has still an important demographic, but in a
>year I expect to be cut in favor of Edge that is the MS bet for the
>future.
>For me it's not aceptable to need lots of work for only one browser (an
>version), when users have Chrome, Firefox, Opera, Safari and Yandex and
>even more
>
>To see what I refer I think you should take a test of JewelExample in
>different browsers. All behaves more or less the same. I see some issues
>in
>Edge and Firefox
>to fix, but if you see the example in IE11 you will literally cry...
>
>So what do you think?
>
>-- 
>Carlos Rovira
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2
>Fcarlosrovira=02%7C01%7Caharui%40adobe.com%7Cfb664630749a424f327708d5
>9c5b39e8%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636586838017132240
>data=cCyvy2Hde5H4Rrs%2F75vMKty9ZvMlJxeqi4LSRKkzRjU%3D=0

Re: [MAVEN-BUILD] Royale-asjs - Build # 615 - Still Failing

[Carlos Rovira]

Hi Piotr, just fixed this problem. Was tricky to imagine what was the
problem.
In the commit I comment about the issue.

CSS compilation now has "grayscale" filter, this conflicts with
"font-smoothing: grayscale", is the same that happens with old "opacity"
and new css filter "opacity".

Maybe Alex could know what to deal with this situation of duplicated css
tokens in css compiler. This is beyond my capabilities with the compiler.




2018-04-06 18:53 GMT+02:00 Piotr Zarzycki :

> DataBinding Flat example is failing. It looks like for some reason some css
> is not parsed well.. Not sure for 100%.
>
> Why ant build is passing?
>
> On Fri, Apr 6, 2018, 18:43 Carlos Rovira  wrote:
>
> > Anbody knows why this is failing?
> > builds seems to be working ok
> >
> > -- Forwarded message --
> > From: Apache Jenkins Server 
> > Date: 2018-04-06 16:03 GMT+02:00
> > Subject: [MAVEN-BUILD] Royale-asjs - Build # 615 - Still Failing
> > To: comm...@royale.apache.org, ha...@in-tools.com
> >
> >
> > The Apache Jenkins build system has built Royale-asjs (build #615)
> >
> > Status: Still Failing
> >
> > Check console output at https://builds.apache.org/job/Royale-asjs/615/
> to
> > view the results.
> >
> >
> >
> > --
> > Carlos Rovira
> > http://about.me/carlosrovira
> >
>



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

Re: testing with browserstack. IE11 bad surprise

[Alex Harui]

Hi Carlos, 

I think you missed my point and main question.  The question is: Does MDL
and Bootstrap support IE?  If so, then they have found a way to customize
Button.  Seems like we should be able to do the same, but maybe it won't
be the Jewel theme.  It might be something else, maybe folks who need IE
should just use our MDL support.

The point is that IE probably has MS support through 2025.  It will likely
fade to insignificant numbers among folks who get to choose which browser
they want to use.  But IE is likely going to live on through 2025 as a
"terminal" for enterprise mission critical applications.  Otherwise, I
think MS would have already announced a true phase out of IE.  IMO, Royale
cannot ignore the "terminal" apps.  That is where Flex was winning back in
the Adobe days.  Getting a big enterprise Adobe Flex customer who still
has a Flex app to use Royale in IE would be a huge win for Royale.  But
again, it doesn't have to be Jewel.  But it might be nice if it looked
better than just Basic components.

My 2 cents,
-Alex

On 4/7/18, 9:47 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira"
 wrote:

>Hi Alex,
>
>I think is better to show you IE11 rendering [1]
>
>I think the image is self explanatory. I didn't analyze it already, maybe
>is some huge problem that makes it totally broken, but if not, if I need
>to
>have a complete rendering only for IE11 for each control and component we
>have, I think simply doesn't worth it.
>
>I don't want to give up with this already, maybe we can find some easy way
>to deal with this, but I want to comment it here so we can have it in
>mind.
>
>Depending of the effort implied, other variables to have in mind is the
>scope of this browser over time. We have deprecated already IE8, IE9 and
>IE10, one for year (more or less). If things makes IE11 be almost in no
>use
>in a year, spend lots of time to get that concrete version of IE working
>will be a huge waste of time.
>
>Let's analyze more the situation and I'm sure the right way to proceed
>will
>emerge in some days...
>
>Thanks
>
>
>[1] 
>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsnag.gy%2
>FdOgomt.jpg=02%7C01%7Caharui%40adobe.com%7C713cce522f334b96532208d59c
>a75127%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636587164837567932
>ta=STfpIPB8inXDym12jvGyOPXzFMMvGFCjdG7I2eMR7Y0%3D=0
>
>2018-04-07 17:10 GMT+02:00 Alex Harui :
>
>> IMO, we need Royale to work on IE11.  It does not mean that Jewel must
>> work on IE11, but it would be nice if some theme did, other than Basic.
>>
>> It turns out that my colleagues can't be sure of their data since IE was
>> mostly being used for intranet apps in large enterprises, but I think IE
>> is being kept around for those large enterprises who are leveraging the
>> "plug-in" capabilities of IE.  And I believe that Royale can be
>>attractive
>> to those enterprises.
>>
>> There is a difference between browsers that folks use for browsing the
>>web
>> and the app that is used in a mission critical app for the front end.  I
>> think MS is saying to use Edge for the first case, but IE is going to be
>> around for many more years for the second case.
>>
>> Does MDL and Bootstrap work on IE?  If so, if you can spend a day
>>figuring
>> out why IE11 doesn't work and come up with a simpler variant that does
>> work, I think that would benefit Royale.
>>
>> My 2 cents,
>> -Alex
>>
>> On 4/7/18, 12:42 AM, "carlos.rov...@gmail.com on behalf of Carlos
>>Rovira"
>>  wrote:
>>
>> >Hi,
>> >
>> >since I'm on Mac I was blind to Microsoft browsers.
>> >I was testing mainly with Chrome (since is the most used) and Safari
>> >(since
>> >is what I use to use).
>> >I have installed Firefox, but I was not testing in a day by day basis.
>> >Never used Opera and Yandex since I doesn't think as relevant
>> >
>> >For me Browserstack is mostly to test IE11 and Edge, and I found that
>> >while
>> >Edge has some issues (and Firefox too), both can be fixed for Jewel
>> >
>> >But the surprise was IE11 this browser is not even near of what it
>> >should show, so taking into account that IE is facing its extinction I
>> >don't think I should
>> >put hours in make that browser work at all. For me IE is the piece of
>> >software we should help to be death and buried, since if it's not
>>capable
>> >of rendering
>> >just a simple button right without lots of hacks, don't want to imagine
>> >what other horrors it deserve to us in this journey.
>> >
>> >It's clear that today IE11 has still an important demographic, but in a
>> >year I expect to be cut in favor of Edge that is the MS bet for the
>> >future.
>> >For me it's not aceptable to need lots of work for only one browser (an
>> >version), when users have Chrome, Firefox, Opera, Safari and Yandex and
>> >even more
>> >
>> >To see what I refer I think you should take a test of 

Re: New Blog Example in website

[Carlos Rovira]

Alex,

I think you don't understand the warnings I'm putting on this. Nowadays put
our website in royale is a really bad idea. I plan to write lots of blog
examples.
If you make me do this "programming" each blog post, or even, have to get
the same look we have for each page, we'll end with something that simply
is not at the same level we have right now, and I simply will not have the
time to invest in that way to do things.

This is not a problem of technology, is not royale vs wp, or whatever other
reason, is only we have a publishing platform, with backend editing for
texts, upload of resources, and lots more if we need in a world of plugins,
and then it's converted to plain static html. We could do a publishing
platform with Royale...but that would be a another huge project and
separate from our main goal that is make an SDK so others can make that
kind of software. Make a web is not our goal. To have a web (made with a
tool done for that) is our goal only to fulfill a concrete target:
communicate with our audience to give them information about the real thing
we do here: royale framework code.

Warning!, we have already royale code in our website:
http://royale.apache.org/using-jewel-alert-control/

In that post the embedded royale example application is a js-release
compilation...so that is really our target! And we are compliant with it :)

We need to do more of this so people see what easy is to make things in
Royale. Instead, no body cares if our website is or not made with royale.

So again, we have lots more needs to fill hours and hours of development
than spending that time replicating the actual pages in Royale. When I did
Thanks-to and IDE pages, it took me some time, but very few compared with
making it without the pieces that WP+Movedo+WPBakety puts to work for me.
It's the same that if we plan to make twitter on royale in order to be on
twitter (it's maybe a silly example, but hope it helps me to illustrate).

To make us elegible for other users there's so much work ahead like the
current MX/Spark effort. AMF needs to work with all possible data
structures that was already working in Flash, we need lots of more controls
in Jewel and working cross platform, we need more libraries infrastructure
like validations, formatting.

Another important thing we need if my company wants to migrate our Avant2
app is to get swiz framework or something like that in Royale, and that
implies annotations metadata to inject models, views, vars, etc..., don't
know what's the actual state of this.

In resume, if we want to make our website in royale, we can do it, but
more, more later, and when we try it, we should try to make it as a
front-end of WP using WP-REST api and in that way to get all components
that MOVEDO supports, we must need to code that parts in royale to get that
output.

We're getting right now lots of interest in social networks. People are
pushing us liking and retwitting our tweets and post of facebook, we need
to get more material out there for them to consume maybe youtube videos,
more posts, etc...so each of us need to have a  good priority plan that
although is free as apache way impose, should be as coordintate as possible
so all the efforts done by us could end with a huge community out there
that support us, or maybe we could end with people not following the actual
hype and getting the project cold and we loosing our time with a project
that has few people supporiting it.

Maybe a long email, but hope you can understand my worries in all of this

Thanks! :)

Carlos




2018-04-07 16:55 GMT+02:00 Alex Harui :

> If I had more time, I would be pushing harder to write our website in
> Royale.  It still bugs me that we haven't done that.  I've proven that
> Royale web pages can be search indexed by Google.
>
> My 2 cents,
> -Alex
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
>
>

Re: New Blog Example in website

[Alex Harui]

If I had more time, I would be pushing harder to write our website in
Royale.  It still bugs me that we haven't done that.  I've proven that
Royale web pages can be search indexed by Google.

My 2 cents,
-Alex

On 4/6/18, 10:08 AM, "Andrew Wetmore"  wrote:

>No, I am not proposing a migration to something else at this point.
>
>On Fri, Apr 6, 2018 at 2:00 PM, Carlos Rovira 
>wrote:
>
>> I'm not a WP advocate, only use to solve a concrete problem, since I
>>know
>> the time that could be spend in publishing a website, and have it fresh
>> with new content periodically. The problem is that I at least doesn't
>>know
>> other system that make us running so quick. I think other like Drupal or
>> Yoomla should have the same problems. And I'm for sure against making
>>all
>> this work from scratch...since the time invested in that can be huge. Do
>> you know of other system better?
>>
>> thanks
>>
>> 2018-04-06 18:53 GMT+02:00 Andrew Wetmore :
>>
>> > I manage WP sites for several clients and find it the most miserable
>> aspect
>> > of my work schedule.
>> >
>> > On Fri, Apr 6, 2018 at 1:42 PM, Carlos Rovira
>>
>> > wrote:
>> >
>> > > Sometimes we have this problems, but are due to plugins that are not
>> > > completely well designed.
>> > > But think that is better than nothing, since imagine the nightmare
>>of
>> > > making the website from scratch...against put this article in
>>almost no
>> > > time ;)
>> > >
>> > > Sometimes is the price we must pay to go fast and have the time to
>> > > concentrate in our code that is what really matters
>> > >
>> > > 2018-04-06 17:13 GMT+02:00 Andrew Wetmore :
>> > >
>> > > > Thanks for the work-around. I find WP about a -2 on a scale of
>>1-10.
>> > > >
>> > > > On Fri, Apr 6, 2018 at 7:43 AM, Carlos Rovira <
>> carlosrov...@apache.org
>> > >
>> > > > wrote:
>> > > >
>> > > > > Hi Andrew,
>> > > > >
>> > > > > changes live! :)
>> > > > >
>> > > > > I see you had to fight with a WP strange bug that removes the
>>code
>> > > > posted.
>> > > > > The only way I found to avoid this problem is to have your
>>editor
>> > > always
>> > > > in
>> > > > > "Text" mode. Avoid "View" mode since it will remove the code in
>> code
>> > > > > coloring.
>> > > > >
>> > > > > Please, let me know if it's all ok, I had to go to my revision,
>> copy
>> > > the
>> > > > > code and go back to yours and paste the code. So I think it
>>should
>> be
>> > > all
>> > > > > ok.
>> > > > >
>> > > > > Thanks for your revision!
>> > > > >
>> > > > > Carlos
>> > > > >
>> > > > >
>> > > > >
>> > > > > 2018-04-06 12:26 GMT+02:00 Andrew Wetmore :
>> > > > >
>> > > > > > Window closed.
>> > > > > >
>> > > > > > On Fri, Apr 6, 2018 at 7:20 AM, Carlos Rovira <
>> > > carlosrov...@apache.org
>> > > > >
>> > > > > > wrote:
>> > > > > >
>> > > > > > > Thanks Andrew!, I'll publish your revision now, but WP says
>>me
>> > that
>> > > > > > you're
>> > > > > > > still editing. If you finished close the window, so I know
>> you're
>> > > > done
>> > > > > > >
>> > > > > > > thanks! :)
>> > > > > > >
>> > > > > > > 2018-04-06 11:58 GMT+02:00 Andrew Wetmore
>>> >:
>> > > > > > >
>> > > > > > > > Very nice! I ducked in and made a few text edits so the
>>text
>> > > > quality
>> > > > > > > > matches the code quality.
>> > > > > > > >
>> > > > > > > > a
>> > > > > > > >
>> > > > > > > > On Fri, Apr 6, 2018 at 6:42 AM, Carlos Rovira <
>> > > > > carlosrov...@apache.org
>> > > > > > >
>> > > > > > > > wrote:
>> > > > > > > >
>> > > > > > > > > Hi,
>> > > > > > > > >
>> > > > > > > > > you can see and share the new Blog Example on "Using
>>Jewel
>> > > Alert
>> > > > > > > Control"
>> > > > > > > > >
>> > > > > > > > > 
>>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Froyale.ap
>>ache.org%2Fusing-jewel-alert-control%2F=02%7C01%7Caharui%40adobe.com
>>%7C16837928ba4d4c28830108d59be10281%7Cfa7b1b5a7b34438794aed2c178decee1%7C
>>0%7C0%7C636586313073670214=FgGK5%2FjdabKY%2FpJRMI4rJ6M%2FCf8ePjPCsI
>>BG%2F0E2dQg%3D=0
>> > > > > > > > >
>> > > > > > > > > Enjoy and Share!! :)
>> > > > > > > > >
>> > > > > > > > >
>> > > > > > > > > --
>> > > > > > > > > Carlos Rovira
>> > > > > > > > > 
>>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%
>>2Fcarlosrovira=02%7C01%7Caharui%40adobe.com%7C16837928ba4d4c28830108
>>d59be10281%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C63658631307367021
>>4=AhNCwAnsUCovD2Ea%2BpcpCX3KeU8CKA38UJt%2F%2FgT9JNQ%3D=0
>> > > > > > > > >
>> > > > > > > > >
>> > > > > > > >
>> > > > > > > >
>> > > > > > > > --
>> > > > > > > > Andrew Wetmore
>> > > > > > > >
>> > > > > > > > 
>>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fcottage14
>>.blogspot.com%2F=02%7C01%7Caharui%40adobe.com%7C16837928ba4d4c288301
>>08d59be10281%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636586313073670

Re: testing with browserstack. IE11 bad surprise

[Carlos Rovira]

Hi Alex,

I think is better to show you IE11 rendering [1]

I think the image is self explanatory. I didn't analyze it already, maybe
is some huge problem that makes it totally broken, but if not, if I need to
have a complete rendering only for IE11 for each control and component we
have, I think simply doesn't worth it.

I don't want to give up with this already, maybe we can find some easy way
to deal with this, but I want to comment it here so we can have it in mind.

Depending of the effort implied, other variables to have in mind is the
scope of this browser over time. We have deprecated already IE8, IE9 and
IE10, one for year (more or less). If things makes IE11 be almost in no use
in a year, spend lots of time to get that concrete version of IE working
will be a huge waste of time.

Let's analyze more the situation and I'm sure the right way to proceed will
emerge in some days...

Thanks


[1] https://snag.gy/dOgomt.jpg

2018-04-07 17:10 GMT+02:00 Alex Harui :

> IMO, we need Royale to work on IE11.  It does not mean that Jewel must
> work on IE11, but it would be nice if some theme did, other than Basic.
>
> It turns out that my colleagues can't be sure of their data since IE was
> mostly being used for intranet apps in large enterprises, but I think IE
> is being kept around for those large enterprises who are leveraging the
> "plug-in" capabilities of IE.  And I believe that Royale can be attractive
> to those enterprises.
>
> There is a difference between browsers that folks use for browsing the web
> and the app that is used in a mission critical app for the front end.  I
> think MS is saying to use Edge for the first case, but IE is going to be
> around for many more years for the second case.
>
> Does MDL and Bootstrap work on IE?  If so, if you can spend a day figuring
> out why IE11 doesn't work and come up with a simpler variant that does
> work, I think that would benefit Royale.
>
> My 2 cents,
> -Alex
>
> On 4/7/18, 12:42 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira"
>  wrote:
>
> >Hi,
> >
> >since I'm on Mac I was blind to Microsoft browsers.
> >I was testing mainly with Chrome (since is the most used) and Safari
> >(since
> >is what I use to use).
> >I have installed Firefox, but I was not testing in a day by day basis.
> >Never used Opera and Yandex since I doesn't think as relevant
> >
> >For me Browserstack is mostly to test IE11 and Edge, and I found that
> >while
> >Edge has some issues (and Firefox too), both can be fixed for Jewel
> >
> >But the surprise was IE11 this browser is not even near of what it
> >should show, so taking into account that IE is facing its extinction I
> >don't think I should
> >put hours in make that browser work at all. For me IE is the piece of
> >software we should help to be death and buried, since if it's not capable
> >of rendering
> >just a simple button right without lots of hacks, don't want to imagine
> >what other horrors it deserve to us in this journey.
> >
> >It's clear that today IE11 has still an important demographic, but in a
> >year I expect to be cut in favor of Edge that is the MS bet for the
> >future.
> >For me it's not aceptable to need lots of work for only one browser (an
> >version), when users have Chrome, Firefox, Opera, Safari and Yandex and
> >even more
> >
> >To see what I refer I think you should take a test of JewelExample in
> >different browsers. All behaves more or less the same. I see some issues
> >in
> >Edge and Firefox
> >to fix, but if you see the example in IE11 you will literally cry...
> >
> >So what do you think?
> >
> >--
> >Carlos Rovira
> >https://na01.safelinks.protection.outlook.com/?url=
> http%3A%2F%2Fabout.me%2
> >Fcarlosrovira=02%7C01%7Caharui%40adobe.com%
> 7Cfb664630749a424f327708d5
> >9c5b39e8%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%
> 7C636586838017132240
> >data=cCyvy2Hde5H4Rrs%2F75vMKty9ZvMlJxeqi4LSRKkzRjU%3D=0
>
>


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

Fail to build with maven since 00h00'

[Carlos Rovira]

Hi,

I'm suffering a strange situation where I can't rebuild the three repos
with maven as I must do at 00h00' each day.

Now I'm getting this:

Downloading from apache.snapshots:
http://repository.apache.org/snapshots/org/apache/flex/utilities/converter/download-retriever/1.0.0-SNAPSHOT/maven-metadata.xml

[*WARNING*] Could not transfer metadata
org.apache.flex.utilities.converter:download-retriever:1.0.0-SNAPSHOT/maven-metadata.xml
from/to apache.snapshots (http://repository.apache.org/snapshots): Connect
to repository.apache.org:80 [repository.apache.org/207.244.88.140] failed:
Operation timed out

[*WARNING*] Failure to transfer
org.apache.flex.utilities.converter:download-retriever:1.0.0-SNAPSHOT/maven-metadata.xml
from http://repository.apache.org/snapshots was cached in the local
repository, resolution will not be reattempted until the update interval of
apache.snapshots has elapsed or updates are forced. Original error: Could
not transfer metadata
org.apache.flex.utilities.converter:download-retriever:1.0.0-SNAPSHOT/maven-metadata.xml
from/to apache.snapshots (http://repository.apache.org/snapshots): Connect
to repository.apache.org:80 [repository.apache.org/207.244.88.140] failed:
Operation timed out

Someone knows what's happening? Maybe some infra problem?

I'm thinking in open an infra ticket

thanks

Carlos


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

Re: Fail to build with maven since 00h00'

[Carlos Rovira]

Seems is down:

https://twitter.com/infrabot/status/8749194632

2018-04-08 0:22 GMT+02:00 Carlos Rovira :

> Hi,
>
> I'm suffering a strange situation where I can't rebuild the three repos
> with maven as I must do at 00h00' each day.
>
> Now I'm getting this:
>
> Downloading from apache.snapshots: http://repository.apache.org/
> snapshots/org/apache/flex/utilities/converter/download-
> retriever/1.0.0-SNAPSHOT/maven-metadata.xml
>
> [*WARNING*] Could not transfer metadata org.apache.flex.utilities.
> converter:download-retriever:1.0.0-SNAPSHOT/maven-metadata.xml from/to
> apache.snapshots (http://repository.apache.org/snapshots): Connect to
> repository.apache.org:80 [repository.apache.org/207.244.88.140] failed:
> Operation timed out
>
> [*WARNING*] Failure to transfer org.apache.flex.utilities.
> converter:download-retriever:1.0.0-SNAPSHOT/maven-metadata.xml from
> http://repository.apache.org/snapshots was cached in the local
> repository, resolution will not be reattempted until the update interval of
> apache.snapshots has elapsed or updates are forced. Original error: Could
> not transfer metadata org.apache.flex.utilities.
> converter:download-retriever:1.0.0-SNAPSHOT/maven-metadata.xml from/to
> apache.snapshots (http://repository.apache.org/snapshots): Connect to
> repository.apache.org:80 [repository.apache.org/207.244.88.140] failed:
> Operation timed out
>
> Someone knows what's happening? Maybe some infra problem?
>
> I'm thinking in open an infra ticket
>
> thanks
>
> Carlos
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
>


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

Re: Fail to build with maven since 00h00'

[Carlos Rovira]

sorry this one:

https://twitter.com/infrabot/status/982729667323965440

2018-04-08 0:25 GMT+02:00 Carlos Rovira :

> Seems is down:
>
> https://twitter.com/infrabot/status/8749194632
>
> 2018-04-08 0:22 GMT+02:00 Carlos Rovira :
>
>> Hi,
>>
>> I'm suffering a strange situation where I can't rebuild the three repos
>> with maven as I must do at 00h00' each day.
>>
>> Now I'm getting this:
>>
>> Downloading from apache.snapshots: http://repository.apache.org/s
>> napshots/org/apache/flex/utilities/converter/download-retrie
>> ver/1.0.0-SNAPSHOT/maven-metadata.xml
>>
>> [*WARNING*] Could not transfer metadata org.apache.flex.utilities.conv
>> erter:download-retriever:1.0.0-SNAPSHOT/maven-metadata.xml from/to
>> apache.snapshots (http://repository.apache.org/snapshots): Connect to
>> repository.apache.org:80 [repository.apache.org/207.244.88.140] failed:
>> Operation timed out
>>
>> [*WARNING*] Failure to transfer org.apache.flex.utilities.conv
>> erter:download-retriever:1.0.0-SNAPSHOT/maven-metadata.xml from
>> http://repository.apache.org/snapshots was cached in the local
>> repository, resolution will not be reattempted until the update interval of
>> apache.snapshots has elapsed or updates are forced. Original error: Could
>> not transfer metadata org.apache.flex.utilities.conv
>> erter:download-retriever:1.0.0-SNAPSHOT/maven-metadata.xml from/to
>> apache.snapshots (http://repository.apache.org/snapshots): Connect to
>> repository.apache.org:80 [repository.apache.org/207.244.88.140] failed:
>> Operation timed out
>>
>> Someone knows what's happening? Maybe some infra problem?
>>
>> I'm thinking in open an infra ticket
>>
>> thanks
>>
>> Carlos
>>
>>
>> --
>> Carlos Rovira
>> http://about.me/carlosrovira
>>
>>
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
>


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