-
1. Re: The latest source code - WHERE ?
theute Feb 8, 2005 4:02 PM (in response to mholzner)STOPPPPPPP
No, the command is wrong wrong wrong :) Where did you see that ?
It's cvs -z3 -d :pserver:anonymous@cvs.sourceforge.net:/cvsroot/jboss co jboss-portal-2.0
And that's it.
It will get all you need.
Where did you guys see the jboss-portal stuff ? It should not be used.
(and yes Arturas, your code is there, with your name on top :) ) -
2. Re: The latest source code - WHERE ?
mholzner Feb 8, 2005 5:56 PM (in response to mholzner)thx for the clarification.
I think I found that browsing the cvs repository. -
3. Re: The latest source code - WHERE ?
arturasb Feb 9, 2005 1:31 AM (in response to mholzner)
It's cvs -z3 -d :pserver:anonymous@cvs.sourceforge.net:/cvsroot/jboss co jboss-portal-2.0
And that's it.
It will get all you need.
Thanks Thomas.
I have executed the CVS command like this one yesterday, but I couldn't find my part - neither new functionality of content type interceptor nor thirdparty libs (WALL and XOM). I decided that I
received the "standard" code of 2.0 alpha.
So, after that I created the "jboss-portal-2.0" Eclipse's project and looked into the CVS repository with the Eclipse's CVS client. I found 2 HEADs in the CVS - "jboss-portal" and "jboss-portal-thirdparty". I also found my new functionality and 3rd party libs there, but the layout of directories surprised me - new names of folders, the "thirdparty" is moved outside the "jboss-portal".
So I think I need your help here. Everything what I need is:
1. Eclipse integration. I use it for development, for updating from CVS repository, for building (ANT) and deploying the project.
2. Updates via command line CVS client. I would like that bothe Eclipse's and command line CVS updates would keep same file system structure.
Could someone help me with this ?
Thanks a lot in advance.
Arturas -
4. Re: The latest source code - WHERE ?
theute Feb 9, 2005 3:39 AM (in response to mholzner)That's the way the CVS is organised.
Again: DO NOT CHECKOUT jboss-portal-thirdparty and jboss-portal separately. It will NOT work.
Try again today, the public CVS is a mirror and i don't know how long it takes to update it.
cvs -z3 -d :pserver:anonymous@cvs.sourceforge.net:/cvsroot/jboss co jboss-portal-2.0
I swear it works. -
5. Re: The latest source code - WHERE ?
arturasb Feb 9, 2005 4:19 AM (in response to mholzner)That's the way the CVS is organised.
Again: DO NOT CHECKOUT jboss-portal-thirdparty and jboss-portal separately. It will NOT work.
Try again today, the public CVS is a mirror and i don't know how long it takes to update it.
cvs -z3 -d :pserver:anonymous@cvs.sourceforge.net:/cvsroot/jboss co jboss-portal-2.0
So, the only correct way to check out portal's source - just to use command line CVS client ? And the Eclipse is only used for development ?I swear it works.
Thomas, trust me - I believe you ;). What it's strange for me - I cannot use the Eclipse for my full development process. I mean, I get the "latest'n'greatest", then I code, build in one place - the IDE. Now I get the latest source by executing a CVS command in command line interface (CLI), then I make my changes with Eclipse and then I go to the CLI to build and to deploy it..... Well I can live with that, but it's less productive, IMHO.... -
6. Re: The latest source code - WHERE ?
theute Feb 9, 2005 4:26 AM (in response to mholzner)No no, you can use it inside Eclipse with the same information.
Host: cvs.sf.net
Repository Path: /cvsroot/jboss
User: anonymous
Password: <-- nothing
Connection type: pserver
Then you will have the CVS tree, pick jboss-portal-2.0 it's at the bottom (not any other)
Create a new project using the wizard (otherwise it won't be a java project). -
7. Re: The latest source code - WHERE ?
arturasb Feb 9, 2005 6:00 AM (in response to mholzner)"thomas.heute@jboss.com" wrote:
No no, you can use it inside Eclipse with the same information.
Host: cvs.sf.net
Repository Path: /cvsroot/jboss
User: anonymous
Password: <-- nothing
Connection type: pserver
Then you will have the CVS tree, pick jboss-portal-2.0 it's at the bottom (not any other)
Create a new project using the wizard (otherwise it won't be a java project).
Thanks God :). Thomas, you just saved my life (my time, I mean :)).
Well, one more question: can I build&deploy right from the Eclipse ? How must the ANT and the Eclipse be configured ? -
8. Re: The latest source code - WHERE ?
theute Feb 9, 2005 6:05 AM (in response to mholzner)You SHOULD can.
The build system sucks a bit, we are expecting a new one. You need a quite old version of ant to build, so the version shipped with Eclipse will probably not work. You need to configure eclipse so that it uses the ant shipped with JBoss Portal.
Personally, i have no problem Alt+tabing and do a build.sh deploy so i didn't bother. -
9. Seeing errors myself still dealing with libraries...
kgelner Feb 10, 2005 4:08 AM (in response to mholzner)"ArturasB" wrote:
It's cvs -z3 -d :pserver:anonymous@cvs.sourceforge.net:/cvsroot/jboss co jboss-portal-2.0
And that's it.
It will get all you need.
Thanks Thomas.
I have executed the CVS command like this one yesterday, but I couldn't find my part - neither new functionality of content type interceptor nor thirdparty libs (WALL and XOM). I decided that I
received the "standard" code of 2.0 alpha.
I think you are getting the right code base. I updated a few days back and found I needed the wurfl-wall and xom thirdparty libs also, which I added manually to get the compilation to proceed - I just updated tonight and still see no sign of them.
I was getting an OK build before, until I tried to deploy the portal module and did an update last Friday or so. Ever since then I have been having trouble getting the whole system to compile or even deploy again.
Currently after the latest update, I get 35 compile errors, most of which I think relate to not finding JWebUnit.
Currently my update command looks like:
cvs -d:pserver:anonymous@cvs.sf.net:/cvsroot/jboss update -d
I cannot remember if I did an initial co of jboss-portal-2.0, but I believe that's what I did originally... and I am seeing updates to the codebase.
It does seem weird that all the issues I have seem to be related to not seeing new thirdparty libs. Is something causing trouble with that update? Should I be seeing xom-xom and wurfl-wall from the update?
As far as command-line vs. GUI goes, I still prefer the command line for building and updating. Or at least I am very comfortable with it. -
10. Re: Seeing errors myself still dealing with libraries...
arturasb Feb 10, 2005 4:35 AM (in response to mholzner)Hi.
It does seem weird that all the issues I have seem to be related to not seeing new thirdparty libs. Is something causing trouble with that update? Should I be seeing xom-xom and wurfl-wall from the update?
As far as command-line vs. GUI goes, I still prefer the command line for building and updating. Or at least I am very comfortable with it.
Please, follow one of these instructions provided by Thomas:
1. Command linecvs -z3 -d :pserver:anonymous@cvs.sourceforge.net:/cvsroot/jboss co jboss-portal-2.0
or
2. IDE (Eclipse)you can use it inside Eclipse with the same information. Host: cvs.sf.net Repository Path: /cvsroot/jboss User: anonymous Password: <-- nothing Connection type: pserver Then you will have the CVS tree, pick jboss-portal-2.0 it's at the bottom (not any other) Create a new project using the wizard (otherwise it won't be a java project)
Both will result into the receiving the latest code, the correct project structure and - most important !!! - it builds with no single problem;) .
Cheers,
Arturas -
11. Re: Seeing errors myself still dealing with libraries...
theute Feb 10, 2005 5:07 AM (in response to mholzner)"kgelner" wrote:
Currently after the latest update, I get 35 compile errors, most of which I think relate to not finding JWebUnit.
Unfortunately when you add a dependant module in the CVS server, the update does not see it, each library is a module, so when we add a new library, you need to redo a fresh checkout :(
Sorry for that.
What you can do to avoid losing your change is to do a full co of jboss-portal-2.0 then copy the thirdparty directory over the former one.
This is tricky, but this is a limitation of CVS :(