Hi Markus,
thanks for the explanation of the unusual commit - I keep on wondering
why git claims me as the author of that changes. Also git blame says
I have created the patch ... hmmmm.
Anyway, I have two remaining questions:
1. I have set:
Debian Java Maintainers <pkg-java-maintain...@alioth-lists.debian.net>
since this is the real address of the new list. In some unrelated
discussion it was decided that we stick to the old e-mail ID for the
maintainer in other projects. Should I rather change to
Debian Java Maintainers <pkg-java-maintain...@lists.alioth.debian.org>
?
2. I remember there was some way to add maven control information to
such library package. I have found something that would fit[1].
Could you please refresh my mind and tell me where I should put
this to enable other depending packages grabbing the proper
information?
Thanks for all your quick help
Andreas.
[1] https://mvnrepository.com/artifact/org.javolution/javolution/6.0.0
----- Forwarded message from Andreas Tille <ti...@debian.org> -----
Date: Sat, 26 May 2018 14:58:35 +0200
From: Andreas Tille <ti...@debian.org>
To: Debian Bug Tracking System <sub...@bugs.debian.org>
Subject: Bug#900124: ITP: libjavolution-java -- Java core library for real-time
and embedded systems
X-Debian-PR-Message: report 900124
X-Debian-PR-Package: wnpp
X-Debian-PR-Keywords:
Package: wnpp
Severity: wishlist
Owner: Andreas Tille <ti...@debian.org>
* Package name : libjavolution-java
Version : 6.0.0
Upstream Author : Javolution
* URL : http://javolution.org/
* License : BSD-2-clause
Programming Lang: Java
Description : Java core library for real-time and embedded systems
Javolution real-time goals are simple: To make your application faster
and more time predictable!
.
* High-Performance - Hardware accelerated computing (GPUs) with
ComputeContext.
* Minimalistic - Collection classes, supporting custom views, closure-
based iterations, map-reduce paradigm, parallel computations, etc.
* Optimized - To reduce the worst case execution time documented
through annotations.
* Innovative - Fractal-based structures to maintain high-performance
regardless of the size of the data.
* Multi-Cores Ready - Most parallelizable classes (including
collections) are either mutex-free (atomic) or using extremely short
locking time (shared).
* OSGi Compliant - Run as a bundle or as a standard library. OSGi
contexts allow cross cutting concerns (concurrency, logging,
security, ...) to be addressed at run-time through OSGi published
services without polluting the application code (Separation of
Concerns).
* Interoperable - Struct and Union base classes for direct interfacing
with native applications. Development of the Javolution C++ library
to mirror its Java counterpart and makes it easy to port any Java
application to C++ for native compilation (maven based) or to write
Java-Like code directly in C++ (more at Javolution C++ Overview)).
* Simple - You don't need to know the hundreds of new Java 8 util.*
classes, most can be built from scratch by chaining Javolution
collections or maps. No need to worry about configuration,
immutability or code bloating !
Remark: This package is maintained by Debian Java Maintainers at
https://salsa.debian.org/java-team/libjavolution-java
This package is a predepencency for some scientific Java packages.
----- End forwarded message -----
--
http://fam-tille.de
