2008/1/26, Piero Sartini <[EMAIL PROTECTED]>: > > during my license-problem-busting I noticed that in struts-core there > > are some classes using TestNG and JUnit, therefore these dependencies > > must be at compile-scope. > > Sorry for the (maybe) stupid question - but does this mean that there are > licensing problems with TestNG and S2? It seems that TestNG is using Apache > License 2.0... do I miss s.th.?
No, no problems. There is only the need to include a line in the NOTICE.txt within the binary distribution. > > Or did I misread your words and this is s.th. you recognized while checking > other parts of the source, unrelated to TestNG and those license problems you > mentioned? No, the problem is that there are libraries usually put in "test" scope (TestNG, JUnit) that are under "compile" scope. Unless you are providing a "test" package (like JCatapult or "shale-test"), you have to put these classes under "test" scope. > > But now you made me curious about what your license-problem-busting is all > about - if there is any source of information about this, could you please > give me a pointer? I am under the impression that apache is very strict with > licensing and that involved people do care a lot about these kind of things. The problem is that, when we package everything in binary form, we ship 3rd party packages together with Struts 2. We should *at least* add a line in the NOTICE.txt file, and when the package is not licensed under the ASL, the license of the package itself. It's not Apache-related, but License-Related. Ciao Antonio --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
