Re: [platform-update-dev] Features will require click-through license

[klicnik@xxxxxxxxxx]

You're right .... I was being too restrictive in the DTD change. The DTD
should still list the element as optional, but any feature that is selected
for install/ update  (via UI or search) will need the click-through
license.

If you make use of nested features, then the nesting parent is the thing
you are selecting for installation, and it will need a license (presumably
representing in that license the full content of what was selected .... ie.
the children). If you do not use nesting (ie. all features are "flat") then
each of them will need a click-through license.

So I'll go back and fix the spec one more time. Sorry for the confusion.



                                                                                                                                
                    Peter                                                                                                       
                    Manahan/Toronto/IBM@IBMCA         To:     platform-update-dev@xxxxxxxxxxx                                   
                    Sent by:                          cc:     platform-update-dev@xxxxxxxxxxx,                                  
                    platform-update-dev-admin@e        platform-update-dev-admin@xxxxxxxxxxx                                    
                    clipse.org                        Subject:     Re: [platform-update-dev] Features will require              
                                                       click-through license                                                    
                                                                                                                                
                    06/13/2002 03:38 PM                                                                                         
                    Please respond to                                                                                           
                    platform-update-dev                                                                                         
                                                                                                                                
                                                                                                                                



So just to be clear.

We will be required to have an entry here for every feature not just
top-level features.

How do multiple features work (or is this not being implemented)
 I would assume that if installing multiple features say through a nested
feature that you only see the licence for the parent feature.

Bascially want to make sure aside from having the text there in each
feature for our 40 or so features. That a customer would only see the
license once.

 ( FYI we are required to translate the license into 9 languages  its a
waste of space as now we have to have 40 features with the same license
embedded into each feature. It would be better to just point to it which we
probably can't do)


Thanks,

-----------------------------------
Peter Manahan
WebSphere Tools
Build/Install and
Product Architecture
------------------------------------
manahan@xxxxxxxxxx



                    Vlad

                    Klicnik/Toronto/IBM@IBMCA         To:
platform-update-dev@xxxxxxxxxxx
                    Sent by:                          cc:

                    platform-update-dev-admin@e       Subject:
[platform-update-dev] Features will require click-through
                    clipse.org                         license



                    06/13/2002 03:15 PM

                    Please respond to

                    platform-update-dev







This is a heads up ....

We are being asked by the lawyers to modify feature handling by the update
manager to always ensure the features selected for installation or update
include a click-through license text (ie. specify <license>click through
text</license>). I have updated the packaging document to reflect this. We
will be making this change for the next milestone build.

If you have features that you have been creating ("real" features, or test
cases), you will need to ensure they specify license text in the
feature.xml, or separated in feature.properties. Otherwise you will not be
able to install them using the update manager support.

The packaging spec is
http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-update-home/doc/eclipse_update_packaging.html



There is a defect opened to track this change
http://dev.eclipse.org/bugs/show_bug.cgi?id=20154


_______________________________________________
platform-update-dev mailing list
platform-update-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/platform-update-dev