Hi,
In order to be able to run the EXTERNC tool using the flex-tool-api, I need a
name for the tool.
I would have chosen "EXTERNC", but as recently there have been discussions on
replacing this, I would like to ask if there eventually is a better, more
general, name for this that
Congratulations and thanks for not giving up ;-)
I also don't see a need to do an announcement, as you say, it is a small
utility, not meant for public consumption.
EdB
On Thu, Nov 20, 2014 at 10:20 AM, Christofer Dutz wrote:
> YE!
>
>
> Ok so it seems the vote passed with 6 +1, 0 +0
YE!
Ok so it seems the vote passed with 6 +1, 0 +0 and 0 -1
alex +1 (binding)
piotr +1 (binding)
erik +1 (binding)
chris +1 (binding)
justin +1 (binding)
om +1 (binding)
Will be switching the staging repository to release the artifacts. As the
posting of announce messages seems to be
+1 Binding
Tested:
http://repository.apache.org/content/repositories/orgapacheflex-1003/org/apache/flex/flex-tool-api/1.0.0/flex-tool-api-1.0.0-source-release.zip
Windows 7 64 bit, Java 1.8
MD5 checksum matches
Good signature from "Christofer Dutz "
Tool compiles without errors using m
Hi,
Checked the latest RC all good, changing my vote to +1 (binding).
Thanks,
Justin
Hi,
> Justin, Erik is right. You should try to be more careful.
I do try to be careful but I made a mistake. I have no issue with constructive
criticism. My response was trying to inject a little humour into the situation
and perhaps point out we're being IMO a little silly about this. There sh
One of the phrases I try to practice is this [1]. It gives the assumption
that the text doesn't convey jokes and sarcasm well.
[1] "Assume positive intent".
-Mark
>
> Erik, I’m not sure Justin takes criticism very well from you. It might be
> more effective if you leave that to someone else.
>
I'm afraid you're right :-(
Thanks for taking this one. I'll refrain from commenting any more on this
or future instances (of which I hope there will be few).
EdB
Justin, Erik is right. You should try to be more careful. I’m a native English
speaker and I had to read it more than once to make sure I read it right. I was
not sure if you were referring to a specific tag. There’s no reason to get
defensive. Take it for what it was: constructive criticism.
E
Hi,
> "what what teh"?
I don't think we need remind people every time they get a a letter out of place
or autocorrect picks the wrong word. Not matter how careful you are mistakes
are sill going to slip though.
Also:
Aoccdrnig to rscheearch at Cmabrigde Uinervtisy, it deosn't mttaer in waht
o
Hi,
I just dropped the RC3 staging repo and created a new one RC4
(orgapacheflex-1003) which should contain all the pom-fixes we recently
discussed. Now the README is fixed and all assembly descriptors have Apache
headers.
You can have a look at the staging repo at:
https://repository.apache.
Von: Justin Mclean
Gesendet: Dienstag, 18. November 2014 10:48
An: dev@flex.apache.org
Betreff: Re: [DISCUSS] Release Apache Flex Tool API 1.0.0 RC2
Hi,
Just had a look at RC3 and looks like with still have the pom tag issue;
apache-flex-tool-api-1.0.0-RC3
Shouldn't this point what
>
> Shouldn't this point what what teh tag will be when the software is
> released?
>
"what what teh"?
Please be more careful writing emails, as per our recent consensus on email
etiquette. Mistakes in spelling easily translate into misunderstandings
about intend. There is no hurry when dealing w
Hi,
Just had a look at RC3 and looks like with still have the pom tag issue;
apache-flex-tool-api-1.0.0-RC3
Shouldn't this point what what teh tag will be when the software is released?
Justin
+1
Package
https://repository.apache.org/content/repositories/orgapacheflex-1002/org/a
pache/flex/flex-tool-api/1.0.0/flex-tool-api-1.0.0-source-release.zip
Java 1.7
OS: Mac OS X x86_64 10.9.5
Source kit signatures match: y
Source kit builds: y
README is ok: y
RELEASE_NOTES is ok: y
NOTICE is ok
Hi,
I just dropped the RC2 staging repo and created a new one RC3
(orgapacheflex-1002) which should contain all the pom-fixes we recently
discussed. Now the README is fixed and all assembly descriptors have Apache
headers.
You can have a look at the staging repo at:
https://repository.apache.
@flex.apache.org
Betreff: Re: [DISCUSS] Release Apache Flex Tool API 1.0.0 RC2
I ran rat, it didn't catch anything but the DEPENDENCIES, for which I added
an exception. Are these files platform specific?
And the 'nits', you can basically do what you think is best, but at the
risk of s
I ran rat, it didn't catch anything but the DEPENDENCIES, for which I added
an exception. Are these files platform specific?
And the 'nits', you can basically do what you think is best, but at the
risk of starting another huge thread about nothing: either en_US or en_GB
are perfectly fine for the
Ugh, somehow we all missed the fact that there aren’t Apache headers on
assembly/assemble*.xml. Can anyone think of a way we can make an
exception? Are they auto-generated? Did they come from somewhere else?
Do the lack any creativity? Otherwise we have to roll an RC3. I checked
in Apache head
Hi,
so I learned a lot more this time.
First of all: If you follow the normal release path of "mvn release:prepare"
"mvn release:perform" the tags arent created correctly. You have to set the
version to the release version and set the tag property manually, commit and
tag that commit manuall
Hi,
I just dropped the RC1 staging repo and created a new one RC2
(orgapacheflex-1001) which should contain all the pom-fixes we recently
discussed. Now the README is fixed as well as the scm section in the pom. Also
the tags should now match niceley.
I'm carrying over the votes of RC1:
al
fu**ing up my
> motivation to contribute at all.
>
> Chris
>
> ____
> Von: Justin Mclean
> Gesendet: Samstag, 15. November 2014 09:11
> An: dev@flex.apache.org
> Betreff: Re: [DISCUSS] Release Flex-Tool-API?
>
> Hi,
>
&
Hi,
> I sort of don't get the problem.
The released pom.xml has this:
scm:svn:https://git-wip-us.apache.org/repos/asf/flex-utilities.git/tags/flex-tool-api-1.0.0-RC1
scm:svn:https://git-wip-us.apache.org/repos/asf/flex-utilities.git/tags/flex-tool-api-1.0.0-RC1
The paths are incorrect
> Hmmm ... well I prepared the release (Removed the SNAPSHOT from the
> version) and tagged that version so it's exactly the version in the
> distribution.
>
> After publishing the release version, I updated the version of the project
> for the next development iteration to 1.1.0-SNAPSHOT. This is
Fix it ... discussing such
things in lengthy email threads is totally fu**ing up my motivation to
contribute at all.
Chris
Von: Justin Mclean
Gesendet: Samstag, 15. November 2014 09:11
An: dev@flex.apache.org
Betreff: Re: [DISCUSS] Release Flex-Tool-API?
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.
Sorry ignore that it does look OK - myself and git were having a disagreement.
It does look to me that perhaps the tag/build was done
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'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
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,
> 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
only one mailing list is listed
it probably should be the dev one
2. scm details look incorrect to me (looks like
https://git-wip-us.apache.org/repos/asf/flex-utilities.git/tags/flex-tool-api-1.0.0-RC1
doesn't exist and that would not be the final URL right?) Probably need to be
fixed befor
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
> >
> >Unapproved licenses:
> >
> >
> >/Users/erik/Documents/ApacheFlex/git/flex-utilities/flex-tool-api/flex-too
> >l-api-1.0.0-source-release/flex-tool-api-1.0.0/DEPENDENCIES
> >
> >***
> >
> >EdB
obably should be the dev one
2. scm details look incorrect to me (looks like
https://git-wip-us.apache.org/repos/asf/flex-utilities.git/tags/flex-tool-api-1.0.0-RC1
doesn't exist and that would not be the final URL right?) Probably need to be
fixed before releasing.
3. Does the target/sou
: dev@flex.apache.org
Betreff: Re: [VOTE] Release Apache Flex Tool API 1.0.0
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/14, 9:14 PM, "Eri
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
On 11/13/14, 11:03 PM, "piotrz" wrote:
>Now it's working. Thanks once again.
>
>Build failed using approve file. I got this error ->
>http://images.devs-on.net/Image/dwQgNsHuJ2hoVFNB-Obszar.png
Can you run mvn on the command-line? Maybe in Windows it needs to be
mvn.exe?
-Alex
e.com/VOTE-Release-Apache-Flex-Tool-API-1-0-0-tp42314p42342.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
.
Piotr
-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/DISCUSS-Release-Flex-Tool-API-tp42286p42341.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
On 11/13/14, 10:23 PM, "piotrz" wrote:
>Thanks Alex,
>
>This web site is password protected -> http://keys.gnupg.net
>How can I login there ?
I just get a web page where I can type in a key id. No login required.
Try this server: https://pgp.mit.edu
-Alex
Thanks Alex,
This web site is password protected -> http://keys.gnupg.net
How can I login there ?
Piotr
-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/DISCUSS-Release-Flex-Tool-API-tp42286p42339.html
S
g of this and why I'm seeing
>this and why it is/is not a problem, I intend to vote +1 (binding) as
>well:
>
>***
>
>Unapproved licenses:
>
>
>/Users/erik/Documents/ApacheFlex/git/flex-utilities/flex-tool-api/flex-too
>l-api-1.0.0
Depending on if someone can explain the meaning of this and why I'm seeing
this and why it is/is not a problem, I intend to vote +1 (binding) as well:
***
Unapproved licenses:
/Users/erik/Documents/ApacheFlex/git/flex-utilities/flex-tool-api/flex-tool-api-
On 11/13/14, 2:47 PM, "piotrz" wrote:
>Alex,
>
>I didn't want to mess a VOTE thread so asking here.
>What do you mean saying "I grabbed your key from a keys server and then
>the
>signature could be verified. " ? - Probably I miss something obvious.
>Where is this "keys server".
Good move switc
Alex,
I didn't want to mess a VOTE thread so asking here.
What do you mean saying "I grabbed your key from a keys server and then the
signature could be verified. " ? - Probably I miss something obvious.
Where is this "keys server".
I wanted to vote for Chris
AM, "Christofer Dutz" wrote:
>Hi,
>
>
>I just staged a first release candidate of the Apache Flex Tool API 1.0.0
>at Apaches maven staging repository.
>
>
>The Flex Tool API is a simple set of generally two interfaces which
>allows it to easily use the Flex to
Hi,
I just staged a first release candidate of the Apache Flex Tool API 1.0.0 at
Apaches maven staging repository.
The Flex Tool API is a simple set of generally two interfaces which allows it
to easily use the Flex tools (most prominent one: the compiler) to be used by
external tools
, 3:05 PM, "Christofer Dutz" wrote:
>Hi Alex,
>
>changing the name of the module to "apache-flex-tool-api" wouldn't be a
>problem. Usually the apache is implicitly given by the group-id ... the
>full name of the artifact is: org.apache.
Hi Alex,
changing the name of the module to "apache-flex-tool-api" wouldn't be a
problem. Usually the apache is implicitly given by the group-id ... the full
name of the artifact is: org.apache.flex:flex-tool-api
but changing this to: org.apache.flex:apache-flex-tool-api i not
unzip and README is in the root. In the
flex-tool-api package, the unzip results in a folder with all of the files
in it.
Otherwise, I would be good to go.
On 11/12/14, 2:16 PM, "Christofer Dutz" wrote:
>During the actual release this all happens automatically.
>
>As I sai
y published. If the RC is denied, I simply delete the
repo and all is gone without leaving a trace.
Chris
Von: Alex Harui
Gesendet: Mittwoch, 12. November 2014 23:28
An: dev@flex.apache.org
Betreff: Re: AW: AW: [DISCUSS] Release Flex-Tool-API?
I’ve run Mav
on creating an RC all would be
>staged in the staging repository and you could have a look there. Do you
>want me to prepare one?
>
>Chris
>
>
>Von: Alex Harui
>Gesendet: Mittwoch, 12. November 2014 23:11
>An: dev@flex.apache.org
one?
Chris
Von: Alex Harui
Gesendet: Mittwoch, 12. November 2014 23:11
An: dev@flex.apache.org
Betreff: Re: AW: [DISCUSS] Release Flex-Tool-API?
On 11/12/14, 2:05 PM, "Christofer Dutz" wrote:
>I just remember what the problem was that
On 11/12/14, 2:05 PM, "Christofer Dutz" wrote:
>I just remember what the problem was that as part of a release each file
>of a release is signed and as soon as I turn on the apache-release
>profile it expects credentials for this signing process.
So is there a way to set an alternative “goal”
lugin are not available.
Chris
Von: Christofer Dutz
Gesendet: Mittwoch, 12. November 2014 21:47
An: dev@flex.apache.org
Betreff: AW: [DISCUSS] Release Flex-Tool-API?
In a "install" run the needed parts of maven don't run as they come when
try tomorrow.
Chris
Von: Alex Harui
Gesendet: Mittwoch, 12. November 2014 18:31
An: dev@flex.apache.org
Betreff: Re: [DISCUSS] Release Flex-Tool-API?
On 11/12/14, 6:53 AM, "Christofer Dutz" wrote:
>If you run:
>
>
>mvn -Papache-release ins
On 11/12/14, 6:53 AM, "Christofer Dutz" wrote:
>If you run:
>
>
>mvn -Papache-release install
Chris,
Is there any reason we can’t add this to the CI build? It will save folks
time trying to poke at what might get released.
-Alex
Hi Guys,
I have finished implementing the flex-tool-api in the flex-sdk, falcon,
falconjy and Flexmojos and all seems to be playing together nicely. During the
process I added some minor changes to my initial version but now I think it's
as finished as it needs to be. So I would li
In which case I suggest we try to release flex-tool-api in the next few
weeks, so the 4.14 release can proceed on schedule (whatever that may mean,
I intend to be flexible with the dates, but only up to a point ;-))
EdB
On Tue, Nov 11, 2014 at 3:49 PM, Alex Harui wrote:
>
>
> On 11
On 11/11/14, 1:42 PM, "Christofer Dutz" wrote:
>That's why I will only merge my stuff to develop after we have released
>the flex-tool-api.
>When using Maven you start paying very detailed attention to stuff like
>this :-)
Technically and legally, you can merge
On 11/11/14, 1:40 PM, "Christofer Dutz" wrote:
>Hi Alex,
>
>the reason for this is that these artifacts are only created if the maven
>profile "apache-release" is enabled.
>I didn't want to turn that on cause I was a little afraid that doing a
>deploy with enabled apache-release profile could d
That's why I will only merge my stuff to develop after we have released the
flex-tool-api.
When using Maven you start paying very detailed attention to stuff like this :-)
Chris
Von: Justin Mclean
Gesendet: Dienstag, 11. November 2014 21:59
An
it to.
Chris
Von: Alex Harui
Gesendet: Dienstag, 11. November 2014 18:50
An: dev@flex.apache.org
Betreff: Re: AW: Flex SDK implementing flex-tool-api
Sorry, somehow hit send. The link is:
https://builds.apache.org/view/E-G/view/Flex/job/flex-tool-api/
Then click on “
HI,
Be careful here, we may have issues releasing something (ie the SDK) if it
contains unreleased Apache software. [1] As example of this issue was [2] which
was solved by Thrift making a release.
Thanks,
Justin
1.
http://incubator.apache.org/guides/releasemanagement.html#best-practice-sourc
Sorry, somehow hit send. The link is:
https://builds.apache.org/view/E-G/view/Flex/job/flex-tool-api/
Then click on “Last Successful Artifacts”
-Alex
On 11/11/14, 9:35 AM, "Alex Harui" wrote:
>Chris,
>
>I added last successful artifacts to the build and ran a new build
” URL always.
>
>-Alex
>
>On 11/11/14, 2:29 AM, "Christofer Dutz" wrote:
>
>>And for the last requirement:
>>Here's the link to the last stable build:
>>https://builds.apache.org/view/E-G/view/Flex/job/flex-tool-api/lastBuild/
>>
>>So I wou
then the jars produced should be available at the
“lastSuccessfulBuild” URL always.
-Alex
On 11/11/14, 2:29 AM, "Christofer Dutz" wrote:
>And for the last requirement:
>Here's the link to the last stable build:
>https://builds.apache.org/view/E-G/view/Flex/job/flex-too
And for the last requirement:
Here's the link to the last stable build:
https://builds.apache.org/view/E-G/view/Flex/job/flex-tool-api/lastBuild/
So I would be glad for some feedback in order to get that project released so I
can merge my changes in flex-sdk and falcon back to develop (Curr
Well I just adjusted the pom of the module and now I have 4 resulting files:
- flex-tool-api-1.0.0-SNAPSHOT.jar (Containing the actual binary build)
- flex-tool-api-1.0.0-SNAPSHOT-sources.jar (Containing only the sources ...
used by IntelliJ for auto-downloading the sources of third party libs
Hi,
I would be surprised if it wouldn't be accepted as a .jar is a .zip, is it an
immutable legal thing ?
Frédéric THOMAS
> From: aha...@adobe.com
> To: dev@flex.apache.org
> Subject: Re: Flex SDK implementing flex-tool-api
> Date: Tue, 11 Nov 2014 05:08:18 +
>
>
On 11/10/14, 4:01 PM, "Justin Mclean" wrote:
>HI,
>
>>> I don’t think we can vote on sources in jars, or do you know for a
>>>fact that other Maven releases do this?
>
>Yes they do see [1]. For recent examples on the incubator take a look at
>Apache Parquet or Calcite (last few days) or the Mav
HI,
>> I don’t think we can vote on sources in jars, or do you know for a fact that
>> other Maven releases do this?
Yes they do see [1]. For recent examples on the incubator take a look at Apache
Parquet or Calcite (last few days) or the Mavin project itself. [2][3][4]
Justin
1. http://www.a
ding releases.
>
>Chris
>
>-Ursprüngliche Nachricht-
>Von: Alex Harui [mailto:aha...@adobe.com]
>Gesendet: Montag, 10. November 2014 23:45
>An: dev@flex.apache.org
>Betreff: Re: AW: Flex SDK implementing flex-tool-api
>
>
>
>On 11/10/14, 2:09 PM, "Chri
]
Gesendet: Montag, 10. November 2014 23:45
An: dev@flex.apache.org
Betreff: Re: AW: Flex SDK implementing flex-tool-api
On 11/10/14, 2:09 PM, "Christofer Dutz" wrote:
>Ok so I just added the 4 documents to the project ... should be ok now
>:-)
>
>Would this slightly mo
gt;only place I can have the SNAPSHOT version deployed to Apaches Maven
>repository. https://builds.apache.org/view/E-G/view/Flex/job/flex-tool-api
You can definitely use builds.a.o, but I think we need to see “last
successful artifacts” at that link that contains the source zip and tar.gz
files (a
.
https://builds.apache.org/view/E-G/view/Flex/job/flex-tool-api
The build would automatically create the complete API docs and create the
source jars, but this is only done for a release build. For snapshot builds
this doesn't happen automatically.
I already extended the Ant builds to pul
On 11/10/14, 1:21 AM, "Christofer Dutz" wrote:
>Hi,
>
>
>After staging a first snapshot of the flex-tool-api, I created a
>feature-branch of the SDK to implement this API. Could you please have a
>look and give any comment if it would be Ok to merge that back to the
On 11/10/14, 1:16 AM, "cd...@apache.org" wrote:
>+unless="flexToolApi.jar.exists"
>+description="Downloads and copies flex-tool-api.jar to the
>lib directory.">
>+
>+src="http://repository.apache.org/content/g
Hi,
After staging a first snapshot of the flex-tool-api, I created a feature-branch
of the SDK to implement this API. Could you please have a look and give any
comment if it would be Ok to merge that back to the develop branch? It doesn't
change any functionality, It just allows to aut
t;.
>
> What do you think?
>
> Chris
>
>
> Von: Christofer Dutz
> Gesendet: Mittwoch, 5. November 2014 09:51
> An: dev@flex.apache.org
> Betreff: flex-tool-api
>
> Hi,
>
>
> has anyone had a look/any comment on my
t exist. Available
tool groups 'DEFAULT'".
What do you think?
Chris
Von: Christofer Dutz
Gesendet: Mittwoch, 5. November 2014 09:51
An: dev@flex.apache.org
Betreff: flex-tool-api
Hi,
has anyone had a look/any comment on my proposed tool api project that would
Hi,
has anyone had a look/any comment on my proposed tool api project that would
allow managing of the various implementations of compilers in the FDK?
I have taken my thoughts a little further. While implementing the PMD
modularization I encountered the
Java SerivceLoder mechanism and I wou
84 matches
Mail list logo
