[RESULT] [VOTE] Apache 3.1.0
The vote has passed with the following: +1 Binding: Arnaud, Stephen, Olivier, Hervé +1 Non-binding: Stevo, Anders, Tony, Tamas, Baptiste, Mark, Mirko I'll promote the release in Nexus and update the docs and announce Monday when it's all done. On Jun 30, 2013, at 3:00 PM, Jason van Zyl wrote: > Here are the release bits for 3.1.0: > > Release notes: > https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=18967 > > Staging repository: > https://repository.apache.org/content/repositories/maven-084/ > > Staged distribution: > https://repository.apache.org/content/repositories/maven-084/org/apache/maven/apache-maven/3.1.0/ > > Staged Site: > http://maven.apache.org/ref/3.1.0 > > Thanks, > > Jason > > -- > Jason van Zyl > Founder, Apache Maven > http://twitter.com/jvanzyl > - > > There's no sense in being precise when you don't even know what you're > talking about. > > -- John von Neumann > > > > > Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl - People develop abstractions by generalizing from concrete examples. Every attempt to determine the correct abstraction on paper without actually developing a running system is doomed to failure. No one is that smart. A framework is a resuable design, so you develop it by looking at the things it is supposed to be a design of. The more examples you look at, the more general your framework will be. -- Ralph Johnson & Don Roberts, Patterns for Evolving Frameworks
Re: [RESULT] [VOTE] Apache 3.1.0
On 13 July 2013 14:54, Jason van Zyl wrote: > The vote has passed with the following: > > +1 Binding: Arnaud, Stephen, Olivier, Hervé > +1 Non-binding: Stevo, Anders, Tony, Tamas, Baptiste, Mark, Mirko I voted -1 (non-binding) because of the invalid NOTICE file (amongst other reasons). > > I'll promote the release in Nexus and update the docs and announce Monday > when it's all done. > > On Jun 30, 2013, at 3:00 PM, Jason van Zyl wrote: > >> Here are the release bits for 3.1.0: >> >> Release notes: >> https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=18967 >> >> Staging repository: >> https://repository.apache.org/content/repositories/maven-084/ >> >> Staged distribution: >> https://repository.apache.org/content/repositories/maven-084/org/apache/maven/apache-maven/3.1.0/ >> >> Staged Site: >> http://maven.apache.org/ref/3.1.0 >> >> Thanks, >> >> Jason >> >> -- >> Jason van Zyl >> Founder, Apache Maven >> http://twitter.com/jvanzyl >> - >> >> There's no sense in being precise when you don't even know what you're >> talking about. >> >> -- John von Neumann >> >> >> >> >> > > Thanks, > > Jason > > -- > Jason van Zyl > Founder, Apache Maven > http://twitter.com/jvanzyl > - > > People develop abstractions by generalizing from concrete examples. > Every attempt to determine the correct abstraction on paper without > actually developing a running system is doomed to failure. No one > is that smart. A framework is a resuable design, so you develop it by > looking at the things it is supposed to be a design of. The more examples > you look at, the more general your framework will be. > > -- Ralph Johnson & Don Roberts, Patterns for Evolving Frameworks > > > > > > - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [RESULT] [VOTE] Apache 3.1.0
Sorry about that. I did register the issue and I'll make something to generate the correct attributions for the next release. Hopefully the next one will not take 7 months. I sent the first email out for the first 3.1.0 on December 2nd, 2012 :-) On Jul 13, 2013, at 10:00 AM, sebb wrote: > On 13 July 2013 14:54, Jason van Zyl wrote: >> The vote has passed with the following: >> >> +1 Binding: Arnaud, Stephen, Olivier, Hervé >> +1 Non-binding: Stevo, Anders, Tony, Tamas, Baptiste, Mark, Mirko > > I voted -1 (non-binding) because of the invalid NOTICE file (amongst > other reasons). > >> >> I'll promote the release in Nexus and update the docs and announce Monday >> when it's all done. >> >> On Jun 30, 2013, at 3:00 PM, Jason van Zyl wrote: >> >>> Here are the release bits for 3.1.0: >>> >>> Release notes: >>> https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=18967 >>> >>> Staging repository: >>> https://repository.apache.org/content/repositories/maven-084/ >>> >>> Staged distribution: >>> https://repository.apache.org/content/repositories/maven-084/org/apache/maven/apache-maven/3.1.0/ >>> >>> Staged Site: >>> http://maven.apache.org/ref/3.1.0 >>> >>> Thanks, >>> >>> Jason >>> >>> -- >>> Jason van Zyl >>> Founder, Apache Maven >>> http://twitter.com/jvanzyl >>> - >>> >>> There's no sense in being precise when you don't even know what you're >>> talking about. >>> >>> -- John von Neumann >>> >>> >>> >>> >>> >> >> Thanks, >> >> Jason >> >> -- >> Jason van Zyl >> Founder, Apache Maven >> http://twitter.com/jvanzyl >> - >> >> People develop abstractions by generalizing from concrete examples. >> Every attempt to determine the correct abstraction on paper without >> actually developing a running system is doomed to failure. No one >> is that smart. A framework is a resuable design, so you develop it by >> looking at the things it is supposed to be a design of. The more examples >> you look at, the more general your framework will be. >> >> -- Ralph Johnson & Don Roberts, Patterns for Evolving Frameworks >> >> >> >> >> >> > > - > 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, Apache Maven http://twitter.com/jvanzyl - A man enjoys his work when he understands the whole and when he is responsible for the quality of the whole -- Christopher Alexander, A Pattern Language
Re: [RESULT] [VOTE] Apache 3.1.0
On 13 July 2013 15:11, Jason van Zyl wrote: > Sorry about that. I did register the issue OK. > and I'll make something to generate the correct attributions for the next > release. There should be need to auto-generate anything for the source release; just ensure the correct N&L files are present in the top-level of SCM. This is required anyway as the SCM is effectively another published source. Once established, the files will need to change rarely if ever. Similarly for the binary release, the NOTICE file may well need to be different, but won't change often. It's not a trivial matter for a program determine what goes in the NOTICE file from machine-readable data. > Hopefully the next one will not take 7 months. I sent the first email out for > the first 3.1.0 on December 2nd, 2012 :-) > > On Jul 13, 2013, at 10:00 AM, sebb wrote: > >> On 13 July 2013 14:54, Jason van Zyl wrote: >>> The vote has passed with the following: >>> >>> +1 Binding: Arnaud, Stephen, Olivier, Hervé >>> +1 Non-binding: Stevo, Anders, Tony, Tamas, Baptiste, Mark, Mirko >> >> I voted -1 (non-binding) because of the invalid NOTICE file (amongst >> other reasons). >> >>> >>> I'll promote the release in Nexus and update the docs and announce Monday >>> when it's all done. >>> >>> On Jun 30, 2013, at 3:00 PM, Jason van Zyl wrote: >>> Here are the release bits for 3.1.0: Release notes: https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=18967 Staging repository: https://repository.apache.org/content/repositories/maven-084/ Staged distribution: https://repository.apache.org/content/repositories/maven-084/org/apache/maven/apache-maven/3.1.0/ Staged Site: http://maven.apache.org/ref/3.1.0 Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl - There's no sense in being precise when you don't even know what you're talking about. -- John von Neumann >>> >>> Thanks, >>> >>> Jason >>> >>> -- >>> Jason van Zyl >>> Founder, Apache Maven >>> http://twitter.com/jvanzyl >>> - >>> >>> People develop abstractions by generalizing from concrete examples. >>> Every attempt to determine the correct abstraction on paper without >>> actually developing a running system is doomed to failure. No one >>> is that smart. A framework is a resuable design, so you develop it by >>> looking at the things it is supposed to be a design of. The more examples >>> you look at, the more general your framework will be. >>> >>> -- Ralph Johnson & Don Roberts, Patterns for Evolving Frameworks >>> >>> >>> >>> >>> >>> >> >> - >> 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, Apache Maven > http://twitter.com/jvanzyl > - > > A man enjoys his work when he understands the whole and when he > is responsible for the quality of the whole > > -- Christopher Alexander, A Pattern Language > > > > > > - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
RE: How Maven works - definitions
If you want to discover how a house was built you need to talk to an Architect The Architecture of maven is a loose Framework which constitute One of 3 default Maven lifecycles http://maven.apache.org/ref/3.0.5/maven-core/lifecycles.html Each Maven lifecycle in turn consists of one or more phases which will allow multiple Modello architected plugins (spec v 4.0.0 of Modello) to be bound to that phase in order to execute the plugins goal for their Mojo class http://www.maestrodev.com/better-builds-with-maven/creating-applications-with-maven/utilizing-the-build-life-cycle/ In order for use to provide further clarification we would need to know which tasks you wish to run HTH Martin Gainty __ Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. > Date: Mon, 8 Jul 2013 07:01:18 +0930 > Subject: Re: How Maven works - definitions > From: baerr...@gmail.com > To: dev@maven.apache.org > > On 8 July 2013 04:01, Mirko Friedenhagen wrote: > > Hello, > > > > first of all, thanks for your replies. I think it would help very much > > if an introductory would be at the plugin development page[1] to get > > the big picture. Or even be repeated at the the run[2] page. > > > > Running Maven is trivial until you encounter problems or wish to > > extend stuff. I deal a lot with supporting our department (roughly 200 > > developers, 150 of whom are using Maven) and I am always reiterating > > explaining the basic glossary (phase, lifecycle, goal). > > > > While the "Complete reference" by Sonatype is great once you know the > > basics, it is quite extensive and not every application developer > > wants or needs to delve throught it :-) > > I will agree the documentation could be improved. > > I've also said in the past that one of Maven's problems is that it > just works for most people. > > Compare that to Ant where before you can build a project you must read > the README, configure your project settings file and then try to > build, often trouble shooting by looking at the Ant website. This > means the average user of Ant has picked up more stuff because they > are forced to. > > In Maven only the person who is modifying the poms generally acquires > more in depth knowledge of Maven - including terminology. > > Which means when someone does need to work out what went wrong there > is a steep learning curve because it was not amortized over time. > > Ideas on how to fix that are welcome. > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org >
Re: [RESULT] [VOTE] Apache 3.1.0
I will try and automate for everyone to have a correct set of attributions. If you want to manually update the correct files that's fine too. On Jul 13, 2013, at 11:24 AM, sebb wrote: > On 13 July 2013 15:11, Jason van Zyl wrote: >> Sorry about that. I did register the issue > > OK. > >> and I'll make something to generate the correct attributions for the next >> release. > > There should be need to auto-generate anything for the source release; > just ensure the correct N&L files are present in the top-level of SCM. > This is required anyway as the SCM is effectively another published > source. Once established, the files will need to change rarely if > ever. > > Similarly for the binary release, the NOTICE file may well need to be > different, but won't change often. > It's not a trivial matter for a program determine what goes in the > NOTICE file from machine-readable data. > >> Hopefully the next one will not take 7 months. I sent the first email out >> for the first 3.1.0 on December 2nd, 2012 :-) >> >> On Jul 13, 2013, at 10:00 AM, sebb wrote: >> >>> On 13 July 2013 14:54, Jason van Zyl wrote: The vote has passed with the following: +1 Binding: Arnaud, Stephen, Olivier, Hervé +1 Non-binding: Stevo, Anders, Tony, Tamas, Baptiste, Mark, Mirko >>> >>> I voted -1 (non-binding) because of the invalid NOTICE file (amongst >>> other reasons). >>> I'll promote the release in Nexus and update the docs and announce Monday when it's all done. On Jun 30, 2013, at 3:00 PM, Jason van Zyl wrote: > Here are the release bits for 3.1.0: > > Release notes: > https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=18967 > > Staging repository: > https://repository.apache.org/content/repositories/maven-084/ > > Staged distribution: > https://repository.apache.org/content/repositories/maven-084/org/apache/maven/apache-maven/3.1.0/ > > Staged Site: > http://maven.apache.org/ref/3.1.0 > > Thanks, > > Jason > > -- > Jason van Zyl > Founder, Apache Maven > http://twitter.com/jvanzyl > - > > There's no sense in being precise when you don't even know what you're > talking about. > > -- John von Neumann > > > > > Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl - People develop abstractions by generalizing from concrete examples. Every attempt to determine the correct abstraction on paper without actually developing a running system is doomed to failure. No one is that smart. A framework is a resuable design, so you develop it by looking at the things it is supposed to be a design of. The more examples you look at, the more general your framework will be. -- Ralph Johnson & Don Roberts, Patterns for Evolving Frameworks >>> >>> - >>> 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, Apache Maven >> http://twitter.com/jvanzyl >> - >> >> A man enjoys his work when he understands the whole and when he >> is responsible for the quality of the whole >> >> -- Christopher Alexander, A Pattern Language >> >> >> >> >> >> > > - > 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, Apache Maven http://twitter.com/jvanzyl - The modern conservative is engaged in one of man's oldest exercises in moral philosophy; that is, the search for a superior moral justification for selfishness. -- John Kenneth Galbraith
Re: [RESULT] [VOTE] Apache 3.1.0
Jason, On Jul 13, 2013, at 12:44 PM, Jason van Zyl wrote: > I will try and automate for everyone to have a correct set of attributions. > > If you want to manually update the correct files that's fine too. I think this is now done on master, but requires a release of the remote-resources. Just haven't had time to do it. Dan > > On Jul 13, 2013, at 11:24 AM, sebb wrote: > >> On 13 July 2013 15:11, Jason van Zyl wrote: >>> Sorry about that. I did register the issue >> >> OK. >> >>> and I'll make something to generate the correct attributions for the next >>> release. >> >> There should be need to auto-generate anything for the source release; >> just ensure the correct N&L files are present in the top-level of SCM. >> This is required anyway as the SCM is effectively another published >> source. Once established, the files will need to change rarely if >> ever. >> >> Similarly for the binary release, the NOTICE file may well need to be >> different, but won't change often. >> It's not a trivial matter for a program determine what goes in the >> NOTICE file from machine-readable data. >> >>> Hopefully the next one will not take 7 months. I sent the first email out >>> for the first 3.1.0 on December 2nd, 2012 :-) >>> >>> On Jul 13, 2013, at 10:00 AM, sebb wrote: >>> On 13 July 2013 14:54, Jason van Zyl wrote: > The vote has passed with the following: > > +1 Binding: Arnaud, Stephen, Olivier, Hervé > +1 Non-binding: Stevo, Anders, Tony, Tamas, Baptiste, Mark, Mirko I voted -1 (non-binding) because of the invalid NOTICE file (amongst other reasons). > > I'll promote the release in Nexus and update the docs and announce Monday > when it's all done. > > On Jun 30, 2013, at 3:00 PM, Jason van Zyl wrote: > >> Here are the release bits for 3.1.0: >> >> Release notes: >> https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=18967 >> >> Staging repository: >> https://repository.apache.org/content/repositories/maven-084/ >> >> Staged distribution: >> https://repository.apache.org/content/repositories/maven-084/org/apache/maven/apache-maven/3.1.0/ >> >> Staged Site: >> http://maven.apache.org/ref/3.1.0 >> >> Thanks, >> >> Jason >> >> -- >> Jason van Zyl >> Founder, Apache Maven >> http://twitter.com/jvanzyl >> - >> >> There's no sense in being precise when you don't even know what you're >> talking about. >> >> -- John von Neumann >> >> >> >> >> > > Thanks, > > Jason > > -- > Jason van Zyl > Founder, Apache Maven > http://twitter.com/jvanzyl > - > > People develop abstractions by generalizing from concrete examples. > Every attempt to determine the correct abstraction on paper without > actually developing a running system is doomed to failure. No one > is that smart. A framework is a resuable design, so you develop it by > looking at the things it is supposed to be a design of. The more examples > you look at, the more general your framework will be. > > -- Ralph Johnson & Don Roberts, Patterns for Evolving Frameworks > > > > > > - 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, Apache Maven >>> http://twitter.com/jvanzyl >>> - >>> >>> A man enjoys his work when he understands the whole and when he >>> is responsible for the quality of the whole >>> >>> -- Christopher Alexander, A Pattern Language >>> >>> >>> >>> >>> >>> >> >> - >> 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, Apache Maven > http://twitter.com/jvanzyl > - > > The modern conservative is engaged in one of man's oldest exercises in moral > philosophy; that is, > the search for a superior moral justification for selfishness. > > -- John Kenneth Galbraith > > > > > > -- Daniel Kulp dk...@apache.org - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com
Re: [VOTE] Release Apache Maven Enforcer version 1.3.1
Op Fri, 12 Jul 2013 23:31:47 +0200 schreef Arnaud Héritier : What are the SCM coordinates? Where is the KEYS file? sebb is a bot in fact ;-P :) so I don't need to repeat myself explaining why these things aren't mentioned. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: MNGSITE-152 - Maven sites don't follow the rules on how to link to the license
How about adding the licence link to the site.xml [1] of maven-parent? Then we'd have it once for all the plugins developed using that parent pom. Or is there any remote reason why someone would use that parent but another licence? If I hear no objections, I'll add the section there. Andreas [1] https://svn.apache.org/repos/asf/maven/pom/trunk/maven/src/site/site.xml 2013/7/13 sebb > As the subject says. > > This was raised over a year ago and has not even attracted a single > comment. > > Please could someone look at the issue? > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
Re: How Maven works - definitions
Martin, my point is mostly that while a lot of documentation is available, a short summary of the base concepts is hidden in all of this pages. Everything I wrote in my first email may be found in these pages, but I feel it is somewhat hidden :-). Regards Mirko -- http://illegalstateexception.blogspot.com/ https://github.com/mfriedenhagen/ https://bitbucket.org/mfriedenhagen/ On Sat, Jul 13, 2013 at 5:30 PM, Martin Gainty wrote: > If you want to discover how a house was built you need to talk to an Architect > > The Architecture of maven is a loose Framework which constitute One of 3 > default Maven lifecycles > http://maven.apache.org/ref/3.0.5/maven-core/lifecycles.html > > Each Maven lifecycle in turn consists of one or more phases which will allow > multiple Modello architected plugins (spec v 4.0.0 of Modello) to be bound to > that phase in order to execute the plugins goal for their Mojo class > http://www.maestrodev.com/better-builds-with-maven/creating-applications-with-maven/utilizing-the-build-life-cycle/ > > In order for use to provide further clarification we would need to know > which tasks you wish to run > > HTH > Martin Gainty > __ > Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité > > Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger > sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung > oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich > dem Austausch von Informationen und entfaltet keine rechtliche > Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen > wir keine Haftung fuer den Inhalt uebernehmen. > Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le > destinataire prévu, nous te demandons avec bonté que pour satisfaire informez > l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci > est interdite. Ce message sert à l'information seulement et n'aura pas > n'importe quel effet légalement obligatoire. Étant donné que les email > peuvent facilement être sujets à la manipulation, nous ne pouvons accepter > aucune responsabilité pour le contenu fourni. > > >> Date: Mon, 8 Jul 2013 07:01:18 +0930 >> Subject: Re: How Maven works - definitions >> From: baerr...@gmail.com >> To: dev@maven.apache.org >> >> On 8 July 2013 04:01, Mirko Friedenhagen wrote: >> > Hello, >> > >> > first of all, thanks for your replies. I think it would help very much >> > if an introductory would be at the plugin development page[1] to get >> > the big picture. Or even be repeated at the the run[2] page. >> > >> > Running Maven is trivial until you encounter problems or wish to >> > extend stuff. I deal a lot with supporting our department (roughly 200 >> > developers, 150 of whom are using Maven) and I am always reiterating >> > explaining the basic glossary (phase, lifecycle, goal). >> > >> > While the "Complete reference" by Sonatype is great once you know the >> > basics, it is quite extensive and not every application developer >> > wants or needs to delve throught it :-) >> >> I will agree the documentation could be improved. >> >> I've also said in the past that one of Maven's problems is that it >> just works for most people. >> >> Compare that to Ant where before you can build a project you must read >> the README, configure your project settings file and then try to >> build, often trouble shooting by looking at the Ant website. This >> means the average user of Ant has picked up more stuff because they >> are forced to. >> >> In Maven only the person who is modifying the poms generally acquires >> more in depth knowledge of Maven - including terminology. >> >> Which means when someone does need to work out what went wrong there >> is a steep learning curve because it was not amortized over time. >> >> Ideas on how to fix that are welcome. >> >> - >> 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 Enforcer version 1.3.1
Robert, I tried to run the integration-tests of the extra-enforcer-rules but most ITs just fail: [ERROR] The following builds failed: [ERROR] * circular-simple/pom.xml [ERROR] * enforce-bytecode-version-jdkVersionOption/pom.xml [ERROR] * enforce-bytecode-version-with-banned-deps/pom.xml [ERROR] * enforce-bytecode-version-wo-banned-deps/pom.xml [ERROR] * mojo-1682/pom.xml [ERROR] * mojo-1731/pom.xml [ERROR] * mojo-1744/pom.xml [ERROR] * mojo-1769/pom.xml [ERROR] * mojo-1799/pom.xml [ERROR] * smokes/pom.xml I modified the pom.xml: [mirko@borg extra-enforcer-rules]$ svn diff pom.xml Index: pom.xml === --- pom.xml (revision 18522) +++ pom.xml (working copy) @@ -140,7 +140,7 @@ verify true -1.0 +1.3.1 and added the staging repository to src/it/settings.xml like this: Index: src/it/settings.xml === --- src/it/settings.xml (revision 18522) +++ src/it/settings.xml (working copy) @@ -1,5 +1,38 @@ + +apache-pre + + + + +apache-pre + + +apache-pre + +true + + +false + + https://repository.apache.org/content/repositories/maven-140/ + + + + +apache-pre + +true + + +false + + https://repository.apache.org/content/repositories/maven-140/ + + + + -1 (non-binding) from me. Regards Mirko -- http://illegalstateexception.blogspot.com/ https://github.com/mfriedenhagen/ https://bitbucket.org/mfriedenhagen/ On Sat, Jul 13, 2013 at 7:01 PM, Robert Scholte wrote: > Op Fri, 12 Jul 2013 23:31:47 +0200 schreef Arnaud Héritier > : > > >>> >>> What are the SCM coordinates? >>> Where is the KEYS file? >>> >>> >> sebb is a bot in fact ;-P > > > > :) so I don't need to repeat myself explaining why these things aren't > mentioned. > > > - > 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 Enforcer version 1.3.1
On Sat, Jul 13, 2013 at 7:01 PM, Robert Scholte wrote: > Op Fri, 12 Jul 2013 23:31:47 +0200 schreef Arnaud Héritier < > aherit...@gmail.com>: > > What are the SCM coordinates? >>> Where is the KEYS file? >> >> >> > sebb is a bot in fact ;-P > > > :) so I don't need to repeat myself explaining why these things aren't > mentioned. Of course not: Laziness! :-)
Re: svn commit: r1502830 - /maven/site/trunk/content/apt/guides/mini/guide-3rd-party-jars-local.apt
On 13 July 2013 19:01, wrote:
> Author: rfscholte
> Date: Sat Jul 13 18:01:39 2013
> New Revision: 1502830
>
> URL: http://svn.apache.org/r1502830
> Log:
> [MINSTALL-95] Enhance documentation of install-file
>
> Modified:
> maven/site/trunk/content/apt/guides/mini/guide-3rd-party-jars-local.apt
>
> Modified:
> maven/site/trunk/content/apt/guides/mini/guide-3rd-party-jars-local.apt
> URL:
> http://svn.apache.org/viewvc/maven/site/trunk/content/apt/guides/mini/guide-3rd-party-jars-local.apt?rev=1502830&r1=1502829&r2=1502830&view=diff
> ==
> --- maven/site/trunk/content/apt/guides/mini/guide-3rd-party-jars-local.apt
> (original)
> +++ maven/site/trunk/content/apt/guides/mini/guide-3rd-party-jars-local.apt
> Sat Jul 13 18:01:39 2013
> @@ -2,17 +2,19 @@
> Guide to installing 3rd party JARs
> --
> Jason van Zyl
> + Robert Scholte
> --
> - 12 October 2005
> + 13 July 2013
> --
>
> Guide to installing 3rd party JARs
>
> - Often times you will have 3rd party JARs that you need to put in your local
> repository for use in your
> - builds. The JARs must be placed in the local repository in the correct
> place in order for it to be correctly
> - picked up by Maven. To make this easier, and less error prone, we have
> provide a goal in the install plug-in
> - which should make this relatively painless. To install a JAR in the local
> repository use the following
> - command:
> + Although rarely, but sometimes you will have 3rd party JARs that you need
> to put in your local repository for use in your
s/Although rarely, but sometimes you will have/Sometimes there will be/
> + builds, since they don't exist in any public repository like
> {{{http://search.maven.org}Maven Central}}.
> + The JARs must be placed in the local repository in the correct place in
> order for it to be correctly
> + picked up by Apache Maven. To make this easier, and less error prone, we
> have provide a goal in the
Grammar:
s/we have provide/we have provided/
> +
> {{{http://maven.apache.org/plugins/maven-install-plugin/}maven-install-plugin}}
> which should make this relatively painless.
> + To install a JAR in the local repository use the following command:
>
> ++
>
> @@ -20,3 +22,22 @@ mvn install:install-file -Dfile= -DartifactId= -Dversion= -Dpackaging=
>
> ++
> +
> + If there's a pom-file as well, you can install it with the following
> command:
> +
> +++
> +
> +mvn install:install-file -Dfile= -DpomFile=
> +
> +++
> +
> + With version 2.5 of the maven-install-plugin it gets even better. If the
> JAR was built by Apache Maven, it'll contain a
> + pom.xml in a subfolder of the META-INF directory, which will be read by
> default. In that case, all you need to do is:
> +
> +++
> +
> +mvn install:install-file -Dfile=
> +
> +++
> +
> +
>
>
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Re: How Maven works - definitions
On 14 July 2013 04:52, Mirko Friedenhagen wrote: > Martin, > > my point is mostly that while a lot of documentation is available, a > short summary of the base concepts is hidden in all of this pages. > Everything I wrote in my first email may be found in these pages, but > I feel it is somewhat hidden :-). > Regards Mirko Please feel free to provide enlightenment via patches. A new set of eyes can help find the gaps that matter and help provide the details needed to explain them. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
