|
[
Permlink
| « Hide
]
David Eric Pugh added a comment - 27/Jan/05 02:34 PM
Can you provide more detail on what you are trying to accomplish? What would be a use case for more variables?
For instance, in our current project, we need to have an external folder with some property files in the classpath. In Eclipse 2.1, one would solve this by adding a environment variable that points to this folder, and add it to the build path of the project. We could solve this by copying the required property files into the project source folder, but this is not what we want, as it can be multiple property files, and they are shared between projects.
This is what we use:
maven.eclipse.classpath.include=src/conf,src/test-resources That adds the src/conf and src/test-resources to the classpath and then everything works! Yes, and we do that already for project local properties that reside in a project relative folder. But this is for system wide property files in folders that are referred to with eclipse classpath variables which are outside the project.
Okay.. I see, so you are pulling in system wide property files. Now, my question is, how (if you aren't using Eclipse, but instead using Maven) and running goals like maven test or jar, how do those property files get pulled into the classpath?
They don't. It's only inside eclipse for integration test clients that we run manually. So it's only relevant for setting up the eclipse project correctly, not for building the project with maven.
I do realise that it might sound a bit out of scope of a maven-plugin, but reality is that we cannot use the eclipse goals if this is not implemented, as we would have to manually add this after every run.
|
|||||||||||||||||||||||||||||||||||||||||||||
 |
|
New Feature
Open
Major
Custom eclipse variables in .classpath generation