#ident "@(#)issues 1.7 08/11/04 SAC" jhf-0 eclipse.org seems like it is a conglomeration of various components. Which projects from the community is this Sun project covering? jhf-1 Section 2.2 describes the release binding for the project. The answer to the question states that eclipse it is a Major release. Is that correct? What is the delivery mechanism for this project? Is it a Minor release of Solaris? jhf-2 What is the installation location? Is it really /usr/eclipse? jhf-3 Besides the eclipse binary is there anything else delivered? Are there any jar files delivered? jhf-4 The package name in the interface table is called eclipse. Is this an SVr4 package or IPS package? jhf-5 Is the project using the JDK that is installed on the system or is it using its own JDK? mhm-1 What consolidation is this going through? mhm-2 What is the j6dev package? What ARC case is that from? mhm-3 Related to jhf-4. Is that package name following package name rules? mhm-4 Is there a man page for this? Could you please put it in materials directory? Commitment Review, Nov. 4, 2008 tdc00 - is this distro being included with OpenSolaris, or is it simply a port that is being "made available" for OpenSolaris?  (FOSS checklist section 6.1 suggests that this is a port being delivered on the eclipse.org web site.) tdc01 - which Eclipse package is proposed, the JEE version, or the Java version?  (eclipse.org has packages 84-162MB in size!) If JEE, which app server is included? tdc02 - FOSS checklist, section 3.1.2, if you need a newer version of SWT, you will have to package it. What else does Eclipse require than the delivered SWT provides? tdc03 - is Eclipse 100% Java, or are there 64-bit issues with C/C++ components? tdc04 - FOSS section 3.4, doesn't Eclipse include an automatic update facility that is a network service? tdc05 - FOSS section 3.4.5, we need to understand any UI's involving passwords. For example, are CLI's CLIP-compliant? tdc06 - FOSS section 4.1, what are versions for imported interfaces? Where are they coming from, and are they packaged inside Eclipse? tdc07 - FOSS section 4.2, what is "GTK"? tdc08 - what are plans to keep this distro up to date? How will new Eclipse releases get into OpenSolaris, and can a user simply download an update and overlay it on the installation that you are providing with OpenSolaris? jhf-6 pkgmap requested jhf-7 SWT needs to be packaged separately. jhf-8 SWT 64-bit library necessary jhf-9 This project uses JUnit. Why can it not use the JUnit from LSARC/2008/633? jhf-9 Security questionnaire needed. jhf-10 How are the passwords stored? Are they stored in a file on disk? How are the passwords entered? (section 3.4.5) mm0 In the ARC 20q, the answer for section 3.4.5 regarding storage of passwords was "no". I believe this is incorrect, as Eclipse now includes the "Secure storage" system. This is a new integrated framework intended for caching passwords -- notably for CVS, which is part of the core bundle. mm1: Regarding core components (i.e. those components expected to be installed in the core distribution and not available as part of a plugin download); SWT and it's JNI dependencies suggest further interface declaration. Notably, GTK+, I believe. Support and maintenance of this piece of core functionality has been spotty in the past, so perhaps I can only offer advice here. If the intent is to deliver (and track) the core Eclipse distribution, then I think it is important to not paint the user in a corner regarding this core component. Having up-to-date SWT libraries has been a challenge in the past. Use of alternate distributions of the Eclipse platform for Solaris/OpenSolaris was often very limited as many additional plugin tools or updates required newer versions of some of the core SWT libraries, and these were often unavailable and had to be compiled by hand (and certainly included dependencies on graphic libraries)! . mm99: Which distribution is this intended to deliver? "Eclipse IDE for Java developers"? "Eclipse Classic"? Are other modules, such as "Eclipse for C/C++" to be included? I suspect the answer here might mean a fuller interface disclosure. mm98: As mentioned in the meeting, how is plugin downloading handled? This may not be the team's responsibility, perhaps, as this is more a question regarding the distribution and should probably be asked of the Indiana team. Does the team intend to make a bundle available for download via the upstream repositories as well?