I think it is resourceBases now or something like that? -- jesse mcconnell jesse.mcconn...@gmail.com
On Wed, Oct 2, 2013 at 11:51 AM, Patrick Moench <patrickmoe...@gmail.com>wrote: > Bump. Any help on this one? Thanks. > > > On Fri, Sep 27, 2013 at 4:25 PM, Patrick Moench > <patrickmoe...@gmail.com>wrote: > >> Hello, >> >> I'm using version 9.1.0.M0 of the maven-jetty-plugin. According to the >> documentation, the preferred way to add "provided" dependencies to the >> container classpath is to add them as explicit dependencies to the plugin. >> Like so: >> >> <plugin> >> <groupId>org.eclipse.jetty</groupId> >> <artifactId>jetty-maven-plugin</artifactId> >> <version>9.1.0.M0</version> >> <dependencies> >> <dependency> >> <groupId>com.something.group</groupId> >> <artifactId>artifact-name</artifactId> >> <version>1.0</version> >> </dependency> >> </dependencies> >> </plugin> >> >> I would like to also add a directory (eg. src/test/resources) to the >> container classpath. Is there an easy way to do this? I remember seeing >> something about an "extraClasspath" tag that could be used under the >> <plugin><configuration> section, but it looks like that's been removed. I >> could potentially create a jar artifact to hold the contents of this >> directory and then add that new artifact as a dependency to the plugin, but >> that seems awkward. >> >> To reiterate my question, is there an easy way to add a directory to the >> container classpath when using the jetty-maven-plugin? >> >> Thank you. >> > > > _______________________________________________ > jetty-users mailing list > jetty-users@eclipse.org > https://dev.eclipse.org/mailman/listinfo/jetty-users > >
_______________________________________________ jetty-users mailing list jetty-users@eclipse.org https://dev.eclipse.org/mailman/listinfo/jetty-users
