[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1532) include jar-versions.xml file
Pete Muir (JIRA)
jira-events at lists.jboss.org
Sat Sep 29 18:48:45 EDT 2007
[ http://jira.jboss.com/jira/browse/JBSEAM-1532?page=comments#action_12379444 ]
Pete Muir commented on JBSEAM-1532:
I can if desired (when the maven dependency plugin releases alpha5) write an ant target that will give you a tree report of the current transitive dependency tree.
> include jar-versions.xml file
> Key: JBSEAM-1532
> URL: http://jira.jboss.com/jira/browse/JBSEAM-1532
> Project: JBoss Seam
> Issue Type: Feature Request
> Components: Documentation
> Affects Versions: 1.3.0.ALPHA
> Environment: seam CVS HEAD
> Reporter: Dan Allen
> Priority: Minor
> 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: http://jira.jboss.com/jira/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the seam-issues