> On 13. Apr 2018, at 11:58, Ben Engbers <ben.engb...@be-logical.nl> wrote:
>> the red signs indicate problems.
>> Is there output in the 'Problems'-View (Window->Show View->Problems)?
> A lot of lines like this one:
> Description Resource Path Location Type
> Archive for required library:
> '/home/bengbers/.m2/repository/org/jdom/jdom/1.1/jdom-1.1.jar' in
> project 'basex-api' cannot be read or is not a valid ZIP file
> basex-api Build path Build Path Problem
You seem to have a maven problem. The .m2 folder is mavens local repository (it
is used to store all your project’s dependencies (plugin jars and other files
which are downloaded by Maven)). Perhaps during the recent installation you
went offline or something like that).
At least, this is not a basex related problem.
However, you can try to get it resolved by
- removing the whole maven folder:
$ rm -rf ~/.m2
- Eclipse: Project -> Clean all projects
(errors and warning afterwards are expected in the package explorer view)
- Eclipse: Package Explorer View - right-click one of the basex-xxx entries ->
Maven -> Update Project -> Select All (basex-api, basex-core, basex-examples,
basex-tests)
The expectation is that the maven local repository is rebuild (dependencies
downloaded again) without problems.
Afterward the automatic build will probably kick in and compile all projects.
Hope this helps,
Alex
