Should not be... I published these changes... but you know I really
have no idea how mvn resolves some of these artifacts.
The more I use mvn, the more I hate remote artifact resolution...
though I had once thought that was one of the best features. BUT...
this has caused more grief than anything else that I can think of.
--jason
On Nov 17, 2006, at 1:35 PM, Dain Sundstrom wrote:
Are we using an old version? The reason I ask is I tried adding
the disclaimer file to some modules and the were not added to the jar.
-dain
On Nov 17, 2006, at 12:20 PM, Jacek Laskowski wrote:
On 11/17/06, Dain Sundstrom <[EMAIL PROTECTED]> wrote:
Maybe you fix got removed or the plugin got changed over last month.
All I know is that the jars weren't getting the files.
It's from plugins/tools-maven-plugin/src/main/java/org/apache/
geronimo/genesis/plugins/tools/CopyLegalFilesMojo.java
(just svn updated).
/**
* The default includes when no fileset is configured.
*/
private static final String[] DEFAULT_INCLUDES = {
"LICENSE.txt",
"LICENSE",
"NOTICE.txt",
"NOTICE",
"DISCLAIMER.txt",
"DISCLAIMER"
};
They're copied to
/**
* Directory to copy legal files into.
*
* @parameter expression="${project.build.outputDirectory}/META-
INF"
* @required
*/
Since it's already done, I'm fine with your change.
Jacek
--
Jacek Laskowski
http://www.jaceklaskowski.pl
