On 2016-12-30 02:07 +0100, Emmanuel Bourg wrote:
> Le 30/12/2016 à 01:59, Wookey a écrit :
>
> > which looks like what's wanted.
>
> Not exactly, the project wants bcel:bcel:5.x and we provide
> org.apache.bcel:bcel:5.x, the groupId is different.
Right. I eventually found https://wiki.debian.org
Le 30/12/2016 à 01:59, Wookey a écrit :
> which looks like what's wanted.
Not exactly, the project wants bcel:bcel:5.x and we provide
org.apache.bcel:bcel:5.x, the groupId is different.
Try this rule instead:
s/bcel/org.apache.bcel/ bcel * s/.*/debian/ * *
Emmanuel Bourg
On 30.12.2016 00:52, Wookey wrote:
> On 2016-12-30 00:11 +0100, Markus Koschany wrote:
>> On 29.12.2016 02:29, Wookey wrote:
>
>> Don't try to hard to make mh_make happy because it can only give you a
>> rudimentary skeleton debian directory. (For "easy" packages it works
>> much better but more c
On 2016-12-30 00:31 +0100, Emmanuel Bourg wrote:
> Le 29/12/2016 à 02:29, Wookey a écrit :
>
> > I also got the complaint that it can't find:
> > backport-util-concurrent
> >
> > Do I care about that? Do I need to package that too?
>
> You don't need that one, it's an obsolete library that bac
On 2016-12-30 00:11 +0100, Markus Koschany wrote:
> On 29.12.2016 02:29, Wookey wrote:
> Don't try to hard to make mh_make happy because it can only give you a
> rudimentary skeleton debian directory. (For "easy" packages it works
> much better but more complicated projects won't work as expected)
Le 29/12/2016 à 02:29, Wookey a écrit :
> I also got the complaint that it can't find:
> backport-util-concurrent
>
> Do I care about that? Do I need to package that too?
You don't need that one, it's an obsolete library that backported the
new java.util classes introduced in Java 5 to older J
On 29.12.2016 02:29, Wookey wrote:
[...]
Hi Wookey,
> So why didn;t my substition rules of
> s/bcel/bcel/ s/bcel/bcel/ jar s/5.1/5.x/
> or
> s/bcel/bcel/ s/bcel/bcel/ jar s/5.1/6.0/
> work?
>
> The upstream pom.xml has:
>
> bcel
> bcel
> 5.1
>
>
> The onl
> Now, to the other real problem: how to tell mh_resolve_dependencies
> to ignore some? (Case in point, multi-module project with parent POM
> and several module POMs which depend on each other; the maven helper
> stuff tries to find a Debian package for each dependency, even the
> one we were jus
OK. I tried some more on this so have an update below.
> On Wed, 2 Nov 2016 14:21, Markus Koschany wrote:
> > On 02.11.2016 05:52, Wookey wrote:
> > > Having hacked about a bit it currenty fails with:
> > > The POM for org.codehaus.mojo:native-maven-plugin:jar:1.0-alpha-7 is
> > > missing,
> >
9 matches
Mail list logo
