Hi Dave, I downloaded the psf and it created the argouml-build project. I tried running the build. It attempts to run the argouml-core-model-mdr build and fails. The error messages indicate that it can't find classes like AssociationRole, Message, and other basic model-related classes.
Any ideas about what I'm doing wrong? Are the default targets (and their dependent targets) building in the wrong order? Also the target that Linus mentioned that cleans up the classpath in the argouml.jar file seems to be missing from the argouml-build build.xml file. Mark On Tue, Nov 4, 2008 at 7:22 AM, Mark Fortner <[EMAIL PROTECTED]> wrote: > Thanks Dave, > I'll give it a try and see what happens. > > Mark > > > On Mon, Nov 3, 2008 at 11:27 AM, Dave Thompson <[EMAIL PROTECTED]> wrote: > >> Hi Mark, >> >> You don't need to download a root build file to get the command line >> build to work. All you need is workspace/argouml-build/, which is >> available from the 'argouml-command-line-build-projectset.psf' project >> settings file, which you can get at: >> http://argouml.tigris.org/psf/ >> >> As far as I know, any build files in the root of the workspace are >> insignificant, and are effectively only a redirect to the build files in >> argouml-build/. >> >> Just import argouml-command-line-build-projectset.psf into the same >> workspace, and you should be fine to launch your command line build from >> workspace/argouml-build/. >> >> The psf files do not need to be downloaded into any particular place. >> They only act as an instruction file telling eclipse what to set up in >> your workspace. You can download them to a temporary directory, or your >> desktop, and then delete them after the import. They are not part of >> the source code. >> >> Hope this helps, >> >> Dave >> >> On Mon, 3 Nov 2008 07:11:06 -0800, "Mark Fortner" <[EMAIL PROTECTED]> >> said: >> > Hi Linus, >> > I think I understand part of what I did wrong. I've been building with >> > Eclipse prior to this. The Eclipse instructions (Section 2.9.3) don't >> > tell >> > you that you need to download the ProjectSet files into a specific >> > subdirectory. Nor do the instructions say that you still need to >> > download a >> > root build file in order to get everything to work in both Eclipse and >> > Ant. >> > >> > Currently my directory structure looks like this: >> > >> > ~/workspace_argo >> > argoprint >> > argouml-app >> > argouml-core-diagrams-sequence2/ >> > argouml-core-infra/ >> > argouml-core-model/ >> > argouml-core-model-euml/ >> > argouml-core-model-mdr/ >> > argouml-core-tools/ >> > >> > It sounds like I'll need to rework the directory structure a little in >> > order >> > to get things to build properly. >> > >> > Thanks, >> > >> > Mark >> > >> > On Sun, Nov 2, 2008 at 2:16 PM, Linus Tolke <[EMAIL PROTECTED]> wrote: >> > >> > > Hello Mark! >> > > >> > > There is a special mechanism populating the classpath attribute and it >> > > is tightly coupled with how the releases are done. >> > > >> > > Because of how the translations are linked into ArgoUML they need to >> > > be on the classpath. Because they are treated like modules and handled >> > > exactly like modules they are built after argouml itself is built. >> > > >> > > To add them on the classpath for the jar in the releases a special >> > > target is used. It is however not available in the Eclipse layout of >> > > the project. The magic is located in /trunk/build.xml in a target >> > > named update-argouml.jar-manifest. This is run after the install >> > > target is run in the argouml project and in all the modules projects. >> > > >> > > If you want to dig into the details of how a release is done, you >> > > could examine the scripts in the argoumlinstaller project (at >> > > http://argoumlinstaller.tigris.org/). >> > > >> > > /Linus >> > > >> > > >> > > 2008/11/1 Mark Fortner <[EMAIL PROTECTED]>: >> > > > I'm working on updating ArgoPrint's build and I noticed that the >> > > argouml-app >> > > > build that ArgoPrint depends on doesn't seem to populate the >> > > argouml.jar's >> > > > manifest. In particular the classpath attribute in the manifest >> file >> > > > doesn't seem to be populated. >> > > > >> > > > When I compared it with the latest release download, I noticed that >> the >> > > > manifest was properly populated. Since the "jar" target is not >> > > populating >> > > > this, I was wondering if someone was producing the releases via an >> > > Eclipse >> > > > JAR export, or through some other approach. >> > > > >> > > > -- >> > > > Mark Fortner >> > > > >> > > > blog: http://feeds.feedburner.com/jroller/ideafactory >> > > > >> > > >> > > --------------------------------------------------------------------- >> > > To unsubscribe, e-mail: [EMAIL PROTECTED] >> > > For additional commands, e-mail: [EMAIL PROTECTED] >> > > >> > > >> > >> > >> > -- >> > Mark Fortner >> > >> > blog: http://feeds.feedburner.com/jroller/ideafactory >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > > -- > Mark Fortner > > blog: http://feeds.feedburner.com/jroller/ideafactory > -- Mark Fortner blog: http://feeds.feedburner.com/jroller/ideafactory
