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 <aha...@adobe.com> Gesendet: Freitag, 14. November 2014 07:04 An: 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, "Erik de Bruin" <e...@ixsoftware.nl> wrote: >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-too >l-api-1.0.0-source-release/flex-tool-api-1.0.0/DEPENDENCIES > >******************************* > >EdB > > > >On Thu, Nov 13, 2014 at 2:00 PM, Alex Harui <aha...@adobe.com> wrote: > >> Hi Chris, >> >> +1 (binding) >> >> Looks good, especially for a first time releasing Apache Flex stuff. >> >> Couple of things: >> >> 1) The artifacts are not viewable from the browser. The browser just >> serves the pom.xml file. But they are there and the approval scripts >>get >> them. >> >> 2) The script couldn’t find your key. Can you add your key to the KEYS >> file in flex-sdk and push it to >> https://dist.apache.org/repos/dist/release/flex/ or I can push it to >>dist >> after you update KEYS in flex-sdk. >> >> I grabbed your key from a keys server and then the signature could be >> verified. When you get to ApacheCon, see if you can get Justin to sign >> your key. >> >> I pushed an approval script to the repo. Anybody who wants to use it to >> test the build can choose the script or perform the steps individually >> some other way. To use the approval script, make sure you have both Ant >> and Maven installed and in your PATH, then copy the script to an empty >> folder and from that folder type: >> >> ant -e -f ApproveFlexToolAPI.xml -Drelease.version=1.0.0 >> >> Wasn’t sure what tests to run, so I just dumped the main jar and saw it >> had the right number of .class files and a reasonable MANIFEST.MF. >> >> >> Congratulations! >> >> -Alex >> >> >> On 11/13/14, 5:03 AM, "Christofer Dutz" <christofer.d...@c-ware.de> >>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 tools (most prominent one: the >>compiler) >> >to be used by external tools (Mainly Flexmojos for now). It doesn't >> >provide any new features to Flex itself from a users point of view. >> > >> > >> >Using the Flex Tool API a project can provide an implementation of the >> >FlexToolGroup interface and register the tools it provides (MXMLC, >>COMPX, >> >DIGEST, etc.). There is also a FlexToolRegistry implementation that >>will >> >return any FlexToolGroups available in the current classpath. >> > >> > >> >As soon as this module is released, I will update the Flex SDK, Flacon >> >and FalconJX to provide tool groups. >> > >> >? >> > >> >Now a little explanation as this is the first time we are doing a >>release >> >of a Maven project here: >> > >> > >> >There is a public location where you should be able to download the >> >artifacts: >> > >> >>https://repository.apache.org/service/local/repositories/orgapacheflex-10 >>0 >> >0/content/org/apache/flex/flex-tool-api/1.0.0/ >> > >> > >> >As far as I understood it this Artifact will be the one we are voting >>on: >> > >> > >> >>https://repository.apache.org/service/local/repositories/orgapacheflex-10 >>0 >> >>>0/content/org/apache/flex/flex-tool-api/1.0.0/flex-tool-api-1.0.0-source >>>-r >> >elease.zip >> > >> > >> >If you have a login to the Nexus, things can be a lot more comfortable >> >though. >> > >> >Simply go to: >> >https://repository.apache.org/index.html#stagingRepositories and login. >> >Here you will have a nice Web UI for browsing the release. As soon as >>you >> >have logged in, select: Staging >> >Repositories<https://repository.apache.org/index.html#> in the Build >> >Promotion section of the Navigation on the left hand side. >> > >> > >> > * As soon as you have selected the repository orgapacheflex-1000 >>you >> >can select the tab: Content and have a look at the repository content. >> > >> > >> >If the vote passes, I will set Close the Staging repository and hereby >> >release the artifacts to Apaches Maven Repo. If it fails, I will drop >>the >> >repo and nothing will be released. >> > >> > >> >Chris >> > >> >> > > >-- >Ix Multimedia Software > >Jan Luykenstraat 27 >3521 VB Utrecht > >T. 06-51952295 >I. www.ixsoftware.nl
