maven2 in svn

[Paul Cager]

On Wed, May 30, 2007 8:19 am, Trygve Laugstøl wrote:
> Paul Cager wrote:
>> Paul Cager wrote:
>>> On Mon, May 28, 2007 10:59 am, Trygve Laugstøl wrote:
>>>> Paul Cager wrote:
>>>>> By the way, I've hit a few problems with maven-ant-helper. Do you
>>>>> mind
>>>>> if I commit a few changes?
>>>> Sure, go ahead. We're a team after all :) Just make sure you apply the
>>>> patch I submitted last night as that fixes a few issues.
>>> I'd forgotten about the maven-ant-helper patches. I'll apply them and
>>> see if the problems go away.
>>
>> Trygve,
>>
>> I've now committed your patch to svn, and it fixes the problems I were
>> experiencing. I made one small tweak - changing plexus-utils.jar to
>> libplexus-utils.jar (we should add another symlink next time we upload
>> plexus-utils).
> 
> I though that it was supposed to be "plexus-utils.jar" and that the
> libplexus-utils source package should go away?

Yes it should be "plexus-utils.jar". I changed it just as a temporary
measure until the libplexus-utils package could be fixed.

Its rather complicated, and it's all my fault! Let me explain:

I created svn directory plexus-utils not realising there was already an
old "libplexus-utils" svn directory (and package in main).

When I realised my mistake I started to edit "libplexus-utils" instead.
But I forgot to delete "plexus-utils".

I introduced a bug in libplexus-utils such that the Jar is named
"libplexus-utils.jar".

You then edited svn plexus-utils, changing release (1.4.1+svn6048-1) to
(1.4.1-1).

So I guess we should:

  * Copy your changes from plexus-utils to libplexus-utils.
  * Delete the plexus-utils svn directory.

There's one more problem: we'll have to convince dak that your package
is newer than the one already in unstable. I'm not sure of the best way
to do this:

  * Use an epoch (and be stuck with it forever).
  * Fiddle the version number to (e.g.) 1.4.1.1debian
  * Create a separate source package, maven-plexus-utils.
  * Change the package so that the orig tarball contains 2 versions of
the code, and creates two versions of the Jar (yuk).

Any ideas?