I downloaded the build-maven.zip and it looks like you guys have already done all the work! This doesn't appear to be in Maven 2's Central repo. Is there a reason for that or do you have your own repo?
Thanks! Matt Marc Guillemot wrote: > > Beein able to run Script.aculo.us is still a major priority of htmlunit. > Daniel Gredler has started work on it so maybe will it come in the near > future... > > Marc. > > > mraible wrote: >> >> I'll try to help out as much as I can. However, HtmlUnit doesn't work >> with the latest version of Script.aculo.us (1.7.0), so it's tempting to >> move to Selenium. ;-) >> >> http://fisheye4.cenqua.com/changelog/appfuse?cs=2324 >> >> Matt >> >> >> Paul King wrote: >>> >>> >>> The other thing which needs to be addressed is resources. >>> We should have dtd's, xsl/css/js/images etc. in the jars and >>> either document or work out how to extract from jars as needed. >>> >>> Cheers, Paul. >>> >>> mraible wrote: >>>> I'll try to look at this build process next week. >>>> >>>> One thing to not is (at first glance), this won't work. The good news >>>> is >>>> it's only because of the filename. They're expected to be named >>>> something >>>> like webtest-build1876-bundle.jar. An even better solution is to >>>> deploy the >>>> artifacts to a URL that can be auto-synced with Maven's central repo - >>>> then >>>> you can publish the download and the Maven JARs at the same time. >>>> >>>> Matt >>>> >>>> >>>> Denis N. Antonioli wrote: >>>>> Hi Matt >>>>> >>>>> As part of the introduction of the pom, I did wrote the code to >>>>> generate a upload bundle for webtest. >>>>> In fact, it was in part upon your impulse: <http://webtest- >>>>> community.canoo.com/jira/browse/WT-93>. ;-) >>>>> >>>>> The complete webtest build process (with the target 'full') generates >>>>> the zip archive deploy/build-maven.zip. >>>>> >>>>> Could you look at it? Is it what you need? >>>>> >>>>> >>>>> One of the reason this bundle was never announced was that I don't >>>>> know what should be done with >>>>> all the dependencies that are not already available through ibiblio, >>>>> either because they are pre-releases >>>>> (like all special htmlunit builds that Marc gives us), or because the >>>>> projects are not published there. >>>>> >>>>> With your help, we may be able to complete this task! >>>>> >>>>> Best >>>>> dna >>>>> >>>>> >>>>> On 3 janv. 07, at 01:39, 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 >>>>>> -- >>>>>> View this message in context: http://www.nabble.com/Maven-2- >>>>>> Dependencies-tf2911044.html#a8133685 >>>>>> Sent from the WebTest mailing list archive at Nabble.com. >>> _______________________________________________ >>> 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#a8855872 Sent from the WebTest mailing list archive at Nabble.com. _______________________________________________ WebTest mailing list [email protected] http://lists.canoo.com/mailman/listinfo/webtest
