On Tue, 26 May 2020 at 9:00 pm, Anders Hammar wrote:
> On Tue, May 26, 2020 at 8:37 AM Olivier Lamy wrote:
>
> > On Tue, 26 May 2020 at 08:05, Robert Scholte
> wrote:
> >
> > > I think it is pretty impressive that we can say that our plugins still
> > > support a wide range of Maven versions.
I don't think I've seen anything earlier than 3.3.x in recent memory,
but 3.3.x is definitely still out there in the wild being used for new
development.
Given the massive amount of important work that remains to be done to
upgrade plugins to Maven 3.1 and Java 7, or even Maven 3 and Java 5, I
Hi,
Thanks for the hint.
The wiki page you mentioned was the first thing I read when I started.
It's worth to say that it states only one explicit requirement: "Do not
name your plugin maven-SOMETHING-plugin."
The phrase You will typically name your
plugin|-maven-plugin|. does not sound as a
On Tue, 26 May 2020 at 08:05, Robert Scholte wrote:
> I missed the proposal for the version. I saw 3.2.5 and that can't be
> correct, hence I tried to explain what the correct version should be.
> So correct minimum version will be one of: 3.0, 3.1.0, 3.2.1, 3.3.1, 3.5.0
> This is the version we
Hi,
Yes, this works. Thank you. :)
A followup question... running whole build like this is a bit clunky.
Basically I have to execute:
mvn clean install
cz.fiisch.maven.plugin.deploy.askpass:askpass-deploy-plugin:1.0-SNAPSHOT:askpass
deploy
to do the whole build. This should be ok as long
Hi
Thanks a lot.
I have merged the first one
2 others moved as branch pr-{id} to check Jenkins build.
If no one else merged, I will finish my tomm.
cheers
Olivier
On Tue, 26 May 2020 at 08:19, Robert Oxspring
wrote:
> Hi folks,
>
>
> I’ve got a few open pull requests (one approved) but without
On Tue, May 26, 2020 at 8:37 AM Olivier Lamy wrote:
> On Tue, 26 May 2020 at 08:05, Robert Scholte wrote:
>
> > I think it is pretty impressive that we can say that our plugins still
> > support a wide range of Maven versions.
> >
> > So my vote will be 3.1.0
> >
>
> even if it doesn't happen
Hi,
The vote has passed with the following result:
+1: Arnaud Hértier, Enrico Olivelli, Olivier Lamy, Karl Heinz Marbaise,
Robert Scholte
PMC quorum: reached
I will promote the artifacts to the central repo, the source release ZIP
file
and add this release the board report.
As creating a new maven-artifact-plugin will probably take some time, maybe it
would be possible to push a release build of
https://github.com/apache/maven-studies/tree/maven-buildinfo-plugin to Maven
Central. Or is there already a rough schedule for coming up with the new
Am 2020-05-23 um 23:13 schrieb Michael Osipov:
Hi,
We solved 13 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317821=12346620
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/projects/MPIR/issues
Staging repo:
The Apache Maven team is pleased to announce the release of the Apache
Maven Wagon, version 3.4.1.
https://maven.apache.org/wagon/
Release Notes - Maven Wagon - Version 3.4.1
** Bug
* [WAGON-591] - Transfer event is not restarted when request is
redirected
* [WAGON-592] - Wagon
Hi,
The vote has passed with the following result:
+1: Michael Osipov, Robert Scholte, Karl Heinz Marbaise
PMC quorum: reached
I will promote the artifacts to the central repo, the source release ZIP
file
and add this release the board report.
The Apache Maven team is pleased to announce the release of the Maven
Project Info Reports Plugin version 3.1.0.
https://maven.apache.org/plugins/maven-project-info-reports-plugin/
You should specify the version in your project's plugin configuration:
org.apache.maven.plugins
+1
On 23-5-2020 23:13:30, Michael Osipov wrote:
Hi,
We solved 13 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317821=12346620
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/projects/MPIR/issues
Staging repo:
elharo opened a new pull request #29:
URL: https://github.com/apache/maven-site-plugin/pull/29
@michael-o
exclusion no longer necessary with latest doxias
[INFO] +- org.apache.maven.doxia:doxia-site-renderer:jar:1.9.2:compile
[INFO] | +-
asfgit closed pull request #12:
URL: https://github.com/apache/maven-site-plugin/pull/12
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
slachiewicz closed pull request #27:
URL: https://github.com/apache/maven-site-plugin/pull/27
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL
elharo opened a new pull request #12:
URL: https://github.com/apache/maven-artifact-transfer/pull/12
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
elharo merged pull request #24:
URL: https://github.com/apache/maven-site-plugin/pull/24
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
elharo merged pull request #12:
URL: https://github.com/apache/maven-artifact-transfer/pull/12
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL
elharo merged pull request #171:
URL: https://github.com/apache/maven-site/pull/171
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
slachiewicz commented on pull request #27:
URL: https://github.com/apache/maven-site-plugin/pull/27#issuecomment-633969397
This is an automated message from the Apache Git Service.
To respond to the message, please log on to
On Tue, 26 May 2020 at 22:47, Elliotte Rusty Harold
wrote:
> I don't think I've seen anything earlier than 3.3.x in recent memory,
> but 3.3.x is definitely still out there in the wild being used for new
> development.
>
> Given the massive amount of important work that remains to be done to
>
elharo opened a new pull request #28:
URL: https://github.com/apache/maven-site-plugin/pull/28
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL
elharo merged pull request #26:
URL: https://github.com/apache/maven-site-plugin/pull/26
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
slachiewicz commented on pull request #24:
URL: https://github.com/apache/maven-site-plugin/pull/24#issuecomment-633713346
Ok #12 merged to master. Please rebase a d resolve conflicts in this pr
This is an automated message
slachiewicz opened a new pull request #27:
URL: https://github.com/apache/maven-site-plugin/pull/27
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
elharo merged pull request #29:
URL: https://github.com/apache/maven-site-plugin/pull/29
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
elharo merged pull request #28:
URL: https://github.com/apache/maven-site-plugin/pull/28
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
elharo commented on pull request #27:
URL: https://github.com/apache/maven-site-plugin/pull/27#issuecomment-634132747
seems to have broken Jenkins:
https://builds.apache.org/job/maven-box/job/maven-site-plugin/job/master/99/
elharo opened a new pull request #26:
URL: https://github.com/apache/maven-site-plugin/pull/26
@olamy
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
31 matches
Mail list logo
