Emmanuel Bernard wrote:
Yes but central is full of broken JBoss stuff at un normalized artifact
ids. So you're screwed either way.
The only viable solution is to use sonar or artifactory and define the
rules you wish.
Personally I'm only using Hibernate itself, and no additional JBoss
stuff,
Adam Warski wrote:
Hello,
Though I'd have to do some adaptation changes. As I was originally
targeting Envers to support JPA mappings, I assumed that it will be
working in an enviroment with Hibernate Annotations/EntityManager. So
I used ReflectionManager to read the @Versioned annotations.
Chris Bredesen wrote:
Max Bowsher wrote:
Chris Bredesen wrote:
and it creates them with
the assumption that the project names are the same as the artifact ID.
This is in fact not the case.
It should be the case, and is for me. What is it for you, and have you
any idea why it's different
Sanne Grinovero wrote:
I knew about the requirement to change the UID, but really hadn't a
clue about the default behaviour:
I thought it was unspecified and I really dislike that word.
The default behaviour is semi-specified - specifically, it's based on a
SHA1 hash of:
class name and
Emmanuel Bernard wrote:
The Hibernate team is pleased to announce the synchronized release of:
- Hibernate Annotations 3.4.0 CR1
- Hibernate EntityManager 3.4.0 CR1
- Hibernate Validator 3.1.0 CR1
- Hibernate Commons Annotations 3.1.0 CR1
As there is a mislabelled
On May 29, 2008, at 07:02, Max Bowsher wrote:
As there is a mislabelled hibernate-commons-annotations 3.3.0.ga in the
wild (Maven2 central and possibly other places), perhaps it might be
worth arbitrarily bumping that project's version number up to 3.4.0 for
new releases, in the interests
Max Rydahl Andersen wrote:
Yes, I also forsee the pissing contest unfortunately.
Part of the problem is that there are the same artifacts in both
repositories with differing poms. Which pom is correct?
I vote for the pom maintained by the dev team behind the project - anything
else is an
Emmanuel Bernard wrote:
On Mar 17, 2008, at 12:14, Max Bowsher wrote:
Steve Ebersole wrote:
JBoss as a whole is working with the Maven team (Jason) about setting
up synching of all the projects we write to the JBoss repo
(http://repository.jboss.org/maven2/) automatically. Personally
Emmanuel Bernard wrote:
Check it out http://in.relation.to/8711.lace
What's the current situation with regards to getting this into the Maven
central repository at repo1.maven.org?
Also, what is the difference between
javax.persistence:persistence-api:1.0 and
