Details

    • Type: Bug Bug
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Cannot Reproduce
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Number of attachments :
      0

      Description

      picocontainer-axis cannot be build, since it has an indirectly missing reference to class javax.xml.rpc.handler.soap.SOAPMessageContext.

        Activity

        Hide
        Aslak Hellesøy added a comment -

        Need more info here:

        o JDK version
        o Maven version
        o error message

        I don't see how an indirect dependency can be required during build. ("build" in this case is just compile, since there are no tests )

        My environment:

        JDK 1.4.2
        Maven 1.0-rc1

        Show
        Aslak Hellesøy added a comment - Need more info here: o JDK version o Maven version o error message I don't see how an indirect dependency can be required during build. ("build" in this case is just compile, since there are no tests ) My environment: JDK 1.4.2 Maven 1.0-rc1
        Hide
        Jörg Schaible added a comment -

        Hi Aslak,

        yes, the component compiles, but you cannot build any (test) app, since Axis depends on that missing class. IMHO they are part of xml-rpc of JSEE 1.4 or within the Sun Web Services Developer Pack 1.3. Unfortunately you cannot stuff this lib into a remote Maven repo because of licensing issues. I don't know the exact problem or if it can be distributed within a package, so we could stuff it into a lib directory as it was done with SWT.

        AFAICS the Axis team is currently working on an own free version, but it is not ready yet.

        How did you handle such issues before?

        Regards,
        Jörg

        Show
        Jörg Schaible added a comment - Hi Aslak, yes, the component compiles, but you cannot build any (test) app, since Axis depends on that missing class. IMHO they are part of xml-rpc of JSEE 1.4 or within the Sun Web Services Developer Pack 1.3. Unfortunately you cannot stuff this lib into a remote Maven repo because of licensing issues. I don't know the exact problem or if it can be distributed within a package, so we could stuff it into a lib directory as it was done with SWT. AFAICS the Axis team is currently working on an own free version, but it is not ready yet. How did you handle such issues before? Regards, Jörg
        Hide
        Aslak Hellesøy added a comment -

        Both I and DamageControl builds the nanocontainer-axis without problems.

        http://builds.codehaus.org/log/picocontainer/20040224190959.log

        Show
        Aslak Hellesøy added a comment - Both I and DamageControl builds the nanocontainer-axis without problems. http://builds.codehaus.org/log/picocontainer/20040224190959.log
        Aslak Hellesøy made changes -
        Field Original Value New Value
        Resolution Cannot Reproduce [ 5 ]
        Status Open [ 1 ] Closed [ 6 ]
        Hide
        Jörg Schaible added a comment -

        You can build it, but you cannot use it. So you will not be able to build any test cases for this component, unless you resolve the missing classes. Have you build it with you IDE? At least Eclipse reports me, that these class cannot be found.

        How will you handle the legal issue? These classes are currently only available in packages of Sun that cannot redistributed freely ... (maybe in jBoss - have not checked yet).

        Show
        Jörg Schaible added a comment - You can build it, but you cannot use it. So you will not be able to build any test cases for this component, unless you resolve the missing classes. Have you build it with you IDE? At least Eclipse reports me, that these class cannot be found. How will you handle the legal issue? These classes are currently only available in packages of Sun that cannot redistributed freely ... (maybe in jBoss - have not checked yet).
        Hide
        Aslak Hellesøy added a comment -

        The bug report complained about *build*ing, so I assumed that was what you meant.

        I have no problems *build*ing it in IDEA.

        Of course you need all dependent classes to use it, but I don't see how that is an issue for our build system, as the built classes are never instantiated. (There are no tests).

        When/if someone submits some tests for this we'll have to deal with it.

        We'll handle the legal issue in the same way as for the IDEA plugin. See picocontainer/java/idea/lib/README.txt and picocontainer/java/project.xml (how IDEA is conditionally excluded).

        Show
        Aslak Hellesøy added a comment - The bug report complained about *build*ing, so I assumed that was what you meant. I have no problems *build*ing it in IDEA. Of course you need all dependent classes to use it, but I don't see how that is an issue for our build system, as the built classes are never instantiated. (There are no tests). When/if someone submits some tests for this we'll have to deal with it. We'll handle the legal issue in the same way as for the IDEA plugin. See picocontainer/java/idea/lib/README.txt and picocontainer/java/project.xml (how IDEA is conditionally excluded).

          People

          • Assignee:
            Unassigned
            Reporter:
            Jörg Schaible
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: