Re: [Treebase-devel] Is TreeBASE down?

[Rutger V. <rut...@gm...>]

Sure, but maybe it's a starting point. Are we talking about the same
sort of principle where there is some point in the output produced by
the webapp where we (and other users) can see "release XXX, revision
YYY"?

By the way, this would be nice to have both in html and in other
produced files, potentially. E.g. to diagnose the provenance of
inconsistencies in produced nexus/nexml/rdf.

On Mon, Mar 29, 2010 at 11:06 PM, Hilmar Lapp <hl...@ne...> wrote:
> Rutger - we really need a release identifier that is displayed, so users and
> everyone else can report it. A hidden svn revision will not solve this.
>
>        -hilmar
>
> On Mar 29, 2010, at 6:00 PM, Rutger Vos wrote:
>
>> If you look in the html source of any page and you scroll all the way
>> down to 'p class="footerLogo"' it will show the SVN revision of that
>> deployment. At least, this used to work back when MJD and I were using
>> the 'publish' script, which used
>>
>> ${TREEBASE_HOME}/treebase-core/src/main/java/org/cipres/treebase/Version.java
>> as a little servlet to embed the SVN revision in  the footer.jsp (this
>> is done by deleting and then updating this version file). Perhaps this
>> can be re-instated?
>>
>> On Mon, Mar 29, 2010 at 10:01 PM, Vladimir Gapeyev
>> <vla...@du...> wrote:
>>>
>>> On Mar 29, 2010, at 4:39 PM, Hilmar Lapp wrote:
>>>
>>> This should be in the tracker as a feature request already. Is it not?
>>> -hilmar
>>> On Mar 29, 2010, at 4:34 PM, Jon Auman wrote:
>>>
>>> I suggested to Vladimir last week that we should put a version and
>>> timestamp
>>> on the builds, like we do with nead.nescent.org. (ex. Version:
>>> 2.2.1   Built: 03/26/2010 12:43 PM )
>>> Otherwise, how can we keep track of which version we are on?
>>> -Jon
>>> On Mar 29, 2010, at 4:31 PM, Hilmar Lapp wrote:
>>>
>>> I'll check and, if it is not there, will put a ticket for the suggestion,
>>> alongside tickets for a few other things we need to do here on the
>>> deployment side (restore the dev server; set up automatic builds, etc.).
>>> The 659 version will be deployed to production soon.
>>> --VG
>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Download Intel&#174; Parallel Studio Eval
>>> Try the new software tools for yourself. Speed compiling, find bugs
>>> proactively, and fine-tune applications for parallel performance.
>>> See why Intel Parallel Studio got high marks during beta.
>>> http://p.sf.net/sfu/intel-sw-dev
>>> _______________________________________________
>>> Treebase-devel mailing list
>>> Tre...@li...
>>> https://lists.sourceforge.net/lists/listinfo/treebase-devel
>>>
>>>
>>
>>
>>
>> --
>> Dr. Rutger A. Vos
>> School of Biological Sciences
>> Philip Lyle Building, Level 4
>> University of Reading
>> Reading
>> RG6 6BX
>> United Kingdom
>> Tel: +44 (0) 118 378 7535
>> http://www.nexml.org
>> http://rutgervos.blogspot.com
>>
>>
>> ------------------------------------------------------------------------------
>> Download Intel&#174; Parallel Studio Eval
>> Try the new software tools for yourself. Speed compiling, find bugs
>> proactively, and fine-tune applications for parallel performance.
>> See why Intel Parallel Studio got high marks during beta.
>> http://p.sf.net/sfu/intel-sw-dev
>> _______________________________________________
>> Treebase-devel mailing list
>> Tre...@li...
>> https://lists.sourceforge.net/lists/listinfo/treebase-devel
>
> --
> ===========================================================
> : Hilmar Lapp  -:- Durham, NC -:- informatics.nescent.org :
> ===========================================================
>
>
>
>



-- 
Dr. Rutger A. Vos
School of Biological Sciences
Philip Lyle Building, Level 4
University of Reading
Reading
RG6 6BX
United Kingdom
Tel: +44 (0) 118 378 7535
http://www.nexml.org
http://rutgervos.blogspot.com