On Thu, Feb 26, 2009 at 11:39 AM, Wojtek Janiszewski < [email protected]> wrote:
> Thanks for your reply, I have comments inline: > > ant elder : > >> Great stuff, that all sounds very impresive. A couple of comments in >> line... Problem 1. Erlang binding uses official jinterface library which >> I >> didn't found in official maven repositories. It can be added locally >> to maven repository, but it obviously breaks automation of building >> project. What is your experience for such case? >> >> >> Ideally we'd get it put in the maven repository, the owner may do that if >> we ask. In the mean time create a repository somewhere and define that >> repository in your pom.xml, eg: >> >> <repositories> >> <!-- This is required to work around a bug in the JRuby pom, see >> http://jira.codehaus.org/browse/JRUBY-901 --> >> <repository> >> <id>ant-jruby</id> >> >> <url>http://people.apache.org/~antelder/jruby-repo<http://people.apache.org/%7Eantelder/jruby-repo> >> </url> >> <snapshots> >> <enabled>true</enabled> >> </snapshots> >> </repository> >> </repositories> >> >> We've a repo in SVN that some are using for that - >> https://svn.apache.org/repos/asf/tuscany/maven/ - I'm not sure if the ASF >> infrastructure people really like us using SVN like that though. >> >> > > So I've fixed jinterface dependency to point at temporary repo. I think > moving Erlang code out of sandbox would be a good moment for installing > jinterface library in official maven repository. Who should I contact? Here's the Maven doc on how to get things into the repository: http://maven.apache.org/guides/mini/guide-central-repository-upload.html The main thing is the request needs to come from someone from the domain being used for the Maven groupid, so if jinterface is going to be in something like <groupid>org.erlang</groupId> then someone from there needs to make the upload request. That may or may not be hard to get to happen ;) I don't think that happening should prevent these new Tuscany modules moved from sandbox to trunk though, and if it ends up proving difficult to get jinterface published we could either publish it oursleves in org.apache.tuscany or use the Tuscany svn repsotory as is done for saxon. > > > Problem 2. Testing- Erlang uses Erlang Port Mapper Demon (epmd) to >> register nodes etc. Epmd is standalone, non-java program and Erlang >> binding tests needs it to be launched - it also can break automation >> of building and testing project. I don't feel like rewriting it in >> Java ;) Also having native Erlang nodes would be the best (not >> emulating them by jinterface) and to do that we need to execute >> native erl binary. Any thoughts? >> >> >> Could you use Runtime.getRuntime().exec()? >> > > We could, but in this case user should have epmd installed manually (which > can be done by building Erlang distribution). I suppose we don't want to add > epmd binary (multiple versions for various platforms) to Tuscany > distribution. So maybe reasonable solution would be enabling JUnit testing > if epmd program is available? In this case we could mark it in documentation > (so Erlang user would be informed), and to have it tested all the time we > could install epmd on Tuscany build machine. > Thats sounds ok to me. ...ant
