[jboss-dev] Hibernate * releases for JBoss AS 5

[Pete Muir]

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.relation.to/Bloggers/Pete
>>
>>
>>
>>
>

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