Ok so I just added the 4 documents to the project ... should be ok now :-) Would this slightly modified, but more Maven-like workflow be ok?
I create a Jenkins job on the official Apache Jenkins (As this is the 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 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 pull the binary artifacts from Apaches Maven Repositories, so I would have to simply change the url as soon as it's released. Sticking exactly to the process you described would make things more complicated as this is intended for ANT builds and not for normal Maven projects (Releasing stuff is a lot easier with Maven) So if you give me an ok, I would start a Discuss thread. Chris ________________________________________ Von: Alex Harui <aha...@adobe.com> Gesendet: Montag, 10. November 2014 21:54 An: dev@flex.apache.org Betreff: Re: Flex SDK implementing flex-tool-api On 11/10/14, 1:21 AM, "Christofer Dutz" <christofer.d...@c-ware.de> 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 >develop branch? It doesn't change any functionality, It just allows to >automate the tools easier. +1 for trying the merge as long as you’ll be around to revert it if something blows up (which I doubt will happen). > > >If you are ok with the flex-tool-api I would like to stage a first >release candidate and cast a vote on it's release. > > >@Justin ... could you please have a look at the mini module of the >flex-tool-api (in flex-utils) and ge me some feedback if any legal things >are still missing? Don't know if we need any README or LICENSE files. > IMO, it should have LICENSE and NOTICE for Apache policy reasons, and README and RELEASE_NOTES for consistency with other releases. We are trying to practice a new release workflow. IMO, the next steps would be: 1) create a jenkins build on apacheflexbuilds.cloudapp.net or elsewhere (probably not daily, just on Git changes) that produces (at minimum) the source packages (zip and tar.gz) and the jar. 2) Point folks at the Jenkins output artifacts and open a [DISCUSS] thread. 3) find some way to get the SDK and Falcon builds to use the .jar produced from the jenkins builds. Once we see enough PMC folks have reviewed the source package then you can open a {VOTE] thread for final approval. -Alex
