s to the MavenSession.
> >
> > I experienced two issues while debugging and comparing with Maven
> > Invoker and the Maven command line.
> >
> > Before adding issues I wanted to contact you and see if
> > a) MavenEmbedder is still under active development (I've
dding issues I wanted to contact you and see if
> a) MavenEmbedder is still under active development (I've seen this
> asked the bug tracker before)?
> b) A better way exists to achieve my goal? (Preferably without copying
> and adjusting Maven code)
> c) You are mayb
you and see if
a) MavenEmbedder is still under active development (I've seen this
asked the bug tracker before)?
b) A better way exists to achieve my goal? (Preferably without copying
and adjusting Maven code)
c) You are maybe already aware of the issues? (I didn't find them in
the b
on Margulies wrote:
>>> On Mon, Jul 4, 2011 at 6:11 PM, Dennis Lundberg wrote:
>>>> Hi
>>>>
>>>> I'm trying to replace an old version 2.0 MavenEmbedder in the
>>>> aspectj-maven-plugin, over at mojo@codehaus. That's because we can&#x
You have correctly diagnosed my incorrect diagnosis.
On Tue, Jul 5, 2011 at 4:14 AM, Dennis Lundberg wrote:
> On 2011-07-05 01:51, Benson Margulies wrote:
>> On Mon, Jul 4, 2011 at 6:11 PM, Dennis Lundberg wrote:
>>> Hi
>>>
>>> I'm trying to replac
wrote:
On 2011-07-05 01:51, Benson Margulies wrote:
On Mon, Jul 4, 2011 at 6:11 PM, Dennis Lundberg wrote:
Hi
I'm trying to replace an old version 2.0 MavenEmbedder in the
aspectj-maven-plugin, over at mojo@codehaus. That's because we can't
upgrade other Maven core dependencies whi
On 2011-07-05 01:51, Benson Margulies wrote:
> On Mon, Jul 4, 2011 at 6:11 PM, Dennis Lundberg wrote:
>> Hi
>>
>> I'm trying to replace an old version 2.0 MavenEmbedder in the
>> aspectj-maven-plugin, over at mojo@codehaus. That's because we can't
>
On Mon, Jul 4, 2011 at 6:11 PM, Dennis Lundberg wrote:
> Hi
>
> I'm trying to replace an old version 2.0 MavenEmbedder in the
> aspectj-maven-plugin, over at mojo@codehaus. That's because we can't
> upgrade other Maven core dependencies while the embedder is b
is can be looked up by Plexus somehow.
>
> On 4 July 2011 23:11, Dennis Lundberg wrote:
>> Hi
>>
>> I'm trying to replace an old version 2.0 MavenEmbedder in the
>> aspectj-maven-plugin, over at mojo@codehaus. That's because we can't
>> upgrade ot
Settings.getLocalRepository()?
Alternatively filter a test resource and have
${settings.localRepository} as the filtered value
On 4 July 2011 23:11, Dennis Lundberg wrote:
> Hi
>
> I'm trying to replace an old version 2.0 MavenEmbedder in the
> aspectj-maven-plugin, over
Hi
I'm trying to replace an old version 2.0 MavenEmbedder in the
aspectj-maven-plugin, over at mojo@codehaus. That's because we can't
upgrade other Maven core dependencies while the embedder is being used.
In a class that extends AbstractMojoTestCase we have this code:
On 31/03/2010, at 10:33 AM, Jason van Zyl wrote:
> I consider it orthogonal to the CLI and it's not really a new feature per se
> and I don't think folks want to wait until 3.1.
Np, as long as we aren't starting to consider 3.1 as "too big a deal" for small
new things. We're notoriously bad at
Fix Version/s: (was: 3.0-beta-1)
>> 3.0.1
>>
>>> maven-embedder 3.0-alpha-6 doesn't contain the MavenEmbedder class
>>> --
>>>
>>> Key: MNG-4
l updated MNG-4568:
> ---
>
>Fix Version/s: (was: 3.0-beta-1)
> 3.0.1
>
>> maven-embedder 3.0-alpha-6 doesn't contain the MavenEmbedder class
>> --
>>
>
Hello,
I'm having a problem with MavenEmbedder and was hoping someone could help me
out.
I'm trying to execute the following command: "mvn
help:describe<https://cygno.com/exchange/cibarra/Inbox/Re:%20Help%20with%20the%20next%20post.EML/>-Dplugin=help
-Dfull".
To do thi
ogger());
ConfigurationValidationResult validation = MavenEmbedder
.validateConfiguration(configuration);
if (!validation.isValid()) {
throw new RuntimeException("Not valid");
}
oader(loader);
configuration.setMavenEmbedderLogger(new
MavenEmbedderConsoleLogger());
ConfigurationValidationResult validation = MavenEmbedder
.validateConfiguration(configuration);
if (!validation.is
.
On 11 Mar 07, at 8:34 PM 11 Mar 07, Shane Isbell wrote:
Does the MavenEmbedder support the use of custom life cycle
configurations?
To explain a little of my situation: I have a components.xmlfile
configuring phases for the component
org.apache.maven.lifecycle.mapping.LifecycleMapping (using
Does the MavenEmbedder support the use of custom life cycle configurations?
To explain a little of my situation: I have a components.xmlfile
configuring phases for the component
org.apache.maven.lifecycle.mapping.LifecycleMapping (using 'library' as a
role hint). I have a class in
EMAIL PROTECTED]> wrote:
On 9 Mar 07, at 8:43 AM 9 Mar 07, Shane Isbell wrote:
> Just to give everybody a heads up, I'm working a MavenEmbedder Web
> Service component for the Apache NMaven project (under incubation).
> The
> component will enable: 1) IDEs to build m
for it yet.
Shane
On 3/9/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
On 9 Mar 07, at 8:43 AM 9 Mar 07, Shane Isbell wrote:
> Just to give everybody a heads up, I'm working a MavenEmbedder Web
> Service component for the Apache NMaven project (under incubation).
> The
> c
On 9 Mar 07, at 8:43 AM 9 Mar 07, Shane Isbell wrote:
Just to give everybody a heads up, I'm working a MavenEmbedder Web
Service component for the Apache NMaven project (under incubation).
The
component will enable: 1) IDEs to build maven projects on local
and remote
build machin
Just to give everybody a heads up, I'm working a MavenEmbedder Web
Service component for the Apache NMaven project (under incubation). The
component will enable: 1) IDEs to build maven projects on local and remote
build machines; 2) IDE interoperability between non-java languages and
maven
at it
becomes part of the 2.1 version if everyone agrees to this fix.
Hermod
-Original Message-
From: Opstvedt, Hermod
Sent: Tuesday, June 06, 2006 7:11 AM
To: dev@maven.apache.org
Subject: RE: creating a new project with the MavenEmbedder
Hi
I might have a slight variation to you stat
project with the MavenEmbedder
Hi
I might have a slight variation to you statement about goals operating on pom's
or not. Let's say that you are creating an archetype that creates a specific
multiproject layout where the pom beeing operated on is about to become a
module in maybe &quo
ED]
Sent: Sunday, June 04, 2006 4:52 PM
To: Maven Developers List
Subject: Re: creating a new project with the MavenEmbedder
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
ECTED]
Sent: Friday, June 02, 2006 9:26 AM
To: Maven Developers List
Subject: Re: creating a new project with the MavenEmbedder
[EMAIL PROTECTED] wrote:
Hi
Have not had the time before now.
It still does not work. The basedir is still set to the current directory.
The ${basedir} will be s
om: Trygve Laugstøl [mailto:[EMAIL PROTECTED]
Sent: Friday, June 02, 2006 12:10 PM
To: Maven Developers List
Subject: Re: creating a new project with the MavenEmbedder
[EMAIL PROTECTED] wrote:
Hi
Something must be wrong in another place. The eclipse:eclipse goal excutes ok
with the supplied (i.
the eclipse:eclipse
archetype does it right.
Hermod
-Original Message-
From: Trygve Laugstøl [mailto:[EMAIL PROTECTED]
Sent: Friday, June 02, 2006 12:10 PM
To: Maven Developers List
Subject: Re: creating a new project with the MavenEmbedder
[EMAIL PROTECTED] wrote:
> Hi
>
>
[EMAIL PROTECTED] wrote:
Hi
Something must be wrong in another place. The eclipse:eclipse goal excutes ok
with the supplied (i.e correct) basedir, but the MavenArchetypeMojo for some
reason is supplied the working directory, which is not what is supplied in the
call.
You mean if you add thi
--Original Message-
From: Trygve Laugstøl [mailto:[EMAIL PROTECTED]
Sent: Friday, June 02, 2006 9:26 AM
To: Maven Developers List
Subject: Re: creating a new project with the MavenEmbedder
[EMAIL PROTECTED] wrote:
> Hi
>
> Have not had the time before now.
>
> It still does not work.
[EMAIL PROTECTED] wrote:
Hi
Have not had the time before now.
It still does not work. The basedir is still set to the current directory.
The ${basedir} will be set to the value you set in the embedder, this is
working for me in my IDEA plugin where I use the embedder.
Can you include the p
@maven.apache.org
Subject: RE: creating a new project with the MavenEmbedder
Hi
I'll fix it, and give it a test run.
thnx
Hermod
-Original Message-
From: Trygve Laugstøl [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 31, 2006 9:22 AM
To: Maven Developers List
Subject: Re: creating a new pr
Hi
I'll fix it, and give it a test run.
thnx
Hermod
-Original Message-
From: Trygve Laugstøl [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 31, 2006 9:22 AM
To: Maven Developers List
Subject: Re: creating a new project with the MavenEmbedder
[EMAIL PROTECTED] wrote:
> Hi
>
[EMAIL PROTECTED] wrote:
Hi
I have been giving this some thought, and I am wondering if this behaviour is by design (Committers: feel free to chip in here).
If you execute a mojo from a commandline, it takes effect from the current
directory. There is no parameter/command line switch to dire
[EMAIL PROTECTED] wrote:
Hi
I tried what you suggested, and it did create a project in a directory with the
given artifactId, i.e:
mvn -f foo/pom.xml archetype:create -DartifactId=whatever <<< creates a project
under whatever and the output is :
[snip]
Notice that the basedir from the lo
2006 9:01 AM
To: Maven Developers List
Subject: Re: creating a new project with the MavenEmbedder
Hi again,
> [...] Anyways, the issue of archetype:create and baseDir still stands.
That's true. The same thing happens to me.
> No cigar - Doing it two steps yields the same result as if
rong first.
Hermod
-Original Message-
From: Ovidio Mallo [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 31, 2006 9:01 AM
To: Maven Developers List
Subject: Re: creating a new project with the MavenEmbedder
Hi again,
> [...] Anyways, the issue of archetype:create and baseDir still stands
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
-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 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
a new project with the MavenEmbedder
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
RE: creating a new project with the MavenEmbedder
Hi
I tried what you suggested, and it did create a project in a directory with the
given artifactId, i.e:
mvn -f foo/pom.xml archetype:create -DartifactId=whatever <<< creates a project
under whatever and the output is :
[INFO] Param
lto:[EMAIL PROTECTED]
Sent: Wednesday, May 31, 2006 7:18 AM
To: dev@maven.apache.org
Subject: RE: creating a new project with the MavenEmbedder
Hi
I tried what you suggested, and it did create a project in a directory with the
given artifactId, i.e:
mvn -f foo/pom.xml archetype:create -DartifactId=
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 30, 2006 2:03 PM
To: dev@maven.apache.org
Subject: RE: creating a new project with the MavenEmbedder
Hi
I'll give it a try. If it does not work, I'll look into what goes on in
DefaultM
t with the MavenEmbedder
[EMAIL PROTECTED] wrote:
> Hi
>
> Now that I got it running, I have discovered something that may be an error
> in the DefaultExecutionRequest:
>
> This is how I run it:
>
> MavenExecutionRequest request = n
[EMAIL PROTECTED] wrote:
Hi
Now that I got it running, I have discovered something that may be an error in
the DefaultExecutionRequest:
This is how I run it:
MavenExecutionRequest request = new
DefaultMavenExecutionRequest()
.setBasedir(new Fil
the project in the current directory ( I am running the
"archetype:create" goal). Is this a known error or am I presuming wrong here.
Hermod
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 30, 2006 1:23 PM
To: dev@maven.apache.org
Subject:
MavenEmbedder
[EMAIL PROTECTED] wrote:
> Hi
>
> I was running in a directory where a pom existed.
>
> Now running it in an empty directory gives me:
>
> Component composition failed. No field of type: 'interface
> org.apache.maven.artifact.transform.ArtifactTransformati
[EMAIL PROTECTED] wrote:
Hi
I was running in a directory where a pom existed.
Now running it in an empty directory gives me:
Component composition failed. No field of type: 'interface
org.apache.maven.artifact.transform.ArtifactTransformationManager' exists in
class 'org.apache.maven.project
PM
To: dev@maven.apache.org
Subject: RE: creating a new project with the MavenEmbedder
Hi
I can't seem to get this to run correctly. I am getting the following error
when running your code:
org.apache.maven.archetype.ArchetypeTemplateProcessingException: Unable to add
module to the c
ssage-
From: Ovidio Mallo [mailto:[EMAIL PROTECTED]
Sent: Monday, May 29, 2006 1:58 PM
To: Maven Developers List
Subject: Re: creating a new project with the MavenEmbedder
Hi Hermod!
The class compiles against the current 2.1-SNAPSHOT version. The previous
versions 2.0.3 and 2.0.4 seem to
---
From: Rinku [mailto:[EMAIL PROTECTED]
Sent: Monday, May 29, 2006 10:19 PM
To: Maven Developers List
Subject: Re: creating a new project with the MavenEmbedder
Hi Hermod,
Coincidently, there was a thread on maven-users list about delegating
goal to another mojo (see yesterday's posts). I h
ginal Message -
From: <[EMAIL PROTECTED]>
To:
Sent: Tuesday, May 30, 2006 12:34 AM
Subject: RE: creating a new project with the MavenEmbedder
Hi
Ok, I'll get it from SVN and compile it. Thnx
Hermod
-Original Message-
From: Ovidio Mallo [mailto:[EMAIL PROTECTED]
Sent: Mond
Hi
Ok, I'll get it from SVN and compile it. Thnx
Hermod
-Original Message-
From: Ovidio Mallo [mailto:[EMAIL PROTECTED]
Sent: Monday, May 29, 2006 1:58 PM
To: Maven Developers List
Subject: Re: creating a new project with the MavenEmbedder
Hi Hermod!
The class compiles agains
ay, May 28, 2006 12:36 PM
To: Maven Developers List
Subject: Re: creating a new project with the MavenEmbedder
Hi,
Thanks a lot, Kenney, for your explanation and code snippet! This is
exactly what I was looking for! I have filled in the tiny missing
details in your sample code to build up a worki
Developers List
Subject: Re: creating a new project with the MavenEmbedder
Hi,
Thanks a lot, Kenney, for your explanation and code snippet! This is
exactly what I was looking for! I have filled in the tiny missing
details in your sample code to build up a working example which you
can find below
public class ProjectCreator {
public static void main(String[] args) throws Exception {
MavenEmbedder embedder = new MavenEmbedder();
embedder.setClassLoader( Thread.currentThread().getContextClassLoader() );
embedder.setLogger( new MavenEmbedderConsoleLogger() );
embedder.start
re an existing pom.xml.
A sequence like this (more or less) should work for you:
MavenEmbedder embedder = new MavenEmbedder();
embedder.start();
Settings settings = embedder.buildSettings(
embedder.getUserSettingsPath( null ),
embedder.getGlobalSettingsPath(),
false,
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 existi
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 po
Hello,
I currently am working on integration maven into Jbuilder for easy build use
by developers. I have the following issue. Even though i implementa custom
loggers for the various goals i still see compile message on the command
line. This is problably due to some plugin running the compile. H
hen I'm executing a MavenEmbedder (trunk version), I have a
problem with it
trying to update the plugins defined in my POM. These plugins are not
available when I run the embedder, so I would like to either remove
them
from the MavenProject, or define in some way that I don't want
maven to
c
hen I'm executing a MavenEmbedder (trunk version), I have a
problem with it
trying to update the plugins defined in my POM. These plugins are not
available when I run the embedder, so I would like to either remove
them
from the MavenProject, or define in some way that I don't want
maven to
c
Hi,
Sorry for cross-posting. Guess the dev list is more suitable than the users.
When I'm executing a MavenEmbedder (trunk version), I have a problem with it
trying to update the plugins defined in my POM. These plugins are not
available when I run the embedder, so I would like to either r
mavenembedder logger not handling exception logs
Key: MNG-1942
URL: http://jira.codehaus.org/browse/MNG-1942
Project: Maven 2
Type: Bug
Components: Embedding
Versions: 2.0.1
Reporter: Milos Kleint
65 matches
Mail list logo
