I posted a question to the DBunit mailing list about an error I see when I compile my program. One of the response I get is shown below:
Please try 2.4.9-SNAPSHOT (you will have to build from source;
snapshots are not currently pre-built). I believe commit 1209 fixes
the problem you are experiencing:
I looked at the DBunit project and I can't figure out how to download this specific version.
I tried this command but it comes back with a Does not exist error
svn checkout https://dbunit.svn.sourceforge.net/svnroot/dbunit/trunc/2.4.9-SNAPSHOT dbunit
I think the command is correct because if I try a release that does exist it does work. For example the following command works
svn checkout https://dbunit.svn.sourceforge.net/svnroot/dbunit/tags/dbunit-2.4.8 dbunit
Looking at the online code browser I can't see an entry with the tag I want. See Example at http://dbunit.svn.sourceforge.net/viewvc/dbunit/
Does this mean that the 2.4.9-SNAPSHOT does not exist or am I doing it wrong?
Also, what does the SNAPSHOT label mean at the end of the release version? I have seen this used quite a lot but not really sure what it means.
Thanks
Just download the source code in specified revision:
$ svn co https://dbunit.svn.sourceforge.net/svnroot/dbunit/trunk dbunit -r 1209
$ cd dbunit
$ mvn clean install
The 2.4.9-SNAPSHOT version should appear in your repository when the build finishes. However I encounter some problems while building it, the com.oracle:ojdbc14:jar:10.2.0.4.0 cannot be found. Consult library developers how to fix this.
Related
I've been learning Clojure for around a month now and I've decided to experiment with Datomic. I'm following the tutorial on the site exactly, but I can't even get past the first tutorial page (http://docs.datomic.com/first-db.html) because I get the following error on run:
run -m datomic.peer-server -p 8998 -a myaccesskey,mysecret -d firstdb,datomic:mem://firstdb
The system cannot find the path specified.
Error: Could not find or load main class clojure.main
I think this is just a classpath issue (I only picked up Java to work with Clojure), but looking at run.bat I think Datomic is set up to determine classpaths automatically, and I'd rather understand why it doesn't work out of the box (presumably a config issue on my machine, although I've tried another).
I've tried the latest version (0.9.5544) as well as the version explicitly mentioned in the tutorial (0.9.5530), as well as installing via Maven. Tried numerous other tutorials and forum-searches as well - plenty of general classpath advice, but nothing relevant to this. Please, send help!
Tom
Update - I seem to have resolved my issue. The instructions on the Datomic tutorial page appear to be incorrect (they say bin/run, but bin\run works). I worked around the bin/run error by running directly from the bin folder, but this obviously had the knock-on effect of making any relative paths incorrect.
I suspect I'm not great at Stack Exchange since I seem to have answered all of my own questions so far, but I hope someone else finds this useful!
When I run the commands specified in OpenBR page to build the library, I am getting the following error. Its coming when I execute the sub module update command.
Is it because the the repository is not available in that location? If that's not the case, why is it not running?
(At first I think it should be a comment but I cant).
I have the same issue like you when I install it. I believe the problem here is the link to repos of doc of openbr(it's not correct, maybe it's changed). You can continue with build process, this error dont have any effect in it and use the doc from official website. Good luck!
I was trying to build QtD using the instructions here:
http://www.dsource.org/projects/qtd/wiki/BuildWindows
I downloaded the repo.
Went inside the repo (it was called repo and not qtd as the instructions said).
I created the build_dir dir and went inside there.
I used the:
cmake -G"MinGW Makefiles" ../
Command and then I got the following error:
Error: CMake: Could not create named generator MinGW Makefiles
Taking advice from a friend I went inside the d2 directory and went inside the qtd dir there, and repeated the steps above.
Same error.
I have the components the instructions listed, and with what I believe is needed on my PATH
What am I doing wrong? Are there any other instructions I'm missing?
I'd heard that QtD was no longer maintained. Certainly, the last commit on dsource was 3 years ago: http://www.dsource.org/projects/qtd/browser
However, the d wiki has a link to bitbucket where someone has a version of it which had a commit as recently as December. So, I guess that someone revived it and put it up on bitbucket.
However, regardless of whether the bitbucket repo is now indeed the "official" QtD repo, given that the last commit to the dsource repo was 3 years ago, the odds are very high that it no longer compiles, even if you use the correct build commands. So, I'd advise checking out the bitbucket repo and seeing if you can get that to work rather than trying to get the version on dsource to work. And even if you could get the dsource version to work, it's clearly unmaintained, so you're not going to want to use it long term, whereas the bitbucket version does appear to have had work done on it relatively recently.
We have been trying to build wso2 (various products) from source to no avail.
I have looked for information all over (with assistance from Google) and followed the few instructions we have found but without luck.
I have, on the other hand, found various posts discussing this process and how error prone it is due to this or that.
Don't get me wrong, WSO2 looks like an amazing framework to work within but confidence in the project is not boosted by the complicated/error prone/enormous build process.
Does anyone here have a good description/recipes to build the 4.x.x version of carbon?
I really don't think it is intentionally hard to build. The product is huge with tons on developers working on it. Most of the issues seem to be around erroneous commits by developers. My understanding is that WSO2 will be changing the development process to make it more robust (source: Manoj's Comment).
The WSO2 set of products are awesome and well engineered. They can be built, but you will need to persist and resolve issues along the way.
It took me quite a few days to get a working build in my spare time. Here is a rough sequence of tasks to perform:
1) Checkout the 4.0.0 branch:
svn co https://svn.wso2.org/repos/wso2/carbon/orbit/branches/4.0.0
svn co https://svn.wso2.org/repos/wso2/carbon/kernel/branches/4.0.0
svn co https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.0.0
For more information of the code base high level structure, see here: what is wso2 'orbit', 'kernel' and 'platform'?
2) Decide which version of a product you need to build - Which version of patch-release to build?
3) Build the three separate code bases (build the main branch plus patch-release versions below your required version).
build orbit 4.0.0/ Then build orbit/patch-release/4.0.x
build kernel 4.0.0/ Then build kernel/patch-release/4.0.x
build platform 4.0.0/ Then build platform/patch-release/4.0.x
Note to build:
use Java 6 (Use Sun/Oracle JDK - not OpenJDK)
use Maven 3
set MAVEN_OPTS to -Xms512m -Xmx1024m -XX:MaxPermSize=1024m
you will probably need to use the following mvn command line: mvn clean install -Dmaven.test.skip=true
You will find the built distribution zip file here: ROOT/distribution/product/modules/distribution/target/ (source: WSO2 Carbon 4.1.x - how to make the distribution)
Be prepared to put in the time to hunt down and fixing issues as you encounter them. Most issues seem to be due to maven dependency issues. Using google, you can usually find the answer. Also you post any issues you need help with on stackoverflow.
http://code.google.com/r/hectorchu-go-windows/source/list
If you could compile it successfully, I like to know the procedures of how to.
Assuming you are using Hector's source tree:
Install MinGW and MSYS, along with MSYS Bison and any other tools you think you'll find useful (vim, etc).
Install ed from the GNUWin32 project.
Install Python and Mercurial.
Clone the [hectorchu-go-windows mercurial repository](https://hectorchu-go-windows.googlecode.com/hg/ hectorchu-go-windows) to C:\Go.
Run an MSYS shell (or rxvt). The rest of these are bash commands...
mkdir $HOME/bin
export PATH=$HOME/bin:$PATH
export GOROOT=C:\\Go
export GOARCH=386
export GOOS=mingw
cd /c/Go/src
./all.bash
Correct errors as it spits them out at you, repeat step 10 until it starts building.
It's the same idea as on Linux or MacOS, basically.
However, I still stand by what I said in my comment above: this isn't necessarily going to generate anything that actually works yet. You'd be better served by waiting until this effort has merged into the main Go tree before tackling it, unless your interest is in assisting with the porting effort.
Update: there is now a mostly-functional pre-built windows port available, for those not interested in building the compiler themselves. However, given the rate of change of the project, the lack of formal releases (other than the hg "release" tag), and the possibility of Hector's changes being merged into the main branch soon, keeping up with development via source builds is likely to produce better results over time.
Just FYI, there is seems official one now.
http://code.google.com/p/go-windows/
Hector said he was only able to get as far as being able to compile and run an empty main. See issue 107:
http://code.google.com/p/go/issues/detail?id=107
There is still a lot of work to do in porting that, especially since the code has lots of dependencies on ptrace and syscall, not to mention the different threading models between Linux/BSD and Windows.
Update:
There's a new thread on golang-nuts (started 26.03.2010) with a link to a recent build and some current building instructions (using MinGW+MSYS).