Getting error while building the code base

[sivashankar ravishankar]

Hi All,

 I am caught with the following error, while building the project using the command "./gradlew clean build install".

 FAILURE: Build failed with an exception.

* What went wrong:

Execution failed for task ':concourse-driver-java:javadoc'.

> Javadoc generation failed.

* Try:

Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

BUILD FAILED

Total time: 2 mins 23.604 secs

--- see the attached file for the complete error.

I am using windows 32 bit OS and executing the command under cygwin. Please let me know if anyone have faced this error during the build.

Thanks in advance.

Regards,

Sivashankar.R

[Prakash Dubey]

Hi Sivashankar,

As far my knowledge concourse is yet to be supported for windows (may be near future we can run/develop concourse on windows)

You may try to build concourse on linux/mac. Concourse is fully supported on both platform (*nix/mac)

Thanks 

--
You received this message because you are subscribed to the Google Groups "Concourse Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to concourse-dev...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Jeff Nelson]

Sivashankar,

What version of Java are you using? The failure you're seeing seems to be stemming from Javadoc generation.

Thanks,

Jeff

--

Jeff Nelson

Founder & CEO | Cinchapi, Inc.

je...@cinchapi.com | 267-495-7751 

Follow us on Twitter | Facebook | Github | AngelList

Start using Cinchapi for real time insight into operational data.

[sivashankar ravishankar]

Hi Jeff,

 Yeah, i changed from jdk 1.8 to 1.7 and tried to build. This javadoc generation error is gone. Now i am stuck up with error in Integration tests. Tests were failing because FileChannel is not getting closed properly in windows. I am looking into it. I will get back to you in case the issue could not be resolved.

Thanks

Sivashankar.R

[Jeff Nelson]

Are you getting an error that says "the process cannot access the file because it is being used by another process"?

If so, I know what the issue is and I might have a fix for it on the way. 

[sivashankar ravishankar]

Hi Jeff,

Yes i am getting this error. Please let me know if you have the fix.

Thanks in advance,

Regards,

Sivashankar.R

[Jeff Nelson]

TLDR: You can run ./gradlew clean installer to build without running the unit tests and that should be a good stop gap

Concourse memory maps files for greater efficiency and it seems that Windows handles that very differently that linux/OS X. The error you're seeing occurs when the unit test tries to delete the temporary directory it was using to store data. But, since the files in that directory are memory mapped and the process that started the memory mapping (the JUnit process) is still going, the Windows filesystem complains.

The possible solutions for this problem are to:

1. Create temporary directories/files in a different location (e.g. the canonical OS temp dir) and let the OS handle cleaning up the files later on. This is the easiest solution.

2. Add logic to "unmap" the memory mapped files when the unit tests are done with them (e.g. the unit test stop the storage engine so we can add logic in the storage engine stop methods to unmap the files it was using). This is a more comprehensive and correct approach, but unmapping isn't actually supported by the JVM so we'd have to use a hack to accomplish this.

I'm still mulling over which approach is best. I'm open to suggestions about which way to go. In the meantime, the best thing to do is just perform a build without running the unit tests on Windows machines. You can do that by doing the following:

./gradlew clean installer