To me it feels like a bug that the plugin ignores my configuration for
the file name and location (even if that would break the tool itself.)
Do you agree? Should the docs be updated to explain that these
things are not actually configurable?
I doubt having every project set svn:ignore is going to be
acceptable-- this needs to be transparent to the projects, with plugin
configuration in the corporate parent pom and a pre-configured build
definition on the CI server to run the scans. That part will likely
need to be taken up with Ounce, though, not the plugin devs. :)
Thanks,
--
Wendy
On Wed, Jul 9, 2008 at 4:04 PM, Brian E. Fox <[EMAIL PROTECTED]> wrote:
> The actual problem is that applicationFile is used to tell scan what
> application to read and scan. There are no options to control where the
> files are produced from application and project mojos...this is because
> the ounce tool has an expectation where they are. It's the same as the
> eclipse .project and .classpath files essentially. Just add them to svn
> ignore...
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
