On Tue, 6 Sep 2016 09:32:53 +0200
Hartmut Goebel wrote:
> Am 06.09.2016 um 00:15 schrieb Björn Höfling:
[..]
> > How do you proceed? Do you have an issue raised where we can share
> > knowledge/coordinate next steps?
>
> I'll convert my intermediate results into patches and some "report" to
>
Am 06.09.2016 um 00:15 schrieb Björn Höfling:
> I'm interested in which version of maven do you start to create? Which
> version(s) of the dependencies/plugins are you rebuilding?
I started building the current version of maven, since the others are
outdated and I did not want to rely on unmaintai
Hi Björn,
> I'm interested in which version of maven do you start to create? Which
> version(s) of the dependencies/plugins are you rebuilding?
I decided to start with the latest and build as many dependencies as
possible without Maven. I briefly considered packaging an older version
but ran in
Hi Hartmut and Ricardo,
On Thu, 1 Sep 2016 14:03:10 +0200
Ricardo Wurmus wrote:
>
> Hartmut Goebel writes:
>
> > is anyone working on this? (I'm lacking knowledge to help with maven
> > or gradle, but could help with commons.)
>
> We are still a long way off before get to a working maven bui
Hartmut Goebel writes:
> Am 02.09.2016 um 13:48 schrieb Ricardo Wurmus:
>
>
> > I found all of these need intervention for building, as there is no
>> "install" target (maybe I missed something). Echo of the packages
>> behaves a bit different (e.g. different directory names), while
Am 02.09.2016 um 13:48 schrieb Ricardo Wurmus:
>> > I found all of these need intervention for building, as there is no
>> > "install" target (maybe I missed something). Echo of the packages
>> > behaves a bit different (e.g. different directory names), while
>> > sharing some common patterns. I'll
Hartmut Goebel writes:
> Meantime I managed to build commons-io, commons-cli, commons-lang and
> commons-codec.
Cool!
> I found all of these need intervention for building, as there is no
> "install" target (maybe I missed something). Echo of the packages
> behaves a bit different (e.g. differ
Am 02.09.2016 um 09:47 schrieb Ricardo Wurmus:
> This should not be on the CLASSPATH. The “ant-build-system” sets
> CLASSPATH to the result of running “generate-classpath” on all inputs.
> Currently, all this does it add any and all “.jar” files to the
> CLASSPATH. To keep “jar” itself out, the r
Hartmut Goebel writes:
> Hallo,
>
> apache-commons
>
> These might have unpackaged dependencies of their own. If you took over
> “apache-commons” that would be very helpful. You should be able to use
> the “ant-build-system” to get started, even if it doesn’t result in the
> prettiest
Hallo,
> apache-commons
>
> These might have unpackaged dependencies of their own. If you took over
> “apache-commons” that would be very helpful. You should be able to use
> the “ant-build-system” to get started, even if it doesn’t result in the
> prettiest packages.
Curiously maven requir
Hartmut Goebel writes:
> is anyone working on this? (I'm lacking knowledge to help with maven
> or gradle, but could help with commons.)
We are still a long way off before get to a working maven build system.
I have a few more Java packages sitting here, but it’s not much.
We first need to rec
11 matches
Mail list logo