On Mon, Mar 05, 2007 at 10:47:36PM +0100, Daniel Leidert wrote:
> Am Montag, den 05.03.2007, 22:36 +0100 schrieb Michael Koch:
>
> > Lucus Nussbaum was so kind to setup a cronjob to generate a comparison
> > between Debian und Ubuntu to make it easier for us to track differences.
> > Its generated
Am Montag, den 05.03.2007, 22:47 +0100 schrieb Daniel Leidert:
> Am Montag, den 05.03.2007, 22:36 +0100 schrieb Michael Koch:
>
> > Lucus Nussbaum was so kind to setup a cronjob to generate a comparison
> > between Debian und Ubuntu to make it easier for us to track differences.
> > Its generated
Am Montag, den 05.03.2007, 22:36 +0100 schrieb Michael Koch:
> Lucus Nussbaum was so kind to setup a cronjob to generate a comparison
> between Debian und Ubuntu to make it easier for us to track differences.
> Its generated every 6 hours and shows all packages with "Java" in the
> Maintainer fiel
Hello list,
Lucus Nussbaum was so kind to setup a cronjob to generate a comparison
between Debian und Ubuntu to make it easier for us to track differences.
Its generated every 6 hours and shows all packages with "Java" in the
Maintainer field.
You can find this at http://tiber.tauware.de/~lucas/
On Mon, Mar 05, 2007 at 11:38:06AM -0800, [EMAIL PROTECTED] wrote:
> Quoting Michael Koch <[EMAIL PROTECTED]>:
>
> >>I dont think this can be the only option. Two very different version
> >>of a library can still be very stable and secure and useful for
> >>different programs. Is there any chance
On Mon, Mar 05, 2007 at 11:43:16AM -0800, [EMAIL PROTECTED] wrote:
> Hi all!
>
> Different follow up on that package. I have installed it on Ubuntu
> Edgy and ran it through my build (large web application that uses a
> lot of Maven plug ins during the build) and all worked fine.
Thanks for
Hi all!
Different follow up on that package. I have installed it on Ubuntu
Edgy and ran it through my build (large web application that uses a
lot of Maven plug ins during the build) and all worked fine.
I forward a "announcement" to the Maven user and Maven developers
list. Lots of the
Quoting Michael Koch <[EMAIL PROTECTED]>:
I dont think this can be the only option. Two very different version
of a library can still be very stable and secure and useful for
different programs. Is there any chance that this approach is being
reconsidered?
I dont think so. Every duplicated lib
Quoting Marcus Better <[EMAIL PROTECTED]>:
[EMAIL PROTECTED] wrote:
I think it would be better to just leave the version as is and accept
that multiple version sit around on the file system. They don' cause
any harm anyway.
The Debian package will support this for _users_, it will work just l
On Mon, Mar 05, 2007 at 09:28:11AM -0800, [EMAIL PROTECTED] wrote:
> Quoting Michael Koch <[EMAIL PROTECTED]>:
>
> >Debian always installs jars with ther version number. The files without
> >version numbers are just symlinks to the latest version.
>
> Ah... thats good to know.
>
> >Debian only p
[EMAIL PROTECTED] writes:
> I think it would be better to just leave the version as is and accept
> that multiple version sit around on the file system. They don' cause
> any harm anyway.
they do. Do you volunteer to provide security upgrades for two years
for 10 versions of the same library?
Quoting Michael Koch <[EMAIL PROTECTED]>:
Debian always installs jars with ther version number. The files without
version numbers are just symlinks to the latest version.
Ah... thats good to know.
Debian only packages one (the latest) version of a Java software.
Everthing else would be a hor
[guys, please don't CC me, I am subscribed.]
[EMAIL PROTECTED] wrote:
> I think it would be better to just leave the version as is and accept
> that multiple version sit around on the file system. They don' cause
> any harm anyway.
The Debian package will support this for _users_, it will work ju
Quoting Marcus Better <[EMAIL PROTECTED]>:
[EMAIL PROTECTED] wrote:
As far as I can tell the problem exists because many libraries do
dramatic changes to their API quite regularly ..
Major API changes may warrant having two different versions of a library in
Debian. This happens from time to
[EMAIL PROTECTED] wrote:
> As far as I can tell the problem exists because many libraries do
> dramatic changes to their API quite regularly ..
Major API changes may warrant having two different versions of a library in
Debian. This happens from time to time. However if such changes happen very
of
On Mon, Mar 05, 2007 at 08:50:18AM -0800, [EMAIL PROTECTED] wrote:
> Quoting Arnaud Vandyck <[EMAIL PROTECTED]>:
>
> >On 3/5/07, Michael Koch <[EMAIL PROTECTED]> wrote:
> >[...]
> >>>I understand your point of view and respect it. But as we are
> >>>responsible in some way of the software we packa
Quoting Michael Koch <[EMAIL PROTECTED]>:
On Mon, Mar 05, 2007 at 04:27:04PM +0100, Marcus Better wrote:
Arnaud Vandyck wrote:
> I was not talking of the dependencies version problem for debian but
> for someone using maven in debian with a debian repository ;-)
I don't see the need for a spec
On Mon, Mar 05, 2007 at 08:41:07AM -0800, [EMAIL PROTECTED] wrote:
> Quoting Marcus Better <[EMAIL PROTECTED]>:
>
> >Another issue: Maven projects tend to specify exact version of their
> >dependencies. For building Debian packages, we need to get Maven to use
> >whatever version we have in Debian
Quoting Arnaud Vandyck <[EMAIL PROTECTED]>:
On 3/5/07, Michael Koch <[EMAIL PROTECTED]> wrote:
[...]
I understand your point of view and respect it. But as we are
responsible in some way of the software we package and distribute, we
cannot distribute a software for Debian that could install non
Quoting Marcus Better <[EMAIL PROTECTED]>:
Another issue: Maven projects tend to specify exact version of their
dependencies. For building Debian packages, we need to get Maven to use
whatever version we have in Debian (and just make sure it's recent enough).
Hi all!
I apologize if the follow
On Mon, Mar 05, 2007 at 03:59:02PM +0100, Arnaud Vandyck wrote:
> On 3/5/07, Michael Koch <[EMAIL PROTECTED]> wrote:
> [...]
> >> I understand your point of view and respect it. But as we are
> >> responsible in some way of the software we package and distribute, we
> >> cannot distribute a softwar
On Mon, Mar 05, 2007 at 04:27:04PM +0100, Marcus Better wrote:
> Arnaud Vandyck wrote:
> > I was not talking of the dependencies version problem for debian but
> > for someone using maven in debian with a debian repository ;-)
>
> I don't see the need for a special Debian-Maven repository.
Me nei
On Mon, Mar 05, 2007 at 04:05:57PM +0100, Arnaud Vandyck wrote:
> We are mixing concepts here ;-) (we should meet for real ;-))
>
> On 3/5/07, Michael Koch <[EMAIL PROTECTED]> wrote:
> >On Mon, Mar 05, 2007 at 02:49:39PM +0100, Marcus Better wrote:
> >> Arnaud Vandyck wrote:
> [...]
> >> > Also, w
On 3/5/07, Michael Koch <[EMAIL PROTECTED]> wrote:
[...]
My plan for this would to upload working packages to some common
repository outside the official Debian archive to get the work done and
dont need to wait for ftp-master approval for each package. When all
packages are done and cleaned up I
On Mon, Mar 05, 2007 at 04:13:28PM +0100, Marcus Better wrote:
> user pkg-java-maintainers@lists.alioth.debian.org
> usertag 323050 maven2-packaging
> thanks
>
> > But I currently try a different route. I put all maven dependencies
> > (jars) into a new big package maven-dependencies and will then
Arnaud Vandyck wrote:
> I was not talking of the dependencies version problem for debian but
> for someone using maven in debian with a debian repository ;-)
I don't see the need for a special Debian-Maven repository.
Marcus
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "uns
On 3/5/07, Michael Koch <[EMAIL PROTECTED]> wrote:
[...]
What we learnt from the past that we dont always manage to do this. We
should cripple Maven so much that people used to it and switching to
Debian can work with it anymore because it behaves different.
Or does not work. I have the same pr
We are mixing concepts here ;-) (we should meet for real ;-))
On 3/5/07, Michael Koch <[EMAIL PROTECTED]> wrote:
On Mon, Mar 05, 2007 at 02:49:39PM +0100, Marcus Better wrote:
> Arnaud Vandyck wrote:
[...]
> > Also, we try to have less possible different versions (we try to have
> > the latest
On Mon, Mar 05, 2007 at 03:52:43PM +0100, Trygve Laugstøl wrote:
> Michael Koch wrote:
> >On Mon, Mar 05, 2007 at 02:16:27PM +0100, Arnaud Vandyck wrote:
> >>Hi Marcus,
> >>
> >>On 3/5/07, Marcus Better <[EMAIL PROTECTED]> wrote:
> >>>Trygve Laugstøl wrote:
> As a user Maven should behave just
On 3/5/07, Michael Koch <[EMAIL PROTECTED]> wrote:
[...]
> I understand your point of view and respect it. But as we are
> responsible in some way of the software we package and distribute, we
> cannot distribute a software for Debian that could install non free
> software in all ~'s.
Binary blo
user pkg-java-maintainers@lists.alioth.debian.org
usertag 323050 maven2-packaging
thanks
> But I currently try a different route. I put all maven dependencies
> (jars) into a new big package maven-dependencies and will then build
> maven2 with it as Build-Dependency.
Ok, fine. As you see I userta
Michael Koch wrote:
On Mon, Mar 05, 2007 at 02:16:27PM +0100, Arnaud Vandyck wrote:
Hi Marcus,
On 3/5/07, Marcus Better <[EMAIL PROTECTED]> wrote:
Trygve Laugstøl wrote:
As a user Maven should behave just like
upstream Maven, meaning that it will download from the internet and
install stuff u
On Mon, Mar 05, 2007 at 03:43:35PM +0100, Marcus Better wrote:
> Michael Koch wrote:
> > And the dependencies mostly need maven2 for building too. Bootstrapping
> > can be fun.
>
> But we can use your preliminary maven2 package to build the dependencies, I
> assume? That would solve the bootstra
Michael Koch wrote:
> And the dependencies mostly need maven2 for building too. Bootstrapping
> can be fun.
But we can use your preliminary maven2 package to build the dependencies, I
assume? That would solve the bootstrapping problem.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a sub
On Mon, Mar 05, 2007 at 03:14:00PM +0100, Marcus Better wrote:
> Arnaud Vandyck wrote:
> >> The only requirement I have from the Debian packagers is that Maven from
> >> Debian still behaves *exactly* like Maven from Apache from a users point
> >> of view.
>
> > we cannot distribute a software for
Aldous,
I am interested in a Debian version of the "forehead" Java library, and I
noticed your ITP for it
(http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=344112).
I was just wondering how it was going, and if you had an idea of when it
is likely to be completed? Or, if you no longer have the ti
On Mon, Mar 05, 2007 at 10:29:37AM +0100, Trygve Laugstøl wrote:
> The only requirement I have from the Debian packagers is that Maven from
> Debian still behaves *exactly* like Maven from Apache from a users point
> of view. If not I will not and can not support it in any way. This is
> imperat
Arnaud Vandyck wrote:
>> The only requirement I have from the Debian packagers is that Maven from
>> Debian still behaves *exactly* like Maven from Apache from a users point
>> of view.
> we cannot distribute a software for Debian that could install non free
> software in all ~'s.
Of course we ca
On Mon, Mar 05, 2007 at 02:16:27PM +0100, Arnaud Vandyck wrote:
> Hi Marcus,
>
> On 3/5/07, Marcus Better <[EMAIL PROTECTED]> wrote:
> >Trygve Laugstøl wrote:
> >> As a user Maven should behave just like
> >> upstream Maven, meaning that it will download from the internet and
> >> install stuff un
On Mon, Mar 05, 2007 at 02:49:39PM +0100, Marcus Better wrote:
> Arnaud Vandyck wrote:
>
> >> 2. For building Debian packages: This needs to use Debian versions of
> >> dependencies.
>
> > Also, we try to have less possible different versions (we try to have
> > the latest stable), but with Maven
On Mon, Mar 05, 2007 at 02:11:41PM +0100, Arnaud Vandyck wrote:
> Hi Trygve,
>
> On 3/5/07, Trygve Laugstøl <[EMAIL PROTECTED]> wrote:
> >Arnaud Vandyck wrote:
> >> On 3/4/07, Manfred Moser <[EMAIL PROTECTED]> wrote:
> >>> On Sunday March 4 2007 09:27, Michael Koch wrote:
> >>>
> >>> > I have buil
Hi Marcus,
On 3/5/07, Marcus Better <[EMAIL PROTECTED]> wrote:
Trygve Laugstøl wrote:
> As a user Maven should behave just like
> upstream Maven, meaning that it will download from the internet and
> install stuff under ~/.m2/repository.
[...]
> For the dpkg builder Maven should still behave l
Hi Trygve,
On 3/5/07, Trygve Laugstøl <[EMAIL PROTECTED]> wrote:
Arnaud Vandyck wrote:
> On 3/4/07, Manfred Moser <[EMAIL PROTECTED]> wrote:
>> On Sunday March 4 2007 09:27, Michael Koch wrote:
>>
>> > I have built a preliminary Debian packages for Maven 2
>
> [...]
To me the answer is obviou
Arnaud Vandyck wrote:
>> 2. For building Debian packages: This needs to use Debian versions of
>> dependencies.
> Also, we try to have less possible different versions (we try to have
> the latest stable), but with Maven, you can work with older versions
> of a lib. Do we accept this?
IMHO we sh
Trygve Laugstøl wrote:
> As a user Maven should behave just like
> upstream Maven, meaning that it will download from the internet and
> install stuff under ~/.m2/repository.
[...]
> For the dpkg builder Maven should still behave like Maven *but* with
> some environmental changes it can comply wi
Arnaud Vandyck wrote:
On 3/4/07, Manfred Moser <[EMAIL PROTECTED]> wrote:
On Sunday March 4 2007 09:27, Michael Koch wrote:
> I have built a preliminary Debian packages for Maven 2
[...]
This is great. I use Maven2 on a daily base as part of my job. I am
running the upstream install in Ubun
46 matches
Mail list logo
