There’s also TortoiseGIT for all TortoiseSVN users. But cmd is still the most powerful way to work.
If you are talking to me, then i don’t need that power I just need a simple and preferabbly gui tool to quickly get the up2date source and test a patch. Don’t really want to dig into all these “branches, trees, leafs” stuff I will try the NetBeans path first, when the transition is completed.
Jason, i have tried to setup Git clone in Netbeans and link it to a new project. I do checkout of master and then build a project. But i get not the recent version (659 build). I see no build number in the About box in this version, like i do in the latest Bamboo build (2.7.0.658 or 659). Maybe this patch is still not in the master or what i’m doing wrong?
I’m using https://github.com/igniterealtime/Spark.git as URL.
the build number is dynamically set at build time. if a build number is not specified, it doesn’t show in the about box. to specify a build number, when building with ant use:
ant <your_target> -Dbuild.number=<your_build_number>
bamboo does something similar to:
ant clean jar -Dbuild.number=${bamboo.buildNumber}
you can specify your own build number by doing something like:
ant clean release -Dbuild.number=9000
passing the build number into ant was the only way to get dynamic build numbers. it’s also generic enough that people doing their own builds can specify custom build numbers easily. note that spark’s version (ie. 2.7.0) is also set dynamically at build time from the version specified inside the ant build script. both being set at build time has the added benefit that nobody has to remember to bump all the version numbers!
I see. Thanks for clarification. Will leave it as is. I just thought it didn’t pull the recent version from the GitHub. I’m going to use this clone just to test patches, so i can live without version or build numbers