Basically, I deleted my .m2/repository/dkpro, then went to my dkpro-core git directory and did the following at the command line:
mvn clean
mvn install -DskipTests
Then I imported the projects in Eclipse, and most of them seem OK. In particular, the one I am need to modify (dkpro-core-api-io-asl) does not show any errors.
However, when I try to do a mvn install on that project, I get the following error:
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:3.1.1:analyze-only (default) on project dkpro-core-api-io-asl: Dependency problems found -> [Help 1]
Any idea what might be causing the problem?
Thx.
> > Then I imported the projects in Eclipse, and most of them seem OK. In particular, the one I am need to modify (dkpro-core-api-io-asl) does not show any errors.
>
> The dkpro-core-api-io-asl contains generic IO code. The BratReader/BratWriter classes are in the dkpro-core-io-brat-asl module.
I know, but the problem I am having is caused by method getRelativePath() which BratWriter inherits from JCasFileWriter_BaseImpl. The latter is in dkpro-core-api-io-asl.
> Declaring too few or too many dependencies in the POM can cause problems for downstream users:
>
> - If there are too many dependencies (i.e. dependencies are declared which are not really used) then it might unnecessarily cause dependency version conflicts with other libraries being used in a client project.
>
> - If there are too few dependencies, it might be that Maven ends up preferring an incompatible version referenced elsewhere in a client project.
>
> So the rule is: all and only dependencies which are directly referenced by the source code must be declared in the POM.
>
> The maven dependency plugin enforces this rule. It also prints which are the offending dependencies you should add/remove, although you might have to scroll back to just before the reactor build summary to find that information in the logs.
>
> Cheers,
Thx, that clarifies things.
With this hint, I was able to locate the culprit dependancy, and get dkpro-core to work. But it was no picnic. In the end, I found what helped was to do all the mvn commands from Terminal before importing the projects into eclipse.
I will submit a pull request for my fix as soon as my employer has signed the DKPro Contributor agreement.
Cheers.
>
> -- Richard
--
You received this message because you are subscribed to a topic in the Google Groups "dkpro-core-developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/dkpro-core-developers/kt14TFmN6Sg/unsubscribe.
To unsubscribe from this group and all its topics, send an email to dkpro-core-devel...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dkpro-core-developers/3FA06CE8-267E-4C3C-9C8B-A237A20D5C4B%40gmail.com.
--
You received this message because you are subscribed to a topic in the Google Groups "dkpro-core-developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/dkpro-core-developers/kt14TFmN6Sg/unsubscribe.
To unsubscribe from this group and all its topics, send an email to dkpro-core-devel...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dkpro-core-developers/BD3E24BD-F6D2-4521-800E-63C7C81F9DD9%40gmail.com.