Why does one package declare another's activity in its own manifest?
<p>As indicated by the tags, this is homework/classwork. (Note that it's really just an in class thing that my instructor can't seem to explain, so I'm turning to the interwebs).</p>

<p>We have an example made up of two apps: Sample1 and Sample2. The point of the example is to show calling into Sample2 from Sample1 using an intent. Sample 2 uses an intent filter to be launched by a certain intent. Here is a snipped from the manifest. </p>

<pre><code>&lt;activity
    android:name=".Sample2"
    android:label="@string/title_activity_Sample02" &gt;
    &lt;intent-filter&gt;
        &lt;action android:name="Sample02.intent.action.Thinger" /&gt;

        &lt;category android:name="android.intent.category.DEFAULT" /&gt;
    &lt;/intent-filter&gt;
&lt;/activity&gt;
</code></pre>

<p>Sample01 invokes this using an intent:</p>

<pre><code>Intent intent = new Intent("Sample02.intent.action.Thinger");
startActivity(intent);
</code></pre>

<p>This works fine, assuming that Sample02 is installed on the target device.</p>

<p>What confuses me is this bit in Sample01's manifest file:</p>

<pre><code>&lt;activity
android:name="com.example.Sample02.Sample02"
&gt;
&lt;/activity&gt;
</code></pre>

<p>I don't understand what this is for. It exists in addition to the  declaration for Sample01 in the same file. Near as I can tell, I can remove it and everything works the same. Anyone know what this about? Thanks.</p>
