I'm ready if you are.
On 5/5/14 5:22 PM, "OmPrakash Muppirala" wrote:
>I updated the badge, it should now point to installer 3.0 for downloads.
>
>Also, I updated installer configs 4.0, 3.1 and 3.0 to point to correct
>version of the installer binary. This is so that the auto-update
>mechanism
I updated the badge, it should now point to installer 3.0 for downloads.
Also, I updated installer configs 4.0, 3.1 and 3.0 to point to correct
version of the installer binary. This is so that the auto-update mechanism
kicks in.
If no one has objections, I will go ahead and push these changes to
On 5/5/14 2:47 PM, "Christofer Dutz" wrote:
> I think for this we need to setup a dedicated technical user. But we
>probably need to order this from Infra. @Alex ... could you request this?
>As soon as you provide me with the credentials I'll whip up a
>settings.xml that should enable our Jenkin
Hi,
> Ok ... so the first BlazeDS 4.7-SNAPSHOT is now available:
> https://repository.apache.org/content/repositories/snapshots/org/apache/flex/blazeds/
Looking at the source:
It's missing a LICENCE and NOTICE file - they would be need before we could
make a release. Does this apply to the SNAP
Ok ... so the first BlazeDS 4.7-SNAPSHOT is now available:
https://repository.apache.org/content/repositories/snapshots/org/apache/flex/blazeds/
Unfortunately I had to deploy these snapshots from my local machine. In order
to have the Jenkins automatically deploy the nightly build snapshots, we n
Ok ... thanks ... I can see now that I can do Admin stuff, but I'm still
missing one permission that only Infra can grant me ... I opened an issue on
this and hopefully they will resolve this quickly.
https://issues.apache.org/jira/browse/INFRA-7678
Chris
-Ursprüngliche Nachricht-
Von:
It will be almost identical ... it's not missing anything that the Adobe
version had, you are just able to provide a BlazeDS configuration from the
applications Classpath (Was actually allways missing this feature and now I
needed to implement this for the tests). So in any case changing the old
Sounds good.
Do you feel confident we have the right pieces and nothing is missing?
IOW, will the flex-messaging-common.jar be the equivalent or better than
the one we download from Adobe?
Thanks,
-Alex
On 5/5/14 1:18 PM, "Christofer Dutz" wrote:
>Ok ... so I just committed a major update to
OK, try again.
On 5/5/14 1:15 PM, "Christofer Dutz" wrote:
>Thanks for that ... I was trying to setup a Agile Board for BlazeDS and
>FlexUnit ... it seems I don't have the Karma to do this ... would it be
>ok if you sort of upgraded me a little, so I could setup this stuff
>myself?
>
>-Urspr
Ok ... so I just committed a major update to BlazeDS ... now we should be able
to publish SNAPSHOTS from Nightly builds and the Testsuite no longer needs a
server up and running.
I even had to implement a new Feature allowing to configure a BlazeDS server
using a configuration located in the cla
Thanks for that ... I was trying to setup a Agile Board for BlazeDS and
FlexUnit ... it seems I don't have the Karma to do this ... would it be ok if
you sort of upgraded me a little, so I could setup this stuff myself?
-Ursprüngliche Nachricht-
Von: Alex Harui [mailto:aha...@adobe.com]
OK, should be there now.
On 5/5/14 12:48 PM, "Christofer Dutz" wrote:
>Hi,
>
>could anyone with enough karma please create a component "BlazeDS" (or
>similar) and a version (4.7) for BlazeDS ... I would like to create some
>Issues describing what I did and to reference them in my commit.
>
>Chri
Hi,
could anyone with enough karma please create a component "BlazeDS" (or similar)
and a version (4.7) for BlazeDS ... I would like to create some Issues
describing what I did and to reference them in my commit.
Chris
Afe is one of the embedded font manager libraries. To get rid of it, we
have to write our own font manager.
On 5/5/14 12:58 AM, "Christofer Dutz" wrote:
>OK well I guess we could resolve one part of the problem.
>
>As the flex-messaging-common.jar is now part of Apache Flex, as soon as
>we have
I'll take a look.
On 5/5/14 7:53 AM, "Erik de Bruin" wrote:
>The Japanese lang test is failing since the version number was 'reverted'.
>
>Who wants to take a look?
>
>EdB
>
>
>
>
>On Mon, May 5, 2014 at 3:16 PM, wrote:
>
>> flex-sdk_mustella - Build # 891 - Still Failing:
>>
>> http://flex-mus
The Japanese lang test is failing since the version number was 'reverted'.
Who wants to take a look?
EdB
On Mon, May 5, 2014 at 3:16 PM, wrote:
> flex-sdk_mustella - Build # 891 - Still Failing:
>
> http://flex-mustella.cloudapp.net/job/flex-sdk_mustella/891/
>
> Changes for Build #888
> [a
Spreading the word in Spain and LATAM! :)
2014-05-04 6:22 GMT+02:00 DarkStone :
> Congraturations!
>
> I've spread the word to China just now.
>
> Keep up the great works!
>
>
> DarkStone
> 2014-05-04
>
>
>
> --
> View this message in context:
> http://apache-flex-development.247.n4.nabble.c
OK well I guess we could resolve one part of the problem.
As the flex-messaging-common.jar is now part of Apache Flex, as soon as we have
a release out the door, we could download the binary from maven-central or the
Apache Maven server. That should be able to handle the load easily.
Would leav
18 matches
Mail list logo
