AW: [DISCUSS] [BlazeDS] Release of Apache BlazeDS 4.7.0.0 RC1

2015-03-02 Thread Christofer Dutz
No objections from my side. Chris Gesendet mit meinem HTC - Reply message - Von: Justin Mclean jus...@classsoftware.com An: dev@flex.apache.org dev@flex.apache.org Betreff: [DISCUSS] [BlazeDS] Release of Apache BlazeDS 4.7.0.0 RC1 Datum: Mo., Mär. 2, 2015 08:22 Hi, If it’s making you

AW: [DISCUSS] [BlazeDS] Release of Apache BlazeDS 4.7.0.0 RC1

2015-03-01 Thread Christofer Dutz
Hi Justin, thanks for looking into this. I'll go through your comments one by one: - I tagged the release RC1 cause it was the RC1 and I remember having trouble deleting and re-adding a tag. If it's not a problem to delete a tag, I'd be glad to change this. - Do you suggest to call the

AW: [DISCUSS] [BlazeDS] Release of Apache BlazeDS 4.7.0.0 RC1

2015-03-01 Thread Christofer Dutz
Thinking about it again I think we don't need the apache in front of the artifact as it's allready part of the groupId. The official name of the artifact is: Org.apache.flex.blazeds:flex-messaging-{module} So I don't think we need the apache in the artifact name again ... and with the

AW: [DISCUSS] [BlazeDS] Release of Apache BlazeDS 4.7.0.0 RC1

2015-03-01 Thread Christofer Dutz
Ah ... ok ... so that's easy ... now the name will be apache-flex-blazeds-{version} I also saw that I had already prepared the creation of a zip and tar-gz source distribution, all I have to do is activate another maven profile ... will definitely do that for RC2 Chris -Ursprüngliche

AW: [DISCUSS] [BlazeDS] Release of Apache BlazeDS 4.7.0.0 RC1

2015-02-27 Thread Christofer Dutz
Unfortunately not that I am aware of. I have tested it by switching my projects, that I have BlazeDS running in to the new version and they worked perfectly. Chris Von: Tom Chiverton t...@extravision.com Gesendet: Freitag, 27. Februar 2015 12:12 An: