Unfortunately it is not obvious that now for staged builds/testing, the
repo needs to be added to the struts pom (for eclipse users).
Does the IDE you use compile OK without staged in the pom?
Generally I have a list of staged repos on as a default, so don't have
these issues.
On 15/12/2024 12:19, Lukasz Lenart wrote:
pt., 13 gru 2024 o 11:11 Greg Huber <gregh3...@gmail.com> napisał(a):
I am using the standard struts git repo.
Why is maven only looking for these two in
https://repo.maven.apache.org/maven2 and ignoring staging.
That's correct. You must explicitly specify if you want to use the
staging repository
There is the same error on other plugin projects eg struts2-velocity-plugin
Caused by: org.apache.maven.lifecycle.LifecycleExecutionException:
Failed to execute goal on project [36mstruts2-tiles-plugin [m:
[1;31mCould not resolve dependencies for project
org.apache.struts:struts2-tiles-plugin:jar:7.0.0
dependency:
org.apache.struts:struts2-velocity-tools-view-jakarta:jar:7.0.0 (compile?)
org.apache.struts:struts2-velocity-tools-view-jakarta:jar:7.0.0 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
This plugin wasn't officially released yet so the artifacts and
dependencies are only available in the staging repository.
Cheers
Ł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
