5.0.0 of fugue-parent not in MVN central
https://mvnrepository.com/artifact/io.atlassian.fugue/fugue-parent does not contain 5.0.0
Trying to use fugue 5.0.0, errors in not able to find fugue-parent of 5.0.0
see https://bitbucket.org/atlassian/fugue/issues/67/462-of-fugue-parent-not-in-mvn-central
Comments (14)
-
-
You can freely update the version in this title to 6.x as well. I don’t know who’s doing the releng for fugue but it makes no sense that you’re publishing an artifact without publishing the parent.
Publishing fugue 6.0.1 and 6.1.0 while publishing ONLY fugue-parent 6.0.0 is chef’s kiss 🧑🍳 😘 Just sink fugue-parent 5.0.0 .. 6.0.1 and 6.1.0 between your internal repo and central!
-
@Tom Rijnbeek can you perhaps take the lead on this?
-
fugue-parent
was never a package intended to be published to the Maven repository and shouldn’t be used. You should refer to the projects individually, most likelyfugue
.6.0.0
was a faulty release, which is why it exists in thefugue-parent
repository and not elsewhere. -
- changed status to wontfix
-
reporter Hi Tom,
the problem is, thatio.atlassian.fugue:fugue
references fugue-parent and this blocks the usage. -
reporter Example gradle build file
plugins { java id("org.springframework.boot") version "3.3.3" id("io.spring.dependency-management") version "1.1.6" } group = "com.example" version = "0.0.1-SNAPSHOT" java { toolchain { languageVersion = JavaLanguageVersion.of(21) } } repositories { mavenCentral() } dependencies { implementation("io.atlassian.fugue:fugue:6.1.0") // implementation("io.atlassian.fugue:fugue:4.7.2") implementation("org.springframework.boot:spring-boot-starter") testImplementation("org.springframework.boot:spring-boot-starter-test") testRuntimeOnly("org.junit.platform:junit-platform-launcher") } tasks.withType<Test> { useJUnitPlatform() }
-
Hi @Tom Rijnbeek ,
As Achim correctly points out, you’ve implicitly publishing parent as it’s part of the artifact pom, this in effect prohibits using the library directly for organisations that don’t have Atlassian in their allowed repository list (for orgs that use proxies).
-
@Tom Rijnbeek. There’s no point in publishing the library to Maven Central then. Come on, this is not what we expect of Atlassian.
-
If this is not going to be fixed, then can you update the Readme, as right now it implies that simply adding:
implementation("io.atlassian.fugue:fugue:6.1.0")
will work.
-
Apologies for the late response, I’ve been OOO lately.
I’ve mirrored this issue in our internal backlog. The team’s been busy recently with unblocking some critical launches, but we’ll investigate to see what the right settings are for these Maven artifacts. We’re reviewing some of the publishing processes internally, so this may just have been caught in the middle of that.
-
- changed status to open
-
Issue
#75was marked as a duplicate of this issue. -
As a paying Atlassian customer I and an open source contributor to a maven plugin that uses your Java Jira REST API client I appreciate it.
- Log in to comment
Dependabot is suggesting we move to 5.0.1 and we have this problem for that release too.
Is anyone going to fix it?