Re: [VOTE] Release Maven Site Plugin version 3.8.1

2019-07-07 Thread Graham Leggett 
On 07 Jul 2019, at 20:51, Michael Osipov  wrote:

> I, too, now see this on the ASF Jenkins instance.
> 
> Can you file an issue and add your finding please? I don't want your effort 
> to be lost in the archives. Someone needs to start digging to find the 
> mismatch. So the IT itself is fine, but the environment is unreliable.

I’ve added the issue here, with a patch:

https://issues.apache.org/jira/browse/MSITE-846

Regards,
Graham
—



smime.p7s
Description: S/MIME cryptographic signature

Re: [VOTE] Release Maven Site Plugin version 3.8.1

2019-07-07 Thread Michael Osipov 

Am 2019-07-07 um 12:13 schrieb Graham Leggett:

On 06 Jul 2019, at 15:02, Graham Leggett  wrote:


I am at a loss as to why - after both tests above, pass and fail, there is no 
file anywhere called target/it/effective-site/effective-site.xml.

The test itself seems straightforward. Create a file called 
effective-site.xml...

[minfrin@gatekeeper maven-site-plugin-3.8.1]$ cat 
src/it/projects/effective-site/invoker.properties
[snip]
invoker.goals = clean site:effective-site
invoker.mavenOpts = -Doutput=effective-site.xml

…and test effective-site.xml exists:

[minfrin@gatekeeper maven-site-plugin-3.8.1]$ cat 
src/it/projects/effective-site/verify.groovy
[snip]
assert new File( basedir, 'effective-site.xml' ).exists();

Looking at target/it/effective-site/build.log in the failure case, the 
effective site is written to the build.log, and not the -Doutput= like it 
should have been.

Not sure what could cause this, something overriding invoker.mavenOpts?


I think this could be caused by different versions of maven plugins being run 
in the two different scenarios. When I ran “invoker:run” directly for the first 
time, a different version of the failsafe plugin was downloaded as opposed to 
when the invoker plugin triggered the tests :

[minfrin@gatekeeper maven-site-plugin-3.8.1]$ mvn invoker:run 
-Dinvoker.test=effective-site
[INFO] Scanning for projects...
Downloading from central: 
https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-deploy-plugin/2.8.2/maven-deploy-plugin-2.8.2.jar
Downloaded from central: 
https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-deploy-plugin/2.8.2/maven-deploy-plugin-2.8.2.jar
 (34 kB at 20 kB/s)
Downloading from central: 
https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-assembly-plugin/3.0.0/maven-assembly-plugin-3.0.0.jar
Downloaded from central: 
https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-assembly-plugin/3.0.0/maven-assembly-plugin-3.0.0.jar
 (241 kB at 262 kB/s)
Downloading from central: 
https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-docck-plugin/1.1/maven-docck-plugin-1.1.jar
Downloaded from central: 
https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-docck-plugin/1.1/maven-docck-plugin-1.1.jar
 (34 kB at 74 kB/s)
Downloading from central: 
https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-ear-plugin/3.0.1/maven-ear-plugin-3.0.1.pom
Downloaded from central: 
https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-ear-plugin/3.0.1/maven-ear-plugin-3.0.1.pom
 (11 kB at 30 kB/s)
Downloading from central: 
https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-ear-plugin/3.0.1/maven-ear-plugin-3.0.1.jar
Downloaded from central: 
https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-ear-plugin/3.0.1/maven-ear-plugin-3.0.1.jar
 (88 kB at 230 kB/s)
Downloading from central: 
https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-failsafe-plugin/2.22.0/maven-failsafe-plugin-2.22.0.pom
Downloaded from central: 
https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-failsafe-plugin/2.22.0/maven-failsafe-plugin-2.22.0.pom
 (12 kB at 32 kB/s)
Downloading from central: 
https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-failsafe-plugin/2.22.0/maven-failsafe-plugin-2.22.0.jar
Downloaded from central: 
https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-failsafe-plugin/2.22.0/maven-failsafe-plugin-2.22.0.jar
 (294 kB at 370 kB/s)
Downloading from central: 
https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-gpg-plugin/1.6/maven-gpg-plugin-1.6.jar
Downloaded from central: 
https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-gpg-plugin/1.6/maven-gpg-plugin-1.6.jar
 (47 kB at 127 kB/s)
Downloading from central: 
https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-help-plugin/3.1.0/maven-help-plugin-3.1.0.pom
Downloaded from central: 
https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-help-plugin/3.1.0/maven-help-plugin-3.1.0.pom
 (9.5 kB at 26 kB/s)
Downloading from central: 
https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-help-plugin/3.1.0/maven-help-plugin-3.1.0.jar
Downloaded from central: 
https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-help-plugin/3.1.0/maven-help-plugin-3.1.0.jar
 (64 kB at 164 kB/s)
[INFO]
[INFO] -< org.apache.maven.plugins:maven-site-plugin >-
[INFO] Building Apache Maven Site Plugin 3.8.1

I think the maven-site-plugin should probably decide what versions of failsafe 
and surefire that it wants to run. The invoker plugin instantiates a whole new 
maven, so I suspect each test needs to decide that versions of failsafe to run 
too.


I, too, now see this on the ASF Jenkins instance.

Can you file an issue and add your finding please? I don't want your 
effort to be lost in the archives. Someone needs to

Re: [VOTE] Release Maven Site Plugin version 3.8.1

2019-07-07 Thread Graham Leggett 
On 06 Jul 2019, at 15:02, Graham Leggett  wrote:

> I am at a loss as to why - after both tests above, pass and fail, there is no 
> file anywhere called target/it/effective-site/effective-site.xml.
> 
> The test itself seems straightforward. Create a file called 
> effective-site.xml...
> 
> [minfrin@gatekeeper maven-site-plugin-3.8.1]$ cat 
> src/it/projects/effective-site/invoker.properties
> [snip]
> invoker.goals = clean site:effective-site
> invoker.mavenOpts = -Doutput=effective-site.xml
> 
> …and test effective-site.xml exists:
> 
> [minfrin@gatekeeper maven-site-plugin-3.8.1]$ cat 
> src/it/projects/effective-site/verify.groovy 
> [snip]
> assert new File( basedir, 'effective-site.xml' ).exists();
> 
> Looking at target/it/effective-site/build.log in the failure case, the 
> effective site is written to the build.log, and not the -Doutput= like it 
> should have been.
> 
> Not sure what could cause this, something overriding invoker.mavenOpts?

I think this could be caused by different versions of maven plugins being run 
in the two different scenarios. When I ran “invoker:run” directly for the first 
time, a different version of the failsafe plugin was downloaded as opposed to 
when the invoker plugin triggered the tests :

[minfrin@gatekeeper maven-site-plugin-3.8.1]$ mvn invoker:run 
-Dinvoker.test=effective-site
[INFO] Scanning for projects...
Downloading from central: 
https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-deploy-plugin/2.8.2/maven-deploy-plugin-2.8.2.jar
Downloaded from central: 
https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-deploy-plugin/2.8.2/maven-deploy-plugin-2.8.2.jar
 (34 kB at 20 kB/s)
Downloading from central: 
https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-assembly-plugin/3.0.0/maven-assembly-plugin-3.0.0.jar
Downloaded from central: 
https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-assembly-plugin/3.0.0/maven-assembly-plugin-3.0.0.jar
 (241 kB at 262 kB/s)
Downloading from central: 
https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-docck-plugin/1.1/maven-docck-plugin-1.1.jar
Downloaded from central: 
https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-docck-plugin/1.1/maven-docck-plugin-1.1.jar
 (34 kB at 74 kB/s)
Downloading from central: 
https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-ear-plugin/3.0.1/maven-ear-plugin-3.0.1.pom
Downloaded from central: 
https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-ear-plugin/3.0.1/maven-ear-plugin-3.0.1.pom
 (11 kB at 30 kB/s)
Downloading from central: 
https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-ear-plugin/3.0.1/maven-ear-plugin-3.0.1.jar
Downloaded from central: 
https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-ear-plugin/3.0.1/maven-ear-plugin-3.0.1.jar
 (88 kB at 230 kB/s)
Downloading from central: 
https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-failsafe-plugin/2.22.0/maven-failsafe-plugin-2.22.0.pom
Downloaded from central: 
https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-failsafe-plugin/2.22.0/maven-failsafe-plugin-2.22.0.pom
 (12 kB at 32 kB/s)
Downloading from central: 
https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-failsafe-plugin/2.22.0/maven-failsafe-plugin-2.22.0.jar
Downloaded from central: 
https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-failsafe-plugin/2.22.0/maven-failsafe-plugin-2.22.0.jar
 (294 kB at 370 kB/s)
Downloading from central: 
https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-gpg-plugin/1.6/maven-gpg-plugin-1.6.jar
Downloaded from central: 
https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-gpg-plugin/1.6/maven-gpg-plugin-1.6.jar
 (47 kB at 127 kB/s)
Downloading from central: 
https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-help-plugin/3.1.0/maven-help-plugin-3.1.0.pom
Downloaded from central: 
https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-help-plugin/3.1.0/maven-help-plugin-3.1.0.pom
 (9.5 kB at 26 kB/s)
Downloading from central: 
https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-help-plugin/3.1.0/maven-help-plugin-3.1.0.jar
Downloaded from central: 
https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-help-plugin/3.1.0/maven-help-plugin-3.1.0.jar
 (64 kB at 164 kB/s)
[INFO] 
[INFO] -< org.apache.maven.plugins:maven-site-plugin >-
[INFO] Building Apache Maven Site Plugin 3.8.1

I think the maven-site-plugin should probably decide what versions of failsafe 
and surefire that it wants to run. The invoker plugin instantiates a whole new 
maven, so I suspect each test needs to decide that versions of failsafe to run 
too.

Regards,
Graham
—




smime.p7s
Description: S/MIME cryptographic signature

[CANCELED] [VOTE] Release Maven Site Plugin version 3.8.1

2019-07-07 Thread Michael Osipov 

Vote has been canceled due to unresolved conflicts regarding Java 8.

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

Re: [VOTE] Release Maven Site Plugin version 3.8.1

2019-07-06 Thread Graham Leggett 
On 04 Jul 2019, at 22:04, Michael Osipov  wrote:

>> One test failed, however this test also fails in maven-site-plugin v3.7.1, 
>> so this is not a regression:
>> [INFO] Building: effective-site/pom.xml
>> [INFO] run post-build script verify.groovy
>> [INFO]   effective-site/pom.xml ... FAILED 
>> (6.0 s)
>> [INFO]   The post-build script did not succeed. assert new File( basedir, 
>> 'effective-site.xml' ).exists()
>>| |   |
>>| |   false
>>| 
>> /home/gatekeeper/minfrin/src/apache/sandbox/maven/maven-site-plugin-maven-site-plugin-3.7.1/target/it/effective-site
>>
>> /home/gatekeeper/minfrin/src/apache/sandbox/maven/maven-site-plugin-maven-site-plugin-3.7.1/target/it/effective-site/effective-site.xml
> 
> Can you share why this one fails for you, but not for me on three different 
> operating systems? I'd like to fix this.

This has made my head bleed.

Run the test on its own, and the test passes:

[minfrin@gatekeeper maven-site-plugin-3.8.1]$ mvn invoker:run 
-Dinvoker.test=projects/effective-site*
[INFO] Scanning for projects...
[INFO] 
[INFO] -< org.apache.maven.plugins:maven-site-plugin >-
[INFO] Building Apache Maven Site Plugin 3.8.1
[INFO] [ maven-plugin ]
[INFO] 
[INFO] --- maven-invoker-plugin:3.1.0:run (default-cli) @ maven-site-plugin ---
[INFO] Building: projects/effective-site/pom.xml
[INFO]   projects/effective-site/pom.xml .. SUCCESS 
(5.5 s)
[INFO] -
[INFO] Build Summary:
[INFO]   Passed: 1, Failed: 0, Errors: 0, Skipped: 0
[INFO] -
[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time:  8.349 s
[INFO] Finished at: 2019-07-06T14:37:27+02:00
[INFO] 

Run the whole test suite, and this test fails:

[minfrin@gatekeeper maven-site-plugin-3.8.1]$ mvn install -P run-its
[snip]
[INFO] Building: effective-site/pom.xml
[INFO] run post-build script verify.groovy
[INFO]   effective-site/pom.xml ... FAILED (4.8 
s)
[INFO]   The post-build script did not succeed. assert new File( basedir, 
'effective-site.xml' ).exists()
   | |   |
   | |   false
   | 
/home/gatekeeper/minfrin/src/apache/sandbox/maven/maven-site-plugin-3.8.1/target/it/effective-site
   
/home/gatekeeper/minfrin/src/apache/sandbox/maven/maven-site-plugin-3.8.1/target/it/effective-site/effective-site.xml

I am at a loss as to why - after both tests above, pass and fail, there is no 
file anywhere called target/it/effective-site/effective-site.xml.

The test itself seems straightforward. Create a file called 
effective-site.xml...

[minfrin@gatekeeper maven-site-plugin-3.8.1]$ cat 
src/it/projects/effective-site/invoker.properties
[snip]
invoker.goals = clean site:effective-site
invoker.mavenOpts = -Doutput=effective-site.xml

…and test effective-site.xml exists:

[minfrin@gatekeeper maven-site-plugin-3.8.1]$ cat 
src/it/projects/effective-site/verify.groovy 
[snip]
assert new File( basedir, 'effective-site.xml' ).exists();

Looking at target/it/effective-site/build.log in the failure case, the 
effective site is written to the build.log, and not the -Doutput= like it 
should have been.

Not sure what could cause this, something overriding invoker.mavenOpts?

Regards,
Graham
—



smime.p7s
Description: S/MIME cryptographic signature

Re: [VOTE] Release Maven Site Plugin version 3.8.1

2019-07-05 Thread Eric Lilja 
+1 (non-binding)

- Eric Lilja

On Thu, Jul 4, 2019 at 10:04 PM Michael Osipov  wrote:

> Am 2019-07-03 um 23:54 schrieb Graham Leggett:
> > On 01 Jul 2019, at 23:10, Michael Osipov  wrote:
> >
> >> We solved 11 issues:
> >>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317923=12343145
> >>
> >> There are still a couple of issues left in JIRA:
> >>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSITE%20AND%20resolution%20%3D%20Unresolved
> >>
> >> Staging repo:
> >> https://repository.apache.org/content/repositories/maven-1520/
> >>
> https://repository.apache.org/content/repositories/maven-1520/org/apache/maven/plugins/maven-site-plugin/3.8.1/maven-site-plugin-3.8.1-source-release.zip
> >>
> >> Source release checksum(s):
> >> maven-site-plugin-3.8.1-source-release.zip
> >> sha512:
> e4e001e848267c50052e2261f98f7b4c0fcc9833d13245c69dc06d26b30f814061048d6bebaef8464120133ffb503c002ddaecdfc9b234801b4ca7729c7a24cd
> >>
> >> Staging site:
> >> https://maven.apache.org/plugins-archives/maven-site-plugin-LATEST/
> >>
> >> Guide to testing staged releases:
> >> https://maven.apache.org/guides/development/guide-testing-releases.html
> >>
> >> Vote open for 72 hours.
> >>
> >> [ ] +1
> >> [ ] +0
> >> [ ] -1
> >
> > Like last time, +1 on Java8.
> >
> > One test failed, however this test also fails in maven-site-plugin
> v3.7.1, so this is not a regression:
> >
> > [INFO] Building: effective-site/pom.xml
> > [INFO] run post-build script verify.groovy
> > [INFO]   effective-site/pom.xml ...
> FAILED (6.0 s)
> > [INFO]   The post-build script did not succeed. assert new File(
> basedir, 'effective-site.xml' ).exists()
> > | |   |
> > | |   false
> > |
>  
> /home/gatekeeper/minfrin/src/apache/sandbox/maven/maven-site-plugin-maven-site-plugin-3.7.1/target/it/effective-site
> >
>  
> /home/gatekeeper/minfrin/src/apache/sandbox/maven/maven-site-plugin-maven-site-plugin-3.7.1/target/it/effective-site/effective-site.xml
>
> Can you share why this one fails for you, but not for me on three
> different operating systems? I'd like to fix this.
>
> Michael
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Re: [VOTE] Release Maven Site Plugin version 3.8.1

2019-07-04 Thread Michael Osipov 

Am 2019-07-03 um 23:54 schrieb Graham Leggett:

On 01 Jul 2019, at 23:10, Michael Osipov  wrote:


We solved 11 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317923=12343145

There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSITE%20AND%20resolution%20%3D%20Unresolved

Staging repo:
https://repository.apache.org/content/repositories/maven-1520/
https://repository.apache.org/content/repositories/maven-1520/org/apache/maven/plugins/maven-site-plugin/3.8.1/maven-site-plugin-3.8.1-source-release.zip

Source release checksum(s):
maven-site-plugin-3.8.1-source-release.zip
sha512: 
e4e001e848267c50052e2261f98f7b4c0fcc9833d13245c69dc06d26b30f814061048d6bebaef8464120133ffb503c002ddaecdfc9b234801b4ca7729c7a24cd

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

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

Vote open for 72 hours.

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


Like last time, +1 on Java8.

One test failed, however this test also fails in maven-site-plugin v3.7.1, so 
this is not a regression:

[INFO] Building: effective-site/pom.xml
[INFO] run post-build script verify.groovy
[INFO]   effective-site/pom.xml ... FAILED (6.0 
s)
[INFO]   The post-build script did not succeed. assert new File( basedir, 
'effective-site.xml' ).exists()
| |   |
| |   false
| 
/home/gatekeeper/minfrin/src/apache/sandbox/maven/maven-site-plugin-maven-site-plugin-3.7.1/target/it/effective-site

/home/gatekeeper/minfrin/src/apache/sandbox/maven/maven-site-plugin-maven-site-plugin-3.7.1/target/it/effective-site/effective-site.xml


Can you share why this one fails for you, but not for me on three 
different operating systems? I'd like to fix this.


Michael

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

Re: [VOTE] Release Maven Site Plugin version 3.8.1

2019-07-04 Thread Michael Osipov 

Am 2019-07-04 um 13:12 schrieb Tibor Digana:

Did you read the Jira and the commit in Git?
It was written in the way to push Java 8 without any strong reason, sorry
for that but it's truth.
I would like to see v9.2 first (after v6) in 3.8.1 and then wait for Maven
3.7.0 which will go most probably with J8. We can release Site 3.9.0 and
use it in bindings in Maven 3.7.0. So we will have strictly segregated
Maven and plugins before MVN 3.7 and embedded plugins for MVN 3.7+. If we
move one plugin to J8 then move all but do it for MVN 3.7+.

We can see that our code may benefit from Lambda, no objections to it. But
this movement needs to be organized in a similar way how we moved al our
plugins to API 3.0. Using one plugin with J8 and not the other means, don't
be afraid, chaos.


I have expressed the very same concerns. This is *not* my fault. People 
demanded to upgrade to 9.4 because of "security" for test scope. Ridiculous.


Please raise another issue to roll this back and ping the previous 
dicussion roster. See this one: 
https://github.com/apache/maven-site-plugin/pull/3#issuecomment-437158167


Personally, absolutely see no reason to move to Java 8 unless I use Java 
8 features.



On Thu, Jul 4, 2019 at 12:53 PM Graham Leggett  wrote:


On 04 Jul 2019, at 09:03, Tibor Digana  wrote:

The build passed successfully after I have used Jetty 9.2.9.v20150224. (no
need to change our code in the plugin)
It was the last J7 but v9.x Jetty.


The reasoning in https://github.com/apache/maven-site-plugin/pull/3 makes
sense to me, insecure dependencies need fixing - can you confirm
whether Jetty 9.2.9.v20150224 resolves the insecure dependencies issue
fixed by this patch?

Regards,
Graham
—








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

Re: [VOTE] Release Maven Site Plugin version 3.8.1

2019-07-04 Thread Michael Osipov 

Am 2019-07-04 um 07:52 schrieb Tibor Digana:

Additionally, if I want to make such a big change like using higher Java
version, I have to upgrade the version of the plugin to 3.9.0 at least. I
was pointing to Java 1.8 in the previous vote.


This was done actually in 3.8.0, a minor release. I have recalled the 
vote due to another bug which had to be fixed for 3.8. Please see the 
vote for 3.8.



And there's interesting unit test which fails. It needs to be investigated
together with Graham in a separate mail thread.

On Thu, Jul 4, 2019 at 7:39 AM Tibor Digana  wrote:


-1: still no answered reasoning about Jetty 9 and Java 8.

On Thu, Jul 4, 2019 at 8:32 AM Michael Osipov  wrote:


Am 2019-07-01 um 23:10 schrieb Michael Osipov:

Hi,

We solved 11 issues:


https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317923=12343145



There are still a couple of issues left in JIRA:


https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSITE%20AND%20resolution%20%3D%20Unresolved



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


https://repository.apache.org/content/repositories/maven-1520/org/apache/maven/plugins/maven-site-plugin/3.8.1/maven-site-plugin-3.8.1-source-release.zip



Source release checksum(s):
maven-site-plugin-3.8.1-source-release.zip
sha512:


e4e001e848267c50052e2261f98f7b4c0fcc9833d13245c69dc06d26b30f814061048d6bebaef8464120133ffb503c002ddaecdfc9b234801b4ca7729c7a24cd




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

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

Vote open for 72 hours.


+1

Guys, I need two more binding votes until tomorrow.

-
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: [VOTE] Release Maven Site Plugin version 3.8.1

2019-07-04 Thread Michael Osipov 

That's not true. I answered you with the PR in
Message-ID: <445f420e-6522-6d3c-53c4-27db0415a...@apache.org>

Am 2019-07-04 um 07:39 schrieb Tibor Digana:

-1: still no answered reasoning about Jetty 9 and Java 8.

On Thu, Jul 4, 2019 at 8:32 AM Michael Osipov  wrote:


Am 2019-07-01 um 23:10 schrieb Michael Osipov:

Hi,

We solved 11 issues:


https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317923=12343145



There are still a couple of issues left in JIRA:


https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSITE%20AND%20resolution%20%3D%20Unresolved



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


https://repository.apache.org/content/repositories/maven-1520/org/apache/maven/plugins/maven-site-plugin/3.8.1/maven-site-plugin-3.8.1-source-release.zip



Source release checksum(s):
maven-site-plugin-3.8.1-source-release.zip
sha512:


e4e001e848267c50052e2261f98f7b4c0fcc9833d13245c69dc06d26b30f814061048d6bebaef8464120133ffb503c002ddaecdfc9b234801b4ca7729c7a24cd




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

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

Vote open for 72 hours.


+1

Guys, I need two more binding votes until tomorrow.

-
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: [VOTE] Release Maven Site Plugin version 3.8.1

2019-07-04 Thread Bertrand Martin 
+1

On 2019/07/01 21:10:52, Michael Osipov  wrote:
> Hi,>
>
> We solved 11 issues:>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317923=12343145>
>
> There are still a couple of issues left in JIRA:>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSITE%20AND%20resolution%20%3D%20Unresolved>
>
> Staging repo:>
> https://repository.apache.org/content/repositories/maven-1520/>
> https://repository.apache.org/content/repositories/maven-1520/org/apache/maven/plugins/maven-site-plugin/3.8.1/maven-site-plugin-3.8.1-source-release.zip>

>
> Source release checksum(s):>
> maven-site-plugin-3.8.1-source-release.zip>
> sha512: >
> e4e001e848267c50052e2261f98f7b4c0fcc9833d13245c69dc06d26b30f814061048d6bebaef8464120133ffb503c002ddaecdfc9b234801b4ca7729c7a24cd>

>
> Staging site:>
> https://maven.apache.org/plugins-archives/maven-site-plugin-LATEST/>
>
> Guide to testing staged releases:>
> https://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 Maven Site Plugin version 3.8.1

2019-07-04 Thread Tibor Digana 
Hello Graham,

I agree with Herve who said in MSITE-837 that the goal "site:run" is
temporarily used by developers when he wants to see the web content in
browser. This goal should not be used in permanent deployment and of course
not in public or production where the security has to be the important
point. There are many very good webcontainers with good security guarantees
which can be installed even for public use and I believe the organizations
would not run Maven goal only because of publishing web content in public
and so they would use Tomcat or Wildfly for instance.

>> 9.2.9.v20150224 works with java7 - does that version also have secure
dependencies?

Not sure which artifact you mean. The version 9.2.9 has the artifact
"jetty-security" too, so perhaps this is the one expected.

Reading MSITE-837 does not list details about the security patches.
Not sure what criteria you guys have, perhaps TLS version or HTTPS or some
security issues, not sure exactly.

Is the security related to Java compiler version or Java runtime version?
Because if it is runtime then it's even easier and we can write a hint in
documentation to use JDK8+.Hello Graham,

Cheers
Tibor17



On Thu, Jul 4, 2019 at 1:48 PM Graham Leggett  wrote:

> On 04 Jul 2019, at 13:12, Tibor Digana  wrote:
>
> Did you read the Jira and the commit in Git?
> It was written in the way to push Java 8 without any strong reason, sorry
> for that but it's truth.
>
>
> I’m not following.
>
> Jetty is a compile time dependency of the maven-site-plugin, I believe
> it’s used to make site:run work.
>
> [INFO] +- org.eclipse.jetty:jetty-server:jar:9.4.12.v20180830:compile
> [INFO] |  +- javax.servlet:javax.servlet-api:jar:3.1.0:compile
> [INFO] |  +- org.eclipse.jetty:jetty-http:jar:9.4.12.v20180830:compile
> [INFO] |  \- org.eclipse.jetty:jetty-io:jar:9.4.12.v20180830:compile
> [INFO] +- org.eclipse.jetty:jetty-servlet:jar:9.4.12.v20180830:compile
> [INFO] |  \- org.eclipse.jetty:jetty-security:jar:9.4.12.v20180830:compile
> [INFO] +- org.eclipse.jetty:jetty-webapp:jar:9.4.12.v20180830:compile
> [INFO] |  \- org.eclipse.jetty:jetty-xml:jar:9.4.12.v20180830:compile
> [INFO] +- org.eclipse.jetty:jetty-util:jar:9.4.12.v20180830:compile
>
> Old versions of jetty pull in insecure dependencies (that’s the point of
> the ticket and patch, as I read it).
>
> The outstanding question is, what is the minimum java version supported by
> the oldest jetty that has fixed secure dependencies? You’ve confirmed Jetty
> 9.2.9.v20150224 works with java7 - does that version also have secure
> dependencies?
>
> I would like to see v9.2 first (after v6) in 3.8.1 and then wait for Maven
> 3.7.0 which will go most probably with J8. We can release Site 3.9.0 and
> use it in bindings in Maven 3.7.0. So we will have strictly segregated
> Maven and plugins before MVN 3.7 and embedded plugins for MVN 3.7+. If we
> move one plugin to J8 then move all but do it for MVN 3.7+.
>
>
> So would you say you’d prefer to delay fixing
> https://issues.apache.org/jira/browse/MSITE-829 until maven 3.7.0 is a
> thing?
>
> (I have no opinion at this point, if there are two maven-site-plugin
> releases, one with the fix deferred, and another with the fix, that seems
> reasonable to me).
>
> Regards,
> Graham
> —
>
>

Re: [VOTE] Release Maven Site Plugin version 3.8.1

2019-07-04 Thread Graham Leggett 
On 04 Jul 2019, at 13:12, Tibor Digana  wrote:

> Did you read the Jira and the commit in Git?
> It was written in the way to push Java 8 without any strong reason, sorry
> for that but it's truth.

I’m not following.

Jetty is a compile time dependency of the maven-site-plugin, I believe it’s 
used to make site:run work.

[INFO] +- org.eclipse.jetty:jetty-server:jar:9.4.12.v20180830:compile
[INFO] |  +- javax.servlet:javax.servlet-api:jar:3.1.0:compile
[INFO] |  +- org.eclipse.jetty:jetty-http:jar:9.4.12.v20180830:compile
[INFO] |  \- org.eclipse.jetty:jetty-io:jar:9.4.12.v20180830:compile
[INFO] +- org.eclipse.jetty:jetty-servlet:jar:9.4.12.v20180830:compile
[INFO] |  \- org.eclipse.jetty:jetty-security:jar:9.4.12.v20180830:compile
[INFO] +- org.eclipse.jetty:jetty-webapp:jar:9.4.12.v20180830:compile
[INFO] |  \- org.eclipse.jetty:jetty-xml:jar:9.4.12.v20180830:compile
[INFO] +- org.eclipse.jetty:jetty-util:jar:9.4.12.v20180830:compile

Old versions of jetty pull in insecure dependencies (that’s the point of the 
ticket and patch, as I read it).

The outstanding question is, what is the minimum java version supported by the 
oldest jetty that has fixed secure dependencies? You’ve confirmed Jetty 
9.2.9.v20150224 works with java7 - does that version also have secure 
dependencies?

> I would like to see v9.2 first (after v6) in 3.8.1 and then wait for Maven
> 3.7.0 which will go most probably with J8. We can release Site 3.9.0 and
> use it in bindings in Maven 3.7.0. So we will have strictly segregated
> Maven and plugins before MVN 3.7 and embedded plugins for MVN 3.7+. If we
> move one plugin to J8 then move all but do it for MVN 3.7+.

So would you say you’d prefer to delay fixing 
https://issues.apache.org/jira/browse/MSITE-829 until maven 3.7.0 is a thing?

(I have no opinion at this point, if there are two maven-site-plugin releases, 
one with the fix deferred, and another with the fix, that seems reasonable to 
me).

Regards,
Graham
—



smime.p7s
Description: S/MIME cryptographic signature

Re: [VOTE] Release Maven Site Plugin version 3.8.1

2019-07-04 Thread Tibor Digana 
Did you read the Jira and the commit in Git?
It was written in the way to push Java 8 without any strong reason, sorry
for that but it's truth.
I would like to see v9.2 first (after v6) in 3.8.1 and then wait for Maven
3.7.0 which will go most probably with J8. We can release Site 3.9.0 and
use it in bindings in Maven 3.7.0. So we will have strictly segregated
Maven and plugins before MVN 3.7 and embedded plugins for MVN 3.7+. If we
move one plugin to J8 then move all but do it for MVN 3.7+.

We can see that our code may benefit from Lambda, no objections to it. But
this movement needs to be organized in a similar way how we moved al our
plugins to API 3.0. Using one plugin with J8 and not the other means, don't
be afraid, chaos.


On Thu, Jul 4, 2019 at 12:53 PM Graham Leggett  wrote:

> On 04 Jul 2019, at 09:03, Tibor Digana  wrote:
>
> The build passed successfully after I have used Jetty 9.2.9.v20150224. (no
> need to change our code in the plugin)
> It was the last J7 but v9.x Jetty.
>
>
> The reasoning in https://github.com/apache/maven-site-plugin/pull/3 makes
> sense to me, insecure dependencies need fixing - can you confirm
> whether Jetty 9.2.9.v20150224 resolves the insecure dependencies issue
> fixed by this patch?
>
> Regards,
> Graham
> —
>
>

Re: [VOTE] Release Maven Site Plugin version 3.8.1

2019-07-04 Thread Graham Leggett 
On 04 Jul 2019, at 09:03, Tibor Digana  wrote:

> The build passed successfully after I have used Jetty 9.2.9.v20150224. (no
> need to change our code in the plugin)
> It was the last J7 but v9.x Jetty.

The reasoning in https://github.com/apache/maven-site-plugin/pull/3 
 makes sense to me, 
insecure dependencies need fixing - can you confirm whether Jetty 
9.2.9.v20150224 resolves the insecure dependencies issue fixed by this patch?

Regards,
Graham
—



smime.p7s
Description: S/MIME cryptographic signature

Re: [VOTE] Release Maven Site Plugin version 3.8.1

2019-07-04 Thread Olivier Lamy 
+1

On Tue, 2 Jul 2019 at 9:10 am, Michael Osipov  wrote:

> Hi,
>
> We solved 11 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317923=12343145
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSITE%20AND%20resolution%20%3D%20Unresolved
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1520/
>
> https://repository.apache.org/content/repositories/maven-1520/org/apache/maven/plugins/maven-site-plugin/3.8.1/maven-site-plugin-3.8.1-source-release.zip
>
> Source release checksum(s):
> maven-site-plugin-3.8.1-source-release.zip
> sha512:
>
> e4e001e848267c50052e2261f98f7b4c0fcc9833d13245c69dc06d26b30f814061048d6bebaef8464120133ffb503c002ddaecdfc9b234801b4ca7729c7a24cd
>
> Staging site:
> https://maven.apache.org/plugins-archives/maven-site-plugin-LATEST/
>
> Guide to testing staged releases:
> https://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
>
> --
Olivier Lamy
http://twitter.com/olamy | http://linkedin.com/in/olamy

Re: [VOTE] Release Maven Site Plugin version 3.8.1

2019-07-04 Thread Tibor Digana 
The build passed successfully after I have used Jetty 9.2.9.v20150224. (no
need to change our code in the plugin)
It was the last J7 but v9.x Jetty.

On Mon, Jul 1, 2019 at 11:11 PM Michael Osipov  wrote:

> Hi,
>
> We solved 11 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317923=12343145
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSITE%20AND%20resolution%20%3D%20Unresolved
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1520/
>
> https://repository.apache.org/content/repositories/maven-1520/org/apache/maven/plugins/maven-site-plugin/3.8.1/maven-site-plugin-3.8.1-source-release.zip
>
> Source release checksum(s):
> maven-site-plugin-3.8.1-source-release.zip
> sha512:
>
> e4e001e848267c50052e2261f98f7b4c0fcc9833d13245c69dc06d26b30f814061048d6bebaef8464120133ffb503c002ddaecdfc9b234801b4ca7729c7a24cd
>
> Staging site:
> https://maven.apache.org/plugins-archives/maven-site-plugin-LATEST/
>
> Guide to testing staged releases:
> https://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 Maven Site Plugin version 3.8.1

2019-07-04 Thread Tibor Digana 
Additionally, if I want to make such a big change like using higher Java
version, I have to upgrade the version of the plugin to 3.9.0 at least. I
was pointing to Java 1.8 in the previous vote.
And there's interesting unit test which fails. It needs to be investigated
together with Graham in a separate mail thread.

On Thu, Jul 4, 2019 at 7:39 AM Tibor Digana  wrote:

> -1: still no answered reasoning about Jetty 9 and Java 8.
>
> On Thu, Jul 4, 2019 at 8:32 AM Michael Osipov  wrote:
>
>> Am 2019-07-01 um 23:10 schrieb Michael Osipov:
>> > Hi,
>> >
>> > We solved 11 issues:
>> >
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317923=12343145
>> >
>> >
>> > There are still a couple of issues left in JIRA:
>> >
>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSITE%20AND%20resolution%20%3D%20Unresolved
>> >
>> >
>> > Staging repo:
>> > https://repository.apache.org/content/repositories/maven-1520/
>> >
>> https://repository.apache.org/content/repositories/maven-1520/org/apache/maven/plugins/maven-site-plugin/3.8.1/maven-site-plugin-3.8.1-source-release.zip
>> >
>> >
>> > Source release checksum(s):
>> > maven-site-plugin-3.8.1-source-release.zip
>> > sha512:
>> >
>> e4e001e848267c50052e2261f98f7b4c0fcc9833d13245c69dc06d26b30f814061048d6bebaef8464120133ffb503c002ddaecdfc9b234801b4ca7729c7a24cd
>>
>> >
>> >
>> > Staging site:
>> > https://maven.apache.org/plugins-archives/maven-site-plugin-LATEST/
>> >
>> > Guide to testing staged releases:
>> > https://maven.apache.org/guides/development/guide-testing-releases.html
>> >
>> > Vote open for 72 hours.
>>
>> +1
>>
>> Guys, I need two more binding votes until tomorrow.
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> For additional commands, e-mail: dev-h...@maven.apache.org
>>
>>

Re: [VOTE] Release Maven Site Plugin version 3.8.1

2019-07-04 Thread Tibor Digana 
-1: still no answered reasoning about Jetty 9 and Java 8.

On Thu, Jul 4, 2019 at 8:32 AM Michael Osipov  wrote:

> Am 2019-07-01 um 23:10 schrieb Michael Osipov:
> > Hi,
> >
> > We solved 11 issues:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317923=12343145
> >
> >
> > There are still a couple of issues left in JIRA:
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSITE%20AND%20resolution%20%3D%20Unresolved
> >
> >
> > Staging repo:
> > https://repository.apache.org/content/repositories/maven-1520/
> >
> https://repository.apache.org/content/repositories/maven-1520/org/apache/maven/plugins/maven-site-plugin/3.8.1/maven-site-plugin-3.8.1-source-release.zip
> >
> >
> > Source release checksum(s):
> > maven-site-plugin-3.8.1-source-release.zip
> > sha512:
> >
> e4e001e848267c50052e2261f98f7b4c0fcc9833d13245c69dc06d26b30f814061048d6bebaef8464120133ffb503c002ddaecdfc9b234801b4ca7729c7a24cd
>
> >
> >
> > Staging site:
> > https://maven.apache.org/plugins-archives/maven-site-plugin-LATEST/
> >
> > Guide to testing staged releases:
> > https://maven.apache.org/guides/development/guide-testing-releases.html
> >
> > Vote open for 72 hours.
>
> +1
>
> Guys, I need two more binding votes until tomorrow.
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Re: [VOTE] Release Maven Site Plugin version 3.8.1

2019-07-04 Thread Michael Osipov 

Am 2019-07-01 um 23:10 schrieb Michael Osipov:

Hi,

We solved 11 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317923=12343145 



There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSITE%20AND%20resolution%20%3D%20Unresolved 



Staging repo:
https://repository.apache.org/content/repositories/maven-1520/
https://repository.apache.org/content/repositories/maven-1520/org/apache/maven/plugins/maven-site-plugin/3.8.1/maven-site-plugin-3.8.1-source-release.zip 



Source release checksum(s):
maven-site-plugin-3.8.1-source-release.zip
sha512: 
e4e001e848267c50052e2261f98f7b4c0fcc9833d13245c69dc06d26b30f814061048d6bebaef8464120133ffb503c002ddaecdfc9b234801b4ca7729c7a24cd 



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

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

Vote open for 72 hours.


+1

Guys, I need two more binding votes until tomorrow.

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

Re: [VOTE] Release Maven Site Plugin version 3.8.1

2019-07-03 Thread Graham Leggett 
On 01 Jul 2019, at 23:10, Michael Osipov  wrote:

> We solved 11 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317923=12343145
> 
> There are still a couple of issues left in JIRA:
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSITE%20AND%20resolution%20%3D%20Unresolved
> 
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1520/
> https://repository.apache.org/content/repositories/maven-1520/org/apache/maven/plugins/maven-site-plugin/3.8.1/maven-site-plugin-3.8.1-source-release.zip
> 
> Source release checksum(s):
> maven-site-plugin-3.8.1-source-release.zip
> sha512: 
> e4e001e848267c50052e2261f98f7b4c0fcc9833d13245c69dc06d26b30f814061048d6bebaef8464120133ffb503c002ddaecdfc9b234801b4ca7729c7a24cd
> 
> Staging site:
> https://maven.apache.org/plugins-archives/maven-site-plugin-LATEST/
> 
> Guide to testing staged releases:
> https://maven.apache.org/guides/development/guide-testing-releases.html
> 
> Vote open for 72 hours.
> 
> [ ] +1
> [ ] +0
> [ ] -1

Like last time, +1 on Java8.

One test failed, however this test also fails in maven-site-plugin v3.7.1, so 
this is not a regression:

[INFO] Building: effective-site/pom.xml
[INFO] run post-build script verify.groovy
[INFO]   effective-site/pom.xml ... FAILED (6.0 
s)
[INFO]   The post-build script did not succeed. assert new File( basedir, 
'effective-site.xml' ).exists()
   | |   |
   | |   false
   | 
/home/gatekeeper/minfrin/src/apache/sandbox/maven/maven-site-plugin-maven-site-plugin-3.7.1/target/it/effective-site
   
/home/gatekeeper/minfrin/src/apache/sandbox/maven/maven-site-plugin-maven-site-plugin-3.7.1/target/it/effective-site/effective-site.xml

Regards,
Graham
—



smime.p7s
Description: S/MIME cryptographic signature

Re: [VOTE] Release Maven Site Plugin version 3.8.1

2019-07-03 Thread Michael Osipov 

Am 2019-07-02 um 00:20 schrieb Tibor Digana:

I could not find any (Jetty to MavenSite related) reasoning about versions
of external frameworks in MSITE-828 and MSITE-829.

Why you have used Jetty 9.4.12 compiled with J8 and not the Jetty 8.2.0
compiled with J7?
What is the benefit to use v9.x and why not to use the v8.2.0?
Would the Maven Site Plugin benefit the same way from Jetty 8.2.0?

The previous version was 6.1.25.

The frameworks might be compiled even with J11 for instance. So the
question is how far we would go with the upgrades?


See here: https://github.com/apache/maven-site-plugin/pull/3


On Mon, Jul 1, 2019 at 11:11 PM Michael Osipov  wrote:


Hi,

We solved 11 issues:

https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317923=12343145

There are still a couple of issues left in JIRA:

https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSITE%20AND%20resolution%20%3D%20Unresolved

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

https://repository.apache.org/content/repositories/maven-1520/org/apache/maven/plugins/maven-site-plugin/3.8.1/maven-site-plugin-3.8.1-source-release.zip

Source release checksum(s):
maven-site-plugin-3.8.1-source-release.zip
sha512:

e4e001e848267c50052e2261f98f7b4c0fcc9833d13245c69dc06d26b30f814061048d6bebaef8464120133ffb503c002ddaecdfc9b234801b4ca7729c7a24cd

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

Guide to testing staged releases:
https://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

Re: [VOTE] Release Maven Site Plugin version 3.8.1

2019-07-01 Thread Tibor Digana 
I could not find any (Jetty to MavenSite related) reasoning about versions
of external frameworks in MSITE-828 and MSITE-829.

Why you have used Jetty 9.4.12 compiled with J8 and not the Jetty 8.2.0
compiled with J7?
What is the benefit to use v9.x and why not to use the v8.2.0?
Would the Maven Site Plugin benefit the same way from Jetty 8.2.0?

The previous version was 6.1.25.

The frameworks might be compiled even with J11 for instance. So the
question is how far we would go with the upgrades?

Cheers
Tibor17

On Mon, Jul 1, 2019 at 11:11 PM Michael Osipov  wrote:

> Hi,
>
> We solved 11 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317923=12343145
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSITE%20AND%20resolution%20%3D%20Unresolved
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1520/
>
> https://repository.apache.org/content/repositories/maven-1520/org/apache/maven/plugins/maven-site-plugin/3.8.1/maven-site-plugin-3.8.1-source-release.zip
>
> Source release checksum(s):
> maven-site-plugin-3.8.1-source-release.zip
> sha512:
>
> e4e001e848267c50052e2261f98f7b4c0fcc9833d13245c69dc06d26b30f814061048d6bebaef8464120133ffb503c002ddaecdfc9b234801b4ca7729c7a24cd
>
> Staging site:
> https://maven.apache.org/plugins-archives/maven-site-plugin-LATEST/
>
> Guide to testing staged releases:
> https://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 Maven Site Plugin version 3.8.1

2019-07-01 Thread Tibor Digana 
no, sorry, very similar names: servlet and server.

On Mon, Jul 1, 2019 at 11:58 PM Tibor Digana  wrote:

> Now the Jetty Server is there twice:
>
> 
> org.eclipse.jetty
> jetty-servlet
> ${jettyVersion}
> 
>
> On Mon, Jul 1, 2019 at 11:11 PM Michael Osipov 
> wrote:
>
>> Hi,
>>
>> We solved 11 issues:
>>
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317923=12343145
>>
>> There are still a couple of issues left in JIRA:
>>
>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSITE%20AND%20resolution%20%3D%20Unresolved
>>
>> Staging repo:
>> https://repository.apache.org/content/repositories/maven-1520/
>>
>> https://repository.apache.org/content/repositories/maven-1520/org/apache/maven/plugins/maven-site-plugin/3.8.1/maven-site-plugin-3.8.1-source-release.zip
>>
>> Source release checksum(s):
>> maven-site-plugin-3.8.1-source-release.zip
>> sha512:
>>
>> e4e001e848267c50052e2261f98f7b4c0fcc9833d13245c69dc06d26b30f814061048d6bebaef8464120133ffb503c002ddaecdfc9b234801b4ca7729c7a24cd
>>
>> Staging site:
>> https://maven.apache.org/plugins-archives/maven-site-plugin-LATEST/
>>
>> Guide to testing staged releases:
>> https://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 Maven Site Plugin version 3.8.1

2019-07-01 Thread Tibor Digana 
Now the Jetty Server is there twice:


org.eclipse.jetty
jetty-servlet
${jettyVersion}


On Mon, Jul 1, 2019 at 11:11 PM Michael Osipov  wrote:

> Hi,
>
> We solved 11 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317923=12343145
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSITE%20AND%20resolution%20%3D%20Unresolved
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1520/
>
> https://repository.apache.org/content/repositories/maven-1520/org/apache/maven/plugins/maven-site-plugin/3.8.1/maven-site-plugin-3.8.1-source-release.zip
>
> Source release checksum(s):
> maven-site-plugin-3.8.1-source-release.zip
> sha512:
>
> e4e001e848267c50052e2261f98f7b4c0fcc9833d13245c69dc06d26b30f814061048d6bebaef8464120133ffb503c002ddaecdfc9b234801b4ca7729c7a24cd
>
> Staging site:
> https://maven.apache.org/plugins-archives/maven-site-plugin-LATEST/
>
> Guide to testing staged releases:
> https://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
>
>

[VOTE] Release Maven Site Plugin version 3.8.1

2019-07-01 Thread Michael Osipov 

Hi,

We solved 11 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317923=12343145

There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSITE%20AND%20resolution%20%3D%20Unresolved

Staging repo:
https://repository.apache.org/content/repositories/maven-1520/
https://repository.apache.org/content/repositories/maven-1520/org/apache/maven/plugins/maven-site-plugin/3.8.1/maven-site-plugin-3.8.1-source-release.zip

Source release checksum(s):
maven-site-plugin-3.8.1-source-release.zip
sha512: 
e4e001e848267c50052e2261f98f7b4c0fcc9833d13245c69dc06d26b30f814061048d6bebaef8464120133ffb503c002ddaecdfc9b234801b4ca7729c7a24cd


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

Guide to testing staged releases:
https://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