If your module depends on org.openide.execution > 1.9
or higher
+ there is no need to specify that it also requires an implementation of
+ the API by use of OpenIDE-Module-Requires: org.openide.execution.ExecutionEngine
,
+ this token will be requested automatically by the org.openide.execution
+ module itself.
+
If your module depends on org.openide.io > 1.11
or higher
+ there is no need to specify that it also requires an implementation of
+ the API by use of OpenIDE-Module-Requires: org.openide.windows.IOProvider
,
+ this token will be requested automatically by the org.openide.io
+ module itself.
+
- * Assuming you want to ensure that a real output window implementation is actually
- * installed and enabled, you must require the token org.openide.windows.IOProvider
- * from the module calling this method.
* @return the default instance (never null)
*/
public static IOProvider getDefault() {
@@ -67,7 +63,7 @@
* the output window. Streams for reading/writing can be accessed via
* getters on the returned instance.
*
- * @param name A localized display name for the tab
+ * @param name A localised display name for the tab
* @param newIO if true, a new InputOutput
is returned, else an existing InputOutput
of the same name may be returned
* @return an InputOutput
instance for accessing the new tab
* @see InputOutput
Index: openide/modules/apichanges.xml
===================================================================
RCS file: /shared/data/ccvs/repository/openide/modules/apichanges.xml,v
retrieving revision 1.7
diff -u -r1.7 apichanges.xml
--- openide/modules/apichanges.xml 1 Jul 2006 09:08:52 -0000 1.7
+++ openide/modules/apichanges.xml 18 Jul 2006 12:05:27 -0000
@@ -24,6 +24,22 @@
OpenIDE-Module-Needs: token
which is slightly
+ less restrictive than usual
+ OpenIDE-Module-Requires: token
as
+ explain in the documentation.
+ OpenIDE-Module-Needs
+which is a weaker version of requires as it does not impose any restriction on
+the ordering of module. The OpenIDE-Module-Needs
is useful for
+modules that define some API and require an implementation of it. Just
+specify the need
for an implementation and make other modules depend
+on your module and OpenIDE-Module-Provides
the implementation token.
+Moreover there is also OpenIDE-Module-Recommends
which is even
+weaker version as it creates a conditional dependency - e.g. enables the module
+providing the token only if it is available, however if it is not, no dependency
+is broken.
At the heart of all these tags are the conventions used in the
Index: platform/samples/minicomposer/manifest.mf
===================================================================
RCS file: /shared/data/ccvs/repository/platform/samples/minicomposer/manifest.mf,v
retrieving revision 1.2
diff -u -r1.2 manifest.mf
--- platform/samples/minicomposer/manifest.mf 19 Jul 2005 11:59:24 -0000 1.2
+++ platform/samples/minicomposer/manifest.mf 18 Jul 2006 12:05:42 -0000
@@ -2,7 +2,7 @@
OpenIDE-Module: org.netbeans.examples.modules.minicomposer
OpenIDE-Module-Localizing-Bundle: org/netbeans/examples/modules/minicomposer/resources/Bundle.properties
OpenIDE-Module-Specification-Version: 1.2
-OpenIDE-Module-Requires: org.netbeans.api.javahelp.Help, org.openide.windows.IOProvider
+OpenIDE-Module-Requires: org.netbeans.api.javahelp.Help
OpenIDE-Module-Layer: org/netbeans/examples/modules/minicomposer/resources/layer.xml
Name: org/netbeans/examples/modules/minicomposer/ScoreDataLoader.class
Index: platform/samples/minicomposer/nbproject/project.xml
===================================================================
RCS file: /shared/data/ccvs/repository/platform/samples/minicomposer/nbproject/project.xml,v
retrieving revision 1.3
diff -u -r1.3 project.xml
--- platform/samples/minicomposer/nbproject/project.xml 30 Jun 2006 14:13:03 -0000 1.3
+++ platform/samples/minicomposer/nbproject/project.xml 18 Jul 2006 12:05:42 -0000
@@ -104,7 +104,7 @@