Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3

...

% mvn exec:java -Dexec.mainClass="com.example.App"

Also 3 ways to run a Java Main from Maven is helpful.

How about making sure all files needed are available so I can run disconnected?

...

I need to not fail the clean if dependecies aren't present, but still fail if the build products could not be deleted. In this case I have dependecies that *must* use systemPath. Those dependecies are deleted from that path by a clean of other projects.  Maven goals are always executed on those other projects first so that the dependency is in place for my other project. (The build of those projects produces an SDK in a folder with a specific layout.  The project with a problem is a sample that uses that SDK.).  I am already aware of failOnError which is a poor workaround as it won't catch real problems.

Can I reference a Non-Maven Project and include it as jar in my Maven Project? How can i do that?