Uploaded image for project: 'Pluto'
  1. Pluto
  2. PLUTO-501

Configuration errors are not much descriptive

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 1.1.7
    • Fix Version/s: 1.1.7
    • Component/s: general
    • Labels:
      None
    • Environment:

      Description

      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.

        Attachments

        1. PLUTO-501_patch2.diff
          25 kB
          Craig Doremus
        2. config_patch_v2.diff
          16 kB
          Gonzalo Aguilar

          Activity

            People

            • Assignee:
              cdoremus Craig Doremus
              Reporter:
              gad Gonzalo Aguilar
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - 72h
                72h
                Remaining:
                Remaining Estimate - 72h
                72h
                Logged:
                Time Spent - Not Specified
                Not Specified