I think I'll whip up something in my +1 day today. Well usually you deploy the jar/swc/rsl whatever and if you're really nice you bundle the source zipped up in a jar together with the binary to allow IDEs to show the code.
Well the minimum requirement to such a pom would be minimal, but it sems apache wants some stuff to go into the root artifact of a release. I have to setup this metadata only once as I bet JIRA, Maven-Repo, CI-Server, License etc. will be the same for all modules we release. Chris ________________________________________ Von: Justin Mclean <jus...@classsoftware.com> Gesendet: Donnerstag, 28. August 2014 14:04 An: dev@flex.apache.org Betreff: Re: [DISCUSSION] Squiggly 1.0 release candidate 0 Hi, > Well it's a SWC isn't it? Several swcs - look in the libs directory. > Eventually all we have to do is write a pom with it's dependencies and an > Apache header, repo, license block etc and manually stage that RC in the > staging repo. Just the swcs or the code as well? Given this is reasonably simple what would the pom look like? Thanks, Justin
