Good question. I may just now be starting to understand this more based on that last question.
You previously said "The problem is that the plugin injects the resources path into the classpath." But the problem is really a bit more subtle, it injects the resources SOURCE path in, rather than the resources TARGET path, and that's the issue, correct? If so then we could add an issue to the tracker to address that, potentially. I don't recall now why it was done that way, whether it was just naive, or it was intentional - would have to research it a bit and test some things. Also, I wonder if there is a way in the Maven API to get the target resources from the compile path - we certainly don't want to try to just hit that path and somehow filter what we think are resources, that would be ugly (hopefully Maven already has a method that does that?). On Nov 7, 8:11 am, "Brian Cribbs" <[EMAIL PROTECTED]> wrote: > Why does it pull the resources from the source tree instead of the target > tree? > > On Fri, Nov 7, 2008 at 6:44 AM, Charlie Collins > <[EMAIL PROTECTED]>wrote: > > > > > The plugin injects stuff into the scripts it writes, yes, but it does > > so based on the Maven resolution process and your POM configuration. > > If you don't have a resources section in your build src/main/resources > > is the Maven default. > > > Here is exactly what the plugin does to "inject" stuff: > > >http://gwt-maven.googlecode.com/svn/trunk/maven-googlewebtoolkit2-plu... > > . > > private static List<Artifact> getResources(final MavenProject project, > > final DependencyScope scope) { > > if (DependencyScope.COMPILE.equals(scope)) { > > return project.getResources(); > > } > > else if (DependencyScope.TEST.equals(scope)) { > > return project.getTestResources(); > > } > > else { > > throw new RuntimeException("Not allowed scope " + scope); > > } > > } > > > At no point does it manually hard code anything, it pulls in Maven > > dependencies and resources. > > > On Nov 5, 1:38 pm, "Brian Cribbs" <[EMAIL PROTECTED]> wrote: > > > The problem is that the plugin injects the resources path into the > > > classpath. I've verified that the below output is from this plugin and > > NOT > > > maven. > > > > On Wed, Nov 5, 2008 at 1:33 PM, Charlie Collins > > > <[EMAIL PROTECTED]>wrote: > > > > > You can configure the resources with the maven resources plugin. I am > > > > not sure I understand what you need to do, but you can tweak all that, > > > > yes (though it's not related to GWT-Maven). > > > > > On Nov 5, 10:30 am, bdcribbs <[EMAIL PROTECTED]> wrote: > > > > > I'm filtering a properties file in order to load remote servlets from > > > > > a GWT-RPC call. I'm using > > > > > this.getClass().getClassLoader().getResourceAsStream("file.name"); > > and > > > > > the application is picking up the unfiltered version of the file. > > > > > > If I run mvn gwt:gwt -X I get this output > > > > > [DEBUG] SCRIPT INJECTION CLASSPATH LIST > > > > > [DEBUG] C:\.m2\repository\com\google\gwt\gwt-user\1.5.3\gwt- > > > > > user-1.5.3.jar > > > > > [DEBUG] C:\.m2\repository\com\google\gwt\gwt-dev\1.5.3\gwt- > > > > > dev-1.5.3-windows.jar > > > > > [DEBUG] C:\projects\hermes\trunk\admin-web\src\main\java > > > > > [DEBUG] C:\projects\hermes\trunk\admin-web\src\main\resources > > > > > [DEBUG] C:\projects\hermes\trunk\admin-web\classes > > > > > [DEBUG] C:\projects\hermes\trunk\admin-web\target\classes > > > > > [DEBUG] C:\.m2\repository\com\thoughtworks\xstream\xstream > > > > > \1.2.2\xstream-1.2.2.jar > > > > > [DEBUG] C:\.m2\repository\xpp3\xpp3_min\1.1.3.4.O > > > > > \xpp3_min-1.1.3.4.O.jar > > > > > [DEBUG] C:\.m2\repository\commons-httpclient\commons-httpclient > > > > > \3.0.1\commons-httpclient-3.0.1.jar > > > > > [DEBUG] C:\.m2\repository\commons-logging\commons-logging > > > > > \1.0.3\commons-logging-1.0.3.jar > > > > > [DEBUG] C:\.m2\repository\commons-codec\commons-codec\1.2\commons- > > > > > codec-1.2.jar > > > > > [DEBUG] C:\.m2\repository\com\extjs\gxt\1.1.2\gxt-1.1.2.jar > > > > > [DEBUG] C:\.m2\repository\org\codehaus\jettison\jettison > > > > > \1.0\jettison-1.0.jar > > > > > [DEBUG] C:\.m2\repository\stax\stax-api\1.0.1\stax-api-1.0.1.jar > > > > > > which leads me to believe it's the plugin adding src/main/resources > > to > > > > > the classpath which is causing the above problem. Is there any way > > to > > > > > tell the plugin to NOT use this directory on the classpath? > > > > > > Thanks, > > > > > Brian --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "gwt-maven" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/gwt-maven?hl=en -~----------~----~----~----~------~----~------~--~---
