-
-
2. Re: 6.1.0 Beta maven repo version ??
suikast42 May 6, 2013 6:12 AM (in response to jaikiran)Thanks for fast response,
what about the source code? I see only the binaries on http://maven.repository.redhat.com/techpreview/eap6/.
And should I change my project versions as shown below ?
<version-infinispan>5.2.5.Final-redhat-1</version-infinispan>
<version-hornetq>2.3.0.CR2-redhat-1</version-hornetq>
<version-hibernate>4.2.0.Final-redhat-1</version-hibernate>
<version-hibernate-validator>4.3.1.Final-redhat-1</version-hibernate-validator>
<version-hibernate-commons-annotations>4.0.1.Final-redhat-2</version-hibernate-commons-annotations>
<version-hibernate-jpa>1.0.1.Final-redhat-2</version-hibernate-jpa>
-
3. Re: 6.1.0 Beta maven repo version ??
jaikiran May 6, 2013 6:20 AM (in response to suikast42)Sueleyman Vurucu wrote:
Thanks for fast response,
what about the source code? I see only the binaries on http://maven.repository.redhat.com/techpreview/eap6/.
Which sources do you mean? The maven jar sources are there within that Maven repo. For example http://maven.repository.redhat.com/techpreview/eap6/6.1.0.Beta1/maven-repository/org/jboss/jboss-ejb-client/1.0.17.Final-redhat-1/
If you are talking about EAP source code as a whole, they have always been available here ftp://ftp.redhat.com/redhat/jbeap/
-
4. Re: 6.1.0 Beta maven repo version ??
jaikiran May 6, 2013 6:21 AM (in response to suikast42)Sueleyman Vurucu wrote:
And should I change my project versions as shown below ?
<version-infinispan>5.2.5.Final-redhat-1</version-infinispan>
<version-hornetq>2.3.0.CR2-redhat-1</version-hornetq>
<version-hibernate>4.2.0.Final-redhat-1</version-hibernate>
<version-hibernate-validator>4.3.1.Final-redhat-1</version-hibernate-validator>
<version-hibernate-commons-annotations>4.0.1.Final-redhat-2</version-hibernate-commons-annotations>
<version-hibernate-jpa>1.0.1.Final-redhat-2</version-hibernate-jpa>
How do these versions get used in your project?
-
5. Re: 6.1.0 Beta maven repo version ??
suikast42 May 6, 2013 6:37 AM (in response to jaikiran)jaikiran pai schrieb:
Which sources do you mean? The maven jar sources are there within that Maven repo. For example http://maven.repository.redhat.com/techpreview/eap6/6.1.0.Beta1/maven-repository/org/jboss/jboss-ejb-client/1.0.17.Final-redhat-1/
If you are talking about EAP source code as a whole, they have always been available here ftp://ftp.redhat.com/redhat/jbeap/
Ok that's exactly what I mean,
-
6. Re: 6.1.0 Beta maven repo version ??
suikast42 May 6, 2013 6:38 AM (in response to jaikiran)jaikiran pai schrieb:
How do these versions get used in your project?
For example
<dependency>
<groupId>org.hibernate.javax.persistence</groupId>
<artifactId>hibernate-jpa-2.0-api</artifactId>
<version>${version-hibernate-jpa}</version>
<scope>provided</scope>
</dependency>
<dependency>
<groupId>org.hibernate</groupId>
<artifactId>hibernate-validator</artifactId>
<version>${version-hibernate-validator}</version>
<scope>provided</scope>
</dependency>
<dependency>
<groupId>org.hibernate.common</groupId>
<artifactId>hibernate-commons-annotations</artifactId>
<version>${version-hibernate-commons-annotations}</version>
<scope>provided</scope>
</dependency>
-
7. Re: 6.1.0 Beta maven repo version ??
jaikiran May 6, 2013 6:45 AM (in response to suikast42)So you don't really package those in the application (provided scope), which really means that unless you want to use a new compile time kind of API in your application, you don't really have to upgrade the versions.
-
8. Re: 6.1.0 Beta maven repo version ??
suikast42 May 6, 2013 7:02 AM (in response to jaikiran)jaikiran pai schrieb:
you don't really have to upgrade the versions.
In some cases ( for clients for example) I need to change the provided scope in compile scope. For this reason I want to be sure use the same jars as provided with the uses JBoss version. So I can use the version above right ??
If I use http://maven.repository.redhat.com/techpreview/eap6/. as maven repo then maven find nothing. But if I use http://maven.repository.redhat.com/techpreview/eap6/6.1.0.Beta1/maven-repository/ then maven will find the artifacts.
-
9. Re: 6.1.0 Beta maven repo version ??
suikast42 May 6, 2013 7:03 AM (in response to suikast42)I forgot to say that I use a own nexus repo which links to http://maven.repository.redhat.com/techpreview/eap6/6.1.0.Beta1/maven-repository/ as a proxy
-
10. Re: 6.1.0 Beta maven repo version ??
suikast42 May 6, 2013 7:20 AM (in response to jaikiran)There is a problem with transitive dependency of hibernate-core
Hibernate core have a transtive dependecy to dom4j-1.6.1-redhat-4 but only dom4j-1.6.1-redhat-5 is located in http://maven.repository.redhat.com/techpreview/eap6/6.1.0.Beta1/maven-repository/.
-
11. Re: 6.1.0 Beta maven repo version ??
jameslivingston May 12, 2013 9:29 PM (in response to suikast42)Sueleyman Vurucu wrote:
There is a problem with transitive dependency of hibernate-core
Hibernate core have a transtive dependecy to dom4j-1.6.1-redhat-4 but only dom4j-1.6.1-redhat-5 is located in http://maven.repository.redhat.com/techpreview/eap6/6.1.0.Beta1/maven-repository/.
That's a known issue which is currently being discussed. Not all the components in the Beta were changed from the alpha, and Hibernate is one of them. Since the beta is still using the build of it from the alpha, it uses the internal BOM from the alpha and ends up pointing to the older version of Dom4J.
The older version won't end up being used in your build, but maven still wants it. I don't think there is a solution yet other than having the alpha repo available too, sorry.
-
12. Re: 6.1.0 Beta maven repo version ??
suikast42 May 13, 2013 3:10 AM (in response to jameslivingston)Thanks for reply james. I'll wating for 8.0.0.Final
-
13. Re: 6.1.0 Beta maven repo version ??
svollmer May 23, 2013 9:53 AM (in response to suikast42)1 of 1 people found this helpfulHi,
I just noticed that the problem still exists in the Maven repository for EAP 6.1.0.Final.
When I add a dependency to org.hibernate:hibernate-entitymanager:4.2.0.Final-redhat-1, then it still has dom4j-1.6.1-redhat-4 as a transitive dependency and the build fails.