[GitHub] [maven-site] slachiewicz commented on pull request #165: docs: git migration is complete

2020-08-11 Thread GitBox


slachiewicz commented on pull request #165:
URL: https://github.com/apache/maven-site/pull/165#issuecomment-672632977


   Yes, we have only few remaining - but this info is longer interesting to 
wider forum.



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



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



[GitHub] [maven-site] asfgit closed pull request #165: docs: git migration is complete

2020-08-11 Thread GitBox


asfgit closed pull request #165:
URL: https://github.com/apache/maven-site/pull/165


   



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



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



[GitHub] [maven-site] olamy merged pull request #188: Introduce section heading for BOM pattern

2020-08-11 Thread GitBox


olamy merged pull request #188:
URL: https://github.com/apache/maven-site/pull/188


   



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



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



[GitHub] [maven-site] edburns commented on pull request #188: Introduce section heading for BOM pattern

2020-08-11 Thread GitBox


edburns commented on pull request #188:
URL: https://github.com/apache/maven-site/pull/188#issuecomment-672292707


   Hello, this is approved.  Can someone please merge it, or let me know what I 
need to do to have it merged?
   
   Thanks,
   
   Ed



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.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 Dependency Analyzer version 1.11.3

2020-08-11 Thread Ian Lavallee
+1

On Mon, Aug 10, 2020 at 10:20 AM Elliotte Rusty Harold 
wrote:

> Let's try this one more time. I updated Jira and regenerated the
> release notes. Nothing else has changed:
>
> Hi,
>
> We solved 3 issues:
>
> [MSHARED-949] - dependency:analyze should recommend narrower scope
> where possible
> [MSHARED-948] - Update link to Jira
> [MSHARED-932] - Remove JMock dependency
>
> There are still five issues left in JIRA:
>
> https://issues.apache.org/jira/browse/MSHARED-916?jql=project%20%3D%20MSHARED%20AND%20status%20%3D%20Open%20AND%20component%20%3D%20maven-dependency-analyzer
>
>
> Staging repo:
>
> https://repository.apache.org/content/repositories/maven-staging-group/org/apache/maven/shared/maven-dependency-analyzer/1.11.3/
>
> https://repository.apache.org/content/repositories/maven-staging-group/org/apache/maven/shared/maven-dependency-analyzer/1.11.3/maven-dependency-analyzer-1.11.3-source-release.zip
>
> Source release checksum(s):
> maven-dependency-analyzer-1.11.3-source-release.zip sha512:
>
> 84a13538660dd877e6ab7b626778267b4ddf06581752235e8e4e282306a6c896e7d737795a81fd05a804e77fa685ddf4891b20c73561bbc741ab671b5ccf75b8
>
> Staging site:
> https://maven.apache.org/shared-archives/maven-dependency-analyzer-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
>
>
> On Wed, Aug 5, 2020 at 4:31 PM Elliotte Rusty Harold 
> wrote:
> >
> > Hi,
> >
> > We solved 2 issues:
> > * [MSHARED-932] Remove JMock dependency
> > * [MDEP-708] dependency:analyze should recommend narrower scope
> > where possible
> >
> > There are still five issues left in JIRA:
> >
> https://issues.apache.org/jira/browse/MSHARED-916?jql=project%20%3D%20MSHARED%20AND%20status%20%3D%20Open%20AND%20component%20%3D%20maven-dependency-analyzer
> >
> >
> > Staging repo:
> >
> https://repository.apache.org/content/repositories/maven-staging-group/org/apache/maven/shared/maven-dependency-analyzer/1.11.3/
> >
> https://repository.apache.org/content/repositories/maven-staging-group/org/apache/maven/shared/maven-dependency-analyzer/1.11.3/maven-dependency-analyzer-1.11.3-source-release.zip
> >
> > Source release checksum(s):
> > maven-dependency-analyzer-1.11.3-source-release.zip sha512:
> >
> 84a13538660dd877e6ab7b626778267b4ddf06581752235e8e4e282306a6c896e7d737795a81fd05a804e77fa685ddf4891b20c73561bbc741ab671b5ccf75b8
> >
> > Staging site:
> >
> https://maven.apache.org/shared-archives/maven-dependency-analyzer-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
> >
> >
> > --
> > Elliotte Rusty Harold
> > elh...@ibiblio.org
>
>
>
> --
> Elliotte Rusty Harold
> elh...@ibiblio.org
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>


Action design cards

2020-08-11 Thread Robert Scholte
On behalf of Amelia:

https://issues.apache.org/jira/browse/MNG-6928: your feedback is welcomed in 
the ticket. If you are an #ossDOER on the project, you have earned the 
opportunity to provide  feedback on designs  [:slightly_smiling_face:] cheers!  
Thank YOU @rfscholte [https://usualsuspectstalk.slack.com/team/U52D4G9NC] for 
enabling us to thank YOU and the Maven Community back. You and what you do 
rocks!  [:muscle::skin-tone-4:] [:martial_arts_uniform:] [:purple_heart:]

[GitHub] [maven-site] elharo commented on a change in pull request #191: docs: system dependencies are not always available

2020-08-11 Thread GitBox


elharo commented on a change in pull request #191:
URL: https://github.com/apache/maven-site/pull/191#discussion_r468747113



##
File path: 
content/apt/guides/introduction/introduction-to-dependency-mechanism.apt
##
@@ -172,9 +172,10 @@ Introduction to the Dependency Mechanism
unit tests (src/test/java) but not in the model code (src/main/java).
 
  * <>\
-   This scope is similar to <<>> except that you have to provide the 
JAR
-   which contains it explicitly. The artifact is always available and is not
-   looked up in a repository.
+   Maven does not add system-scoped dependencies to any classpath.

Review comment:
   I was referring to the "maybe"in your comment. :-)





This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



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



Re: Need help merging pull requests for maven-site

2020-08-11 Thread Olivier Lamy
On Tue, 11 Aug 2020 at 20:37, Dennis Lundberg 
wrote:

> Den tis 11 aug. 2020 kl 13:46 skrev Olivier Lamy :
>
> > On Tue, 11 Aug 2020 at 19:40, Dennis Lundberg 
> > wrote:
> >
> > > Thanks Olivier,
> > >
> > > I was just following our release process at
> > >
> > >
> >
> https://maven.apache.org/developers/release/maven-project-release-procedure.html
> >
> >
> > I do not see anything related to create pull request for such easy change
> >
>
> The pull requests are created automatically when you edit the github page.
>
I'm sure there is an option to commit/push directly..
 look at the options next time ;)


> >
> > >
> > > Under step 2 of "Promote the release" it says
> > > "In case there's an overview table with version (e.g. plugins
> > >  and shared
> > > ) you can directly edit it
> > on
> > > the github page."
> > >
> > > Should i change those instructions to push to master if you have those
> > > permissions?
> >
> >
> > frankly we are adults we do not need instructions to create pr request
> for
> > such obvious change :)
> >
>
> I agree :)
>
> >
> >
> >
> > > --
> > > Dennis Lundberg
> > >
> > >
> > > Den tis 11 aug. 2020 kl 13:29 skrev Olivier Lamy :
> > >
> > > > Hi Dennis
> > > > I just merged your pr.
> > > > But for those changes just push to master branch you do not really
> need
> > > > approval and it's a bit useless...
> > > > (and this will avoid some notifications noise)
> > > >
> > > > On Tue, 11 Aug 2020 at 19:25, Dennis Lundberg 
> > > wrote:
> > > >
> > > > > Hi,
> > > > >
> > > > > During the release I've made recently I have updated
> > maven-site@github
> > > > > with
> > > > > the new versions and release dates. These turn into pull requests
> > that
> > > > have
> > > > > now been approved. However I seem to lack some permissions (or
> > > knowledge)
> > > > > to merge these pull requests from the GitHub UI.
> > > > >
> > > > > Can someone point me in the right direction, or help me merge
> these:
> > > > > https://github.com/apache/maven-site/pull/189
> > > > > https://github.com/apache/maven-site/pull/192
> > > > > https://github.com/apache/maven-site/pull/193
> > > > >
> > > > > Thanks in advance,
> > > > > Dennis Lundberg
> > > > >
> > > >
> > > >
> > > > --
> > > > Olivier Lamy
> > > > http://twitter.com/olamy | http://linkedin.com/in/olamy
> > > >
> > >
> >
> >
> > --
> > Olivier Lamy
> > http://twitter.com/olamy | http://linkedin.com/in/olamy
> >
>


-- 
Olivier Lamy
http://twitter.com/olamy | http://linkedin.com/in/olamy


Re: Need help merging pull requests for maven-site

2020-08-11 Thread Dennis Lundberg
Den tis 11 aug. 2020 kl 13:46 skrev Olivier Lamy :

> On Tue, 11 Aug 2020 at 19:40, Dennis Lundberg 
> wrote:
>
> > Thanks Olivier,
> >
> > I was just following our release process at
> >
> >
> https://maven.apache.org/developers/release/maven-project-release-procedure.html
>
>
> I do not see anything related to create pull request for such easy change
>

The pull requests are created automatically when you edit the github page.

>
> >
> > Under step 2 of "Promote the release" it says
> > "In case there's an overview table with version (e.g. plugins
> >  and shared
> > ) you can directly edit it
> on
> > the github page."
> >
> > Should i change those instructions to push to master if you have those
> > permissions?
>
>
> frankly we are adults we do not need instructions to create pr request for
> such obvious change :)
>

I agree :)

>
>
>
> > --
> > Dennis Lundberg
> >
> >
> > Den tis 11 aug. 2020 kl 13:29 skrev Olivier Lamy :
> >
> > > Hi Dennis
> > > I just merged your pr.
> > > But for those changes just push to master branch you do not really need
> > > approval and it's a bit useless...
> > > (and this will avoid some notifications noise)
> > >
> > > On Tue, 11 Aug 2020 at 19:25, Dennis Lundberg 
> > wrote:
> > >
> > > > Hi,
> > > >
> > > > During the release I've made recently I have updated
> maven-site@github
> > > > with
> > > > the new versions and release dates. These turn into pull requests
> that
> > > have
> > > > now been approved. However I seem to lack some permissions (or
> > knowledge)
> > > > to merge these pull requests from the GitHub UI.
> > > >
> > > > Can someone point me in the right direction, or help me merge these:
> > > > https://github.com/apache/maven-site/pull/189
> > > > https://github.com/apache/maven-site/pull/192
> > > > https://github.com/apache/maven-site/pull/193
> > > >
> > > > Thanks in advance,
> > > > Dennis Lundberg
> > > >
> > >
> > >
> > > --
> > > Olivier Lamy
> > > http://twitter.com/olamy | http://linkedin.com/in/olamy
> > >
> >
>
>
> --
> Olivier Lamy
> http://twitter.com/olamy | http://linkedin.com/in/olamy
>


Re: Need help merging pull requests for maven-site

2020-08-11 Thread Olivier Lamy
On Tue, 11 Aug 2020 at 19:40, Dennis Lundberg 
wrote:

> Thanks Olivier,
>
> I was just following our release process at
>
> https://maven.apache.org/developers/release/maven-project-release-procedure.html


I do not see anything related to create pull request for such easy change


>
>
> Under step 2 of "Promote the release" it says
> "In case there's an overview table with version (e.g. plugins
>  and shared
> ) you can directly edit it on
> the github page."
>
> Should i change those instructions to push to master if you have those
> permissions?


frankly we are adults we do not need instructions to create pr request for
such obvious change :)



>


> --
> Dennis Lundberg
>
>
> Den tis 11 aug. 2020 kl 13:29 skrev Olivier Lamy :
>
> > Hi Dennis
> > I just merged your pr.
> > But for those changes just push to master branch you do not really need
> > approval and it's a bit useless...
> > (and this will avoid some notifications noise)
> >
> > On Tue, 11 Aug 2020 at 19:25, Dennis Lundberg 
> wrote:
> >
> > > Hi,
> > >
> > > During the release I've made recently I have updated maven-site@github
> > > with
> > > the new versions and release dates. These turn into pull requests that
> > have
> > > now been approved. However I seem to lack some permissions (or
> knowledge)
> > > to merge these pull requests from the GitHub UI.
> > >
> > > Can someone point me in the right direction, or help me merge these:
> > > https://github.com/apache/maven-site/pull/189
> > > https://github.com/apache/maven-site/pull/192
> > > https://github.com/apache/maven-site/pull/193
> > >
> > > Thanks in advance,
> > > Dennis Lundberg
> > >
> >
> >
> > --
> > Olivier Lamy
> > http://twitter.com/olamy | http://linkedin.com/in/olamy
> >
>


-- 
Olivier Lamy
http://twitter.com/olamy | http://linkedin.com/in/olamy


Re: Need help merging pull requests for maven-site

2020-08-11 Thread Dennis Lundberg
Thanks Olivier,

I was just following our release process at
https://maven.apache.org/developers/release/maven-project-release-procedure.html

Under step 2 of "Promote the release" it says
"In case there's an overview table with version (e.g. plugins
 and shared
) you can directly edit it on
the github page."

Should i change those instructions to push to master if you have those
permissions?

--
Dennis Lundberg


Den tis 11 aug. 2020 kl 13:29 skrev Olivier Lamy :

> Hi Dennis
> I just merged your pr.
> But for those changes just push to master branch you do not really need
> approval and it's a bit useless...
> (and this will avoid some notifications noise)
>
> On Tue, 11 Aug 2020 at 19:25, Dennis Lundberg  wrote:
>
> > Hi,
> >
> > During the release I've made recently I have updated maven-site@github
> > with
> > the new versions and release dates. These turn into pull requests that
> have
> > now been approved. However I seem to lack some permissions (or knowledge)
> > to merge these pull requests from the GitHub UI.
> >
> > Can someone point me in the right direction, or help me merge these:
> > https://github.com/apache/maven-site/pull/189
> > https://github.com/apache/maven-site/pull/192
> > https://github.com/apache/maven-site/pull/193
> >
> > Thanks in advance,
> > Dennis Lundberg
> >
>
>
> --
> Olivier Lamy
> http://twitter.com/olamy | http://linkedin.com/in/olamy
>


Re: Need help merging pull requests for maven-site

2020-08-11 Thread Olivier Lamy
Hi Dennis
I just merged your pr.
But for those changes just push to master branch you do not really need
approval and it's a bit useless...
(and this will avoid some notifications noise)

On Tue, 11 Aug 2020 at 19:25, Dennis Lundberg  wrote:

> Hi,
>
> During the release I've made recently I have updated maven-site@github
> with
> the new versions and release dates. These turn into pull requests that have
> now been approved. However I seem to lack some permissions (or knowledge)
> to merge these pull requests from the GitHub UI.
>
> Can someone point me in the right direction, or help me merge these:
> https://github.com/apache/maven-site/pull/189
> https://github.com/apache/maven-site/pull/192
> https://github.com/apache/maven-site/pull/193
>
> Thanks in advance,
> Dennis Lundberg
>


-- 
Olivier Lamy
http://twitter.com/olamy | http://linkedin.com/in/olamy


[GitHub] [maven-site] olamy merged pull request #192: maven-resources-plugin-3.2.0

2020-08-11 Thread GitBox


olamy merged pull request #192:
URL: https://github.com/apache/maven-site/pull/192


   



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



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



[GitHub] [maven-site] olamy merged pull request #193: maven-filtering-3.2.0

2020-08-11 Thread GitBox


olamy merged pull request #193:
URL: https://github.com/apache/maven-site/pull/193


   



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



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



[GitHub] [maven-site] olamy merged pull request #189: Maven Shared Utils 3.3.3

2020-08-11 Thread GitBox


olamy merged pull request #189:
URL: https://github.com/apache/maven-site/pull/189


   



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



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



Need help merging pull requests for maven-site

2020-08-11 Thread Dennis Lundberg
Hi,

During the release I've made recently I have updated maven-site@github with
the new versions and release dates. These turn into pull requests that have
now been approved. However I seem to lack some permissions (or knowledge)
to merge these pull requests from the GitHub UI.

Can someone point me in the right direction, or help me merge these:
https://github.com/apache/maven-site/pull/189
https://github.com/apache/maven-site/pull/192
https://github.com/apache/maven-site/pull/193

Thanks in advance,
Dennis Lundberg


[ANN] Apache Maven Resources Plugin 3.2.0 Released

2020-08-11 Thread Dennis Lundberg
The Apache Maven team is pleased to announce the release of the Apache
Maven Resources Plugin, version 3.2.0

 The Resources Plugin handles the copying of project resources to the
output directory.

https://maven.apache.org/plugins/maven-resources-plugin/

You should specify the version in your project's plugin configuration:


  org.apache.maven.plugins
  maven-resources-plugin
  3.2.0


You can download the appropriate sources etc. from the download page:

https://maven.apache.org/plugins/maven-resources-plugin/download.cgi


Release Notes - Maven Resources Plugin - Version 3.2.0

** Bug
* [MRESOURCES-171] - ISO8859-1 properties files get changed into UTF-8
when filtered
* [MRESOURCES-210] - copy-resources erases file permissions
* [MRESOURCES-236] - Copying of files with permissions broken
* [MRESOURCES-257] - property from list element in pom model

** Improvement
* [MRESOURCES-251] - Upgrade plexus-interpolation 1.26
* [MRESOURCES-252] - Add m2e lifecycle Metadata to plugin
* [MRESOURCES-256] - make build Reproducible
* [MRESOURCES-258] - Only overwrite filtered resources when contents
differ

** Dependency upgrade
* [MRESOURCES-249] - Upgrade maven-plugins parent to version 32
* [MRESOURCES-255] - Upgrade plexus-utils 3.3.0
* [MRESOURCES-261] - Make Maven 3.1.0 the minimum version
* [MRESOURCES-263] - Update to maven-filtering 3.2.0


Enjoy,

-The Apache Maven team


[ANN] Apache Maven Filtering 3.2.0 Released

2020-08-11 Thread Dennis Lundberg
The Apache Maven team is pleased to announce the release of the Apache
Maven Filtering, version 3.2.0

This is a shared component for all plugins that need to filter resources.
https://maven.apache.org/shared/maven-filtering/

You should specify the version in your project's plugin configuration:


  org.apache.maven.shared
  maven-filtering
  3.2.0


You can download the appropriate sources etc. from the download page:
https://maven.apache.org/shared/maven-filtering/download.cgi

Release Notes - Maven Filtering  - Version 3.2.0

** Bug
* [MSHARED-417] - Infinite loop when loading self-referencing properties
* [MSHARED-599] - Escaping the escape string produces incorrect output.
* [MSHARED-829] - MavenResourcesExecution.copyOf() returns new
instance without properties set

** New Feature
* [MSHARED-934] - Allow using a different encoding when filtering
properties files

** Improvement
* [MSHARED-646] - Removed prerequisites for none maven-plugin project
* [MSHARED-664] - Add ico files to default non-filtered extensions
* [MSHARED-830] - Require Java 7
* [MSHARED-879] - make build Reproducible
* [MSHARED-884] - Only overwrite filtered resources when contents differ
* [MSHARED-946] - Update to maven-shared-utils 3.3.3

** Dependency upgrade
* [MSHARED-575] - Upgrade maven-shared-utils to 3.1.0
* [MSHARED-600] - Upgrade of plexus-interpolation to 1.24.
* [MSHARED-645] - Upgrade to maven-shared-utils 3.2.0
* [MSHARED-667] - plexus-utils 3.0.24 to 3.1.0
* [MSHARED-711] - Upgrade parent to 31
* [MSHARED-712] - Upgrade maven-surefire/failsafe-plugin 2.21.0 for JDK 10
* [MSHARED-755] - Upgrade parent to version 32.
* [MSHARED-756] - Upgrade plexus-interpolation to 1.25
* [MSHARED-757] - Upgrade maven-shared-utils to 3.2.1
* [MSHARED-758] - Upgrade JUnit to 4.12
* [MSHARED-789] - Upgrade maven-shared-components parent to 33
* [MSHARED-790] - Upgrade plexus-utils 3.1.1
* [MSHARED-809] - Upgrade plexus-utils 3.2.0

Enjoy,

-The Apache Maven team


[GitHub] [maven-site] dennisl opened a new pull request #193: maven-filtering-3.2.0

2020-08-11 Thread GitBox


dennisl opened a new pull request #193:
URL: https://github.com/apache/maven-site/pull/193


   



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



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



[GitHub] [maven-site] dennisl opened a new pull request #192: maven-resources-plugin-3.2.0

2020-08-11 Thread GitBox


dennisl opened a new pull request #192:
URL: https://github.com/apache/maven-site/pull/192


   



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.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 Maven Resources Plugin version 3.2.0 and Apache Maven Filtering version 3.2.0

2020-08-11 Thread Dennis Lundberg
Hi,

The vote has passed with the following result:

+1 : Robert Scholte, Dennis Lundberg, Olivier Lamy, Sylwester Lachiewicz,
Karl Heinz Marbaise

PMC quorum: Robert Scholte, Dennis Lundberg, Olivier Lamy, Karl Heinz
Marbaise

I will promote the artifacts to the central repo.

--
Dennis Lundberg


Den ons 5 aug. 2020 kl 18:22 skrev Dennis Lundberg :

> Hi,
>
> We solved 12 and 23 
> issues:https://issues.apache.org/jira/projects/MRESOURCES/versions/12343158https://issues.apache.org/jira/projects/MSHARED/versions/12338083
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MRESOURCES%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESChttps://issues.apache.org/jira/issues/?jql=project%20%3D%20MSHARED%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20maven-filtering%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC
>
> Staging 
> repo:https://repository.apache.org/content/repositories/maven-1603/https://repository.apache.org/service/local/repositories/maven-1603/content/org/apache/maven/plugins/maven-resources-plugin/3.2.0/maven-resources-plugin-3.2.0-source-release.ziphttps://repository.apache.org/service/local/repositories/maven-1603/content/org/apache/maven/shared/maven-filtering/3.2.0/maven-filtering-3.2.0-source-release.zip
>
> Source release checksum(s):
> maven-resources-plugin-3.2.0-source-release.zip  sha512: 
> ca920a510de6195d563c49617920823562aaa9be56cc8ca8f87fa9473d65814a6f4ce33f32ccdb7c9115162f8a560cded3deb2cc32bd4b8649a8e57ccc4fb020
> maven-filtering-3.2.0-source-release.zip  sha512: 
> 6cb730fbf9d5a2f3dbf951547d3b2720989906001a1844cfd38367a579f7a11d073807d68d4a907d083daa4295154fa135205dabba94f21ab73afca3022fbe7b
>
> Staging 
> site:https://maven.apache.org/plugins-archives/maven-resources-plugin-LATEST/https://maven.apache.org/shared-archives/maven-filtering-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
>
>
> --
>
> Dennis Lundberg
>