You COULD experiment with configuring in the remote-resources plugin with the Apache resource bundle thing. It generates a DEPENDENCIES file that could be included directly in the assembly. It normally uses the information available in the poms if possible, but it ALSO supports a supplementalModel file that provides supplimental information for poms that have missing stuff.
For CXF, it works quite well. I can look at the generated DEPENDENCIES and a quick scan for some of the keywords like "unnamed" or "unknown" lets me know that I need to go research more and update the supplimental model. Otherwise, I don't need to do much. Just a thought. I tend to like to automate as much as possible. I'm quite lazy. :-) Dan On Wednesday 29 September 2010 4:13:40 am Bertrand Delacretaz wrote: > On Wed, Sep 29, 2010 at 9:42 AM, Richard Hirsch <[email protected]> wrote: > >>>> ... > >>>> Unknown: Unnamed - com.twitter:xrayspecs:pom:1.0.7, Unnamed - > >>>> org.jboss.netty:netty:pom:3.1.5.GA, Unnamed - > >>>> org.scala-tools:vscaladoc:pom:1.1-md-3, asm, cglib > > > > netty is Apache 2.0 - http://www.jboss.org/netty/downloads.html > > vscaladoc is Apache License 2.0 - see http://code.google.com/p/vscaladoc/ > > xrayspecs is also Apache 2.0 but you have to look in the source to see > > the license - > > http://github.com/twitter/xrayspecs/blob/master/src/main/scala/com/twitt > > er/xrayspecs/Time.scala > > Looks all good to me, thanks for checking! > > > Should this information be placed in the THIRD-PARTY.txt file and be > > placed in the trunk - same level as KEYS, etc? Is there a particular > > format for this file? > > I don't think there's a standard but I think it's good to keep this > information around, to avoid having to re-check every time someone > like me is being picky with this ;-) > > THIRD-PARTY.txt at the same level as KEYS etc. looks good to me, maybe > with an intro text that explains its purpose. > > -Bertrand -- Daniel Kulp [email protected] http://dankulp.com/blog
