Re: [VOTE] Plugins parent 24 and Shared parent 19

+1 Den 30. jan. 2013 kl. 00:41 skrev Olivier Lamy : > Hi, > I'd like to release Plugins parent 24 and Shared parent 19. > Staging repository: > https://repository.apache.org/content/repositories/maven-172/ > > Diffs: > > * Plugins parent 24: > http://svn.apache.org/viewvc/maven/plugins/tags/maven

[SCM] GitExe : no fetch after push ?

Hi folks ! I recently aligned from git impl v1.6 to 1.8 and there seems to have a behaviour change between these 2 versions. I noticed when I call a checkIn(), following commands are executed : cd && git status --porcelain cd && git commit --verbose -F -a cd && git symbolic-ref HEAD cd && gi

[VOTE] Plugins parent 24 and Shared parent 19

Hi, I'd like to release Plugins parent 24 and Shared parent 19. Staging repository: https://repository.apache.org/content/repositories/maven-172/ Diffs: * Plugins parent 24: http://svn.apache.org/viewvc/maven/plugins/tags/maven-plugins-24/pom.xml?r1=HEAD&r2=1371605&diff_format=h * Shared parent

Re: Maven Plugin - plugin version based on pluginManagement

Le lundi 28 janvier 2013 23:22:15 Karl Heinz Marbaise a écrit : > So the question is how does Maven know of the version of the above > plugin which has been defined in the pluginManagement section before. see maven-model-builder, phase 2, "plugin management injection" step [1], done in code [2] by

Re: Site:stage relativization against a variable URL

Patch created and attached to the JIRA. Feedback would be appreciated. Lukas: Could we please include this patch into the upcoming release of the site plugin? It would simplify/enable the generation of big documentation sites where the reactor structure does not map to the [parent] inheritance str

Re: Changing (internal) interface signatures in a plugin

Well, to be absolutely clear, to fix that issue I might need to make bigger changes (incl. public methods) as there should probably be some design changes. The patch is not complete. But I'd like this discussion to be generic and not specific to this issue. /Anders On Tue, Jan 29, 2013 at 3:59

Re: git: on urls on source pages?

http://maven.apache.org/plugins/maven-project-info-reports-plugin/scm-mojo.html Op Tue, 29 Jan 2013 09:01:03 +0100 schreef Benson Margulies : The surefire source repo page says things like: git:https://git-wip-us.apache.org/repos/asf/maven-surefire.git That 'git:' is an internal Maven thi

Re: Changing (internal) interface signatures in a plugin

+1 And the patch is a signature change on a private method so not a real issue. 2013/1/29 Anders Hammar : > Just want to check what the general opinion is about changing method > signatures of Plexus component interfaces in our plugins for a minor > version release. > > In a perfect world it would

Re: Changing (internal) interface signatures in a plugin

+1 on changing. no one is forced to upgrade. On Jan 29, 2013, at 1:19 PM, Anders Hammar wrote: > Just want to check what the general opinion is about changing method > signatures of Plexus component interfaces in our plugins for a minor > version release. > > In a perfect world it would be aweso

Changing (internal) interface signatures in a plugin

Just want to check what the general opinion is about changing method signatures of Plexus component interfaces in our plugins for a minor version release. In a perfect world it would be awesome to always keep backwards compatibility and at least never do any changes unless a major version. But as

git: on urls on source pages?

The surefire source repo page says things like: git:https://git-wip-us.apache.org/repos/asf/maven-surefire.git That 'git:' is an internal Maven thing, and I think it should not be there. Is this a site plugin issue or a surefire pom issue? ---