Skip to Content
Last modified by Lachlan Deck on 2009/03/24 19:05
From version 22.1
edited by Greg.Brown
on 2009/03/23 13:41
Change comment: There is no comment for this version
To version 32.1
edited by Greg.Brown
on 2009/02/16 09:49
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,35 +1,30 @@
1 -Building instructions are in the file BUILD.txt at the top level of the svn checkout.
1 +Building instructions are in the file BUILD.txt at the top level of the CVS checkout.
2 2  
3 -https:~/~/wonder.svn.sourceforge.net/svnroot/wonder/trunk/Wonder/BUILD.txt
3 +http:~/~/wonder.cvs.sourceforge.net/*checkout*/wonder/Wonder/BUILD.txt?revision=HEAD
4 4  
5 -{{note}}
6 - These Maven built directory frameworks are slightly different than the ant built directory frameworks. For example, the Ajax framework has dependencies on json, and the ant built Ajax.framework includes a jabsorb-1.2.2.jar, whereas the Maven built Ajax.framework does not include this jabsorb-1.2.2.jar. This is, of course, because Maven dependencies are detailed in the pom.xml, and will be pulled in via standard Maven mechanisms. The frameworks are not interchangeable--at least without manipulating dependencies. There are also a different number of frameworks.
7 -
8 -{{/note}}
9 -
10 10  Currently (February 2009) the wonder frameworks, applications, etc, can be built for WebObjects 5.3.x or 5.4.x; the choice is made by using a "profile" which has the value of wo53 or wo54, e.g.:
11 11  
12 12  {{code}}
13 13  
14 - mvn clean install -P wo54
9 + mvn clean install -P wo53
15 15  
16 16  {{/code}}
17 17  
18 -This installs NSJarBundle frameworks for WebObjects 5.4.x into your ,,/.m2/repository, some of which appear in your local repository with the wo54 qualifier:,,
13 +This installs frameworks for WebObjects 5.3.x, some of which appear in your local repository with the wo53 qualifier:
19 19  
20 20  {{code}}
21 21  
22 -./repository/wonder/core/ERExtensions/5.0.0-SNAPSHOT/ERExtensions-5.0.0-SNAPSHOT-wo54.jar
17 +./repository/wonder/core/ERExtensions/5.0.0-SNAPSHOT/ERExtensions-5.0.0-SNAPSHOT-wo53.jar
23 23  
24 24  {{/code}}
25 25  
26 26  and most frameworks are the same for either version of WebObjects, and have nor need any qualifier.
27 27  
28 -To utilize these NSJarBundle frameworks in a Maven Wonder supported project, one must add the correct dependency, and this will depend on which profile you want to link to. This is done by a maven "classifier", which is used to select the correct qualifier. A qualifier is part of the basic artifact coordinate system:
23 +To utilize these frameworks in a wonder supported project, one must add the correct dependency, and this will depend on which profile you want to link to. This is done by a maven "classifier", which is used to select the correct qualifier. A qualifier is part of the basic artifact coordinate system:
29 29  
30 30  <major version>.<minor version>.<incremental version>-<qualifier>
31 31  
32 -For ERExtensions, this is: 5 . 0 . 0-SNAPSHOT - wo54; which selects the correct dependency for WebObjects 5.4.x. In the pom dependencies section this would be
27 +For ERExtensions, this is: 5 . 0 . 0-SNAPSHOT - wo53; which selects the correct dependency for WebObjects 5.3.x. In the pom dependencies section this would be
33 33  
34 34  {{code value="xml"}}
35 35  
... ... @@ -37,13 +37,11 @@
37 37   <groupId>wonder.core</groupId>
38 38   <artifactId>ERExtensions</artifactId>
39 39   <version>5.0.0-SNAPSHOT</version>
40 - <classifier>wo54</classifier>
35 + <classifier>wo53</classifier>
41 41  </dependency>
42 42  
43 43  {{/code}}
44 44  
45 45  
46 -
47 -You should also know that although the WebObjects and Wonder frameworks can work with the NSJarBundle framework jars, Eclipse will instead will use the classes which are pulled into the "target" directory by Maven.
48 48  
49 49  See also the woapplication-archetype ( [[http://wiki.objectstyle.org/confluence/display/WOL/woapplication-archetype]] ) which can create wonder supported applications or frameworks which utilize the maven standard project layout.