You can automate the deployment of SNAPSHOT versions using Apache Jenkins Credentials. It's simply that they have vonfigured Jenkins to use a settings.xml in which the server tags are filled with the credentials of a technical user we can use to deploy stuff.
Releases can never be automatic as all releases have to go to a special staging repo. Regarding the working of the distribution ... well I only take binaries and copy them and add a text file. If the dependency structure you named works, so shoud the snapshots. I would like to ask someone who actually uses Squiggly to eventually give this a test drive. I have no idea how to use it ... as far as I understood it's an "online spell checker thigy" ... correct? ;-) Chris -----Ursprüngliche Nachricht----- Von: Justin Mclean [mailto:jus...@classsoftware.com] Gesendet: Sonntag, 31. August 2014 03:26 An: dev@flex.apache.org Betreff: Re: [DISCUSSION] Squiggly 1.0 release candidate 0 Hi, > Glad that it's now working :-) Well making a snapshop and the snapshop and 100% working may be two different things. Mind checking the contents for me? > When running on the Apache Jenkins this automatically works. Good to know, but making a release is still a manual process right via https://oss.sonatype.org? Thanks, Justin
