On 11/14/14, 11:01 PM, "Justin Mclean" wrote:
>HI,
>
>Also of a concern is that the pom.xml in version control doesn't match
>the one in the distribution. That's probably a blocker and needs to be
>fixed.
I pulled the pom.xml for the hash in the tag. It matched the distribution
for me. What
HI,
Also of a concern is that the pom.xml in version control doesn't match the one
in the distribution. That's probably a blocker and needs to be fixed.
Thanks,
Justin
Hi,
> I don’t think we agreed to use international English, so utilize should
> have a ‘z’.
Nor have we agreed on using American English, more of our user base uses
English other than American English if you look at the Google stats. Off top of
head of the the English speakers about 30-40% of t
Hi,
I've also made an attempt to fix the pom, but don't 100% really know what I'm
doing or what the values typically should be.
The SCM section incorrectly referred to SVN rather than Git, while I've fixed
that I'm fairly certain the SMC entries developer and developerConnection are
still inco
I don’t think we agreed to use international English, so utilize should
have a ‘z’.
>-You can always checkout the latest source via git using the following
>-command:
>+You can always checkout the latest source from Apache's source
>control repository
>+using the following commands
Hi,
> Regarding any mis-spellings ...
I made some fixes/improvements, feel free to alter as you see fit.
I'm certainly not an expert when it come to the English language and I'm sure
there's many foreign speakers that spell better than me (as they learnt it
rather than absorbed it). Going to
Hi,
> With 4 +1 and 2 +0 binding votes, we have a very valid release.
We certainly do and it's up the the RM if they want to release it or, assuming
no one changes their vote between now and until when the 72 hours are up.
Thanks,
Justin
We just can't help ourselves. can we?
With 4 +1 and 2 +0 binding votes, we have a very valid release. Let's leave
it at that, so the other sub-projects can benefit from this release, and
not try to make a big deal of improvements that don't affect the utility of
this utility at all. If the tool ca
>
> All it would take is create a new RC build and upload the artifacts to the
> dist site.
>
I take that back. I forgot we are releasing via maven. Even so, I think
we should make one more RC.
Thanks,
Om
> On Fri, Nov 14, 2014 at 5:09 PM, Christofer Dutz <
> christofer.d...@c-ware.de> wrote:
>
>
> There's a few minor spelling errors in the README etc, Several PMC members
> have considered these blockers in the past (I don't consider them as such).
> As they don't object to them now I can only assume that's no longer the
> case for this release or any other future releases.
>
Please li
Hi,
> I forgot to manually push the tag ... after doing so the tag should now be
> available.
Thanks.
> So I guess this issue can be treated as resolved.
And the other pom issues?
> Regarding any mis-spellings ...
Depends on if you going to make another release or not, given this in unlik
+0 Binding.
Lets get in the latest changes because we want to release this only once.
Thanks,
Om
On Fri, Nov 14, 2014 at 9:03 AM, Justin Mclean
wrote:
> Hi,
>
> +0 until issues in discussion are sorted, while none are probably
> blockers, the version control path being incorrect may cause issu
Hi,
> I doubt that it makes sense to release something just for releasing the
> changes to the release procedure, so if it's up to me, I don't need another
> release ;-)
There are possibly other minor issues with this release. eg The wrong version
control path in pom - isn't that going to caus
I hate to be that guy, but lets get all the changes so far (even the ones
that affect only the release process) and make the one and only release
perfect.
All it would take is create a new RC build and upload the artifacts to the
dist site.
And I propose that votes be carried over from the first
I forgot to manually push the tag ... after doing so the tag should now be
available.
So I guess this issue can be treated as resolved.
Regarding any mis-spellings ... well ... why don't you just fix what you found,
cause just saying "there are spelling errors" sort of isn't that much help.
Well you were right ... it pushed my tag ... was sort of expecting that to
happen automatically ... well ... you never stop learning :-)
I doubt that it makes sense to release something just for releasing the changes
to the release procedure, so if it's up to me, I don't need another release ;-
Well if you guys wouldn't have been so active in accepting donations, we now
wouldn't have the work with releasing that stuff ;-) (Just kidding)
Well ... in my pipeline there will definitely be BlazeDS and FlexPMD coming in
the near future. But I guess we will use the new flex-ci-build profile i
Given the rate at which Chris is contributing, I'm sure we'll have a hard
time just trying to keep up with the votes ;-)
EdB
On Fri, Nov 14, 2014 at 4:17 PM, Alex Harui wrote:
>
>
> On 11/14/14, 2:07 PM, "Erik de Bruin" wrote:
>
> >>
> >> >I would suggest to release the staged ones and use t
On 11/14/14, 2:07 PM, "Erik de Bruin" wrote:
>>
>> >I would suggest to release the staged ones and use the optimized pom
>>for
>> >the next release.
>>
>> OK, but is there going to be a next release? I was hoping for
>> one-and-done.
>>
>
>Let's not drag this out. This is a utility release, an
>
> >I would suggest to release the staged ones and use the optimized pom for
> >the next release.
>
> OK, but is there going to be a next release? I was hoping for
> one-and-done.
>
Let's not drag this out. This is a utility release, and 'good enough to
work with' should mean 'good enough to rel
On 11/14/14, 1:13 PM, "Christofer Dutz" wrote:
>Hi,
>
>Actually I did create that tag ... wonder why it wasn't transferred to
>the Apache Git ... do Tags not get pushed automatically?
I think in Git you need to "push --tags”.
>
>I would suggest to release the staged ones and use the optimized
Hi,
Actually I did create that tag ... wonder why it wasn't transferred to the
Apache Git ... do Tags not get pushed automatically?
As we did a little tweaking of the poms after the vote was initiated and the
artifacts were published to the staging repo, I would suggest to release the
staged o
On 11/14/14, 11:41 AM, "Frédéric THOMAS" wrote:
>Ok thanks, will do it tomorrow as Im out tonight. You sure u cant get it
>from my patch though ?
I’m sure I could. If it isn’t that urgent, can it wait until you are next
at home? That way you will get the credit you deserve.
-Alex
Ok thanks, will do it tomorrow as Im out tonight. You sure u cant get it from
my patch though ?
--- Message initial ---
De : "Alex Harui"
Envoyé : 14 novembre 2014 19:49
A : dev@flex.apache.org
Objet : Re: Re : Re: [GitHub] flex-utilities pull request: Update
apache-flex-spelling-framework...
Fred, Email the file to me off list.
On 11/14/14, 10:17 AM, "Frédéric THOMAS" wrote:
>Thanks guys for the explaination, unfortunately cant work from home at
>the moment, will check with the company Im working with at the moment if
>they allow me to setup a dev sdk, etc...
>
>--- Message initial
>
> What you write below is why Maven is hard. Because it wraps up complex
> patterns into small entities like commands and profiles, you aren’t always
> able to tell what is going to happen until you try it. Whereas in Ant,
> you can always read the script. But that’s not to say it is bad, it j
Hi,
> IMO, I’d just make sure the tag is in Git and ship what we have voted on.
As git tag are mutable strictly the original vote should have the commit that
was voted on. This has come up on the incubator many times in recent months,
although in this case it's reasonably obvious even without
Thanks guys for the explaination, unfortunately cant work from home at the
moment, will check with the company Im working with at the moment if they allow
me to setup a dev sdk, etc...
--- Message initial ---
De : "OmPrakash Muppirala"
Envoyé : 14 novembre 2014 18:33
A : dev@flex.apache.org
Ob
Yes, the release manager gets to vote on the release. Do these config
changes invalidate the vote? IMO, I’d just make sure the tag is in Git and
ship what we have voted on.
(everything below is not important, just me musing about Maven and Ant)
What you write below is why Maven is hard. Because
Fred, we cannot merge pull requests from GitHub, because we dont have
admin access. We have to download the patch and apply to the Apache Git
repo. And if we add a magic comment in the format: "This closes #", the PR gets closed automatically.
I think in this case, you just have to commit the c
Makes sense. Won’t hurt, might help.
Regarding merging the PR, what error are you getting? Don’t forget that
the ASF GH repos are read-only. There is a whole workflow for taking PR
into the actual ASF Git repos. And since you are a committer, it’d
probably be faster to simply copy the modified
My web outlook is very shitty today, sorry.
> Given that squiggly is on the small size is there a huge need for RSLs? Don't
> mind either way, just curious to why you would need them.
I have an Air app that downloads modules, I try to make them as small as
possible because some of our clients hav
> Looks like windows only? That may be an issue.
Right, never did Ant for other platforms, does someone know how I could solve
that ?
Frédéric THOMAS
> Subject: Re: [GitHub] flex-utilities pull request: Update
> apache-flex-spelling-framework...
> From: jus...@classsoftware.com
> Date: Sat, 15
Hi,
+0 until issues in discussion are sorted, while none are probably blockers, the
version control path being incorrect may cause issues. Given this is not going
to be released often, may be best to fix this now?
Thanks,
Justin
Hi,
I was trying to use Squiggly and felt on this issue, being at work, I went thru
github to fix it but noticed I hadn't got the right karma to merge pull
requests.Does someone can do something ?
An other thing, Squiggly does come with RSLs, I can try to fix that in the week
if I find a bit
Hi,
> output="${output.dir}/flex-optimizer-@{swc-name}.log" append="true">
Looks like windows only? That may be an issue.
Given that squiggly is on the small size is there a huge need for RSLs? Don't
mind either way, just curious to why you would need them.
Thanks,
Justin
Erratum: "Squiggly does come with RSLs", I mean't "Squiggly does not come with
RSLs"
PS: I will need to update the Maven part too indeed if it's ok for you.
Thanks,
Frédéric THOMAS
From: webdoubl...@hotmail.com
To: dev@flex.apache.org
Subject: RE: [GitHub] flex-utilities pull request: Update
ap
GitHub user doublefx opened a pull request:
https://github.com/apache/flex-utilities/pull/3
Update apache-flex-spelling-framework.pom
Misspelling of apache-flex-linguistic-utils instead of
apache-flex-spelling-linguistic-utils
You can merge this pull request into a Git repository b
Done.
And: +1 (binding)
EdB
On Fri, Nov 14, 2014 at 12:04 AM, Alex Harui wrote:
> I didn’t add it to the RAT excludes, but it appears to be a notice file
> like README, RELEASE_NOTES, CONTRIBUTING, etc, so I think it is ok. Feel
> free to add it to the RAT excludes.
>
> -Alex
>
> On 11/13/1
Hi,
This is a TourDeFlex 1.2 Release Candidate 1. Please see the RELEASE_NOTES and
the README.
Changes since the last RC:
- Changes to how 3rd party examples are shown (simple image and link)
- Commented out some of the 3rd party examples
- Fixed issue with Squiggly spelling engine examples
Th
Hi,
Please place all discussion here and not in the VOTE thread.
Thanks,
Justin
Hi,
I'm jet lagged and still travelling so please excuse any sillly mistakes I make
here.
- LICENSE and NOTICE correct
- all source files have correct headers
- no binaries in release
- can compile from source
Only minor things I noticed where:
- The artefact name should have "apache" in it as
Hi,
I just thought I would write down the reasons for me putting that much effort
in adding Maven support to Flex. I know that currently most people will be
using Ant builds or FlashBuilder builds. Nevertheless I think Maven is
essential.
1. For the last 4 years I have been working as a cons
That file is automatically created during the release (I think by the assembly
plugin if the apache-release profile is active) ... you won't find that
anywhere in the repository.
Chris
Von: Alex Harui
Gesendet: Freitag, 14. November 2014 07:04
An: dev@f
Hi Alex,
ok ... I'll write one mail summing up all ;-)
1. First of all ... it was not that Maven isn't able to, it was just that it
wasn't configured to. Unfortunately I didn't have the time to spend on
fine-tuning the build as I did want to get FlexJS flying ;-)
2. In the apache master pom th
Here's how to install Maven on Windows:
http://www.mkyong.com/maven/how-to-install-maven-in-windows/
Thanks,
Om
On Nov 13, 2014 11:19 PM, "Alex Harui" wrote:
>
>
> On 11/13/14, 11:03 PM, "piotrz" wrote:
>
> >Now it's working. Thanks once again.
> >
> >Build failed using approve file. I got this
46 matches
Mail list logo
