Details

    • Type: Task
    • Status: Closed (View Workflow)
    • Priority: Minor
    • Resolution: Done
    • Affects Version/s: 1.3.0.ALPHA
    • Fix Version/s: 2.1.0.A1
    • Component/s: Build
    • Labels:
      None
    • Environment:

      seam CVS HEAD

    • Affects:
      Documentation (Ref Guide, User Guide, etc.)
    • Estimated Difficulty:
      Medium

      Description

      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.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                pmuir Pete Muir
                Reporter:
                dan.j.allen Dan Allen
              • Votes:
                2 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 4 hours
                  4h
                  Remaining:
                  Remaining Estimate - 4 hours
                  4h
                  Logged:
                  Time Spent - Not Specified
                  Not Specified