[
http://jira.dspace.org/jira/browse/DS-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=10801#action_10801
]
Larry Stone commented on DS-377:
--------------------------------
That's true, the value embedded in dspace.cfg probably would get out of date.
It looks like the maven "resources" plugin can interpolate maven properties
into arbitrary resource files, see
http://maven.apache.org/plugins/maven-resources-plugin/ ...but I'll hold off
on using it until Mark verifies that it doesn't cause obnoxious problems in
builds like the overlay feature. If it can be used safely, then I think the
cleanest thing to do is add a filtered resource file to dspace-api, and a Utils
method to fetch its value, e.g. Utils.getVersion() => "DSpace 1.6.0"
> Add META tags identifying DSpace source version to Web UIs
> ----------------------------------------------------------
>
> Key: DS-377
> URL: http://jira.dspace.org/jira/browse/DS-377
> Project: DSpace 1.x
> Issue Type: New Feature
> Components: DSpace API, JSPUI, XMLUI
> Affects Versions: 1.6.0
> Reporter: Larry Stone
> Assignee: Larry Stone
> Priority: Minor
> Fix For: 1.6.0
>
> Attachments: version-meta.patch.txt
>
>
> Add a META tag to the HTML generated for each web-UI page that identfies the
> version of the DSpace source running on the site. This lets administrators
> and developers tell at a glance what their test servers are running, and
> curious visitors see what version of DSpace is behind a production site.
> The change is very simple and automated in action. Maven is already doing
> property-substitution on the dspace.cfg file, so let it plug in the verison
> of the "dspace" project (under group "org.dspace"), which should always be
> the same as the released or snapshot project for the source tree. From there
> it's a simple matter of putting it in a pageMeta element for the XMLUI.
> NOTE: This still needs a volunteer to either implement it for JSPUI or point
> out the most efficient way to do -- I'll be happy to code and test but I
> don't know the JSPUI well enough to spot the most effective place to put a
> META tag that goes on every page.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.dspace.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
