Jörg Schaible-2 wrote:
>
> Why don't you simply keep those filters in an own module and pack them
> into
> an archive? Every other project that needs to access them may declare a
> dep
> on that artifact and can user the build-helper plugin to unpack them into
> a
> temporary location.
>
> - Jörg
>
Two reasons:
1) I'm really new at maven and i still haven't gotten 100% into the maven
packaging mindset. When i have more time i'll investigate your suggestion
closer.
2) It seems non-intuitive to bundle 4 xml files into an archive, then
expand that archive out before i compile my java files ('cause i need to
filter them) for all 12 of my sub-projects vs: have my sub-project simply
point to the filter in the parent.
--
View this message in context:
http://www.nabble.com/How-can-I-get-the-path-for-a-root-pom.xml%27s-basedir-in-a-multimodule-project-with-pom-inheritance-tf4577123s177.html#a13435319
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
