Hello
I am having trouble building with Maven 2 using Sun JDK 1.5. The build is
looking for the Sun jar Tools.jar, but I have not got this in the JDK
distribution I installed on my system. The JAVA_HOME environment variable is
set to point to the location of my JDK( ie
Double-check that you've installed the JDK, not the JRE. The JRE does not
ship tools.jar. Also, if you've installed *both*, you may want to check
that you've installed them to different locations. A conversation about
this is here:
On 3/31/07, Victor Katte [EMAIL PROTECTED] wrote:
Hello
I am having trouble building with Maven 2 using Sun JDK 1.5. The build is
looking for the Sun jar Tools.jar, but I have not got this in the JDK
distribution I installed on my system. The JAVA_HOME environment variable is
set to point to
Am I the only one for whom the upgrade from the SCM plugin 1.5 to
1.6.1broke the build.
Everything worked fine with 1.5. When I upgraded to 1.6.1 it failed with
this message:
echo] DEPRECATED: scm:validate has been deprecated
BUILD FAILED
File..
I've been getting failed builds with Archiva since last night for the
following error in the archiva-proxy project.
Test set: org.apache.maven.archiva.proxy.ProxyRequestHandlerTest
---
Tests run: 64, Failures: 0, Errors:
You can try http://jira.codehaus.org/browse/MOJO-535 -- I havent tried
it so your milage may vary.
It seems that these operations (reading properties from a file into
the maven build and writing the current maven properties to a file)
are highly desirable. Is there any reason why maven
Platform: Win32,
maven-2.0.4,
maven-dependency-plugin 2.0-alpha-3 and 2.0-alpha-4
People at work, following my development environment setup howtos,
have started complaining to me that dependency:unpack of .tgz files
fails.
What seems to be happening is that responses with
Is it possible to have the dependency plugin (or the eclipse plugin?
not sure which is responsible for this bit when doing
'eclipse:eclipse') download the sources for dependencies with a
classifier of tests? The problem seems to be that deployed test
sources ends up with a classifier of
This is not an uncommon question, and JvZ has responded to it previously.
http://www.nabble.com/Making-properties-accessible-in-pom.xml-tf3236898s177.html#a9023112
Wayne
On 3/31/07, Trevor Torrez [EMAIL PROTECTED] wrote:
You can try http://jira.codehaus.org/browse/MOJO-535 -- I havent tried
Which version of maven 1 are you using ? 1.0.2, 1.1-beta-X ?
What are your scm plugin settings and your scm url ?
Why are you using the deprecated goal scm:validate ?
Supported goals are :
http://maven.apache.org/maven-1.x/plugins/scm/goals.html
There's certainly a bug because this property is
Steinar,
Putting explicit versions should force it. The only caveat is that it
seems that once maven picks a version in a multi-module build, it uses
that throughout the build, regardless of individual poms.
Looking over the change log[1], I don't see anything that would affect
this between the
Hi All,
Has anyone used windows LDAP to authenticate users trying to connect to a
maven remote repository on an internal server?
Thanks,
David Williams
12 matches
Mail list logo