Re: [Wrapper-user] JWS & maven2 usage II

[Leif M. <le...@ta...>]

Dave,
    The Wrapper builds up a classpath which is compatible with the 
standard Java
classpath argument.   This means that you can add directories.  But 
those directories
become classpath entries for unjared class files.

    The Wrapper does go one step farther in that it will expand 
wildcards at run time.
This means that you can do the following:
wrapper.java.classpath.1=../lib/*.jar

    This is what I usually do for my applications and it works like a charm.
Will this work for you?

Cheers,
Leif


Dave Hoffer wrote:
>
> Is it possible to specify the java.classpath in the wrapper.conf file 
> by specifying a directory?  I want it to include all jars in a 
> specified folder.  This would be another way to solve the problem of 
> using JWS with maven.
>
>  
>
> -dh
>
>  
>
> ------------------------------------------------------------------------
>
> *From:* Dave Hoffer
> *Sent:* Wednesday, October 04, 2006 7:42 PM
> *To:* 'wra...@li...'
> *Subject:* JWS & maven2 usage
>
>  
>
> I would like to use JWS in a maven2 build environment.  
>
>  
>
> Usage of JWS requires manual configuration of the 
> wrapper.java.classpath.X section of the wrapper.conf file.  Maven 
> build systems put the version of the artifacts in the jar file names. 
>  These means that the list of jar names to be added to the conf file 
> changes often.  This should be dynamic so that these dependencies are 
> automatically added to the conf file.
>
>  
>
> Has there been any work done on a JWS plugin for maven that can 
> automatically configure the conf file?
>
>  
>
> -David
>
>  
>