If you want to remove those maven files, you need to update the POM to
include this:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-jar-plugin</artifactId>
<configuration>
<archive>
>>> <addMavenDescriptor>false</addMavenDescriptor>
</archive>
</configuration>
</plugin>
Paul
Musachy Barroso 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
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
