Pluto
  1. Pluto
  2. PLUTO-508

pluto:install / pluto missing commons logging

    Details

      Description

      after a fresh 2.0 build and pluto:install - got CNEs for commons logging when starting tomcat, added commongs-logging 1.1.1 to tomcat lib dir and pluto started without error.

      Is this intentional? If so - please add a note regarding it to the page:
      http://portals.apache.org/pluto/v11/getting-started.html

        Activity

        Hide
        Ate Douma added a comment -

        Fixed after merging the 2.0-refactoring branch

        Show
        Ate Douma added a comment - Fixed after merging the 2.0-refactoring branch
        Hide
        Eric Dalquist added a comment -

        Adding commons-logging-api to shared/lib seems to work fairly well but I'm with Ate that we need to end up with as few libraries in shared/lib as possible. We're currently running into issues with Pluto 1.1 requiring Castor in shared/lib causing conflicts with webapps that use a different version of Caster for web service implementations.

        Show
        Eric Dalquist added a comment - Adding commons-logging-api to shared/lib seems to work fairly well but I'm with Ate that we need to end up with as few libraries in shared/lib as possible. We're currently running into issues with Pluto 1.1 requiring Castor in shared/lib causing conflicts with webapps that use a different version of Caster for web service implementations.
        Hide
        Ate Douma added a comment -

        Actually, the fact you need to put commons-logging in the shared libs is a problem.
        And not just commons-logging, there are far too many non-standard-api implementation jars in the shared lib already.

        Depending on non-standard shared libraries really is a problem when you would need to run a pluto (based) portal side-by-side with lots of other applications (e.g. portlet applications...)
        If one of those would be depending on a different version of one of these shared libraries, your in big trouble.
        For Pluto 1.0.1 we had this pretty good covered, but since Pluto 1.1.x many new dependencies have crept in over time...

        There is only one solution for that: removing all these dependencies again from classes provided through the shared libs...
        This means for instance getting rid of all common-logging usages ...

        For the Pluto 2.0-refactoring branch we're already working on this (and other clean outs) but those haven't been committed yet.
        You can expect us to move quickly there though as we need this resolved to be able to embed Pluto 2.0 in Jetspeed again.

        Show
        Ate Douma added a comment - Actually, the fact you need to put commons-logging in the shared libs is a problem. And not just commons-logging, there are far too many non-standard-api implementation jars in the shared lib already. Depending on non-standard shared libraries really is a problem when you would need to run a pluto (based) portal side-by-side with lots of other applications (e.g. portlet applications...) If one of those would be depending on a different version of one of these shared libraries, your in big trouble. For Pluto 1.0.1 we had this pretty good covered, but since Pluto 1.1.x many new dependencies have crept in over time... There is only one solution for that: removing all these dependencies again from classes provided through the shared libs... This means for instance getting rid of all common-logging usages ... For the Pluto 2.0-refactoring branch we're already working on this (and other clean outs) but those haven't been committed yet. You can expect us to move quickly there though as we need this resolved to be able to embed Pluto 2.0 in Jetspeed again.

          People

          • Assignee:
            Unassigned
            Reporter:
            Antony Stubbs
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development