You are viewing a plain text version of this content. The canonical link for it is here.
Posted to pluto-dev@portals.apache.org by "Antony Stubbs (JIRA)" <ji...@apache.org> on 2008/10/13 18:56:44 UTC
[jira] Created: (PLUTO-508) pluto:install / pluto missing commons
logging
pluto:install / pluto missing commons logging
---------------------------------------------
Key: PLUTO-508
URL: https://issues.apache.org/jira/browse/PLUTO-508
Project: Pluto
Issue Type: Bug
Components: build system, maven pluto plugin, portlet container
Affects Versions: 2.0.0
Reporter: Antony Stubbs
Priority: Minor
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
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (PLUTO-508) pluto:install / pluto missing commons
logging
Posted by "Eric Dalquist (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PLUTO-508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639886#action_12639886 ]
Eric Dalquist commented on PLUTO-508:
-------------------------------------
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.
> pluto:install / pluto missing commons logging
> ---------------------------------------------
>
> Key: PLUTO-508
> URL: https://issues.apache.org/jira/browse/PLUTO-508
> Project: Pluto
> Issue Type: Bug
> Components: build system, maven pluto plugin, portlet container
> Affects Versions: 2.0.0
> Reporter: Antony Stubbs
> Priority: Minor
>
> 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
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (PLUTO-508) pluto:install / pluto missing commons
logging
Posted by "Ate Douma (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PLUTO-508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639874#action_12639874 ]
Ate Douma commented on PLUTO-508:
---------------------------------
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.
> pluto:install / pluto missing commons logging
> ---------------------------------------------
>
> Key: PLUTO-508
> URL: https://issues.apache.org/jira/browse/PLUTO-508
> Project: Pluto
> Issue Type: Bug
> Components: build system, maven pluto plugin, portlet container
> Affects Versions: 2.0.0
> Reporter: Antony Stubbs
> Priority: Minor
>
> 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
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (PLUTO-508) pluto:install / pluto missing commons
logging
Posted by "Ate Douma (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PLUTO-508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ate Douma closed PLUTO-508.
---------------------------
Resolution: Fixed
Fix Version/s: 2.0.0
Fixed after merging the 2.0-refactoring branch
> pluto:install / pluto missing commons logging
> ---------------------------------------------
>
> Key: PLUTO-508
> URL: https://issues.apache.org/jira/browse/PLUTO-508
> Project: Pluto
> Issue Type: Bug
> Components: build system, maven pluto plugin, portlet container
> Affects Versions: 2.0.0
> Reporter: Antony Stubbs
> Priority: Minor
> Fix For: 2.0.0
>
>
> 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
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.