Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

My project uses a Maven build system, and the Maven build includes a command line call to thrift to compile some files.

In bash, mvn generate-sources successfully completes.

But when I use m2e's Run as... -> generate-sources, the Eclipse console log shows an error about a binary not in PATH. How can I correct m2e's/Eclipse's notion of user PATH?

Using latest Eclipse, on latest Mac OS X.

share|improve this question
Not a solution, but "Why" -> Maven expects to be entirely self contained, and whatever plugin that is making the call to thrift is responsible for finding the executable or including it. While unavoidable sometimes, relying on a program simply being in the correct place on the PATH is bad practice in the maven world. – Darth Android Sep 17 '13 at 14:49
@DarthAndroid 1) How else should integrate Thrift compilation into my Maven build process? 2) As I said, mvn generate-sources works in bash. It's Eclipse/m2e that completely fails to load to the user PATH environment variable. – apennebaker Sep 17 '13 at 15:32

You must log in to answer this question.

Browse other questions tagged .