Would be great to see the jar in http://repository.jboss.org/maven2/org/hibernate/hibernate/3.3.2.GA/ ...

Where's the api document? I can't find it.

Try http://repository.jboss.org/maven2/org/hibernate/hibernate-core/3.3.2.GA (I don't think 'hibernate' exists as a maven artifact for hibernate 3.3)

Why is there a directory 'http://repository.jboss.org/maven2/org/hibernate/hibernate/3.3.2.GA/' then ?

Because Maven makes there be one. http://repository.jboss.org/maven2/org/hibernate/hibernate/3.3.2.GA/ I simply the aggregator project/module

We do not coordinate with sonatype for uploading to the central repo. We tried in the past and could not meet their requirements. So we upload to the JBoss repo, which is also a Maven repo. The Maven developers will even tell you that you should not be relying on direct repo access anyway, using a repository manager in any case (ala their Nexus server), so this is a non-issue

Why not to package them into one zip file as before?

1 compatibility matrix

please

'one zip' as in the distribution download I upload to sourceforge you mean?

Steve Ebersole wrote on Jun 24, 2009 16:50:
We do not coordinate with sonatype for uploading to the central repo. We tried in the past and could not meet their requirements. So we upload to the JBoss repo, which is also a Maven repo. The Maven developers will even tell you that you should not be relying on direct repo access anyway, using a repository manager in any case (ala their Nexus server), so this is a non-issue

Does this help: http://www.sonatype.com/people/2009/06/publishing-your-artifacts-to-the-central-maven-repository/

Where's the api document? I can't find it.

Look, for the love of all that is holy, please stop flaunting Sonatype conventions and publish a build I can just USE. Or, in the absence of managing to publish to the central repo, post clear instructions for how to modify my pom to work with your new build conventions.

I really find this build change both puzzling and aggravating. The most aggravating part is that the Hibernate project has changed Maven usage without providing clear instructions for how to fix your pom and actually use 3.3.2.

Instead, I have to trawl Google, wade through your poms, and peruse Maven documentation trying to figure out how the fsck to upgrade from Hibernate 3.2.6.GA to 3.3.2.GA.

EPIC FAIL.

Is anyone at Hibernate listening? Please sort your build problems.

irritated user wrote:

... post clear instructions for how to modify my pom to work with your new build conventions.

Looking at hibernate.org Maven Guide, you'll need to add at least*:

  <!-- add this to under your '<project>' element -->
  <repositories>
    <repository>
      <id>jboss</id>
      <url>http://repository.jboss.com/maven2</url>
      <releases>
        <enabled>true</enabled>
      </releases>
      <snapshots>
        <enabled>false</enabled>
      </snapshots>
    </repository>
  </repositories>

* = while the article recommends others (plugins for example) I've never had the need to add those. If you experience problems, do everything by the article.

springhill wrote on Jun 24, 2009 13:33:
Where's the api document? I can't find it.

Click HELP for text formatting instructions. Then edit this text and check the preview.

Has anyone ever able to obtain Hibernate Core 3.3.2.GA Javadocs from the the 3.3.2 distribution?

I'd like to have the Javadocs API offline.