[
https://issues.apache.org/jira/browse/PLUTO-565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12714372#action_12714372 ]
Ate Douma commented on PLUTO-565:
---------------------------------
Subscribing to the pluto-dev list as described on
http://portals.apache.org/pluto/mail-lists.html definitely should work.
Make sure to use the correct email account (and sender email address) where you expect the emails to be delivered and possibly check your spam filter...
About the m2eclipse problem:
The pluto-portal-driver-config.xml is merged into the war through the war-plugin itself because it needs to be filtered first (injecting the portal.version value).
That might be doable differently too like with an additional build/resources configuration but that *still* means the m2eclipse plugin might not "see" it.
The m2eclipse plugin is great (I use it myself), but still too limited IMO to deal with more customized/complex build configuration, so deployment I always still do through maven itself. (either through Eclipse or command line).
OFFTOPIC: we (ASF) prefer using the mailing lists because that ensures *everyone* can see, chime in and learn from the shared/archived information.
> Resource config not found under /WEB-INF/
> -----------------------------------------
>
> Key: PLUTO-565
> URL:
https://issues.apache.org/jira/browse/PLUTO-565> Project: Pluto
> Issue Type: Bug
> Affects Versions: 2.0.0
> Reporter: Gonzalo Aguilar
> Fix For: 2.0.1
>
> Attachments: handle-config-PLUTO-565.patch
>
>
> It seems that the file "pluto-portal-driver-config.xml" doesn't get deployed to the portal WEB-INF directory.
> Pluto hangs because the file cannot be found in the context but it says almost nothing about what file is not found. This path is hardcoded in ResourceConfigReader.class
> I proposed to move the file from
> ./pluto-portal/src/main/resources/pluto-portal-driver-config.xml
> to
> WEB-INF directory or update build path in the pluto portal proyect.
> Also I will atach a patch to handle this situation.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
