Re: [VOTE] Retire maven-idea-plugin

+1 On 20/07/2013, at 3:01 AM, Dennis Lundberg wrote: > Hi > > It has been almost five years since I made the last release of > maven-idea-plugin. The features in IDEA to integrate Maven has been greatly > improved since then, making our own plugin obsolete. I therefor propose > that we retire m

Re: [VOTE] Retire Maven One Plugin

(Re-posting to dev@, got confused by the cross-posting of the vote...) +1 Thanks Dennis! - Brett On 20/07/2013, at 7:13 PM, Dennis Lundberg wrote: > Hi, > > Now that we have Maven 1 at End-Of-Life, I think it's time to retire > Maven One Plugin as well. It has been almost six years since the

Re: [VOTE] Retire Maven Model Converter

+1 On 21/07/2013, at 3:26 AM, Dennis Lundberg wrote: > Hi, > > The only consumer of Maven Model Converter we have left at the Apache > Maven project is Maven One Plugin. If the vote for the retirement of > Maven One Plugin succeeds we should also retire Maven Model Converter. > The last release

Re: [maven-scm] add some debugging but still does not work locally on osx (665256d)

Hi, @Domi, we usually mailing list to communicate here. So yes for some reasons I don't know, this fail on my laptop but work fine on all others. (the famous: It doesn't work on my machine :-) ) 2013/7/22 Dominik Bartholdi > @olamy is there anyone we could ask for h

Re: RAT setup

Here you go: https://issues.apache.org/jira/browse/RAT-145 For the record the maven-license-plugin works very well and can insert the correct licenses as well. On Jul 21, 2013, at 5:19 PM, sebb wrote: > On 21 July 2013 21:23, Jason van Zyl wrote: >> >> On Jul 21, 2013, at 3:14 PM, sebb wrot

Re: svn commit: r1505380 - in /maven/resources/trunk: apache-jar-resource-bundle/src/main/resources/META-INF/NOTICE.vm apache-jar-txt-resource-bundle/src/main/resources/META-INF/NOTICE.txt.vm pom.xml

On Sun, Jul 21, 2013 at 9:19 PM, sebb wrote: > On 21 July 2013 14:39, wrote: >> Author: dennisl >> Date: Sun Jul 21 13:39:23 2013 >> New Revision: 1505380 >> >> URL: http://svn.apache.org/r1505380 >> Log: >> Remove spurious blank lines in generated NOTICE file. >> >> Modified: >> >> maven/r

Re: RAT setup

On 21 July 2013 21:23, Jason van Zyl wrote: > > On Jul 21, 2013, at 3:14 PM, sebb wrote: > >> On 21 July 2013 19:47, Jason van Zyl wrote: >>> >>> On Jul 21, 2013, at 2:29 PM, Stephen Connolly >>> wrote: >>> Revert my change upping to RAT 0.9 Stupid plugin has major regression in

Re: RAT setup

On Jul 21, 2013, at 3:14 PM, sebb wrote: > On 21 July 2013 19:47, Jason van Zyl wrote: >> >> On Jul 21, 2013, at 2:29 PM, Stephen Connolly >> wrote: >> >>> Revert my change upping to RAT 0.9 >>> >>> Stupid plugin has major regression in performance, but 0.8 needs excludes >>> for git >>>

Re: svn commit: r1505380 - in /maven/resources/trunk: apache-jar-resource-bundle/src/main/resources/META-INF/NOTICE.vm apache-jar-txt-resource-bundle/src/main/resources/META-INF/NOTICE.txt.vm pom.xml

On 21 July 2013 14:39, wrote: > Author: dennisl > Date: Sun Jul 21 13:39:23 2013 > New Revision: 1505380 > > URL: http://svn.apache.org/r1505380 > Log: > Remove spurious blank lines in generated NOTICE file. > > Modified: > > maven/resources/trunk/apache-jar-resource-bundle/src/main/resource

Re: RAT setup

On 21 July 2013 19:47, Jason van Zyl wrote: > > On Jul 21, 2013, at 2:29 PM, Stephen Connolly > wrote: > >> Revert my change upping to RAT 0.9 >> >> Stupid plugin has major regression in performance, but 0.8 needs excludes >> for git >> > > Yup, just noticed that as well. After trying to attempt

Re: [3/3] git commit: Merge branch 'master' of https://git-wip-us.apache.org/repos/asf/maven

I should, sorry about that. On Jul 21, 2013, at 2:54 PM, Hervé BOUTEMY wrote: > what's this commit? > I'm not a git master, but I suppose a rebase before committing should avoid > such things, no? > > Regards, > > Hervé > > Le dimanche 21 juillet 2013 18:10:09 jvan...@apache.org a écrit : >>

Re: [3/3] git commit: Merge branch 'master' of https://git-wip-us.apache.org/repos/asf/maven

what's this commit? I'm not a git master, but I suppose a rebase before committing should avoid such things, no? Regards, Hervé Le dimanche 21 juillet 2013 18:10:09 jvan...@apache.org a écrit : > Merge branch 'master' of https://git-wip-us.apache.org/repos/asf/maven > > > Project: http://git-

Re: RAT setup

On Jul 21, 2013, at 2:29 PM, Stephen Connolly wrote: > Revert my change upping to RAT 0.9 > > Stupid plugin has major regression in performance, but 0.8 needs excludes > for git > Yup, just noticed that as well. After trying to attempt to release my distribution 4 times and the RAT plugin b

Re: svn commit: r1505129 - in /maven/plugins/trunk/maven-install-plugin: LICENSE NOTICE

On 21 July 2013 14:05, Olivier Lamy wrote: > 2013/7/21 sebb : >> On 21 July 2013 13:30, Robert Scholte wrote: >>> "Also, the files change relatively rarely once set up." >>> >>> I thought you strongly believed in Murphy's Law... >> >> Not sure how that is relevant. >> >>> >>> I agree with Dennis:

Re: Do we document the protocol with the repo manager? And what about deploy:deploy-file and multiple attached artifacts?

On Sun, Jul 21, 2013 at 2:29 PM, Benson Margulies wrote: > > > > On Sun, Jul 21, 2013 at 2:26 PM, Stephen Connolly < > stephen.alan.conno...@gmail.com> wrote: > >> On Sunday, 21 July 2013, Benson Margulies wrote: >> >> > On Sun, Jul 21, 2013 at 1:52 PM, Robert Scholte > >> > >wrote: >> > >> > > H

Re: Do we document the protocol with the repo manager? And what about deploy:deploy-file and multiple attached artifacts?

On Sun, Jul 21, 2013 at 2:26 PM, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: > On Sunday, 21 July 2013, Benson Margulies wrote: > > > On Sun, Jul 21, 2013 at 1:52 PM, Robert Scholte > > >wrote: > > > > > Hi Benson, > > > > > > I don't understand, because deploy:deploy-file should

Re: RAT setup

Revert my change upping to RAT 0.9 Stupid plugin has major regression in performance, but 0.8 needs excludes for git If I'd had notice I'd have reverted it my self but on a phone so no access to revert it... Once they get a proper usable release we *should* be ok... Though they don't seem to know

Re: Do we document the protocol with the repo manager? And what about deploy:deploy-file and multiple attached artifacts?

On Sunday, 21 July 2013, Benson Margulies wrote: > On Sun, Jul 21, 2013 at 1:52 PM, Robert Scholte > > >wrote: > > > Hi Benson, > > > > I don't understand, because deploy:deploy-file should be able to upload > > pom + artifact + classified-artifacts at once. > > > > There's no provision for uplo

Re: Do we document the protocol with the repo manager? And what about deploy:deploy-file and multiple attached artifacts?

On Sun, Jul 21, 2013 at 1:52 PM, Robert Scholte wrote: > Hi Benson, > > I don't understand, because deploy:deploy-file should be able to upload > pom + artifact + classified-artifacts at once. > There's no provision for uploading one pom plus multiple classified artifacts in a single transation.

Re: Do we document the protocol with the repo manager? And what about deploy:deploy-file and multiple attached artifacts?

Hi Benson, I don't understand, because deploy:deploy-file should be able to upload pom + artifact + classified-artifacts at once. Robert Op Sun, 21 Jul 2013 19:40:04 +0200 schreef Benson Margulies : Other than in the source of the deploy plugin, do we have a document for 'deploy'? I s

RAT setup

I just tried to cut a distribution using the existing Maven POM and it let me get through the release:prepare phase without any issues and then failed during the release:perform phase. I have no idea how RAT works, or who set it up but that behavior is sub-optimal. Would probably be all right to

Re: The command line used by Maven Javadoc Plugin

Hi Dennis, The ${project.reporting.outputDirectory}/apidocs is the working directory, whereas the javadoc executable is used with its absolute path. So in the end it will often be: cd ${project.reporting.outputDirectory}/apidocs %JAVA_HOME%\bin\javadoc.exe @options @packages | @argfile I s

Do we document the protocol with the repo manager? And what about deploy:deploy-file and multiple attached artifacts?

Other than in the source of the deploy plugin, do we have a document for 'deploy'? I sporadically run into the fact that the command-line deploy plugin isn't so hot when one has multiple classified objects. On the one hand, I'm thinking of creating deploy:deploy-files (note the 's') with some sch

The command line used by Maven Javadoc Plugin

Hi I got sidetracked by this and cannot let go of it. On the index page of Maven Javadoc Plugin http://maven.apache.org/plugins/maven-javadoc-plugin/ it says this: - ...the Javadoc Plugin generates argument files and calls the Javadoc tool as follow: #${project.reporting.outputDirectory}/api

Issue management and documentation for Apache resources, such as apache-jar-resource-bundle

Hi, I had a look at, and fixed https://jira.codehaus.org/browse/MRRESOURCES-69 When I first saw the issue I thought, hey this is in the wrong JIRA project and went about trying to move it to the correct one. But there is no IssueManagement in any of the POMs at https://svn.apache.org/viewvc/maven

Re: svn commit: r1505129 - in /maven/plugins/trunk/maven-install-plugin: LICENSE NOTICE

2013/7/21 sebb : > On 21 July 2013 13:30, Robert Scholte wrote: >> "Also, the files change relatively rarely once set up." >> >> I thought you strongly believed in Murphy's Law... > > Not sure how that is relevant. > >> >> I agree with Dennis: let's ask for the *facts* why these files are required

Re: svn commit: r1505129 - in /maven/plugins/trunk/maven-install-plugin: LICENSE NOTICE

On 21 July 2013 13:38, Daniel Kulp wrote: > > Also keep in mind, there is likely a large difference between the > LICENSE/NOTICE files that would go into a "source release" than would go into > the binary convenience releases. 90% of the source NOTICE/LICESE files are > just plain Apache Lice

Re: svn commit: r1505129 - in /maven/plugins/trunk/maven-install-plugin: LICENSE NOTICE

On 21 July 2013 13:30, Robert Scholte wrote: > "Also, the files change relatively rarely once set up." > > I thought you strongly believed in Murphy's Law... Not sure how that is relevant. > > I agree with Dennis: let's ask for the *facts* why these files are required > here. Robert already quo

Re: svn commit: r1505129 - in /maven/plugins/trunk/maven-install-plugin: LICENSE NOTICE

On 21 July 2013 13:22, Robert Scholte wrote: > Op Sun, 21 Jul 2013 14:10:12 +0200 schreef sebb : > > >> On 21 July 2013 12:39, Robert Scholte wrote: >>> >>> Having a copy here does indeed mean we have to maintain it, unless we use >>> svn:externals (but better not do that). >>> If I'm correct, bo

Re: svn commit: r1505129 - in /maven/plugins/trunk/maven-install-plugin: LICENSE NOTICE

Also keep in mind, there is likely a large difference between the LICENSE/NOTICE files that would go into a "source release" than would go into the binary convenience releases. 90% of the source NOTICE/LICESE files are just plain Apache License and the simple 4 line NOTICE. For the binary

Re: svn commit: r1505129 - in /maven/plugins/trunk/maven-install-plugin: LICENSE NOTICE

"Also, the files change relatively rarely once set up." I thought you strongly believed in Murphy's Law... I agree with Dennis: let's ask for the *facts* why these files are required here. If it is because they need to be included in the source-release file, then add them additionally inste

Re: svn commit: r1505129 - in /maven/plugins/trunk/maven-install-plugin: LICENSE NOTICE

Op Sun, 21 Jul 2013 14:10:12 +0200 schreef sebb : On 21 July 2013 12:39, Robert Scholte wrote: Having a copy here does indeed mean we have to maintain it, unless we use svn:externals (but better not do that). If I'm correct, both files contain custom 'fields', referring to the name of the

Re: svn commit: r1505129 - in /maven/plugins/trunk/maven-install-plugin: LICENSE NOTICE

On 21 July 2013 13:09, Dennis Lundberg wrote: > Hi > > Has anyone asked if we can use generated files instead? > > Many of the ASF rules are written by people that have not concidered the > fact that things such as these can be automated. Therefore many of these > rules are stated in a way that do

Re: svn commit: r1505129 - in /maven/plugins/trunk/maven-install-plugin: LICENSE NOTICE

On 21 July 2013 12:39, Robert Scholte wrote: > Having a copy here does indeed mean we have to maintain it, unless we use > svn:externals (but better not do that). > If I'm correct, both files contain custom 'fields', referring to the name of > the project and/or a year or date. "both files" - whi

Re: svn commit: r1505129 - in /maven/plugins/trunk/maven-install-plugin: LICENSE NOTICE

Hi Has anyone asked if we can use generated files instead? Many of the ASF rules are written by people that have not concidered the fact that things such as these can be automated. Therefore many of these rules are stated in a way that does not fit directly into the Maven way of doing things. We

Re: svn commit: r1505129 - in /maven/plugins/trunk/maven-install-plugin: LICENSE NOTICE

Having a copy here does indeed mean we have to maintain it, unless we use svn:externals (but better not do that). If I'm correct, both files contain custom 'fields', referring to the name of the project and/or a year or date. Also, I'm always having trouble with year ranges: suppose the range

Re: svn commit: r1505129 - in /maven/plugins/trunk/maven-install-plugin: LICENSE NOTICE

On 21 July 2013 11:48, Olivier Lamy wrote: > Damned there are plenty of Apache projects which don't do that :-) They will have to be fixed over time. > But in this case the plugin maven-remote-resources-plugin doesn't have > to be used anymore? > Because now we can have duplicate N&L with possib

Re: svn commit: r1505129 - in /maven/plugins/trunk/maven-install-plugin: LICENSE NOTICE

Damned there are plenty of Apache projects which don't do that :-) But in this case the plugin maven-remote-resources-plugin doesn't have to be used anymore? Because now we can have duplicate N&L with possible different content. As one will be maintained manually which mean we can miss to add cont

Re: svn commit: r1505129 - in /maven/plugins/trunk/maven-install-plugin: LICENSE NOTICE

From http://www.apache.org/dev/licensing-howto.html#source-tree-location "Location Within the Source Tree LICENSE and NOTICE belong at the top level of the source tree. They may be named LICENSE.txt and NOTICE.txt, but the bare names are preferred." If you consider a release root as the top

Re: [VOTE] Retire Maven Model Converter

+1 Ralph On Jul 20, 2013, at 10:26 AM, Dennis Lundberg wrote: > Hi, > > The only consumer of Maven Model Converter we have left at the Apache > Maven project is Maven One Plugin. If the vote for the retirement of > Maven One Plugin succeeds we should also retire Maven Model Converter. > The las

Re: [VOTE] Retire Maven One Plugin

+1 Ralph On Jul 20, 2013, at 2:13 AM, Dennis Lundberg wrote: > Hi, > > Now that we have Maven 1 at End-Of-Life, I think it's time to retire > Maven One Plugin as well. It has been almost six years since the last > release. I therefor propose that we retire maven-one-plugin. > > http://maven.ap

Re: [VOTE] Retire Maven Model Converter

+1 On Saturday, 20 July 2013, Dennis Lundberg wrote: > Hi, > > The only consumer of Maven Model Converter we have left at the Apache > Maven project is Maven One Plugin. If the vote for the retirement of > Maven One Plugin succeeds we should also retire Maven Model Converter. > The last release w