NatTable has its own download directory, /nattable It's generally better to leverage the "flat" directory structure.
URLs are shorter. Project moves are easier and less traumatic on user and adopter communities. Wayne On 09/12/2012 01:48 PM, Wim Jongman wrote: > Think about where to put things: > > > technology/nebula/nattable > > is a good start but you need versions. for example you could decide to > push the result of your automatic build to: > > technology/nebula/nattable/snapshot > > Then, you can push releases to > > technology/nebula/nattable/juno > technology/nebula/nattable/kepler > > or whatever you decide to name your releases. > > and so on. > > finally you need a symbolic link to the latest release in the form of > > technology/nebula/nattable > > Something like that. The first is an automatic process, the others are > manual tasks. whenever you release, copy the happy snapshot to the > release directory. > > Best regards, > > Wim > > On Wed, Sep 12, 2012 at 6:28 PM, Mickael Istria <[email protected] > <mailto:[email protected]>> wrote: > > Hi, > > > On 09/12/2012 06:03 PM, Edwin Park wrote: >> 1. Sign jars with the Eclipse cert > We directly sign the generated update-site. This is done using the > |eclipse-signing-maven-plugin|, See > > http://git.eclipse.org/c/nebula/org.eclipse.nebula.git/tree/releng/org.eclipse.nebula.updatesite/pom.xml > fpr an example of usage. After you invoked this plugin, the signed > repo is available in target/checksumFix folder. > You'll notice we use a profile, since this plugin only works on > build.eclipse.org <http://build.eclipse.org>. > > Another plugin is available, but I never tried it. > >> 2. Create p2 repository > See same pom: it's an eclipse-repository packaging type, and it > uses a category.xml to define the content of the repository. > Category.xml has same syntax as site.xml, so you can simply rename > a site.xml you like into category.xml > > >> Also, when we release our binaries on build.eclipse.org >> <http://build.eclipse.org> I was thinking of putting them under >> /shared/technology/nebula/nattable. Let me know if that's ok with >> you guys. > Build.eclipse.org <http://Build.eclipse.org> is not recommanded > for publishing stuff. You should use download.eclipse.org > <http://download.eclipse.org> instead, that you can access from > most Ecipse machines through folder > /home/data/httpd/download.eclipse.org <http://download.eclipse.org>. > > See the configuration of Jenkins job for exemple of build > invocation and publishing > https://hudson.eclipse.org/hudson/job/nebula.nebula/configure > > HTH > -- > Mickael Istria > Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools> > My blog <http://mickaelistria.wordpress.com> - My Tweets > <http://twitter.com/mickaelistria> > > _______________________________________________ > nebula-dev mailing list > [email protected] <mailto:[email protected]> > https://dev.eclipse.org/mailman/listinfo/nebula-dev > > > > _______________________________________________ > nebula-dev mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/nebula-dev -- Wayne Beaton The Eclipse Foundation Twitter: @waynebeaton Explore Eclipse Projects <http://www.eclipse.org/projects>
_______________________________________________ nebula-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/nebula-dev
