Sounds good :-) And I would assume that Apache would allow releases using Maven after all ... Maven is an Apache project. So I guess they build it in a way that they can actually use it (Eat their own dogfood)
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, "Christofer Dutz" <christofer.d...@c-ware.de> wrote: >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 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 (and md5 files for them). > >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 don’t think we can vote on sources in jars, or do you know for a fact that other Maven releases do this? Maven Central has jars for lots of Apache projects, but those projects also seem to have source tar.gz and zip files as their non-Maven, but official Apache release artifacts. I also just realized that as part of release approval we’re supposed to get a source package and run a build script packaged with it that creates the jar. We’ve used Ant for everything so far, but it should be ok to require us to use Maven for this one. >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. Just to be clear, I would expect the Discuss thread to have a link to a lastSuccessfulBuild on build.a.o, similar to what we have for Tour De Flex [1]. We will pull the source packages, examine the four notice files you submitted and follow the steps in the README to get a jar and somehow test that it is the right jar. Will that work for you? -Alex [1] http://s.apache.org/6ea Shortened from: apacheflexbuild.cloudapp.net:8080/job/flex-utilities_tour-de-flex-release/l astSuccessfulBuild/artifact/TourDeFlex/TourDeFlex3/out/
