[LANG] Drop Ant build?

classic Classic list List threaded Threaded
25 messages Options
12
Reply | Threaded
Open this post in threaded view
|

Re: [LANG] Drop Ant build?

Emmanuel Bourg-3
Le 17/10/2015 10:41, Benedikt Ritter a écrit :

> Any idea how we can find out whether this is the case?

For the reference, there is a Debian Sources site [1] where the source
packages can be viewed. The relevant file to check is debian/control [2]
for the current version in the sid suite (i.e. the trunk for the next
Debian release). If debian/control has a Build-Depends on
maven-debian-helper it means Maven is used to build the package. A
package built with Ant would have a Build-Depends on the ant package.

Emmanuel Bourg

[1] https://sources.debian.net
[2]
https://sources.debian.net/src/libcommons-lang3-java/3.4-1/debian/control


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [LANG] Drop Ant build?

Oliver Heger-3
In reply to this post by James Carman
So is this a global decision, should we drop ant support for all Commons
components? I think there are only a few still maintaining an ant build,
and there is no guarantee that these build.xml files are up-to-date.

Oliver

Am 19.10.2015 um 13:24 schrieb James Carman:

> +1
>
> On Mon, Oct 19, 2015 at 5:39 AM Benedikt Ritter <[hidden email]> wrote:
>
>> 2015-10-19 10:50 GMT+02:00 Jan Matèrne (jhm) <[hidden email]>:
>>
>>>>> I thought it was being used to create Debian packages.
>>>>
>>>> If this turns out to be the case, then please add a note to the Ant
>>>> build file to explain this requirement.
>>>
>>>
>>> Haven't looked at the build script.
>>> But maybe you could keep only that part producing the Debian packages and
>>> use Maven ant-run for including that.
>>>
>>
>> TBH I don't see why Apache Commons should do that. If the Debain Project
>> wishes to use a build system different from what Commons is using, they
>> should take care of maintaining it.
>>
>> Regards,
>> Benedikt
>>
>>
>>>
>>>
>>> Jan
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [hidden email]
>>> For additional commands, e-mail: [hidden email]
>>>
>>>
>>
>>
>> --
>> http://people.apache.org/~britter/
>> http://www.systemoutprintln.de/
>> http://twitter.com/BenediktRitter
>> http://github.com/britter
>>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [LANG] Drop Ant build?

Benedikt Ritter-4
2015-10-19 21:36 GMT+02:00 Oliver Heger <[hidden email]>:

> So is this a global decision, should we drop ant support for all Commons
> components? I think there are only a few still maintaining an ant build,
> and there is no guarantee that these build.xml files are up-to-date.
>

I think I've read, that some of the components are still build with ant at
the Debian project. That's why I've offered to migrate all the Debian
builds that are still using Ant to Maven. After that it's save for us to
remove the Ant builds from our projects.

Benedikt


>
> Oliver
>
> Am 19.10.2015 um 13:24 schrieb James Carman:
> > +1
> >
> > On Mon, Oct 19, 2015 at 5:39 AM Benedikt Ritter <[hidden email]>
> wrote:
> >
> >> 2015-10-19 10:50 GMT+02:00 Jan Matèrne (jhm) <[hidden email]>:
> >>
> >>>>> I thought it was being used to create Debian packages.
> >>>>
> >>>> If this turns out to be the case, then please add a note to the Ant
> >>>> build file to explain this requirement.
> >>>
> >>>
> >>> Haven't looked at the build script.
> >>> But maybe you could keep only that part producing the Debian packages
> and
> >>> use Maven ant-run for including that.
> >>>
> >>
> >> TBH I don't see why Apache Commons should do that. If the Debain Project
> >> wishes to use a build system different from what Commons is using, they
> >> should take care of maintaining it.
> >>
> >> Regards,
> >> Benedikt
> >>
> >>
> >>>
> >>>
> >>> Jan
> >>>
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: [hidden email]
> >>> For additional commands, e-mail: [hidden email]
> >>>
> >>>
> >>
> >>
> >> --
> >> http://people.apache.org/~britter/
> >> http://www.systemoutprintln.de/
> >> http://twitter.com/BenediktRitter
> >> http://github.com/britter
> >>
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>


--
http://people.apache.org/~britter/
http://www.systemoutprintln.de/
http://twitter.com/BenediktRitter
http://github.com/britter
Reply | Threaded
Open this post in threaded view
|

Re: [LANG] Drop Ant build?

Sergio Fernández-3
These are all packages in currently in Debian:

https://packages.debian.org/search?keywords=libcommons

Checking the unstable distribution (the most recently updated package),
these are the packages I saw still depending on ant to build
(Build-Depends):

* libcommons-cli-java 1.3.1-2:
https://sources.debian.net/src/libcommons-cli-java/1.3.1-2/debian/control/
* libcommons-codec-java 1.10-1:
https://sources.debian.net/src/libcommons-codec-java/1.10-1/debian/control/
* libcommons-collections-java 2.1.1-10:
https://sources.debian.net/src/libcommons-collections-java/2.1.1-10/debian/control/
* libcommons-collections3-java 3.2.1-8:
https://sources.debian.net/src/libcommons-collections3-java/3.2.1-8/debian/control/
* libcommons-compress-java 1.10-1:
https://sources.debian.net/src/libcommons-compress-java/1.10-1/debian/control/
* libcommons-digester-java 1.8.1-4:
https://sources.debian.net/src/libcommons-digester-java/1.8.1-4/debian/control/
* libcommons-el-java 1.0-8:
https://sources.debian.net/src/libcommons-el-java/1.0-8/debian/control/
* libcommons-lang-java 2.6-5:
https://sources.debian.net/src/libcommons-lang-java/2.6-5/debian/control/
* libcommons-launcher-java 1.1-8:
https://sources.debian.net/src/libcommons-launcher-java/1.1-8/debian/control/
* libcommons-modeler-java 2.0.1-7:
https://sources.debian.net/src/libcommons-modeler-java/2.0.1-7/debian/control/
* libcommons-net-java 3.3-2:
https://sources.debian.net/src/libcommons-net-java/3.3-2/debian/control/
* libcommons-net2-java 2.2-2:
https://sources.debian.net/src/libcommons-net2-java/2.2-2/debian/control/
* libcommons-validator-java 1:1.4.1-1:
https://sources.debian.net/src/libcommons-validator-java/1:1.4.1-1/debian/control/

Double check would be good, since I could missed any. I think most are old
versions, and given the package naming in Debian are still there. How many
components do actually still use Ant as build system?


On Mon, Oct 19, 2015 at 9:38 PM, Benedikt Ritter <[hidden email]> wrote:

> 2015-10-19 21:36 GMT+02:00 Oliver Heger <[hidden email]>:
>
> > So is this a global decision, should we drop ant support for all Commons
> > components? I think there are only a few still maintaining an ant build,
> > and there is no guarantee that these build.xml files are up-to-date.
> >
>
> I think I've read, that some of the components are still build with ant at
> the Debian project. That's why I've offered to migrate all the Debian
> builds that are still using Ant to Maven. After that it's save for us to
> remove the Ant builds from our projects.
>
> Benedikt
>
>
> >
> > Oliver
> >
> > Am 19.10.2015 um 13:24 schrieb James Carman:
> > > +1
> > >
> > > On Mon, Oct 19, 2015 at 5:39 AM Benedikt Ritter <[hidden email]>
> > wrote:
> > >
> > >> 2015-10-19 10:50 GMT+02:00 Jan Matèrne (jhm) <[hidden email]>:
> > >>
> > >>>>> I thought it was being used to create Debian packages.
> > >>>>
> > >>>> If this turns out to be the case, then please add a note to the Ant
> > >>>> build file to explain this requirement.
> > >>>
> > >>>
> > >>> Haven't looked at the build script.
> > >>> But maybe you could keep only that part producing the Debian packages
> > and
> > >>> use Maven ant-run for including that.
> > >>>
> > >>
> > >> TBH I don't see why Apache Commons should do that. If the Debain
> Project
> > >> wishes to use a build system different from what Commons is using,
> they
> > >> should take care of maintaining it.
> > >>
> > >> Regards,
> > >> Benedikt
> > >>
> > >>
> > >>>
> > >>>
> > >>> Jan
> > >>>
> > >>>
> > >>> ---------------------------------------------------------------------
> > >>> To unsubscribe, e-mail: [hidden email]
> > >>> For additional commands, e-mail: [hidden email]
> > >>>
> > >>>
> > >>
> > >>
> > >> --
> > >> http://people.apache.org/~britter/
> > >> http://www.systemoutprintln.de/
> > >> http://twitter.com/BenediktRitter
> > >> http://github.com/britter
> > >>
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [hidden email]
> > For additional commands, e-mail: [hidden email]
> >
> >
>
>
> --
> http://people.apache.org/~britter/
> http://www.systemoutprintln.de/
> http://twitter.com/BenediktRitter
> http://github.com/britter
>



--
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: [hidden email]
w: http://redlink.co
Reply | Threaded
Open this post in threaded view
|

Re: [LANG] Drop Ant build?

Emmanuel Bourg-3
Le 20/10/2015 08:32, Sergio Fernández a écrit :

> Double check would be good, since I could missed any. I think most are old
> versions, and given the package naming in Debian are still there. How many
> components do actually still use Ant as build system?

Another way to find the source packages depending on Ant is to use the
build-rdeps command (from the devscripts package) :

  commons-configuration
  commons-daemon
  commons-httpclient
  commons-io
  commons-javaflow
  commons-jci
  commons-math
  commons-math3
  commons-pool
  libcommons-attributes-java
  libcommons-cli-java
  libcommons-codec-java
  libcommons-collections3-java
  libcommons-compress-java
  libcommons-digester-java
  libcommons-el-java
  libcommons-jexl-java
  libcommons-jxpath-java
  libcommons-lang-java
  libcommons-launcher-java
  libcommons-modeler-java
  libcommons-net1-java
  libcommons-net2-java
  libcommons-net-java
  libcommons-openpgp-java
  libcommons-validator-java

Some of them can be ignored, because they contain an old version of a
commons components, or a dormant component that won't evolve anymore:

  commons-httpclient -> Old httpclient, to be removed
  commons-math -> Math 3.x is in src:commons-math3
  libcommons-attributes-java -> dormant
  libcommons-collections3-java -> 4.x in libcommons-collections4-java
  libcommons-digester-java -> Old 1.x line, 2.x not packaged yet
  libcommons-lang-java -> Lang 3.x is in libcommons-lang3-java
  libcommons-launcher-java -> dormant, unused in Debian
  libcommons-modeler-java -> dormant component
  libcommons-net{1,2}-java -> Latest version is libcommons-net-java
  libcommons-openpgp-java -> dormant sandbox component


A word on Ant vs Maven usage in Debian: at some point in time it was
possible to build the Maven dependencies with Ant. That was necessary to
bootstrap Maven in Debian. This is no longer true today and Maven can be
used to build its own dependencies. So from the Debian point of view it
should be ok to remove all Ant builds from the Commons components.

Emmanuel Bourg


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

12