When we deployed archiva on our CI server we noticed that archiva was
generating tons of logging statements in the log file. The average size
of a log file each day was 50+ MB! This of course is not acceptable, is
there a way to reduce the logging level in archiva? I looked at
archiva.xml and c
I hope this is the right forum to ask this question. When writing a
maven Mojo the maven @component annotation allows you to inject a plexus
component. My question is how can I configure this plexus component to
use a custom components.xml instead of the default components.xml in the
component'
f mvn which then tries to use the same MAVEN_OPTS and fails because the
debug port is already taken.
Makes sense?
Jorg
On Nov 26, 2007 5:11 PM, Bashar Jawad <[EMAIL PROTECTED]> wrote:
I still can't resolve this issue. I am using Maven 2.0.7. This is a
major blocker issue for me s
I still can't resolve this issue. I am using Maven 2.0.7. This is a
major blocker issue for me so I would really appreciate any help. Does
anyone at least know what port the release plugin uses ?
Thanks,
Bashar Jawad wrote:
I am trying to use the maven-release-plugin to prepare and perf
I am trying to use the maven-release-plugin to prepare and perform a
release. I simply created a new empty maven 2 project and added the
required scm information in the POM. However any time I run the command:
mvn release:clean release:prepare maven asks me for
release/tag/developement version