bump luciphor to 2.1#21375
Conversation
|
ping @oliveralka do you think we java requirements are OK this way? just realized how bad the versioning is now. somehow I chose the date as version. seems impossible to switch to the correct version (2.1) since this is smaller (?) than the date 2019 |
|
I think the java requirements are alright - tested with java8 and java13 on MacOS 10.15.13. Version wise, the only difference is that the 2.1 is using maven, which allows the use of luciphor2 with higher java versions. It seems that the base version of LuciPhor does not have changed directly... (Version: 1.2014Oct10) Edit: There was an update around 2018-06-28, which allowed the use of different precision values for mz and int in the mzML e.g. 64bit m/z and 32bit int, but it seems that the version number was not changed internally.
Should work - I guess! |
|
@BiocondaBot please fetch artifacts |
|
Package(s) built on CircleCI are ready for inspection:
You may also use
Docker image(s) built:
|
|
OK. Maybe we should have a round of testing:
I can test on Linux. Do you have a command / test data in mind? |
|
I uploaded some data here: https://drive.google.com/drive/folders/1Po15DJpuzZVXcHx7VIPNWJC3LvyiJ3hi?usp=sharing Unfortunately, we do not have anything smaller, since there might be a bug when we reindex the attributes in the mzML, which might clash with the java mzML parser used in luciphor2. We are not sure yet. |
|
Works for me (LuciPhor2.1 - using the environment above): |
|
Work. But I get a few warnings in the beginning: |
|
Yes, I saw them as well, but that is probably due to the maven fix - not sure. |
|
@oliveralka This is ok, what this says is one dependency library is "shadowed" by another. That would only (possibly) be a problem in case someone was consuming this as a library from Java JDK 9+ and even then most likely not. But this is just an application, not a library, so it's ok. As long as you don't mind the warnings. |
|
Wonderful, then lets go ahead |
|
@BiocondaBot please add label |
|
@BiocondaBot please merge |
|
I will attempt to upload artifacts and merge this PR. This may take some time, please have patience. |
Describe your pull request here
Please read the guidelines for Bioconda recipes before opening a pull request (PR).
@BiocondaBot please add labelcommand.@bioconda/corein a comment.Please use the following BiocondaBot commands:
Everyone has access to the following BiocondaBot commands, which can be given in a comment:
@BiocondaBot please update@BiocondaBot please add labelplease review & mergelabel.@BiocondaBot please fetch artifactsYou can use this to test packages locally.
For members of the Bioconda project, the following command is also available:
@BiocondaBot please mergeSomeone must approve a PR first!
This reduces CI build time by reusing built artifacts.
Also, the bot watches for comments from non-members that include
@bioconda/<team>and will automatically re-post them to notify the addressed<team>.