Well it's a SWC isn't it? A mavenized form isn't a different release, it's more an additional location for placing the released binaries. 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. I think we could use the Ant Maven Tasks to so this from ant cause you need to sign the pom with the same certificate as the binary (I think).
Perhaps it would be good if I created a pom template and an Ant code snippet tat we can use to deploy SNAPSHOT versions and to stage release versions. So we can simply extend the zoo of little projects to release maven artifacts. Chris ________________________________________ Von: Justin Mclean <jus...@classsoftware.com> Gesendet: Donnerstag, 28. August 2014 13:38 An: dev@flex.apache.org Betreff: Re: [DISCUSSION] Squiggly 1.0 release candidate 0 Hi, > As we noticed with FlexUnit that simply releasing Maven artifacts of a > previously released library isn't that easy (From Apache procedures ... the > releasing itself is easy), I think we should think about releasing the maven > artifacts together with the normal release. So how do we release both at once? And do users actually need a mavenized version of Squiggly? Justin
