id="classpath"/>
        </classpath>
        <batchtest todir="${target.reports.dir}">
           <fileset dir="${src.dir}">
              <include name="emailMarketing/AssetLibrary/*.java" />
              <include name="emailMarketing/attributes/*.java" />
              <include name="emailMarketing/contacts/*.java" />
              <include name="emailMarketing/DomainKeys/*.java" />
              <include name="emailMarketing/lists/*.java" />
              <include name="emailMarketing/messages/*.java" />
              <include name="emailMarketing/Segments/*.java" />
              <include name="emailMarketing/UploadContact/*.java" />
              <exclude name="emailMarketing/lists/ListArchive.java"/>
              <exclude name="emailMarketing/messages/MessageCreation.java" />
           </fileset>
        </batchtest>
        <jvmarg value="-Duser=${user}"/>
        <jvmarg value="-Dpw=${pw}"/>
        <jvmarg value="-Dbrowser=${browser}"/>
        <jvmarg value="-Dserver=${server}"/>
        <jvmarg value="-Dopen=${open}"/>
        <jvmarg value="-DtestType=regression"/>
    </junit>
    <junitreport todir="${target.reports.dir}">
        <fileset dir="${target.reports.dir}">
            <include name="TEST-*.xml"/>
        </fileset>
        <report todir="${target.reports.dir}"/>
    </junitreport>
    <fail if="junit.failure" message="Test(s) failed.  See reports!"/>
    <fail if="junit.error" message="Test(s) errored.  See reports!"/>
</target>


A: Take a look at the Ant Retry task.
<target name="myTest1">
    <mkdir dir="${junit.output.dir}" />
    <retry retrycount="3">
      <junit haltonerror="yes" haltonfailure="yes" 
             fork="no" printsummary="withOutAndErr" 
             showoutput="true" tempdir="c:/tmp">
      <formatter type="xml" />
      <test name="MyPackage.myTest1" todir="${junit.output.dir}" />
      <classpath refid="Libs.classpath" />
      <formatter type="brief" usefile="false"/>
      </junit>
    </retry>
</target>


A: Tests should be deterministic, such that errors are reproducible. Hence immediately rerunning a failed test will fail again.
Tests should be independent, i.e. each one should make its own setup (and teardown). With junit, you usually do not have a specific order in which the tests are executed. Hence it is not necessary to rerun test6 for setting up the environment for test7. 
If you want test case prioritization, i.e. start with the failed tests when rerunning tests after a code fix:


*

*http://www.cs.umd.edu/~atif/Teaching/Fall2009/Yuening.pdf gives an overview of some techniques

*Kent Beck's JUnit Max is a great tool, but costs about 100$ per year

*Infinitest is an alternative continuous test runner and open source. It also makes use of test case prioritization, but my experience with that was rather disappointing.


A: Would this work?
http://stefan.samaflost.de/blog/en/Apache/Ant/rerun_tests_that_failed.html

A: JUnit 1.8.0 has a "failure" formatter for junit, which can be used to create a TestCase that just contain the failed tests. See http://ant.apache.org/manual/Tasks/junit.html :
The fourth formatter named failure (since Ant 1.8.0) collects all failing testXXX()
methods and creates a new TestCase which delegates only these failing methods.
The name and the location can be specified via Java System property or Ant property
ant.junit.failureCollector. The value has to point to the directory and the name of
the resulting class (without suffix). It defaults to java-tmp-dir/FailedTests.

Particle as a Service?
Is it possible (both in technical and legal terms) to use the Particle cloud from third-party devices? The full Particle stack would be too complex to reimplement of course but basic functions like Particle.publish(), Particle.variable(), Particle.function(), etc could be done with reasonable effort given that an API documentation is available. A library implementing these functions could allow any (or some, at least) WiFi capable microcontrollers to exploit the Particle cloudâ€™s features, extending the range of available controllers to a much wider spectrum thus attract more users.
There are therefore two types of legal persons: human and non-human. In law, a human person is designated as a natural person (sometimes even a natural person) and a non-human person is designated as a legal person (sometimes as a legal, legal, artificial, legal or fictitious person, in Latin: persona ficta). This film is protected by the copyright laws of the United States and other countries around the world. Country of first publication: United States of America. Any unauthorized exhibition, distribution or reproduction of this film or any part thereof (including the soundtrack) may give rise to civil liability and criminal prosecution. The story, all names, characters and events presented in this production are fictional. No identification with natural persons (living or deceased), premises, buildings and products is envisaged or should be derived. No natural or legal person related to this film has received any payment or anything of value or has entered into an agreement regarding the representation of tobacco products. No animals were injured during the making of this film.
Suppose a client built a house on Alicia`s land. However, the client signed a contract with Bobby, who claimed to be Alicia`s agent, but who, in reality, was not. Although there is no binding contract between Alicia and the client, most courts would allow the client to recover the costs of Alicia`s services and materials in order to avoid an unfair outcome. A court would achieve this by creating a fictitious agreement between the developer and Alicia and making Alicia liable for the cost of the owner`s services and materials. A quasi-contract may allow for less recovery than a tacit contract. An implied contract will construct the entire agreement as provided by the parties, which will allow the party seeking the creation of a tacit contract to be entitled to the expected profits as well as the costs of labor and equipment. A quasi-treaty is created only to the extent necessary to avoid unjustified enrichment. As one court has held, contracts implied by law “are only appeals granted by the Tribunal to enforce reasonable or moral obligations despite the lack of approval by the party sued” (Gray v. Rankin, 721 F. Supp 115 [S.D. Miss. 1989]).
The amount of recovery from an implied contract is usually limited to labor and material costs, as it would be unfair to force a person who does not intend to enter into a contract to pay profits. In such circumstances, the contract of sale at issue may be classified as a transaction which did not have as its object the materiality of the legal consequences which it entailed, that is to say, a fictitious transaction. An obligation that the law establishes in the absence of agreement between the parties. It is alleged by the courts that the undue enrichment that occurs, when one person retains money or benefits that belong fairly to another, existed without judicial protection. Variations sometimes use irony or satire. The movie Return of the Living Dead contains a disclaimer that says, “The events presented in this movie are all true. Names are real names of real people and real organizations. Kurt Vonnegut`s novel Breakfast of Champions contains an abridged version of the disclaimer: “All people, living and dead, are purely random and should not be interpreted,” which concerns the existentialist themes of the novel. Richard Linklater`s 1990 feature film Slacker ends with “This story was based on facts. Any resemblance to fictional events or characters was purely coincidental. Therefore, the main features of a fictional deal are as follows: the film began by stating that “it is about the destruction of an empire. Some characters are still alive – the rest were killed by violence. According to reports, a judge in the MGM case said that this allegation was not only prejudicial to their case, but that their case would be stronger if they had recorded a directly opposite statement that the film was not intended as an accurate depiction of real people or events. [3] Spurred on by the outcome of this case, many studios have begun to include in their films a “fictitious” disclaimer for all people in order to protect themselves from similar legal proceedings.
<issue_start><issue_comment>Title: bug(@vtmn/svelte): problem when importing `@vtmn/svelte` in our Svelte stack 
username_0: <!-- Before submitting an issue, please consult our docs (https://decathlon.design). -->

<!-- Please make sure you are posting an issue pertaining to the Decath