Not sure what you are talking about. We do have takes for the artifacts in svn. They are in the releases dir. We just don't have a tag for the trunk at that point but only for the individual subprojects just like felix is doing it as well (and sling iirc).
http://svn.apache.org/repos/asf/incubator/ace/releases/ regards, Karl On Thu, Nov 17, 2011 at 3:39 PM, Bertrand Delacretaz <bdelacre...@apache.org> wrote: > (moving thread here from general@incubator.a.o) > > On Thu, Nov 17, 2011 at 3:07 PM, Karl Pauls <karlpa...@gmail.com> wrote: >> $ mkdir org.apache.ace.client.automation-0.8.0-incubator >> $ cd org.apache.ace.client.automation-0.8.0-incubator/ >> $ wget >> http://www.apache.org/dist/incubator/ace/org.apache.ace.client.automation-0.8.0-incubator-source.jar >> $ jar -xf org.apache.ace.client.automation-0.8.0-incubator-sources.jar >> $ wget >> http://www.apache.org/dist/incubator/ace/org.apache.ace.client.automation-0.8.0-incubator.pom >> $ mv org.apache.ace.client.automation-0.8.0-incubator.pom pom.xml >> $ mvn clean install > > I agree with others that having an svn tag for that release would be > much more convenient, and it's the expected way. IIRC you're only > expected to keep the latest release under /dist, so the above URLs > will change over time, and it's too easy to delete those files by > mistake. > > What prevents you from creating svn tags when releasing bundles? > > Sling does release bundles individually, and we do have svn tags under > http://svn.apache.org/repos/asf/sling/tags/ > > -Bertrand > -- Karl Pauls karlpa...@gmail.com http://twitter.com/karlpauls http://www.linkedin.com/in/karlpauls https://profiles.google.com/karlpauls
