Re: wolips / webobjects build question
Re: wolips / webobjects build question
- Subject: Re: wolips / webobjects build question
- From: Fred Shurtleff <email@hidden>
- Date: Wed, 12 Dec 2007 07:37:40 -0500
Anjo Krank wrote:
Am 12.12.2007 um 12:52 schrieb Kieran Kelleher:
Besides, checking out the whole tree lets you browse it to look for
goodies :-)
You shouldn't need to open the projects to see the source or debug it.
All binary Wonder frameworks have a "src.jar" which should let Eclipse
open the included java files (much like the JRE src.jar if you have it
installed). This should also provide the javadoc help. If it doesn't,
it's a bug in Eclipse/WOLips and needs to get handled there. Of course
you can't make changes to the source.
Can you detail how the source be viewed in src.jar?
I know Eclipse has a 'Java View' which I believe is purported to enable
this functionality; however I did not have any success.
Also I am aware of a 'jadEclipse' plugin designed for this purpose -
just trying to understand the options?
And, the other thing is that is how Anjo works AFAIK. He has whole
Wonder tree from CVS and I believe the same tree is checked into his
own team's svn repos ...... so they can make changes and manage micro
revisions using svn and then he can submit all those changes in bulk.
Kind of like having a branch in his svn repos and merging to the
trunk in soureforge CVS. .... this is what I gather from past email
discussions anyway. Anjo can correct me if I am wrong there.
Yeah that's about right. Branching, tagging and the like is extremely
costly in CVS. And I don't want to tie Wonder "releases" to our
release schedule. So what we do is:
initially:
- check out Wonder from CVS
- edit .subversion/config so it ignores "CVS" (and a few others)
global-ignores = ant .pbproj *._wpbxproj build bin dist target
ant.classpaths* ant.framework* CVS .DS_Store *.xcodeproj PB.project
CPFileList.txt *.pbxuser *.o *.lo *.la #*# .*.rej *.rej .*~ *~ .#*
*CVDL.launch *DW.launch .cvsignore pom.xml
- edit .cvsignore to ignore ".svn" (and a few others)
ricardo:~ ak$ cat .cvsignore
*.pbxuser
.DS_Store
CPFileList.txt
.svn
ant.*
build
bin
*.pbproj
*~.nib
*.xcodeproj
PB.project
- import the whole thing into svn (I think by "svn add", but I don't
remember)
Then, on changes by myself:
- commit to CVS (cvs commit -m 'Blabla')
- commit to svn (cursor up and change "cvs" to "svn")
On changes by others (only every few days or so):
- cvs up -dP
- svn commit -m "update from HEAD: blabla"
And when the time comes branch and tag in svn by normal "svn cp
.../trunk/Wonder .../branches/Wonder/R57"
Then checkout the branch, build the app and deploy in
.../Projects/Releases/R57/ (which allows us to have multiple versions
on the deployment machine). Small changes to the trunk are then merged
into the Release and tagged with "R57.0", "R57.1" etc.
When it's time to make a new release, start over, change the path in
Monitor to .../Projects/Releases/R58/...SomeApp.woa. Our Wonder
releases coincide with our app releases. So when we release our main
product R58, there is always a Wonder R58.
Someone might want to add this to the wiki, so it doesn't get lost as
it gets asked every few weeks...
Cheers, Anjo
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
--
MacOS: Tiger 10.4.11
Eclipse: 3.3.1.1
WOLips: 3.3.4705
WebObjects: 5.3.3
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden