Jetty

John,

Mmm, I could not replicate. Could you try using the semi-colon as the separator (instead of comma) and see if the error goes away?
Btw, there's a bug with using ResourceCollection on static resources (JETTY-683) on 6.1.12rc1. Its fixed for 6.1.12( now available in 6.1 branch)

Thanks,
dyu

David,

Semicolons don't make a difference. But some more information for you. The configuration works fine under jdk 1.5. I get the problem only when running under 1.6. The version I'm using is:

java version "1.6.0_05"
Java(TM) SE Runtime Environment (build 1.6.0_05-b13-120)
Java HotSpot(TM) 64-Bit Server VM (build 1.6.0_05-b13-52, mixed mode)

I really think that maven is getting confused by the overridden setters.

Here is more output from mvn -X jetty:run

[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Failed to configure plugin parameters for: org.mortbay.jetty:maven-jetty-plugin:6.1.12rc1

(found static expression: '/Users/john/Projects/mlsdb/target/mlsdb,/Users/john/Projects/mlsdb/src/main/webapp' which may act as a default value).

Cause: Cannot assign configuration entry 'resources' to 'class [Lorg.mortbay.resource.Resource;' from '/Users/john/Projects/mlsdb/target/mlsdb,/Users/john/Projects/mlsdb/src/main/webapp', which is of type class java.lang.String
[INFO] ------------------------------------------------------------------------
[DEBUG] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Error configuring: org.mortbay.jetty:maven-jetty-plugin. Reason: Unable to parse the created DOM for plugin configuration
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:587)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.PluginConfigurationException: Error configuring: org.mortbay.jetty:maven-jetty-plugin. Reason: Unable to parse the created DOM for plugin configuration
at org.apache.maven.plugin.DefaultPluginManager.populatePluginFields(DefaultPluginManager.java:1288)
at org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:661)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:429)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
... 16 more
Caused by: org.codehaus.plexus.component.configurator.ComponentConfigurationException: Cannot assign configuration entry 'resources' to 'class [Lorg.mortbay.resource.Resource;' from '/Users/john/Projects/mlsdb/target/mlsdb,/Users/john/Projects/mlsdb/src/main/webapp', which is of type class java.lang.String
at org.codehaus.plexus.component.configurator.converters.AbstractConfigurationConverter.fromExpression(AbstractConfigurationConverter.java:149)
at org.codehaus.plexus.component.configurator.converters.composite.ArrayConverter.fromConfiguration(ArrayConverter.java:62)
at org.codehaus.plexus.component.configurator.converters.ComponentValueSetter.configure(ComponentValueSetter.java:207)
at org.codehaus.plexus.component.configurator.converters.composite.ObjectWithFieldsConverter.processConfiguration(ObjectWithFieldsConverter.java:137)
at org.codehaus.plexus.component.configurator.converters.composite.ObjectWithFieldsConverter.fromConfiguration(ObjectWithFieldsConverter.java:90)
at org.codehaus.plexus.component.configurator.converters.ComponentValueSetter.configure(ComponentValueSetter.java:207)
at org.codehaus.plexus.component.configurator.converters.composite.ObjectWithFieldsConverter.processConfiguration(ObjectWithFieldsConverter.java:137)
at org.codehaus.plexus.component.configurator.converters.composite.ObjectWithFieldsConverter.fromConfiguration(ObjectWithFieldsConverter.java:90)
at org.codehaus.plexus.component.configurator.converters.ComponentValueSetter.configure(ComponentValueSetter.java:247)
at org.codehaus.plexus.component.configurator.converters.composite.ObjectWithFieldsConverter.processConfiguration(ObjectWithFieldsConverter.java:137)
at org.codehaus.plexus.component.configurator.BasicComponentConfigurator.configureComponent(BasicComponentConfigurator.java:56)
at org.apache.maven.plugin.DefaultPluginManager.populatePluginFields(DefaultPluginManager.java:1282)
... 19 more

John,

Tried it on java 1.6_06 on windows. Got no errors.
It looks like its spefically a java 1.6-on-mac issue.
And more likely a maven2 issue.
I'll see if I can find a workaround

Cheers

Got the same error on

maven2.0.9
Windows
jdk1.6.0_07

So probably not a mac-issue.

Tried with

jdk1.5.0_16
maven2.0.9
Windows

Same error.. Just to be sure 1.5 didnt solve it.

Sorry for making multiple comments and not one.

Just wanted to inform its the same error using 7.0.0pre3.

Thats interesting... It works for me on java 1.6.06 on windows xp.

java version "1.6.0_06"
Java(TM) SE Runtime Environment (build 1.6.0_06-b02)
Java HotSpot(TM) Client VM (build 10.0-b22, mixed mode, sharing)

To avoid the maven overloading bug, use resourcesAsCSV instead.

<baseResource implementation="org.mortbay.resource.ResourceCollection">
<resourcesAsCSV>src/main/webapp,target/mlsdb</resourcesAsCSV>
</baseResource>

Cheers

I can confirm this bug on Linux. Version info:

mvn -v
Maven version: 2.0.8
Java version: 1.6.0_07
OS name: "linux" version: "2.6.24-21-generic" arch: "i386" Family: "unix"

Using resourcesAsCSV did work.

This was using 6.1.12.rc2

I had the same issues and was able to get it working, using 6.1.12.rc3 on Maven 2.2.1. However, if you specify a contextPath other than /, it will not work.

If I enter a contextPath value as eg. "/test" and goto http://localhost:9081/, I can see that my additional source path is being recognized by Jetty, but somehow these resources are not servable.

Working configuration:
----------------------

<plugin>
<groupId>org.mortbay.jetty</groupId>
<artifactId>maven-jetty-plugin</artifactId>
<version>6.1.12.rc3</version>
<configuration>
<scanIntervalSeconds>10</scanIntervalSeconds>
<webDefaultXml>src/dev/jetty/pb_webdefault.xml</webDefaultXml>
<connectors>
<connector implementation="org.mortbay.jetty.nio.SelectChannelConnector">
<port>9081</port>
<maxIdleTime>60000</maxIdleTime>
</connector>
</connectors>

<!-- For Dojo integration -->
<webAppConfig>
<contextPath>/</contextPath>
<baseResource implementation="org.mortbay.resource.ResourceCollection">
<resourcesAsCSV>src/main/webapp,..\pb-dojo\dist\release</resourcesAsCSV>
</baseResource>
</webAppConfig>
<!-- End Dojo integration -->

<jettyEnvXml>${basedir}/src/dev/jetty/jetty-env.xml</jettyEnvXml>
</configuration>
<dependencies>
...
</dependencies>
</plugin