I don't mind the "kitchen sink" approach since this is a testing framework
and nothing ends up in the final WAR. That being said, it might make sense
to upload different JARs (or maybe just POMs) for different sets of
functionality. For example:
webtest
webtest-pdf
webtest-excel
webtest-email
All of the last 3 would have a dependency on the first one, so you'd still
only need to declare one dependency - unless you wanted multiple pieces of
functionality of course.
Matt
Marc Guillemot wrote:
>
> Hi Matt,
>
> have you had a look at WebTest's POM?
>
> You can reduce it if you just want to use a subset of WebTest
> functionalities. For instance you can remove all pdf stuff if you don't
> want to test pdf documents. The same for Excel documents or applets or
> emails.
>
> Marc.
>
> mraible wrote:
>> Hello all,
>>
>> I've been creating Maven 2 upload bundles for Canoo WebTest periodically
>> over the last several months. For the most part, I've only ever included
>> a
>> dependency on htmlunit, but I've noticed that many more dependencies
>> (oro,
>> log4j, javamail) are needed when running WebTest with the
>> maven-antrun-plugin.
>>
>> <plugin>
>> <artifactId>maven-antrun-plugin</artifactId>
>> <configuration>
>> <tasks>
>> <taskdef resource="webtest_base_relaxed.taskdef">
>> <classpath refid="maven.test.classpath"/>
>> </taskdef>
>> <mkdir dir="target/webtest-data"/>
>> <!-- Delete old results file if it exists -->
>> <delete
>> file="target/webtest-data/web-tests-result.xml"/>
>> <!-- This is so the default will be used if no
>> test
>> case is specified -->
>> <property name="test" value="run-all-tests"/>
>> <echo level="info">Testing
>> '${project.build.finalName}' with locale '${user.language}'</echo>
>> <ant antfile="src/test/resources/web-tests.xml"
>> target="${test}">
>> <property name="user.language"
>> value="${user.language}"/>
>> <property name="webapp.name"
>> value="${project.build.finalName}"/>
>> <property name="host" value="${cargo.host}"/>
>> <property name="port" value="${cargo.port}"/>
>> </ant>
>> </tasks>
>> </configuration>
>> <executions>
>> <execution>
>> <phase>integration-test</phase>
>> <goals>
>> <goal>run</goal>
>> </goals>
>> </execution>
>> </executions>
>> <dependencies>
>> <dependency>
>> <groupId>com.canoo</groupId>
>> <artifactId>webtest</artifactId>
>> <version>${webtest.version}</version>
>> <exclusions>
>> <exclusion>
>> <groupId>javax.xml</groupId>
>> <artifactId>jsr173</artifactId>
>> </exclusion>
>> </exclusions>
>> </dependency>
>> <dependency>
>> <groupId>javax.mail</groupId>
>> <artifactId>mail</artifactId>
>> <version>${javamail.version}</version>
>> </dependency>
>> <dependency>
>> <groupId>log4j</groupId>
>> <artifactId>log4j</artifactId>
>> <version>${log4j.version}</version>
>> </dependency>
>> <dependency>
>> <groupId>oro</groupId>
>> <artifactId>oro</artifactId>
>> <version>${oro.version}</version>
>> </dependency>
>> </dependencies>
>> </plugin>
>>
>> What are the correct set of dependencies (and versions) that should be
>> included for WebTest? I'd like to correct these after the next release
>> so
>> its possible to have a much smaller <dependencies> section.
>>
>> Thanks,
>>
>> Matt
>
> _______________________________________________
> WebTest mailing list
> [email protected]
> http://lists.canoo.com/mailman/listinfo/webtest
>
>
--
View this message in context:
http://www.nabble.com/Maven-2-Dependencies-tf2911044.html#a8458471
Sent from the WebTest mailing list archive at Nabble.com.
_______________________________________________
WebTest mailing list
[email protected]
http://lists.canoo.com/mailman/listinfo/webtest
