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. 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?
regards musachy On 2/11/07, Ted Husted <[EMAIL PROTECTED]> wrote:
It is in the -sources JAR, though, but that maven folder is not. Weird. On 2/11/07, Ted Husted <[EMAIL PROTECTED]> wrote: > From a clean Maven repository, and a clean checkout of the 2_0_x > branch, with no TLD present, > > $ mvn clean install site -P all,alljars,pre-assembly > > does not generate a core JAR with a TLD for me. > > The Manifest.mf is under META-INF, along with the mysterious maven > folder, but the not TLD. > > If I build it a second time, the TLD does appear, which implies it's > picking up the TLD from the first build. > > -Ted. > > > On 2/11/07, Musachy Barroso <[EMAIL PROTECTED]> wrote: > > Inside the META-INF folder inside the core jar, there is a "maven" folder. I > > don't remember that folder, is it supposed to be there? > > > > musachy > > > > On 2/11/07, Musachy Barroso <[EMAIL PROTECTED]> wrote: > > > > > > > > > On 2/11/07, Ted Husted <[EMAIL PROTECTED]> wrote: > > > > > > > > On 2/11/07, Musachy Barroso <[EMAIL PROTECTED]> wrote: > > > > > I'm not sure what you mean. If I delete the TLD and do: > > > > > > > > > > mvn compile > > > > > > > > > > on core, it generates the TLD. > > > > > > > > Try it from a clean checkout and look to see if the TLD is in the JAR. > > > > > > > > > > > > Clean checkout: > > > > > > mvn -o -Dmaven.test.skip=true -Pcore > > > > > > and the TLD is under META-INF in the jar, are you doing any other step? > > > > > > > > > Meanwhile, we seem to have two tags (doubleselect and > > > > optiontransferselect) )with vacillating HTML docs. > > > > > > > > r506206 > > > > - <td align="left" > > > > valign="top">Set the list key of the second attribute</td> > > > > + <td align="left" > > > > valign="top">The key expression to use for second list</td> > > > > > > > > r506210 > > > > - <td align="left" > > > > valign="top">The key expression to use for second list</td> > > > > + <td align="left" > > > > valign="top">Set the list key of the second attribute</td> > > > > > > > > > > > > When I build it again, the patch comes out > > > > > > > > - <td align="left" > > > > valign="top">Set the list key of the second > > > > attribute</td> > > > > + <td align="left" > > > > valign="top">The key expression to use for > > > > second list</td> > > > > > > > > I totally don't understand what is happening here. Every time I commit > > > > the latest HTML docs, they revert to an alternate form. Spooky. > > > > > > > > > > > > I will check it out. > > > > > > musachy > > > > > > > > > -- > > > "Hey you! Would you help me to carry the stone?" Pink Floyd > > > > > > > > > > > -- > > "Hey you! Would you help me to carry the stone?" Pink Floyd > > > > > -- > HTH, Ted. > * http://www.husted.com/struts/ > -- HTH, Ted. * http://www.husted.com/struts/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- "Hey you! Would you help me to carry the stone?" Pink Floyd
