StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>Without being able to look at your POM file, my best guess is that you're not defining your dependencies correctly. Apache's POM reference at: <a href="http://maven.apache.org/pom.html#The_Basics" rel="nofollow">http://maven.apache.org/pom.html#The_Basics</a> shows: </p> <pre><code><dependencies> <dependency> <groupId>junit</groupId> <artifactId>junit</artifactId> <version>4.0</version> <type>jar</type> <scope>test</scope> <optional>true</optional> </dependency> ... </code></pre> <p></p> <p>I think you need to focus on the 'scope' attribute, where you can list it as either 'provided' or 'system'. That way maven won't look for your jars in its repository. Here are the possibilities w/ descriptions: </p> <blockquote> <p>scope: This element refers to the classpath of the task at hand (compiling and runtime, testing, >etc.) as well as how to limit the transitivity of a dependency. There are five scopes >available: compile, provided, runtime, test, system.</p> <p>compile - this is the default scope, used if none is specified. Compile dependencies are >available in all classpaths. Furthermore, those dependencies are propagated to dependent >projects.</p> <p>provided - this is much like compile, but indicates you expect the JDK or a container to >provide it at runtime. It is only available on the compilation and test classpath, and is >not transitive.</p> <p>runtime - this scope indicates that the dependency is not required for compilation, but is >for execution. It is in the runtime and test classpaths, but not the compile classpath.</p> <p>test - this scope indicates that the dependency is not required for normal use of the >application, and is only available for the test compilation and execution phases.</p> <p>system - this scope is similar to provided except that you have to provide the JAR which >contains it explicitly. The artifact is always available and is not looked up in a >repository.</p> </blockquote> <p>It's also important to remember to include a groupId for each dependency that corresponds with the groupId of a repository. I've found that even if my files are saved locally, they still need a groupId - even if the scope is 'provided.'</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload