Re: Build failed in Jenkins: maven-plugins-ITs-m3-windows #187
Fantastic! Thanks for that.
Mark
On 11 June 2013 21:33, Robert Scholte rfscho...@apache.org wrote:
After 272 failing builds finally FIXED!
Jenkins build is back to normal : maven-plugins-ITs-m3-windows #273
Robert
Op Sun, 09 Jun 2013 13:39:56 +0200 schreef Robert Scholte
rfscho...@apache.org:
We're one step closer:
Infra has added 2 options to the list of JDKs on the build-server.
I've switched to JDK 1.5 and now the maven-javadoc-plugin succeeds.
The job was executed with the following JVM Options:
-Xmx768m
-XX:MaxPermSize=128m
should we change this? If yes, to what?
Robert
Op Sun, 12 May 2013 12:26:00 +0200 schreef Mark Hobson
markhob...@gmail.com:
Any ideas what the problem is with the Java installation on this
slave? This build has been failing for as long as I remember, and
every time it does it emails 18 people and counting.
The secondary problem is the Maven Dependency Plugin tests failing
with Java heap space, which then causes six other plugins to fail.
Can we increase the heap size for this job?
Thanks,
Mark
On 2 March 2013 15:34, Robert Scholte rfscho...@apache.org wrote:
I think I have to rephrase that. I just had a look at the logging. Now
it is
failing due to the following issue:
Caused by: java.io.IOException: The environment variable
JAVA_HOME=f:\hudson\tools\java\latest-1.5-64 doesn't exist or is not a
valid
directory.
at
org.apache.maven.plugin.javadoc.AbstractJavadocMojo.getJavadocExecutable(AbstractJavadocMojo.java:3526)
at
org.apache.maven.plugin.javadoc.AbstractJavadocMojo.executeReport(AbstractJavadocMojo.java:1872)
... 31 more
This is probably a symbolic link.
The related code looks like this:
//
--
// Try to find javadocExe from JAVA_HOME environment variable
//
--
if ( !javadocExe.exists() || !javadocExe.isFile() )
{
Properties env = CommandLineUtils.getSystemEnvVars();
String javaHome = env.getProperty( JAVA_HOME );
if ( StringUtils.isEmpty( javaHome ) )
{
throw new IOException( The environment variable
JAVA_HOME
is not correctly set. );
}
if ( ( !new File( javaHome ).getCanonicalFile().exists() )
|| (
new File( javaHome ).getCanonicalFile().isFile() ) )
{
throw new IOException(
The environment variable JAVA_HOME= + javaHome +
doesn't exist or is not a valid directory. );
}
javadocExe = new File( javaHome + File.separator + bin,
javadocCommand );
}
I always thought that the getCanonicalFile() should have resolved the
symbolic link, but it seems like I'm wrong here.
Robert
btw, Dennis, nice job on the changelog issue!
Op Sat, 02 Mar 2013 15:50:40 +0100 schreef Dennis Lundberg
denn...@apache.org:
AFAIK we only have one Windows slave. I think it would be better if we
asked on builds@a.o to get the Javadoc tool to be installed properly on
the existing slave.
On 2013-03-01 21:07, Robert Scholte wrote:
Is it possible to add a javadoc label to the Windows-systems which do
have javadoc installed properly and add a restriction to this job to
be
sure it is executed on the right slave?
Robert
Op Fri, 01 Mar 2013 18:14:03 +0100 schreef Apache Jenkins Server
jenk...@builds.apache.org:
See
https://builds.apache.org/job/maven-plugins-ITs-m3-windows/187/changes
Changes:
[andham] Some clean ups
--
[...truncated 10167 lines...]
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec
Running org.apache.maven.plugins.shade.mojo.RelativizePathTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.043
sec
Running org.apache.maven.plugins.shade.mojo.ShadeMojoTest
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.525
sec
Running
org.apache.maven.plugins.shade.relocation.SimpleRelocatorParameterTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.013
sec
Running org.apache.maven.plugins.shade.relocation.SimpleRelocatorTest
Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec
Running
org.apache.maven.plugins.shade.resource.ApacheLicenseResourceTransformerTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec
Running
org.apache.maven.plugins.shade.resource.ApacheNoticeResourceTransformerTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec
Running
org.apache.maven.plugins.shade.resource.AppendingTransformerTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec
Running
org.apache.maven.plugins.shade.resource.ComponentsXmlResourceTransformerTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time
Re: Build failed in Jenkins: maven-plugins-ITs-m3-windows #187
Any ideas what the problem is with the Java installation on this
slave? This build has been failing for as long as I remember, and
every time it does it emails 18 people and counting.
The secondary problem is the Maven Dependency Plugin tests failing
with Java heap space, which then causes six other plugins to fail.
Can we increase the heap size for this job?
Thanks,
Mark
On 2 March 2013 15:34, Robert Scholte rfscho...@apache.org wrote:
I think I have to rephrase that. I just had a look at the logging. Now it is
failing due to the following issue:
Caused by: java.io.IOException: The environment variable
JAVA_HOME=f:\hudson\tools\java\latest-1.5-64 doesn't exist or is not a valid
directory.
at
org.apache.maven.plugin.javadoc.AbstractJavadocMojo.getJavadocExecutable(AbstractJavadocMojo.java:3526)
at
org.apache.maven.plugin.javadoc.AbstractJavadocMojo.executeReport(AbstractJavadocMojo.java:1872)
... 31 more
This is probably a symbolic link.
The related code looks like this:
//
--
// Try to find javadocExe from JAVA_HOME environment variable
//
--
if ( !javadocExe.exists() || !javadocExe.isFile() )
{
Properties env = CommandLineUtils.getSystemEnvVars();
String javaHome = env.getProperty( JAVA_HOME );
if ( StringUtils.isEmpty( javaHome ) )
{
throw new IOException( The environment variable JAVA_HOME
is not correctly set. );
}
if ( ( !new File( javaHome ).getCanonicalFile().exists() ) || (
new File( javaHome ).getCanonicalFile().isFile() ) )
{
throw new IOException(
The environment variable JAVA_HOME= + javaHome +
doesn't exist or is not a valid directory. );
}
javadocExe = new File( javaHome + File.separator + bin,
javadocCommand );
}
I always thought that the getCanonicalFile() should have resolved the
symbolic link, but it seems like I'm wrong here.
Robert
btw, Dennis, nice job on the changelog issue!
Op Sat, 02 Mar 2013 15:50:40 +0100 schreef Dennis Lundberg
denn...@apache.org:
AFAIK we only have one Windows slave. I think it would be better if we
asked on builds@a.o to get the Javadoc tool to be installed properly on
the existing slave.
On 2013-03-01 21:07, Robert Scholte wrote:
Is it possible to add a javadoc label to the Windows-systems which do
have javadoc installed properly and add a restriction to this job to be
sure it is executed on the right slave?
Robert
Op Fri, 01 Mar 2013 18:14:03 +0100 schreef Apache Jenkins Server
jenk...@builds.apache.org:
See
https://builds.apache.org/job/maven-plugins-ITs-m3-windows/187/changes
Changes:
[andham] Some clean ups
--
[...truncated 10167 lines...]
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec
Running org.apache.maven.plugins.shade.mojo.RelativizePathTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.043
sec
Running org.apache.maven.plugins.shade.mojo.ShadeMojoTest
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.525
sec
Running
org.apache.maven.plugins.shade.relocation.SimpleRelocatorParameterTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.013
sec
Running org.apache.maven.plugins.shade.relocation.SimpleRelocatorTest
Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec
Running
org.apache.maven.plugins.shade.resource.ApacheLicenseResourceTransformerTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec
Running
org.apache.maven.plugins.shade.resource.ApacheNoticeResourceTransformerTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec
Running org.apache.maven.plugins.shade.resource.AppendingTransformerTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec
Running
org.apache.maven.plugins.shade.resource.ComponentsXmlResourceTransformerTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec
Running
org.apache.maven.plugins.shade.resource.XmlAppendingTransformerTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.013
sec
Results :
Tests run: 27, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ maven-shade-plugin
---
[INFO] Building jar:
F:\hudson\hudson-slave\workspace\maven-plugins-ITs-m3-windows\maven-shade-plugin\target\maven-shade-plugin-3.0-SNAPSHOT.jar
[INFO]
[INFO] --- maven-plugin-plugin:3.2:addPluginArtifactMetadata
(default-addPluginArtifactMetadata) @ maven-shade-plugin ---
[INFO]
[INFO] --- maven-jar-plugin:2.4:test-jar (default) @
maven-shade-plugin ---
[INFO] Building jar:
MNG-3092
Hi all, I see Jason's suggested MNG-3092 [1] for 3.1.0, which is great, but as the comments show this is a political hot potato. I'm happy to apply my original patch if that really is the consensus? Thanks, Mark [1] http://jira.codehaus.org/browse/MNG-3092 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: MNG-3092
Personally I'd like to see it adhere to the original specification. Whether that's optimal depends on what development process is being used, as reflected in the comments. Mark On 14 November 2012 21:44, Jason van Zyl ja...@tesla.io wrote: So what would you propose the optimal behaviour would be? On Nov 14, 2012, at 3:54 PM, Mark Hobson markhob...@gmail.com wrote: Hi all, I see Jason's suggested MNG-3092 [1] for 3.1.0, which is great, but as the comments show this is a political hot potato. I'm happy to apply my original patch if that really is the consensus? Thanks, Mark [1] http://jira.codehaus.org/browse/MNG-3092 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org Thanks, Jason -- Jason van Zyl Founder CTO, Sonatype Founder, Apache Maven http://twitter.com/jvanzyl - the course of true love never did run smooth ... -- Shakespeare - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: https://jira.codehaus.org/browse/MNG-1304
+1 Standardisation on version semantics is key to dependency management. Mark On 13 Nov 2012, at 20:38, Jason van Zyl ja...@tesla.io wrote: This is a long-standing issue, but I think a document and standard has emerged that I think is reasonable. How do people feel about trying to adhere to: http://semver.org and moving toward using this as our standard versioning documentation? Thanks, Jason -- Jason van Zyl Founder CTO, Sonatype Founder, Apache Maven http://twitter.com/jvanzyl - To do two things at once is to do neither. -- Publilius Syrus, Roman slave, first century B.C. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[ANN] Maven SCM 1.8.1 Released
The Maven team is pleased to announce the release of Maven SCM, version 1.8.1. Maven SCM provides a common API for doing SCM operations. http://maven.apache.org/scm/ Release Notes - Maven SCM - Version 1.8.1 Bug: * [SCM-696] - SVN tagging fails with svn+ssh://username@host URL * [SCM-697] - git add fail on windows when a lot of files to add New Feature: * [SCM-694] - git checkin command doesn't work with renamed files Task: * [SCM-698] - Migrate from plexus-maven-plugin to plexus-component-metadata Enjoy, -The Maven team - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[ANN] Maven SCM Publish Plugin 1.0-beta-2 Released
The Maven team is pleased to announce the release of the Maven SCM Publish Plugin, version 1.0-beta-2. This plugin allows Maven websites to be published to any supported SCM. http://maven.apache.org/plugins/maven-scm-publish-plugin/ You should specify the version in your project's plugin configuration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-scm-publish-plugin/artifactId version1.0-beta-2/version /plugin Release Notes - Maven SCM Publish Plugin - Version 1.0-beta-2 Bug: * [MSCMPUB-2] - publish-scm can fail with many files on windows. Task: * [MSCMPUB-1] - remove obsolete prepare and publish goals Enjoy, -The Maven team - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Deploying maven-scm site
I'd be happy to temporarily not use keys and put my password in
settings.xml, although I still get prompted even then. What do others
do when deploying multi-module sites?
Thanks,
Mark
On 6 November 2012 23:00, Chris Graham chrisgw...@gmail.com wrote:
Your key is being refused (for a variety of reasons). That's been the case
for me when I've been prompted for passwords when using keys. Good luck in
finding out why. :-)
-Chris
Sent from my iPhone
On 07/11/2012, at 9:34 AM, Mark Hobson markhob...@gmail.com wrote:
Hi,
I'm trying to deploy the maven-scm-1.8.1 site but am getting prompted
for a password for every module.
As per [1] my settings.xml contains:
server
idapache.website/id
usernamemarkh/username
privateKey${user.home}/.ssh/id_rsa/privateKey
/server
I'm running Maven 3.0.4 under Cygwin with the following from [2]:
mvn site-deploy -Preporting -DstagingRepositoryId=apache.website
Which prompts me for a password as follows:
[INFO] --- maven-site-plugin:3.1:deploy (default-deploy) @ maven-scm ---
[INFO] Parent project loaded from repository:
org.apache.maven:maven-parent:pom:22
[INFO] Parent project loaded from repository: org.apache:apache:pom:11
[INFO] Parent project loaded from repository:
org.apache.maven:maven-parent:pom:22
[INFO] Parent project loaded from repository: org.apache:apache:pom:11
Using private key: C:\Users\mark\.ssh\id_rsa
Password:
Any idea what I'm missing?
Thanks,
Mark
[1] http://www.apache.org/dev/publishing-maven-artifacts.html#dev-env
[2] http://maven.apache.org/developers/release/maven-shared-release.html
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Re: Deploying maven-scm site
Hi Benson,
I can ssh and scp to people.apache.org by entering my passphrase.
I've even tried using ssh-add to remove the passphrase prompt but it
still resorts to a password. What takes the -d switch you mention?
My settings.xml looks similar, but uncommenting password still
doesn't stop the prompt.
Thanks,
Mark
On 7 November 2012 13:58, Benson Margulies bimargul...@gmail.com wrote:
Can you do a plain ssh to the target, and/or an SCP? If not, use -d and see
what the fuss is about. If so, then I suspect that you have the wrong
settings.xml.
Mine looks like:
server
idapache.website/id
usernamebimargulies/username
!--
passworduncomment and put in password to give up on ssh./password
--
privateKey/users/benson/.ssh/id_rsa/privateKey
/server
On Wed, Nov 7, 2012 at 8:55 AM, Mark Hobson markhob...@gmail.com wrote:
I'd be happy to temporarily not use keys and put my password in
settings.xml, although I still get prompted even then. What do others
do when deploying multi-module sites?
Thanks,
Mark
On 6 November 2012 23:00, Chris Graham chrisgw...@gmail.com wrote:
Your key is being refused (for a variety of reasons). That's been the
case for me when I've been prompted for passwords when using keys. Good
luck in finding out why. :-)
-Chris
Sent from my iPhone
On 07/11/2012, at 9:34 AM, Mark Hobson markhob...@gmail.com wrote:
Hi,
I'm trying to deploy the maven-scm-1.8.1 site but am getting prompted
for a password for every module.
As per [1] my settings.xml contains:
server
idapache.website/id
usernamemarkh/username
privateKey${user.home}/.ssh/id_rsa/privateKey
/server
I'm running Maven 3.0.4 under Cygwin with the following from [2]:
mvn site-deploy -Preporting -DstagingRepositoryId=apache.website
Which prompts me for a password as follows:
[INFO] --- maven-site-plugin:3.1:deploy (default-deploy) @ maven-scm
---
[INFO] Parent project loaded from repository:
org.apache.maven:maven-parent:pom:22
[INFO] Parent project loaded from repository:
org.apache:apache:pom:11
[INFO] Parent project loaded from repository:
org.apache.maven:maven-parent:pom:22
[INFO] Parent project loaded from repository:
org.apache:apache:pom:11
Using private key: C:\Users\mark\.ssh\id_rsa
Password:
Any idea what I'm missing?
Thanks,
Mark
[1] http://www.apache.org/dev/publishing-maven-artifacts.html#dev-env
[2]
http://maven.apache.org/developers/release/maven-shared-release.html
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Re: Deploying maven-scm site
I do mean passphrase. My public key is on people.apache.org.
Adding password to settings.xml results in:
[INFO] --- maven-site-plugin:3.1:deploy (default-deploy) @ maven-scm ---
[INFO] Parent project loaded from repository:
org.apache.maven:maven-parent:pom:22
[INFO] Parent project loaded from repository: org.apache:apache:pom:11
[INFO] Parent project loaded from repository:
org.apache.maven:maven-parent:pom:22
[INFO] Parent project loaded from repository: org.apache:apache:pom:11
Keyboard interactive required, supplied password is ignored
Password:
Not sure if I've got the patience to enter my password when prompted
for 34 modules! It doesn't help that it seems to timeout if it's not
entered promptly.
Thanks,
Mark
On 7 November 2012 19:45, Benson Margulies bimargul...@gmail.com wrote:
Do you really mean passphrase or password? Have you added your public key
to your authorized_keys on people?
On Wed, Nov 7, 2012 at 2:21 PM, Mark Hobson markhob...@gmail.com wrote:
Hi Benson,
I can ssh and scp to people.apache.org by entering my passphrase.
I've even tried using ssh-add to remove the passphrase prompt but it
still resorts to a password. What takes the -d switch you mention?
My settings.xml looks similar, but uncommenting password still
doesn't stop the prompt.
Thanks,
Mark
On 7 November 2012 13:58, Benson Margulies bimargul...@gmail.com wrote:
Can you do a plain ssh to the target, and/or an SCP? If not, use -d and
see
what the fuss is about. If so, then I suspect that you have the wrong
settings.xml.
Mine looks like:
server
idapache.website/id
usernamebimargulies/username
!--
passworduncomment and put in password to give up on
ssh./password
--
privateKey/users/benson/.ssh/id_rsa/privateKey
/server
On Wed, Nov 7, 2012 at 8:55 AM, Mark Hobson markhob...@gmail.com
wrote:
I'd be happy to temporarily not use keys and put my password in
settings.xml, although I still get prompted even then. What do others
do when deploying multi-module sites?
Thanks,
Mark
On 6 November 2012 23:00, Chris Graham chrisgw...@gmail.com wrote:
Your key is being refused (for a variety of reasons). That's been the
case for me when I've been prompted for passwords when using keys. Good
luck in finding out why. :-)
-Chris
Sent from my iPhone
On 07/11/2012, at 9:34 AM, Mark Hobson markhob...@gmail.com wrote:
Hi,
I'm trying to deploy the maven-scm-1.8.1 site but am getting prompted
for a password for every module.
As per [1] my settings.xml contains:
server
idapache.website/id
usernamemarkh/username
privateKey${user.home}/.ssh/id_rsa/privateKey
/server
I'm running Maven 3.0.4 under Cygwin with the following from [2]:
mvn site-deploy -Preporting -DstagingRepositoryId=apache.website
Which prompts me for a password as follows:
[INFO] --- maven-site-plugin:3.1:deploy (default-deploy) @
maven-scm
---
[INFO] Parent project loaded from repository:
org.apache.maven:maven-parent:pom:22
[INFO] Parent project loaded from repository:
org.apache:apache:pom:11
[INFO] Parent project loaded from repository:
org.apache.maven:maven-parent:pom:22
[INFO] Parent project loaded from repository:
org.apache:apache:pom:11
Using private key: C:\Users\mark\.ssh\id_rsa
Password:
Any idea what I'm missing?
Thanks,
Mark
[1]
http://www.apache.org/dev/publishing-maven-artifacts.html#dev-env
[2]
http://maven.apache.org/developers/release/maven-shared-release.html
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Re: Deploying maven-scm site
Goodness, I've just tried adding passphrase to settings.xml and so
far it seems to be happily scp'ing autonomously. I'm sure I tried
this the other night..
Thanks for listening,
Mark
On 7 November 2012 19:51, Mark Hobson markhob...@gmail.com wrote:
I do mean passphrase. My public key is on people.apache.org.
Adding password to settings.xml results in:
[INFO] --- maven-site-plugin:3.1:deploy (default-deploy) @ maven-scm ---
[INFO] Parent project loaded from repository:
org.apache.maven:maven-parent:pom:22
[INFO] Parent project loaded from repository: org.apache:apache:pom:11
[INFO] Parent project loaded from repository:
org.apache.maven:maven-parent:pom:22
[INFO] Parent project loaded from repository: org.apache:apache:pom:11
Keyboard interactive required, supplied password is ignored
Password:
Not sure if I've got the patience to enter my password when prompted
for 34 modules! It doesn't help that it seems to timeout if it's not
entered promptly.
Thanks,
Mark
On 7 November 2012 19:45, Benson Margulies bimargul...@gmail.com wrote:
Do you really mean passphrase or password? Have you added your public key
to your authorized_keys on people?
On Wed, Nov 7, 2012 at 2:21 PM, Mark Hobson markhob...@gmail.com wrote:
Hi Benson,
I can ssh and scp to people.apache.org by entering my passphrase.
I've even tried using ssh-add to remove the passphrase prompt but it
still resorts to a password. What takes the -d switch you mention?
My settings.xml looks similar, but uncommenting password still
doesn't stop the prompt.
Thanks,
Mark
On 7 November 2012 13:58, Benson Margulies bimargul...@gmail.com wrote:
Can you do a plain ssh to the target, and/or an SCP? If not, use -d and
see
what the fuss is about. If so, then I suspect that you have the wrong
settings.xml.
Mine looks like:
server
idapache.website/id
usernamebimargulies/username
!--
passworduncomment and put in password to give up on
ssh./password
--
privateKey/users/benson/.ssh/id_rsa/privateKey
/server
On Wed, Nov 7, 2012 at 8:55 AM, Mark Hobson markhob...@gmail.com
wrote:
I'd be happy to temporarily not use keys and put my password in
settings.xml, although I still get prompted even then. What do others
do when deploying multi-module sites?
Thanks,
Mark
On 6 November 2012 23:00, Chris Graham chrisgw...@gmail.com wrote:
Your key is being refused (for a variety of reasons). That's been the
case for me when I've been prompted for passwords when using keys. Good
luck in finding out why. :-)
-Chris
Sent from my iPhone
On 07/11/2012, at 9:34 AM, Mark Hobson markhob...@gmail.com wrote:
Hi,
I'm trying to deploy the maven-scm-1.8.1 site but am getting prompted
for a password for every module.
As per [1] my settings.xml contains:
server
idapache.website/id
usernamemarkh/username
privateKey${user.home}/.ssh/id_rsa/privateKey
/server
I'm running Maven 3.0.4 under Cygwin with the following from [2]:
mvn site-deploy -Preporting -DstagingRepositoryId=apache.website
Which prompts me for a password as follows:
[INFO] --- maven-site-plugin:3.1:deploy (default-deploy) @
maven-scm
---
[INFO] Parent project loaded from repository:
org.apache.maven:maven-parent:pom:22
[INFO] Parent project loaded from repository:
org.apache:apache:pom:11
[INFO] Parent project loaded from repository:
org.apache.maven:maven-parent:pom:22
[INFO] Parent project loaded from repository:
org.apache:apache:pom:11
Using private key: C:\Users\mark\.ssh\id_rsa
Password:
Any idea what I'm missing?
Thanks,
Mark
[1]
http://www.apache.org/dev/publishing-maven-artifacts.html#dev-env
[2]
http://maven.apache.org/developers/release/maven-shared-release.html
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Deploying maven-scm site
Hi,
I'm trying to deploy the maven-scm-1.8.1 site but am getting prompted
for a password for every module.
As per [1] my settings.xml contains:
server
idapache.website/id
usernamemarkh/username
privateKey${user.home}/.ssh/id_rsa/privateKey
/server
I'm running Maven 3.0.4 under Cygwin with the following from [2]:
mvn site-deploy -Preporting -DstagingRepositoryId=apache.website
Which prompts me for a password as follows:
[INFO] --- maven-site-plugin:3.1:deploy (default-deploy) @ maven-scm ---
[INFO] Parent project loaded from repository:
org.apache.maven:maven-parent:pom:22
[INFO] Parent project loaded from repository: org.apache:apache:pom:11
[INFO] Parent project loaded from repository:
org.apache.maven:maven-parent:pom:22
[INFO] Parent project loaded from repository: org.apache:apache:pom:11
Using private key: C:\Users\mark\.ssh\id_rsa
Password:
Any idea what I'm missing?
Thanks,
Mark
[1] http://www.apache.org/dev/publishing-maven-artifacts.html#dev-env
[2] http://maven.apache.org/developers/release/maven-shared-release.html
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
[RESULT] [VOTE] Release Maven SCM version 1.8.1
Hi, The vote has passed with the following result : +1 (binding): Mark Hobson, Herve Boutemy, Mark Struberg, Olivier Lamy +1 (non binding): N/A I will promote the artifacts to the central repo. Mark - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[RESULT] [VOTE] Release Maven SCM Publish Plugin version 1.0-beta-2
Hi, The vote has passed with the following result : +1 (binding): Mark Hobson, Herve Boutemy, Mark Struberg, Olivier Lamy +0 (binding): Robert Scholte +1 (non binding): N/A I will promote the artifacts to the central repo. Mark - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven SCM Publish Plugin version 1.0-beta-2
I'd also like to see that fixed as I'm using Windows too and had to perform the release under Linux. Ironically this release is to fix a bug under Windows.. Mark On 2 November 2012 15:22, Robert Scholte rfscho...@apache.org wrote: As Windows user I must give a +0 since the unit-tests fail due to MSCMPUB-3[1] I was a bit too late to fix it on the SCM project, because it moved to GIT. I'll accept this issue for this beta release, won't do that for a final release. -Robert [1] https://jira.codehaus.org/browse/MSCMPUB-3 Op Fri, 02 Nov 2012 10:39:03 +0100 schreef Mark Struberg strub...@yahoo.de: +1 LieGrue, strub - Original Message - From: Mark Hobson markhob...@gmail.com To: Maven Developers List dev@maven.apache.org Cc: Sent: Thursday, November 1, 2012 11:04 PM Subject: [VOTE] Release Maven SCM Publish Plugin version 1.0-beta-2 Hi, Note that this release is dependent upon the maven-scm-1.8.1 vote currently taking place. We solved 2 issues:http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=12730styleName=Htmlversion=18939 There are still a couple of issues left in JIRA:http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=12730status=1 Staging repo:https://repository.apache.org/content/repositories/maven-006/https://repository.apache.org/content/repositories/maven-006/org/apache/maven/plugins/maven-scm-publish-plugin/1.0-beta-2/maven-scm-publish-plugin-1.0-beta-2-source-release.zip Staging site:http://maven.apache.org/plugins/maven-scm-publish-plugin-1.0-beta-2/maven-scm-publish-plugin (wait for sync) Guide to testing staged releases:http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 Here's my +1. Thanks, Mark - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[VOTE] Release Maven SCM version 1.8.1
Hi, We solved 4 issues:http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10527styleName=Htmlversion=18930 There are still plenty of issues left in JIRA:http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=10527status=1 Staging repo:https://repository.apache.org/content/repositories/maven-005/ https://repository.apache.org/content/repositories/maven-005/org/apache/maven/scm/maven-scm/1.8.1/maven-scm-1.8.1-source-release.zip Staging site:http://maven.apache.org/scm-1.8.1 (wait for sync) Guide to testing staged releases:http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 Here's my +1. Thanks, Mark
[VOTE] Release Maven SCM Publish Plugin version 1.0-beta-2
Hi, Note that this release is dependent upon the maven-scm-1.8.1 vote currently taking place. We solved 2 issues:http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=12730styleName=Htmlversion=18939 There are still a couple of issues left in JIRA:http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=12730status=1 Staging repo:https://repository.apache.org/content/repositories/maven-006/https://repository.apache.org/content/repositories/maven-006/org/apache/maven/plugins/maven-scm-publish-plugin/1.0-beta-2/maven-scm-publish-plugin-1.0-beta-2-source-release.zip Staging site:http://maven.apache.org/plugins/maven-scm-publish-plugin-1.0-beta-2/maven-scm-publish-plugin (wait for sync) Guide to testing staged releases:http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 Here's my +1. Thanks, Mark
Re: Releasing maven-scm and maven-scm-publish-plugin
Strange. I've checked the maven-scm released artifacts and they seem okay, thanks for the heads up though. Mark On 31 October 2012 20:38, Robert Scholte rfscho...@apache.org wrote: Hi Mark, yes, I meant SCM-698. It's really weird what happened, because I would expect tests to fail if there's no components.xml. It happened to me only once, during the most critical moment: release:perform. Just double check your release, that's all I'm saying. Robert Op Tue, 30 Oct 2012 23:50:39 +0100 schreef Mark Hobson markhob...@gmail.com: Hi Robert, Is this in reference to SCM-698 which switched from plexus-maven-plugin to plexus-component-metadata? The latter plugin still correctly generates the plexus components.xml files for maven-scm. Perhaps the maven-invoker problem is specific to plexus annotations which I don't believe we're using yet. Thanks, Mark On 30 October 2012 22:11, Robert Scholte rfscho...@apache.org wrote: Mark, FYI, it seems like there's an issue with the plexus-component-metadata. My latest release is of the maven-invoker is missing the plexus/components.xml so I'll have to re-release a new one as soon as I know what the issue is. Running a package twice does generate the file. I assume it's this project: https://github.com/sonatype/plexus-containers but I still haven't found the right sources on my system Robert Op Tue, 30 Oct 2012 22:41:21 +0100 schreef Mark Hobson markhob...@gmail.com: Sounds reasonable to me, I'll release it as 1.8.1. Mark On 27 October 2012 23:28, Chris Graham chrisgw...@gmail.com wrote: 1.9 or 1.8.1? It doesn't appear to be a major change. -Chris Sent from my iPhone On 27/10/2012, at 11:31 PM, Mark Hobson markhob...@gmail.com wrote: On 26 October 2012 21:14, Olivier Lamy ol...@apache.org wrote: 2012/10/26 Mark Hobson markhob...@gmail.com: Any objections before I start a vote? Nope Great, I'll get the ball rolling. Also, what is the convention for running maven-scm ITs? I'm guessing it's done manually prior to releasing. Does it require all the SCM tools to be installed locally or can we just trust CI? Some are not available for free. Perso I usually run tck for git,svn and cvs (-Ptck-git,tck-svn,tck-cvs) Thanks to care of this release ! Sounds good, no probs! Mark - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Releasing maven-scm and maven-scm-publish-plugin
Sounds reasonable to me, I'll release it as 1.8.1. Mark On 27 October 2012 23:28, Chris Graham chrisgw...@gmail.com wrote: 1.9 or 1.8.1? It doesn't appear to be a major change. -Chris Sent from my iPhone On 27/10/2012, at 11:31 PM, Mark Hobson markhob...@gmail.com wrote: On 26 October 2012 21:14, Olivier Lamy ol...@apache.org wrote: 2012/10/26 Mark Hobson markhob...@gmail.com: Any objections before I start a vote? Nope Great, I'll get the ball rolling. Also, what is the convention for running maven-scm ITs? I'm guessing it's done manually prior to releasing. Does it require all the SCM tools to be installed locally or can we just trust CI? Some are not available for free. Perso I usually run tck for git,svn and cvs (-Ptck-git,tck-svn,tck-cvs) Thanks to care of this release ! Sounds good, no probs! Mark - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
GPG Keys
Hi, I'm trying to update the /dist/maven/KEYS file on people.apache.org as described here: https://svn.apache.org/repos/asf/maven/project/KEYS It's owned by the svnwc user and I don't appear to have permissions to overwrite it. Am I missing something here? Thanks, Mark - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Releasing maven-scm and maven-scm-publish-plugin
Hi Robert, Is this in reference to SCM-698 which switched from plexus-maven-plugin to plexus-component-metadata? The latter plugin still correctly generates the plexus components.xml files for maven-scm. Perhaps the maven-invoker problem is specific to plexus annotations which I don't believe we're using yet. Thanks, Mark On 30 October 2012 22:11, Robert Scholte rfscho...@apache.org wrote: Mark, FYI, it seems like there's an issue with the plexus-component-metadata. My latest release is of the maven-invoker is missing the plexus/components.xml so I'll have to re-release a new one as soon as I know what the issue is. Running a package twice does generate the file. I assume it's this project: https://github.com/sonatype/plexus-containers but I still haven't found the right sources on my system Robert Op Tue, 30 Oct 2012 22:41:21 +0100 schreef Mark Hobson markhob...@gmail.com: Sounds reasonable to me, I'll release it as 1.8.1. Mark On 27 October 2012 23:28, Chris Graham chrisgw...@gmail.com wrote: 1.9 or 1.8.1? It doesn't appear to be a major change. -Chris Sent from my iPhone On 27/10/2012, at 11:31 PM, Mark Hobson markhob...@gmail.com wrote: On 26 October 2012 21:14, Olivier Lamy ol...@apache.org wrote: 2012/10/26 Mark Hobson markhob...@gmail.com: Any objections before I start a vote? Nope Great, I'll get the ball rolling. Also, what is the convention for running maven-scm ITs? I'm guessing it's done manually prior to releasing. Does it require all the SCM tools to be installed locally or can we just trust CI? Some are not available for free. Perso I usually run tck for git,svn and cvs (-Ptck-git,tck-svn,tck-cvs) Thanks to care of this release ! Sounds good, no probs! Mark - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: GPG Keys
That worked, thanks Olivier. Mark On 30 October 2012 22:53, Olivier Lamy ol...@apache.org wrote: I missed to update instructions here when we moved to svnpubsub for dist. Now instrusctions up2date. The file to update is located here https://dist.apache.org/repos/dist/release/maven/ 2012/10/30 Mark Hobson markhob...@gmail.com: Hi, I'm trying to update the /dist/maven/KEYS file on people.apache.org as described here: https://svn.apache.org/repos/asf/maven/project/KEYS It's owned by the svnwc user and I don't appear to have permissions to overwrite it. Am I missing something here? Thanks, Mark - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Releasing maven-scm and maven-scm-publish-plugin
On 26 October 2012 21:14, Olivier Lamy ol...@apache.org wrote: 2012/10/26 Mark Hobson markhob...@gmail.com: Any objections before I start a vote? Nope Great, I'll get the ball rolling. Also, what is the convention for running maven-scm ITs? I'm guessing it's done manually prior to releasing. Does it require all the SCM tools to be installed locally or can we just trust CI? Some are not available for free. Perso I usually run tck for git,svn and cvs (-Ptck-git,tck-svn,tck-cvs) Thanks to care of this release ! Sounds good, no probs! Mark - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Releasing maven-scm and maven-scm-publish-plugin
Hi, I'd like to release maven-scm-publish-plugin 1.0-beta-2 for the MSCMPUB-2 fix. This issue is in turn fixed by SCM-697 so I'll also need to release maven-scm 1.9. The remaining issue scheduled for 1.9 is SCM-435 which I can move to 1.10 instead. Any objections before I start a vote? Also, what is the convention for running maven-scm ITs? I'm guessing it's done manually prior to releasing. Does it require all the SCM tools to be installed locally or can we just trust CI? Thanks, Mark - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven Runtime version 1.0-alpha-3
Good spot Tony, I'll fix the links. Shall I re-release the project or amend the tag? I'd rather re-release but do we need to vote for 72hrs again? Thanks, Mark On 28 May 2012 09:46, Tony Chemit che...@codelutin.com wrote: On Tue, 22 May 2012 13:29:48 +0100 Mark Hobson ma...@apache.org wrote: Hi, This release adds Maven3 support. +0 (non-binding) there is some broken links on main page. Use the ./xxx.html pattern to fix this Perharps this can be done in released tag and then site redeployed ? If so then +1 ! (:)) thanks, tony. We solved 2 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11761version=15963 There are no issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truejqlQuery=project+%3D+MSHARED+AND+component+%3D+maven-runtime+AND+status+%3D+Open Staging repo: https://repository.apache.org/content/repositories/maven-115/ https://repository.apache.org/content/repositories/maven-115/org/apache/maven/shared/maven-runtime/1.0-alpha-3/maven-runtime-1.0-alpha-3-source-release.zip Staging site: http://maven.apache.org/shared/maven-runtime-1.0-alpha-3/ (once synced) Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 Thanks, Mark - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Tony Chemit tél: +33 (0) 2 40 50 29 28 email: che...@codelutin.com http://www.codelutin.com - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven Runtime version 1.0-alpha-3
Sure, will do thanks. Mark On 28 May 2012 10:32, Hervé BOUTEMY herve.bout...@free.fr wrote: it's only the documentation: just fix your local checkout to publish content that will be ok and of course, check-in for future releases :) Regards, Hervé Le lundi 28 mai 2012 10:29:09 Mark Hobson a écrit : Good spot Tony, I'll fix the links. Shall I re-release the project or amend the tag? I'd rather re-release but do we need to vote for 72hrs again? Thanks, Mark On 28 May 2012 09:46, Tony Chemit che...@codelutin.com wrote: On Tue, 22 May 2012 13:29:48 +0100 Mark Hobson ma...@apache.org wrote: Hi, This release adds Maven3 support. +0 (non-binding) there is some broken links on main page. Use the ./xxx.html pattern to fix this Perharps this can be done in released tag and then site redeployed ? If so then +1 ! (:)) thanks, tony. We solved 2 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11761version= 15963 There are no issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truejqlQuery=p roject+%3D+MSHARED+AND+component+%3D+maven-runtime+AND+status+%3D+Open Staging repo: https://repository.apache.org/content/repositories/maven-115/ https://repository.apache.org/content/repositories/maven-115/org/apache/m aven/shared/maven-runtime/1.0-alpha-3/maven-runtime-1.0-alpha-3-source-re lease.zip Staging site: http://maven.apache.org/shared/maven-runtime-1.0-alpha-3/ (once synced) Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 Thanks, Mark - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Tony Chemit tél: +33 (0) 2 40 50 29 28 email: che...@codelutin.com http://www.codelutin.com - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[RESULT] [VOTE] Release Maven Runtime version 1.0-alpha-3
Hi, The vote has passed with the following result : +1 (binding): Olivier Lamy, Hervé BOUTEMY, Stephen Connolly +1 (non binding): Tony Chemit I will promote the artifacts to the central repo. Thanks, Mark - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[ANN] Maven Runtime 1.0-alpha-3 Released
The Maven team is pleased to announce the release of the Maven Runtime, version 1.0-alpha-3 Maven Runtime allows introspection of Maven project metadata at runtime. Basic artifact information or full Maven project metadata can be obtained for all projects within a given class loader, optionally sorted into dependency order, and also for a given class within a project. http://maven.apache.org/shared/maven-runtime/ You should specify the version in your project's dependency configuration: dependency groupIdorg.apache.maven.shared/groupId artifactIdmaven-runtime/artifactId version1.0-alpha-3/version /dependency Release Notes - Maven Runtime - Version 1.0-alpha-3 Bug * [MSHARED-165] Mediate dependency versions for stricter Maven3 ProjectSorter Improvement * [MSHARED-227] Upgrade dependencies to Maven3 Enjoy, -The Maven team - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Board report request
Hi, Could a PMC add Maven Runtime 1.0-alpha-3 to the next board report please? Thanks, Mark - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Board report request
Thanks. On 28 May 2012 13:40, Olivier Lamy ol...@apache.org wrote: done 2012/5/28 Mark Hobson ma...@apache.org: Hi, Could a PMC add Maven Runtime 1.0-alpha-3 to the next board report please? Thanks, Mark - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven Release Plugin version 2.3.1
Vote is nearing completion and need one more binding vote, anyone? Thanks, Mark On 22 May 2012 20:48, Olivier Lamy ol...@apache.org wrote: +1 2012/5/22 Mark Hobson ma...@apache.org: Hi, We solved 3 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11144styleName=Htmlversion=18526 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11144status=1 Staging repo: https://repository.apache.org/content/repositories/maven-113/ https://repository.apache.org/content/repositories/maven-113/org/apache/maven/release/maven-release/2.3.1/maven-release-2.3.1-source-release.zip Staging site: http://maven.apache.org/plugins/maven-release-plugin-2.3.1/ (once synced) Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 Thanks, Mark - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven Runtime version 1.0-alpha-3
Vote is nearing completion and need one more binding vote, anyone? Thanks, Mark On 24 May 2012 21:01, Hervé BOUTEMY herve.bout...@free.fr wrote: +1 Hervé Le mardi 22 mai 2012 13:29:48 Mark Hobson a écrit : Hi, This release adds Maven3 support. We solved 2 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11761version=159 63 There are no issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truejqlQuery=proj ect+%3D+MSHARED+AND+component+%3D+maven-runtime+AND+status+%3D+Open Staging repo: https://repository.apache.org/content/repositories/maven-115/ https://repository.apache.org/content/repositories/maven-115/org/apache/mave n/shared/maven-runtime/1.0-alpha-3/maven-runtime-1.0-alpha-3-source-release. zip Staging site: http://maven.apache.org/shared/maven-runtime-1.0-alpha-3/ (once synced) Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 Thanks, Mark - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[RESULT] [VOTE] Release Maven Release Plugin version 2.3.1
Hi, The vote has passed with the following result : +1 (binding): Robert Scholte, Olivier Lamy, Benson Margulies +1 (non binding): Mark Hobson, Tony Chemit, abhijith tn I will promote the artifacts to the central repo. Thanks, Mark - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Board report request
Hi, Could a PMC add Maven Release Plugin 2.3.1 to the next board report please? Thanks, Mark - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Board report request
Thanks Olivier. On 25 May 2012 15:40, Olivier Lamy ol...@apache.org wrote: done. 2012/5/25 Mark Hobson ma...@apache.org: Hi, Could a PMC add Maven Release Plugin 2.3.1 to the next board report please? Thanks, Mark - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[ANN] Maven Release Plugin 2.3.1 Released
The Maven team is pleased to announce the release of the Maven Release Plugin, version 2.3.1 This plugin is used to release a project with Maven, saving a lot of repetitive, manual work. Releasing a project is made in two steps: prepare and perform. http://maven.apache.org/plugins/maven-release-plugin/ You should specify the version in your project's plugin configuration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-release-plugin/artifactId version2.3.1/version /plugin Release Notes - Maven 2.x Release Plugin - Version 2.3.1 Bug * [MRELEASE-757] - cannot perform a release with another pom then pom.xml * [MRELEASE-758] - [regression] release:perform no longer removes release.properties * [MRELEASE-759] - default excludes are not recognized by Jazz Enjoy, -The Maven team - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven Runtime version 1.0-alpha-3
Good spot thanks, done. I wrongly assumed that the permissions would be correctly set since maven-release-plugin's were. Cheers, Mark On 23 May 2012 16:03, Olivier Lamy ol...@apache.org wrote: Mark, Can you fix file permissions for site part ? olamy@minotaur:~$ ls -lrt /www/maven.apache.org/shared/maven-runtime-1.0-alpha-3 total 0 ls: /www/maven.apache.org/shared/maven-runtime-1.0-alpha-3: Permission denied Will prevent olamy@minotaur:~$ curl -I http://maven.apache.org/shared/maven-runtime-1.0-alpha-3 HTTP/1.1 403 Forbidden 2012/5/22 Olivier Lamy ol...@apache.org: +1 2012/5/22 Mark Hobson ma...@apache.org: Hi, This release adds Maven3 support. We solved 2 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11761version=15963 There are no issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truejqlQuery=project+%3D+MSHARED+AND+component+%3D+maven-runtime+AND+status+%3D+Open Staging repo: https://repository.apache.org/content/repositories/maven-115/ https://repository.apache.org/content/repositories/maven-115/org/apache/maven/shared/maven-runtime/1.0-alpha-3/maven-runtime-1.0-alpha-3-source-release.zip Staging site: http://maven.apache.org/shared/maven-runtime-1.0-alpha-3/ (once synced) Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 Thanks, Mark - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
JIRA spam
Hi, This guy looks like spam if anyone wants to delete him? https://jira.codehaus.org/secure/ViewProfile.jspa?name=hendy Cheers, Mark - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[VOTE] Release Maven Release Plugin version 2.3.1
Hi, We solved 3 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11144styleName=Htmlversion=18526 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11144status=1 Staging repo: https://repository.apache.org/content/repositories/maven-113/ https://repository.apache.org/content/repositories/maven-113/org/apache/maven/release/maven-release/2.3.1/maven-release-2.3.1-source-release.zip Staging site: http://maven.apache.org/plugins/maven-release-plugin-2.3.1/ (once synced) Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 Thanks, Mark - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[VOTE] Release Maven Runtime version 1.0-alpha-3
Hi, This release adds Maven3 support. We solved 2 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11761version=15963 There are no issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truejqlQuery=project+%3D+MSHARED+AND+component+%3D+maven-runtime+AND+status+%3D+Open Staging repo: https://repository.apache.org/content/repositories/maven-115/ https://repository.apache.org/content/repositories/maven-115/org/apache/maven/shared/maven-runtime/1.0-alpha-3/maven-runtime-1.0-alpha-3-source-release.zip Staging site: http://maven.apache.org/shared/maven-runtime-1.0-alpha-3/ (once synced) Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 Thanks, Mark - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[RESULT] [VOTE] Release Maven Checkstyle Plugin version 2.8
Hi, The vote has passed with the following result : +1 (binding): Olivier Lamy, Stephen Connolly, Herve Boutemy +1 (non binding): Mark Struberg, Lukas Theussl I will promote the artifacts to the central repo. Cheers, Mark - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Add Maven Checkstyle Plugin 2.8 to board report
Hi, Could a PMC add the Maven Checkstyle Plugin 2.8 release to the next board report please? Cheers, Mark - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[ANN] Maven Checkstyle Plugin 2.8 Released
The Maven team is pleased to announce the release of the Maven Checkstyle Plugin, version 2.8 Generates a report on violations of code style and optionally fails the build if violations are detected. http://maven.apache.org/plugins/maven-checkstyle-plugin You should specify the version in your project's plugin configuration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-checkstyle-plugin/artifactId version2.8/version /plugin Release Notes - Maven Checkstyle Plugin - Version 2.8 Bug * [MCHECKSTYLE-159] Optional treeWalker.cacheFile property must not be required New Feature * [MCHECKSTYLE-62] Support aggregated reports in a multi-modules project Enjoy, -The Maven team - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Checkstyle plugin 2.8 release?
Great, thanks Olivier. Just back from holiday so apologies for the delay. I'll push the release now. Cheers, Mark On 16 October 2011 17:37, Olivier Lamy ol...@apache.org wrote: Mark, I don't know if you follow commits logs but you have karma back :-) Let me know if you want to push the release. 2011/10/14 Mark Hobson markhob...@gmail.com: That'd be great, thanks Olivier! Mark On 14 October 2011 08:26, Olivier Lamy ol...@apache.org wrote: Hello, I can probably do that around middle next week. Ping me if I miss :-) 2011/10/13 Mark Hobson markhob...@gmail.com: Hi, I need to use maven-checkstyle-plugin 2.7 for the checkstyle upgrade but am being blocked by MCHECKSTYLE-159. This is fixed in trunk and there are no further unresolved issues targeting 2.8, so any objections to performing a release? Next question is would someone mind doing it? :) I'm happy to but have appeared to have dropped into emeritus status again, so would have to get reinstated first. Cheers, Mark - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Olivier Lamy Talend : http://talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Olivier Lamy Talend : http://talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[VOTE] Release Maven Checkstyle Plugin version 2.8
Hi, We solved 2 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11127version=17520 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11127status=1 Staging repo: https://repository.apache.org/content/repositories/maven-091/ Staging site: http://maven.apache.org/plugins/maven-checkstyle-plugin-2.8/plugins/maven-checkstyle-plugin/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 Cheers, Mark - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Checkstyle plugin 2.8 release?
That'd be great, thanks Olivier! Mark On 14 October 2011 08:26, Olivier Lamy ol...@apache.org wrote: Hello, I can probably do that around middle next week. Ping me if I miss :-) 2011/10/13 Mark Hobson markhob...@gmail.com: Hi, I need to use maven-checkstyle-plugin 2.7 for the checkstyle upgrade but am being blocked by MCHECKSTYLE-159. This is fixed in trunk and there are no further unresolved issues targeting 2.8, so any objections to performing a release? Next question is would someone mind doing it? :) I'm happy to but have appeared to have dropped into emeritus status again, so would have to get reinstated first. Cheers, Mark - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Olivier Lamy Talend : http://talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Checkstyle plugin 2.8 release?
Hi, I need to use maven-checkstyle-plugin 2.7 for the checkstyle upgrade but am being blocked by MCHECKSTYLE-159. This is fixed in trunk and there are no further unresolved issues targeting 2.8, so any objections to performing a release? Next question is would someone mind doing it? :) I'm happy to but have appeared to have dropped into emeritus status again, so would have to get reinstated first. Cheers, Mark - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Auto apache version standard as an enforcer rule?
On 10 November 2010 14:02, Jesse Glick jesse.gl...@oracle.com wrote: The trouble with Javadoc pseudo-annotations is that they are unavailable in bytecode and thus invisible to a tool like sigtest. I don't know about Clirr. I suspect this particular set of Javadoc tags was designed with Eclipse editor hints in mind, which probably have access to HTML Javadoc of APIs if not the original source project, and possibly predated JSR 175. Furthermore, they will (ironically enough) not appear in the Javadoc HTML output by default, unlike a true @Documented annotation. The burden is on the library developer to remember to pass a complex argument such as -tag noimplement:t:Do Not Implement to the javadoc tool for each such annotation in use. Also consider other tools which might want to analyze this information - such as FindBugs, or a hypothetical annotation processor that verified that a @NoImplement interface was not in fact implemented except by authorized providers. I certainly agree that some JSR-175 annotations for these concepts would be best. I'd be surprised if the Eclipse folks haven't got this on their road map already, might be worth checking. Mark - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Auto apache version standard as an enforcer rule?
On 9 November 2010 16:30, Rex Hoffman r...@e-hoffman.org wrote: My thoughts exactly on the annotation ie. hosted in a generic context. The concern I have is the number of useful open source projects that expose interfaces that clients are not required to implement. Ultimately since this style of checking is primarily used by the devs of the project, I can have them define the annotation, and whether it marks an interface as client implements, or client does not implement. Those might not be the best names for the annotation, as it really would mean 'Client implements it and my code will break binary compatibility, by calling it at runtime. Note that Eclipse's PDE has Javadoc tags for these notions: http://help.eclipse.org/helios/index.jsp?topic=/org.eclipse.pde.doc.user/reference/api-tooling/api_javadoc_tags.htm Mark - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Auto apache version standard as an enforcer rule?
On 4 November 2010 18:28, Rex Hoffman r...@e-hoffman.org wrote: Seems reasonable, build a helper library to run clirr and analyze it's results, allow the clirr plugin to use it in it's existing manner, or by an enforcer rule. That fact that it's clirr under the hood of that enforcer rule will be completely abstracted. This will be a rule to enforce apache version standard, that happens to use clirr. I'll write a clean api for it's analysis provider (clirr). I know it'll be annoying, that's kinda the point. If your working on a 1.1-SNAPSHOT and create a backwards breaking change, you have messed up. The rule will tell the dev to correct the method, or bump the version number to 2.0-SNAPSHOT. The real danger is a dev not being aware that they have produced a backwards breaking change. Again, very helpful for apis. Given Brett's email today citing the desire for Configurable conflict resolution strategy - newest, oldest that satisfies Enforcer rule to lock down above Importance of specificity, not magic - break the build if conflicting versions, not try and solve it Be deterministic is maven's strength I think it's important we codify how maven wants devs to think about versions. Right now it a snapshot or release. The ranges have vague meaning at best, not knowing what version policy the project you depend on follows. If you want to hold of the release until Monday, I will commit to having it done and tested by then?? I think having the dependency-convergence rule and this rule will do a lot for many organization that have or are adopting maven. I know it definitely helped at the last place I worked. Enforcing no API breaking changes within minor versions has been on my wish list for a while too. My plan was to use the Clirr plugin in a profile that is only activated for minor versions. This latter point requires something like MNG-3826 though. Personally I feel that this check is beyond the scope of the enforcer. By default the enforcer runs at validate phase, way before classes are compiled for Clirr, so I'd feel happier achieving this in the verify phase using clirr:check. It is a hazy line between enforcer rules and other plugin goals, but I'd suggest using rules for (fast) environment and POM checks and other plugins for (slower) checks that require results of lifecycle phases. Mark - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [ANN] Apache Maven 3.0 Released
Congrats! Thanks to everyone who put the substantial effort into making this milestone release. Mark On 8 October 2010 14:10, Benjamin Bentmann bentm...@apache.org wrote: The Maven team is pleased to announce the release of Apache Maven 3.0. Maven is a project comprehension and build tool, designed to simplify the process of maintaining a healthy development lifecycle for your project. You can read more here: http://maven.apache.org/ Downloads of source and binary distributions are listed in our download section: http://maven.apache.org/download.html A major goal of Maven 3.0 is to be compatible, to the extent possible, with existing plugins and projects designed for Maven 2.x. Users interested in upgrading to this new major release should have a glance at the compatibility notes for known differences between Maven 3.0 and Maven 2.x: http://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html If you encounter unexpected problems while using Maven 3.0, please feel free to contact us via the Maven developer list: http://maven.apache.org/mail-lists.html Last but not least, the Maven team would like to thank all the users that tested the various alphas/betas/RCs and provided valuable feedback that helped us to eventually release a solid Maven 3.0! Release Notes - Maven 2 3 - Version 3.0 (since 3.0-beta-3 only) ** Bug * [MNG-4592] - Snapshot artifacts that could not be downloaded due to communication problems are blacklisted for a day by default. * [MNG-4751] - Snapshot version not resolved for version range * [MNG-4785] - NPE in dependency resolution code for TC plugin * [MNG-4786] - [regression] Ant-based mojo using maven-script-ant:2.1.0+ cause NPE * [MNG-4788] - [regression] Appassembler Maven Plugin doesn't work like as it should * [MNG-4789] - [regression] Difference in compile scope dependency resolution * [MNG-4791] - [regression] POM artifacts passed into MavenProjectBuilder.buildFromRepository() are no longer resolved * [MNG-4793] - Unable to obtain archiver for extension 'zip' * [MNG-4794] - 'org.apache.maven.plugins:maven-install-plugin:2.3.1'. A required class is missing: org.codehaus.plexus.digest.Digester * [MNG-4795] - [regression] Dependencies in forked reactor projects are not resolved when aggregator bound to lifecycle forks * [MNG-4800] - Conflict resolution does not pick sub tree of nearest dependency if farther conflicting dependency has wider scope * [MNG-4810] - Maven cannot build if loaded in a classloader that is not backed by a real JAR file / classpath * [MNG-4811] - Custom Maven Plugin regression in Maven 3.x, custom ComponentConfigurator causes infinite loop * [MNG-4814] - Eary dependency resolution attempts for reactor projects prevent their later resolution from the reactor * [MNG-4818] - NPE in legacy.DefaultWagonManager.getArtifact * [MNG-4829] - [regression] Checksum failures aren't logged * [MNG-4832] - Maven 3 Regression: Missing constructor of org.codehaus.plexus.component.configurator.converters.special.ClassRealmConverter * [MNG-4834] - [regression] MavenProject.getParent() ignores configured repositories * [MNG-4836] - Incorrect recursive expression cycle errors (update plexus-interpolation) * [MNG-4837] - Interpolation error due to cyclic expression for one of the POM coordinates gets needlessly repeated * [MNG-4842] - [regression] Repositories discovered in dependency POMs override repositories configured for original resolution request of POM * [MNG-4845] - [regression] MavenProject.getDependencyArtifact() returns artifacts without version for dependency with version range ** Improvement * [MNG-4452] - Metadata for snapshots should include classifier * [MNG-4787] - Allow class realm manager delegates to alter public part of Maven core realm * [MNG-4815] - (3.0-RC1) Maven Java API does not give nice error messages when improperly configured * [MNG-4824] - multiple failures need additional whitespace * [MNG-4825] - Relative path errors could be more explicit ** New Feature * [MNG-4484] - Create a Maven API for component configuration ** Task * [MNG-4805] - Update default plugin versions used for built-in lifecycle mappings * [MNG-4807] - Extend core artifact filter to exclude relocated Guice-based Plexus shim ** Wish * [MNG-4796] - add a warning when profiles.xml is used (Maven 2) or detected (Maven 3) Enjoy, -The Maven team - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven 3.0
It generally works for my builds apart from the behaviour of an internal Maven plugin. This plugin uses the shared component maven-runtime to determine the dependency order of the project's dependencies, which is subtly different between m2.2.1 and m3. I haven't had time to fully debug the problem, but it could be a classloader or dependency resolution issue. maven-runtime itself passes all tests under m3. I'll try to delve further when time allows, but if there is an underlying problem then I'm happy to target m3.0.1. So +0 from me (non-binding). Mark On 4 October 2010 13:16, Benjamin Bentmann benjamin.bentm...@udo.edu wrote: Hi, feedback on the RCs seems to be decreasing and I am currently not aware of any major regression so let's try and cross the finishing line of this marathon. We solved 31 issues since 3.0-beta-3: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=13142 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=10500status=1 Staging repo: https://repository.apache.org/content/repositories/maven-004/ Staged source and binary distros: https://repository.apache.org/content/repositories/maven-004/org/apache/maven/apache-maven/3.0/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 +1 from me Benjamin - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven 3.0
On 5 October 2010 14:31, Baptiste MATHUS m...@batmat.net wrote: +1. It'd confirm what I checked yesterday (see my other mail). I was having problem with XML parser due to a different classpath ordering inside surefire between m2.2.1 and m3. As Olivier said, it's true it's bad to rely on classpath ordering, but I'm wondering if something could be done so that classpath is always calculated the same way (or so is ordered the same) between m2/3. In fact, I fear this difference could cause some compatibility problems between m23 that will refrain some users from migrating. I guess this is something inside aether that was done on purpose, maybe to clean things that might have specially been done in m2. It's not actually the classpath order that I'm relying on, it's the order of dependencies on the classpath after they've been sorted by ProjectSorter, which should be deterministic. I've just had a look at the log between 2.2.1 and 3.0 for ProjectSorter [1] and there appears to be quite a few changes. I thought its testcase was missing until I found it elsewhere [2] - we may want to align its package. Is anyone aware of any potentially breaking changes that have been made to ProjectSorter? It's definitely returning slightly different results than 2.2.1. Mark [1] http://svn.apache.org/repos/asf/maven/maven-3/trunk/maven-core/src/main/java/org/apache/maven/project/ProjectSorter.java [2] http://svn.apache.org/repos/asf/maven/maven-3/trunk/maven-core/src/test/java/org/apache/maven/execution/ProjectSorterTest.java - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven 3.0
On 5 October 2010 15:54, Jason van Zyl ja...@sonatype.com wrote:
a DAG which is toposorted is naturally unordered for elements at the same
level in a graph. The set is deterministic, the order of that set is not.
Relying on any ordering for something that is naturally unordered is not
really a great idea.
For visualization I would agree that from one rendering to another it should
appear the same and most graphing libraries provide a sorting attribute to
ensure this. A deterministic ordering across the resolution for a project
would be tricky. You're fighting against the ordering the user has provided
in the POMs, and what you want to sort against. How you mix those needs to be
defined. I don't think this is actually much easier even within the reactor.
Do you use the module order? Do you build out the list from the first
element? The last element? Alphabetically? Do you take an element's order
where the conflict was won? The conflict in one case may be won in one part
of the tree, and somewhere else under different conditions. If that's the
element you rely on then it's placement just changed as a result of conflict
resolution and you're punched again.
You could try and simplify the whole strategy by ordering the resolved set.
If the order truly shouldn't matter then if you alphabetized, as one example,
the final output would always be consistent. But this negates any ordering
the user has made. Slight changes in resolution change the ordering is the
problem and it will change as the underlying tree changes and the process by
which it is transformed into a graph.
I would avoid this completely and if you need some fudge factor, then make a
utility that might do something like:
DependencyList list = new DependencySetAsList( set )
.move( gav0 ).toFront()
.move( gav1 ).after( gav0 );
And possibly allow some ordering textually if you want to put it in a POM:
classpath${gav0}${gav1}${remainder}/classpath
Sorry, I don't think I was clear enough before. It's not the ordering
of elements at the same level that's a problem, it's that the element
order is wrong. I was also meaning deterministic with regard from
m2.2.1 to m3.
I'm relying on processing dependencies in dependency order, i.e. the
order returned from ProjectSorter. I have a project of 100+ internal
dependencies that is coming back in the wrong order using m3's
ProjectSorter, but it is correct under m2.2.1's version. I have
checked the dependency tree using m3's -X and a dependency of tree
depth 2 is appearing *before* a dependency of tree depth 8 in the
sorted list, which is meant to be in accumulating dependency order.
Mark
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
[m3] ProjectSorter problems (was: Re: [VOTE] Release Apache Maven 3.0)
Branching the m3 vote thread: On 5 October 2010 16:22, Mark Hobson markhob...@gmail.com wrote: Sorry, I don't think I was clear enough before. It's not the ordering of elements at the same level that's a problem, it's that the element order is wrong. I was also meaning deterministic with regard from m2.2.1 to m3. I'm relying on processing dependencies in dependency order, i.e. the order returned from ProjectSorter. I have a project of 100+ internal dependencies that is coming back in the wrong order using m3's ProjectSorter, but it is correct under m2.2.1's version. I have checked the dependency tree using m3's -X and a dependency of tree depth 2 is appearing *before* a dependency of tree depth 8 in the sorted list, which is meant to be in accumulating dependency order. I've taken a quick look at ProjectSorter in the debugger and it looks like it's skipping vertexes where versions don't match. For example, if A depends on B:1.0 but B is resolved to 1.1 (via resolution or management) then A-B:1.0 is lost. One suspect could be isSpecificVersion which returns true for 1.0, which isn't a specific version like [1.0], so this vertex gets lost as B:1.0 doesn't exist. Mark - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [m3] ProjectSorter problems (was: Re: [VOTE] Release Apache Maven 3.0)
On 5 October 2010 18:35, Mark Hobson markhob...@gmail.com wrote: I've taken a quick look at ProjectSorter in the debugger and it looks like it's skipping vertexes where versions don't match. For example, if A depends on B:1.0 but B is resolved to 1.1 (via resolution or management) then A-B:1.0 is lost. One suspect could be isSpecificVersion which returns true for 1.0, which isn't a specific version like [1.0], so this vertex gets lost as B:1.0 doesn't exist. I've raised MNG-4854 [1] to demonstrate the problem. Mark [1] http://jira.codehaus.org/browse/MNG-4854 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [m3] ProjectSorter problems (was: Re: [VOTE] Release Apache Maven 3.0)
On 5 October 2010 21:50, Mark Hobson markhob...@gmail.com wrote: I've raised MNG-4854 [1] to demonstrate the problem. Benjamin, I understand your comment on the issue. The situation I have is with maven-runtime where all dependencies have already been mediated, so project:1.0 is in fact using dependency:1.0 at runtime. Is there a way that we could support both behaviours? The alternative would be for maven-runtime to align all dependency versions to those that are available at runtime. Mark - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [m3] ProjectSorter problems (was: Re: [VOTE] Release Apache Maven 3.0)
On 5 October 2010 22:43, Benjamin Bentmann benjamin.bentm...@udo.edu wrote: To me the situation looks like this: The ProjectSorter serves one purpose, that is to figure out the build order of projects within a reactor. Unless I misunderstand, you seem to have a different use case and merely use the ProjectSorter because its API/signatures matches. If so, then I suggest to simply fork the sorter from 2.x into your own code base. It's not wildly different, and being a Maven shared component I'd rather not fork 2.x code. I'll deal with it in maven-runtime, thanks. Mark - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[RESULT] [VOTE] Release Maven Checkstyle plugin version 2.6
Hi, The vote has passed with the following result : +1 (binding): Emmanuel Venisse, Lukas Theussl, Olivier Lamy, John Casey, Herve Boutemy I will promote the artifacts to the central repo. Mark - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Add maven-checkstyle-plugin:2.6 to board report
Hi there, Could a PMC add maven-checkstyle-plugin:2.6 to the board report please? Thanks, Mark - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[ANN] Maven Checkstyle Plugin 2.6 Released
The Maven team is pleased to announce the release of the Maven Checkstyle Plugin, version 2.6. This plugin generates a report regarding the code style used by the developers. http://maven.apache.org/plugins/maven-checkstyle-plugin/ You should specify the version in your project's plugin configuration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-checkstyle-plugin/artifactId version2.6/version /plugin Release Notes - Maven 2.x Checkstyle Plugin - Version 2.6 ** Bug * [MCHECKSTYLE-129] - Unable To Load configLocation From URL * [MCHECKSTYLE-130] - multimodule project requires src/main/java after 2.5 update * [MCHECKSTYLE-131] - Plugin can't use configLocation from parent. * [MCHECKSTYLE-135] - Can't use a configFile with an URL ** Improvement * [MCHECKSTYLE-139] - Add @threadSafe support for maven3 Enjoy, -The Maven team - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[VOTE] Release Maven Checkstyle plugin version 2.6
Hi, We solved 5 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11127styleName=Htmlversion=16212 There are still several issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11127status=1 Staging repo: https://repository.apache.org/content/repositories/maven-005/ Staging site (wait for sync): http://maven.apache.org/plugins/maven-checkstyle-plugin-2.6/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 Mark - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Plugin deployment problems
On 21 September 2010 04:45, Brian Fox bri...@infinity.nu wrote: I'm at JavaOne this week so I didn't see this until know. You're back in the group now. Great, thanks Brian, all working now. Mark - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Plugin deployment problems
On 17 September 2010 21:38, Anders Hammar and...@hammar.net wrote:
That's what I would do. Start with a simple setup and when that works add
the encryption.
I still get a 403 when using no password encryption. I've also tried
using the httpclient wagon provider but to no avail:
[INFO] [deploy:deploy {execution: default-deploy}]
[INFO] Retrieving previous build number from apache.snapshots.https
[DEBUG] Using Wagon implementation httpclient from default mapping for
protocol https
[DEBUG] Checking for pre-existing User-Agent configuration.
[DEBUG] Adding User-Agent configuration.
[DEBUG] Connecting to repository: 'apache.snapshots.https' with url:
'https://repository.apache.org/content/repositories/snapshots'.
[DEBUG] Using Wagon implementation httpclient from default mapping for
protocol https
[DEBUG] Using Wagon implementation httpclient from default mapping for
protocol https
[DEBUG] Checking for pre-existing User-Agent configuration.
[DEBUG] Adding User-Agent configuration.
[DEBUG] not adding permissions to wagon connection
Uploading:
https://repository.apache.org/content/repositories/snapshots/org/apache/maven/plugins/maven-checkstyle-plugin/2.6-SNAPSHOT/maven-checkstyle-plugin-2.6-20100920.100436-5.jar
[DEBUG]
https://repository.apache.org/content/repositories/snapshots/org/apache/maven/plugins/maven-checkstyle-plugin/2.6-SNAPSHOT/maven-checkstyle-plugin-2.6-20100920.100436-5.jar
- Status code: 403
[DEBUG] Using Wagon implementation httpclient from default mapping for
protocol https
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error deploying artifact: Authorization failed: Access denied
to:
https://repository.apache.org/content/repositories/snapshots/org/apache/maven/plugins/maven-checkstyle-plugin/2.6-SNAPSHOT/maven-checkstyle-plugin-2.6-20100920.100436-5.jar
[INFO]
[DEBUG] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Error
deploying artifact: Authorization failed: Access denied to:
https://repository.apache.org/content/repositories/snapshots/org/apache/maven/plugins/maven-checkstyle-plugin/2.6-SNAPSHOT/maven-checkstyle-plugin-2.6-20100920.100436-5.jar
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:719)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at
org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:592)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.MojoExecutionException: Error
deploying artifact: Authorization failed: Access denied to:
https://repository.apache.org/content/repositories/snapshots/org/apache/maven/plugins/maven-checkstyle-plugin/2.6-SNAPSHOT/maven-checkstyle-plugin-2.6-20100920.100436-5.jar
at
org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:189)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
... 17 more
Caused by: org.apache.maven.artifact.deployer.ArtifactDeploymentException:
Error deploying artifact: Authorization failed: Access denied to:
https://repository.apache.org/content/repositories/snapshots/org/apache/maven/plugins/maven-checkstyle-plugin/2.6-SNAPSHOT/maven-checkstyle-plugin-2.6-20100920.100436-5.jar
at
org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:121)
Re: Plugin deployment problems
On 20 September 2010 13:01, Martin Gainty mgai...@hotmail.com wrote: did you add repository.apache.org/content/repositories/snapshots repository to your list of proxied repositories in your ./.m2/settings.xml http://maven.apache.org/ref/2.2.1/maven-settings/settings.html I haven't got any proxy elements in my settings.xml, just server ones as detailed in: http://maven.apache.org/developers/committer-settings.html Mark - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Plugin deployment problems
On 20 September 2010 13:00, Anders Hammar and...@hammar.net wrote: I'd say you don't have permission to deploy (snapshots) to m-checkstyle-p. You need to get someone to verify this for you. Strange, I successfully released 2.4 about a year ago, but the infrastructure has changed somewhat since then. Can anyone be so kind to check my permissions please? I do hope I'm not missing something obvious here. Mark - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Plugin deployment problems
On 20 September 2010 14:20, Anders Hammar and...@hammar.net wrote: I'm kind of thinking that Jason was right when he said that the switch to ldap could have caused this... Not sure if it's related, but I couldn't add my new PGP key to KEYS [1] either: svn: Commit failed (details follow): svn: Server sent unexpected return value (403 Forbidden) in response to CHECKOUT request for '/repos/asf/!svn/ver/941720/maven/project/KEYS' Mark [1] https://svn.apache.org/repos/asf/maven/project/KEYS - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Plugin deployment problems
On 20 September 2010 15:12, Benjamin Bentmann benjamin.bentm...@udo.edu wrote: I don't see your user id among [0] and the Maven Parent POM says your role is emeritus, that explains it I guess. Two months back, there was some cleanup of the groups. Maybe you fall through and didn't get a mail when your status was changed. Oh no! You're right, Brian demoted me back in July; that'll teach me for getting caught up with work. Do I have to do anything special to get reinstated? Just curious: the glossary [1] states, Emeritus status indicates interest but not activity, so does that mean lack of activity doesn't necessarily imply emeritus status? Mark [1] http://www.apache.org/foundation/glossary.html - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Plugin deployment problems
On 20 September 2010 16:43, Wendy Smoak wsm...@gmail.com wrote: (If Brian hasn't seen this thread and done it already,) send an email to the PMC list private@ and ask to be reinstated. Sent, thanks. Mark - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Plugin deployment problems
Any ideas on this one? It's blocking me from releasing the maven-checkstyle-plugin which I'd like to do ASAP. Mark On 16 September 2010 18:44, Mark Hobson markhob...@gmail.com wrote: Hi there, I've been updating my environment to release the Checkstyle plugin and am having problems even deploying a snapshot. I've configured settings.xml as specified [1] but still get: [INFO] Error deploying artifact: Authorization failed: Access denied to: https://repository.apache.org/content/repositories/snapshots/org/apache/maven/plugins/maven-checkstyle-plugin/2.6-SNAPSHOT/maven-checkstyle-plugin-2.6-20100916.173741-5.jar I've used the same credentials that are in my settings.xml for apache.snapshots.https to successfully log into Apache's Nexus. Is there anything I'm missing? Cheers, Mark [1] http://www.apache.org/dev/publishing-maven-artifacts.html#settings - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Plugin deployment problems
On 17 September 2010 19:41, Anders Hammar and...@hammar.net wrote: But he could log into the Apache Nexus instance through the UI, so that can't be the case. Mark, are you sure the server id in settings.xml match the id of the repo (e.i. apache.snapshots.https)? Is the password encrypted? As sure as I can be as it is encrypted. I can try without encryption just to make sure that isn't causing problems. Mark - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [Checkstyle plugin] possible release
I could do with this release too and am happy to perform it. Having a few problems updating my environment though; I'll send a separate mail. Mark On 13 September 2010 22:37, Olivier Lamy ol...@apache.org wrote: Hi, I will try to work on this at the end of the week (if no spare time issue :-) ). 2010/9/13 Dominique Jean-Prost dominique.jean-pr...@dexia-sofaxis.com: Hello, Could someone consider releasing checkstyle plugin 2.6 as there are no more pending issues please ? As I'm eagerly waiting for some fixes, I dared to write here. Thank you in advance. Dom -- View this message in context: http://maven.40175.n5.nabble.com/Checkstyle-plugin-possible-release-tp2837375p2837375.html Sent from the Maven Developers mailing list archive at Nabble.com. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Olivier http://twitter.com/olamy http://www.linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Plugin deployment problems
Hi there, I've been updating my environment to release the Checkstyle plugin and am having problems even deploying a snapshot. I've configured settings.xml as specified [1] but still get: [INFO] Error deploying artifact: Authorization failed: Access denied to: https://repository.apache.org/content/repositories/snapshots/org/apache/maven/plugins/maven-checkstyle-plugin/2.6-SNAPSHOT/maven-checkstyle-plugin-2.6-20100916.173741-5.jar I've used the same credentials that are in my settings.xml for apache.snapshots.https to successfully log into Apache's Nexus. Is there anything I'm missing? Cheers, Mark [1] http://www.apache.org/dev/publishing-maven-artifacts.html#settings - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Filling in a few gaps with enforcer rules
Great, thanks Rex. Mark On 13 September 2010 18:45, Rex Hoffman r...@e-hoffman.org wrote: Hey Mark, A little later than I promised but here it is: http://jira.codehaus.org/browse/MENFORCER-107 Rex On Wed, Sep 8, 2010 at 1:16 PM, Mark Hobson markhob...@gmail.com wrote: Great, no real rush thanks, I just wondered if anything was happening. If you could post the issues to this thread when they're raised then I'll track it from there. Thanks and happy time off! Mark On 8 September 2010 18:41, Rex Hoffman r...@e-hoffman.org wrote: I haven't opened it yet as I still have to separate out functionality, and write up some info for the site report. Already have the integration test done. I just quit my job and have two weeks off until I start my next, last day, yay! So really good news for you! I expect to have this split out and the site info done this week. If you can't wait I released it for my (old) companies use on my website ( http://www.e-hoffman.org/released/repo ) Sites are under repo as well Not heavily documented but, if you include that location and add this to your pom, you get the goodness. plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-enforcer-plugin/artifactId version1.0-beta-1/version dependencies dependency groupIdorg.apache.maven.enforcer.rules/groupId artifactIdmaven-enforce-releasability/artifactId version1.0.0/version /dependency /dependencies executions execution idenforce/id configuration rules myCustomRule implementation=org.apache.maven.enforcer.rule.DependencyRule enforceNoSnapshotsOnReleasefalse/enforceNoSnapshotsOnRelease enforceDependencyConvergencetrue/enforceDependencyConvergence /myCustomRule /rules /configuration goals goalenforce/goal /goals /execution /executions /plugin Or you can wait on me, and then a dev with commit rights to get in to maven proper. Cheers, Rex On Wed, Sep 8, 2010 at 4:26 AM, Mark Hobson markhob...@gmail.com wrote: Were any issues raised to track the progress of these new rules? I'm particularly interested in this one: 2) Maven should have the option of forcing developers to ensure dependencies converge rather than relying on the closest to the top rule it uses by default. In large projects this can be problematic. Cheers, Mark - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Filling in a few gaps with enforcer rules
Were any issues raised to track the progress of these new rules? I'm particularly interested in this one: 2) Maven should have the option of forcing developers to ensure dependencies converge rather than relying on the closest to the top rule it uses by default. In large projects this can be problematic. Cheers, Mark - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Filling in a few gaps with enforcer rules
Great, no real rush thanks, I just wondered if anything was happening. If you could post the issues to this thread when they're raised then I'll track it from there. Thanks and happy time off! Mark On 8 September 2010 18:41, Rex Hoffman r...@e-hoffman.org wrote: I haven't opened it yet as I still have to separate out functionality, and write up some info for the site report. Already have the integration test done. I just quit my job and have two weeks off until I start my next, last day, yay! So really good news for you! I expect to have this split out and the site info done this week. If you can't wait I released it for my (old) companies use on my website ( http://www.e-hoffman.org/released/repo ) Sites are under repo as well Not heavily documented but, if you include that location and add this to your pom, you get the goodness. plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-enforcer-plugin/artifactId version1.0-beta-1/version dependencies dependency groupIdorg.apache.maven.enforcer.rules/groupId artifactIdmaven-enforce-releasability/artifactId version1.0.0/version /dependency /dependencies executions execution idenforce/id configuration rules myCustomRule implementation=org.apache.maven.enforcer.rule.DependencyRule enforceNoSnapshotsOnReleasefalse/enforceNoSnapshotsOnRelease enforceDependencyConvergencetrue/enforceDependencyConvergence /myCustomRule /rules /configuration goals goalenforce/goal /goals /execution /executions /plugin Or you can wait on me, and then a dev with commit rights to get in to maven proper. Cheers, Rex On Wed, Sep 8, 2010 at 4:26 AM, Mark Hobson markhob...@gmail.com wrote: Were any issues raised to track the progress of these new rules? I'm particularly interested in this one: 2) Maven should have the option of forcing developers to ensure dependencies converge rather than relying on the closest to the top rule it uses by default. In large projects this can be problematic. Cheers, Mark - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: annotations support in compiler mojo
On 29 March 2010 10:35, Milos Kleint mkle...@gmail.com wrote: yes, one place when this issue arises is when your own project defines a annotation processor of it's own. See http://jira.codehaus.org/browse/MCOMPILER-97 Hmm, maybe we'll have to split the compiler plugin up into two different executions for proc:none and proc:only. It'd be interesting to see what the actual performance hit is for this set up compared to a single invocation. I'd like to do a 2.2 release sometimes later this month. Cool, I'll try it out soon. Cheers, Mark - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: annotations support in compiler mojo
Hi Milos, Sorry for the delay again, I've been away from code for a while. On 6 March 2010 13:27, Milos Kleint mkle...@gmail.com wrote: I see. I think the regular compilation classpath shall be the default though. The question is how to encode this special processor path? is there a way to encode dependency elements inside the configuration? or shall we just have a simple boolean parameter that would take plugin's classpath/dependencies instead of the project compilation cp and encode the processor path as dependency of the plugin? I agree that the compile classpath should be the default, as it is with javac. Unless there's any other use case for specifying plugin dependencies to the compiler plugin, I'd just use them as the processor path if specified, avoiding the need to encode them. what is the purpose of the staleness checking? to avoid regenerating resources all over again? The various rules assume you always know what the given annotation generates, which might not be applicable to everyone (and requires additional mandatory configuration?) If we add it can it be off be default? So that only those caring enough get to configure it? Yeah, the staleness checking is merely an optimisation. Like you say, It isn't straightforward as you need to know how the processors generate files. It can certainly be off by default, and it's more a nice-to-have than absolutely necessary. I'm sure builds will be quicker now if we're only invoking javac once, rather than javac and then apt. Obviously this is complicated if we're also compiling too. Yes, you would have to somehow recognize this upfront and pass -proc:none to avoid processing? but how do you figure? the current netbeans annotations do generate resources (layer.xml files and META-INF/services content) and also java/class files. If you generate class files, you cannot probably do just annotation processing (in process-resources) without compiling as well. Or we would have to add the generated sources root to the project? OTOH when resources get generated in compile phase, it probably only matters if you want to do filtering of these resources? but that assumes your annotations do generated filterable content. Hmm. I suppose this setup can be configured in the pom, additional execution with -proc:only and the default compile execution with -proc:none So I would go with doing annotation processing along with compiling, it's going to be faster and is actually the default javac behaviour as well. The other scenarios seem to be configurable then as well using the current parameters, right? Sounds good to me. I just wanted to highlight the fact that this circumnavigates Maven's traditional lifecycle phases. Thanks for doing the work on this, I'll look forward to using it soon! Cheers, Mark - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: annotations support in compiler mojo
Hi Milos, Apologies for the delayed reply. See my responses inline: On 25 February 2010 09:10, Milos Kleint mkle...@gmail.com wrote: Hello Mark, what are the required feaures you are after? From the glimpse at the apt plugin, I got the impression that it has quite a lot of configuration, some I didn't completely understand.. here's what already implemented in code -proc parameter to turn aannotation processing off, or enable it exclusively without compilation. default is process+compile. -s path with reasonable path for generated source fles - target/generated/sources/annotations (or test-annotation when executed from test-compile mojo) -processor parameter with optional list of processor classes All these switches are only applied to javac when the source/compiler level is 1.6+. It can already be tested with the latest snapshot of maven-compiler-plugin in apache snapshot repository. What is missing? 1. -processorpath handling. Not sure how many projects have different processor path from compile path, but probably useful to have. I'm not sure how to represent it in terms of mojo parameters. Any hints, precedents welcome.. I certainly use this, since processors are only required at build time I like to keep them out of the runtime dependencies. See the second example here for how apt-maven-plugin configures this: http://mojo.codehaus.org/apt-maven-plugin/examples/configuring-a-factory.html 2. -implicit - i'm entirely clueless what this is supposed to do.. I'm not too familiar with this either, will need to read more. 3. -Akey=value parameters for annotation processors. could be left for configuration via the generic compileArguments parameter I guess.. Yeah, this is currently achieved with an options mojo parameter, but I agree the compileArguments parameters would be better in maven-compiler-plugin. 4. currently we put just java source root on the -sourcepath. At least in netbeans codebase we have cases where the sourcepath is supposed to contain resources accessed by the annotation processors. Bundle properties files get checked for presence of keys at compile time etc. I've experimented with adding either target/classes or src/main/resources of source path, but neither worked now due to a bug in javac - jglick filed it under http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6929404 (might take a few days to appear). There is an ugly workaround, to define the resources in src/main/java. I expect we add the relevant portion to the compiler plugin only after at least one jdk release includes the fix. I see, nasty, I haven't encountered such a setup yet. Anything else that could be described as dealbreaker for anyone? I'd like to see support for the apt staleness checking that currently exists: http://mojo.codehaus.org/apt-maven-plugin/examples/configuring-staleness-checking.html Obviously this is complicated if we're also compiling too. Another thought I had was that the lifecycle phases are going to get muddied somewhat by the compiler goal also running apt. For example, resources may be generated during the compile phase rather than at the generate-resources phase. I wonder what we want to be the default behaviour? Either to split out the compiler mojo into two separate executions, thus being slower, or to combine them for speed. Even with the former, we don't know in advance whether apt is generating sources or resources, so it still could be executing in the wrong phase. Cheers, Mark - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: annotations support in compiler mojo
Late reply on this one, but I'm certainly interested in seeing apt support added to maven-compiler-plugin. There is already a separate plugin for apt over at Mojo, apt-maven-plugin [1]. I worked on this a while back to get it into shape and am currently using it in production. I'd be happy to see this superseded by the compiler plugin if it incorporates all of the existing functionality. Cheers, Mark [1] http://mojo.codehaus.org/apt-maven-plugin/ On 10 February 2010 15:21, nicolas de loof nicolas.del...@gmail.com wrote: Would such a dedicated plugin only apply annotation processing or replace compiler plugin ? This may implies duplicate configuration for compiler + annotation-processing plugins. Also consider slower build process as javac will need to parse source code 2 times. (late) +1 for annotations support in maven-compiler-plugin Nicolas 2010/2/10 Brian Fox bri...@infinity.nu Does it make sense to create a plugin specifically for annotation processing? On Sat, Jan 30, 2010 at 3:06 AM, Milos Kleint mkle...@gmail.com wrote: can I read silence as lazy consensus to add annotation processing to the compiler plugin? Milos On Mon, Jan 25, 2010 at 2:48 PM, Milos Kleint mkle...@gmail.com wrote: Hello, I'd like to start a discussion about how annotations are supported in maven builds. I'm currently trying to use some NetBeans Platform based annotations in maven projects and I'm encountering some problems. 1. http://jira.codehaus.org/browse/MCOMPILER-98 - -sourcepath needs to be always set to have the annotations processed. fixed in latest plexus compiler sources.. 2. some annotation processors require resources to be present on the sourcepath eg. one that generates java beans from schema or another one that checks for property bundle key presence. I'm not sure how to make this generally available to the processor. resources themselves (in src/main/resources) are not to be referenced I guess (as they could be on wrong targetPath or not filtered). So the only other option is to include the target/classes folder somehow with the correctly processed resources. Any other idea? 3. Some annotation processors generate xml files or META-INF/services content, some generate java files. the default output location for the processor is target/classes, which is fine for xml files, but it's inconvenient to generate java files there as they end up in the jar file then. I've tried to configure the compiler to use target/generated-sources/annotations as the output folder for sources (via -s dir switch). Unfortunately there are problems associated with that approach. a. the folder needs to exist up front or the compiler chokes on it. Doable with some ant-run scripting, but ugly. b. what to do with the resources there that need to be copied to the target/classes folder? Doable with resources:copy-resources but again ugly. 4. reporting from the annotations processors is broken - http://jira.codehaus.org/browse/MCOMPILER-66 Issue http://jira.codehaus.org/browse/MCOMPILER-75 seems to be dedicated to annotation support. Is anyone actively working on it? I'm volunteering to add some of the required switches as prameters for the compiler mojo, but I'm unsure how to proceed. Is it ok just to add the required stuff as mojo params, even if it will be unused by some of the other compilers? and even by the non 1.6 javac compilers? or have some new ways fo configuring the mojo (as pointed out in http://jira.codehaus.org/browse/MCOMPILER-14)? Thanks for any comments. Milos PS: I can provide a sample project with the above mentioned annotations being used if there is interest. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: New Release Tree Maven Module
I'm a little confused as to what this approach involves, as you seem to suggest releasing up the dependency tree from a given leaf project? I'd certainly advocate a release goal to release in the opposite direction, i.e. a project and all its snapshot dependencies down the dependency tree. Mark On 16 January 2010 13:37, Daniel Frey qwer12...@gmx.ch wrote: Hi I would like to write my first maven module that does releases over all the dependencies of a main module. I am interested in your opinion, recommondations and critical feedback. Let me first illustrate why I would like to do that. The maven-release-plugin does a release in a way that it: 1. Adds a tag to the repository for the main module 2. Releases al artifacts of the main module (JARs, website) 3. Deploys all artifacts of the main module to the remote repository (JARs for bitecode, sources and javadoc) 4. Allows to change the development versions of the dependent modules What I miss in this approach is: 1. The sites of all dependent modules (including test results and coverage, javadocs, dependencies) 2. Dependent modules artifacts in the repository (distinctly versioned JARs for bitecode, sources and javadoc) 3. Distinct versions of the dependent modules when copying all the needed libraries to the official website (say in a JNLP release) The idea of the new module would be to iterate through all dependent modules from dependency tree leaf towards its root and: 1. Investigate the existing tags on the SVN repository to find one for the dependent module 2. If the dependent module has code changes since the tags revision: 2a. Alter the POM dependent module so it reflects the dependencies to its dependent modules correctly by replacing SNAPSHOT versions with distinct tagged versions 2b. Release the dependent module 3. Else do not release the module but keep the tagged version as the one to replace SNAPSHOTs in subsequent dependent modules Let me illustrate that with a concrete example. Say I have the following multi-module project dependencies for my main module ch.xmatrix.ups.tools.ust (filtering out only my own dependencies): ch.xmatrix.ups.tools.ust 2.1-SNAPSHOT +- ch.xmatrix.ups.tools.common 2.0-SNAPSHOT | +- ch.xmatrix.common.utils-all 2.3-SNAPSHOT | | \- ch.xmatrix.common.icon 1.4-SNAPSHOT | +- ch.xmatrix.ups.data.taxa 2.0-SNAPSHOT | \- ch.xmatrix.ups.data.constraints SNAPSHOT +- ch.xmatrix.ups.data.sessions SNAPSHOT +- ch.xmatrix.ups.data.courses SNAPSHOT \- ch.xmatrix.ups.server.client 2.0-SNAPSHOT \- ch.xmatrix.ups.server.interface 2.0-SNAPSHOT And there would be no current tag for ch.xmatrix.common.utils-all, ch.xmatrix.ups.data.constraints, ch.xmatrix.ups.server.interface and ch.xmatrix.ups.tools.ust without any changes in the meantime. I would like to be prompted for the desired development version change of each these remaining dependent modules. If I choose to keep the same development version, then the release order, the current development version would stay and the release version of this example would be: ch.xmatrix.common.utils-all 2.3-SNAPSHOT 2.3 ch.xmatrix.ups.data.constraints SNAPSHOT 1.0 ch.xmatrix.ups.server.interface 2.0-SNAPSHOT 2.0 ch.xmatrix.ups.tools.ust 2.1-SNAPSHOT 2.1 I currently achive that with a perl script. However, I wonder whether such a task would make sense to be done as a maven module (maven-releasetree-module). If it would make sense, I would see the following main limitation: My approach would use other maven modules like maven-dependency-modules and maven-release-module. Having had a quick look at the maven modules howto, this seem not to be a valid approach. Each module should be self-contained and independent of others. Any advices, recommondations, critical feedback, thoughts would be highly appreciated... Thanks for feedback in advance Daniel Daniel Frey Senior Software Engineer xmatrix Kellerweg 65 CH-8055 Zürich daniel.f...@xmatrix.ch http://www.xmatrix.ch tel: mobile: +41 (44) 241 64 46 +41 (77) 425 28 57 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[PMC] Maven Checkstyle Plugin 2.4 needs adding to board report
The Maven Checkstyle Plugin has been released. Can this get added to the next board report please. Cheers, Mark - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [PMC] Maven Checkstyle Plugin 2.4 needs adding to board report
2009/11/19 Benjamin Bentmann benjamin.bentm...@udo.edu: Done. For the future, please remember to cc the result to the PMC as well (cf. step 9 of the [0]). Ah ha, thanks, I missed that. Oh for a plugin to automate this process! Mark - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven Checkstyle plugin version 2.4
Hi, The vote has passed with the following result : +1 (binding): Arnaud HERITIER, Benjamin Bentmann, Hervé BOUTEMY, Olivier Lamy, Vincent Siveton +1 (non binding): nicolas de loof I will promote the artifacts to the central repo. Mark 2009/11/17 Vincent Siveton vsive...@apache.org: +1 Vincent 2009/11/12 Mark Hobson markhob...@gmail.com: Hi, The big new feature in this release is an upgrade to Checkstyle 5.0, which brings Java 5 compatibility. We solved 6 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11127version=15336 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11127status=1 Staging repo: https://repository.apache.org/content/repositories/maven-001/ Staging site: http://maven.apache.org/plugins/maven-checkstyle-plugin-2.4/ (Wait for sync, or use proxy) Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 Cheers, Mark - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven reporting impl version 2.0.4.3
2009/11/10 Vincent Siveton vsive...@apache.org: The vote has passed with the following result : +1 Benjamin, Lukas, Dennis, Hervé, Vincent I will promote the artifacts to the central repo. Have the artifacts been promoted to central? I can't see them: http://repo1.maven.org/maven2/org/apache/maven/shared/maven-reporting-impl/ Mark - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven reporting impl version 2.0.4.3
Ah great, thanks :) Mark 2009/11/12 Vincent Siveton vsive...@apache.org: Hi Mark, It seems that we changed the groupid/artifactid in the past. Here the right link: http://repo1.maven.org/maven2/org/apache/maven/reporting/maven-reporting-impl/ Cheers, Vincent 2009/11/12 Mark Hobson markhob...@gmail.com: 2009/11/10 Vincent Siveton vsive...@apache.org: The vote has passed with the following result : +1 Benjamin, Lukas, Dennis, Hervé, Vincent I will promote the artifacts to the central repo. Have the artifacts been promoted to central? I can't see them: http://repo1.maven.org/maven2/org/apache/maven/shared/maven-reporting-impl/ Mark - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Checkstyle ready for a 2.4 release?
I've upgraded maven-reporting-impl now that it has been released. The only unresolved issue destined for 2.4 is now MCHECKSTYLE-123 [1]. Can this be resolved quickly or shall we defer it until 2.5? Cheers, Mark [1] http://jira.codehaus.org/browse/MCHECKSTYLE-123 2009/11/4 Mark Hobson markhob...@gmail.com: Okay, I'll wait for that release first, thanks. Unless anyone else objects in the meantime, I'll start a vote to release maven-checkstyle-plugin 2.4 after that. Cheers, Mark 2009/11/3 Vincent Siveton vsive...@apache.org: Hi, maven-reporting-impl:2.0.4.3 should be release to be able to write single report, ie mvn checkstyle:checkstyle See MSHARED-120 Cheers, Vincent 2009/11/3 Mark Hobson markhob...@gmail.com: Hi there, Has anyone got any objections to rolling a Checkstyle 2.4 release? The big addition in this version is MCHECKSTYLE-105 [1] which upgrades Checkstyle to 5.0, and thus is compatible with Java 5. Several users have been using 2.4-SNAPSHOT successfully for a while now without problems, myself included. The remaining outstanding issue [2] is MCHECKSTYLE-123 [3]. Is there any rush to get this in 2.4 or can we defer this until 2.5? Cheers, Mark [1] http://jira.codehaus.org/browse/MCHECKSTYLE-105 [2] http://jira.codehaus.org/browse/MCHECKSTYLE/fixforversion/15336 [3] http://jira.codehaus.org/browse/MCHECKSTYLE-123 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Checkstyle ready for a 2.4 release?
Great, thanks Olivier. I'll start the vote for 2.4. Cheers, Mark 2009/11/12 Olivier Lamy ol...@apache.org: Hi, Move it to 2.5. I wanted to work on some refactoring on the plugin. But the best is to do it after the release :-) -- Olivier 2009/11/12 Mark Hobson markhob...@gmail.com: I've upgraded maven-reporting-impl now that it has been released. The only unresolved issue destined for 2.4 is now MCHECKSTYLE-123 [1]. Can this be resolved quickly or shall we defer it until 2.5? Cheers, Mark [1] http://jira.codehaus.org/browse/MCHECKSTYLE-123 2009/11/4 Mark Hobson markhob...@gmail.com: Okay, I'll wait for that release first, thanks. Unless anyone else objects in the meantime, I'll start a vote to release maven-checkstyle-plugin 2.4 after that. Cheers, Mark 2009/11/3 Vincent Siveton vsive...@apache.org: Hi, maven-reporting-impl:2.0.4.3 should be release to be able to write single report, ie mvn checkstyle:checkstyle See MSHARED-120 Cheers, Vincent 2009/11/3 Mark Hobson markhob...@gmail.com: Hi there, Has anyone got any objections to rolling a Checkstyle 2.4 release? The big addition in this version is MCHECKSTYLE-105 [1] which upgrades Checkstyle to 5.0, and thus is compatible with Java 5. Several users have been using 2.4-SNAPSHOT successfully for a while now without problems, myself included. The remaining outstanding issue [2] is MCHECKSTYLE-123 [3]. Is there any rush to get this in 2.4 or can we defer this until 2.5? Cheers, Mark [1] http://jira.codehaus.org/browse/MCHECKSTYLE-105 [2] http://jira.codehaus.org/browse/MCHECKSTYLE/fixforversion/15336 [3] http://jira.codehaus.org/browse/MCHECKSTYLE-123 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Olivier - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[VOTE] Release Maven Checkstyle plugin version 2.4
Hi, The big new feature in this release is an upgrade to Checkstyle 5.0, which brings Java 5 compatibility. We solved 6 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11127version=15336 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11127status=1 Staging repo: https://repository.apache.org/content/repositories/maven-001/ Staging site: http://maven.apache.org/plugins/maven-checkstyle-plugin-2.4/ (Wait for sync, or use proxy) Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 Cheers, Mark - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[ANN] Maven Runtime 1.0-alpha-2 Released
The Maven team is pleased to announce the release of Maven Runtime, version 1.0-alpha-2. Maven Runtime allows introspection of Maven project metadata at runtime. http://maven.apache.org/shared/maven-runtime/ You should specify the dependency in your project's POM: dependency groupIdorg.apache.maven.shared/groupId artifactIdmaven-runtime/artifactId version1.0-alpha-2/version /dependency Release Notes - Maven Runtime - Version 1.0-alpha-2 - Added support for introspecting URLs to MavenRuntime - Added url to parsing exception messages Enjoy, -The Maven team - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[PMC] Maven Runtime 1.0-alpha-2 needs adding to board report
Maven Runtime has been released. Can this get added to the next board report please. Cheers, Mark - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven reporting impl version 2.0.4.3
Just tried it with maven-checkstyle-plugin:checkstyle. It produces the single report, which is an improvement, but the CSSs are missing. Is this a known issue? Cheers, Mark 2009/11/3 Vincent Siveton vsive...@apache.org: Hi, This is a maintenance release to fix MSHARED-120. Staging repo: https://repository.apache.org/content/repositories/maven-013/ Staging site: http://maven.apache.org/shared/maven-reporting-impl-2.0.4.3 Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Checkstyle ready for a 2.4 release?
Okay, I'll wait for that release first, thanks. Unless anyone else objects in the meantime, I'll start a vote to release maven-checkstyle-plugin 2.4 after that. Cheers, Mark 2009/11/3 Vincent Siveton vsive...@apache.org: Hi, maven-reporting-impl:2.0.4.3 should be release to be able to write single report, ie mvn checkstyle:checkstyle See MSHARED-120 Cheers, Vincent 2009/11/3 Mark Hobson markhob...@gmail.com: Hi there, Has anyone got any objections to rolling a Checkstyle 2.4 release? The big addition in this version is MCHECKSTYLE-105 [1] which upgrades Checkstyle to 5.0, and thus is compatible with Java 5. Several users have been using 2.4-SNAPSHOT successfully for a while now without problems, myself included. The remaining outstanding issue [2] is MCHECKSTYLE-123 [3]. Is there any rush to get this in 2.4 or can we defer this until 2.5? Cheers, Mark [1] http://jira.codehaus.org/browse/MCHECKSTYLE-105 [2] http://jira.codehaus.org/browse/MCHECKSTYLE/fixforversion/15336 [3] http://jira.codehaus.org/browse/MCHECKSTYLE-123 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven Runtime version 1.0-alpha-2
2009/11/2 Stephen Connolly stephen.alan.conno...@gmail.com: 2009/11/2 Mark Hobson markhob...@gmail.com: Staging site: http://maven.apache.org/shared/maven-runtime-1.0-alpha-2/ The above link is broken for me, even using the Apache Proxy :-( It wasn't synced when I sent the email, but it's working for me now. Have you still got problems accessing the site? 2009/11/2 Jason van Zyl ja...@sonatype.com: Mark, Did you close the staging repostiory? I always forget to do this so it shows up as a broken link. I did close the staging repository, but I thought Stephen was referring to the site. 2009/11/2 Benjamin Bentmann benjamin.bentm...@udo.edu: Staging site: http://maven.apache.org/shared/maven-runtime-1.0-alpha-2/ The site apparently suffers from the missing site descriptor for maven-shared-components:13, i.e. it's missing stuff like the proper skin, the Privacy Policy disclaimer etc. So I suggest before deploying the final site, you hack the POM in your local checkout of the tag to inherit from maven-shared-components:14 and deploy the site using the fixed parent. Good point, let me rollback the release and update the parent to maven-shared-components:14. I'll cancel this vote and start another one shortly. Cheers, Mark - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[VOTE] Release Maven Runtime version 1.0-alpha-2 (take 2)
Hi, This second attempt now inherits maven-shared-components:14 to fix the site skin problems. We solved 2 issues: - Added support for introspecting URLs to MavenRuntime - Added url to parsing exception messages There are no issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truemode=hidejqlQuery=component+%3D+maven-runtime+AND+project+%3D+MSHARED+AND+resolution+%3D+Unresolved+ORDER+BY+updated+DESC Staging repo: https://repository.apache.org/content/repositories/maven-012/ Staging site: http://maven.apache.org/shared/maven-runtime-1.0-alpha-2/ (wait for the sync, or use the Apache proxy) Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 Cheers, Mark - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Checkstyle ready for a 2.4 release?
Hi there, Has anyone got any objections to rolling a Checkstyle 2.4 release? The big addition in this version is MCHECKSTYLE-105 [1] which upgrades Checkstyle to 5.0, and thus is compatible with Java 5. Several users have been using 2.4-SNAPSHOT successfully for a while now without problems, myself included. The remaining outstanding issue [2] is MCHECKSTYLE-123 [3]. Is there any rush to get this in 2.4 or can we defer this until 2.5? Cheers, Mark [1] http://jira.codehaus.org/browse/MCHECKSTYLE-105 [2] http://jira.codehaus.org/browse/MCHECKSTYLE/fixforversion/15336 [3] http://jira.codehaus.org/browse/MCHECKSTYLE-123 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[VOTE] Release Maven Runtime version 1.0-alpha-2
Hi, We solved 2 issues: - Added support for introspecting URLs to MavenRuntime - Added url to parsing exception messages There are no issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truemode=hidejqlQuery=component+%3D+maven-runtime+AND+project+%3D+MSHARED+AND+resolution+%3D+Unresolved+ORDER+BY+updated+DESC Staging repo: https://repository.apache.org/content/repositories/maven-009/ Staging site: http://maven.apache.org/shared/maven-runtime-1.0-alpha-2/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 Cheers, Mark - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: How to retrieve the current maven version from a plugin?
2009/10/22 Brett Porter br...@apache.org:
Well, there's maven-runtime in shared, but that stack dumps on M3 (not sure
if that's a regression or known incompat.)
Code like this:
try {
System.out.println( runtime.getProject( Mojo.class ).getVersion() );
} catch ( MavenRuntimeException e ) {
throw new MojoExecutionException( e.getMessage(), e );
}
Error:
[ERROR] : A required class was missing while executing
test:easy-mojo-plugin:1.0-SNAPSHOT:touch:
org/apache/maven/project/DuplicateProjectException
I think this is because maven-runtime uses maven-project-2.0.8 as a
dependency, the exceptions thrown by the project sorter API seem to change
over time.
Interesting, I haven't tried maven-runtime on M3. The maven-project
dependency is only required for the MavenRuntime.getProject method
calls, since they return full MavenProject instances. Try the
MavenRuntime.getProjectProperties methods which return the basic GAV
info instead.
Mark
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
apache-source-release-assembly-descriptor POM hierarchy
Hi there, Just been checking out the apache-source-release-assembly-descriptor project and noticed the strange POM hierarchy: org.apache:apache:6 v (inherits) org.apache.maven:maven-parent:13 | (uses) +- org.apache.apache.resources:apache-source-release-assembly-descriptor:1.0 org.apache.maven:maven-parent:12 v (inherits) org.apache.apache.resources:apache-resource-bundles:3 v (inherits) org.apache.apache.resources:apache-source-release-assembly-descriptor:1.0 Which means that apache-source-release-assembly-descriptor can't inherit maven-parent = 13 without a circular dependency. Thought I'd highlight it in case people weren't aware. Cheers, Mark - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: apache-source-release-assembly-descriptor POM hierarchy
2009/10/7 Brett Porter br...@apache.org: By that point, it'll be 1.1-SNAPSHOT, using 1.0, and so on. I think that's not a problem in the fashion that it is used. I guess, seems a bit weird to me. I'd probably have factored a new parent in that both maven-parent and apache-source-release-assembly-descriptor could share. Mark - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
