]
Pete Muir updated JBSEAM-1532:
------------------------------
Issue Type: Task (was: Feature Request)
Component/s: (was: Documentation)
Fix Version/s: 2.0.x
Assignee: Pete Muir
include jar-versions.xml file
-----------------------------
Key: JBSEAM-1532
URL:
http://jira.jboss.com/jira/browse/JBSEAM-1532
Project: JBoss Seam
Issue Type: Task
Affects Versions: 1.3.0.ALPHA
Environment: seam CVS HEAD
Reporter: Dan Allen
Assigned To: Pete Muir
Priority: Minor
Fix For: 2.0.x
Original Estimate: 4 hours
Remaining Estimate: 4 hours
It would be so helpful if a jar-versions.xml file could be kept up to date in the root of
the seam source code to track the versions of the bundle libraries, in the absence of
other solutions. This idea comes from the JBoss AS, which uses this file to communicate
the versions of libraries used.
Documenting the versions helps:
1. developers, who may find challenge in combining APIs of libraries without knowing the
version
2. users who are unable to determine the contents of what they downloaded
3. for legal reasons, just in case there are differences in licenses amongst releases of
third party products, to protect seam itself as well as integrators of seam.
With all that said, the better solution is to use ant-ivy or maven2 to get the jar files
out of the source code. But I digress.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: