You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[bugfix] repo:install-and-deploy: use the resolved version for the classpath too
The previous commit deployed the explicitly-requested version but still drove
ClasspathHelper.updateClasspath() (and the install status/action reporting) from
installPackage()'s return value, which can be packages.latest() -- a higher
already-installed version. So repo:install-and-deploy(name, "<older>", url)
deployed the older version's XQuery resources while loading the newer version's
Java JARs onto the classpath, a silent version mismatch.
Resolve the deploy target once (resolveInstalledVersion) before the classpath
update and use it for BOTH the classpath update and the deploy, so they always
act on the same package version. Also treat an empty @Version (the DOM
getAttribute returns "" not null for a versionless descriptor) as "no specific
version requested", and drop a redundant Packages import already covered by the
package wildcard.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01ThoADnh6VvDt5w8kz7d2d3
0 commit comments