-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Change build to use pip #305
Comments
Progress so far on the maven jython plugin to use pip in version 2.0 is here: |
Somewhat related: using pip would potentially be easier if we move to Gradle instead of Maven, as suggested in #112, through the Juthon Gradle plugin. |
The plugin is now working, and is able to pip install all of the dependencies. We have submitted the new version on nexus and are waiting for it to be published online so that we can build jar files without a local development version of the plugin. We expect version 2.0 of the plugin to appear here: https://repo.maven.apache.org/maven2/net/sf/mavenjython/jython-compile-maven-plugin/ And the successfully submitted version 2.0 is listed here: https://oss.sonatype.org/#nexus-search;gav~net.sf.mavenjython~jython-compile-maven-plugin~~~~kw,versionexpand We followed the instructions in #35 to submit the new version, the only thing we had to change was the server we submitted my public key to, as the mit server was down when we tried. I submitted my key to http://keyserver.ubuntu.com:11371 using the online form instead. I generated my armoured public key using the command |
Somehow this works perfectly on Stuart's machine, but doesn't seem to work on Travis or mine one :( It complains about pyyaml and mako, and when commenting those out, it complains about pyoracc's mako dependency. These are errors we had before and were gone when we last tested in Stuart's machine with version 2.0 of the plugin.
After commenting pyyaml out in the pom file:
I can't replicate the plugin working well, so I'll have a look again with Stuart on Wednesday when he's back. |
hi @raquel-ucl , not sure if this is the right place to post my question as I guess it could be also ralated with #302 or #304 Btw, I am trying to use the mavenjython plugin in a Java project that should integrate python libraries. This is the pom of the specific module using mavenjython. The resulting python environment should include/use the Running
These error is raised both on my local set-up and on travis-ci. Have you any suggestion on how to address the problem? |
Hi @gulyx. Your question has to do with the mavenjython plugin itself rather than Nammu. I'm afraid that neither @raquel-ucl or anyone involved with Nammu actively maintain the mavenjython plugin at the moment, however, so it may be hard to get an answer. Perhaps the fix from #304 or another point in the discussion in #302 will help. Sorry we can't give more support with this! |
Currently, the Maven build uses easy_install to download and install the dependencies, but this is proving problematic in some cases (#302, #303). Ideally we can change this to use pip instead, and make the process more straightforward. The mavenjython plugin will address that in version 2.0, when we fix the setuptools import problem and publish it on the Nexus maven repo.
The text was updated successfully, but these errors were encountered: