Carla Mott wrote:
>ok, thanks. BTW how do you get the dev-tests if you want them under the
>new scenario?
>
>
if you want to checkout devtests, 2 ways of doing this:
cd workspace (directory where you have the server code)
cvs -d :pserver:<userid>@cvs.dev.java.net:/cvs checkout glassfish/appserv-tests/devtests
or
cvs -d :pserver:<userid>@cvs.dev.java.net:/cvs checkout glassfish/bootstrap
cd glassfish/bootstrap
maven checkout-quicklook
cd ../appserv-tests
cvs update -d devtests
>There is a link to the FAQ on the build page already and not sure how
>to make that more visible.
>
>I will also update step 7 of the build instructions to and remove the
>sentence about commiting code. I will add a pointer to the section
>which actually talks about committing code so things are a bit cleaner.
>I think the following is confusing.
>
> 7. Cleaning the build. --> This is required before committing code to the
>trunk.
>
>% maven clobber
>
> This will remove all the scripts and jar files used to run the server. It
>will remove everything under glassfish.home.
>
>
>
>
>Dinesh Patil wrote:
>
>
>>Ok thanks Carla, i will updat it now.
>>I will be adding the checkout-quicklook target here to checkout
>>quicklook instead of checking out whole appserv-tests (which has bigger
>>dev-tests which are not required to checkout)
>>thanks
>>Dinesh
>>
>>Carla Mott wrote:
>>
>>
>>
>>>Hi dinesh,
>>>
>>>This is a wiki so all you have to do is hit the edit button at
>>>the bottom of the page. If you are not familiar with wikis
>>>then let me know and I will send more info.
>>>
>>>carla
>>>
>>>Dinesh Patil wrote:
>>>
>>>
>>>
>>>
>>>>We will have to add this in Build page :
>>>>http://wiki.java.net/bin/view/Projects/GlassFishBuildQuestions
>>>>
>>>>configure-runtime creates admin domain, domain1 as per setup.xml file,
>>>>so if you run configure-runtime again, it will fail since domain1 is
>>>>already present. There is "maven clean-config" target to delete domain
>>>>and can run configure-runtime again. (We will add this in build faq page)
>>>>
>>>>Please update this page or let me know how to update it.
>>>>thanks
>>>>Dinesh
>>>>
>>>>Dinesh Patil wrote:
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>>comments inline.
>>>>>Bill Shannon wrote:
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>>I'm still trying to learn the new build system. While I can probably
>>>>>>figure out the answers to these questions myself, I thought it might be
>>>>>>helpful to have the answers here for others to reference.
>>>>>>
>>>>>>I'm following the basic instructions at
>>>>>>https://glassfish.dev.java.net/public/BuildGlassFish.html.
>>>>>>These instructions worked fine to do the first build, but
>>>>>>what happens next?
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>Some more details can be accessed from the FAQ link which has
>>>>>"Glassfish Build Questions" link
>>>>>https://glassfish.dev.java.net/public/faq/index.html
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>>I did a build and ran some tests and then went back to make
>>>>>>changes and do another build. When I get to "maven configure-runtime"
>>>>>>it fails. Apparently you can only do configure-runtime once.
>>>>>>I'm not clear on whether I *need* to do configure-runtime after
>>>>>>each time I rebuild, or whether it's only needed once per what?
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>configure-runtime creates admin domain, domain1 as per setup.xml file,
>>>>>so if you run configure-runtime again, it will fail since domain1 is
>>>>>already present. There is "maven clean-config" target to delete domain
>>>>>and can run configure-runtime again. (We will add this in build faq page)
>>>>>About doing configure-runtime each rebuild time, it depends on the
>>>>>changes developer does on the rebuild, if its affect domain creation
>>>>>or domain.xml classpaths, jvm-options etc then yes will have to rerun
>>>>>this target otherwise no need if its just jar file updates.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>>Since configure-runtime failed, I decided I needed to go back
>>>>>>further in the build instructions so I did "maven clobber".
>>>>>>But then I wasn't sure how far back that took me. Did I now
>>>>>>need to do "maven bootstrap" again, or could I go straight into
>>>>>>"maven build"?
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>if you run maven clobber, it cleans up the server image so you will
>>>>>have to do "maven bootstrap build".
>>>>>http://wiki.java.net/bin/view/Projects/GlassFishBuildQuestions#MavenClobber
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>>Now I've made all my changes. Do I put the changes back using
>>>>>>"cvs commit", or is there a "maven commit"?
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>No there is no goal as "maven commit" so you will have to use "cvs
>>>>>commit"
>>>>>List of useful maven goals:
>>>>>http://wiki.java.net/bin/view/Projects/GlassFishBuildQuestions#MavenGoals
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>>If I later want to update my workspace with the latest changes from
>>>>>>the master workspace, do I use "cvs update" or is there a "maven
>>>>>>update"?
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>There is no goal as "maven update" but "maven checkout" will update
>>>>>the workspace.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>>Other than the first "cvs checkout glassfish/bootstrap" to get started,
>>>>>>is there any other time I should do a "cvs checkout"? Or should I
>>>>>>always
>>>>>>use "maven checkout"?
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>"maven checkout" needs to be used after glassfish/bootstrap module is
>>>>>checked out.
>>>>>Hope this helps.
>>>>>thanks
>>>>>Dinesh
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>>Thanks for helping me with these basic questions!
>>>>>>
>>>>>>---------------------------------------------------------------------
>>>>>>To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>>>>>>For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>---------------------------------------------------------------------
>>>>>To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>>>>>For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>
>
>
>