The 3.7.5 and 3.8 artifacts are now again searchable:
http://search.maven.org/#search|gav|1|g%3A%22org.jbehave%22%20AND%20a%3A%22jbehave%22
On 17/04/2013 23:58, Jorge Pombar wrote:
Thx a bunch Mauro, the dependendyManagement works like a charm. Adding
that section of my POM here in case it helps someone
<properties>
<jbehave.core.version>3.8</jbehave.core.version>
</properties>
<dependencyManagement>
<dependencies>
<dependency>
<groupId>org.jbehave</groupId>
<artifactId>_jbehave_-core</artifactId>
<version>3.8</version>
</dependency>
</dependencies>
</dependencyManagement>
Thanks,
Enrique
*From:*Mauro Talevi [mailto:[email protected]]
*Sent:* Wednesday, April 17, 2013 1:52 PM
*To:* [email protected]
*Subject:* Re: [jbehave-user] When will jbehave-core 3.8.0 be on Maven
Central
Hi,
these are indeed more Maven questions. The short answer is no, you
don't need to wait for a new web release.
If you want to use the latest version of core with web, simple declare
it in the <dependencyManagement/> section of your pom.xml. This will
override the transitive dependency from web pom.xml.
Alternatively, you can explicitly exclude the transitive dependency on
jbehave-core from the jbehave-web artifacts and re-add explicitly with
the desired version. The <dependencyManagement /> solution is more
elegant, but less known and less used.
As for sources in the your local repo, these are not downloaded by
default by Maven CLI. Usually, they are downloaded by the IDE, e.g.
Eclipse, either on demand or eagerly depending on the the
configuration of the relevant plugin. If you're using m2e, check the
preferences.
Cheers
On 17/04/2013 22:39, Jorge Pombar wrote:
Thanks for the quick reply Mauro. This might be more of a Maven
question but I think it might be pertinent to other users
I found out why maven wasn't pulling the 3.8 jar from the repo. It
is because our project is a jBehave-web project.
The latest version of jBehave-web is 3.5.5 and that depends on
jBehave 3.7.4. Maven resolved this by download and using the core
3.7.4 jar and ignoring my setting on my POM of jBehave-core
version 3.8. I don't think this can be resolved (since the users
don't manage jBehave web's pom) until there is a new Web release
that depends on core 3.8. Am I correct in this assumption?
One last maven question. On my local repo all the jbehave-core
version 3.6 and below have the core jar AND the sources.jar, 3.7
and above only have the code jar and not the sources. I do see the
sources.jar when I navigate to the maven repo on the browser. Do
you know why maven stopped downloading them?
Thanks,
Enrique
*From:*Mauro Talevi [mailto:[email protected]]
*Sent:* Wednesday, April 17, 2013 11:24 AM
*To:* [email protected] <mailto:[email protected]>
*Subject:* Re: [jbehave-user] When will jbehave-core 3.8.0 be on
Maven Central
Hi Jorge,
JBehave 3.7.5 and 3.8 are synched with Central. E.g. :
http://repo2.maven.org/maven2/org/jbehave/jbehave/3.8/
But for some reason they don't appear in http://search.maven.org/
I'll try to get to the reason, but for the time being, you can
simply pull it from Central as you would normally.
Cheers
PS: Thanks for your kind words - always appreciated :-)
On 17/04/2013 19:22, Jorge Pombar wrote:
Hi guys,
Thanks as usual for the great project you guys run. We are
currently stuck at version jbehave-core 3.6.8 (and web 3.5.4)
because of the metaFilters bug (JBEHAVE-868
<https://jira.codehaus.org/browse/JBEHAVE-868>). I took the
latest 3.8 SNAPSHOT and confirmed that this issue is fixed.
The problem is that on Maven Central I only see up to version
3.7.4. Do you know when will you push 3.8 to Maven Central?
Thanks,
Enrique
