[RESULT][VOTE] Release Apache Maven Invoker Plugin version 1.9

Hi, the vote has passed with the following results: +1 (binding): Kristian Rosenvold, Benson Margulies, Hervé Boutemy 0: None +1 (non binding): None. I will promote the artifacts to the central repo. Kind regards Karl-Heinz Marbaise On 6/28/14 12:04 PM, Karl Heinz Marbaise wrote: Hi, We so

Using Maven archetype for dynamic file creation

I am using maven archetypes for generation of code and as given they also use Velocity. Velocity can be used for dynamic file generation, it can use java objects and use there methods, fields etc to generate dynamic file. However as far

Re: Using Markdown

So my little experiment today was to convert some documents in the site to Markdown and see what tools were available for editing. So I pushed a clone of the site to Github: https://github.com/jvanzyl/maven-site/blob/master/content/markdown/what-is-maven.md Even just viewing that is nice for pe

[RESULT] [VOTE] Release Apache Doxia base and Site Tools version 1.6

Hi, The vote has passed with the following result: +1 (binding): Robert Scholte, Kristian Rosenvold, Hervé Boutemy +1 (non binding): Karl-Heinz Marbaise, Michael Osipov, I will promote the artifacts to the central repo.

Re: [VOTE] Release Apache Maven Invoker Plugin version 1.9

+1 Regards, Hervé Le samedi 28 juin 2014 12:04:02 Karl Heinz Marbaise a écrit : > Hi, > > We solved 6 issues: > http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11441&version=189 > 96 > > There are still a couple of issues left in JIRA: > http://jira.codehaus.org/issues/?jql=project%

Using Markdown

I starting converting some site docs to Markdown and it's relatively straight forward. I used the Doxia converter to produce XHTML and then used Pandoc to convert that to Markdown. Works better than I expected. If anyone else wants to convert some documents here's what I used: java -jar apache-

Re: [VOTE] Release Apache Maven Invoker Plugin version 1.9

On Mon, Jun 30, 2014 at 4:36 PM, Karl Heinz Marbaise wrote: > Karl-Heinz Marbaise +1 binding - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org

Issues to be reviewed for 3.x

There are about 295 closed issues in "Issues to be reviews for 3.x", presumably all closed due to the massive issue cleanup. I can do a query to find out for sure. For the ones I can verify, does anyone care if I remove the version from these tickets? They aren't being released and that's our polic

Re: [VOTE] Release Apache Maven Invoker Plugin version 1.9

Hi, i need only two other votes ;-) Kind regards Karl-Heinz Marbaise wrote: Hi, We solved 6 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11441&version=18996 There are still a couple of issues left in JIRA: http://jira.codehaus.org/issues/?jql=project%20%3D%20MINVOKER%2

[VOTE] Release Doxia Tools version 3 + Doxia Integartion Tools version 1.6

Hi, We solved 3 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=12125&styleName=Html&version=18797 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=12125&status=1 Staging repo: http://repository.apache.org/cont

Re: [VOTE] Release Apache Doxia base and Site Tools version 1.6

here is my +1 Regards, Hervé Le samedi 28 juin 2014 00:38:16 Hervé BOUTEMY a écrit : > Hi, > > We solved 6 issues in Doxia base and 7 issues in Doxia Site Tools: > http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10780&styleName=H > tml&version=19820 > http://jira.codehaus.org/secure/

Re: [RFC] [MENFORCER-174]

Hi, based on the suggestions i would go with: RestrictDistributionManagement Thanks for your comments Kind regards Karl-Heinz Marbaise On 6/30/14 6:46 PM, Robert Scholte wrote: I was thinking of 'restrict' as well Op Mon, 30 Jun 2014 10:48:44 +0200 schreef Chris Graham : Limit or Restrict

Re: [RFC] [MENFORCER-174]

Hi Martin, > If I understand what you are attempting here: you wish to place additional restrictions on which artifacts are being exposed to distribution-management via a maven-enforcer-plugin rule implementor ? No. I don't want to restrict which artifact is being exposed in contradiction i

Re: [RFC] [MENFORCER-174]

I was thinking of 'restrict' as well Op Mon, 30 Jun 2014 10:48:44 +0200 schreef Chris Graham : Limit or Restrict... Sent from my iPhone On 30/06/2014, at 4:08 PM, Karl Heinz Marbaise wrote: Hi, according to comments about the naming of the rule (BanDistributionManagement my original

RE: [RFC] [MENFORCER-174]

If I understand what you are attempting here: you wish to place additional restrictions on which artifacts are being exposed to distribution-management via a maven-enforcer-plugin rule implementor ? from a conceptual point of view Repo Managers (nexus specifically) can grant or deny access to re

Re: [RFC] [MENFORCER-174]

Limit or Restrict... Sent from my iPhone On 30/06/2014, at 4:08 PM, Karl Heinz Marbaise wrote: > Hi, > > according to comments about the naming of the rule (BanDistributionManagement > my original name) and the suggestions made by Robert Scholte which of course > are true in particular about

[RFC] [MENFORCER-174]

Hi, according to comments about the naming of the rule (BanDistributionManagement my original name) and the suggestions made by Robert Scholte which of course are true in particular about the confusions about the intention of the rule. I would like to know if someone of the devs has a good/b