Nightly Builds

2011-04-18 Thread Matthias Wessendorf
Hi,

I was wondering if there are nightly builds available, for the
1.3.1-incubating-SNAPSHOT version.

I couldn't see them in here:

https://repository.apache.org/content/repositories/snapshots/

Thx,
Matthias

-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf


Test Failures

2011-04-18 Thread Matthias Wessendorf
Hi,

in my previous email, I reported to JUnit test failures.

One I corrected already ([1]) - The patch contains a bit of documentation.
(as stated in the bug - I am surprised that on Linux the return-code
is 1 as well for 'command not found')

The second failure:

testTooLongCommandName_withSpace(npanday.executable.CommandExecutorTest)

generates something like:
/bin/bash -c echo x.

Not sure I get why you are expecting a test failure here.

Thanks!
Matthias

[1] https://issues.apache.org/jira/browse/NPANDAY-407

-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf


Re: Test Failures

2011-04-18 Thread Lars Corneliussen
That is a regression. I tried to catch Command line to long for cmd.exe. This 
test should only run on windows. 

Brett, do we support categories by os?

--
Message sent from mobile device

Am 18.04.2011 um 15:47 schrieb Matthias Wessendorf mat...@apache.org:

 Hi,
 
 in my previous email, I reported to JUnit test failures.
 
 One I corrected already ([1]) - The patch contains a bit of documentation.
 (as stated in the bug - I am surprised that on Linux the return-code
 is 1 as well for 'command not found')
 
 The second failure:
 
 testTooLongCommandName_withSpace(npanday.executable.CommandExecutorTest)
 
 generates something like:
 /bin/bash -c echo x.
 
 Not sure I get why you are expecting a test failure here.
 
 Thanks!
 Matthias
 
 [1] https://issues.apache.org/jira/browse/NPANDAY-407
 
 -- 
 Matthias Wessendorf
 
 blog: http://matthiaswessendorf.wordpress.com/
 sessions: http://www.slideshare.net/mwessendorf
 twitter: http://twitter.com/mwessendorf


Re: Building issues on Mac OS (10.6) with Mono 2.10.1

2011-04-18 Thread Matthias Wessendorf
Hi Lars,

I uploaded a new patch to 407 - which (temporary) allows these two
windows specific test to be executed on windows only

-Matthias


PS: this still does not make the build complete, on Mac/Mono - I guess
there is something wrong with the npanday-settings, that I posted
before.

Is there some example (for Mono) available - or is there a generator
for that file?



[INFO] NPANDAY-068-003: Compiling Artifact: Vendor = MONO, Language =
MONO, Assembly Name =
/Users/matzew/Work/plugins/npanday/dotnet/assemblies/NPanday.Model.Pom/target/NPanday.Model.Pom.dll
[INFO] NPANDAY-068-005: Found executable path for gmcs:
/Library/Frameworks/Mono.framework/Versions/Current/bin
[INFO] error CS1577: Referenced assembly `NUnit.Framework,
Version=2.2.8.0, Culture=neutral, PublicKeyToken=null' does not have a
strong name
Compilation failed: 1 error(s), 0 warnings
[INFO] 
[ERROR] BUILD ERROR
[INFO] 
[INFO] NPANDAY-900-006: Unable to Compile: Language = C_SHARP, Vendor
= null, ArtifactType = library, Source Directory =
/Users/matzew/Work/plugins/npanday/dotnet/assemblies/NPanday.Model.Pom/src/main/csharp

Embedded error: NPANDAY-040-001: Could not execute: Command =  gmcs
@/Users/matzew/Work/plugins/npanday/dotnet/assemblies/NPanday.Model.Pom/target/1816429/responsefile.rsp,
Result = 1




On Mon, Apr 18, 2011 at 3:57 PM, Lars Corneliussen m...@lcorneliussen.de 
wrote:
 hi,

 we have had some trouble building npanday on mac, so we gave up for this 
 release. see https://issues.apache.org/jira/browse/NPANDAY-370

 if you'd submit a patch we'll be happy to apply it

 --
 Message sent from mobile device

 Am 18.04.2011 um 15:03 schrieb Matthias Wessendorf mat...@apache.org:

 Hi,

 I checked out trunk (since I couldn't find nightly builds) and I am
 noticing a few issues on my Mono/MacOS environment.

 1) Surefire test failing:
 Failed tests:
  testTooLongCommandName(npanday.executable.CommandExecutorTest)
  testTooLongCommandName_withSpace(npanday.executable.CommandExecutorTest)

 Tests run: 5, Failures: 2, Errors: 0, Skipped: 0

 OUTPUT

 testTooLongCommandName(npanday.executable.CommandExecutorTest)  Time
 elapsed: 0.059 sec   FAILURE!
 java.lang.AssertionError: expected:1 but was:127
    at org.junit.Assert.fail(Assert.java:91)
    at org.junit.Assert.failNotEquals(Assert.java:645)
    at org.junit.Assert.assertEquals(Assert.java:126)
    at org.junit.Assert.assertEquals(Assert.java:470)
    at org.junit.Assert.assertEquals(Assert.java:454)
    at 
 npanday.executable.CommandExecutorTest.testTooLongCommandName(CommandExecutorTest.java:117)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at 
 org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
    at 
 org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
    at 
 org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
    at 
 org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
    at 
 org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:76)
    at 
 org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
    at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
    at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
    at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
    at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
    at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
    at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
    at 
 org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62)
    at 
 org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:140)
    at 
 org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:127)
    at org.apache.maven.surefire.Surefire.run(Surefire.java:177)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at 
 org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:345)
    at 
 org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1009)

 testTooLongCommandName_withSpace(npanday.executable.CommandExecutorTest)
 Time elapsed: 0.022 sec   FAILURE!
 

NUnit version update?

2011-04-18 Thread Matthias Wessendorf
Hi,

currently NPanday uses 2.2.8.0 of NUnit;

However I got an issue with that version:

error CS1577: Referenced assembly `NUnit.Framework, Version=2.2.8.0,
Culture=neutral, PublicKeyToken=null' does not have a strong name


However, installing/using 2.5.10.0 made it working.

If the community is willing to update to 2.5.10.0, I am happy to
provide a patch!

-Matthias


-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf


Re: NUnit version update?

2011-04-18 Thread Matthias Wessendorf
btw.

this repos seems to be down, currently:

http://repo.npanday.org/archiva/repository/3rdparty/

-M

On Mon, Apr 18, 2011 at 6:48 PM, Matthias Wessendorf mat...@apache.org wrote:
 Hi,

 currently NPanday uses 2.2.8.0 of NUnit;

 However I got an issue with that version:

 error CS1577: Referenced assembly `NUnit.Framework, Version=2.2.8.0,
 Culture=neutral, PublicKeyToken=null' does not have a strong name


 However, installing/using 2.5.10.0 made it working.

 If the community is willing to update to 2.5.10.0, I am happy to
 provide a patch!

 -Matthias


 --
 Matthias Wessendorf

 blog: http://matthiaswessendorf.wordpress.com/
 sessions: http://www.slideshare.net/mwessendorf
 twitter: http://twitter.com/mwessendorf




-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf