In preparation to the 3.1-final vote, I ran the same set of tests as we did for
RC1. All tests are on Java 1.6 unless specified otherwise. You can compare it
with the previous results at http://markmail.org/message/slaj64iunxbeg4cs .
Essentially everything is the same, so the latest 3.1 changes
Hi Mike,
On Aug 30, 2014, at 3:48 PM, Mike Kienenberger wrote:
> If it is directly referenced by our tests,
It is.
> then I would say we should
> not have this as a dependency, since any code that references it is
> now polluted by the viral nature of LGPL.
Ok. I guess we’ll need to find a r
http://www.apache.org/legal/resolved.html#prohibited
Can Apache projects rely on components under prohibited licenses?
Apache projects cannot distribute any such components. As with the
previous question on platforms, the component can be relied on if the
Another one of Alex’s patches adds a test dependency on
org.fluttercode.datafactory:datafactory, which helps assembling complex test
object trees. One caveat is that Datafactory is under LGPL:
https://github.com/andygibson/datafactory/blob/master/license.txt
I am about 80% certain that this is
Since we still don’t have commit emails, I wanted to mention that I just
committed the latest set of pull requests from Alex. Among them jacoco test
coverage tool:
https://github.com/apache/cayenne/pull/7
Which seems the same thing as Emma that we used in the past. Nicely integrated
as an op
