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 artifacts
Hi,
> - 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.
No issue with the tag in git, it's the fact that it part of the release that's
an issue. The pom.xml in the r
(Forgot to include dev)
-- Forwarded message --
From: "Mihai Chira"
Date: 1 Mar 2015 11:30
Subject: Re: [jira] (FLEX-34756) How to know when the textFlow is damaged?
To: "Alex Harui"
Cc:
Good idea, Alex, thanks. I'll do just that next week.
And yes, that's exactly why I need the
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 flex
Hi,
> 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.
I was referring to the name of the of the source zip file. Having apache in the
name gives a little more legal protection, but it's not a requirement.
Justin
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 Nachr
I just deployed an RC2 ... will start a new thread.
Chris
-Ursprüngliche Nachricht-
Von: Justin Mclean [mailto:jus...@classsoftware.com]
Gesendet: Sonntag, 1. März 2015 07:47
An: dev@flex.apache.org
Betreff: Re: [VOTE] [BlazeDS] Release of Apache BlazeDS 4.7.0.0 RC1
Hi,
+0 binding for
Hi guys,
As I won't have time to do so in the next few days, I decided to spin a new RC
today. I just staged the second RC for BlazeDS 4.7.0. It is available at:
https://repository.apache.org/content/repositories/orgapacheflex-1005/
This version is a parity release to Adobe BlazeDS 4.6.0.0
This is the new discussion thread for RC2 of BlazeDS
Chris
HI,
+1 (binding) everything checks out
I checked:
- signatures and hashes correct
- LICENCE and NOTICE correct
- all files have Apache header
- no binary files in release
- can compile from source
- all tests pass
Minor issues (not blockers/can be done next release):
- Signed by non apache signa
I've taken a long look at it, and it really won't be that bad. We will
need to update some of the UI sections to account for some of the changes
we made in the last bit.
I estimate that it would take about 40 man-hours to get it up to snuff,
including replacing the graphics and updating the UI/Se
On 2/28/15, 11:12 PM, "Justin Mclean" wrote:
>Hi,
>
>One thing I did noticed about the code is the large number of @author
>tags. This is generally frowned on in Apache. [1][2] Should we remove
>them?
If it’s making you itch, go ahead and scratch it.
-Alex
Hi,
> If it’s making you itch, go ahead and scratch it.
Anyone else have any objections to removing them? If not and once I have time
I'll remove them.
Thanks,
Justin
13 matches
Mail list logo
