Menu
▾
▴
Re: [Jamon-users] Issues compiling Jamon from sources
|
From: electrotype <ele...@gm...> - 2013-09-09 13:29:25
|
This fixes the first failures. Now there is this one :
-------------------------------------------------------------------------------
Test set: org.jamon.test.MissingTemplateDirectoryTest
-------------------------------------------------------------------------------
Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.11 sec <<< FAILURE!
missingDirectory(org.jamon.test.MissingTemplateDirectoryTest) Time elapsed: 0.047 sec <<< FAILURE!
org.junit.ComparisonFailure: expected:<templateSourceDir [/no/such/]directory does not e...> but
was:<templateSourceDir [\no\such\]directory does not e...>
at org.junit.Assert.assertEquals(Assert.java:123)
at org.junit.Assert.assertEquals(Assert.java:145)
at
org.jamon.test.MissingTemplateDirectoryTest.missingDirectory(MissingTemplateDirectoryTest.java:23)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
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:53)
at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:119)
at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:101)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at
org.apache.maven.surefire.booter.ProviderFactory$ClassLoaderProxy.invoke(ProviderFactory.java:103)
at $Proxy0.invoke(Unknown Source)
at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:150)
at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:91)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:69)
Let me know when you want me to try again with another svn update, it takes 2 minutes.
electrotype
On 9/9/2013 9:21 AM, Ian Robertson wrote:
> Ah, that makes sense. In fact, the testIndentation method of CodeWriterTest uses
> System.getProperty("line.separator") instead of "\n", and appears to be working for you. I've just
> checked in a change into trunk that should fix this issue; would you mind testing it for me?
>
>
> On Mon, Sep 9, 2013 at 4:27 AM, electrotype <ele...@gm... <mailto:ele...@gm...>>
> wrote:
>
> I think I may get those test failures because I use Windows. Maybe because of "\" characters
> in some paths?
>
> That said, I was thinking about forking Jamon to implement the modifications I needed for my
> framework, but Jamon is actually a bigger beast than what I though. The fact that there is
> several ways of generating the .java files, and that there even exist third-party plugins to
> do so (like http://code.google.com/p/jamon-intellij-plugin/ ) makes you think two times before
> changing any code. I'm instead gonna stick to the Jamon code you provide and try to workaround
> the issues I face.
>
> Here's the Surefire output :
>
> -------------------------------------------------------------------------------
> Test set: org.jamon.codegen.CodeWriterTest
> -------------------------------------------------------------------------------
> Tests run: 10, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.016 sec <<< FAILURE!
> testNestedList(org.jamon.codegen.CodeWriterTest) Time elapsed: 0 sec <<< FAILURE!
> junit.framework.ComparisonFailure: null expected:<(outer1={}, outer2={[
> mid1=[inner1, inner2],]
> mid2}, outer3)> but was:<(outer1={}, outer2={[
> mid1=[inner1, inner2],
> ]
> mid2}, outer3)>
> at junit.framework.Assert.assertEquals(Assert.java:81)
> at junit.framework.Assert.assertEquals(Assert.java:87)
> at org.jamon.codegen.CodeWriterTest.checkOutput(CodeWriterTest.java:146)
> at org.jamon.codegen.CodeWriterTest.testNestedList(CodeWriterTest.java:141)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at junit.framework.TestCase.runTest(TestCase.java:168)
> at junit.framework.TestCase.runBare(TestCase.java:134)
> at junit.framework.TestResult$1.protect(TestResult.java:110)
> at junit.framework.TestResult.runProtected(TestResult.java:128)
> at junit.framework.TestResult.run(TestResult.java:113)
> at junit.framework.TestCase.run(TestCase.java:124)
> at junit.framework.TestSuite.runTest(TestSuite.java:243)
> at junit.framework.TestSuite.run(TestSuite.java:238)
> at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83)
> at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:119)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:101)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at
> org.apache.maven.surefire.booter.ProviderFactory$ClassLoaderProxy.invoke(ProviderFactory.java:103)
> at $Proxy0.invoke(Unknown Source)
> at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:150)
> at
> org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:91)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:69)
>
>
> electrotype
>
>
>
>
>
> On 9/9/2013 12:57 AM, Ian Robertson wrote:
>> Those test failures are a bit baffling to me. Can you post the contents of
>> target/surefire-reports/org.jamon.codegen.CodeWriterTest.txt?
>>
>> As for the eclipse errors, if memory serves, you'll need to manually tell eclipse that the
>> nodesrc directory is a source directory.
>>
>> It probably wouldn't be a bad idea if the nodegen-plugin didn't declare the generated sources
>> as a source directory, but instead left that to jamon-processor to do via
>> maven-buildhelper-plugin, since I believe the latter is something eclipse knows about
>>
>>
>> On Fri, Sep 6, 2013 at 12:28 PM, electrotype <ele...@gm...
>> <mailto:ele...@gm...>> wrote:
>>
>> I'm building : /svn://svn.code.sf.net/p/jamon/code/trunk/jamon/
>>
>> And I've finally been able to build it by skipping the tests ("mvn clean install
>> -DskipTests"). With the tests enabled it fails :
>>
>> =========================================
>> Failed tests:
>> testNestedList(org.jamon.codegen.CodeWriterTest): null expected:<(outer1={}, outer2={[
>> testEscaping(org.jamon.codegen.LiteralStatementTest): null expected:<// 1, 1[
>>
>> Tests run: 312, Failures: 2, Errors: 0, Skipped: 0
>>
>> [INFO] ------------------------------------------------------------------------
>> [INFO] Reactor Summary:
>> [INFO]
>> [INFO] Jamon Parent ...................................... SUCCESS [0.727s]
>> [INFO] jamon-checkstyle .................................. SUCCESS [2.050s]
>> [INFO] Jamon Java Parent ................................. SUCCESS [0.268s]
>> [INFO] jamon-runtime ..................................... SUCCESS [3.440s]
>> [INFO] jamon-api ......................................... SUCCESS [1.138s]
>> [INFO] jamon-nodegen-plugin .............................. SUCCESS [2.908s]
>> [INFO] jamon-processor ................................... FAILURE [12.512s]
>>
>> =========================================
>>
>> But then, I try to import the projects in Eclipse (Kepler). Using m2e, I do "Import /
>> Existing Maven projects" and I select "jamon/pom.xml".
>>
>> This results in a lot of warnings/errors :
>>
>> http://i.imgur.com/672PIxz.png
>>
>> A lot of them being classes not found in the /org.jamon.node/ package.
>>
>> Any ideas?
>>
>> electrotype
>>
>>
>>
>>
>>
>> On 9/6/2013 2:06 PM, Ian Robertson wrote:
>>> From which directory are you trying to build? The parent directory of the modules you
>>> listed is where the build needs to be launched from. In particular, it builds the
>>> jamon-nodegen-plugin, which is used by jamon-processor to generate the node java files.
>>>
>>>
>>> On Fri, Sep 6, 2013 at 12:01 PM, electrotype <ele...@gm...
>>> <mailto:ele...@gm...>> wrote:
>>>
>>> Hi,
>>>
>>> I'm trying to compile Jamon from sources and I'm having some issues.
>>>
>>> From /svn://svn.code.sf.net/p/jamon/code/ , is there a trunk/tag/branch that can be
>>> checkouted and that would directly compile using "mvn clean install"? I've tried
>>> with the trunk and from some "releases" entries, but without success.
>>>
>>> One of the obvious problem I see is (from the trunk) in
>>> /jamon/jamon-processor/src/main/java/org/jamon/node/ : this folder only contains
>>> "AbstractNode.java" and "LocationImpl.java". It seems a lot of files are missing.
>>> When I look into the /jamon-processor-2.4.1.jar/ that is in my /.m2/ folder, there
>>> are 78 files in that folder!
>>>
>>> I'd like to, at least, be able to compile :
>>>
>>> - jamon-maven-plugin
>>> - jamon-processor
>>> - jamon-runtime
>>>
>>> Any help?
>>>
>>> Thanks in advance.
>>>
>>> electrotype
>>>
>>> ------------------------------------------------------------------------------
>>> Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
>>> Discover the easy way to master current and previous Microsoft technologies
>>> and advance your career. Get an incredible 1,500+ hours of step-by-step
>>> tutorial videos with LearnDevNow. Subscribe today and save!
>>> http://pubads.g.doubleclick.net/gampad/clk?id=58041391&iu=/4140/ostg.clktrk
>>> _______________________________________________
>>> Jamon-users mailing list
>>> Jam...@li... <mailto:Jam...@li...>
>>> https://lists.sourceforge.net/lists/listinfo/jamon-users
>>>
>>>
>>
>>
>
>
|
