The documented process [0] is as follows:
[0]
http://download.jboss.org/jbosstools/examples/readme.process.txt
Could developers push things into the "nightly" folder in SVN [1]
instead of the root, thus ensuring not-ready-for-primetime files [2]
don't overlap the good ones?
[1]
http://anonsvn.jboss.org/repos/jbosstools/trunk/download.jboss.org/jbosst...
[2]
http://download.jboss.org/jbosstools/examples/nightly/readme.html
On 01/18/2012 08:50 AM, Max Rydahl Andersen wrote:
Hi,
Today Fred was experimenting with changing project examples for some improvements in B1.
That included renaming some categories which he changed, committed to svn trunk and then
later today
I got 1,2,3 and now 4 mails about examples being broken in M5.
Why ?
Because we have some automatic update script running that takes whatever is latest in
trunk and pushes to the examples site.
We really need to find a better solution for this!
I say *disable* the job and have it only update at controlled times - not automatically.
Anything that needs to use it should have a flag/property to override the urls needed to
do local testing.
But I know that does not scale well - anyone with a bright idea on how to fix this better
?
/max
http://about.me/maxandersen
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com