Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [glassfish-dev] test failures
On 12/3/18 12:13 PM, arjan tijms wrote:
Hi Romain,

It could well be that I did something wrong, but before the commit the branch didn't even build. It referred to Mojarra 2.3.3.102, which doesn't seem to be published anywhere (at least not in a location known by GF).
See https://github.com/eclipse-ee4j/glassfish/commits/EE4J_8
The previous commit had passed all tests.

So I'm a little puzzled how the failures can be new ones.
It's mostly likely related to the Maven coordinate changes or OSGi metadata changes.
Do you know how GF was able to build before that PR? Where did it get Mojarra 2.3.3.102 from?
The pipelines uses a cache for all non GF artifacts.
Mojarra 2.3.3.102 was released to Maven Central on June 2018.

Kind regards,
Arjan




On Mon, Dec 3, 2018 at 9:03 PM Romain Grecourt <romain.grecourt@xxxxxxxxxx> wrote:
Hi,

PR #22644 has been merged with test failures. See [1] and [2]

This is impact every other pull requests for the EE4J_8 branch.
I'm going to revert the corresponding commit(s).

Thanks,
Romain


[1] https://github.com/eclipse-ee4j/glassfish/pull/22644
[2]
https://jenkins.eclipse.org/glassfish/blue/organizations/jenkins/glassfish/detail/PR-22644/2/

Back to the top