I found this:
http://activemq.apache.org/how-do-i-avoid-maven-downloading-latest-jars.html
which describes the -o flag in mvn, which could prevent it from issuing
tons of messages re: eclipse plugins, etc., and probably would make the
build go faster. Haven't tried it though.
-Marshall
Adam Lally wrote:
On 3/1/07, Marshall Schor <[EMAIL PROTECTED]> wrote:
Maybe there's some low-hanging fruit kinds of things we could do to cut
way down on the noise output?
I was able to stop the junit tests from logging to the console by
adding this to the room pom:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-surefire-plugin</artifactId>
<configuration>
<systemProperties>
<property>
<name>java.util.logging.config.file</name>
<value>${basedir}/../uimaj-distr/src/main/config/Logger.properties</value>
</property>
</systemProperties>
</configuration>
</plugin>
Although, I could not then find the uima.log file, so I have no idea
where the log output actually went!
Even with no log output, Maven is still pretty noisy. So I think it
would very difficult to get it to the point where it the person doing
the build would be sure to see a warning message.
It might be better if we make the build fail when jai is missing. Or
prompt the user whether they want to continue.
-Adam
