Hi Chris, I’m not sure I’m asking to change the module name per-se. I’m just noting that the source zips I looked up on dist.a.o starts with the word “apache”, even Maven. I don’t know what the protocol or pattern is for group-id or artifacts or module names are in Maven. Looks like the maven repository builder artifacts on repository.a.o don’t start with “apache”. Maybe we should just leave it alone and rename the file when posting it on dist.a.o?
When I unpack our other Flex source packages on my Mac via Ant it creates the README file in the destination folder. This package created README inside a folder within the destination folder. However, I just tried it from Mac Finder and it did the right thing, so I guess just ignore this issue. I think you are probably good to go if you can generate .md5 and .asc files for the source zip. Thanks for working on it. -Alex On 11/12/14, 3:05 PM, "Christofer Dutz" <christofer.d...@c-ware.de> 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.flex:flex-tool-api >but changing this to: org.apache.flex:apache-flex-tool-api i not problem >at all. > >I just re-checked and unpacked the zip file. The result is the 5 text >files, the pom.xml and the src directory and this contains the normal >file structure. So what's wrong with this? > >Chris > >________________________________________ >Von: Alex Harui <aha...@adobe.com> >Gesendet: Mittwoch, 12. November 2014 23:43 >An: dev@flex.apache.org >Betreff: Re: AW: AW: [DISCUSS] Release Flex-Tool-API? > >OK, finished looking. > >Everything looks ok, except I think we need md5 and .asc files for the >source-release.zip file and md5 for the other jars would be helpful. > >Some minor/optional stuff: >1) Could/should the package name start with “apache-“? All of our other >releases do. >2) Our other packages 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" <christofer.d...@c-ware.de> wrote: > >>During the actual release this all happens automatically. >> >>As I said ... you should be able to see the results by simply running the >>maven build locally. As soon as I intend 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 <aha...@adobe.com> >>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" <christofer.d...@c-ware.de> >>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” (is that the right word >>that is equivalent to an Ant target?) that will be more like “build” >>instead of “install” and doesn’t try the signing. Also, it would be >>great >>to have MD5 files generated for each download. Is that hard to do? >> >>-Alex >>
