02-05-2009 04:22 AM
Hi guys,
I need to know whether the Blackberry JDE is supporting the SVN(subversion) concept? or not?
If it's possible please let me know through this.
Thanks in advance!
02-05-2009 05:45 AM
As far as I know Blackberry JDE does not support subversion.
To use subversion - try BlackBerry JDE Plug-in for Eclipse
02-05-2009 08:24 AM
Cygwin supports it just fine. I don't usually use source control but I have used
it to download projects etc. Now that you mention it however, I guess
I could consider adding it to my scripts.
btw, how do those things handle builds for multiple jdes? I just downloaded
4.7 and added it to the build scripts and from the limited feedback I got
the resulting app runs on simulator ( same one built for 4.0.2 ran but was
stuck in compatability mode). I would also mention that scripts
can easily support a distributed development environment as the last step
is to upload to server so anyone else can test it from anywhere.
02-05-2009 08:36 AM
02-05-2009 12:26 PM
I also agree with groverblue - we use Tortoise on Windows systems. This is an Exporer plug-in. You simply right-click on the folder and select the SVN command that you want to execute.
04-22-2009 08:41 AM
tbilisoft wrote:As far as I know Blackberry JDE does not support subversion.
To use subversion - try BlackBerry JDE Plug-in for Eclipse
I used the BlackBerry JDE Plug-in for Eclipse, but I discovered that rapc includes the subversion metadata files in the set of build files which leads to the following error:
Executing rapc for the project Gryphos-Barcode at Wed Apr 22 13:51:17 CEST 2009. C:\d\Programme\eclipse-3.4\eclipse\plugins\net.rim
.eide.componentpack4.7.0_4.7.0.46\components\bin\l auncher.exe C:\d\Programme\eclipse-3.4\eclipse\plugins\net.rim .eide.componentpack4.7.0_4.7.0.46\components\bin\r apc.exe -deprecation import=..\..\Programme\eclipse-3.4\eclipse\plugins \net.rim.eide.componentpack4.7.0_4.7.0.46\componen ts\lib\net_rim_api.jar codename=Gryphos-Barcode\Gryphos-Barcode Gryphos-Barcode\Gryphos-Barcode.rapc -sourceroot=C:\d\_SVN_PROJECTS\BlackBerryJDE\Gryph os-Barcode\.tmp;C:\d\_SVN_PROJECTS\BlackBerryJDE\G ryphos-Barcode\src-gen;C:\d\_SVN_PROJECTS\BlackBer ryJDE\Gryphos-Barcode\src @Gryphos-Barcode_build.files I/O Error: C:\d\_SVN_PROJECTS\BlackBerryJDE\Gryphos-Barcode\. tmp\.svn\all-wcprops (Das System kann den angegebenen Pfad nicht finden) rapc executed for the project Gryphos-Barcode
The same error appears in the BlackBerry JDE once the project is shared with a SVN repository. I guess using TortoiseSVN does not help in this case because rabc parses the project directory for build files and allways find the SVN files.
If anybody has any idea about that problem I like to here about it.
04-22-2009 09:04 AM
Custom scripts are working just fine- I'm using subversion and cygwin for everything now, just used svn copy to port
code from another project, and can build for desktop or phone from same code. Works fine.
04-22-2009 09:15 AM
marchywka wrote:Custom scripts are working just fine- I'm using subversion and cygwin for everything now, just used svn copy to port
code from another project, and can build for desktop or phone from same code. Works fine.
Hi,
can you please post your scripts for reference ?
04-22-2009 09:36 AM
I've posted to relevant parts. Most of it is project specific make files. I just list the files in a file I always call
"setup" in each project directory and then have the build scripts reference this. The approach is perfectly
general, I use this for building java projects from other places ( ignoring the ant files ) and collating
data from csv files etc.
Since it doesn't work with IDE's, you don't get things like function signatures to pop up
but I'm working on thins like this as a need arises. If I could feed error locations to vi
I'd be happy but it hasn't been a high priority although there are examples for doing this with c++
output.
I don't actually have any scripts afaik that invoke svn as this is usually a really manual step depending
on what is going on.
04-22-2009 06:04 PM
I guess you could do an svn commit or make a tag or branch on release, but I haven't had a need for
that yet. In any case, that would be afew lines of a bash script hardly a big deal.