maven-compat, maven-toolchain ??

Hi, I'm trying to get familiar with maven codebase. Can anyone tell me the purpose of "maven-compat" and "maven-toolchain" in the latest trunk? I would guess "maven-compat" is for backward compatibility (as it has old structures inside)? Then what about toolchain? Cheers, Pi Song

RE: [vote] release asf/maven/maven-plugins/maven-shared poms

Results: Binding +8: Brian, John, Jason, Arnaud, Brett, Vincent, Olivier, Dennis NB +2: Oleg, Mark Struberg I'll promote the poms. -Original Message- From: Dennis Lundberg [mailto:denn...@apache.org] Sent: Friday, February 20, 2009 7:08 PM To: Maven Developers List Subject: Re: [vote] re

Re: [vote] release asf/maven/maven-plugins/maven-shared poms

Yep, looks fine now +1 Brian E. Fox wrote: > Grrr. It's fixed now: > https://repository.apache.org/content/repositories/maven-staging-493287f > 5223d96/org/apache/maven/plugins/maven-plugins/13/ > > FWIW, the release plugin puked on this file because it found a cycle in > the plugins even though

RE: Release/staging question

Best to wait, I just fixed the issues you found, if you change your vote, we can release them, it's been 72hrs. -Original Message- From: Dennis Lundberg [mailto:denn...@apache.org] Sent: Friday, February 20, 2009 6:49 PM To: Maven Developers List Subject: Release/staging question Hi I'm

RE: [vote] release asf/maven/maven-plugins/maven-shared poms

Grrr. It's fixed now: https://repository.apache.org/content/repositories/maven-staging-493287f 5223d96/org/apache/maven/plugins/maven-plugins/13/ FWIW, the release plugin puked on this file because it found a cycle in the plugins even though I specified the -N flag, so I had to effectively finish

Release/staging question

Hi I'm about to stage the release of Doxia Sitetools 1.0. Do I have to wait for the new parent POMs to come through, and upgrade to those? Or can I use the "deploy.altRepository" in my release profile in settings.xml? If so, should I use the URL https://repository.apache.org/service/local/staging

Re: [vote] release asf/maven/maven-plugins/maven-shared poms

ASF and Maven POMs are ok. +1 for those The section point to trunk for maven-plugins-13. It's the same in the staged POM. Still -1 I'm afraid The staged POM for shared also has an section that points to trunk. -1 Brian E. Fox wrote: > Dennis, can you take another look and hopefully update you

Re: settings security: --enc-passwd / --enc-master-passwd options

Brett Porter wrote: On 20/02/2009, at 10:19 PM, Brett Porter wrote: Hi, To make it a bit easier to remember, I added two options to the CLI for 2.1: --enc-master-passwd and --enc-passwd; which are equivalent to -m and -p on DefaultSecDispatcher. For consistency with other options, it ta

RE: [vote] release asf/maven/maven-plugins/maven-shared poms

Dennis, can you take another look and hopefully update your vote? -Original Message- From: Dennis Lundberg [mailto:denn...@apache.org] Sent: Thursday, February 19, 2009 4:15 PM To: Maven Developers List Subject: Re: [vote] release asf/maven/maven-plugins/maven-shared poms -1 on the maven

RE: svn commit: r746002 - in /maven/components/trunk: maven-core/src/main/java/org/apache/maven/plugin/ maven-embedder/src/main/java/org/apache/maven/embedder/ maven-project-builder/ maven-project-bui

Ok, I mean either enable it all the time, or get some reports or CI etc. -Original Message- From: Dennis Lundberg [mailto:denn...@apache.org] Sent: Friday, February 20, 2009 11:26 AM To: Maven Developers List Subject: Re: svn commit: r746002 - in /maven/components/trunk: maven-core/src/m

Re: svn commit: r746002 - in /maven/components/trunk: maven-core/src/main/java/org/apache/maven/plugin/ maven-embedder/src/main/java/org/apache/maven/embedder/ maven-project-builder/ maven-project-bui

We already have it in the Maven parent POM. When using the "reporting" profile you get a Checkstyle report for the current artifact. Brian E. Fox wrote: > Why don't we just hookup checkstyle to maven? > > -Original Message- > From: Hervé BOUTEMY [mailto:herve.bout...@free.fr] > Sent: Th

Re: pde build with maven

Maybe late but... I had the same problem. It was because I had different entries for the buildId in buildConfiguration/build.properties and the artifact-id in my pom.xml. Christopher Klewes wrote: > > Hi, i want to setup my rcp project with a maven build. so first i want > to build succesful

Re: settings security: --enc-passwd / --enc-master-passwd options

On 20/02/2009, at 10:19 PM, Brett Porter wrote: Hi, To make it a bit easier to remember, I added two options to the CLI for 2.1: --enc-master-passwd and --enc-passwd; which are equivalent to -m and -p on DefaultSecDispatcher. For consistency with other options, it takes the password as a

Re: maven-pdf-plugin ready for testing

*) I have to investigate the image warnings, it seems that some resources are not copied This was actually a bug in relative link resolution for figure sources, it's fixed and new snapshot deployed. -Lukas - To unsubs

settings security: --enc-passwd / --enc-master-passwd options

Hi, To make it a bit easier to remember, I added two options to the CLI for 2.1: --enc-master-passwd and --enc-passwd; which are equivalent to -m and -p on DefaultSecDispatcher. For consistency with other options, it takes the password as an option on the CLI rather than delegating to the

Re: maven-pdf-plugin ready for testing

Hi Wendy, First, thanks for testing! Wendy Smoak wrote: I initially got a build failure because the plugin uses _itself_ during the build. I commented that part out and jumped through some hoops building doxia and various parent poms, then it worked. The plugin is only used to build the pd