Open ahadas opened 4 years ago
Sorry seen this really late.
We may consider renaming the packages for a future release.
This is currently addressed in muCommander by injecting the classes of unix4j into one of our jar files. I realize that if you don't use unix4j with an OSGi framework, this is probably not something you'll get to any time soon. If you're ok with making such a change, I can give it a try
This is currently addressed in muCommander by injecting the classes of unix4j into one of our jar files. I realize that if you don't use unix4j with an OSGi framework, this is probably not something you'll get to any time soon. If you're ok with making such a change, I can give it a try
Thanks for your offer --- but please hold off with this for now. We are currently working on a release and possibly also migration to gradle. Also many classes are generated so we would have to see how exactly we structure the whole project and package structure.
Any news on this ? I'd love to use unix4j, but at the moment this package issue make it too complex.
sorry I didn't have time yet to do this.
@terzerm please let us know if we can assist with that
any update on this?
any update on this?
can you check latest master? is this good with the packages in the jars?
Using unix4j with an OSGi framework is challenging at the moment because some packages that clients are expected to use are served by more than one jar file. For instance
org.unix4j.builder
is served by both unix4j-base and unix4j-command. Would it be possible to rename the packages so each jar would serve unique packages?