Jason van Zyl wrote:
What is it concretely you are trying to do. Often users give us
solutions to their problems without actually telling us what the problem
is. We really need to know what you're trying to do first. We definitely
don't want duplication and is something we try to avoid so we need more
details.
I'll try again with an example:
Given a project with three subprojects, I want to use a checkstyle definition
that is valid for all three subprojects. (The checkstyle definition itself
differs from project to project since it mostly depends on the style used by
the customer.)
+- toplevel/
|
+- pom.xml
+- src/
| |
| +- java/
| |
| +- resources/
| |
| +- checkstyle.xml
|
+- subproj1/
| |
| +- pom.xml
| +- src/
| +- ...
|
+- subproj2/
|
+- pom.xml
+- src/
+- ...
Now, if I want to include a checkstyle configuration like the following in
toplevel/pom.xml so that it is picked up by all subprojects:
...
<configuration>
<configFile>${topdir}/src/java/resources/checkstyle.xml</configFile>
</configuration>
...
I cannot use ${basedir} since this always yields the base directory of the
subproject being built. What I want is to access resources relative to the
toplevel directory.
I don't want to use a fixed URL for the location since I want to have versioning
for the file and I also need it to be in a relative location since a customer
will build the project in a location that may not even have access to the
fixed URL (even though I could work around this using a profile).
Cheers,
// Bruno
PS: I am aware that I cannot currently set the checkstyle configuration, see
http://jira.codehaus.org/browse/MNG-587 and
http://jira.codehaus.org/browse/MNG-1113
(I have a local copy that allows me to do anyway until an official solution is
out).
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
