<div dir="ltr">I'll try to explain the options by going through your list :)<div><br></div><div>1.) Test project's pom.xml - This allows addon versions to be resolved if no version is specified in the test's @AddonDependency annotation. </div>
<div><br></div><div>2.) Addon project's pom.xml - This adds the addon as a dependency to the addon itself, and all addon-dependency rules from the documentation apply: <a href="https://github.com/forge/core#what-scope-should-my-addon-dependencies-be">https://github.com/forge/core#what-scope-should-my-addon-dependencies-be</a></div>
<div><br></div><div>3.) Parent project's pom.xml - This would add the dependency to all sub-projects. You definitely don't want to do this.</div><div><br></div><div>4.) <span style="font-family:arial,sans-serif;font-size:13px">As @AddonDependency annotation of the getDeployment method - </span>This tells the test-harness to deploy the specified addon before running the test case. We should probably renamed this to @AddonDeployment(...). If the version is not specified, it will attempt to resolve against the current project's pom to find the version that is being included by the build. (Allows you to keep tests up to date with the POM more easily.)</div>
<div><br></div><div>5.) <span style="font-size:13px;font-family:arial,sans-serif">As parameter of ShrikWrap's </span><span style="font-size:13px;font-family:arial,sans-serif">addAsAddonDependencies method - </span>This is what actually adds the addon as a dependency of the addon you are bundling (typically the test case itself). It is the equivalent of adding a dependency to the addon/ project's pom.xml file, but for the test case, not the addon.</div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Oct 8, 2013 at 4:53 PM, Ivan St. Ivanov <span dir="ltr"><<a href="mailto:ivan.st.ivanov@gmail.com" target="_blank">ivan.st.ivanov@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi folks,<div><br></div><div>As you might know I am working on the Git tools plugin migration to Forge 2.0 addon. I reached the point of migrating the tests and am trying to understand how to declare the dependencies of the test to the current and to other addons. I see five ways to do that:</div>
<div><br></div><div>1) In the test project's pom.xml</div><div>2) In the addon project's pom.xml</div><div>3) In the parent project's pom.xml</div><div>4) As @AddonDependency annotation of the getDeployment method</div>
<div>5) As parameter of ShrikWrap's addAsAddonDependencies method</div><div><br></div><div>Should I declare all my dependencies in those five places? Or there is a difference between them. I need to understand especially the difference between 4) and 5) and why do we need them both.</div>
<div><br></div><div>Thanks,</div><div>Ivan</div></div>
<br>_______________________________________________<br>
forge-dev mailing list<br>
<a href="mailto:forge-dev@lists.jboss.org">forge-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/forge-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/forge-dev</a><br></blockquote></div><br><br clear="all"><div><br></div>-- <br>Lincoln Baxter, III<br><a href="http://ocpsoft.org" target="_blank">http://ocpsoft.org</a><br>
"Simpler is better."
</div>