Re: how to add additional path to the compiler ?

[garyng]

thanks for the information.

I want  to do this is because certain jars are not in the maven
repositories. I know the option I can have is to install a local repo but
that can be quite time consuming and if I have multiple machines, I have to
do it on each of them or must go to the length of setting up a local web
server just for maven.

dropping those into WEB-INF/lib means they always go with the project rather
than have to setup each and every time. And given the delicacy of how a
simple version change can break things, I sometimes find maven2's transitive
dependency doing more harm then help having my specific WEB-INF/lib version
is much better.

In fact, under eclipse(and the m2eclipse plugin), I am effectively working
in this mode. It is just that when I want to do it outside eclispse, I don't
know how to.

The main issue with local maven repo is that maintaining it requires quote
some efforts.

Simon Kitching-4 wrote:
> 
> 
> Adding libs to the classpath directly, bypassing maven, is not the right
> way to do things. I suspect you'll find that *other* compiler arguments
> work fine, but that classpath is not passed through because Maven wants to
> set that itself.
> 
> You probably should declare these extra jars as normal 
> sections in your pom. If you absolutely have to, then use 
>   system
>   ..
> although "normal" maven dependency resolution via the repository is better
> wherever possible.
> 
> I haven't tried it, but maybe 
>   ${project.basedir}/
> could be used in the systemPath section if the files are checked in within
> a subdir beneath the pom.
> 
> Regards,
> 
> Simon
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/how-to-add-additional-path-to-the-compiler---tp14728064s177p14730523.html
Sent from the Maven - Users mailing list archive at Nabble.com.


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

how to add additional path to the compiler ?

[garyng]

I followed this

http://maven.apache.org/plugins/maven-compiler-plugin/examples/pass-compiler-arguments.html

but it seems that it is being ignored/eaten.

What I want is to include the "src/main/webapp/WEB-INF/lib" to the compiler
classpath as there are libraries not managed in maven.

I believe this is pretty standard situation.

-classpath src/main/webapp/WEB-INF/lib"

would results in javac error


src/main/webapp/WEB-INF/lib


doesn't seem to be passed to javac, even though the mvn -X dump shows that
it has been picked up by the plugin.

I am wondering if the feature has even been tested before ? 

-- 
View this message in context: 
http://www.nabble.com/how-to-add-additional-path-to-the-compiler---tp14728064s177p14728064.html
Sent from the Maven - Users mailing list archive at Nabble.com.


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