Kenney Westerhof wrote: > Thinking about this, I'm not really sure anymore what the correct solution > would be. We have the following features/demands:
I had the same feeling yesterday when I wrote the last proposal :) > > 1) being able to split resources up into two groups: the filtered-on-copy > group and the 'just-copy' group. > > 2) being able to specify different filter properties using profiles > > 3) (?) being able to split filtered resources up into more groups (not > just the one group as said in 1), so each group can have a different filter > property files. > > > 4) being able to specify multiple properties files / having a default file > so users can override. Much like project.properties/build.properties > in maven1. > > 5) Nice to have: defining the tokens in the pom so the plugin > could check which ones are missing and you have an overview of > all the configuration settings used in all the resource files > (the latter being more important). > > More ideas? Comments? > > I think it's best to go back after a while, look at > what you originally _needed_ in the first place, and then fill in the > blanks with solutions. ;) > Hehe, now, actually the more I think about it the more I agree with your list, meaning we don't need 3) and 5) is nice to have but not important. I could imagine that most users would not use 5) anyway and would use the default. I'll start filing a JIRA entry soon with a proposal and as soon as we agree on something there, I will try to implement it. Carsten -- Carsten Ziegeler - Open Source Group, S&N AG http://www.s-und-n.de http://www.osoco.org/weblogs/rael/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
