Can anyone help me figure out what this means? I'm using maven 2.0.4
(but I tried maven-2.1-SNAPSHOT with the same results). I'm doing a
reactor build and although my build works perfectly fine when I go to
each submodule and invoke "mvn install", if I try to do this from the
top level pom direct
guring out what
is going wrong? I can't debug into Field.set (part of the reflection
api) and I see no reason why java.lang.reflect would be failing -
especially since we execute the exact same code in other cases without
any problem.
Help! Thanks. -- Eric
___
splay/MAVENUSER/Dealing+with+Eclipse-based+ID
E
On 10/12/06, Swenson, Eric <[EMAIL PROTECTED]> wrote:
>
> I've managed to create an eclipse project by running "mvn
> eclipse:eclipse" in the maven-2.0.4 source tree. And after defining
the
> M2_REPO classpath variable, I
I apologize for the stupidity, I used the command line parameters rather
than the vm parameters. I can get past this problem and into MavenCli
now. So I'm going to try to debug the problem with the plugin manager.
Thanks. -- Eric
From: Swenson, Eric
a conf file? Thanks. -- Eric
________
From: Swenson, Eric
Sent: Thursday, October 12, 2006 9:18 PM
To: 'Maven Developers List'
Subject: debugging maven with eclipse
Can anyone point me to instructions on how to use eclipse to debug
maven? I'm having a problem that no one, so fa
Can anyone point me to instructions on how to use eclipse to debug
maven? I'm having a problem that no one, so far, has commented on -
namely that when I do a reactor build of my project (top-level with
sub-projects), I get the error (when doing "mvn install"):
[ERROR] BUILD ERROR
[INFO]
Can anyone explain what this error means:
[INFO] Internal error in the plugin manager executing goal
'org.apache.maven.plugins:maven-jar-plugin:2.1:jar': Unable to find the
mojo 'org.apache.maven.plugins:maven-jar-plugin:2.1:jar' in the plugin
'org.apache.maven.plugins:maven-jar-plugin'
[I posted this on the Maven Users List, but got no answer so thought I'd
try here. - Hope that's ok.]
I'm trying to assemble an image consisting of the artifacts created by
a maven2 project. The artifacts (all installed and in the repository)
are of three forms:
- jar files
- wsr fi
y artifact being the jar. This would
at
least solve the packaging/deploy extension coupling "problem".
Sorry some of this is OT to maven-dev, but I'd really like to see the
jboss-packaging mojo inherit your WSR code, and be stablized for a
release.
Regards,
Doug
On 10/7/06, Swen
e your plugin is not a "standard" plugin you have to
use
the element with your plugin declaration in the pom of the
project that uses the maven-wsr-plugin so that maven knows to look for
lifecycle enahncements in the plugin.
Wb
On 10/7/06, Swenson, Eric <[EMAIL PROTECTED]> wrote
I looked in both the maven-jar-plugin and the maven-war-plugin and don't
see any components.xml. Yet these both appear to define a default life
cycle mapping (somehow). -- Eric
-Original Message-
From: Swenson, Eric
Sent: Friday, October 06, 2006 11:56 PM
To: Maven Developers
ng is an "extension" [2] element in your POM.
-Nathan
[1]
http://maven.apache.org/guides/introduction/introduction-to-the-lifecycl
e.html
[2]
http://maven.apache.org/ref/current/maven-model/maven.html#class_extensi
on
On 10/6/06, Swenson, Eric <[EMAIL PROTECTED]> wrote:
> Well, I'
ponent descriptor cannot be found in the component repository:
org.apache.maven.lifecycle.mapping.LifecycleMappingwsr.
If my pom uses jar
I'm able to use "mvn compile" or "mvn package" or "mvn install".
How can I enable this for my maven-wsr-plugin (e.g. pom files
I'm using Maven 2.0.4 and need to produce a .wsr file. A .wsr file is a
jboss web service archive and is very similar to a .war file, a .sar
file, and an .ear file. I've tried two tacts so far, neither
successful.
The first approach was to take the mavin-war-plugin sources, renaming
all insta
14 matches
Mail list logo
