[jira] Subscription: Outstanding Repository Maintenance: Uploads

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 http://jira.codehaus.org/browse/MAV

[jira] Subscription: Outstanding Repository Maintenance: Evangelism

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 in batik v1.6 poms on

Re: maven-eclipse-plugin and Eclipse Plugin support

Hi Reinhard, Some notes inlined below: Reinhard Poetz wrote: Rinku wrote: 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. Thou

Re: [maven-maven1-plugin] 3 patches awaiting review

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 inst

Re: [maven-maven1-plugin] 3 patches awaiting review

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

[maven-maven1-plugin] 3 patches awaiting review

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 plugin

Error Checking out a module

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 C:/eclipse-workspace/jboss-maven-plugin/

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 project with the MavenEmbedder [EMAIL PROTECTED] wrote: > Hi > > I tried w

Re: creating a new project with the MavenEmbedder

[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

Re: creating a new project with the MavenEmbedder

[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

RE: creating a new project with the MavenEmbedder

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 d

Integration testing with Clover plugin (was RE: [VOTE] Release Clover plugin v2.2)

> -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 abo

RE: creating a new project with the MavenEmbedder

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. Her

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 doing it in one step - Here is the output: What POM file have you set on the request for the eclipse:eclipse