Probably no need. But it can't hurt. On Nov 1, 2007, at 5:35 PM, Orion Letizi wrote:
> Juris, > > Is this something that should go in the documentation about the forge? > > --Orion > > On Nov 1, 2007, at 4:19 PM, Juris Galang wrote: > >> If you own a project in the Forge and it's almost done (ie: you >> still have to round-up some loose-ends like documentation and >> project site generation stuff) but would still like to make its >> artifact available from our maven-repo, then you can add an entry >> in the terracotta.forge config file >> >> publish 'your-project', :except => [:site_deploy] >> >> What this means is that the next time the forge publication script >> runs, it will checkout your project, run tests, and deploy its >> artifacts to our maven repository but it will NOT publish the >> project's website. >> >> Likewise, if your project's tests are not yet ready, you could do >> something like: >> >> publish 'your-project', :except => [:site_deploy, :test] >> >> Basically saying: don't generate the project's website or run any >> of its tests. >> >> The terracotta.forge config file is very simple; you can check it >> out to add your project for publication from svn like so: >> >> svn co https://svn.terracotta.org/repo/forge/projects/forge- >> publish-script/trunk/terracotta.forge >> >> >> _______________________________________________ >> tc-dev mailing list >> [email protected] >> http://lists.terracotta.org/mailman/listinfo/tc-dev > > _______________________________________________ > tc-dev mailing list > [email protected] > http://lists.terracotta.org/mailman/listinfo/tc-dev _______________________________________________ tc-dev mailing list [email protected] http://lists.terracotta.org/mailman/listinfo/tc-dev
