Maven Javadoc Plugin regression

2007-10-23 Thread ArneD
There is a serious regression in the maven-javadoc-plugin: MJAVADOC-116. It has been open for quite some time now, and has 21 votes. A test case is attached to the issue. I believe many users are forced to still use the 2.0 version as long as this issue is open. The related MJAVADOC-111 has

Re: [poll] Requiring users to specify plugin versions in Maven 2.1 or later

2007-09-03 Thread ArneD
Stephen Connolly wrote: B With the following proviso: I'd like to see main Maven releases more often, and have those main releases specify a suite of endorsed plugin versions for that Maven release. That way, if I want a stable reproducible build, I just continue to use the

Re: Remove auto-resolution of plugin versions from Maven 2.1

2007-04-13 Thread ArneD
Hi everybody, from a corporate user's point of view, I believe, the following points are important: 1. Corporate users want to be completely decoupled from what's happening on repo1. Many even don't want to proxy repo1 but instead manage their own repository. This is especially true for build

Re: Remove auto-resolution of plugin versions from Maven 2.1

2007-04-13 Thread ArneD
Jason, thanks a lot for your answer. I did not want to suggest that every Maven user should be forced to work decoupled from repo1. But currently it is much harder than it should be, and this should be improved. And I do agree that the separation of the Maven core and the plugins has its

Javadoc-Plugin - enhancement to support different JDK

2007-04-04 Thread ArneD
Dear Maven committers, there is an issue in JIRA to make the Javadoc-Plugin support running Javadoc from a JDK other than the one in JAVA_HOME. This is necessary if you e.g. run your build with JDK 1.4, because it's the default JDK in an organization, and want to build some JDK 1.5 projects on

Re: Towards full ClearCase integration

2007-03-22 Thread ArneD
Emmanuel, I've additionally filed the following issues that further improve the usability and documentation of the ClearCase SCM provider: http://jira.codehaus.org/browse/SCM-289 http://jira.codehaus.org/browse/SCM-290 Is it possible to stage the new site somewhere? Other ClearCase users

Re: Towards full ClearCase integration

2007-03-22 Thread ArneD
Emmanuel Venisse wrote: I'll look at them, thanks. But for Maven-SCM diiscussion, I'd prefer to do it on scm-dev@maven.apache.org Oh, sorry, I wasn't aware that there's a scm-dev list. The reason is that I am using nabble.com, and scm-dev doesn't seem to be listed there... I'll ask the

Re: Towards full ClearCase integration

2007-03-20 Thread ArneD
Jason van Zyl-2 wrote: Arne, Do you have any plans for ClearCase UCM? Jason. No, sorry, I don't. I am doing this for a customer who is using ClearCase SCM, but not UCM. Currently they use ClearCase dynamic views together with scm-local. But they want to have the full ClearCase (SCM)

Re: Towards full ClearCase integration

2007-03-20 Thread ArneD
Emmanuel, I filed the following issue. Could you please have a look at it: http://jira.codehaus.org/browse/SCM-288 Thanks - Arne Emmanuel Venisse wrote: Emmanuel Venisse a écrit : ArneD a écrit : Hi Emmanuel, after SCM-287 has been applied, I still see the following problem

Towards full ClearCase integration

2007-03-20 Thread ArneD
Hi Emmanuel, after SCM-287 has been applied, I still see the following problem with the Maven/Continuum and ClearCase integration. The ClearCase implementation of the checkout command for ClearCase creates a ClearCase snapshot view. Such a snaphsot view is very similiar to a CVS or Subversion

Implemented ClearCase support for checking out from a tag and auto-creation of config specs

2007-03-15 Thread ArneD
Hi Emmanuel and others, I implemented the above mentioned feature. Please have a look at the patch, and apply it. If you apply it, it would be great if you could deploy a new maven-scm SNAPSHOT version to the apache snapshots repository as well. http://jira.codehaus.org/browse/SCM-287 Thanks -