To answer my own question, I solved the problem by adding the maven dependencies on the application instead of the plugin. This makes sure they're beeing loaded by the same classloader as the rest of the web application (and the resource bundle). However, solving that issue required me to add a lot of other files to my portlet as well (stylesheets, images etc)...
I've followed up on my previous blog entry describing how I tried to make the solution less intrusive: http://portletwork.blogspot.com/2007/08/maven-jetty-plugin-and-jsr168-portlets.html As you know a lot more about the internals of pluto, please correct me if anything I have written is wrong. Nils-H On 8/1/07, Nils-Helge Garli <[EMAIL PROTECTED]> wrote: > Hi! > > I'm currently trying to embed pluto with the maven-jetty-plugin to be > able to run my maven portlet projects by simply issuing the command > "mvn jetty:run". I have used the information in the faq about "What's > the easiest way to include a portlet in my webapp" and looking through > the sources, and I've managed to run my portlet with the jetty plugin > (I've compiled a list of the steps I had to go through here: > http://portletwork.blogspot.com/2007/07/mvnjetty-and-portlets.html) > > (I'm not sure if this is the correct way to do it, or maybe a solution > for this already exists, so if anybody has any corrections/objections, > please let me know) > > But one of the things I have not been able to solve yet is using the > pluto:modeAnchor and pluto:windowStateAnchor tags in the jsp file that > acts as the portal. The problem is that it cannot resolve the > ToolTips.properties resource bundle. I assume this is a classloader > issue. I have tried putting the ToolTips.properties in the > WEB-INF/classes folder (also in various sub folders) without success. > I've even tried putting it in the same jar as the tag classes, but > still no luck. Any ideas where I should put the ToolTips.properties > file, or what I have done wrong since my "embedded pluto" project > cannot resolve it? > > Nils-H >
