The ebuild needs to be updated to build the packages from source
seems to depend on jmi, http://java.sun.com/products/jmi/ . the possibility to download it seems to be very confuse:
If you are building your own implementation of JMI and would like to either certify it as JMI-compliant, or just use the test suite to use for your internal quality assurance, the JMI TCK is available free of charge under a modified SCSL license.
Print out two copies of the license and execute them on behalf of your company. Then send email to firstname.lastname@example.org for details on where to send the executed JMI TCK license agreements.
Once Sun receives the licences, the binaries and source to the JMI TCK, together with one of the jointly-executed licenses, will be sent back to the licensee.
What todo, how can we resolve the dependencie? jmi.jar is needed to argouml.
ok. there are other implementations of jmi available. i tracked down the dependency chain and think it wouldnt be wise to integrate argouml via a source only build into the portage. if we integrate it into the portage with an source based build we have to add the following:
the problem is nsuml and ocl-argo both need xerces-1 and we can't build them on amd64. the bin version of argouml works on amd64. what to do ?
(In reply to comment #2)
> - sablecc.jar
> - dtdarser111.jar
I added gef to the migrated-java-overlay and toolbar is already in the tree. jmi is a bit problem but let's see if I can figure something to that.
Work in progress. *Does not work*. Keyworded -*.
Out of curiosity, what's the status of this?