search

SemanticApplicationDesignLanguage / sadl

Semantic Application Design Language (SADL) Open Source Code
http://semanticapplicationdesignlanguage.github.io/sadl/
Eclipse Public License 1.0
30 stars 12 forks source link

Bundle 'org.jsoup' cannot be resolved #643

Open agabaldon opened 3 years ago

agabaldon commented 3 years ago

Did a pull today and built successfully on the command line. But in Eclipse, I can't make the jsoup error go away.

Screen Shot 2021-04-01 at 12 19 08 PM

tuxji commented 3 years ago

I'm using Eclipse Java 2021-03 with the following installed software:

Name Version
Buildship: Eclipse Plug-ins for Gradle 3.1.5.v20210113-0929
DevStyle (includes Darkest Dark Theme) 1.11.0.202103191838
EclEmma Java Code Coverage 3.1.4.202012082030
Eclipse IDE for Java Developers 4.19.0.20210311-1200
Eclipse Java Development Tools 3.18.700.v20210303-1800
Emacs+ 4.3.4
Emacs+ Options 4.3.2
Git integration for Eclipse 5.11.0.202103091610-r
Java implementation of Git 5.11.0.202103091610-r
JustJ OpenJDK Hotspot JRE Complete 15.0.1.v20201027-0507
m2e - Maven Integration for Eclipse (includes Incubating components) 1.17.2.20210219-1922
m2e - slf4j over logback logging (Optional) 1.17.0.20200924-1339
m2e connector for the Maven Dependency Plugin 0.0.4.201409291703
Marketplace Client 1.9.1.v20210204-1408
Mylyn WikiText Editors 3.0.38.202008172112
POM Editor using LemMinX language server (includes Incubating components) 1.17.1.20210225-1838
Tip of the Day UI Feature 0.2.1300.v20210226-2208
TM Terminal 10.2.0.202012191711
Tycho Project Configurators 0.8.1.201704211436
Wild Web Developer XML tools 0.10.4.202102250843
Xtend IDE 2.25.0.v20210301-1429

After starting Eclipse with an empty workspace and doing the following steps, I had no errors and 797 warnings in my Problems tab (note I had imported the projects before so they already had .project files):

  1. Build the projects from the command line (mvn verify -DskipTests -Dtycho.localArtifacts=ignore)
  2. Import the projects into the workspace as existing Maven projects
  3. Open the project com.ge.research.sadl.target, open the file com.ge.research.sadl.target.target, and click "Set as Target Platform" in the upper right corner
  4. The Problem tab will go from XXX errors YYY warnings to no errors 797 warnings
  5. Open the file SadlMarkerDeserializerService.xtend and note there are no error markers on the "import org.jsoup.Jsoup" line

I had to additionally install the Xtend IDE from the Marketplace Client to get the same look as your screenshot since that software wasn't part of Eclipse Java originally, but there still were no errors even after restarting Eclipse and reopening the xtend file.

agabaldon commented 3 years ago

A clean install of Eclipse to 2021_03 and the SADL project worked. The question is what fixed it: upgrading Eclipse or reinstalling from scratch. I will try reinstalling 2020_12 and SADL from scratch when I have a chance.

Are there any upgrade requirements for Dev install or User (SADL plugin) install?

tuxji commented 3 years ago

SADL's target platform is Eclipse 2020-12. Dev installs (importing SADL projects into an Eclipse workspace) can succeed in both Eclipse 2020-12 and 2021-03. Even if the installed Eclipse platform is different than the target Eclipse platform, the errors will go away after you set the Eclipse workspace to the SADL projects' expected target platform. User installs (installing the SADL plugin into Eclipse) will succeed in Eclipse 2020-12 and may succeed in Eclipse 2021-03 as long as you don't have a conflicting Xtext SDK installed/required by other software. If you want to use Eclipse 2021-03, you're safer using Eclipse Java 2021-03 than Eclipse DSL 2021-03, which already has a newer Xtext SDK installed.

crapo commented 3 years ago

I suddenly got this error out of the clear blue, unclear why it suddenly appeared. I reloaded the platform, did a Maven update project on all projects, then ran a Maven clean followed by a Maven install and the problem disappeared.