[VOTE] Release Apache Maven Archetype Bundles version 1.3

[Hervé BOUTEMY]

Hi,

We solved 14 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317123=12342794=Text

There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MARCHETYPES%20AND%20status%20%3D%20Open%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC

Staging repo:
https://repository.apache.org/content/repositories/maven-1411/
https://repository.apache.org/content/repositories/maven-1411/org/apache/maven/archetypes/maven-archetype-bundles/1.3/maven-archetype-bundles-1.3-source-release.zip

Source release checksum(s):
maven-archetype-bundles-1.3-source-release.zip sha1: 
9f4a9422942ca7e6b737a86e21fd39d66b4e73ec

Staging site:
https://maven.apache.org/archetypes-archives/archetypes-LATEST/

Guide to testing staged releases:
https://maven.apache.org/guides/development/guide-testing-releases.html

Vote open for at least 72 hours.

[ ] +1
[ ] +0
[ ] -1

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

[VOTE] Release Apache Maven Shade Plugin version 3.1.1

[Karl Heinz Marbaise]

Hi,

We solved 10 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317921=12341390

There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSHADE%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC%2C%20updated%20DESC

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

https://repository.apache.org/content/repositories/maven-1410/org/apache/maven/plugins/maven-shade-plugin/3.1.1/maven-shade-plugin-3.1.1-source-release.zip

Source release checksum(s):
maven-shade-plugin-3.1.1-source-release.zip sha1: 
40371b464195e84f0225f11c515ae7a21c393297


Staging site:
https://maven.apache.org/plugins-archives/maven-shade-plugin-LATEST/

Guide to testing staged releases:
https://maven.apache.org/guides/development/guide-testing-releases.html

Vote open for at least 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

Re: [VOTE] Release Apache Maven Dependency Plugin version 3.1.0

[Mark Raynsford]

+1

Tested on multiple Java 9 projects with all sorts of Java 9
dependencies. No issues.


-- 
Mark Raynsford | http://www.io7m.com



pgpnlcDViWCTx.pgp
Description: OpenPGP digital signature

[VOTE] Release Apache Maven Dependency Plugin version 3.1.0

[Karl Heinz Marbaise]

Hi,

We solved 6 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317227=12341595

There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20XX%20AND%20status%20%3D%20Open%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC

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

https://repository.apache.org/content/repositories/maven-1409/org/apache/maven/plugins/maven-dependency-plugin/3.1.0/maven-dependency-plugin-3.1.0-source-release.zip

Source release checksum(s):
maven-dependency-plugin-3.1.0-source-release.zip sha1: 
9098f4024981218d0c2c22b176f51b92850e3960


Staging site:
https://maven.apache.org/plugins-archives/maven-dependency-plugin-LATEST/

Guide to testing staged releases:
https://maven.apache.org/guides/development/guide-testing-releases.html

Vote open for at least 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

Re: Name Question / Trade Marks Maven

[Michael Osipov]

Am 2018-04-02 um 18:43 schrieb Karl Heinz Marbaise:

Hi, by coincidence I stumbled over the following:

http://search.maven.org/remotecontent?filepath=io/gatling/maven-shade-plugin/3.1.0.1/maven-shade-plugin-3.1.0.1.pom 



http://search.maven.org/remotecontent?filepath=org/immutables/tools/maven-shade-plugin/4/maven-shade-plugin-4.pom 




which is an exact copy of maven-shade-plugin but it contains the same 
name and mentioned as "Apache Maven Shade Plugin" (also artifactId: 
maven-shade-plugiN) ...which if I correctly understand is not correct 
cause this name is covered by Trademarks If I'm correctly remember...?


WDYT ?


There are more plugins doing this, but this seems to be a special case. 
Using our parent *and* our plugin name.


See also: 
http://search.maven.org/#search%7Cga%7C1%7Ca%3Amaven-*-plugin%20AND%20NOT%20g%3Aorg.apache.maven.plugins


g: io.gatling

If the name wouldn't collide at least. I'd request them to rename the 
repackaged plugin.


Michael

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

Name Question / Trade Marks Maven

[Karl Heinz Marbaise]

Hi, by coincidence I stumbled over the following:

http://search.maven.org/remotecontent?filepath=io/gatling/maven-shade-plugin/3.1.0.1/maven-shade-plugin-3.1.0.1.pom

http://search.maven.org/remotecontent?filepath=org/immutables/tools/maven-shade-plugin/4/maven-shade-plugin-4.pom


which is an exact copy of maven-shade-plugin but it contains the same 
name and mentioned as "Apache Maven Shade Plugin" (also artifactId: 
maven-shade-plugiN) ...which if I correctly understand is not correct 
cause this name is covered by Trademarks If I'm correctly remember...?


WDYT ?


Kind regards
Karl Heinz Marbaise

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

[GitHub] maven-plugins pull request #142: Fixed the example code in usage.apt.vm

[petukhov]

Github user petukhov closed the pull request at:

https://github.com/apache/maven-plugins/pull/142


---

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

[GitHub] maven-plugins pull request #142: Fixed the example code in usage.apt.vm

[petukhov]

GitHub user petukhov opened a pull request:

https://github.com/apache/maven-plugins/pull/142

Fixed the example code in usage.apt.vm

Had the original code copied to my project and it was resulting in an 
error. After the configuration tag directly under the plugin tag everything 
worked.

Here is the related StackOverflow question with the solution: 
https://stackoverflow.com/questions/49606513/maven-checkstyle-plugin3-0-0check-failed-during-checkstyle-configuration-can/49610945#49610945

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/petukhov/maven-plugins trunk

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/maven-plugins/pull/142.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #142


commit e97815d64944a9ef59e4d85fbb54ef7fd14b2d6d
Author: Georgy Petukhov 
Date:   2018-04-02T16:27:37Z

Updated usage.apt.vm




---

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

[GitHub] maven-plugins pull request #134: MPH-124: add alias to describe detail

[bentatham]

Github user bentatham closed the pull request at:

https://github.com/apache/maven-plugins/pull/134


---

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

[GitHub] maven-plugins pull request #136: [MDEP-584] Update plexus-utils to 3.1.0

[io7m]

Github user io7m closed the pull request at:

https://github.com/apache/maven-plugins/pull/136


---

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

Re: ScmProvider.list()

[Stephen Connolly]

On Sun 1 Apr 2018 at 22:12, Michael Osipov  wrote:

> Am 2018-04-01 um 23:01 schrieb Stephen Connolly:
> > On Sun 1 Apr 2018 at 17:21, Michael Osipov  wrote:
> >
> >> Am 2018-04-01 um 13:54 schrieb Stephen Connolly:
> >>> On Fri 30 Mar 2018 at 10:20, Michael Osipov 
> wrote:
> >>>
>  Am 2018-03-30 um 10:47 schrieb Basin Ilya:
> > Hi.
> > We need your opinion on the following topic. While Svn and Cvs
> >> providers
>  perform the list() operation remotely and don't need a checkout
> >> directory,
>  Git and some others
> > simply list the local files (generally, because their SCMs don't
> >> provide
>  a remote list method). Arguments passed to the list() method also have
>  different meanings for those
> > providers.
> >
> >
> > We should specify in the ScmProvider.list() javadoc that if the SCM
> >> does
>  not support remote listing, then the method should just fail and also
>  modify the existing
> > ListCommand implementations.
> 
>  My opinion on this is that the ListCommand says remote repos. If some
>  SCM provider implements it wrong, it either has to be dropped or
>  corrected. I don't like the idea to checkout or clone to list files.
> 
>  The Git provider has been implemented incorrectly from the beginning.
> I
>  checked some other SCMs and they don't implement it at all.
> 
>  This needs to be fixed in 2.0.0.
> >>>
> >>>
> >>> It depends, git being distributed, if you have the local checkout, you
> >> can
> >>> list exactly without needing to go remote.
> >>
> >> No, the docs say remote list. Not local list.
> >>
> >>> But perhaps the thing here is to enhance the api to provide for both
> >> cases.
> >>
> >> Likely, but you will end up in a split situation because not every SCM
> >> will implement your usercase.
> >>
> >>> At the minimum, git could do an ls-remote and then list from local once
> >> the
> >>> revision is confirmed present (which would meet a goal of being a “read
> >>> only” operation)
> >>
> >> ls-remote does *not* list any files remotely, it lists remote refs.
> >
> >
> > And if we have the remote ref local then *because refs are immutable* we
> > can list the files from local.
> >
> > I think the only issue is the lack of a call to ls-remote
>
> I do not understand what you are trying to say. How is the output of
> ls-remote/remote refs relateed to the remote file listing?
> Even if you have the current branch, you still cannot list the files
> because you don't know wether your local branch is uptodate with remote.


That is what ls-remote tells you. It tells you the revisions of every
branch and tag in the remote (or you can just ask for one branch)

Then if the revision is in the .git database you can list the files


>
> Michael
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
> --
Sent from my phone