Re: The state of Maven
On Sat, 5 Aug 2017, Emmanuel Bourg wrote: > Le 3/08/2017 à 14:03, Thorsten Glaser a écrit : > > > I’d have preferred it doing something like tty detection, to behave > > nice with other OSS citizens, but oh well and it’s upstream’s issue. > > Interesting, do you know how to do that in Perl? We could perform the > detection in maven-debian-helper and pass the -B parameter if necessary. The C function isatty() on the output filedescriptor, but in a build helper like that I’d expect it to always be disabled. bye, //mirabilos -- tarent solutions GmbH Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/ Tel: +49 228 54881-393 • Fax: +49 228 54881-235 HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941 Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg
Re: The state of Maven
Le 5/08/2017 à 13:15, Markus Koschany a écrit : > My question: What exactly can I/we do to help? Excellent question, thanks :) Some help migrating away from the older packages I mentioned would be nice (for example libplexus-utils-java which still has 50 reverse dependencies). Emmanuel Bourg
Re: The state of Maven
Le 3/08/2017 à 14:03, Thorsten Glaser a écrit : > I’d have preferred it doing something like tty detection, to behave > nice with other OSS citizens, but oh well and it’s upstream’s issue. Interesting, do you know how to do that in Perl? We could perform the detection in maven-debian-helper and pass the -B parameter if necessary. > My own desktop and the Jenkins are running unstable, so I always get > this kind of updates. Is there a way I can check the list of maven > plugins used/preferred by Debian, so I can enter them in the POM > (where it always warns when no version is given anyway) so that > others (e.g. my coworkers using *buntu) get the same versions but > I can use the packaged versions instead of it having to download > stuff from Central? Sorry I don't see an easy way to track the Maven plugins packaged in Debian. Someday it would be nice to index all the Maven artifacts packaged and have a search engine like http://www.mvnrepository.com to inspect them. That would be the right place to look for plugins in Debian. Emmanuel Bourg
Re: Request to join the debian-java team
On 05/08/17 06:25, Alastair McKinstry wrote: Hi, I'd like to join the debian-java team. I've been working on and packaging several Java packages for debian, such as jpy (python-java gateway), thredds, netcdf, geoserver and beam libraries, used in geospatial data (ITPs submitted). (These packages are interrelated; thredds and beam provide and work with netcdf files and netcdf-java, etc.) These have a tree of dependencies i've also been working on, typically gradle plugins that are required for them to build. I would like to add these to The Java team-maintained packages and co-ordinate with existing work in Debian. Hi, thank you for your contributions. Please click on the link at the bottom right corner on this page [1] and follow the instructions to join the team. Regards, Markus [1] https://alioth.debian.org/projects/pkg-java/
Re: Java BoF at DebConf?
On 20/07/17 00:26, tony mancill wrote: On Wed, Jul 19, 2017 at 01:28:31AM +0200, Markus Koschany wrote: Am 19.07.2017 um 01:14 schrieb Matthias Klose: Hi, not sure how many people will visit DebConf. Would it make sense to have a buster BoF? I'll be there, and would like helping organizing such a BoF if there is interest. I'll be in Montreal too. Also wanted to bring this topic up myself. I will hold a talk about Debian Games related stuff but otherwise I'm absolutely available. There will also be a clojure BoF, not sure if we should just "merge" both of them or organize a separate event. I guess we will find more than enough topics to talk about. :) Hi Matthias, Thank you for coordinating this. I will be there too and am definitely interested in attending a Java BoF. I expect that clojure is distinct enough for us to at least try for a separate Java BoF to talk about what we need/would like accomplish in buster, but combining them would better than not having one at all. I have beamed myself to Canada. Ready, when you are. Markus
Re: The state of Maven
On 03/08/17 04:31, Emmanuel Bourg wrote: Hi all, As you may have noticed I have updated many Maven related packages recently, and I'd like to summarize quickly what I'm doing and where we're heading. Hi, first of all thank you very much for updating this core build tool for Java. Maven in testing/unstable is currently at the latest upstream release (3.5.0). The most visible change since Maven 3.3.9 is the colored console output which is really nice (except for the builder logs, they are now cluttered with ANSI escape code and I don't know if there is a way to avoid that). If time allows I'll try to backport this version to Stretch. I like the new color output but the ANSI escape code makes it difficult to copy&paste log information. I would be great if we could avoid it. [...] Thanks for explaining the most important changes. My question: What exactly can I/we do to help? Once all of this is over I'd like to invest some time on maven-debian-helper to better support multi module projects. I have 3 improvements in mind: Sounds good to me. Markus
Request to join the debian-java team
Hi, I'd like to join the debian-java team. I've been working on and packaging several Java packages for debian, such as jpy (python-java gateway), thredds, netcdf, geoserver and beam libraries, used in geospatial data (ITPs submitted). (These packages are interrelated; thredds and beam provide and work with netcdf files and netcdf-java, etc.) These have a tree of dependencies i've also been working on, typically gradle plugins that are required for them to build. I would like to add these to The Java team-maintained packages and co-ordinate with existing work in Debian. Best regards Alastair McKinstry -- Alastair McKinstry, , , https://diaspora.sceal.ie/u/amckinstry Misentropy: doubting that the Universe is becoming more disordered. signature.asc Description: OpenPGP digital signature
Re: The state of Maven
On Thu, 3 Aug 2017, Emmanuel Bourg wrote: > Hi all, > > As you may have noticed I have updated many Maven related packages > recently, and I'd like to summarize quickly what I'm doing and where > we're heading. > > Maven in testing/unstable is currently at the latest upstream release > (3.5.0). The most visible change since Maven 3.3.9 is the colored > console output which is really nice (except for the builder logs, they > are now cluttered with ANSI escape code and I don't know if there is a > way to avoid that). If time allows I'll try to backport this version to > Stretch. > > [...] > > The situation is improving but we can do better. The upstream binary for > Maven 3.5.0 weighs 8.2MB compressed, 10MB installed, so even with the > package overhead I expect to halve the current numbers. Hi Emmanuel, Thanks for your work on this area, the improvements are clearly notable. Cheers, Miguel. -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. "Faith means not wanting to know what is true." -- Nietzsche signature.asc Description: Digital signature
Advice regarding Java packages for SimpleITK
Dear all, I am in the process of packaging SimpleITK [1] for Debian which provides several language bindings around the ITK C++ library using swig. [1] https://github.com/SimpleITK/SimpleITK So far, I have only taken care of the common C++ library and Python 3 bindings, but Java is also supported and used by the ImageJ v2 stack optionally. Consequently, I'd like to provide an additional binary package for Java, and wanted to consult the team on how best to handle it. The build system uses CMake to generate the bindings. If Java is enabled, the following files are generated: /<>/SimpleITK-build/Wrapping/Java/build/javadoc/* /<>/SimpleITK-build/Wrapping/Java/build/org/itk/simple/*class /<>/SimpleITK-build/Wrapping/Java/lib/libSimpleITKJava.so /<>/SimpleITK-build/Wrapping/Java/org/itk/simple/*.java /<>/SimpleITK-build/Wrapping/Java/simpleitk-1.0.1.jar /<>/SimpleITK-build/Wrapping/Java/simpleitk-javadoc-1.0.1.jar /<>/SimpleITK-build/Wrapping/Java/simpleitk-source-1.0.1.jar I was wondering which files should be installed (and to which location) to produce corresponding Java packages which are policy compliant. Thanks in advance, Ghis
