You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by Peter Klügl <pk...@uni-wuerzburg.de> on 2013/05/14 13:45:36 UTC
Dependencies to other projects
Hi,
I am planning to extend the UIMA Ruta documentation where ruta projects
making use of java projects in the same workspace. The idea would be to
add a simple maven project, which has dependencies, for example, to
DKPro (ASL/GPL), and therefore takes care of the availability of the
implementation and models. The UIMA Ruta project then has a dependency
to that java project and is able to execute the analysis engines within
its script files.
I wonder if I can set a simple dependency to an artifact licensed under
GPL in an example project. Does that already "include" the artifact?
There would be no class at all, which depends on the artifact, only a
descriptor, which points to the implementation.
Besides the license thing, are there any reasons or problems to add a
dependency to other projects? I could actually also refer to our sandbox
components for the example in the documentation, but DKPro has simply
more components.
Best,
Peter
Re: Dependencies to other projects
Posted by Marshall Schor <ms...@schor.com>.
On 5/14/2013 7:45 AM, Peter Klügl wrote:
> Hi,
>
> I am planning to extend the UIMA Ruta documentation where ruta projects
> making use of java projects in the same workspace. The idea would be to
> add a simple maven project, which has dependencies, for example, to
> DKPro (ASL/GPL), and therefore takes care of the availability of the
> implementation and models. The UIMA Ruta project then has a dependency
> to that java project and is able to execute the analysis engines within
> its script files.
>
> I wonder if I can set a simple dependency to an artifact licensed under
> GPL in an example project. Does that already "include" the artifact?
> There would be no class at all, which depends on the artifact, only a
> descriptor, which points to the implementation.
According to http://www.apache.org/legal/resolved.html#prohibited
The component cannot be distributed, but it's OK if the component's license
terms don't affect the Apache product's licensing - the example given is you can
use a GPL compiler, for instance, during the build.
The next item in the list of issues, says that if a component is "optional",
then we can include instructions on how to obtain and install the non-included
work. The main question for deciding on if it is optional enough, is "Will the
majority of users want to use my product without this component".
-Marshall
>
> Besides the license thing, are there any reasons or problems to add a
> dependency to other projects? I could actually also refer to our sandbox
> components for the example in the documentation, but DKPro has simply
> more components.
>
> Best,
>
> Peter
>
Re: Dependencies to other projects
Posted by Richard Eckart de Castilho <ri...@gmail.com>.
Hi,
DKPro Core 1.4.0 is available via Maven Central (mostly, except models
which are currently still in another public repository) and you should
be able to find components for most thing in the ASL part. There shouldn't
be an immediate need to use the GPLed components. You'll want to avoid
using the TreeTagger component due to the license of TreeTagger.
Cheers,
-- Richard
Am 14.05.2013 um 13:45 schrieb Peter Klügl <pk...@uni-wuerzburg.de>:
> Hi,
>
> I am planning to extend the UIMA Ruta documentation where ruta projects
> making use of java projects in the same workspace. The idea would be to
> add a simple maven project, which has dependencies, for example, to
> DKPro (ASL/GPL), and therefore takes care of the availability of the
> implementation and models. The UIMA Ruta project then has a dependency
> to that java project and is able to execute the analysis engines within
> its script files.
>
> I wonder if I can set a simple dependency to an artifact licensed under
> GPL in an example project. Does that already "include" the artifact?
> There would be no class at all, which depends on the artifact, only a
> descriptor, which points to the implementation.
>
> Besides the license thing, are there any reasons or problems to add a
> dependency to other projects? I could actually also refer to our sandbox
> components for the example in the documentation, but DKPro has simply
> more components.
>
> Best,
>
> Peter