Guys,
I might also include in the discussion an email that I found useful in deciding
how to incorporate RAT [1]. I'd invite others, including Ross, to comment as
well, but I think there is great value in knowing immediately if something is
potentially problematic from a licensing perspective.
Hi Andrew and Dave,
Interesting. Yeah I think that RAT shouldn't per se block a build unless we
specifically ask it to (i.e., where it matters, on releases and distribution).
That said, I think this can be overcome by commenting out the RAT plugin in
your xmlps code. Question: the code you are
Andrew,
I introduced RAT as part of the build process while working toward closing out
OODT-3 [1]. The reason for running RAT as part of the builds for some
components is that we know immediately when we introduce code that is not
compliant with licensing, nor do will build and push out anythin
Hey guys,
Can anyone provide me with a little bit of information as to what is
going on here?
I'm working with Dave Kale to implement OODT-29 (import web-grid into
apache oodt) and we've recently been frustrated by something which
appears to be related to RAT being a little (too?) controllin
