I agree the best long-term solution to this problem is to move the "*-jakarta" subprojects so they are not children of the parent pom. That way, when you import your projects into your IDE, these projects will not be automatically imported with everything else. Having them in a separate repo completely isolates them and is the most complete solution of all. With the projects isolated, the IDE will get the artifacts from the maven repository and not look for the missing code in these projects.
In Eclipse anyhow, you can work around the issue immediately by right clicking on the projects having the errors and selecting "Maven > Disable Workspace Resolution". Then you can run the unit tests within Eclipse. On 2024/02/25 10:57:34 Greg Huber wrote: > Also building in eclipse I get these strange errors > > Missing artifact org.apache.struts:struts2-freemarker-jakarta:jar:7.0.0-M3 > > Missing artifact > org.apache.struts:struts2-velocity-tools-jsp-jakarta:jar:7.0.0-M3 > > Missing artifact > org.apache.struts:struts2-velocity-tools-view-jakarta:jar:7.0.0-M3 > > [ERROR] Failed to execute goal on project [36mstruts2-core[m: > [1;31mCould not resolve dependencies for project > org.apache.struts:struts2-core:jar:7.0.0-M3: The following artifacts > could not be resolved: > org.apache.struts:struts2-freemarker-jakarta:jar:7.0.0-M3 (present, but > unavailable): org.apache.struts:struts2-freemarker-jakarta:jar:7.0.0-M3 > was not found in https://repo.maven.apache.org/maven2 during a previous > attempt. This failure was cached in the local repository and resolution > is not reattempted until the update interval of central has elapsed or > updates are forced[m-> [1m[Help 1][m > > Caused by: org.apache.maven.lifecycle.LifecycleExecutionException: > Failed to execute goal on project [36mstruts2-core[m: [1;31mCould not > resolve dependencies for project > org.apache.struts:struts2-core:jar:7.0.0-M3: The following artifacts > could not be resolved: > org.apache.struts:struts2-freemarker-jakarta:jar:7.0.0-M3 (present, but > unavailable): org.apache.struts:struts2-freemarker-jakarta:jar:7.0.0-M3 > was not found in https://repo.maven.apache.org/maven2 during a previous > attempt. This failure was cached in the local repository and resolution > is not reattempted until the update interval of central has elapsed or > updates are forced > > I have deleted my ~.m2 and it makes no difference. > > > On 24/02/2024 08:46, Lukasz Lenart wrote: > > Hello, > > > > This is a third milestone of Struts 7.x series, which is based on > > JakartaEE 6. Please take the time and test the bits - any help is > > appreciated. Please report any problems you will spot. > > > > Here are the changes from the previous version: > > https://github.com/apache/struts/releases/tag/STRUTS_7_0_0_M3 > > > > Staging Maven repo > > https://repository.apache.org/content/groups/staging/ > > > > * please read our guideline how to setup your Maven build to include > > the Staging repository > > https://struts.apache.org/builds.html#test-builds > > > > Standalone artifacts > > https://dist.apache.org/repos/dist/dev/struts/7.0.0-M3/ > > > > Release notes > > https://cwiki.apache.org/confluence/display/WW/Version+Notes+7.0.0-M3 > > > > > > Have fun! > > Łukasz > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail:dev-unsubscr...@struts.apache.org > > For additional commands, e-mail:dev-h...@struts.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
