Steve Ebersole wrote:
> Hibernate will never deploy directly to central. At best it was always
> going to just be synched across to central. So for Hibernate the JBoss
> repo is in fact the authoritative source. That's in direct difference
> to the other artifacts with which you deal it sounds l
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
stuf
e as ones which
exist in central but which may or may not be the same, that I do not and
will not trust it.
And even if that were not the case, it is still convenient to have
everything available in central.
Max.
> Max Bowsher wrote:
>> With Hibernate Core 3.3.2 just released, it seems li
With Hibernate Core 3.3.2 just released, it seems like a relevant time
to ask:
What happened to the ongoing struggle to get jboss artifacts synced to
maven central?
Could we please have an update of what the current status is?
Thanks,
Max.
signature.asc
Description: OpenPGP digital signature
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
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.
Chris Bredesen wrote:
> All,
>
> I just brought down a fresh copy of Branch_3_3, compiled and then ran
> mvn eclipse:eclipse. The Eclipse projects were created mostly fine and
> they all imported into Ganymede.
>
> However, there's an issue with each module's dependency on
> hibernate-core and h
Max Rydahl Andersen wrote:
> On Mon, 18 Aug 2008 12:36:23 +0200, Max Bowsher wrote:
>
>> Steve Ebersole wrote:
>>> http://in.relation.to/Bloggers/HibernateCore330GoesGA
>>
>> Very nice!
>>
>> Will new arrangements for syncing artifacts to Maven2 cent
Steve Ebersole wrote:
> http://in.relation.to/Bloggers/HibernateCore330GoesGA
Very nice!
Will new arrangements for syncing artifacts to Maven2 central now be
going active, or it is still up to interested third parties to file
requests for a manual copy of specific artifact versions in codehaus JI
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 m
> 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 f
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 hibernate-commons-a
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
>
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, it
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, it is
not worth my time, imo, to have to go through this "upload" rigamarole
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
org.hibernate:ejb3-persistence
Looking at MAVENUPLOAD JIRA, it looks like for Hibernate 3.2.x, upload
bundles are produced by anyone who has the time and decides to do it -
is that correct?
If the reason why 3.2.6.ga hasn't been uploaded to central yet is
because no-one's got around to it yet, I'll volunteer.
Have previou
17 matches
Mail list logo
