On Thu, Aug 5, 2010 at 7:47 PM, Stuart McCulloch <[email protected]> wrote: > On 6 August 2010 00:07, David Savage <[email protected]> wrote: > >> On Thu, Aug 5, 2010 at 5:00 PM, Stuart McCulloch <[email protected]> >> wrote: >> > ---> http://felix.apache.org/site/release-management-nexus.html >> >> Right I guess I could push it to a mvn repo - but not sure if that'll >> be any use for eclipse bundles - if people want to test them that is. >> > > for non-maven builds it's probably easiest to make the staged release > available from your account on people.apache.org under ~/public_html > > ( see http://tuscany.apache.org/making-releases.html for an example )
Thanks that looks like a very useful set of notes - I'll dig through and come up with something... > > >> Does nexus support generation of an update site for a set of >> features/plugins? If so that'd be great... >> > > nexus-pro has support for p2 update sites, not sure about generating > them from a set of binaries - of course you could use tycho for that :) > > ( http://tycho.sonatype.org ) Yeah that's a possibility :) I'd like to hook in the sigil resolver to Tycho eventually and have the basic plan of what to do. It's just never quite yet become the priority. I currently have a pretty simple groovy script [1] for generating the old style eclipse update site which works for now with eclipse. Guess I may need to move to the p2 format update site at some point... Thinking about it in the medium term possibly I need to do both, publish the artifacts to maven for maven/tycho builds to consume and build an update site for eclipse to download. Hmmm ponders... Regards, Dave [1] https://svn.apache.org/repos/asf/felix/trunk/sigil/bldcommon/updatesite.groovy > > >> Regards, >> >> Dave >> > > -- > Cheers, Stuart >
