Versions Compared

Old Version 3

changes.mady.by.user Joseph Germuska

Saved on

compared with

New Version 4

changes.mady.by.user Ted Husted

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment:

Update nomenclature

Because WebWork the framework is under active development, these instructions are likely to be out-of-date in specifics.  Hopefully the basic strategies will still apply.

First, if xwork is not available from a froma Maven repo (for example, if it has moved to a SNAPSHOT dependency), then check it out from the CVS repository and run "mvn install" - this gives you the snapshot of XWork as well as the POM for resolving transitive dependencies like oscore.  This may apply to other dependencies which are not on ibiblio, but when I first tried this, xwork was the one with enough transitive dependencies to be hard to manage any other way.

For other dependencies which are not on ibiblio, from the webwork CVS SAF repository checkout (sandbox), run "ant common.jar". This will cause Ivy to fetch the other dependencies you need.

...

Code Block
none
none
mvn install:install-file -DartifactId=dwr -DgroupId=dwr -Dpackaging=jar -Dversion=1.1.3-beta \
    -Dfile=/Users/germuska/.ivy-cache/dwr/dwr/jars/dwr-1.1-beta-3.jar

mvn install:install-file -DartifactId=plexus-container-default -DgroupId=org.codehaus.plexus \
    -Dpackaging=jar -Dversion=1.0-alpha-10-SNAPSHOT \
    -Dfile=/Users/germuska/.ivy-cache/org.codehaus.plexus/plexus-container-default/jars/plexus-container-default-1.0-alpha-10-20060215.222714-5.jar

If you , like me, are not running Java 5.0, then you will also need to install the dom3 APIs.  As far as I we can tell, the compiled JAR is not on any Maven repository. the source for dom3 can be found here: http://ibiblio.org/maven2/xerces/dom3-xml-apis/1.0/dom3-xml-apis-1.0-sources.jar&nbspImage Removed; You can build a jar from it and then put it in your own repository.  After that, I had to edit webwork's pom.xml to point to the dependency -- webwork has there is a comment in the <profiles> section acknowledging the need for this, but presumably it will not be changed until dom3 gets officially loaded as a compiled JAR to some maven repository.  I believe there There should be a way to use Maven2's settings.xml file to do this locally without editing pom.xml, but I we have not had a chance to investigate this yet.

These steps worked for me a week or so ago; the pom has changed since then and I haven't yet had time to rebuildmay change as the  pom changes, but this kind of approach should work.