I'll start it this week and I hope to finish the css changes and webwork 2.2.2
for the end of next week
Emmanuel
Brett Porter a écrit :
Where are we at here?
Emmanuel Venisse wrote:
I have some plexus changes to apply because continuum trunk use some
snapshot that must be updated.
I'll
Title: RE: M2 : How to implement goals in SCM provider implementation ?
Hi Emmanuel,
Initially, I have implemented the connect method other functionality in SCM provider for MKS plugin and it has been been built and installed in local repository. I want to know, how to configure this plugin
...why? Could you elaborate?
I find the current behaviour counter-intuitive.
I think if you were building a jar that had modules, 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
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
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
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:
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 doing it in one step
- Here is the output:
What POM file have you set on the request for the eclipse:eclipse
Hi
Yepp, you are right. The problem stems from the fact that the archetype:create
goals creates it in the wrong directory. I just have'nt done anything with the
code to work around this. I'm going to start debugging through the
archetype:create mojo-code to see where things go wrong first.
-Original Message-
From: Mike Perham [mailto:[EMAIL PROTECTED]
Sent: mercredi 31 mai 2006 00:14
To: Maven Developers List
Subject: RE: [VOTE] Release Clover plugin v2.2
+1
Did you ever get the coverage numbers to include calls from other modules
(you were talking about adding
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 direct it to another
working
[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 log
[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
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
I tried
Tried to do a clean checkout of the jboss module but keep getting the
following errors. Am I doing something wrong?
checkout -r HEAD svn://svn.codehaus.org/mojo/trunk/mojo/jboss-maven-plugin
A C:/eclipse-workspace/jboss-maven-plugin/LICENSE.txt
A
Hi all
Work on the maven-maven1-plugin is coming along nicely. So far I've
submitted 3 patches to JIRA and a couple more are in the pipeline.
Coming up next are:
- use maven-model-converter instead of bundled class
- property configuration converters for the checkstyle, jar and javadoc
Done. Thanks.
On 5/31/06, Dennis Lundberg [EMAIL PROTECTED] wrote:
Hi all
Work on the maven-maven1-plugin is coming along nicely. So far I've
submitted 3 patches to JIRA and a couple more are in the pipeline.
Coming up next are:
- use maven-model-converter instead of bundled class
- property
Thanks!
Carlos Sanchez wrote:
Done. Thanks.
On 5/31/06, Dennis Lundberg [EMAIL PROTECTED] wrote:
Hi all
Work on the maven-maven1-plugin is coming along nicely. So far I've
submitted 3 patches to JIRA and a couple more are in the pipeline.
Coming up next are:
- use maven-model-converter
Hi Reinhard,
Some notes inlined below:
Reinhard Poetz wrote:
Rinku wrote:
snip/
So far I added the configuration parameter pde. If set to true,
the PluginNature and the schema and manifest builders are added to
.project.
I have a patch submitted for this for the maven-eclipse-plugin.
Issue Subscription
Filter: Outstanding Repository Maintenance: Evangelism (31 issues)
Subscriber: mavendevlist
Key Summary
MEV-401 Incoherences / duplication between javax.xml and com.sun.xml
http://jira.codehaus.org/browse/MEV-401
MEV-279 empty dependencies/ in batik
Issue Subscription
Filter: Outstanding Repository Maintenance: Uploads (14 issues)
Subscriber: mavendevlist
Key Summary
MAVENUPLOAD-925Java Bean Library
http://jira.codehaus.org/browse/MAVENUPLOAD-925
MAVENUPLOAD-900mocquer 0.9.3
20 matches
Mail list logo
