Skip to content

org.springframework.roo:org.springframework.roo.annotations:pom:1.2.3.RELEASE was not found #2347

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
RouxAntoine opened this issue Nov 3, 2021 · 4 comments
Labels
status: duplicate A duplicate of another issue status: invalid An issue that we don't feel is valid

Comments

@RouxAntoine
Copy link

RouxAntoine commented Nov 3, 2021

Hello everybody,

I have a relatively similar error to #2285

I add spring-boot-starter-data-jpa version 2.5.5 to the pom.xml project :

like this (some exclusion to avoid dependency conflict)

		<dependency>
			<groupId>org.springframework.boot</groupId>
			<artifactId>spring-boot-starter-data-jpa</artifactId>
			<exclusions>
				<exclusion>
					<groupId>com.google.code.findbugs</groupId>
					<artifactId>annotations</artifactId>
				</exclusion>
				<exclusion>
					<groupId>com.google.code.findbugs</groupId>
					<artifactId>jsr305</artifactId>
				</exclusion>
				<exclusion>
					<groupId>org.javassist</groupId>
					<artifactId>javassist</artifactId>
				</exclusion>
				<exclusion>
					<groupId>com.google.guava</groupId>
					<artifactId>guava</artifactId>
				</exclusion>
			</exclusions>
		</dependency>

with maven 3.6.3 : mvn clean verify -DskipTest=true give a build success

[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------

with maven 3.8.2 : mvn clean vertify -DskipTest=true give error

org.springframework.roo:org.springframework.roo.annotations:pom:1.2.3.RELEASE was not found in https://repo.spring.io/milestone during a previous attempt. This failure was cached in the local repository and resolution is not reattempted until the update interval of spring-milestones has elapsed or updates are forced

Tried workaround :

  • fixed version 2.0.0-RELEASE
			<dependency>
				<groupId>org.springframework.roo</groupId>
				<artifactId>org.springframework.roo.annotations</artifactId>
				<version>2.0.0.RELEASE</version>
			</dependency>

give following error

org.springframework.roo.wrapping:org.springframework.roo.wrapping.inflector:pom:0.7.0.010 was not found in https://repo.spring.io/milestone during a previous attempt. This failure was cached in the local repository and resolution is not reattempted until the update interval of spring-milestones has elapsed or updates are forced
  • with version 1.3.2-RELEASE
			<dependency>
				<groupId>org.springframework.roo</groupId>
				<artifactId>org.springframework.roo.annotations</artifactId>
				<version>1.3.2.RELEASE</version>
			</dependency>

build success again.

  • try fixinig querydsl version failed too
			<dependency>
				<groupId>com.querydsl</groupId>
				<artifactId>querydsl-jpa</artifactId>
				<version>5.0.0</version>
				<optional>true</optional>
			</dependency>

Always requiring org.springframework.roo.annotations version 1.2.3.RELEASE

org.springframework.roo:org.springframework.roo.annotations:pom:1.2.3.RELEASE was not found in https://repo.spring.io/milestone during a previous attempt. This failure was cached in the local repository and resolution is not reattempted until the update interval of spring-milestones has elapsed or updates are forced

maybe due to querydsl/querydsl#3005
and fix with querydsl release 5.0.0 https://github.com/querydsl/querydsl/releases/tag/QUERYDSL_5_0_0
but it seem difficult to find which dependency really include org.springframework.roo:org.springframework.roo.annotations

cordially

@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged label Nov 3, 2021
@RouxAntoine
Copy link
Author

RouxAntoine commented Nov 3, 2021

Spring querydsl always use legacy version of org.springframework.roo.annotations here

https://github.com/querydsl/querydsl/blob/26f3c89a8a007a9135eb57f095b07e6fc24c516d/querydsl-apt/pom.xml#L58

so overloading repositories into our project cause missing repo :

adding this solve issue

  <repositories>
    <!--for org.springframework.roo:org.springframework.roo.annotations -->
    <repository>
      <id>spring roo repository</id>
      <url>https://spring-roo-repository.springsource.org/release</url>
    </repository>
  </repositories>

or exclude org.springframework.roo from spring-data-jpa :

		<dependency>
			<groupId>org.springframework.boot</groupId>
			<artifactId>spring-boot-starter-data-jpa</artifactId>
			<exclusions>
				<exclusion>
					<groupId>org.springframework.roo</groupId>
					<artifactId>org.springframework.roo.annotations</artifactId>
				</exclusion>
			</exclusions>
		</dependency>

@schauder
Copy link
Contributor

schauder commented Nov 3, 2021

This is essentially the same as #2285 and just as that it is a problem of Querydsl.
Thanks for posting the work arounds.

@schauder schauder closed this as completed Nov 3, 2021
@schauder schauder added status: duplicate A duplicate of another issue status: invalid An issue that we don't feel is valid and removed status: waiting-for-triage An issue we've not yet triaged labels Nov 3, 2021
@RouxAntoine
Copy link
Author

RouxAntoine commented Nov 3, 2021

Thanks for fast answering, Any idea why it's working with maven 3.6.3 ?

@schauder
Copy link
Contributor

schauder commented Nov 3, 2021

Just a guess, but maybe maven changed the order in which it applies dependencies and repository configurations. You could generate the effective pom for both variants and diff them to get an idea what is going on. Also, mvn dependency:tree will tell you where a dependency is coming from.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: duplicate A duplicate of another issue status: invalid An issue that we don't feel is valid
Projects
None yet
Development

No branches or pull requests

3 participants