[
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.
