commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Damjan Jovanovic <damjan....@gmail.com>
Subject Re: [sanselan] how to build a release
Date Sat, 17 Dec 2011 06:05:22 GMT
On Sat, Dec 17, 2011 at 1:35 AM, Gary Gregory <garydgregory@gmail.com>wrote:

> On Fri, Dec 16, 2011 at 5:54 PM, sebb <sebbaz@gmail.com> wrote:
>
> > On 16 December 2011 20:49, Gary Gregory <garydgregory@gmail.com> wrote:
> > > On Fri, Dec 16, 2011 at 1:43 PM, sebb <sebbaz@gmail.com> wrote:
> > >
> > >> On 16 December 2011 17:27, Simone Tripodi <simonetripodi@apache.org>
> > >> wrote:
> > >> > AH yes, that's because Sanselan came from the Incubator and hasn't
> > >> > been updated yet :P
> > >>
> > >> Yes - that's good (as it happens).
> > >>
> > >> The previous (incubator) Maven release was under the groupId
> > >> org.apache.sanselan, and the package was also o.a.sanselan
> > >>
> > >> The package name has been changed already, so we can change the Maven
> > >> groupId to o.a.commons, which will automatically give Nexus access.
> > >>
> > >
> > > I see "package org.apache.sanselan" all over in
> > > https://svn.apache.org/repos/asf/commons/proper/sanselan/trunk
> > >
> > > Do I have the right project checked out?
> >
> > Oops!  Yes, you do.
> >
> > Sorry, got that wrong - I thought I had checked the current package.
> >
> > In which case, we either need to
> > * keep the package name & make another release under the old Maven
> coords,
> > or
> > * change the package to o.a.c and make a release under Maven o.a.c.
> >
>
>  IMO "change the package to o.a.c", should be done now.
>
> I'll could it unless you or anyone gets to it first, or makes other kinds
> of noises.
>
>
If a 1.0 release is necessary, I'd like to make other changes too before
that.

As for the Java 1.5 update, that would make a Java ME port harder to do,
but I'd rather have an Android port anyway.

Damjan

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message