Attachment #105702 for bug #194518

This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

View | Details | Raw Unified | Return to bug 194518
Collapse All | Expand All




<?xml version="1.0" encoding="UTF-8"?>
<!--
DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS HEADER.

Copyright 1997-2010 Oracle and/or its affiliates. All rights reserved.

Oracle and Java are registered trademarks of Oracle and/or its affiliates.
Other names may be trademarks of their respective owners.


The contents of this file are subject to the terms of either the GNU
General Public License Version 2 only ("GPL") or the Common
Development and Distribution License("CDDL") (collectively, the
"License"). You may not use this file except in compliance with the
License. You can obtain a copy of the License at
http://www.netbeans.org/cddl-gplv2.html
or nbbuild/licenses/CDDL-GPL-2-CP. See the License for the
specific language governing permissions and limitations under the
License.  When distributing the software, include this License Header
Notice in each file and include the License file at
nbbuild/licenses/CDDL-GPL-2-CP.  Oracle designates this
particular file as subject to the "Classpath" exception as provided
by Oracle in the GPL Version 2 section of the License file that
accompanied this code. If applicable, add the following below the
License Header, with the fields enclosed by brackets [] replaced by
your own identifying information:
"Portions Copyrighted [year] [name of copyright owner]"

Contributor(s):

The Original Software is NetBeans. The Initial Developer of the Original
Software is Sun Microsystems, Inc. Portions Copyright 1997-2008 Sun
Microsystems, Inc. All Rights Reserved.

If you wish your version of this file to be governed by only the CDDL
or only the GPL Version 2, indicate your decision by adding
"[Contributor] elects to include this software in this distribution
under the [CDDL or GPL Version 2] license." If you do not indicate a
single choice of license, a recipient has the option to distribute
your version of this file under either the CDDL, the GPL Version 2 or
to extend the choice of license to its licensees as provided above.
However, if you add GPL Version 2 code and therefore, elected the GPL
Version 2 license, then the option applies only if the new code is
made subject to such option by the copyright holder.
-->
<?xml-stylesheet type="text/xml" href="../nbbuild/javadoctools/apichanges.xsl"?>
<!DOCTYPE apichanges PUBLIC "-//NetBeans//DTD API changes list 1.0//EN" "../nbbuild/javadoctools/apichanges.dtd">

<apichanges>

    <!-- First, a list of API names you may use: -->
    <apidefs>
        <apidef name="ui">Autoupdate UI API</apidef>
    </apidefs>

    <!-- ACTUAL CHANGES BEGIN HERE: -->

    <changes>
        <change id="PluginManager.openInstallWizard">
            <api name="ui"/>
            <summary>PluginManager.openInstallWizard</summary>
            <version major="1" minor="20"/>
            <date day="14" month="2" year="2011"/>
            <author login="jtulach"/>   
            <compatibility addition="yes" binary="compatible" deletion="no"
                deprecation="yes" semantic="compatible" source="compatible"  
            />
            <description>
                <p>
                <code>PluginManager</code> ands its <code>openInstallWizard</code>
                shows standard UI for installing of selected modules.
                </p>
            </description>
            <class package="org.netbeans.modules.autoupdate.ui.api" name="PluginManager"/>
            <issue number="194518"/>
        </change>
    </changes>

    <!-- Now the surrounding HTML text and document structure: -->

    <htmlcontents>
<!--

                            NO NO NO NO NO!

         ==============>    DO NOT EDIT ME!  <==============

          AUTOMATICALLY GENERATED FROM APICHANGES.XML, DO NOT EDIT

                SEE projects/projectapi/apichanges.xml

-->
    <head>
      <title>Change History for the Autoupdate UI API</title>
      <link rel="stylesheet" href="prose.css" type="text/css"/>
    </head>
    <body>

<p class="overviewlink"><a href="overview-summary.html">Overview</a></p>

<h1>Introduction</h1>

<p>This document lists changes made to the <a href="@org-netbeans-modules-autoupdate-ui@/index.html">Autoupdate UI API</a>.</p>

<!-- The actual lists of changes, as summaries and details: -->
      <hr/>
      <standard-changelists module-code-name="org.netbeans.modules.autoupdate.ui"/>

      <hr/><p>@FOOTER@</p>

    </body>
  </htmlcontents>

</apichanges>




<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE api-answers PUBLIC "-//NetBeans//DTD Arch Answers//EN" "../nbbuild/antsrc/org/netbeans/nbbuild/Arch.dtd" [
  <!ENTITY api-questions SYSTEM "../nbbuild/antsrc/org/netbeans/nbbuild/Arch-api-questions.xml">
]>

<api-answers
  question-version="1.29"
  author="yourname@netbeans.org"
>

  &api-questions;


<!--
        <question id="arch-overall" when="init">
            Describe the overall architecture. 
            <hint>
            What will be API for 
            <a href="http://openide.netbeans.org/tutorial/api-design.html#design.apiandspi">
                clients and what support API</a>? 
            What parts will be pluggable?
            How will plug-ins be registered? Please use <code>&lt;api type="export"/&gt;</code>
            to describe your general APIs and specify their
            <a href="http://openide.netbeans.org/tutorial/api-design.html#category-private">
            stability categories</a>.
            If possible please provide simple diagrams.
            </hint>
        </question>
-->
 <answer id="arch-overall">
  <p>
   The AutoUpdate UI module contains user visible elements (actions in menu, 
   dialogs), that allow any users to download new, or existing modules from
   a pre-registered or manually registered update centers. In addition 
   the module also provides an API to allow other modules to 
   invoke pieces of the user related work flow (dialogs, wizards) directly
   at moments independent on the rest of the provided UI.
  </p>
 </answer>



<!--
        <question id="arch-quality" when="init">
            How will the <a href="http://www.netbeans.org/community/guidelines/q-evangelism.html">quality</a>
            of your code be tested and 
            how are future regressions going to be prevented?
            <hint>
            What kind of testing do
            you want to use? How much functionality, in which areas,
            should be covered by the tests? How you find out that your
            project was successful?
            </hint>
        </question>
-->
 <answer id="arch-quality">
  <p>
   XXX
  </p>
 </answer>



<!--
        <question id="arch-time" when="init">
            What are the time estimates of the work?
            <hint>
            Please express your estimates of how long the design, implementation,
            stabilization are likely to last. How many people will be needed to
            implement this and what is the expected milestone by which the work should be 
            ready?
            </hint>
        </question>
-->
 <answer id="arch-time">
  <p>
   The module is part of NetBeans IDE distribution for long time and its 
   functionality is covered and tested by many eyes using NetBeans IDE. 
   The API will be added in incremental manner (starting from 7.0) 
   and will slowly expose the
   bits of already existing UI to external module writers.
  </p>
 </answer>



<!--
        <question id="arch-usecases" when="init">
            <hint>
                Content of this answer will be displayed as part of page at
                http://www.netbeans.org/download/dev/javadoc/usecases.html 
                You can use tags &lt;usecase name="name&gt; regular html description &lt;/usecase&gt;
                and if you want to use an URL you can prefix if with @TOP@ to begin
                at the root of your javadoc
            </hint>
        
            Describe the main <a href="http://openide.netbeans.org/tutorial/api-design.html#usecase">
            use cases</a> of the new API. Who will use it under
            what circumstances? What kind of code would typically need to be written
            to use the module?
        </question>
-->
 <answer id="arch-usecases">
  <usecase id="PluginManager.openInstallWizard" name="Download and Install">
  Primary purpose of the API is to share classical UI for downloading and
  installing additional modules. Read about 
  <a href="@TOP@/org/netbeans/modules/autoupdate/ui/api/PluginManager.html">PluginManager.openInstallWizard</a>.
  </usecase>
 </answer>



<!--
        <question id="arch-what" when="init">
            What is this project good for?
            <hint>
            Please provide here a few lines describing the project, 
            what problem it should solve, provide links to documentation, 
            specifications, etc.
            </hint>
        </question>
-->
 <answer id="arch-what">
  <p>
   <api category="stable" group="java" name="AutoUpdateUI" type="export">
       this module exposes bits of its UI and user related workflow actions
       (related to installing, upgrading, etc.) by providing an API calls
       for other modules to invoke bits of here-in available functionality.
   </api>
  </p>
 </answer>



<!--
        <question id="arch-where" when="impl">
            Where one can find sources for your module?
            <hint>
                Please provide link to the Hg web client at
                http://hg.netbeans.org/
                or just use tag defaultanswer generate='here'
            </hint>
        </question>
-->
 <answer id="arch-where">
  <defaultanswer generate='here' />
 </answer>



<!--
        <question id="compat-deprecation" when="init">
            How the introduction of your project influences functionality
            provided by previous version of the product?
            <hint>
            If you are planning to deprecate/remove/change any existing APIs,
            list them here accompanied with the reason explaining why you
            are doing so.
            </hint>
        </question>
-->
 <answer id="compat-deprecation">
  <p>
   XXX no answer for compat-deprecation
  </p>
 </answer>



<!--
        <question id="compat-i18n" when="impl">
            Is your module correctly internationalized?
            <hint>
            Correct internationalization means that it obeys instructions 
            at <a href="http://www.netbeans.org/download/dev/javadoc/org-openide-modules/org/openide/modules/doc-files/i18n-branding.html">
            NetBeans I18N pages</a>.
            </hint>
        </question>
-->
 <answer id="compat-i18n">
  <p>
   XXX no answer for compat-i18n
  </p>
 </answer>



<!--
        <question id="compat-standards" when="init">
            Does the module implement or define any standards? Is the 
            implementation exact or does it deviate somehow?
        </question>
-->
 <answer id="compat-standards">
  <p>
   XXX no answer for compat-standards
  </p>
 </answer>



<!--
        <question id="compat-version" when="impl">
            Can your module coexist with earlier and future
            versions of itself? Can you correctly read all old settings? Will future
            versions be able to read your current settings? Can you read
            or politely ignore settings stored by a future version?
            
            <hint>
            Very helpful for reading settings is to store version number
            there, so future versions can decide whether how to read/convert
            the settings and older versions can ignore the new ones.
            </hint>
        </question>
-->
 <answer id="compat-version">
  <p>
   XXX no answer for compat-version
  </p>
 </answer>



<!--
        <question id="dep-jre" when="final">
            Which version of JRE do you need (1.2, 1.3, 1.4, etc.)?
            <hint>
            It is expected that if your module runs on 1.x that it will run 
            on 1.x+1 if no, state that please. Also describe here cases where
            you run different code on different versions of JRE and why.
            </hint>
        </question>
-->
 <answer id="dep-jre">
  <p>
   Runs of JRE.
  </p>
 </answer>



<!--
        <question id="dep-jrejdk" when="final">
            Do you require the JDK or is the JRE enough?
        </question>
-->
 <answer id="dep-jrejdk">
  <p>
   No need for JDK.
  </p>
 </answer>



<!--
        <question id="dep-nb" when="init">
            What other NetBeans projects and modules does this one depend on?
            <hint>
            Depending on other NetBeans projects influnces the ability of
            users of your work to customize their own branded version of
            NetBeans by enabling and disabling some modules. Too
            much dependencies restrict this kind of customization. If that
            is your case, then you may want to split your functionality into
            pieces of autoload, eager and regular modules which can be
            enabled independently. Usually the answer to this question
            is generated from your <code>project.xml</code> file, but
            if it is not guessed correctly, you can suppress it by
            specifying &lt;defaultanswer generate="none"/&gt; and
            write here your own. Please describe such projects as imported APIs using
            the <code>&lt;api name="identification" type="import or export" category="stable" url="where is the description" /&gt;</code>.
            By doing this information gets listed in the summary page of your
            javadoc.
            </hint>
        </question>
-->
 <answer id="dep-nb">
  <defaultanswer generate='here' />
 </answer>



<!--
        <question id="dep-non-nb" when="init">
            What other projects outside NetBeans does this one depend on?
            
            <hint>
            Depending on 3rd party libraries is always problematic,
            especially if they are not open source, as that complicates
            the licensing scheme of NetBeans. Please enumerate your
            external dependencies here, so it is correctly understood since
            the begining what are the legal implications of your project.
            Also please note that
            some non-NetBeans projects are packaged as NetBeans modules
            (see <a href="http://libs.netbeans.org/">libraries</a>) and
            it is preferred to use this approach when more modules may
            depend and share such third-party libraries.
            </hint>
        </question>
-->
 <answer id="dep-non-nb">
  <p>
   XXX no answer for dep-non-nb
  </p>
 </answer>



<!--
        <question id="dep-platform" when="init">
            On which platforms does your module run? Does it run in the same
            way on each?
            <hint>
            If you plan any dependency on OS or any usage of native code,
            please describe why you are doing so and describe how you envision
            to enforce the portability of your code.
            Please note that there is a support for <a href="http://www.netbeans.org/download/dev/javadoc/org-openide-modules/org/openide/modules/doc-files/api.html#how-os-specific">OS conditionally
            enabled modules</a> which together with autoload/eager modules
            can allow you to enable to provide the best OS aware support
            on certain OSes while providing compatibility bridge on the not
            supported ones.
            Also please list the supported
            OSes/HW platforms and mentioned the lovest version of JDK required
            for your project to run on. Also state whether JRE is enough or
            you really need JDK.
            </hint>
        </question>
-->
 <answer id="dep-platform">
  <p>
   XXX no answer for dep-platform
  </p>
 </answer>



<!--
        <question id="deploy-dependencies" when="final">
            What do other modules need to do to declare a dependency on this one,
            in addition to or instead of the normal module dependency declaration
            (e.g. tokens to require)?
            <hint>
                Provide a sample of the actual lines you would add to a module manifest
                to declare a dependency, for example OpenIDE-Module-Requires: some.token.
                If other modules should not depend on this module, or should just use a
                simple regular module dependency, you can just answer "nothing". If you
                intentionally expose a semistable API to clients using implementation
                dependencies, you should mention that here (but there is no need to give
                an example of usage).
            </hint>
        </question>
-->
 <answer id="deploy-dependencies">
  <p>
   You modules can use the <code>AutoUpdateUI</code> API directly (of course
   you almost certainly need also <a href="@org-netbeans-modules-autoupdate-services@/architecture-summary.html">
   Autoudate Services</a>), just be aware that this module comes with a UI.
   It is not always practical to depend on modules that provide a UI from 
   low level infrastructure modules - if that is your case, consider separating
   calls to <code>AutoUpdateUI</code> into separate 
   <a href="@org-openide-modules@/org/openide/modules/doc-files/api.html#enablement">bridge module</a>.
  </p>
 </answer>



<!--
        <question id="deploy-jar" when="impl">
            Do you deploy just module JAR file(s) or other files as well?
            <hint>
            Usually a module consist of one JAR file (perhaps with Class-Path
            extensions) and also a configuration file that enables it. If you
            have any other files, use
            &lt;api group="java.io.File" name="yourname" type="export" category="friend"&gt;...&lt;/api&gt;
            to define the location, name and stability of your files (of course
            changing "yourname" and "friend" to suit your needs).
            
            If it uses more than one JAR, describe where they are located, how
            they refer to each other. 
            If it consist of module JAR(s) and other files, please describe
            what is their purpose, why other files are necessary. Please 
            make sure that installation/uninstallation leaves the system 
            in state as it was before installation.
            </hint>
        </question>
-->
 <answer id="deploy-jar">
  <p>
   XXX no answer for deploy-jar
  </p>
 </answer>



<!--
        <question id="deploy-nbm" when="impl">
            Can you deploy an NBM via the Update Center?
            <hint>
            If not why?
            </hint>
        </question>
-->
 <answer id="deploy-nbm">
  <p>
   XXX no answer for deploy-nbm
  </p>
 </answer>



<!--
        <question id="deploy-packages" when="init">
            Are packages of your module made inaccessible by not declaring them
            public?
            
            <hint>
            By default NetBeans build harness treats all packages are private.
            If you export some of them - either as public or friend packages,
            you should have a reason. If the reason is described elsewhere
            in this document, you can ignore this question.
            </hint>
        </question>
-->
 <answer id="deploy-packages">
  <p>
   XXX no answer for deploy-packages
  </p>
 </answer>



<!--
        <question id="deploy-shared" when="final">
            Do you need to be installed in the shared location only, or in the user directory only,
            or can your module be installed anywhere?
            <hint>
            Installation location shall not matter, if it does explain why.
            Consider also whether <code>InstalledFileLocator</code> can help.
            </hint>
        </question>
-->
 <answer id="deploy-shared">
  <p>
   XXX no answer for deploy-shared
  </p>
 </answer>



<!--
        <question id="exec-ant-tasks" when="impl">
            Do you define or register any ant tasks that other can use?
            
            <hint>
            If you provide an ant task that users can use, you need to be very
            careful about its syntax and behaviour, as it most likely forms an
	          API for end users and as there is a lot of end users, their reaction
            when such API gets broken can be pretty strong.
            </hint>
        </question>
-->
 <answer id="exec-ant-tasks">
  <p>
   XXX no answer for exec-ant-tasks
  </p>
 </answer>



<!--
        <question id="exec-classloader" when="impl">
            Does your code create its own class loader(s)?
            <hint>
            A bit unusual. Please explain why and what for.
            </hint>
        </question>
-->
 <answer id="exec-classloader">
  <p>
   XXX no answer for exec-classloader
  </p>
 </answer>



<!--
        <question id="exec-component" when="impl">
            Is execution of your code influenced by any (string) property
            of any of your components?
            
            <hint>
            Often <code>JComponent.getClientProperty</code>, <code>Action.getValue</code>
            or <code>PropertyDescriptor.getValue</code>, etc. are used to influence
            a behavior of some code. This of course forms an interface that should
            be documented. Also if one depends on some interface that an object
            implements (<code>component instanceof Runnable</code>) that forms an
            API as well.
            </hint>
        </question>
-->
 <answer id="exec-component">
  <p>
   XXX no answer for exec-component
  </p>
 </answer>



<!--
        <question id="exec-introspection" when="impl">
            Does your module use any kind of runtime type information (<code>instanceof</code>,
            work with <code>java.lang.Class</code>, etc.)?
            <hint>
            Check for cases when you have an object of type A and you also
            expect it to (possibly) be of type B and do some special action. That
            should be documented. The same applies on operations in meta-level
            (Class.isInstance(...), Class.isAssignableFrom(...), etc.).
            </hint>
        </question>
-->
 <answer id="exec-introspection">
  <p>
   XXX no answer for exec-introspection
  </p>
 </answer>



<!--
        <question id="exec-privateaccess" when="final">
            Are you aware of any other parts of the system calling some of 
            your methods by reflection?
            <hint>
            If so, describe the "contract" as an API. Likely private or friend one, but
            still API and consider rewrite of it.
            </hint>
        </question>
-->
 <answer id="exec-privateaccess">
  <p>
   XXX no answer for exec-privateaccess
  </p>
 </answer>



<!--
        <question id="exec-process" when="impl">
            Do you execute an external process from your module? How do you ensure
            that the result is the same on different platforms? Do you parse output?
            Do you depend on result code?
            <hint>
            If you feed an input, parse the output please declare that as an API.
            </hint>
        </question>
-->
 <answer id="exec-process">
  <p>
   XXX no answer for exec-process
  </p>
 </answer>



<!--
        <question id="exec-property" when="impl">
            Is execution of your code influenced by any environment or
            Java system (<code>System.getProperty</code>) property?
            On a similar note, is there something interesting that you
            pass to <code>java.util.logging.Logger</code>? Or do you observe
            what others log?
            <hint>
            If there is a property that can change the behavior of your 
            code, somebody will likely use it. You should describe what it does 
            and the <a href="http://openide.netbeans.org/tutorial/api-design.html#life">stability category</a>
            of this API. You may use
            <pre>
                &lt;api type="export" group="property" name="id" category="private" url="http://..."&gt;
                    description of the property, where it is used, what it influence, etc.
                &lt;/api&gt;            
            </pre>
            </hint>
        </question>
-->
 <answer id="exec-property">
  <p>
   XXX no answer for exec-property
  </p>
 </answer>



<!--
        <question id="exec-reflection" when="impl">
            Does your code use Java Reflection to execute other code?
            <hint>
            This usually indicates a missing or insufficient API in the other
            part of the system. If the other side is not aware of your dependency
            this contract can be easily broken.
            </hint>
        </question>
-->
 <answer id="exec-reflection">
  <p>
   XXX no answer for exec-reflection
  </p>
 </answer>



<!--
        <question id="exec-threading" when="init">
            What threading models, if any, does your module adhere to? How the
            project behaves with respect to threading?
            <hint>
                Is your API threadsafe? Can it be accessed from any threads or
                just from some dedicated ones? Any special relation to AWT and
                its Event Dispatch thread? Also
                if your module calls foreign APIs which have a specific threading model,
                indicate how you comply with the requirements for multithreaded access
                (synchronization, mutexes, etc.) applicable to those APIs.
                If your module defines any APIs, or has complex internal structures
                that might be used from multiple threads, declare how you protect
                data against concurrent access, race conditions, deadlocks, etc.,
                and whether such rules are enforced by runtime warnings, errors, assertions, etc.
                Examples: a class might be non-thread-safe (like Java Collections); might
                be fully thread-safe (internal locking); might require access through a mutex
                (and may or may not automatically acquire that mutex on behalf of a client method);
                might be able to run only in the event queue; etc.
                Also describe when any events are fired: synchronously, asynchronously, etc.
                Ideas: <a href="http://core.netbeans.org/proposals/threading/index.html#recommendations">Threading Recommendations</a> (in progress)
            </hint>
        </question>
-->
 <answer id="exec-threading">
  <p>
   XXX no answer for exec-threading
  </p>
 </answer>



<!--
        <question id="format-clipboard" when="impl">
            Which data flavors (if any) does your code read from or insert to
            the clipboard (by access to clipboard on means calling methods on <code>java.awt.datatransfer.Transferable</code>?
            
            <hint>
            Often Node's deal with clipboard by usage of <code>Node.clipboardCopy, Node.clipboardCut and Node.pasteTypes</code>.
            Check your code for overriding these methods.
            </hint>
        </question>
-->
 <answer id="format-clipboard">
  <p>
   XXX no answer for format-clipboard
  </p>
 </answer>



<!--
        <question id="format-dnd" when="impl">
            Which protocols (if any) does your code understand during Drag &amp; Drop?
            <hint>
            Often Node's deal with clipboard by usage of <code>Node.drag, Node.getDropType</code>. 
            Check your code for overriding these methods. Btw. if they are not overridden, they
            by default delegate to <code>Node.clipboardCopy, Node.clipboardCut and Node.pasteTypes</code>.
            </hint>
        </question>
-->
 <answer id="format-dnd">
  <p>
   XXX no answer for format-dnd
  </p>
 </answer>



<!--
        <question id="format-types" when="impl">
            Which protocols and file formats (if any) does your module read or write on disk,
            or transmit or receive over the network? Do you generate an ant build script?
            Can it be edited and modified? 
            
            <hint>
            <p>
            Files can be read and written by other programs, modules and users. If they influence
            your behaviour, make sure you either document the format or claim that it is a private
            api (using the &lt;api&gt; tag). 
            </p>
            
            <p>
            If you generate an ant build file, this is very likely going to be seen by end users and
            they will be attempted to edit it. You should be ready for that and provide here a link
            to documentation that you have for such purposes and also describe how you are going to
            understand such files during next release, when you (very likely) slightly change the 
            format.
            </p>
            </hint>
        </question>
-->
 <answer id="format-types">
  <p>
   XXX no answer for format-types
  </p>
 </answer>



<!--
        <question id="lookup-lookup" when="init">
            Does your module use <code>org.openide.util.Lookup</code>
            or any similar technology to find any components to communicate with? Which ones?
            
            <hint>
            NetBeans is build around a generic registry of services called
            lookup. It is preferable to use it for registration and discovery
            if possible. See
            <a href="http://www.netbeans.org/download/dev/javadoc/org-openide-util/org/openide/util/lookup/doc-files/index.html">
            The Solution to Comunication Between Components
            </a>. If you do not plan to use lookup and insist usage
            of other solution, then please describe why it is not working for
            you.
            <br/>
            When filling the final version of your arch document, please
            describe the interfaces you are searching for, where 
            are defined, whether you are searching for just one or more of them,
            if the order is important, etc. Also classify the stability of such
            API contract. Use &lt;api group=&amp;lookup&amp; /&gt; tag, so
            your information gets listed in the summary page of your javadoc.
            </hint>
        </question>
-->
 <answer id="lookup-lookup">
  <p>
   XXX no answer for lookup-lookup
  </p>
 </answer>



<!--
        <question id="lookup-register" when="final">
            Do you register anything into lookup for other code to find?
            <hint>
            Do you register using layer file or using a declarative annotation such as <code>@ServiceProvider</code>?
            Who is supposed to find your component?
            </hint>
        </question>
-->
 <answer id="lookup-register">
  <p>
   XXX no answer for lookup-register
  </p>
 </answer>



<!--
        <question id="lookup-remove" when="final">
            Do you remove entries of other modules from lookup?
            <hint>
            Why? Of course, that is possible, but it can be dangerous. Is the module
            your are masking resource from aware of what you are doing?
            </hint>
        </question>
-->
 <answer id="lookup-remove">
  <p>
   XXX no answer for lookup-remove
  </p>
 </answer>



<!--
        <question id="perf-exit" when="final">
            Does your module run any code on exit?
        </question>
-->
 <answer id="perf-exit">
  <p>
   XXX no answer for perf-exit
  </p>
 </answer>



<!--
        <question id="perf-huge_dialogs" when="final">
            Does your module contain any dialogs or wizards with a large number of
            GUI controls such as combo boxes, lists, trees, or text areas?
        </question>
-->
 <answer id="perf-huge_dialogs">
  <p>
   XXX no answer for perf-huge_dialogs
  </p>
 </answer>



<!--
        <question id="perf-limit" when="init">
            Are there any hard-coded or practical limits in the number or size of
            elements your code can handle?
            <hint>
                Most of algorithms have increasing memory and speed complexity
                with respect to size of data they operate on. What is the critical
                part of your project that can be seen as a bottleneck with
                respect to speed or required memory? What are the practical
                sizes of data you tested your project with? What is your estimate
                of potential size of data that would cause visible performance
                problems? Is there some kind of check to detect such situation
                and prevent "hard" crashes - for example the CloneableEditorSupport
                checks for size of a file to be opened in editor
                and if it is larger than 1Mb it shows a dialog giving the
                user the right to decide - e.g. to cancel or commit suicide.
            </hint>
        </question>
-->
 <answer id="perf-limit">
  <p>
   XXX no answer for perf-limit
  </p>
 </answer>



<!--
        <question id="perf-mem" when="final">
            How much memory does your component consume? Estimate
            with a relation to the number of windows, etc.
        </question>
-->
 <answer id="perf-mem">
  <p>
   XXX no answer for perf-mem
  </p>
 </answer>



<!--
        <question id="perf-menus" when="final">
            Does your module use dynamically updated context menus, or
            context-sensitive actions with complicated and slow enablement logic?
            <hint>
                If you do a lot of tricks when adding actions to regular or context menus, you can significantly
                slow down display of the menu, even when the user is not using your action. Pay attention to
                actions you add to the main menu bar, and to context menus of foreign nodes or components. If
                the action is conditionally enabled, or changes its display dynamically, you need to check the
                impact on performance. In some cases it may be more appropriate to make a simple action that is
                always enabled but does more detailed checks in a dialog if it is actually run.
            </hint>
        </question>
-->
 <answer id="perf-menus">
  <p>
   XXX no answer for perf-menus
  </p>
 </answer>



<!--
        <question id="perf-progress" when="final">
            Does your module execute any long-running tasks?
            
            <hint>Long running tasks should never block 
            AWT thread as it badly hurts the UI
            <a href="http://performance.netbeans.org/responsiveness/issues.html">
            responsiveness</a>.
            Tasks like connecting over
            network, computing huge amount of data, compilation
            be done asynchronously (for example
            using <code>RequestProcessor</code>), definitively it should 
            not block AWT thread.
            </hint>
        </question>
-->
 <answer id="perf-progress">
  <p>
   XXX no answer for perf-progress
  </p>
 </answer>



<!--
        <question id="perf-scale" when="init">
            Which external criteria influence the performance of your
            program (size of file in editor, number of files in menu, 
            in source directory, etc.) and how well your code scales?
            <hint>
            Please include some estimates, there are other more detailed 
            questions to answer in later phases of implementation. 
            </hint>
        </question>
-->
 <answer id="perf-scale">
  <p>
   XXX no answer for perf-scale
  </p>
 </answer>



<!--
        <question id="perf-spi" when="init">
            How the performance of the plugged in code will be enforced?
            <hint>
            If you allow foreign code to be plugged into your own module, how
            do you enforce that it will behave correctly and quickly and will not
            negatively influence the performance of your own module?
            </hint>
        </question>
-->
 <answer id="perf-spi">
  <p>
   XXX no answer for perf-spi
  </p>
 </answer>



<!--
        <question id="perf-startup" when="final">
            Does your module run any code on startup?
        </question>
-->
 <answer id="perf-startup">
  <p>
   XXX no answer for perf-startup
  </p>
 </answer>



<!--
        <question id="perf-wakeup" when="final">
            Does any piece of your code wake up periodically and do something
            even when the system is otherwise idle (no user interaction)?
        </question>
-->
 <answer id="perf-wakeup">
  <p>
   XXX no answer for perf-wakeup
  </p>
 </answer>



<!--
        <question id="resources-file" when="final">
            Does your module use <code>java.io.File</code> directly?
            
            <hint>
            NetBeans provide a logical wrapper over plain files called 
            <code>org.openide.filesystems.FileObject</code> that
            provides uniform access to such resources and is the preferred
            way that should be used. But of course there can be situations when
            this is not suitable.
            </hint>
        </question>
-->
 <answer id="resources-file">
  <p>
   XXX no answer for resources-file
  </p>
 </answer>



<!--
        <question id="resources-layer" when="final">
            Does your module provide own layer? Does it create any files or
            folders in it? What it is trying to communicate by that and with which 
            components?
            
            <hint>
            NetBeans allows automatic and declarative installation of resources 
            by module layers. Module register files into appropriate places
            and other components use that information to perform their task
            (build menu, toolbar, window layout, list of templates, set of
            options, etc.). 
            </hint>
        </question>
-->
 <answer id="resources-layer">
  <p>
   XXX no answer for resources-layer
  </p>
 </answer>



<!--
        <question id="resources-mask" when="final">
            Does your module mask/hide/override any resources provided by other modules in
            their layers?
            
            <hint>
            If you mask a file provided by another module, you probably depend
            on that and do not want the other module to (for example) change
            the file's name. That module shall thus make that file available as an API
            of some stability category.
            </hint>
        </question>
-->
 <answer id="resources-mask">
  <p>
   XXX no answer for resources-mask
  </p>
 </answer>



<!--
        <question id="resources-preferences" when="final">
            Does your module uses preferences via Preferences API? Does your module use NbPreferences or
            or regular JDK Preferences ? Does it read, write or both ? 
            Does it share preferences with other modules ? If so, then why ?
            <hint>
                You may use
                    &lt;api type="export" group="preferences"
                    name="preference node name" category="private"&gt;
                    description of individual keys, where it is used, what it
                    influences, whether the module reads/write it, etc.
                    &lt;/api&gt;
                Due to XML ID restrictions, rather than /org/netbeans/modules/foo give the "name" as org.netbeans.modules.foo.
                Note that if you use NbPreferences this name will then be the same as the code name base of the module.
            </hint>
        </question>
-->
 <answer id="resources-preferences">
  <p>
   XXX no answer for resources-preferences
  </p>
 </answer>



<!--
        <question id="resources-read" when="final">
            Does your module read any resources from layers? For what purpose?
            
            <hint>
            As this is some kind of intermodule dependency, it is a kind of API.
            Please describe it and classify according to 
            <a href="http://openide.netbeans.org/tutorial/api-design.html#categories">
            common stability categories</a>.
            </hint>
        </question>
-->
 <answer id="resources-read">
  <p>
   XXX no answer for resources-read
  </p>
 </answer>



<!--
        <question id="security-grant" when="final">
            Does your code grant additional rights to some other code?
            <hint>Avoid using a class loader that adds extra
            permissions to loaded code unless really necessary.
            Also note that your API implementation
            can also expose unneeded permissions to enemy code by
            calling AccessController.doPrivileged().</hint>
        </question>
-->
 <answer id="security-grant">
  <p>
   XXX no answer for security-grant
  </p>
 </answer>



<!--
        <question id="security-policy" when="final">
            Does your functionality require modifications to the standard policy file?
            <hint>Your code might pass control to third-party code not
            coming from trusted domains. This could be code downloaded over the
            network or code coming from libraries that are not bundled
            with NetBeans. Which permissions need to be granted to which domains?</hint>
        </question>
-->
 <answer id="security-policy">
  <p>
   XXX no answer for security-policy
  </p>
 </answer>

</api-answers>

Lines 3-8 Link Here

(-)a/autoupdate.ui/manifest.mf (-1 / +1 lines)
3	OpenIDE-Module-Install: org/netbeans/modules/autoupdate/ui/actions/Installer.class	3	OpenIDE-Module-Install: org/netbeans/modules/autoupdate/ui/actions/Installer.class
4	OpenIDE-Module-Layer: org/netbeans/modules/autoupdate/ui/resources/layer.xml	4	OpenIDE-Module-Layer: org/netbeans/modules/autoupdate/ui/resources/layer.xml
5	OpenIDE-Module-Localizing-Bundle: org/netbeans/modules/autoupdate/ui/resources/Bundle.properties	5	OpenIDE-Module-Localizing-Bundle: org/netbeans/modules/autoupdate/ui/resources/Bundle.properties
6	OpenIDE-Module-Specification-Version: 1.19	6	OpenIDE-Module-Specification-Version: 1.20
7	AutoUpdate-Show-In-Client: false	7	AutoUpdate-Show-In-Client: false
8	AutoUpdate-Essential-Module: true	8	AutoUpdate-Essential-Module: true

Lines 9-11 Link Here

(-)a/autoupdate.ui/nbproject/project.properties (+3 lines)
9		9
10	test.config.working.includes=\	10	test.config.working.includes=\
11	org/netbeans/test/autoupdate/Autoupdate.class	11	org/netbeans/test/autoupdate/Autoupdate.class
		12
		13	javadoc.arch=${basedir}/arch.xml
		14	javadoc.apichanges=${basedir}/apichanges.xml




                    </test-dependency>
                </test-type>
            </test-dependencies>
            <public-packages>
                <friend>com.microchip.mplab.nbide.embedded</friend>
                <friend>com.sun.tools.dlight.tools.customizer</friend>
                <friend>org.netbeans.modules.autoupdate.pluginimporter</friend>
                <friend>org.netbeans.modules.cnd.toolchain</friend>
                <friend>org.netbeans.modules.maven.junit</friend>
                <package>org.netbeans.modules.autoupdate.ui.api</package>
            </public-packages>
        </data>
    </configuration>
</project>




import org.netbeans.api.autoupdate.InstallSupport;
import org.netbeans.api.autoupdate.OperationContainer;
import org.netbeans.api.autoupdate.OperationContainer.OperationInfo;
import org.netbeans.api.autoupdate.UpdateManager;
import org.netbeans.modules.autoupdate.ui.wizards.InstallUnitWizard;
import org.netbeans.modules.autoupdate.ui.wizards.InstallUnitWizardModel;
import org.netbeans.modules.autoupdate.ui.wizards.OperationWizardModel.OperationType;

/** Access to UI features of PluginManager that can be useful in other modules
 * as well. 
 * @since 1.20
 * 
 * @author Jirka Rechtacek
 */
public final class PluginManager {
    private PluginManager() {
    private static Runnable toRun = null;
    public static void show () {
        if (p == null) {
            p = new PluginManagerAction ();
        }
        p.performAction ();
    }

    /** Open standard dialog for installing set of modules. Shows it to the user,
     * asks for confirmation, license acceptance, etc. The whole operation requires
     * AWT dispatch thread access (to show the dialog) and blocks 
     * (until the user clicks through), so either call from AWT dispatch thread
     * directly, or be sure you hold no locks and block no progress of other
     * threads to avoid deadlocks.
<pre>
{@link OperationContainer}<InstallSupport> container = OperationContainer.createForInstall();
for ({@link UpdateUnit} u : {@link UpdateManager#getUpdateUnits(org.netbeans.api.autoupdate.UpdateManager.TYPE[]) UpdateManager.getDefault().getUpdateUnits(UpdateManager.TYPE.MODULE)}) {
    if (u.getCodeName().matches("org.my.favorite.module")) {
        if (u.getAvailableUpdates().isEmpty()) {
            continue;
        }
        container.add(u.getAvailableUpdates().get(0));
    }
}
PluginManager.openInstallWizard(container);
</pre>
     * 
     * @param container the container with list of modules for install
     * @return true if all the requested modules were successfullly installed, 
     *    false otherwise.
     */
    public static boolean openInstallWizard(OperationContainer<InstallSupport> container) {
        if (container == null) {
            throw new IllegalArgumentException ("OperationContainer cannot be null."); // NOI18N
        }
        List<OperationContainer.OperationInfo<InstallSupport>> all = container.listAll ();
        if (all.isEmpty ()) {
            throw new IllegalArgumentException ("OperationContainer cannot be empty."); // NOI18N
        }
        List<OperationContainer.OperationInfo<InstallSupport>> invalid = container.listInvalid();
        if (! invalid.isEmpty ()) {
            throw new IllegalArgumentException ("OperationContainer cannot contain invalid elements but " + invalid); // NOI18N
        }
        OperationInfo<InstallSupport> info = all.get (0);
        OperationType doOperation = info.getUpdateUnit ().getInstalled () == null ? OperationType.INSTALL : OperationType.UPDATE;
        return new InstallUnitWizard ().invokeWizard (new InstallUnitWizardModel (doOperation, container));
    }
}

Lines 101-106 Link Here

(-)a/nbbuild/build.properties (+1 lines)
101	config.javadoc.stable=\	101	config.javadoc.stable=\
102	api.annotations.common,\	102	api.annotations.common,\
103	autoupdate.services,\	103	autoupdate.services,\
		104	autoupdate.ui,\
104	core.ide,\	105	core.ide,\
105	openide.util,\	106	openide.util,\
106	openide.util.lookup,\	107	openide.util.lookup,\

Lines 202-204 Link Here

(-)a/nbbuild/javadoctools/links.xml (+1 lines)
202	<link href="${javadoc.docs.org-netbeans-modules-dlight-nativeexecution}" offline="true" packagelistloc="${netbeans.javadoc.dir}/org-netbeans-modules-dlight-nativeexecution"/>	202	<link href="${javadoc.docs.org-netbeans-modules-dlight-nativeexecution}" offline="true" packagelistloc="${netbeans.javadoc.dir}/org-netbeans-modules-dlight-nativeexecution"/>
203	<link href="${javadoc.docs.org-netbeans-core-netigso}" offline="true" packagelistloc="${netbeans.javadoc.dir}/org-netbeans-core-netigso"/>	203	<link href="${javadoc.docs.org-netbeans-core-netigso}" offline="true" packagelistloc="${netbeans.javadoc.dir}/org-netbeans-core-netigso"/>
204	<link href="${javadoc.docs.org-netbeans-modules-parsing-lucene}" offline="true" packagelistloc="${netbeans.javadoc.dir}/org-netbeans-modules-parsing-lucene"/>	204	<link href="${javadoc.docs.org-netbeans-modules-parsing-lucene}" offline="true" packagelistloc="${netbeans.javadoc.dir}/org-netbeans-modules-parsing-lucene"/>
		205	<link href="${javadoc.docs.org-netbeans-modules-autoupdate-ui}" offline="true" packagelistloc="${netbeans.javadoc.dir}/org-netbeans-modules-autoupdate-ui"/>

Lines 200-202 Link Here

(-)a/nbbuild/javadoctools/properties.xml (+1 lines)
200	<property name="javadoc.docs.org-netbeans-modules-dlight-nativeexecution" value="${javadoc.web.root}/org-netbeans-modules-dlight-nativeexecution"/>	200	<property name="javadoc.docs.org-netbeans-modules-dlight-nativeexecution" value="${javadoc.web.root}/org-netbeans-modules-dlight-nativeexecution"/>
201	<property name="javadoc.docs.org-netbeans-core-netigso" value="${javadoc.web.root}/org-netbeans-core-netigso"/>	201	<property name="javadoc.docs.org-netbeans-core-netigso" value="${javadoc.web.root}/org-netbeans-core-netigso"/>
202	<property name="javadoc.docs.org-netbeans-modules-parsing-lucene" value="${javadoc.web.root}/org-netbeans-modules-parsing-lucene"/>	202	<property name="javadoc.docs.org-netbeans-modules-parsing-lucene" value="${javadoc.web.root}/org-netbeans-modules-parsing-lucene"/>
		203	<property name="javadoc.docs.org-netbeans-modules-autoupdate-ui" value="${javadoc.web.root}/org-netbeans-modules-autoupdate-ui"/>

Lines 200-202 Link Here

(-)a/nbbuild/javadoctools/replaces.xml (+1 lines)
200	<replacefilter token="@org-netbeans-modules-dlight-nativeexecution@" value="${javadoc.docs.org-netbeans-modules-dlight-nativeexecution}"/>	200	<replacefilter token="@org-netbeans-modules-dlight-nativeexecution@" value="${javadoc.docs.org-netbeans-modules-dlight-nativeexecution}"/>
201	<replacefilter token="@org-netbeans-core-netigso@" value="${javadoc.docs.org-netbeans-core-netigso}"/>	201	<replacefilter token="@org-netbeans-core-netigso@" value="${javadoc.docs.org-netbeans-core-netigso}"/>
202	<replacefilter token="@org-netbeans-modules-parsing-lucene@" value="${javadoc.docs.org-netbeans-modules-parsing-lucene}"/>	202	<replacefilter token="@org-netbeans-modules-parsing-lucene@" value="${javadoc.docs.org-netbeans-modules-parsing-lucene}"/>
		203	<replacefilter token="@org-netbeans-modules-autoupdate-ui@" value="${javadoc.docs.org-netbeans-modules-autoupdate-ui}"/>

Return to bug 194518

Lines 126-139 Link Here

(-)a/autoupdate.ui/nbproject/project.xml (-7 / +2 lines)
126	</test-dependency>	126	</test-dependency>
127	</test-type>	127	</test-type>
128	</test-dependencies>	128	</test-dependencies>
129	<friend-packages>	129	<public-packages>
130	<friend>com.microchip.mplab.nbide.embedded</friend>
131	<friend>com.sun.tools.dlight.tools.customizer</friend>
132	<friend>org.netbeans.modules.autoupdate.pluginimporter</friend>
133	<friend>org.netbeans.modules.cnd.toolchain</friend>
134	<friend>org.netbeans.modules.maven.junit</friend>
135	<package>org.netbeans.modules.autoupdate.ui.api</package>	130	<package>org.netbeans.modules.autoupdate.ui.api</package>
136	</friend-packages>	131	</public-packages>
137	</data>	132	</data>
138	</configuration>	133	</configuration>
139	</project>	134	</project>

Lines 46-84 Link Here

(-)a/autoupdate.ui/src/org/netbeans/modules/autoupdate/ui/api/PluginManager.java (-15 / +34 lines)
46	import org.netbeans.api.autoupdate.InstallSupport;	46	import org.netbeans.api.autoupdate.InstallSupport;
47	import org.netbeans.api.autoupdate.OperationContainer;	47	import org.netbeans.api.autoupdate.OperationContainer;
48	import org.netbeans.api.autoupdate.OperationContainer.OperationInfo;	48	import org.netbeans.api.autoupdate.OperationContainer.OperationInfo;
49	import org.netbeans.modules.autoupdate.ui.actions.PluginManagerAction;	49	import org.netbeans.api.autoupdate.UpdateManager;
50	import org.netbeans.modules.autoupdate.ui.wizards.InstallUnitWizard;	50	import org.netbeans.modules.autoupdate.ui.wizards.InstallUnitWizard;
51	import org.netbeans.modules.autoupdate.ui.wizards.InstallUnitWizardModel;	51	import org.netbeans.modules.autoupdate.ui.wizards.InstallUnitWizardModel;
52	import org.netbeans.modules.autoupdate.ui.wizards.OperationWizardModel.OperationType;	52	import org.netbeans.modules.autoupdate.ui.wizards.OperationWizardModel.OperationType;
53		53
54	/**	54	/** Access to UI features of PluginManager that can be useful in other modules
55	*	55	* as well.
		56	* @since 1.20
		57	*
56	* @author Jirka Rechtacek	58	* @author Jirka Rechtacek
57	*/	59	*/
58	public final class PluginManager {	60	public final class PluginManager {
59	private static PluginManagerAction p = null;	61	private PluginManager() {
60	private static Runnable toRun = null;
61	public static void show () {
62	if (p == null) {
63	p = new PluginManagerAction ();
64	}
65	p.performAction ();
66	}	62	}
67		63
68	public static boolean openInstallWizard (OperationContainer<InstallSupport> updateContainer) {	64	/** Open standard dialog for installing set of modules. Shows it to the user,
69	if (updateContainer == null) {	65	* asks for confirmation, license acceptance, etc. The whole operation requires
		66	* AWT dispatch thread access (to show the dialog) and blocks
		67	* (until the user clicks through), so either call from AWT dispatch thread
		68	* directly, or be sure you hold no locks and block no progress of other
		69	* threads to avoid deadlocks.
		70	<pre>
		71	{@link OperationContainer}<InstallSupport> container = OperationContainer.createForInstall();
		72	for ({@link UpdateUnit} u : {@link UpdateManager#getUpdateUnits(org.netbeans.api.autoupdate.UpdateManager.TYPE[]) UpdateManager.getDefault().getUpdateUnits(UpdateManager.TYPE.MODULE)}) {
		73	if (u.getCodeName().matches("org.my.favorite.module")) {
		74	if (u.getAvailableUpdates().isEmpty()) {
		75	continue;
		76	}
		77	container.add(u.getAvailableUpdates().get(0));
		78	}
		79	}
		80	PluginManager.openInstallWizard(container);
		81	</pre>
		82	*
		83	* @param container the container with list of modules for install
		84	* @return true if all the requested modules were successfullly installed,
		85	* false otherwise.
		86	*/
		87	public static boolean openInstallWizard(OperationContainer<InstallSupport> container) {
		88	if (container == null) {
70	throw new IllegalArgumentException ("OperationContainer cannot be null."); // NOI18N	89	throw new IllegalArgumentException ("OperationContainer cannot be null."); // NOI18N
71	}	90	}
72	List<OperationContainer.OperationInfo<InstallSupport>> all = updateContainer.listAll ();	91	List<OperationContainer.OperationInfo<InstallSupport>> all = container.listAll ();
73	if (all.isEmpty ()) {	92	if (all.isEmpty ()) {
74	throw new IllegalArgumentException ("OperationContainer cannot be empty."); // NOI18N	93	throw new IllegalArgumentException ("OperationContainer cannot be empty."); // NOI18N
75	}	94	}
76	List<OperationContainer.OperationInfo<InstallSupport>> invalid = updateContainer.listInvalid();	95	List<OperationContainer.OperationInfo<InstallSupport>> invalid = container.listInvalid();
77	if (! invalid.isEmpty ()) {	96	if (! invalid.isEmpty ()) {
78	throw new IllegalArgumentException ("OperationContainer cannot contain invalid elements but " + invalid); // NOI18N	97	throw new IllegalArgumentException ("OperationContainer cannot contain invalid elements but " + invalid); // NOI18N
79	}	98	}
80	OperationInfo<InstallSupport> info = all.get (0);	99	OperationInfo<InstallSupport> info = all.get (0);
81	OperationType doOperation = info.getUpdateUnit ().getInstalled () == null ? OperationType.INSTALL : OperationType.UPDATE;	100	OperationType doOperation = info.getUpdateUnit ().getInstalled () == null ? OperationType.INSTALL : OperationType.UPDATE;
82	return new InstallUnitWizard ().invokeWizard (new InstallUnitWizardModel (doOperation, updateContainer));	101	return new InstallUnitWizard ().invokeWizard (new InstallUnitWizardModel (doOperation, container));
83	}	102	}
84	}	103	}

Added Link Here

(-)b3d334d8c4fb (+114 lines)
1	<?xml version="1.0" encoding="UTF-8"?>
2	<!--
3	DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS HEADER.
4
5	Copyright 1997-2010 Oracle and/or its affiliates. All rights reserved.
6
7	Oracle and Java are registered trademarks of Oracle and/or its affiliates.
8	Other names may be trademarks of their respective owners.
9
10
11	The contents of this file are subject to the terms of either the GNU
12	General Public License Version 2 only ("GPL") or the Common
13	Development and Distribution License("CDDL") (collectively, the
14	"License"). You may not use this file except in compliance with the
15	License. You can obtain a copy of the License at
16	http://www.netbeans.org/cddl-gplv2.html
17	or nbbuild/licenses/CDDL-GPL-2-CP. See the License for the
18	specific language governing permissions and limitations under the
19	License. When distributing the software, include this License Header
20	Notice in each file and include the License file at
21	nbbuild/licenses/CDDL-GPL-2-CP. Oracle designates this
22	particular file as subject to the "Classpath" exception as provided
23	by Oracle in the GPL Version 2 section of the License file that
24	accompanied this code. If applicable, add the following below the
25	License Header, with the fields enclosed by brackets [] replaced by
26	your own identifying information:
27	"Portions Copyrighted [year] [name of copyright owner]"
28
29	Contributor(s):
30
31	The Original Software is NetBeans. The Initial Developer of the Original
32	Software is Sun Microsystems, Inc. Portions Copyright 1997-2008 Sun
33	Microsystems, Inc. All Rights Reserved.
34
35	If you wish your version of this file to be governed by only the CDDL
36	or only the GPL Version 2, indicate your decision by adding
37	"[Contributor] elects to include this software in this distribution
38	under the [CDDL or GPL Version 2] license." If you do not indicate a
39	single choice of license, a recipient has the option to distribute
40	your version of this file under either the CDDL, the GPL Version 2 or
41	to extend the choice of license to its licensees as provided above.
42	However, if you add GPL Version 2 code and therefore, elected the GPL
43	Version 2 license, then the option applies only if the new code is
44	made subject to such option by the copyright holder.
45	-->
46	<?xml-stylesheet type="text/xml" href="../nbbuild/javadoctools/apichanges.xsl"?>
47	<!DOCTYPE apichanges PUBLIC "-//NetBeans//DTD API changes list 1.0//EN" "../nbbuild/javadoctools/apichanges.dtd">
48
49	<apichanges>
50
51	<!-- First, a list of API names you may use: -->
52	<apidefs>
53	<apidef name="ui">Autoupdate UI API</apidef>
54	</apidefs>
55
56	<!-- ACTUAL CHANGES BEGIN HERE: -->
57
58	<changes>
59	<change id="PluginManager.openInstallWizard">
60	<api name="ui"/>
61	<summary>PluginManager.openInstallWizard</summary>
62	<version major="1" minor="20"/>
63	<date day="14" month="2" year="2011"/>
64	<author login="jtulach"/>
65	<compatibility addition="yes" binary="compatible" deletion="no"
66	deprecation="yes" semantic="compatible" source="compatible"
67	/>
68	<description>
69	<p>
70	<code>PluginManager</code> ands its <code>openInstallWizard</code>
71	shows standard UI for installing of selected modules.
72	</p>
73	</description>
74	<class package="org.netbeans.modules.autoupdate.ui.api" name="PluginManager"/>
75	<issue number="194518"/>
76	</change>
77	</changes>
78
79	<!-- Now the surrounding HTML text and document structure: -->
80
81	<htmlcontents>
82	<!--
83
84	NO NO NO NO NO!
85
86	==============> DO NOT EDIT ME! <==============
87
88	AUTOMATICALLY GENERATED FROM APICHANGES.XML, DO NOT EDIT
89
90	SEE projects/projectapi/apichanges.xml
91
92	-->
93	<head>
94	<title>Change History for the Autoupdate UI API</title>
95	<link rel="stylesheet" href="prose.css" type="text/css"/>
96	</head>
97	<body>
98
99	<p class="overviewlink"><a href="overview-summary.html">Overview</a></p>
100
101	<h1>Introduction</h1>
102
103	<p>This document lists changes made to the <a href="@org-netbeans-modules-autoupdate-ui@/index.html">Autoupdate UI API</a>.</p>
104
105	<!-- The actual lists of changes, as summaries and details: -->
106	<hr/>
107	<standard-changelists module-code-name="org.netbeans.modules.autoupdate.ui"/>
108
109	<hr/><p>@FOOTER@</p>
110
111	</body>
112	</htmlcontents>
113
114	</apichanges>