would be nice if <lib> configuration element supported local jars, i.e.,
workaround is to install local jars in m2/repository.
should not be so difficult to implement. Comes with the next milestone (maybe april).
i will do it until next week but i dont understand why somebody should use it that way. There is no difference between copy a configuration jar and copy all configuration files to every project.
The default way to provide tomcat configuration e.g. setting JNDI resources in context.xml is to copy your configurations under /src/main/tomcat.
This Dir will be copied into the tomcat root directory. So you can overwrite the default files with your project specific ones.
We used this to define a bunch of JMS and database resources in context.xml. Because we have a lot of projects we had to changed this configuration in every projekt if one resource has to be changed. So the configuration.jar feature is realy useful for us.
An example can be found here: https://github.com/t7mp/examples/tree/master/simple
Is this an adequate solution for your problem? If yes i won't implement this feature because i think providing the configuration as files in the configuration directory is the same as putting a jar with the configuration into the projekt.
Ok, i missunderstood the issue. Now it is clear to me. Verry usefull feature I hope to get it done during the upcomming week.
I implemented this feature in the last days. Russt can you please verify that it works for you. You can find an example configuration here. It is not necessary to specify an 'scope'. That makes no sense in this case.
Let us know and reopen this issue if it do not work for you. The version you have to use is 0.9.10.M2. That version should be available in central on monday.
thanks for your response. I will have a look what's going wrong.
sorry but I couldn't reproduce the exception. I added one more integration-test for running in forked mode but all integration-tests were successful. I also use the specified version (0.9.10.M2) on the examples project. Without any exception. All my tests were executed with Maven 3.0.4. What version do you use?
can you please verify that version 0.9.10.M2 works?
I hope the latest release 0.9.10.M3 works better for you ;-). The tests passed successfully with Maven 2. Please try again when the plugin will be available at central.