Details
-
Type: Task
-
Status: Resolved
-
Priority: Minor
-
Resolution: Won't Fix
-
Affects Version/s: 3.1.2
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
-
Number of attachments :
Description
All the JBehave 3.1.2 artifacts look to be present and correct in the Maven Central repository with the exception of jbehave-site-resources which is missing (see http://repo2.maven.org/maven2/org/jbehave/site/jbehave-site-resources/).
I tend to have a single "jbehave.version" property in my POMs - I've now updated it 3.1.2 but my build now breaks because of a reference to the jbehave-site-resources artifact in my maven-dependency-plugin definition. It's a minor annoyance which can easily be worked around of course but uploading it would be neater.
I'd happily have a go myself but I believe I would need to have my public PGP key assigned the appropriate trusts before I could do so (which seems fair enough!).
Activity
Mauro Talevi
made changes -
Field | Original Value | New Value |
---|---|---|
Status | Open [ 1 ] | Resolved [ 5 ] |
Resolution | Won't Fix [ 2 ] |
There is no such version of site resources, the latest being 3.1.1.
Site, core and web releases have independent versioning, and you need to allow for different version variables in your scripts.