Hi, some progress: while re-reading the Felix release guide, the download page can be changed from content/downloads.list (see [1]) , and this file seems to contain some macros which are interpreted by another downloads.cgi script.
Then, when releasing DM, will it be possible to add in the downloads.list file a hardcoded link to the released DM artifacts, which link will be: https://dist.apache.org/repos/dist/release/felix/org.apache.felix.dependencymanager-r1/ <https://dist.apache.org/repos/dist/release/felix/org.apache.felix.dependencymanager-r1/org.apache.felix.dependencymanager-r1-src.zip> ? Now, I would like to make a release soon (we still have to update the website documentation), so it would be cool if other people could take a quick look at https://issues.apache.org/jira/browse/FELIX-4818, in order to check if there is no critical problems with this new release process. Also, does someone knows how to manually release artifacts in maven central ? [1] https://svn.apache.org/repos/asf/felix/site/trunk/content/downloads.list thanks a lot; cheers; /Pierre On Mon, Mar 2, 2015 at 2:32 PM, Pierre De Rop <[email protected]> wrote: > Hi everyone, > > This week I would like to try to make a difficult release for dependency > manager. > > This release is unusual, because we are now building DM using Gradle and > BndTools, but we are not using Maven anymore. > So, because of that, we have to use a different release process, which is > described in [1]. > > For this release, we have used the simplest form of release process, which > is a basic Apache process (see [2]). So, for now, we are not using the > Maven Nexus repository, and we don't release to Maven central, but we'll > possibly try to do that later (by gradually improving our gradle release > script). > > So, before attempting to do that release, I have few questions: > > 1) how is generted the Felix download page (see [3]) ? > > According to [1], we'll put the final released DM archives in the > following Apache release repo locations: > > > https://dist.apache.org/repos/dist/release/felix/org.apache.felix.dependencymanager-r1/org.apache.felix.dependencymanager-r1-src.zip > > https://dist.apache.org/repos/dist/release/felix/org.apache.felix.dependencymanager-r1/org.apache.felix.dependencymanager-r1-deps.zip > > https://dist.apache.org/repos/dist/release/felix/org.apache.felix.dependencymanager-r1/org.apache.felix.dependencymanager-r1-bin.zip > (and all *.asc, *.sha, *.md5 signatures for each archives above) > > The -src.zip will contain the whole bndtools source workspace for DM; the > -deps.zip will contain the build-time binaries being part of the bndtools > source DM workspace, and the -bin.zip file will contain the DM binary > bundles (for convenience). > > I guess that the Felix download page won't be able to display these three > zip files ? > Then how could I deal with this problem ? Is it possible to manually > update the Felix download page, by just adding some links in the page (that > will point to > https://dist.apache.org/repos/dist/release/felix/org.apache.felix.dependencymanager-r1/ > ?) > > 2) for this new release process, we are not using the nexus repository and > we are not release to maven central (we'll try to do that in a later > release). > But is there is way to do this manually using the nexus web admin ?. I > don't know if this is even possible since we are not using the nexus > staging repo ? > Any idea about how to do that manually ? > > 3) Then, is it possible to manually upload the released binary artifacts > (from the -bin.zip) in the Felix OBR ? > > Many thanks for your help. > > cheers; > /Pierre > > [1] https://issues.apache.org/jira/browse/FELIX-4818 > [2] http://www.apache.org/dev/release.html > [3] http://felix.apache.org/downloads.cgi >
