Good point. Theoretical, I would say aries-extra if you are based on
Aries weaving. However, as Aries is a library, in order to use/test it
you have to use it in a container like Karaf. So as a ready to use
solution (with features), it could be in karaf-extra. Actually, it's
likely like the other Aries project: the library/API codebase is in
Aries, the execution (features and usage) is in Karaf.
Regards
JB
On 01/11/2014 01:02 PM, Krzysztof Sobkowiak wrote:
By the way, which project would be the best final place for the solution
with AspectJ? Karaf (in this case karaf-extra) or Aries (aries-extra)?
Best regards
Krzysztof
On 10.01.2014 08:06, Jean-Baptiste Onofré wrote:
I use an example again - AspectJ is licensed under EPL 1.0 license.
Assume I'd like to implement a WeavingHook using the AspectJ classes
(reference AspectJ as maven dependency and use the classes in my code).
Does it mean, my code can not be included in Apache licensed project,
but I can implement the hook in a project under other license and
eventually reference it in Karaf feature?
Correct, you can't include in Apache project. You can create your
project outside of Apache project and reference it. Same as before:
you can do your WeavingHook in karaf-extra.
--
Krzysztof Sobkowiak
JEE & OSS Architect | Technical Architect @ Capgemini
Capgemini <http://www.pl.capgemini.com/> | Software Solutions Center
<http://www.pl.capgemini-sdm.com/> | Wroclaw
e-mail: [email protected] <mailto:[email protected]> |
Twitter: @KSobkowiak
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
