You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Tibor Digana (JIRA)" <ji...@apache.org> on 2015/06/23 23:00:43 UTC
[jira] [Closed] (SUREFIRE-574) additionalClasspathElements-feature
improved
[ https://issues.apache.org/jira/browse/SUREFIRE-574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tibor Digana closed SUREFIRE-574.
---------------------------------
Resolution: Fixed
commit 552f876438abb66424783008ed143b78cb65dc5c
> additionalClasspathElements-feature improved
> --------------------------------------------
>
> Key: SUREFIRE-574
> URL: https://issues.apache.org/jira/browse/SUREFIRE-574
> Project: Maven Surefire
> Issue Type: Improvement
> Components: Maven Surefire Plugin
> Affects Versions: 2.4.3
> Environment: any
> Reporter: Christian Moser
> Assignee: Tibor Digana
> Priority: Minor
> Fix For: 2.19
>
> Attachments: surefireAddClasspath.diff
>
>
> I need to extend the classpath of the surefire-plugin by a standard java classpath (file.jar;file2.jar;file3.jar) contained in a property accessible by the executing pom file.
> Unfortunatelly you have to add every single file by your own:
> <additionalClasspathElements>
> <additionalClasspathElement>file1.jar</additionalClasspathElement>
> <additionalClasspathElement>file2.jar</additionalClasspathElement>
> </additionalClasspathElements>
> So I've wrote a simple patch to extend the classpath by adding just one element:
> <additionalClasspathElements>
> <additionalClasspathElement>${var.cp}</additionalClasspathElement> (var.cp contains: file1.jar;file2.jar;file3.jar etc)
> </additionalClasspathElements>
> What do you think about it and will you add this improvement to the release version?
> I need this feature in my daily busines..
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)