Hi
No cigar - Doing it two steps yields the same result as if doing it in one step
- Here is the output:
[ maven embedder INFO]
[ maven embedder INFO] Using following parameters for creating Archetype:
maven-archetype
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:[EMAIL PROTECTED]
Sent: Wednesday, May 31, 2006 8:30 AM
To: Maven Developers List
Subject: Re: creating a new proj
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:
> ...why? Could you elaborate?
> I find the current behaviour counter-intuitive.
I think if you were building a jar that had , 9/10 people would
expect the modules to be included in some way.
Hm... the whole point of modules is to be modular - and not be part of the whole
thing. So of course it
Hi
A little update. I added .setPomFile("E:/foo/pom.xml") to
DefaultMavenExecutionRequest, and now it definitly gets weird :
[ maven embedder INFO]
[ maven embedder INFO] Using following parameters for creating Archet
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] Parameter: groupId, Value: a.b.c
[INFO] Parameter: packageNam
Did anyone make any advancement on this?
Mike Perham wrote:
There are a number of JIRA issues related to velocity verbosity. All of
them are marked as fixed and yet the latest site plugin is spewing the
same drek as it has been for the last 6 months. Does something need to
be toggled or did th
can you add it to JIRA please?
David Smiley wrote:
I developed an XSLT script that I'd like the maven team to add to this
page:
http://maven.apache.org/guides/mini/guide-m1-m2.html
My mailing list submission of the script to maven.user is here:
http://article.gmane.org/gmane.comp.jakarta.turbi
Torsten Curdt wrote:
> I meant: why shouldn't also the parent pom have a src directory and
> generate a jar? I don't understand the concept of this distinction
> that forces me to have all my code in modules.
It would be counter-intuitive unless it were aggregating.
...why? Could you elabora
+1
Vincent Massol wrote:
Hi,
I'd like to release v2.2 of the Clover plugin. Here are the changes brought
since v2.1:
** Bug
* [MCLOVER-35] - Missing a "test-jar" dependency at compile time.
* [MCLOVER-36] - Plugin should locate clover artifact based on
groupId+artifactId and not only o
+1
Did you ever get the coverage numbers to include calls from other modules (you
were talking about adding a clover artifact to the repo for this)? 2.3?
-Original Message-
From: Vincent Massol [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 30, 2006 9:16 AM
To: 'Maven Developers List'
S
done, will be there in some hours
On 5/30/06, Jochen Wiedmann <[EMAIL PROTECTED]> wrote:
... the directory
/www/www.apache.org/dist/maven-repository/org/apache/ws/commons to
Ibiblio, if this still needs manual work. If not, please let me know, so
that I'll stop such nagging in the future. :-)
... the directory
/www/www.apache.org/dist/maven-repository/org/apache/ws/commons to
Ibiblio, if this still needs manual work. If not, please let me know, so
that I'll stop such nagging in the future. :-)
Jochen
-
To unsubscrib
+1
Vincent Massol wrote:
Hi,
I'd like to release v2.2 of the Clover plugin. Here are the changes brought
since v2.1:
** Bug
* [MCLOVER-35] - Missing a "test-jar" dependency at compile time.
* [MCLOVER-36] - Plugin should locate clover artifact based on
groupId+artifactId and not only o
Hi Mike,
(answering an email from the past that I hadn't processed and was still
sitting in my inbox)
> -Original Message-
> From: Mike Perham [mailto:[EMAIL PROTECTED]
> Sent: mercredi 12 avril 2006 00:35
> To: Maven Developers List
> Subject: clover and cpd plugin clashes
>
> So this i
I developed an XSLT script that I'd like the maven team to add to this page:
http://maven.apache.org/guides/mini/guide-m1-m2.html
My mailing list submission of the script to maven.user is here:
http://article.gmane.org/gmane.comp.jakarta.turbine.maven.user/45067
Thanks.
~ David Smiley
--
Hi,
I'd like to release v2.2 of the Clover plugin. Here are the changes brought
since v2.1:
** Bug
* [MCLOVER-35] - Missing a "test-jar" dependency at compile time.
* [MCLOVER-36] - Plugin should locate clover artifact based on
groupId+artifactId and not only on artifactId
* [MCLOVER-
hi,
Thanks for ur reply...
but, im using cvs - eclipse in mac...and im connecting the cvs of my client
through vpn...my vpn is connected...so, is there any cvs client for
mac?...also, this repository is thru eclipse-cvs repositroy...
i m not getting a clear picture of the connection...
plz.sugge
Hi
I'll give it a try. If it does not work, I'll look into what goes on in
DefaultMavenExecutionRequest.
Hermod
-Original Message-
From: Trygve Laugstøl [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 30, 2006 1:55 PM
To: Maven Developers List
Subject: Re: creating a new project with the
cvs isn't in your path. You must add it.
Emmanuel
Chandrika a écrit :
Hi,
I tried adding maven 2 project in Continuum.My SCM url format is
perfect.This is my scm tag in pom.xml
scm:cvs:pserver:[EMAIL
PROTECTED]:/istcvs/CVSHOME:ETS/ESP/ESP-POC
wher ETS/ESP/ESP-POC is my module in workspace
O
Hi Chandrika,
You need to have the CVS client installed and for it to be available on
the bin path of the user continuum is running as.
thanks
-Original Message-
From: Chandrika [mailto:[EMAIL PROTECTED]
Sent: 30 May 2006 12:55
To: continuum-dev@maven.apache.org
Subject: Build failure
[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
Hi,
I tried adding maven 2 project in Continuum.My SCM url format is
perfect.This is my scm tag in pom.xml
scm:cvs:pserver:[EMAIL
PROTECTED]:/istcvs/CVSHOME:ETS/ESP/ESP-POC
wher ETS/ESP/ESP-POC is my module in workspace
On building the project the following error is thrown
Exception:
cannot c
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 File("E:/Test")).setGoals(goal
Hi
Bullseye - I had a 2.0.1 version in there. Now they are all 2.1-SNAPSHOT and it
works OK. Thnx.
Hermod
-Original Message-
From: Trygve Laugstøl [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 30, 2006 1:07 PM
To: Maven Developers List
Subject: Re: creating a new project with the MavenEm
[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
Hi!
I have seen you have filed a similar bug in jira
(http://jira.codehaus.org/browse/MNG-2289). I have added my description to that
bug and have voted to it.
Roger
> -Ursprüngliche Nachricht-
> Von: Jörg Schaible [mailto:[EMAIL PROTECTED]
> Gesendet: Montag, 29. Mai 2006 18:28
> An:
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.DefaultMavenProjectBuilder
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 current project as it is not of packaging type 'pom'
Hermod
-Original Message-
From: Ovid
multi-module
ok ...multi-module it is from now on :)
> I meant: why shouldn't also the parent pom have a src directory and
> generate a jar? I don't understand the concept of this distinction
> that forces me to have all my code in modules.
It would be counter-intuitive unless it were aggrega
Hi
Thank you for the tip. However the ting is that the functionality that I am
after actualy presumes that there does not exist any pom. Your sample does
require a pom.
I was hoping to create an archetype that creates a complete project setup for
new developers coming into any of our projects.
The default is snapshots are disabled. Checked the
http://www.ibiblio.org/maven2/org/apache/apache/1/apache-1.pom and
maven-repository-artifact-applet wasn't downloading the snapshot
maven-jar-plugin.
Brett Porter wrote:
That's the default?
[EMAIL PROTECTED] wrote:
Author: jtolentino
Date:
That's the default?
[EMAIL PROTECTED] wrote:
Author: jtolentino
Date: Tue May 30 00:09:00 2006
New Revision: 410201
URL: http://svn.apache.org/viewvc?rev=410201&view=rev
Log:
Enabled plugin snapshot downloading.
Modified:
maven/repository-manager/trunk/maven-repository-artifact-applet/pom.
33 matches
Mail list logo
