Paul Cager wrote:
For packages that are built by Maven it would take no more than a few
minutes to write a debian/build.xml for the Debian build system.
That is probably true for most projects, but it also means we have to
maintain that build.xml file. I think some projects are more complicated
Marcus Better wrote:
A Debian user (building stuff for
their own use) would expect Maven to work the same as it does elsewhere.
How about this mini-plan for packaging Maven:
Step 1. Package Maven for use case 1 only, i.e., targetted for regular
users, with functionality identical to
Quoting Michael Koch [EMAIL PROTECTED]:
deb-src http://people.debian.org/~mkoch/maven2/ ./
Then do
apt-get update
apt-get source maven2-binary
This downloads the package sources for you and unpacks them.
to build the package just do debuild. This builds the whole package.
Thanks Michael. I
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 built a preliminary Debian packages for Maven 2
[...]
To me the answer
Quoting Michael Koch [EMAIL PROTECTED]:
And another thanks for all your input. This is really appreciated and
discussion is needed.
No problem. I am sticking around. I also joined the package
maintainers list out of curiosity. I am in the process of learning how
to create a binary package
On Tue, Mar 06, 2007 at 12:22:56PM -0800, [EMAIL PROTECTED] wrote:
Quoting Michael Koch [EMAIL PROTECTED]:
And another thanks for all your input. This is really appreciated and
discussion is needed.
No problem. I am sticking around. I also joined the package
maintainers list out of
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
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 with
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 should
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 obvious. As a user
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 like
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 built a preliminary Debian
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, you can
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 under
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 can -
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
imperative
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 Debian that
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
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
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 blobs
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 like
upstream Maven,
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 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
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
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 build
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: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, we try to have
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 neither.
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 software for Debian
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
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
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 (and
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 special
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 package and
[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
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
[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 just
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
[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?
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 packages one
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
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
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
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
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 that this
. It will not get uploaded to the
official Debian archive. The Debian Java team (including me) is working
on a maven2 package for Debian which builds from source but has itself
around 90 dependencies. And the dependencies mostly need maven2 for
building too. Bootstrapping can be fun.
Cheers,
Michael
On Sunday March 4 2007 09:27, Michael Koch wrote:
I have built a preliminary Debian packages for Maven 2 for people
who need it or wanna look into Maven. I did this by using the
binary distribution from upstream. You can install it by adding
deb http://people.debian.org/~mkoch/maven2/ ./
Hi
On Sun, Mar 04, 2007 at 01:03:33PM -0800, Manfred Moser wrote:
On Sunday March 4 2007 09:27, Michael Koch wrote:
I have built a preliminary Debian packages for Maven 2 for people
who need it or wanna look into Maven. I did this by using the
binary distribution from upstream. You can
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 Ubuntu. I am going to give
On Sun, Mar 04, 2007 at 11:19:31PM +0100, Arnaud Vandyck wrote:
There are tools to help packaging software and there are examples, see
http://pkg-java.debian.org
http://pkg-java.alioth.debian.org
Also, we surely need more informations that those provided by the pom.xml
And another one ...
50 matches
Mail list logo
