* Sylvestre Ledru:
> Asking several times the same question won't help you with that ...
> You should focus on packaging itself.
Way to go, telling people in a largely volunteer-based community what
their priorities should be...
-Hilko
--
To UNSUBSCRIBE, email to debian-java-requ...@lists.deb
On 03/22/2013 01:09 AM, Emmanuel Bourg wrote:
> Hi Thomas,
>
> Le 22/03/2013 08:41, Thomas Koch a écrit :
>
>> I usually migrate all packages from SVN to Git when I touch them. There are
>> only a few (2-3?) Debian Java Devs who still prefer SVN.
>>
>> So if you like, we could quickly do the mig
Hi,
Here is my first RFS for a simple upgrade of Apache Commons Compress. If
it goes well there is more to follow soon :)
Emmanuel Bourg
---
I am looking for a sponsor for my package "libcommons-compress-java"
* Package name: libcommons-compress-java
Version : 1.5-1
Section
On Thu, 21. Mar 21:06 tony mancill wrote:
> Hello Markus,
>
> Nice job with the packaging. You might consider adding maven
> coordinates in a future revisions, but the package appears ready for the
> archive, so I have uploaded it. Feel free to contact me either directly
> or via the list for s
On Fri, 22 Mar 2013 08:53:05 +0100, Thomas Koch wrote:
> Second thing is with source tarballs or Git repos. For building a Debian
> package we need a source tarball that does not contain any non-free or binary
> artifacts.
What's equally annyoing are tarballs/zipfiles that don't contain the
co
Hi Thomas,
I did some improvements to mdh related to non interactive mode:
1. Package version defaults to maven version.
2. ignore-missing flag Introduced to ignore not needed libraries to be able
to continue and see if build fails.
3. mh_make skip test / doc flag fixes.
4. Default licence versio
Le 22/03/2013 09:22, Thomas Koch a écrit :
> However I'm not sure whether a source.jar produced by maven can be used to
> build a Debian package. I assume that generated java code from tools like
> protobuf or jflex is included in the source.jar? We don't want generated
> source code but the "r
Le 22/03/2013 09:34, Thomas Koch a écrit :
> the groupId declared in the dependency (org.apache.commons) and the groupId
> provided (commons-jexl) are different. Please look, which would be the most
> "official" groupId and we can patch the commons-jexl to publish its artifacts
> under the corr
Le 22/03/2013 08:53, Thomas Koch a écrit :
> thank you for offering your help. As I wrote, it would be very helpful, if
> somebody (you) could start to lobby for sane artifact signing on Apache
> Conferences and on mailing lists.
>
> It doesn't make sense to sign release artifacts with GPG keys
Emmanuel Bourg:
> Le 19/03/2013 15:44, Niels Thykier a écrit :
> > So, I never took time to understand what all of that maven-stuff means,
> > but if
> >
> > """org.apache.commons:commons-jexl:jar:debian"""
> >
> > is "::", then that is probably the issue
> > because the commons-jexl pom appears
Manfred Moser:
> Some clarifications..
dito, thx for your reply.
> > - Release source tarballs, not only binaries to maven central.
>
> This has been a requirement for open source components in Central for
> years. You can find them with the -sources classifier in a jar file. E.g.
> looking at
>
Hi Thomas,
Le 22/03/2013 08:41, Thomas Koch a écrit :
> I usually migrate all packages from SVN to Git when I touch them. There are
> only a few (2-3?) Debian Java Devs who still prefer SVN.
>
> So if you like, we could quickly do the migration and then you can learn
> packaging with current t
Emmanuel Bourg:
> Hi Thomas,
>
> I'm a committer on the Apache Commons project, if you have an itch to
> scratch with one of the libraries (commons-lang, commons-collections,
> etc) I should be able to help quickly.
>
> Do you have specific examples of Apache projects affected by the issues
> you
On 22/03/2013 08:45, Thomas Koch wrote:
> Hi,
>
> I remember that some people in the Debian-Java team wrote that they'd prefer
> their packages to remain in SVN. But I can't find the mail thread anymore.
>
> And people might have changed their minds in the last months.
>
> Could you be so kind,
Hi,
I remember that some people in the Debian-Java team wrote that they'd prefer
their packages to remain in SVN. But I can't find the mail thread anymore.
And people might have changed their minds in the last months.
Could you be so kind, to give a short response to this mail in case that you
Emmanuel Bourg:
> Hi,
>
> I updated Commons Compress in SVN for the recent 1.5 release. What is
Hi Emmanuel,
I usually migrate all packages from SVN to Git when I touch them. There are
only a few (2-3?) Debian Java Devs who still prefer SVN.
So if you like, we could quickly do the migration an
16 matches
Mail list logo
