Update center needs to be ready - Abhijit would know the answer to this.
Scott also needs to change v3 quick start for this.
Barbara
Jennifer Ball wrote:
> Thanks, Barbara. Do you know when it will be ready? I have to check
> in my work by 11:59 PM this Wednesday, 4/30. I'd like at least a few
> hours to change the docs and test the examples.
>
> Jennifer
>
> Barbara Louis wrote:
>> Jennifer,
>>
>> Hold onto this thought - once the updatetool is ready we will let you
>> know for Jruby.
>> Barbara
>>
>>
>> Jennifer Ball wrote:
>>> Originally, I thought that those who wanted to use JRuby or jMaki
>>> with GF V3 TP2 would need to use the update tool to get them, but I
>>> didn't get the information I needed about the update tool in time to
>>> document using it to get JRuby or jMaki.
>>> So, I just did the following:
>>>
>>> * in the JRuby guide, I tell readers to get JRuby from
>>> jruby.codehaus.org.
>>> * in the jMaki guide, I tell readers to get jMaki via the NetBeans
>>> update center.
>>>
>>> If this isn't correct, please let me know ASAP.
>>>
>>> Thanks.
>>> Jennifer
>>>
>>> Scott Fordin wrote:
>>>> Thanks for the clarification, Snjezana.
>>>>
>>>> Given that JavaDB will be available in TP2 but Update Tool will
>>>> require an additional installation step, does it make sense to
>>>> *not* talk about Update Tool in the QSG? I mean, I say only a
>>>> little about Update Tool now, in part so readers know what I'm
>>>> talking about when I tell them that they have to use it to get
>>>> JavaDB. Now that JavaDB is in the TP2 distribution after all, I
>>>> don't think we really gain anything in a QSG context by talking
>>>> about Update Tool. How do others feel about this?
>>>>
>>>> Thanks,
>>>>
>>>> Scott
>>>>
>>>> Snjezana Sevo-Zenzerovic wrote:
>>>>> Note that updatetool integration has not been fully merged into
>>>>> the trunk yet and in order to get it you would actually need to
>>>>> build packager and installer modules (and to build packager module
>>>>> you need to have package repository server up and running so this
>>>>> is not something you would regularly do in developer build).
>>>>>
>>>>> JavaDB will definitely be available in TP2 distributions.
>>>>> Updatetool will also be available, but users will either have to
>>>>> choose to download and install it while running installer or
>>>>> consent to download and install it once they attempt to run
>>>>> skeleton updatetool scripts which will be part of TP2 distribution.
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Snjezana
>>>>>
>>>>> Scott Fordin wrote:
>>>>>
>>>>>> Two other things to note here:
>>>>>>
>>>>>> 1. In the build I just made from a fresh checkout of the
>>>>>> v3 trunk, there is still no Update Tool, but the
>>>>>> default start page you see at localhost:8080 after
>>>>>> starting the default domain refers to Update Tool.
>>>>>>
>>>>>> 2. The wiki page to which the default start page points
>>>>>> refers to "Update Center" rather than "Update Tool."
>>>>>>
>>>>>> Scott
>>>>>>
>>>>>>> Can someone please provide clarification here? I'm getting
>>>>>>> conflicting stories about Java DB and Update Tool in TP2.
>>>>>>>
>>>>>>> 1. Is Java DB going to be bundled in TP2? When I do
>>>>>>> builds from the source tree, it's there, but I've
>>>>>>> been told that it will only be available from Update
>>>>>>> Tool.
>>>>>>>
>>>>>>> 2. Is Update Tool going to be bundled in TP2? I've been
>>>>>>> told that it is, but I do not see it when I do builds
>>>>>>> from the source tree.
>>>>>>>
>>>>>>> The answers to these questions have implications for the
>>>>>>> Release Notes and Quick Start, among other docs.
>>>>>>>
>>>>>>> Thanks,
>>>>>>>
>>>>>>> Scott
>>>>>>>
>>>>>>> Anissa Lam wrote:
>>>>>>>
>>>>>>>> Hi Paul,
>>>>>>>> Here is my comment regarding draft 2 Release Notes.
>>>>>>>>
>>>>>>>> - resolve any trademark issue
>>>>>>>>
>>>>>>>> - Please coordinate the name with the QSG that Scott sent out.
>>>>>>>> Where the word "Application Server" sits ?
>>>>>>>> RN: GlassFish v3 Technology Preview 2 *Application Server*
>>>>>>>> QSG: GlassFish *Application Server* v3 Technology Preview 2
>>>>>>>>
>>>>>>>> - In table 2-2, please change the port # 4848 Administration
>>>>>>>> Server to #8080 instead.
>>>>>>>>
>>>>>>>> - pg 12, Java DB utility Scripts
>>>>>>>> The following scripts are available for use in the
>>>>>>>> *as-install/javadb/bin* directory:
>>>>>>>> It should be glassfish/javadb/bin or
>>>>>>>> as-install/glassfish/javadb/bin because after unzip, there is
>>>>>>>> the glassfish directory.
>>>>>>>>
>>>>>>>> Same as in step2 for configuration.
>>>>>>>> Set the DERBY_HOME environment variable to point to the
>>>>>>>> *as-install/javadb* directory.
>>>>>>>>
>>>>>>>> pg. 16
>>>>>>>> *as-install/bin/asadmin* set
>>>>>>>> "server.java-config.java-home=path-to-java-home"
>>>>>>>>
>>>>>>>>
>>>>>>>> - pg 17. Uninstalling GlassFish
>>>>>>>> To uninstall GlassFish v3 Technology Preview 2 Application
>>>>>>>> Server, you must use the
>>>>>>>> uninstallation program that is included with the software.
>>>>>>>> I am not aware of such a tool. And if it exists, you should
>>>>>>>> specify what that tool is, at least the tool name.
>>>>>>>>
>>>>>>>> - pg 18 Update Tool.
>>>>>>>> It talks about how to use the update tool. However, i don't
>>>>>>>> believe update tool is available in tp2. bin/updatetool
>>>>>>>> doesn't exist. You should check with Nazrul about this.
>>>>>>>>
>>>>>>>> thanks
>>>>>>>> Anissa
>>>>>>>>
>>>>>>>>
>>>>>>>> Paul Davies wrote:
>>>>>>>>
>>>>>>>>> Hi,
>>>>>>>>>
>>>>>>>>> When I sent out draft 1 of the Glass Fish v3 TP2 Release
>>>>>>>>> Notes, I omitted information about asadmin command options
>>>>>>>>> that are not supported at TP2. Attached is draft 2, which
>>>>>>>>> rectifies that omission.
>>>>>>>>>
>>>>>>>>> The only changes compared with draft 1 are as follows:
>>>>>>>>>
>>>>>>>>> * I added Restrictions forGlassFish v3Technology Preview2
>>>>>>>>> Application Server, which contains the new sections
>>>>>>>>> Unsupported Options in asadmin Commands (pp17-18).
>>>>>>>>>
>>>>>>>>> * I moved Features Not Supported on All Operating Systems
>>>>>>>>> (p18) inside the Restrictions section.
>>>>>>>>>
>>>>>>>>> If you have already reviewed draft 1, please look at the
>>>>>>>>> changed sections on pp 17-18.
>>>>>>>>>
>>>>>>>>> If you have not already reviewed draft 1, please review draft 2.
>>>>>>>>>
>>>>>>>>> Draft 2 does not include any comments that I have already
>>>>>>>>> received (for which many thanks). I shall wait until my
>>>>>>>>> orginial review deadline has passed before I process the
>>>>>>>>> review comments that I have already received.
>>>>>>>>>
>>>>>>>>> If possible, please provide your feedback by the origianl
>>>>>>>>> deadline of Thursday, April 24, 2008.
>>>>>>>>>
>>>>>>>>> Thank you.
>>>>>>>>> ------------------------------------------------------------------------
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>>
>>>>>>>>> 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
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>>
>>>>>> 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
>>>>>
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: docs-unsubscribe_at_glassfish.dev.java.net
>>>> For additional commands, e-mail: docs-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
>>>
>>
>> ---------------------------------------------------------------------
>> 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
>