https://bugzilla.redhat.com/show_bug.cgi?id=1312015 --- Comment #14 from jiri vanek <jvanek@xxxxxxxxxx> --- Spec URL: https://jvanek.fedorapeople.org/offlinesearch/v3/javadocofflinesearch.spec SRPM URL: https://jvanek.fedorapeople.org/offlinesearch/v3/javadocofflinesearch-2.2-1.fc23.src.rpm (also bin directory with build binaries..) License fixed, java-devel added. TYVM! The packing: This idea really crossed my mind. Issue is that netbeans generated (and from time to time regenerated) build script is easy to extend, but clumsy to modify. So I have basically three options: 1- patch (in spec) generated buildscript to exclude manifest generation and call ant dist. Then this jar may be reused 2 - create new upstream ant target, which pack the built classes. This may sound like best idea but the target is completely useless out of fedora world. 3 - go as now - use generated target to build classes and pack manually >From those (3) seems like smallest evil based on my experience on packaging netbeasn projects. IMHO - build IS *.java -> *.class. As you can equally run directory full of classes or ziparchive full of classes (jar). Fedora have infrastructure to help with jars. So result of build - the classes - are JARed. When you look to release on github - the preferred way out of distribution package is assembled jar with all dependences. -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component _______________________________________________ package-review mailing list package-review@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/package-review