Tapestry
  1. Tapestry
  2. TAPESTRY-60

current build (2003-7-23 cvs version) uses jdom, but doesn't bring it in from anywhere

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Resolution: Incomplete
    • Affects Version/s: 3.0
    • Fix Version/s: None
    • Component/s: Build
    • Labels:
      None
    • Environment:
      Operating System: Other
      Platform: Other

      Description

      cvs head as of 2003-7-23 needs JDom. However, there appears to be no inclusion
      of jdom.jar from anywhere (internal or external), so the build breaks.

        Activity

        Mark Thomas made changes -
        Workflow Default workflow, editable Closed status [ 12568938 ] jira [ 12591999 ]
        Mark Thomas made changes -
        Assignee Tapestry Developer List [ tapestry-dev@jakarta.apache.org ]
        Mark Thomas made changes -
        Workflow jira [ 32562 ] Default workflow, editable Closed status [ 12568938 ]
        Serge Knystautas made changes -
        Field Original Value New Value
        issue.field.bugzillaimportkey 21835 22567
        Hide
        Colin Sampaleanu added a comment -

        I can't find it in the contributor's guide actually. Also, since the Readme.html
        file has a section called 'Building from Source" this kind of stuff should be
        there I think.

        Also, where is junit itself supposed to come from? There is as far as I can tell
        no mention anywhere of the need to bring in junit (I do see it in the attic in
        the master lib dir), and on my system the junit subproject breaks unless I
        manually add junit.

        Show
        Colin Sampaleanu added a comment - I can't find it in the contributor's guide actually. Also, since the Readme.html file has a section called 'Building from Source" this kind of stuff should be there I think. Also, where is junit itself supposed to come from? There is as far as I can tell no mention anywhere of the need to bring in junit (I do see it in the attic in the master lib dir), and on my system the junit subproject breaks unless I manually add junit.
        Hide
        Howard M. Lewis Ship added a comment -

        I believe this is covered in the Contributor's Guide.

        I'll be stripping out the JDom dependency fairly soon anyway and making use of
        Digester instead.

        Show
        Howard M. Lewis Ship added a comment - I believe this is covered in the Contributor's Guide. I'll be stripping out the JDom dependency fairly soon anyway and making use of Digester instead.
        Hide
        Colin Sampaleanu added a comment -

        This is in the junit subproject (as called by the 'dist' target of the master
        build). Now there is in fact a jdom-b8.jar inside the lib dir of the junit
        project, but as far as I can tell there is nothing anywhere including it, which
        is causing the breakage.

        Also, why not use jdom beta 9? It does resolve the performance/memory issue with
        jdom b8 and the use of StringBuffer...

        Show
        Colin Sampaleanu added a comment - This is in the junit subproject (as called by the 'dist' target of the master build). Now there is in fact a jdom-b8.jar inside the lib dir of the junit project, but as far as I can tell there is nothing anywhere including it, which is causing the breakage. Also, why not use jdom beta 9? It does resolve the performance/memory issue with jdom b8 and the use of StringBuffer...
        Colin Sampaleanu created issue -

          People

          • Assignee:
            Unassigned
            Reporter:
            Colin Sampaleanu
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development