ahahah, touché.
On 14 déc. 2009, at 18:39, Steve Ebersole wrote:
> Well we can also do what you suggest and you can be the one fielding bug
> reports about some other providers jar if you wish ;)
>
> On Mon, 2009-12-14 at 17:38 +0100, Emmanuel Bernard wrote:
>> If you guys like that. But you wil
Well we can also do what you suggest and you can be the one fielding bug
reports about some other providers jar if you wish ;)
On Mon, 2009-12-14 at 17:38 +0100, Emmanuel Bernard wrote:
> If you guys like that. But you will be the ones answering the questions:
> - why is Hibernate not standard
>
If you guys like that. But you will be the ones answering the questions:
- why is Hibernate not standard
- why do I need an hibernate specific jar to use JPA 2
:)
On 14 déc. 2009, at 16:02, Hardy Ferentschik wrote:
> I like the idea of having 'hibernate' in the actual jar name as well. When
>
I like the idea of having 'hibernate' in the actual jar name as well. When
you are
building a project the dependencies are clear. But when you just look at
an artifact
like for example a war file it helps a lot if the jar file names are a
little more descriptive.
We also have hibernate-core a
Shizzle, that explains it. I forgot to commit after releasing :(
Done now.
Same for jpamodelgen too btw. I cut a Beta-2 release in order to align
the jpa api jars
On Mon, 2009-12-14 at 11:29 -0300, Hardy Ferentschik wrote:
> In pom.xml is still uses file://${maven.repository.root} and looking
When the user simply has the jar file "in hand".
On Mon, 2009-12-14 at 15:30 +0100, Emmanuel Bernard wrote:
> Since jpa-api is not a standard name, people will search
> javax.persistence and they will see the group is prefix.
> When is the artifactID not next to the groupId? I don't remember where
Since jpa-api is not a standard name, people will search javax.persistence and
they will see the group is prefix.
When is the artifactID not next to the groupId? I don't remember where that
could happen in ivy or maven but I am no expert here.
On 14 déc. 2009, at 15:22, Steve Ebersole wrote:
>
In pom.xml is still uses file://${maven.repository.root} and looking at
the gradle build file
it also seems to use file based deployment
file://${jbossReleaseRepositoryRoot}
Webdav is used for the snapshot repository. My understanding was webdav
was not working yet for the
main repository du
I am thinking of users here. Since there will be multiple jpa api jars out
there I liked the idea of the jar name itself encoding the fact that this is
the one from hibernate. I think this is more user friendly. I hear what you
are saying though about the ability to bootstrap any/all provider
Synching from where? That project is set up for webdav deployment. Let me
check when I get to my computer...
-- Sent from my Palm Prē
st...@hibernate.org
http://hibernate.orgHardy Ferentschik wrote:
I think I found the answer to my question in another email:
"the syncing to repository.jboss
I think I found the answer to my question in another email:
"the syncing to repository.jboss.org is currently broken" :(
On Mon, 14 Dec 2009 10:54:15 -0300, Hardy Ferentschik
wrote:
> just tried to build core, but the following dependency seems to be
> missing
> :
>
> org.hibernate.javax.p
Hi
just tried to build core, but the following dependency seems to be missing
:
org.hibernate.javax.persistence:hibernate-jpa-2.0-api:jar:1.0.0-CR-1
Looking at the svn log for the jpa api project it seems that Steve already
went
through the release process for this dependency.
The question
javax.persistence is owned by "Sun" as spec lead.
And more concretely, they don't publish the spec jars to maven repos under an
open source license. So our lawyers asked us to use a clean code.
Emmanuel
On 14 déc. 2009, at 11:18, Sanne Grinovero wrote:
> out of curiosity, why not drop org.hibe
out of curiosity, why not drop org.hibernate?
javax.persistence:jpa-2.0-api:1.0.0-SNAPSHOT
are there more api vendors ?
Cheers,
Sanne
2009/12/14 Emmanuel Bernard :
> I would use
> org.hibernate.javax.persistence:jpa-2.0-api:1.0.0-SNAPSHOT
>
> Because while there is code written by us, it's not s
I would use
org.hibernate.javax.persistence:jpa-2.0-api:1.0.0-SNAPSHOT
Because while there is code written by us, it's not specific to Hibernate and
can bootstrap all providers on the market.
On 11 déc. 2009, at 22:24, Steve Ebersole wrote:
> Of course that should be
> org.hibernate.javax.persi
Of course that should be
org.hibernate.javax.persistence:hibernate-jpa-2.0-api:1.0.0-SNAPSHOT
;)
On Fri, 2009-12-11 at 14:59 -0600, Steve Ebersole wrote:
> I think there is a consensus we need to rename our JPA api jar. The
> main concern is that we should be capturing the spec version in the
>
I think there is a consensus we need to rename our JPA api jar. The
main concern is that we should be capturing the spec version in the
artifact name but that the versioning should be its own thing since
there is in fact Hibernate specific code in the classes that we will
have need to maintain and
17 matches
Mail list logo
