[RFC] [MENFORCER-174]

[Karl Heinz Marbaise]

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/better idea...

My idea is: FilterDistributionManagement

The idea of the rule is to limit the usage of distributionManagement in 
particular areas of pom may be only within a company pom etc.


What about LimitDistributionManagementUsage

Many thanks in advance...

Kind regards
Karl-Heinz Marbaise

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: [RFC] [MENFORCER-174]

[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 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/better idea...
> 
> My idea is: FilterDistributionManagement
> 
> The idea of the rule is to limit the usage of distributionManagement in 
> particular areas of pom may be only within a company pom etc.
> 
> What about LimitDistributionManagementUsage
> 
> Many thanks in advance...
> 
> Kind regards
> Karl-Heinz Marbaise
> 
> -
> 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: [RFC] [MENFORCER-174]

[Martin Gainty]

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 repos, packages within those repos and artifacts within 
the packages
 From there the permissions matrix of that folder can be implemented by 
imposing .htaccess on the folder
in this way devs do not have access to any of the RELEASE repositories
Operators do not have insert/update capability to SNAPSHOTs 

 if this your intent here?

Martin 
__


> Date: Mon, 30 Jun 2014 08:08:10 +0200
> From: khmarba...@gmx.de
> To: dev@maven.apache.org
> Subject: [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/better idea...
> 
> My idea is: FilterDistributionManagement
> 
> The idea of the rule is to limit the usage of distributionManagement in 
> particular areas of pom may be only within a company pom etc.
> 
> What about LimitDistributionManagementUsage
> 
> Many thanks in advance...
> 
> Kind regards
> Karl-Heinz Marbaise
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
> 
  

Re: [RFC] [MENFORCER-174]

[Robert Scholte]

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 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/better idea...

My idea is: FilterDistributionManagement

The idea of the rule is to limit the usage of distributionManagement in  
particular areas of pom may be only within a company pom etc.


What about LimitDistributionManagementUsage

Many thanks in advance...

Kind regards
Karl-Heinz Marbaise

-
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: [RFC] [MENFORCER-174]

[Karl Heinz Marbaise]

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 would like to restrict the usage of the 
distributionManagement tag (or sub parts) itself in pom's to force the 
usage of it only once or with some exceptions within projects in a 
larger company which leads often to problems.




from a conceptual point of view Repo Managers (nexus specifically) can
grant or deny access to repos, packages within those repos and artifacts within 
the packages

I know that...


  From there the permissions matrix of that folder can be implemented by 
imposing .htaccess on the folder
in this way devs do not have access to any of the RELEASE repositories
Operators do not have insert/update capability to SNAPSHOTs

That's not my intention...



  if this your intent here?

Martin
__



Date: Mon, 30 Jun 2014 08:08:10 +0200
From: khmarba...@gmx.de
To: dev@maven.apache.org
Subject: [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/better idea...

My idea is: FilterDistributionManagement

The idea of the rule is to limit the usage of distributionManagement in
particular areas of pom may be only within a company pom etc.

What about LimitDistributionManagementUsage

Many thanks in advance...

Kind regards
Karl-Heinz Marbaise

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org







Mit freundlichem Gruß
Karl-Heinz Marbaise
--
SoftwareEntwicklung Beratung SchulungTel.: +49 (0) 2405 / 415 893
Dipl.Ing.(FH) Karl-Heinz MarbaiseICQ#: 135949029
Hauptstrasse 177 USt.IdNr: DE191347579
52146 Würselen   http://www.soebes.de

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: [RFC] [MENFORCER-174]

[Karl Heinz Marbaise]

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...

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 the
confusions about the intention of the rule.

I would like to know if someone of the devs has a good/better idea...

My idea is: FilterDistributionManagement

The idea of the rule is to limit the usage of distributionManagement
in particular areas of pom may be only within a company pom etc.

What about LimitDistributionManagementUsage

Many thanks in advance...


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

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

[Hervé BOUTEMY]

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/ReleaseNote.jspa?projectId=11624&styleName=
> Html&version=19925
> 
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=10780&sta
> tus=1
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11624&st
> atus=1
> 
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1030/
> http://repository.apache.org/content/repositories/maven-1030/org/apache/mave
> n/doxia/doxia/1.6/doxia-1.6-source-release.zip
> http://repository.apache.org/content/repositories/maven-1030/org/apache/mav
> en/doxia/doxia-sitetools/1.6/doxia-sitetools-1.6-source-release.zip
> 
> Source release checksum(s):
> doxia-1.6-source-release.zip sha1: 0ae9b9a09bfdc9d0aada1cbc5571c710805abae6
> doxia-sitetools-1.6-source-release.zip sha1:
> 9a166407b659452379fc680a25e43b3a162ed27e
> 
> Staging site:
> http://maven.apache.org/doxia/doxia-archives/doxia-LATEST/
> http://maven.apache.org/doxia/doxia-sitetools-archives/doxia-sitetools-LATES
> T/
> 
> 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

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

[Hervé BOUTEMY]

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/content/repositories/maven-1035/
http://repository.apache.org/content/repositories/maven-1035/org/apache/maven/doxia/doxia-tools/3/doxia-tools-3-source-release.zip
http://repository.apache.org/content/repositories/maven-1035/org/apache/maven/doxia/doxia-integration-tools/1.6/doxia-integration-tools-1.6-source-release.zip

Source release checksum(s):
doxia-tools-3-source-release.zip sha1: 
f1c1bf2acf613f94129e71cd9dc59edd7f89b67a
doxia-integration-tools-1.6-source-release.zip sha1: 
0115962439d7d61cfebfe6a2899b16dd356879c4

Staging site:
http://maven.apache.org/doxia/doxia-tools-archives/doxia-integration-tools-LATEST/

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

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

[Karl Heinz Marbaise]

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%20AND%20status%20%3D%20Open%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC


Staging repo:
https://repository.apache.org/content/repositories/maven-1031

http://repository.apache.org/content/repositories/maven-1031/org/apache/maven/plugins/maven-invoker-plugin/1.9/maven-invoker-plugin-1.9-source-release.zip


Source release checksum(s):
maven-invoker-plugin-1.9-source-release.zip sha1:
aef0b555f8c571108b9f26230392adf5abef8b6d

Staging site:
http://maven.apache.org/plugins-archives/maven-invoker-plugin-LATEST/

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

Issues to be reviewed for 3.x

[Paul Benedict]

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
policy now -- not to set the Fix Version for issues that are
incomplete/invalid.

Cheers,
Paul

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

[Benson Margulies]

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

Using Markdown

[Jason van Zyl]

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-doxia-1.3-SNAPSHOT-jar-with-dependencies.jar -in 
${whatever}.apt -from apt -out . -to xhtml
pandoc -f html -t markdown --atx-headers ${whatever}.apt.xhtml > ${whatever}.md

Thanks,

Jason

--
Jason van Zyl
Founder,  Apache Maven
http://twitter.com/jvanzyl
http://twitter.com/takari_io
-

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

[Hervé BOUTEMY]

+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%20%3D%20MINVOKER%20AND%20status
> %20%3D%20Open%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC
> 
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1031
> 
> http://repository.apache.org/content/repositories/maven-1031/org/apache/mave
> n/plugins/maven-invoker-plugin/1.9/maven-invoker-plugin-1.9-source-release.z
> ip
> 
> Source release checksum(s):
> maven-invoker-plugin-1.9-source-release.zip sha1:
> aef0b555f8c571108b9f26230392adf5abef8b6d
> 
> Staging site:
> http://maven.apache.org/plugins-archives/maven-invoker-plugin-LATEST/
> 
> Guide to testing staged releases:
> http://maven.apache.org/guides/development/guide-testing-releases.html
> 
> Vote open for 72 hours.
> 
> [ ] +1
> [ ] +0
> [ ] -1
> 
> Kind regards
> Karl-Heinz Marbaise
> 
> -
> 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 Apache Doxia base and Site Tools version 1.6

[Hervé BOUTEMY]

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: Using Markdown

[Jason van Zyl]

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 people as it's more like a Wiki. But it gets 
better. Then I wired up 

http://dillinger.io

to that repository and I immediately got instant viewing on the right while I'm 
editing on the left which is just awesome. 

I believe this would enable the entire community to help edit the website as 
you fork a repo, pop open dillinger.io (or stackedit.io) and easily make edits 
and submit a PR.

It's just awesome.

On Jun 30, 2014, at 7:36 PM, Jason van Zyl  wrote:

> 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-doxia-1.3-SNAPSHOT-jar-with-dependencies.jar -in 
> ${whatever}.apt -from apt -out . -to xhtml
> pandoc -f html -t markdown --atx-headers ${whatever}.apt.xhtml > 
> ${whatever}.md
> 
> Thanks,
> 
> Jason
> 
> --
> Jason van Zyl
> Founder,  Apache Maven
> http://twitter.com/jvanzyl
> http://twitter.com/takari_io
> -
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 

Thanks,

Jason

--
Jason van Zyl
Founder,  Apache Maven
http://twitter.com/jvanzyl
http://twitter.com/takari_io
-

First, the taking in of scattered particulars under one Idea,
so that everyone understands what is being talked about ... Second,
the separation of the Idea into parts, by dividing it at the joints,
as nature directs, not breaking any limb in half as a bad carver might.

  -- Plato, Phaedrus (Notes on the Synthesis of Form by C. Alexander)

Using Maven archetype for dynamic file creation

[sanchit gupta]

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 as maven archetype is
concerned I see that they are only capable of simple variable substitution
and a static file/folder structure.

   1.

   Is there a way to do processing prior to creating a project from an
   archetype, add java objects to the velocity context, and have the archetype
   templates be able to access them.
   2. Is there some documentation about how to use java objects with the
   maven archetype to generate dynamic file content?


-- 

Sincere Regards,
Sanchit Gupta

"A man is a success if he gets up in the morning and gets to bed at night,
and in between he does what he wants to do."
— Bob Dylan

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

[Karl Heinz Marbaise]

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 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%20AND%20status%20%3D%20Open%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC


Staging repo:
https://repository.apache.org/content/repositories/maven-1031

http://repository.apache.org/content/repositories/maven-1031/org/apache/maven/plugins/maven-invoker-plugin/1.9/maven-invoker-plugin-1.9-source-release.zip


Source release checksum(s):
maven-invoker-plugin-1.9-source-release.zip sha1:
aef0b555f8c571108b9f26230392adf5abef8b6d

Staging site:
http://maven.apache.org/plugins-archives/maven-invoker-plugin-LATEST/

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