cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 33545] - [Enh] Make StatusGenerator show Cocoon version information
Date Sun, 13 Feb 2005 18:48:13 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=33545>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=33545





------- Additional Comments From tschlabach@apache.org  2005-02-13 19:48 -------
I have done some experiments myself, but I am not yet sure about the right approach.

One attempts would be to just use the ${version} from build.properties and place
it in StatusGenerator.java using @version@ and an Ant <replace> task. But this
would probably require an additional step like copying all java source files to
an intermediate directory, then patch them using the <replace> task and compile
from there. I am not sure if this is feasible.

Also of course it would be nice to not only have information on the Cocoon
version as such but also on the Xerces and Xalan versions as they are often the
source of trouble.

It might be possible to access the information in the Manifest.mf. But this
would require the information to be present there. In the Manifest of Cocoon for
example, there is no version information at all.

It might be possible to put it in, though. I did not yet check how other libs
(jakarta-commons-* for example) treat this.

I might also be on the wrong path with this. Maybe one of the Cocoon core
developers could comment on this.


-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Mime
View raw message