Skip to content
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

SEC-1895: Spring Security 3.1.0.RELEASE is not available on Spring EBR Maven repository #2122

Closed
spring-projects-issues opened this issue Jan 21, 2012 · 6 comments
Labels
in: build type: bug type: jira

Comments

@spring-projects-issues
Copy link

@spring-projects-issues spring-projects-issues commented Jan 21, 2012

Rick Herrick (Migrated from SEC-1895) said:

The latest version available on the Spring Maven repository is 3.0.4.RELEASE, which is 3 point releases behind even the 3.0.x branch (up to 3.0.7) and there are no 3.1.0.X releases available. You guys can, like, automate this as part of the release process, you know:

mvn deploy
@spring-projects-issues
Copy link
Author

@spring-projects-issues spring-projects-issues commented May 31, 2012

Andrew Finnell said:

It becomes very frustrating when 90% of the Spring components can be found in a maven repo, then the last one you need is not there.

@spring-projects-issues
Copy link
Author

@spring-projects-issues spring-projects-issues commented Jul 9, 2012

Greg Turnquist said:

It was added to the EBR in June.

@spring-projects-issues
Copy link
Author

@spring-projects-issues spring-projects-issues commented Jul 9, 2012

Rick Herrick said:

That's fine, but the longer term issue is the latency in getting new releases up there. I understand that more testing goes on for the EBR releases, but we've actually cut EBR out of our repo chain and just use Maven Central now because it takes way too long for security patches and bug fixes to make their way in.

@spring-projects-issues
Copy link
Author

@spring-projects-issues spring-projects-issues commented Jul 9, 2012

Greg Turnquist said:

The title of this ticket is "...not available on Spring EBR Maven repository". If this isn't about the EBR, but instead general publishing to maven central, then the ticket needs to be updated to reflect that. If indeed it is about the EBR, then there is little we can do to accelerate the process. The EBR process doesn't lend itself to automation, especially given it's end-of-life.

@spring-projects-issues
Copy link
Author

@spring-projects-issues spring-projects-issues commented Jul 9, 2012

Rick Herrick said:

Are you EOL'ing EBR? In which case, switching to Maven Central's the right thing to do anyway :)

@spring-projects-issues
Copy link
Author

@spring-projects-issues spring-projects-issues commented Jul 12, 2012

Rob Winch said:

Close as this was deployed in June per Greg's comment

@spring-projects-issues spring-projects-issues added in: build Closed type: bug type: jira labels Feb 5, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: build type: bug type: jira
Projects
None yet
Development

No branches or pull requests

1 participant