[#SUREFIRE-118] Cannot override read-only parameter: classpathElements

Maven Surefire

Cannot override read-only parameter: classpathElements

Created: 08/Feb/06 06:45 AM Updated: 23/Nov/07 08:04 PM

Component/s:

None

Affects Version/s:

1.5.2 (2.1.2 plugin), 2.0 (2.2 plugin)

Fix Version/s:

2.4

Time Tracking:

Not Specified

File Attachments:

additionalClasspaths.patch (1 kB)

Issue Links:

Duplicate

This issue is duplicated by:

~~SUREFIRE-180~~ Ability to add additions to classpath

Patch Submitted:

Yes

Description

« Hide

When calling "mvn site" on a multi-module project the goal "surefire:test" fails for the second project:
Error configuring: org.apache.maven.plugins:maven-surefire-plugin. Reason: ERROR: Cannot override read-only parameter: classpathElements in goal: surefire:test

"mvn test" works and runs the tests on all modules.

All

Comments

Work Log

Change History

Sort Order:

[ Permalink | « Hide ]

Jean-Laurent de Morlhon added a comment - 16/Feb/06 07:05 AM

this is still happening with a fresh build of the plugin with svn at revision 1496

[ Permalink | « Hide ]

Brett Porter added a comment - 04/Mar/06 12:11 AM

what part of the site is failing? surefire-report, or cobertura, or something else?

[ Permalink | « Hide ]

David J. M. Karlsen added a comment - 26/Jul/06 03:34 PM

And what are your effective <surefire> settings for each artifact.
The variable is readonly, and the configuration may be errorneous?

[ Permalink | « Hide ]

Zarar Siddiqi added a comment - 27/Sep/06 03:10 PM

OK, I'm trying to run StrutsTestCase with Maven 2.x and need the web.xml and struts-config.xml to be in the classpath, which they are not by default.

So, I have the following configuration for the surefire plugin:

<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-surefire-plugin</artifactId>
<version>2.2</version>
<configuration>
<classpathElements>
<classpathElement>target/${project.artifactId}-${project.version}</classpathElement>
</classpathElements>
</configuration>
</plugin>

And this expectedly yields:

Error configuring: org.apache.maven.plugins:maven-surefire-plugin. Reason: ERROR: Cannot override read-only parameter: classpathElements in goal: surefire:test

The reason this is expected is because an explanation is provided here:

http://www.nabble.com/testing-webapp-with-surefire-tf519140.html#a1403158

Brett Porter has recommended requesting another element called additionalClasspathElements to be added which would not be read-only and thus allow for additional classpath elements to be added.

I tried that using the following but it didn't get me anywhere.

<additionalClasspathElements>
<classpathElement>target/${project.artifactId}-${project.version}</classpathElement>
</additionalClasspathElements>

Any ideas?

[ Permalink | « Hide ]

Zarar Siddiqi added a comment - 27/Sep/06 10:26 PM

I've created a patch against revision 450675 which fixes this issue and allows you to specify additional classpaths:

<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-surefire-plugin</artifactId>
<configuration>
<additionalClasspathElements>
<additionalClasspathElement>path/to/additional/resources</additionalClasspathElement>
</additionalClasspathElements>
</configuration>
</plugin>

This patch does pretty much the same thing as the one supplied in MSUREFIRE-153 but I can't understand why that one hasn't been applied.

I'm using this for now.

[ Permalink | « Hide ]

Peter Anning added a comment - 14/Aug/07 10:59 PM

I don't want to patch core maven I've done this before and it leads to a maintenance headache. For now I am running Junit via the ant plugin but this is not the point of maven. Please can we get this into the core asap.

Cheers
Peter

[ Permalink | « Hide ]

Dan Fabulich added a comment - 23/Nov/07 08:04 PM

Fixed and integration tested in revision 597783.