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]
