Skip to content
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

Access from a public maven #1

Open
kephale opened this issue Mar 23, 2018 · 4 comments
Open

Access from a public maven #1

kephale opened this issue Mar 23, 2018 · 4 comments

Comments

@kephale
Copy link

kephale commented Mar 23, 2018

@krzysg is there a public location for the MosaicSuite jar that I can get via Maven?

@krzysg
Copy link
Owner

krzysg commented Mar 26, 2018

Hi, sorry for late answer. Currently we do not put MosaicSuite jar in maven. My goal was to first clenaup and maybe split MosaicSutie into serveral subprojects but... I'm working alone and it takes lot of time. If you need that I can try to figure it out how to do that (we have some dependencies to libraries that are no more supported in maven and that's the reason I produce fat library with everything we need)...

@kephale
Copy link
Author

kephale commented Mar 26, 2018

No worries, I know you're busy APRing. I'll use a local repo with the fat jar for now and that will be just fine.

Ideally the subproject jars would be on the imagej maven repo. Even better, they would be ported to imagej-ops, but personally I would be completely happy if I could just get them from any public repo.

@kephale kephale closed this as completed Mar 26, 2018
@kephale
Copy link
Author

kephale commented Dec 9, 2018

Hey @krzysg,

I'm just bumping this question, but no rush.

Perhaps the MosaicSuite jar could be deployed to Maven using the SciJava Travis scripts, while the fat jar is pushed to the update site. Automated update sites are supported now too (although you might have some of the same issues as SciView because of the dependencies).

@kephale kephale reopened this Dec 9, 2018
@krzysg
Copy link
Owner

krzysg commented Jan 10, 2019

Hi Kyle,

since the long history of MosaicSuite it wasn't that obvious what to do - for example we still are using some jar files that technically disappeared from web :-) and we were downloading them from our local MOSAIC maven repo. Anyway I have put them in a source tree (they are small enough to do so).

Latest MosaicSuite is currently in our MOSAIC repository, let me know if this is OK for you (it should be easily accessible from outside). Just update your pom.xml with:

<repository>
    <id>mosaic.public</id>
    <url>http://mosaic.mpi-cbg.de/maven/</url>
</repository>

<dependency>
    <groupId>mosaic</groupId>
    <artifactId>MosaicSuite</artifactId>     
    <version>1.0.16_Full</version>
</dependency>

Just to explain - 1.0.16_Full is exactly same jar as you get from update sites when you update your Fiji/ImageJ and this is fat jar with all dependencies. If you just need jar with mosaic stuff without dependencies use just 1.0.16 as a version.

Hope this help.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants