gmane.comp.java.jmock.devel

Re: Unexpected behaviour with package private classes - IllegalAccessError

Duncan Jones — 2013-02-21T15:38:22

Another interesting observation - if I change all my classes to be in
the default package, the problem goes away.

On 21 February 2013 13:06, Duncan Jones <duncan-VgTxFcESRta8IPqWsmCfhg< at >public.gmane.org> wrote:

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

Unexpected behaviour with package private classes - IllegalAccessError

Duncan Jones — 2013-02-21T13:06:00

Hi,

I've encountered some strange behaviour when using package private
classes within expectations. The proxy class gets an
IllegalAccessError when referring to a package private class instance
in a return value.

I've attached a minimal working Maven project ("example-project.zip"),
which demonstrates the behaviour. I'm unclear whether this is expected
or not.

Some notes:

 - The issue does not occur if the method in question returns null
(see testSuccess() in my example test file).

 - If I convert ExampleInterface to be package private, the error does
not occur.

Kind regards,

Duncan

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

Re: jmock maven distribution?

Andreas Pieber — 2013-01-08T17:15:43

Well, not much further since no final decision had been made IIRC. IMHO
we've the following options:

a) switch from ant to ivy; the difference should be minimal but with ivy
we've a useful resource management at hand and can push to maven central
b) add maven poms in parallel to the ant scripts; well, not quite sure
about the usefulness of this (except that we can push to m2 central)
c) Simply upload the artifact to m2 central manually after the release
d) Switch to maven
e) switch to Gradle (from there we can also push to m2 central)
f) switch to Buildr (from there we can also push to m2 central).
g) switch to any other build system which can push to m2 central of which I
don't know by now

Since I'm pretty new to the community I would not dare to influence any
decision but I could help with whatever option had been chosen to see the
artifacts reaching m2 central (as this would be kind of valuable for me :-))

Kind regards,
Andreas


On Mon, Jan 7, 2013 at 3:33 PM, Steve Freeman <steve-/6t1Ty3A97Vaa/9Udqfw

jmock maven distribution?

Steve Freeman — 2013-01-07T14:33:18

Where are we with this?

S.


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

Re: [jmock-user] doesn't compile with Java 7. Breaking change?

Steve Freeman — 2012-12-31T13:18:12

Thanks for offering, but I don't think that'll do much good. The same rules apply for Java 8 and beyond. We've been pushing the boundaries of what can be done with generics and it looks like we found an edge case. In the end, the underlying problem is the brokenness of the language, in this case: type erasure and primitive types.

S.

On 30 Dec 2012, at 22:42, James Abley wrote:


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

doesn't compile with Java 7. Breaking change?

Steve Freeman — 2012-12-30T22:23:10

It turns out that JMock doesn't compile with Java7. They've changed the type system so that it doesn't know what to do with all the overloads of the with() method in ArgumentConstraintPhrases. If we delete the overloads for the primitive types to make the code compile, then it fails at runtime because we cannot return null as a primitive type and we don't have a runtime way to find out what type we're supposed to be returning. 

The best we can think of is to do something based on Expectations.WithClause where we specify the return type in the method name for primitives, for example:

  oneOf(foo).blah(with.intIs(lessThan(2)));

Unfortunately, this is a breaking change.

Unless someone has a better idea, we'll do this in the next release (2.7). This new API should still compile and work with Java 6, even if it's more clunky.

Thoughts?

S.



---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[jira] (JMOCK-256) Mocks being finalized report "the Mockery is not thread-safe: use a Synchroniser to ensure thread safety"

Steve Freeman (JIRA — 2012-12-21T10:56:13

[jira] (JMOCK-249) ClassImposteriser generates spurious "unexpected invocation" failures.

Steve Freeman (JIRA — 2012-12-21T10:52:13

[jira] (JMOCK-228) Report further detail in unexpected invocation

Steve Freeman (JIRA — 2012-12-21T10:48:13

[jira] (JMOCK-228) Report further detail in unexpected invocation

Steve Freeman (JIRA — 2012-12-21T10:48:13

[jira] (JMOCK-227) Allow ReturnDefaultValueAction to be replaced/extended

Steve Freeman (JIRA — 2012-12-21T10:46:13

[jira] (JMOCK-225) Imposteriser produces ClassCastException when JUnit tests are run with Ant.

Steve Freeman (JIRA — 2012-12-21T10:43:13

[jira] (JMOCK-236) docs say Expectations has allOf() and anyOf() methods - but it doesn't

Steve Freeman (JIRA — 2012-12-21T10:38:13

[jira] (JMOCK-206) Lost test Exception in org.jmock.core.VerifyingTestCase.runBare()

Steve Freeman (JIRA — 2012-12-21T10:31:13

[jira] (JMOCK-206) Lost test Exception in org.jmock.core.VerifyingTestCase.runBare()

Steve Freeman (JIRA — 2012-12-21T10:29:13

[jira] (JMOCK-259) Synchronization Issue with assertIsSatisfied() using ThreadingPolicy = Synchronizer

Steve Freeman (JIRA — 2012-12-21T10:27:13

[jira] (JMOCK-266) jmock-junit4 2.6.0-RC2 POM refers to wrong junit:junit-dep version

Steve Freeman (JIRA — 2012-12-21T10:24:13

[jira] (JMOCK-246) Expectations "a" and "an" are deprecated, but there is no adequate substitute

Steve Freeman (JIRA — 2012-12-20T10:57:13

[jira] (JMOCK-267) jMock fails to build from source with openjdk-7

Steve Freeman (JIRA — 2012-12-20T10:51:13

[jira] (JMOCK-261) Behaviour of Expectations.any Matcher has drastically changed

Steve Freeman (JIRA — 2012-12-20T10:44:13

[jira] (JMOCK-261) Behaviour of Expectations.any Matcher has drastically changed

Steve Freeman (JIRA — 2012-12-20T10:42:13