On 2/15/07, Musachy Barroso <[EMAIL PROTECTED]> wrote:
I think the problem is that when the TLD is generated into the META-INF folder, maven already copied the resources to the target folder, so the new TLD doesn't make it into the jar file.
Sounds like the TLD is getting generated too late in the build lifecycle, then. What phase is the plugin execution bound to?
We can change the output path to the target/class/META-INF, but maven doesn't create the META-INF folder if it is empty, so the annotations code fails to create the file. Is there anyway to force maven to create the META-INF folder?
Shouldn't the plugin create the directory if it doesn't exist? -- Wendy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
