Add a short comment explain path dependencies

Author: jonasfj

packages/android_alarm_manager/example/pubspec.yaml

@@ -5,6 +5,11 @@ dependencies:
   flutter:
     sdk: flutter
   android_alarm_manager:
+    # The example app is bundled with the plugin so we use a path dependency on
+    # the parent directory to use the current plugin's version. 
+    # When depending on this package from a real application you should use:
+    #   android_alarm_manager: ^x.y.z
+    # See https://dart.dev/tools/pub/dependencies#version-constraints
     path: ../
   e2e: ^0.2.1
   path_provider: ^1.3.1

packages/android_intent/example/pubspec.yaml

@@ -5,6 +5,11 @@ dependencies:
   flutter:
     sdk: flutter
   android_intent:
+    # The example app is bundled with the plugin so we use a path dependency on
+    # the parent directory to use the current plugin's version. 
+    # When depending on this package from a real application you should use:
+    #   android_intent: ^x.y.z
+    # See https://dart.dev/tools/pub/dependencies#version-constraints
     path: ../
 
 dev_dependencies:
@@ -17,4 +22,4 @@ flutter:
   uses-material-design: true
 
 environment:
-  flutter: ">=1.9.1+hotfix.2 <2.0.0"
+  flutter: ">=1.9.1+hotfix.2 <2.0.0"

packages/battery/example/pubspec.yaml

@@ -5,6 +5,11 @@ dependencies:
   flutter:
     sdk: flutter
   battery:
+    # The example app is bundled with the plugin so we use a path dependency on
+    # the parent directory to use the current plugin's version. 
+    # When depending on this package from a real application you should use:
+    #   battery: ^x.y.z
+    # See https://dart.dev/tools/pub/dependencies#version-constraints
     path: ../
 
 dev_dependencies:

packages/camera/example/pubspec.yaml

@@ -3,6 +3,11 @@ description: Demonstrates how to use the camera plugin.
 
 dependencies:
   camera:
+    # The example app is bundled with the plugin so we use a path dependency on
+    # the parent directory to use the current plugin's version. 
+    # When depending on this package from a real application you should use:
+    #   camera: ^x.y.z
+    # See https://dart.dev/tools/pub/dependencies#version-constraints
     path: ../
   path_provider: ^0.5.0
   flutter:

packages/connectivity/example/pubspec.yaml

@@ -5,8 +5,18 @@ dependencies:
   flutter:
     sdk: flutter
   connectivity:
+    # The example app is bundled with the plugin so we use a path dependency on
+    # the parent directory to use the current plugin's version. 
+    # When depending on this package from a real application you should use:
+    #   connectivity: ^x.y.z
+    # See https://dart.dev/tools/pub/dependencies#version-constraints
     path: ../
   connectivity_macos:
+    # The example app is bundled with the plugin so we use a path dependency on
+    # the parent directory to use the current plugin's version. 
+    # When depending on this package from a real application you should use:
+    #   connectivity_macos: ^x.y.z
+    # See https://dart.dev/tools/pub/dependencies#version-constraints
     path: ../connectivity_macos
 
 dev_dependencies:

packages/device_info/example/pubspec.yaml

@@ -5,6 +5,11 @@ dependencies:
   flutter:
     sdk: flutter
   device_info:
+    # The example app is bundled with the plugin so we use a path dependency on
+    # the parent directory to use the current plugin's version. 
+    # When depending on this package from a real application you should use:
+    #   device_info: ^x.y.z
+    # See https://dart.dev/tools/pub/dependencies#version-constraints
     path: ../
 
 dev_dependencies:

packages/e2e/example/pubspec.yaml

@@ -19,8 +19,18 @@ dev_dependencies:
   flutter_driver:
     sdk: flutter
   e2e:
+    # The example app is bundled with the plugin so we use a path dependency on
+    # the parent directory to use the current plugin's version. 
+    # When depending on this package from a real application you should use:
+    #   e2e: ^x.y.z
+    # See https://dart.dev/tools/pub/dependencies#version-constraints
     path: ../
   e2e_macos:
+    # The example app is bundled with the plugin so we use a path dependency on
+    # the parent directory to use the current plugin's version. 
+    # When depending on this package from a real application you should use:
+    #   e2e_macos: ^x.y.z
+    # See https://dart.dev/tools/pub/dependencies#version-constraints
     path: ../e2e_macos
   test: any
 

packages/espresso/example/pubspec.yaml

@@ -20,6 +20,11 @@ dev_dependencies:
     sdk: flutter
 
   espresso:
+    # The example app is bundled with the plugin so we use a path dependency on
+    # the parent directory to use the current plugin's version. 
+    # When depending on this package from a real application you should use:
+    #   espresso: ^x.y.z
+    # See https://dart.dev/tools/pub/dependencies#version-constraints
     path: ../
 
 # For information on the generic Dart part of this file, see the

packages/flutter_plugin_android_lifecycle/example/pubspec.yaml

@@ -15,6 +15,11 @@ dev_dependencies:
     sdk: flutter
 
   flutter_plugin_android_lifecycle:
+    # The example app is bundled with the plugin so we use a path dependency on
+    # the parent directory to use the current plugin's version. 
+    # When depending on this package from a real application you should use:
+    #   flutter_plugin_android_lifecycle: ^x.y.z
+    # See https://dart.dev/tools/pub/dependencies#version-constraints
     path: ../
 
 flutter:

packages/google_maps_flutter/google_maps_flutter/example/pubspec.yaml

@@ -9,6 +9,11 @@ dependencies:
   # Use with the CupertinoIcons class for iOS style icons.
   cupertino_icons: ^0.1.0
   google_maps_flutter:
+    # The example app is bundled with the plugin so we use a path dependency on
+    # the parent directory to use the current plugin's version. 
+    # When depending on this package from a real application you should use:
+    #   google_maps_flutter: ^x.y.z
+    # See https://dart.dev/tools/pub/dependencies#version-constraints
     path: ../
   flutter_plugin_android_lifecycle: ^1.0.0