Re: [jira] [Commented] (MNG-6691) Maven protocol specification

[Tamás Cservenák]

Just fyi, am aware of 3+2 oss solutions out there (the +2 are the trimmed
ones)

On Sat, Jul 6, 2019, 00:26 dzikoysk (JIRA)  wrote:

>
> [
> https://issues.apache.org/jira/browse/MNG-6691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16879546#comment-16879546
> ]
>
> dzikoysk commented on MNG-6691:
> ---
>
> Yeah, it's what we need to do now and it's why I'm loking for something
> better. At this moment, we have only 3 open source repository managers
> where 2 of them are just trimmed-down versions of pro (commercial) software
> that is huge and heavy - honestly, I don't think that `yet another` phrase
> just fits here. Also, in our case it's not just Maven support, we're also
> targeting our language and related stuff, nvm, but it is not an option. It
> looks like there is no other resources than sources and we have to stay
> with our present methods. Thanks for your answers, just consider simple
> specification for future users :)
>
> > Maven protocol specification
> > 
> >
> > Key: MNG-6691
> > URL: https://issues.apache.org/jira/browse/MNG-6691
> > Project: Maven
> >  Issue Type: Wish
> >  Components: Documentation:  General
> >Reporter: dzikoysk
> >Priority: Trivial
> >  Labels: documentation
> >
> > There is a lot of guides and docs about "How to start" on [
> maven.apache.org|https://maven.apache.org/] with maven as developer who
> wants to use maven in a project, but I'm not able to find something for
> people working with repository managers. Is there any technical
> specification of maven http/protocol specification/rest api and what's
> required from a custom repository manager to serve requests properly or the
> only way is to search in maven/other repositories like nexus, artifcatory
> sources?
>
>
>
> --
> This message was sent by Atlassian JIRA
> (v7.6.3#76005)
>

Re: [VOTE] Release Maven Site Plugin version 3.8.1

[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