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 "Gonzalo Aguilar (JIRA)" <ji...@apache.org> on 2008/09/23 19:15:44 UTC
[jira] Created: (PLUTO-501) Configuration errors are not much
descriptive
Configuration errors are not much descriptive
---------------------------------------------
Key: PLUTO-501
URL: https://issues.apache.org/jira/browse/PLUTO-501
Project: Pluto
Issue Type: Improvement
Components: general
Affects Versions: 2.0.0
Environment: Linux ws-esp16 2.6.24-21-generic #1 SMP Mon Aug 25 17:32:09 UTC 2008 i686 GNU/Linux
java version "1.6.0_07"
Java(TM) SE Runtime Environment (build 1.6.0_07-b06)
Java HotSpot(TM) Server VM (build 10.0-b23, mixed mode)
Tomcat 5.5
Reporter: Gonzalo Aguilar
Priority: Minor
Fix For: 2.0.0
Attachments: config_patch_v2.diff
Hi all,
I was playing around with the project and found that sometimes is very difficult to trace down errors because missing configuration when deployment occurs.
Also messages are not much descriptive and constructions like:
PortletAppDD portletAppDD = PortletDescriptorRegistry.getRegistry().getPortletAppDD(servletContext);
Makes tracing difficult to do.
So I ask. Should we add a configurator or instructions ot configure the project?
I mean, Where the files should be when deploying, Why files are found in classes directory and others in WEB-INF, while others in META-INF.
I found particularly difficult the error with the file pluto-portal-driver-config.xml that was found in resources in maven and must be deployed to WEB-INF to let pluto find it.
So I wrote some small patches that I include with this bug report to clarify some of the bugs, and let the user know what was wrong.
I know this patch makes changes to the pom.xml of some subdirs, but they are needed to let m2eclipse plugin play fair.
Thank you.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (PLUTO-501) Configuration errors are not much
descriptive
Posted by "Ate Douma (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PLUTO-501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ate Douma closed PLUTO-501.
---------------------------
Resolution: Fixed
> Configuration errors are not much descriptive
> ---------------------------------------------
>
> Key: PLUTO-501
> URL: https://issues.apache.org/jira/browse/PLUTO-501
> Project: Pluto
> Issue Type: Improvement
> Components: general
> Affects Versions: 1.1.7
> Environment: Linux ws-esp16 2.6.24-21-generic #1 SMP Mon Aug 25 17:32:09 UTC 2008 i686 GNU/Linux
> java version "1.6.0_07"
> Java(TM) SE Runtime Environment (build 1.6.0_07-b06)
> Java HotSpot(TM) Server VM (build 10.0-b23, mixed mode)
> Tomcat 5.5
> Reporter: Gonzalo Aguilar
> Assignee: Craig Doremus
> Priority: Minor
> Fix For: 1.1.7
>
> Attachments: config_patch_v2.diff, PLUTO-501_patch2.diff
>
> Original Estimate: 72h
> Remaining Estimate: 72h
>
> Hi all,
> I was playing around with the project and found that sometimes is very difficult to trace down errors because missing configuration when deployment occurs.
> Also messages are not much descriptive and constructions like:
> PortletAppDD portletAppDD = PortletDescriptorRegistry.getRegistry().getPortletAppDD(servletContext);
> Makes tracing difficult to do.
> So I ask. Should we add a configurator or instructions ot configure the project?
> I mean, Where the files should be when deploying, Why files are found in classes directory and others in WEB-INF, while others in META-INF.
> I found particularly difficult the error with the file pluto-portal-driver-config.xml that was found in resources in maven and must be deployed to WEB-INF to let pluto find it.
> So I wrote some small patches that I include with this bug report to clarify some of the bugs, and let the user know what was wrong.
> I know this patch makes changes to the pom.xml of some subdirs, but they are needed to let m2eclipse plugin play fair.
> Thank you.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (PLUTO-501) Configuration errors are not much
descriptive
Posted by "Craig Doremus (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PLUTO-501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Craig Doremus updated PLUTO-501:
--------------------------------
Affects Version/s: (was: 2.0.0)
1.1.7
2.0-refactoring
Fix Version/s: (was: 2.0.0)
1.1.7
2.0-refactoring
Modified affects and fixed version to reflect patch applied in SVN rev 701912.
> Configuration errors are not much descriptive
> ---------------------------------------------
>
> Key: PLUTO-501
> URL: https://issues.apache.org/jira/browse/PLUTO-501
> Project: Pluto
> Issue Type: Improvement
> Components: general
> Affects Versions: 2.0-refactoring, 1.1.7
> Environment: Linux ws-esp16 2.6.24-21-generic #1 SMP Mon Aug 25 17:32:09 UTC 2008 i686 GNU/Linux
> java version "1.6.0_07"
> Java(TM) SE Runtime Environment (build 1.6.0_07-b06)
> Java HotSpot(TM) Server VM (build 10.0-b23, mixed mode)
> Tomcat 5.5
> Reporter: Gonzalo Aguilar
> Assignee: Craig Doremus
> Priority: Minor
> Fix For: 2.0-refactoring, 1.1.7
>
> Attachments: config_patch_v2.diff, PLUTO-501_patch2.diff
>
> Original Estimate: 72h
> Remaining Estimate: 72h
>
> Hi all,
> I was playing around with the project and found that sometimes is very difficult to trace down errors because missing configuration when deployment occurs.
> Also messages are not much descriptive and constructions like:
> PortletAppDD portletAppDD = PortletDescriptorRegistry.getRegistry().getPortletAppDD(servletContext);
> Makes tracing difficult to do.
> So I ask. Should we add a configurator or instructions ot configure the project?
> I mean, Where the files should be when deploying, Why files are found in classes directory and others in WEB-INF, while others in META-INF.
> I found particularly difficult the error with the file pluto-portal-driver-config.xml that was found in resources in maven and must be deployed to WEB-INF to let pluto find it.
> So I wrote some small patches that I include with this bug report to clarify some of the bugs, and let the user know what was wrong.
> I know this patch makes changes to the pom.xml of some subdirs, but they are needed to let m2eclipse plugin play fair.
> Thank you.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (PLUTO-501) Configuration errors are not much
descriptive
Posted by "Gonzalo Aguilar (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PLUTO-501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gonzalo Aguilar updated PLUTO-501:
----------------------------------
Attachment: config_patch_v2.diff
This patch makes some errors more descriptive.
Also this adds a message to the portlet window if the portlet cannot be loaded instead of the ugly trace of the error that can be seen in logs.
> Configuration errors are not much descriptive
> ---------------------------------------------
>
> Key: PLUTO-501
> URL: https://issues.apache.org/jira/browse/PLUTO-501
> Project: Pluto
> Issue Type: Improvement
> Components: general
> Affects Versions: 2.0.0
> Environment: Linux ws-esp16 2.6.24-21-generic #1 SMP Mon Aug 25 17:32:09 UTC 2008 i686 GNU/Linux
> java version "1.6.0_07"
> Java(TM) SE Runtime Environment (build 1.6.0_07-b06)
> Java HotSpot(TM) Server VM (build 10.0-b23, mixed mode)
> Tomcat 5.5
> Reporter: Gonzalo Aguilar
> Priority: Minor
> Fix For: 2.0.0
>
> Attachments: config_patch_v2.diff
>
> Original Estimate: 72h
> Remaining Estimate: 72h
>
> Hi all,
> I was playing around with the project and found that sometimes is very difficult to trace down errors because missing configuration when deployment occurs.
> Also messages are not much descriptive and constructions like:
> PortletAppDD portletAppDD = PortletDescriptorRegistry.getRegistry().getPortletAppDD(servletContext);
> Makes tracing difficult to do.
> So I ask. Should we add a configurator or instructions ot configure the project?
> I mean, Where the files should be when deploying, Why files are found in classes directory and others in WEB-INF, while others in META-INF.
> I found particularly difficult the error with the file pluto-portal-driver-config.xml that was found in resources in maven and must be deployed to WEB-INF to let pluto find it.
> So I wrote some small patches that I include with this bug report to clarify some of the bugs, and let the user know what was wrong.
> I know this patch makes changes to the pom.xml of some subdirs, but they are needed to let m2eclipse plugin play fair.
> Thank you.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (PLUTO-501) Configuration errors are not much
descriptive
Posted by "Craig Doremus (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PLUTO-501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Craig Doremus updated PLUTO-501:
--------------------------------
Attachment: (was: PLUTO-501_patch2.diff)
> Configuration errors are not much descriptive
> ---------------------------------------------
>
> Key: PLUTO-501
> URL: https://issues.apache.org/jira/browse/PLUTO-501
> Project: Pluto
> Issue Type: Improvement
> Components: general
> Affects Versions: 2.0.0
> Environment: Linux ws-esp16 2.6.24-21-generic #1 SMP Mon Aug 25 17:32:09 UTC 2008 i686 GNU/Linux
> java version "1.6.0_07"
> Java(TM) SE Runtime Environment (build 1.6.0_07-b06)
> Java HotSpot(TM) Server VM (build 10.0-b23, mixed mode)
> Tomcat 5.5
> Reporter: Gonzalo Aguilar
> Assignee: Craig Doremus
> Priority: Minor
> Fix For: 2.0.0
>
> Attachments: config_patch_v2.diff
>
> Original Estimate: 72h
> Remaining Estimate: 72h
>
> Hi all,
> I was playing around with the project and found that sometimes is very difficult to trace down errors because missing configuration when deployment occurs.
> Also messages are not much descriptive and constructions like:
> PortletAppDD portletAppDD = PortletDescriptorRegistry.getRegistry().getPortletAppDD(servletContext);
> Makes tracing difficult to do.
> So I ask. Should we add a configurator or instructions ot configure the project?
> I mean, Where the files should be when deploying, Why files are found in classes directory and others in WEB-INF, while others in META-INF.
> I found particularly difficult the error with the file pluto-portal-driver-config.xml that was found in resources in maven and must be deployed to WEB-INF to let pluto find it.
> So I wrote some small patches that I include with this bug report to clarify some of the bugs, and let the user know what was wrong.
> I know this patch makes changes to the pom.xml of some subdirs, but they are needed to let m2eclipse plugin play fair.
> Thank you.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (PLUTO-501) Configuration errors are not much
descriptive
Posted by "Craig Doremus (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PLUTO-501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12636981#action_12636981 ]
Craig Doremus commented on PLUTO-501:
-------------------------------------
I have applied PLUTO-501_patch2.diff in SVN rev 701912. This patch will have to be applied to the 2.0-refactoring branch. I think the 1.1.x branch would also benefit from these changes.
> Configuration errors are not much descriptive
> ---------------------------------------------
>
> Key: PLUTO-501
> URL: https://issues.apache.org/jira/browse/PLUTO-501
> Project: Pluto
> Issue Type: Improvement
> Components: general
> Affects Versions: 2.0.0
> Environment: Linux ws-esp16 2.6.24-21-generic #1 SMP Mon Aug 25 17:32:09 UTC 2008 i686 GNU/Linux
> java version "1.6.0_07"
> Java(TM) SE Runtime Environment (build 1.6.0_07-b06)
> Java HotSpot(TM) Server VM (build 10.0-b23, mixed mode)
> Tomcat 5.5
> Reporter: Gonzalo Aguilar
> Assignee: Craig Doremus
> Priority: Minor
> Fix For: 2.0.0
>
> Attachments: config_patch_v2.diff, PLUTO-501_patch2.diff
>
> Original Estimate: 72h
> Remaining Estimate: 72h
>
> Hi all,
> I was playing around with the project and found that sometimes is very difficult to trace down errors because missing configuration when deployment occurs.
> Also messages are not much descriptive and constructions like:
> PortletAppDD portletAppDD = PortletDescriptorRegistry.getRegistry().getPortletAppDD(servletContext);
> Makes tracing difficult to do.
> So I ask. Should we add a configurator or instructions ot configure the project?
> I mean, Where the files should be when deploying, Why files are found in classes directory and others in WEB-INF, while others in META-INF.
> I found particularly difficult the error with the file pluto-portal-driver-config.xml that was found in resources in maven and must be deployed to WEB-INF to let pluto find it.
> So I wrote some small patches that I include with this bug report to clarify some of the bugs, and let the user know what was wrong.
> I know this patch makes changes to the pom.xml of some subdirs, but they are needed to let m2eclipse plugin play fair.
> Thank you.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (PLUTO-501) Configuration errors are not much
descriptive
Posted by "Craig Doremus (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PLUTO-501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12636826#action_12636826 ]
Craig Doremus commented on PLUTO-501:
-------------------------------------
Thank you for your contribution Gonzalo. I agree that we need to do a better job reporting configuration errors, but some of the changes in your patch do not relate to this. Specifically, there are pom.xml modifications and a change to portlet.xml in the testsuite. Please add these these to separate Jira issues. Other parts of your patch do not change anything, in particular the modifications to logging.properties and web.xml just add whitespace to the files.
> Configuration errors are not much descriptive
> ---------------------------------------------
>
> Key: PLUTO-501
> URL: https://issues.apache.org/jira/browse/PLUTO-501
> Project: Pluto
> Issue Type: Improvement
> Components: general
> Affects Versions: 2.0.0
> Environment: Linux ws-esp16 2.6.24-21-generic #1 SMP Mon Aug 25 17:32:09 UTC 2008 i686 GNU/Linux
> java version "1.6.0_07"
> Java(TM) SE Runtime Environment (build 1.6.0_07-b06)
> Java HotSpot(TM) Server VM (build 10.0-b23, mixed mode)
> Tomcat 5.5
> Reporter: Gonzalo Aguilar
> Priority: Minor
> Fix For: 2.0.0
>
> Attachments: config_patch_v2.diff
>
> Original Estimate: 72h
> Remaining Estimate: 72h
>
> Hi all,
> I was playing around with the project and found that sometimes is very difficult to trace down errors because missing configuration when deployment occurs.
> Also messages are not much descriptive and constructions like:
> PortletAppDD portletAppDD = PortletDescriptorRegistry.getRegistry().getPortletAppDD(servletContext);
> Makes tracing difficult to do.
> So I ask. Should we add a configurator or instructions ot configure the project?
> I mean, Where the files should be when deploying, Why files are found in classes directory and others in WEB-INF, while others in META-INF.
> I found particularly difficult the error with the file pluto-portal-driver-config.xml that was found in resources in maven and must be deployed to WEB-INF to let pluto find it.
> So I wrote some small patches that I include with this bug report to clarify some of the bugs, and let the user know what was wrong.
> I know this patch makes changes to the pom.xml of some subdirs, but they are needed to let m2eclipse plugin play fair.
> Thank you.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (PLUTO-501) Configuration errors are not much
descriptive
Posted by "Gonzalo Aguilar (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PLUTO-501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12636900#action_12636900 ]
Gonzalo Aguilar commented on PLUTO-501:
---------------------------------------
Hi Craig,
Yep sorry. I realized some of the patchs are not related after sending it. I have to do better job.
Ok. I will separate the patch so only configuration error handling will go on it. Also some of the patch that does not change anything will be removed. I don't know why diff included them. I think I touched them without being conscience...
Sorry to not doing it clean enough, my fault. Will not do again.
Very thank's
> Configuration errors are not much descriptive
> ---------------------------------------------
>
> Key: PLUTO-501
> URL: https://issues.apache.org/jira/browse/PLUTO-501
> Project: Pluto
> Issue Type: Improvement
> Components: general
> Affects Versions: 2.0.0
> Environment: Linux ws-esp16 2.6.24-21-generic #1 SMP Mon Aug 25 17:32:09 UTC 2008 i686 GNU/Linux
> java version "1.6.0_07"
> Java(TM) SE Runtime Environment (build 1.6.0_07-b06)
> Java HotSpot(TM) Server VM (build 10.0-b23, mixed mode)
> Tomcat 5.5
> Reporter: Gonzalo Aguilar
> Priority: Minor
> Fix For: 2.0.0
>
> Attachments: config_patch_v2.diff
>
> Original Estimate: 72h
> Remaining Estimate: 72h
>
> Hi all,
> I was playing around with the project and found that sometimes is very difficult to trace down errors because missing configuration when deployment occurs.
> Also messages are not much descriptive and constructions like:
> PortletAppDD portletAppDD = PortletDescriptorRegistry.getRegistry().getPortletAppDD(servletContext);
> Makes tracing difficult to do.
> So I ask. Should we add a configurator or instructions ot configure the project?
> I mean, Where the files should be when deploying, Why files are found in classes directory and others in WEB-INF, while others in META-INF.
> I found particularly difficult the error with the file pluto-portal-driver-config.xml that was found in resources in maven and must be deployed to WEB-INF to let pluto find it.
> So I wrote some small patches that I include with this bug report to clarify some of the bugs, and let the user know what was wrong.
> I know this patch makes changes to the pom.xml of some subdirs, but they are needed to let m2eclipse plugin play fair.
> Thank you.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (PLUTO-501) Configuration errors are not much
descriptive
Posted by "Craig Doremus (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PLUTO-501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Craig Doremus reassigned PLUTO-501:
-----------------------------------
Assignee: Craig Doremus
> Configuration errors are not much descriptive
> ---------------------------------------------
>
> Key: PLUTO-501
> URL: https://issues.apache.org/jira/browse/PLUTO-501
> Project: Pluto
> Issue Type: Improvement
> Components: general
> Affects Versions: 2.0.0
> Environment: Linux ws-esp16 2.6.24-21-generic #1 SMP Mon Aug 25 17:32:09 UTC 2008 i686 GNU/Linux
> java version "1.6.0_07"
> Java(TM) SE Runtime Environment (build 1.6.0_07-b06)
> Java HotSpot(TM) Server VM (build 10.0-b23, mixed mode)
> Tomcat 5.5
> Reporter: Gonzalo Aguilar
> Assignee: Craig Doremus
> Priority: Minor
> Fix For: 2.0.0
>
> Attachments: config_patch_v2.diff
>
> Original Estimate: 72h
> Remaining Estimate: 72h
>
> Hi all,
> I was playing around with the project and found that sometimes is very difficult to trace down errors because missing configuration when deployment occurs.
> Also messages are not much descriptive and constructions like:
> PortletAppDD portletAppDD = PortletDescriptorRegistry.getRegistry().getPortletAppDD(servletContext);
> Makes tracing difficult to do.
> So I ask. Should we add a configurator or instructions ot configure the project?
> I mean, Where the files should be when deploying, Why files are found in classes directory and others in WEB-INF, while others in META-INF.
> I found particularly difficult the error with the file pluto-portal-driver-config.xml that was found in resources in maven and must be deployed to WEB-INF to let pluto find it.
> So I wrote some small patches that I include with this bug report to clarify some of the bugs, and let the user know what was wrong.
> I know this patch makes changes to the pom.xml of some subdirs, but they are needed to let m2eclipse plugin play fair.
> Thank you.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (PLUTO-501) Configuration errors are not much
descriptive
Posted by "Craig Doremus (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PLUTO-501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Craig Doremus updated PLUTO-501:
--------------------------------
Attachment: PLUTO-501_patch2.diff
I took a look at Gonzalo's patch, removed all the extraneous files and modified a few other area that had poor logging and exception handling. I will commit this when I get a chance.
> Configuration errors are not much descriptive
> ---------------------------------------------
>
> Key: PLUTO-501
> URL: https://issues.apache.org/jira/browse/PLUTO-501
> Project: Pluto
> Issue Type: Improvement
> Components: general
> Affects Versions: 2.0.0
> Environment: Linux ws-esp16 2.6.24-21-generic #1 SMP Mon Aug 25 17:32:09 UTC 2008 i686 GNU/Linux
> java version "1.6.0_07"
> Java(TM) SE Runtime Environment (build 1.6.0_07-b06)
> Java HotSpot(TM) Server VM (build 10.0-b23, mixed mode)
> Tomcat 5.5
> Reporter: Gonzalo Aguilar
> Assignee: Craig Doremus
> Priority: Minor
> Fix For: 2.0.0
>
> Attachments: config_patch_v2.diff, PLUTO-501_patch2.diff
>
> Original Estimate: 72h
> Remaining Estimate: 72h
>
> Hi all,
> I was playing around with the project and found that sometimes is very difficult to trace down errors because missing configuration when deployment occurs.
> Also messages are not much descriptive and constructions like:
> PortletAppDD portletAppDD = PortletDescriptorRegistry.getRegistry().getPortletAppDD(servletContext);
> Makes tracing difficult to do.
> So I ask. Should we add a configurator or instructions ot configure the project?
> I mean, Where the files should be when deploying, Why files are found in classes directory and others in WEB-INF, while others in META-INF.
> I found particularly difficult the error with the file pluto-portal-driver-config.xml that was found in resources in maven and must be deployed to WEB-INF to let pluto find it.
> So I wrote some small patches that I include with this bug report to clarify some of the bugs, and let the user know what was wrong.
> I know this patch makes changes to the pom.xml of some subdirs, but they are needed to let m2eclipse plugin play fair.
> Thank you.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (PLUTO-501) Configuration errors are not much
descriptive
Posted by "Craig Doremus (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PLUTO-501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Craig Doremus updated PLUTO-501:
--------------------------------
Attachment: PLUTO-501_patch2.diff
I missed the pluto-portal-driver files in the last patch file. This is a replacement that includes that file and the other Java files from Gonzalo's original post. Thanks, again, for your help.
> Configuration errors are not much descriptive
> ---------------------------------------------
>
> Key: PLUTO-501
> URL: https://issues.apache.org/jira/browse/PLUTO-501
> Project: Pluto
> Issue Type: Improvement
> Components: general
> Affects Versions: 2.0.0
> Environment: Linux ws-esp16 2.6.24-21-generic #1 SMP Mon Aug 25 17:32:09 UTC 2008 i686 GNU/Linux
> java version "1.6.0_07"
> Java(TM) SE Runtime Environment (build 1.6.0_07-b06)
> Java HotSpot(TM) Server VM (build 10.0-b23, mixed mode)
> Tomcat 5.5
> Reporter: Gonzalo Aguilar
> Assignee: Craig Doremus
> Priority: Minor
> Fix For: 2.0.0
>
> Attachments: config_patch_v2.diff, PLUTO-501_patch2.diff
>
> Original Estimate: 72h
> Remaining Estimate: 72h
>
> Hi all,
> I was playing around with the project and found that sometimes is very difficult to trace down errors because missing configuration when deployment occurs.
> Also messages are not much descriptive and constructions like:
> PortletAppDD portletAppDD = PortletDescriptorRegistry.getRegistry().getPortletAppDD(servletContext);
> Makes tracing difficult to do.
> So I ask. Should we add a configurator or instructions ot configure the project?
> I mean, Where the files should be when deploying, Why files are found in classes directory and others in WEB-INF, while others in META-INF.
> I found particularly difficult the error with the file pluto-portal-driver-config.xml that was found in resources in maven and must be deployed to WEB-INF to let pluto find it.
> So I wrote some small patches that I include with this bug report to clarify some of the bugs, and let the user know what was wrong.
> I know this patch makes changes to the pom.xml of some subdirs, but they are needed to let m2eclipse plugin play fair.
> Thank you.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (PLUTO-501) Configuration errors are not much
descriptive
Posted by "Craig Doremus (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PLUTO-501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Craig Doremus updated PLUTO-501:
--------------------------------
Affects Version/s: (was: 2.0-refactoring)
Fix Version/s: (was: 2.0-refactoring)
Applied patches to 2.0-refactoring branch in SVN rev 702005.
> Configuration errors are not much descriptive
> ---------------------------------------------
>
> Key: PLUTO-501
> URL: https://issues.apache.org/jira/browse/PLUTO-501
> Project: Pluto
> Issue Type: Improvement
> Components: general
> Affects Versions: 1.1.7
> Environment: Linux ws-esp16 2.6.24-21-generic #1 SMP Mon Aug 25 17:32:09 UTC 2008 i686 GNU/Linux
> java version "1.6.0_07"
> Java(TM) SE Runtime Environment (build 1.6.0_07-b06)
> Java HotSpot(TM) Server VM (build 10.0-b23, mixed mode)
> Tomcat 5.5
> Reporter: Gonzalo Aguilar
> Assignee: Craig Doremus
> Priority: Minor
> Fix For: 1.1.7
>
> Attachments: config_patch_v2.diff, PLUTO-501_patch2.diff
>
> Original Estimate: 72h
> Remaining Estimate: 72h
>
> Hi all,
> I was playing around with the project and found that sometimes is very difficult to trace down errors because missing configuration when deployment occurs.
> Also messages are not much descriptive and constructions like:
> PortletAppDD portletAppDD = PortletDescriptorRegistry.getRegistry().getPortletAppDD(servletContext);
> Makes tracing difficult to do.
> So I ask. Should we add a configurator or instructions ot configure the project?
> I mean, Where the files should be when deploying, Why files are found in classes directory and others in WEB-INF, while others in META-INF.
> I found particularly difficult the error with the file pluto-portal-driver-config.xml that was found in resources in maven and must be deployed to WEB-INF to let pluto find it.
> So I wrote some small patches that I include with this bug report to clarify some of the bugs, and let the user know what was wrong.
> I know this patch makes changes to the pom.xml of some subdirs, but they are needed to let m2eclipse plugin play fair.
> Thank you.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.