Hibernate * releases for JBoss AS 5

I have just released the following:
  - Hibernate Annotations 3.3.1.GA
  - Hibernate EntityManager 3.3.2.GA
  - ejb3-persistence 1.0.1.GA

In addition to that, additional existing dependencies are:
  - hibernate 3.2.6.GA
  - Hibernate Commons Annotations 3.0.0.GA

All of them in the groupId org.hibernate

I did make an attempt to release correct Maven 2 poms, I
would  
appreciate a feedback on that.

I've seen some inconsistencies in the release used in ejb3
trunk (the  
old ones are used).

Emmanuel
_______________________________________________
jboss-development mailing list
jboss-developmentlists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-develop
ment

Emmanuel Bernard wrote:
 > I've seen some inconsistencies in the release used in
ejb3 trunk (the
 > old ones are used).

If you're referring to JBossAS trunk/ejb3, we've moved and
are now out 
of jbossas/projects/ejb3/build/trunk/build/pom.xml.

...which is probably also out-of-date. ;)

S,
ALR
_______________________________________________
jboss-development mailing list
jboss-developmentlists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-develop
ment

Emmanuel Bernard wrote:
> On  Mar 15, 2008, at 08:40, Andrew Lee Rubinger wrote:
>> Emmanuel Bernard wrote:
>> > I've seen some inconsistencies in the release
used in ejb3 trunk (the
>> > old ones are used).
> I was refering to the new place 

We have a discussion currently taking place to define how
we'll 
establish a proper build matrix contract between AS
Components and their 
consumers (ie. EJB3):

http://www.jboss.com/index.html?module=b
b&op=viewtopic&p=4136329

This, when implemented, will ensure everything is of proper
version.

S,
ALR
_______________________________________________
jboss-development mailing list
jboss-developmentlists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-develop
ment

Emmanuel,

On 14 Mar 2008, at 23:55, Emmanuel Bernard wrote:

> I did make an attempt to release correct Maven 2 poms,
I would  
> appreciate a feedback on that.

On a related note, it would be great if you can upload
-sources.jar  
when you do releases (along with associated -sources.jar.md5
and - 
sources.jar.sha1) as maven clients will download these and
attach  
them as source jars e.g. when building the IDE classpath.

--
Pete Muir
http://www.seamframework
.org
http://in.relatio
n.to/Bloggers/Pete




_______________________________________________
jboss-development mailing list
jboss-developmentlists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-develop
ment

If you can find an ant task that does that, I will.
But I am not using maven for the release process (ant +
ivy). It took  
me a day total to release two projects last Friday (granted
I had to  
understand the legacy dependency mess we have in our repo
and in the  
maven central repo).
It's a manual process for me today.

On  Mar 18, 2008, at 06:24, Pete Muir wrote:

> Emmanuel,
>
> On 14 Mar 2008, at 23:55, Emmanuel Bernard wrote:
>
>> I did make an attempt to release correct Maven 2
poms, I would  
>> appreciate a feedback on that.
>
> On a related note, it would be great if you can upload
-sources.jar  
> when you do releases (along with associated
-sources.jar.md5 and - 
> sources.jar.sha1) as maven clients will download these
and attach  
> them as source jars e.g. when building the IDE
classpath.
>
> --
> Pete Muir
> http://www.seamframework
.org
> http://in.relatio
n.to/Bloggers/Pete
>
>
>
>

_______________________________________________
jboss-development mailing list
jboss-developmentlists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-develop
ment

This is what we use in Seam* (I assume you are using Maven
Ant Tasks  
to generate your deployment):

<jar jarfile="${src.jar}"
basedir="${src.dir}">
    <include name="**/*.java" />
    <exclude name="**/test/*.java" />
    <patternset refid="meta.files" />
</jar>

<artifact:remoteRepository
id="offline.repository.jboss.org"  
url="file:///${offline.repository.jboss.org}"
/>

<artifact:deploy file="${bin.jar}">
    <pom file="${pom.file} />
    <remoteRepository
refId="offine.repository.jboss.org" />
    <attach file="${src.jar}"
classifier="sources" />
</artifact:deploy>

You can then commit the results to svn

* Well, actually, it's all wrapped up in macrodef's, but
this is them  
expanded out

On 18 Mar 2008, at 14:52, Emmanuel Bernard wrote:

> If you can find an ant task that does that, I will.
> But I am not using maven for the release process (ant +
ivy). It  
> took me a day total to release two projects last Friday
(granted I  
> had to understand the legacy dependency mess we have in
our repo  
> and in the maven central repo).
> It's a manual process for me today.
>
> On  Mar 18, 2008, at 06:24, Pete Muir wrote:
>
>> Emmanuel,
>>
>> On 14 Mar 2008, at 23:55, Emmanuel Bernard wrote:
>>
>>> I did make an attempt to release correct Maven
2 poms, I would  
>>> appreciate a feedback on that.
>>
>> On a related note, it would be great if you can
upload - 
>> sources.jar when you do releases (along with
associated - 
>> sources.jar.md5 and -sources.jar.sha1) as maven
clients will  
>> download these and attach them as source jars e.g.
when building  
>> the IDE classpath.
>>
>> --
>> Pete Muir
>> http://www.seamframework
.org
>> http://in.relatio
n.to/Bloggers/Pete
>>
>>
>>
>>
>

--
Pete Muir
http://www.seamframework
.org
http://in.relatio
n.to/Bloggers/Pete




_______________________________________________
jboss-development mailing list
jboss-developmentlists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-develop
ment

Thanks Pete, after jumping above a NPE in the ant task, I
managed to  
make it work. will use that in the future.

On  Mar 18, 2008, at 11:01, Pete Muir wrote:

> This is what we use in Seam* (I assume you are using
Maven Ant Tasks  
> to generate your deployment):
>
> <jar jarfile="${src.jar}"
basedir="${src.dir}">
>   <include name="**/*.java" />
>   <exclude name="**/test/*.java" />
>   <patternset refid="meta.files" />
> </jar>
>
> <artifact:remoteRepository
id="offline.repository.jboss.org"
url="file:///$ 
> {offline.repository.jboss.org}" />
>
> <artifact:deploy file="${bin.jar}">
>   <pom file="${pom.file} />
>   <remoteRepository
refId="offine.repository.jboss.org" />
>   <attach file="${src.jar}"
classifier="sources" />
> </artifact:deploy>
>
> You can then commit the results to svn
>
> * Well, actually, it's all wrapped up in macrodef's,
but this is  
> them expanded out
>
> On 18 Mar 2008, at 14:52, Emmanuel Bernard wrote:
>
>> If you can find an ant task that does that, I
will.
>> But I am not using maven for the release process
(ant + ivy). It  
>> took me a day total to release two projects last
Friday (granted I  
>> had to understand the legacy dependency mess we
have in our repo  
>> and in the maven central repo).
>> It's a manual process for me today.
>>
>> On  Mar 18, 2008, at 06:24, Pete Muir wrote:
>>
>>> Emmanuel,
>>>
>>> On 14 Mar 2008, at 23:55, Emmanuel Bernard
wrote:
>>>
>>>> I did make an attempt to release correct
Maven 2 poms, I would  
>>>> appreciate a feedback on that.
>>>
>>> On a related note, it would be great if you can
upload - 
>>> sources.jar when you do releases (along with
associated - 
>>> sources.jar.md5 and -sources.jar.sha1) as maven
clients will  
>>> download these and attach them as source jars
e.g. when building  
>>> the IDE classpath.
>>>
>>> --
>>> Pete Muir
>>> http://www.seamframework
.org
>>> http://in.relatio
n.to/Bloggers/Pete
>>>
>>>
>>>
>>>
>>
>
> --
> Pete Muir
> http://www.seamframework
.org
> http://in.relatio
n.to/Bloggers/Pete
>
>
>
>

_______________________________________________
jboss-development mailing list
jboss-developmentlists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-develop
ment