On Friday 03 September 2010 2:34:00 am han hongfang wrote: > Forward to dev list to see if somebody has some advice for me on this > question.
It's not the release plugin, it's the remote-resources plugin generating them. You would need to figure out where the remote-resources thing is configured. You don't mention which project, but if it's and Apache project using the Apache parent pom, that would be pulled in automatically. Th easy fix is to rename your files to LICENSE and and NOTICE. remote- resources will not overwrite new files if existing files exist. Dan > > Best regards, > > Han Hong Fang > > ---------- Forwarded message ---------- > From: han hongfang <hanhongf...@gmail.com> > Date: Fri, Aug 27, 2010 at 5:27 PM > Subject: [maven-release-plugin] Is it possible to configure > maven-release-plugin to NOT pull in META-INF/LICENSE and NOTICE > To: us...@maven.apache.org > > > > Hi, > > Our project uses maven-release-plugin in the release process. We maintain > the LICENSE.txt and NOTICE.txt (which contains module specifc statement) > for each of our modules in subversion. When we issue mvn release:prepare, > standard LICENSE and NOTICE files are pulled into META-INF folder of > target artifact. These standard files are duplicated with LICENSE.txt and > NOTICE.txt we maintained. > > Is it possible to configure maven-release-plugin to not pull in these > files? If yes, could you show me how to do it? > > Thanks in advance for your reply! -- Daniel Kulp dk...@apache.org http://dankulp.com/blog --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
