Re: configjsr branch not buildable in travis / other Travis builds are ok except CDI test failures in extensions

Hi *, Am 21.01.2018 um 04:55 schrieb William Lieurance: > While I would definitely like to see javaconfig-api jars published correctly, > as long as we're talking about bad workarounds I was able to get Anatole's > branch built and tests passing using jitpack.io as a passthrough to their >

[jira] [Created] (TAMAYA-325) Integrate not yet finalized ConfigJSR-API via jitpack

Philipp Ottlinger created TAMAYA-325: Summary: Integrate not yet finalized ConfigJSR-API via jitpack Key: TAMAYA-325 URL: https://issues.apache.org/jira/browse/TAMAYA-325 Project: Tamaya

Build failed in Jenkins: Tamaya-Site-Master #775

See -- Started by an SCM change [EnvInject] - Loading node environment variables. [EnvInject] - Preparing an environment for the build. [EnvInject] - Keeping Jenkins system variables.

Jenkins build is back to normal : Tamaya-Sandbox-Master #1412

See

Jenkins build is back to normal : Tamaya-Sandbox-Master » Apache Tamaya Sandbox #1412

See

Build failed in Jenkins: Tamaya-Site-Master #773

See -- Started by an SCM change [EnvInject] - Loading node environment variables. [EnvInject] - Preparing an environment for the build. [EnvInject] - Keeping Jenkins system variables.

Jenkins build is back to normal : Tamaya-Master-branch #1357

See

[jira] [Commented] (TAMAYA-296) Update maven site plugins

[ https://issues.apache.org/jira/browse/TAMAYA-296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16338288#comment-16338288 ] ASF subversion and git services commented on TAMAYA-296: Commit

Build failed in Jenkins: Tamaya-Sandbox-Master #1414

See -- Started by user pottlinger Started by an SCM change [EnvInject] - Loading node environment variables. [EnvInject] - Preparing an environment for the build. [EnvInject] -

Jenkins build is back to normal : Tamaya-Sandbox-Master #1415

See

Build failed in Jenkins: Tamaya-Master-branch #1354

See -- Started by an SCM change [EnvInject] - Loading node environment variables. [EnvInject] - Preparing an environment for the build. [EnvInject] - Keeping Jenkins system

Build failed in Jenkins: Tamaya-Site-Master #772

See -- Started by an SCM change [EnvInject] - Loading node environment variables. [EnvInject] - Preparing an environment for the build. [EnvInject] - Keeping Jenkins system variables.

Build failed in Jenkins: Tamaya-Master-branch #1356

See -- Started by user pottlinger [EnvInject] - Loading node environment variables. [EnvInject] - Preparing an environment for the build. [EnvInject] - Keeping Jenkins system

[jira] [Closed] (TAMAYA-296) Update maven site plugins

[ https://issues.apache.org/jira/browse/TAMAYA-296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philipp Ottlinger closed TAMAYA-296. Resolution: Fixed Fix Version/s: 0.4-incubating Thanks for the patches [~wlieurance]

Jenkins build is back to normal : Tamaya-Extensions-Master-with-Coverage #366

See

Jenkins build is back to normal : Tamaya-Site-Master #777

See

Build failed in Jenkins: Tamaya-Sandbox-Master #1413

See -- Started by an SCM change [EnvInject] - Loading node environment variables. [EnvInject] - Preparing an environment for the build. [EnvInject] - Keeping Jenkins system

Jenkins build is back to normal : Tamaya-Branch-Master-with-Coverage #181

See

Build failed in Jenkins: Tamaya-Extensions-Master-with-Coverage #365

See -- Started by an SCM change [EnvInject] - Loading node environment variables. [EnvInject] - Preparing an environment for the build. [EnvInject] - Keeping

[jira] [Commented] (TAMAYA-296) Update maven site plugins

[ https://issues.apache.org/jira/browse/TAMAYA-296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16338309#comment-16338309 ] ASF subversion and git services commented on TAMAYA-296: Commit

Build failed in Jenkins: Tamaya-Site-Master #776

See -- Started by an SCM change Started by an SCM change [EnvInject] - Loading node environment variables. [EnvInject] - Preparing an environment for the build. [EnvInject] - Keeping

[jira] [Assigned] (TAMAYA-296) Update maven site plugins

[ https://issues.apache.org/jira/browse/TAMAYA-296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philipp Ottlinger reassigned TAMAYA-296: Assignee: Philipp Ottlinger > Update maven site plugins >

Build failed in Jenkins: Tamaya-Master-branch #1355

See -- Started by an SCM change [EnvInject] - Loading node environment variables. [EnvInject] - Preparing an environment for the build. [EnvInject] - Keeping Jenkins system

Build failed in Jenkins: Tamaya-Extensions-Master #1335

See -- Started by upstream project "Tamaya-Master-branch" build number 1357 originally caused by: Started by an SCM change Started by upstream project "Tamaya-Master-branch"

Build failed in Jenkins: Tamaya-Sandbox-Master #1416

See -- Started by upstream project "Tamaya-Master-branch" build number 1357 originally caused by: Started by an SCM change Started by upstream project "Tamaya-Extensions-Master"

Build failed in Jenkins: Tamaya-Extensions-Master-with-Coverage #367

See -- Started by upstream project "Tamaya-Master-branch" build number 1357 originally caused by: Started by an SCM change Started by upstream project

Re: configjsr branch not buildable in travis / other Travis builds are ok except CDI test failures in extensions

Sure thing. The request is at https://github.com/apache/incubator-tamaya/pull/9 Let me know if you'd like a patch file on the Jira ticket instead. --William From: P. Ottlinger Sent: Wednesday, January 24, 2018 3:45:51 PM To:

[jira] [Commented] (TAMAYA-325) Integrate not yet finalized ConfigJSR-API via jitpack

[ https://issues.apache.org/jira/browse/TAMAYA-325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16338863#comment-16338863 ] ASF GitHub Bot commented on TAMAYA-325: --- GitHub user peculater opened a pull request:

[GitHub] incubator-tamaya pull request #9: TAMAYA-325: Fake JSR API JAR with jitpack

GitHub user peculater opened a pull request: https://github.com/apache/incubator-tamaya/pull/9 TAMAYA-325: Fake JSR API JAR with jitpack Also get tests passing once the jar is in. You can merge this pull request into a Git repository by running: $ git pull

[jira] [Commented] (TAMAYA-325) Integrate not yet finalized ConfigJSR-API via jitpack

[ https://issues.apache.org/jira/browse/TAMAYA-325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16338873#comment-16338873 ] William Lieurance commented on TAMAYA-325: -- Created pull request

Jenkins build is back to normal : Tamaya-Sandbox-Master #1417

See

Jenkins build is back to normal : Tamaya-Extensions-Master #1337

See

Jenkins build is back to normal : Tamaya-Extensions-Master-with-Coverage #368

See

Build failed in Jenkins: Tamaya-Extensions-Master #1336

See -- [...truncated 6.19 MB...] at org.eclipse.aether.internal.impl.DefaultDeployer.deploy (DefaultDeployer.java:320) at

Build failed in Jenkins: Tamaya-Sandbox-Master » Apache Tamaya Sandbox #1411

See -- Established TCP socket on 44720 maven33-agent.jar already up to date maven33-interceptor.jar already up to date

Build failed in Jenkins: Tamaya-Sandbox-Master #1411

See -- [...truncated 7.76 KB...] [INFO] Will parse SCM ignores for exclusions... [INFO] Parsing exclusions from