Hi Justin, well I think this might be an issue. Maven releases need pom.xml files that accompany the jars. There is quite a list of requirements to the content of these poms. They then need to be signed and published to the staging repo. Then we need to vote on the release and as soon as the vote passes, we can release the staging repo.
So I doubt it would be allowed to manually stage the jar files and then simply release them. Guess it would be best if I started adding the maven-ant-target stuff (Which I added to Falcon) to the other parts we want to release so in the future we could do this in one step. Chris -----Ursprüngliche Nachricht----- Von: Justin Mclean [mailto:jus...@classsoftware.com] Gesendet: Sonntag, 24. August 2014 13:11 An: dev@flex.apache.org Betreff: Re: Releasing BlazeDS, FlexUnit and Mavenizer Hi, > Ok so would it be ok to take the released artifacts and to stage them in > Apaches Staging Maven Repo? Or would this have to be a new release? As they are already a release I see zero issues with that. May or may not need a VOTE to move it into the release area? sorry but I'm not sure of the process. I assume you have read [1]. Thanks, Justin 1. http://www.apache.org/dev/publishing-maven-artifacts.html
