David Jencks wrote:
On May 12, 2009, at 7:27 AM, Ate Douma wrote:
<snip/>
After several fruitless attempts to force the assembly plugin to do
what we need, I concluded there is no way to "fix" this without
resorting to custom assemblies, *per project* :(
And so I did. I modified the portals-pom and removed the configuration
element and added a custom project assembly descriptor to both the 1.0
and 2.0 spec projects. Now this works fine AFAICT.
I should have mentioned something about this.
I think we can keep using the built-in "project" descriptor because we
use this only during release. The release plugin does an svn export of
the project before building the release. This won't have any or the
.eclipse files, and if we get the assembly to run early enough in the
build, the velocity.log file won't be there either.
I'm not sure how that can work and produce the expected/required resulting NOTICE file, besides how to ensure the assembly is run first
before the m-r-r-plugin which I haven't figured out yete how to do.
The "odd" thing about such a release distro project assembly build is that it should contain the actual project source tree but also a
complete and valid NOTICE file. As we only have a partial NOTICE file in svn, augmented by the m-r-r-plugin at build time, which one should
be provided in the assembled distro? Either way this seems like conflicting requirements to me.
And, if we choose (or are required) to include the augmented NOTICE file, we're back to square one, as this will result in the velocity.log
to be included as well.
Maybe there is a way to suppress the creation of the velocity.log or have it put somewhere else, using a -D system property overriding the
logdir?
Any thoughts?
I'd rather stick with the built-in descriptor.
thanks
david jencks
