Details

    • Type: Wish Wish
    • Status: Closed Closed
    • Resolution: Fixed
    • Labels:
      None

      Description

      XMLUnit for Java 1.1 has been released today.

      http://xmlunit.sf.net/

      I am listed as a project admin at http://sourceforge.net/projects/xmlunit/

        Activity

        Hide
        Carlos Sanchez added a comment -
        if it's only used for testing then
         <scope>test</scope>

        no need for optional
        Show
        Carlos Sanchez added a comment - if it's only used for testing then  <scope>test</scope> no need for optional
        Hide
        Paul King added a comment - - edited
        It is needed to compile a production class file of XmlUnit. The class file is only used by a subset of users. Many users will have XmlUnit as a test-scoped dependency.
        Show
        Paul King added a comment - - edited It is needed to compile a production class file of XmlUnit. The class file is only used by a subset of users. Many users will have XmlUnit as a test-scoped dependency.
        Hide
        Paul King added a comment -
        Any suggestions on the path forward? Is there a standard maven way to handle the above or is this use case outside what the standard model supports? Or to rephrase, does moving forward while sticking with the current model involve splitting the deliverables into two: one which would have the required compile-time dependency, the other would have to remove the class and remove the dependency? Is there something equivalent to ivy's profiles? I am not 100% sure about the full capabilities of ivy's profiles but I believe they can handle scenarios like this.
        Show
        Paul King added a comment - Any suggestions on the path forward? Is there a standard maven way to handle the above or is this use case outside what the standard model supports? Or to rephrase, does moving forward while sticking with the current model involve splitting the deliverables into two: one which would have the required compile-time dependency, the other would have to remove the class and remove the dependency? Is there something equivalent to ivy's profiles? I am not 100% sure about the full capabilities of ivy's profiles but I believe they can handle scenarios like this.
        Hide
        Stefan Bodewig added a comment -
        Sorry for the delay, I've been on vacation.

        As requested I've added an optional dependency on JUnit, so please upload the artifact.

        The XMLUnit developers (me ;-) do not intend to build XMLUnit using Maven, but we do want to provide it via the repository because our users asked for it.

        The dependency on JUnit is non-optional at compile time, but as I said, we don't build with Maven, so marking it as optional (as it is at runtime) will be fine for us.
        Show
        Stefan Bodewig added a comment - Sorry for the delay, I've been on vacation. As requested I've added an optional dependency on JUnit, so please upload the artifact. The XMLUnit developers (me ;-) do not intend to build XMLUnit using Maven, but we do want to provide it via the repository because our users asked for it. The dependency on JUnit is non-optional at compile time, but as I said, we don't build with Maven, so marking it as optional (as it is at runtime) will be fine for us.
        Hide
        Erik van Oosten added a comment -
        Meanwhile, is there another repository?
        Show
        Erik van Oosten added a comment - Meanwhile, is there another repository?

          People

          • Assignee:
            Carlos Sanchez
            Reporter:
            Stefan Bodewig
          • Votes:
            2 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: