java - Include a library while programming & compiling, but exclude from build, in NetBeans Maven-based project

Question

In NetBeans 8, in a Maven-based project, how does one use a jar while programming but omit from build?

I need to access some specific classes in a specific JDBC driver in my Vaadin web app. But in web apps, we normally do not bundle JDBC drivers within our build (the .war file). Instead, the JDBC drivers belong in a folder controlled by the Servlet container (the runtime environment).

So, I need the JDBC driver (a jar file) to be on the classpath while I am editing my code and compiling. But that jar file must be omitted from the build.

exclusions Tag

I tried adding the exclusions and exclusion tags to my dependency element. But this did not work –?The postgresql-9.4-1201.jdbc41.jar appeared in WEB-INF/lib folder.

<dependency>
    <groupId>org.postgresql</groupId>
    <artifactId>postgresql</artifactId>
    <version>9.4-1201-jdbc41</version>
    <exclusions>
        <exclusion>
            <groupId>org.postgresql</groupId>  Exclude from build 
            <artifactId>postgresql</artifactId>
        </exclusion>
    </exclusions>
</dependency>

New Profile?

This Answer by ZNK - M on the Question, Setting custom runtime classpath for a maven project in netbeans, may be what I need.

But creating a new project profile seems like overkill what seems like small little task to me. And, I always want to exclude this jar from my build output, not just when testing or in other limited scenarios.

You should add a new profile run-with-netbeans in your pom that declares the additional dependencies (use the provided scope to not include them in the release).

Then you'll have to add the new profile to your IDE to run the pom with the -P run-with-netbeans option in the command line.

But I am familiar only with the basics of editing a POM file. If that approach is the way to go, it would be helpful if someone could expand on the details and steps needed.

Answer 1

Use the provided scope instead of the default compile scope for this dependency. That's exactly what it's for.

<dependency>
    <scope>provided</scope>
    <groupId>...</groupId>
    <artifactId>...</artifactId>
    <version>...</version>
</dependency>