I am fine with maintaining my own but I think there is benefit at large for maintaining it in svn.

I would like to get help for specific maven direction, and we could put to sleep the old sar.
Can you give me/setup a server main like with the mods I described?

Aron
Chris Custine wrote:
You could use another exclude in apacheds-main.xml to keep it from packaging the slf4jnlog4j jar file, but causing it to include the slf4jlog4j file will require a modification of the pom to add it as a dependency. If you are OK with maintaining these mods locally then that should be all you need. If you need the specific maven directions let me know.

Chris

On 4/25/07, *Aron Sogor* <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote:

    So the point is that I did not do that with the old sar.

    I just assembled /server-main and that surgically removed stuffed.

    What I would need is help to tell me how to do the SAME thing as
    /server-main mvn assembly:assmeble
    with -sf4jlog4j NOT sf4jnlog4j
    and omit log4j out of the packaging.
    How do I do that?(I need maven help)

    sar does some other crazy Mojo in Maven, I did not even use it.


    Alex Karasulu wrote:
    >
    >
    > On 4/25/07, *Aron Sogor* <[EMAIL PROTECTED]
    <mailto:[EMAIL PROTECTED]>
    > <mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>>> wrote:
    >
    >
    >     Based on old postings I got it working.
    >
    >
    > Oh good.
    >
    >     I have replaced sfl4j-nlog with sf4j-log4j api and got rid
    of any
    >     org.log4j.*classes from the final jar build in server-main.
    >     This deploys snug as an MBean without exception, I was able to
    >     bind too.
    >
    >
    > Nicely done.  You got patches to make the JBoss Sar work with these
    > discoveries?
    >
    >     Question how it integrate that to Maven?
    >     Any interest?
    >
    >
    > Hmmm don't know if I understand your question or your
    intent.  Can you
    > elaborate?
    >
    > Alex



Reply via email to