ok, I've now fixed this test in the codebase (under ISIS-437)
On 15 October 2013 16:57, james agada wrote:
> Thanks.
>
>
> On Mon, Oct 14, 2013 at 8:52 AM, Jeroen van der Wal >wrote:
>
> > There was a typo in the command. It should be: mvn clean install
> > -DskipTests (note the capital T)
>
Thanks.
On Mon, Oct 14, 2013 at 8:52 AM, Jeroen van der Wal wrote:
> There was a typo in the command. It should be: mvn clean install
> -DskipTests (note the capital T)
>
>
> On Mon, Oct 14, 2013 at 12:22 AM, james agada
> wrote:
>
> > Thanks for the hint but still no luck.
> > ---
There was a typo in the command. It should be: mvn clean install
-DskipTests (note the capital T)
On Mon, Oct 14, 2013 at 12:22 AM, james agada wrote:
> Thanks for the hint but still no luck.
> --
> T E S T S
> --
Thanks for the hint but still no luck.
--
T E S T S
---
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See
Hi James,
If you don't want to change the Isis code to have Maven ignore the failing
test but still want to build Isis from source you could skip all tests [1]
until this issue is resolved.
[1] mvn clean install -Dskiptests
Jeroen
On Sun, Oct 13, 2013 at 8:48 PM, Dan Haywood
wrote:
> Alongside
Alongside the @Test of the failing tests. Make sure it is the
org.junit.Ignore, not the Isis one in the applib.
I take it you do my site tests., then :-)?
Sorry to be brief, sent from my phone
On 13 Oct 2013 19:07, "james agada" wrote:
> Where exactly am i to place the @Ignore?
>
>
> On Fri, Oc
Where exactly am i to place the @Ignore?
On Fri, Oct 11, 2013 at 4:07 PM, Dan Haywood
wrote:
> Nice! I guess running a different JVM is altering the order of the methods
> being found.
>
> Could you raise a ticket (attach the above stacktrace) and I'll do a quick
> fix.
>
> In the meantime, sug
Nice! I guess running a different JVM is altering the order of the methods
being found.
Could you raise a ticket (attach the above stacktrace) and I'll do a quick
fix.
In the meantime, suggest you add an @Ignore to your local copy of the
failing test(s), so you aren't blocked.
Thx
Dan
On 11
---
Test set: org.apache.isis.core.metamodel.specloader.ServiceInitializerTest
---
Tests run: 7, Failures: 2, Errors: 0, Skipped: 0, Time elapsed:
What are the test errors? locate the files in isis-core-metamodel/
target/surefire-reports.
And/or run the tests for that module in Eclipse JUnit... it's easier to see
any test failures that way.
Our CI build is green, so it's probably some sort of local glitch. Or, it
might be a new i18n issue
I cloned the repository today and tried to rebuild from source. I am
getting the error
>
> [ERROR] Failed to execute goal
>> org.apache.maven.plugins:maven-surefire-plugin:2.12:test (default-test) on
>> project isis-core-metamodel: There are test failures.
>
> [ERROR]
>
> [ERROR] Please refer to
>>
11 matches
Mail list logo