[ 
https://issues.apache.org/jira/browse/SCM-931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17963714#comment-17963714
 ] 

ASF GitHub Bot commented on SCM-931:
------------------------------------

jira-importer opened a new issue, #1157:
URL: https://github.com/apache/maven-scm/issues/1157

   **[Jeremy 
Landis](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=hazendaz)** 
opened 
**[SCM-931](https://issues.apache.org/jira/browse/SCM-931?redirect=false)** and 
commented
   
   While internally jenkins is used to perform testing, outside developers will 
not generally know that. The project currently contains travis-ci and flipping 
it on shows that it fails for numerous reasons.
   
       - Project moved to jdk7 some time back so openjdk6 is going to fail 
regardless
   
       - The default travis-ci ubuntu platform is now on xenial. Thus 'oracle' 
will fail due to licensing restrictions now so only openjdk is viable.
   
       - Xenial builds use a script to get jdks and jdk 7 is no longer valid so 
both 'oracle' and 'open' variations will fail.
   
       - Going back to 'trusty' will get 'oracle' for jdk 8 working but won't 
help with jdk7 at all.
   
       - Going back to 'precise' will acheive getting 'openjdk7', 'oraclejdk7', 
and 'oraclejdk8' working.
   
   As that is the furthest back travis-ci can go, its likely this will pop up 
with failures in the future once that is completely discontinued. At that time, 
'oracle' should be dropped and only openjdk8 and above should be used. That 
will put more reliance on animal sniffer being accurate which feels mostly the 
case here.
   
   
   ---
   
   **Affects:** 1.11.2
   
   **Remote Links:**
   - [GitHub Pull Request #95
   ](https://github.com/apache/maven-scm/pull/95)
   




> [travis-ci] Re-establish working travis-ci for pull requests
> ------------------------------------------------------------
>
>                 Key: SCM-931
>                 URL: https://issues.apache.org/jira/browse/SCM-931
>             Project: Maven SCM (Moved to GitHub Issues)
>          Issue Type: Improvement
>          Components: Technical tasks
>    Affects Versions: 1.11.2
>            Reporter: Jeremy Landis
>            Priority: Trivial
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> {color:#24292e}While internally jenkins is used to perform testing, outside 
> developers will not generally know that. The project currently contains 
> travis-ci and flipping it on shows that it fails for numerous reasons.{color}
> {color:#24292e}    - Project moved to jdk7 some time back so openjdk6 is 
> going to fail regardless{color}
> {color:#24292e}    - The default travis-ci ubuntu platform is now on xenial. 
> Thus 'oracle' will fail due to licensing restrictions now so only openjdk is 
> viable.{color}
> {color:#24292e}    - Xenial builds use a script to get jdks and jdk 7 is no 
> longer valid so both 'oracle' and 'open' variations will fail. {color}
> {color:#24292e}    - Going back to 'trusty' will get 'oracle' for jdk 8 
> working but won't help with jdk7 at all.
> {color}
> {color:#24292e}    - Going back to 'precise' will acheive getting 'openjdk7', 
> 'oraclejdk7', and 'oraclejdk8' working.{color}
> {color:#24292e} As that is the furthest back travis-ci can go, its likely 
> this will pop up with failures in the future once that is completely 
> discontinued. At that time, 'oracle' should be dropped and only openjdk8 and 
> above should be used. That will put more reliance on animal sniffer being 
> accurate which feels mostly the case here.{color}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to