-
Notifications
You must be signed in to change notification settings - Fork 87
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
The version is now jscep-2.5.8
?
#364
Comments
No, not intended. I will ship a replacement.
…On Wed, 12 Feb 2025 at 09:58, Petar Petrov ***@***.***> wrote:
Hi,
The latest release on Maven has its version noted as jscep-2.5.8 whereas
it was 2.5.7 without the jscep- prefix before.
<dependency>
<groupId>com.google.code.jscep</groupId>
<artifactId>jscep</artifactId>
<version>jscep-2.5.8</version>
</dependency>
<dependency>
<groupId>com.google.code.jscep</groupId>
<artifactId>jscep</artifactId>
<version>2.5.7</version>
</dependency>
Was this intended? The reason I ask is because I have some tools that
automatically detect new dependency versions and 2.5.8 is not being
detected probably due to the prefix.
Thanks
—
Reply to this email directly, view it on GitHub
<#364>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAE5UO5G6YNZP7H4AVD23WT2PMLL7AVCNFSM6AAAAABW7FSFBGVHI2DSMVQWIX3LMV43ASLTON2WKOZSHA2DONZTGIYDOMQ>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
[image: petarov]*petarov* created an issue (seize-the-dave/jscep#364)
<#364>
Hi,
The latest release on Maven has its version noted as jscep-2.5.8 whereas
it was 2.5.7 without the jscep- prefix before.
<dependency>
<groupId>com.google.code.jscep</groupId>
<artifactId>jscep</artifactId>
<version>jscep-2.5.8</version>
</dependency>
<dependency>
<groupId>com.google.code.jscep</groupId>
<artifactId>jscep</artifactId>
<version>2.5.7</version>
</dependency>
Was this intended? The reason I ask is because I have some tools that
automatically detect new dependency versions and 2.5.8 is not being
detected probably due to the prefix.
Thanks
—
Reply to this email directly, view it on GitHub
<#364>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAE5UO5G6YNZP7H4AVD23WT2PMLL7AVCNFSM6AAAAABW7FSFBGVHI2DSMVQWIX3LMV43ASLTON2WKOZSHA2DONZTGIYDOMQ>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Published. Should be available shortly. |
@seize-the-dave Sorry to bug you again, but I feel like something still isn't quite right. I'm using Gradle with -------- 3.0.0
Cached resource https://repo.maven.apache.org/maven2/com/google/code/jscep/jscep/3.0.0/jscep-3.0.0.pom is up-to-date (lastModified: Fri Feb 14 06:34:32 CET 2025).
* What went wrong:
Execution failed for task ':project-name:compileKotlin'.
> Could not resolve all files for configuration ':project-name:compileClasspath'.
> Could not resolve com.google.code.jscep:jscep:3.0.0.
Required by:
project :project-name
> Could not resolve com.google.code.jscep:jscep:3.0.0.
> inconsistent module metadata found. Descriptor: com.google.code.jscep:jscep:2.5.7-SNAPSHOT Errors: bad version: expected='3.0.0' found='2.5.7-SNAPSHOT'
> Could not resolve com.google.code.jscep:jscep:3.0.0.
> inconsistent module metadata found. Descriptor: com.google.code.jscep:jscep:2.5.7-SNAPSHOT Errors: bad version: expected='3.0.0' found='2.5.7-SNAPSHOT'
-------- 2.8.0
Resource missing. [HTTP GET: https://repo.maven.apache.org/maven2/com/google/code/jscep/jscep/2.8.0/jscep-2.8.0.pom]
* What went wrong:
Execution failed for task ':project-name:compileKotlin'.
> Could not resolve all files for configuration ':project-name:compileClasspath'.
> Could not find com.google.code.jscep:jscep:2.8.0.
Searched in the following locations:
- https://interal.nexus/nexus/content/repositories/central/com/google/code/jscep/jscep/2.8.0/jscep-2.8.0.pom
- https://repo.maven.apache.org/maven2/com/google/code/jscep/jscep/2.8.0/jscep-2.8.0.pom
Required by:
project :project-name Any ideas? |
@petarov can you try 3.0.1 please? |
@seize-the-dave Yeah, this one seems to work. It got resolved. Thank you. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
The latest release on Maven has its version noted as
jscep-2.5.8
whereas it was2.5.7
without thejscep-
prefix before.Was this intended? The reason I ask is because I have some tools that automatically detect new dependency versions and
2.5.8
is not being detected probably due to the prefix.Thanks
The text was updated successfully, but these errors were encountered: