I agree, that is essentially what I've done myself.
One thing:  the jboss-service.xml is "supposed" to be in a META-INF
subdirectory.
It didn't seem to mind that it was in the root, I mean it still worked.  I
went ahead and set the

maven.xdoclet.hibernatedoclet.jbossservice.0.destDir=${maven.build.dest}/MET
A-INF

just to be sure, it also seems to have worked.

What I was really getting at though is that in the WAR plugin it lets you
set the extension in the maven.final.name, or at least you have the option
of circumventing the

  <ant:property name="maven.war.final.name"
      value="${pom.artifactId}.war"/>
and then
    <ant:jar
         destfile="${maven.war.build.dir}/${maven.war.final.name}"

while in the jar plugin

The JAR plugin forces you to
    <ant:jar
      jarfile="${maven.build.dir}/${maven.final.name}.jar"


slightly different behavior.  I run into things like this in my code when I
compare things I've done early on in the project and come up with better
ways later on ... nothing is broken, it just shows me history of things.

----- Original Message ----- 
From: "Alwyn Schoeman" <[EMAIL PROTECTED]>
To: "Maven Users List" <[EMAIL PROTECTED]>
Sent: Wednesday, October 01, 2003 10:43 PM
Subject: Re: maven, xdoclet, hibernate


> I have looked into a SAR plugin and basically you would be duplicating so
much
> of the JAR plugin that it is basically not worth the effort if the only
value
> you'll be adding is a different extension.
>
> So I do no jar:jar kludgery but only,
>
>   <preGoal name="jar:install">
>       <echo>jar:install pregoal running...</echo>
>       <ant:property name="sardir__"
> value="${maven.repo.local}/${pom.artifactDirectory}/sars"/>
>       <ant:mkdir dir="${sardir__}"/>
>       <ant:copy
>          file="${maven.build.dir}/${maven.final.name}.jar"
>          tofile="${sardir__}/${maven.final.name}.sar"
>          overwrite="true"
>       />
>   </preGoal>
>
> along with:
>
>   <build>
>     <sourceDirectory>src/java</sourceDirectory>
>     <resources>
>     <resource>
>     <directory>${basedir}/src</directory>
>     <includes>
>     <include>**/*.xml</include>
>     </includes>
>     </resource>
>     </resources>
>   </build>
>
> As for rar you could probably do the same.
>
> On Thu, Oct 02, 2003 at 08:36:16AM +0800, [EMAIL PROTECTED] wrote:
> > "khote" <[EMAIL PROTECTED]> wrote on 02/10/2003 04:38:05 AM:
> > [snip]
> > > Is this just a legacy thing from maven early days, I mean the JAR
> > plugin
> > was
> > > written long before the WAR plugin, nobody ever got around to
> > sar-plugin?
> > Nope, noone has written a SAR or RAR plugin.
> > --
> > dIon Gillard, Multitask Consulting
> > Blog:      http://blogs.codehaus.org/people/dion/
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
>
>
>
> -- 
> Alwyn Schoeman
> SMART Money Inc.
>
> If you're a SMARTY and you're using the better DNS connections, you
> can access my homepage at http://nevyn.smarties.com.ph/Members/alwyn.
> The other unlucky ones: http://10.126.68.24/myplone
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to