On 02/04/2011 08:43 AM, Wendy Smoak wrote:
On Fri, Feb 4, 2011 at 9:32 AM, Steve Cohen<[email protected]> wrote:
No, there is a POM. I believe I ran mvn:install:install-file and I would
guess that you're right that -DgeneratePom=true is the default because I
know I didn't create a POM myself. This POM is quite simple. Is it too
simple? Or is this what -Dgenerate=true should generate? Should it's type be
jar?
<dependency>
<groupId>biz.what.ever</groupId>
<artifactId>ever</artifactId>
<version>1.1.3</version>
<type>pom</type>
</dependency>
That does not look like the minimal pom that should be sitting beside
the jar in your local repo.
It shouldn't have a<dependency>, it should just list the
groupId/artifactId/version, and yes, the type should be jar.
Maybe remove it from your local repo and try installing it again?
Thanks, Wendy, you were right the first time. That fragment I sent was
from a Nexus web page (not connected to the local repo I am working
from) and was supposed to indicate how I was to reference this file as a
dependency in other poms.
The actual contents are:
<project xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd";>
<modelVersion>4.0.0</modelVersion>
<groupId>biz.what.ever</groupId>
<artifactId>ever</artifactId>
<version>1.1.3</version>
<description>POM was created from install:install-file</description>
</project>
There was no POM in the local repo.
I still have to question the supposed <dependency> fragment provided by
Nexus is right. Shouldn't the <type> be jar?
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
