Hi Alexis,
you may try with
@parameter expression="${excludes}"
in the annotation of your array. I can't test it right now, but I
guess this should work.
Regards,
Ovidio
Alexis Midon wrote:
Hi all,
I'm currently writting a custom plugin, but I've got a problem with the
parameter setting
Hi,
is there some way to enumerate the individual directories of the default
Maven2 directory layout as described in
http://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html
in order to avoid having to hardcode the directories in some client code
which needs
er you to do for now as I do not have any work-around in mind for
your problem.
Thanks a lot for taking the time to look at it, Edwin! I think I will
indeed open a feature issue for it on JIRA.
Cheers,
Ovidio
Ovidio Mallo wrote:
Edwin Punzalan wrote:
Have you tried using the assembly p
vidio
Ovidio Mallo wrote:
Hi,
a few days ago I have posted a request on the Maven user list for some
way to create a source bundle for an artifact which not only includes
the artifact's source (as produced by source:jar) but also the sources
of its transitive dependencies. I was tol
Hi,
a few days ago I have posted a request on the Maven user list for some
way to create a source bundle for an artifact which not only includes
the artifact's source (as produced by source:jar) but also the sources
of its transitive dependencies. I was told that the closest approach
to this is u
rence between the path to
the pom, and what you consider the basedir of you structure.
I'll give your patch a try and see if it solves the problem immidiatly at hand.
Hermod
-----Original Message-
From: Ovidio Mallo [mailto:[EMAIL PROTECTED]
Sent: Sunday, June 04, 2006 4:52 PM
To: Mav
Hi,
I'm attaching a patch which tries to solve the issue with the basedir
discussed in this thread. The value of the ${basedir} expression is
thereby computed by one of the following fallbacks (in the given order):
1. If the goal being executed is attached to a project, take the directory where
Hi,
indeed, there seems to be something wrong at some other place. I'm also looking
a bit at the code, but I still have a question about the purpose of using a
basedir: for plugins which do not operate on an existing maven project (e.g. the
archetype), having such a basedir is fine and intuitive,
y 31, 2006 8:39 AM
To: dev@maven.apache.org
Subject: RE: creating a new project with the MavenEmbedder
Hi
Ok, I'll give that a try and see what happens then. Anyways, the issue of
archetype:create and baseDir still stands.
Hermod
-Original Message-
From: Ovidio Mallo [mailto:[EMA
Hi Hermod,
I'm not sure what it is but in any case I would avoid calling a second goal
together with the archetype:create goal which should work on the project
yet to be created since the following maven2 invocation also fails on the
commandline:
mvn -DgroupId=a.b.c -DartifactId=d archetype:
st regards,
Ovidio
[EMAIL PROTECTED] wrote:
Hi
Which version of the embedder is this? I get errors on the methods:
getUserSettingsPath and getGlobalSettingsPath - No such methods in the Maven
embedder (2.0.3).
Hermod
-Original Message-----
From: Ovidio Mallo [mailto:[EMAIL PROTECTED]
Sent: Sund
VEL_DISABLED, "logger" ) ) );
embedder.execute( request );
}
}
====
Kenney Westerhof wrote:
> On Sat, 27 May 2006, Ovidio Mallo wrote:
>
> Hi,
>
> Well, currently running archetype:create seems the simplest way to me.
> The embedde
Hi everyone!
I just wanted to ask whether there is a clean way to create a new maven
project using the MavenEmbedder API. It is of course possible to
execute the "archetype:create" goal but the API seems to always
require that you already pass in an existing project (at least
an existing pom.xml
Hi everyone!
I was wondering whether there is a clean way to create a new maven
project using the MavenEmbedder API. It is of course possible to
execute the "archetype:create" goal but the API seems to always
require that you already pass in an existing project (at least
an existing pom.xml file)
14 matches
Mail list logo
