Skip to content

LDEV-6568 use https for Maven Central when resolving Lucee dependencies - #8

Merged
michaeloffner merged 1 commit into
lucee:mainfrom
GianTschingt:LDEV-6568-central-https
Oct 13, 2026
Merged

michaeloffner merged 1 commit into
lucee:mainfrom
GianTschingt:LDEV-6568-central-https

Conversation

@GianTschingt

Copy link
Copy Markdown
Contributor

Test runs on Lucee 7.1 (e.g. extension-smb run 38399150229) fail while resolving jakarta.servlet-api:6.0.0's parent org.eclipse.ee4j:project:1.0.7:

Downloading: org/eclipse/ee4j/project/1.0.7/project-1.0.7.pom from repository central at http://repo1.maven.org/maven2
CHECKSUM FAILED ... remote = '<html><head><title>301'
Cannot find parent: org.eclipse.ee4j:project

maven-ant-tasks 2.1.3 (build.xml, artifact:dependencies) has central built in as http://repo1.maven.org/maven2, and Central now answers http with a 301. Declaring a repository with id central in the POMs overrides that default with https. Applied to pom.xml, pom-javax.xml and pom-jakarta.xml.

Found via LDEV-6568 (extension S3 rollout); affects every repo that uses lucee/script-runner@main.

@michaeloffner
michaeloffner merged commit 5fa1d92 into lucee:main Oct 13, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants