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
