On 16 December 2011 23:35, Gary Gregory <garydgreg...@gmail.com> wrote:
> On Fri, Dec 16, 2011 at 5:54 PM, sebb <seb...@gmail.com> wrote:
>
>> On 16 December 2011 20:49, Gary Gregory <garydgreg...@gmail.com> wrote:
>> > On Fri, Dec 16, 2011 at 1:43 PM, sebb <seb...@gmail.com> wrote:
>> >
>> >> On 16 December 2011 17:27, Simone Tripodi <simonetrip...@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.

Fine by me.

Must also change the version to 1.0 (it's a major change) and the
Maven groupId (don't want to use the current on by accident).

Worth checking that the standard Maven layout is used too.

> Gary
>
>
>> [Whichever we choose, the current pom has the wrong Maven coords]
>>
>> I think we should probably release 1.0 under o.a.c Maven & package.
>> Fix any bugs over the next few months in 1.x, while considering if the
>> API needs adjustment, and deciding how generics should be applied.
>>
>> Then release 2,0 with generics.
>> If the API needs to be fixed, and that cannot be done without breaking
>> compat, then we also change package name and Maven id.
>>
>> > Gary
>> >
>> >
>> >>
>> >> The groupId commons-sanselan does not appear to have been used, which is
>> >> lucky.
>> >>
>> >> > On Fri, Dec 16, 2011 at 6:04 PM, Gary Gregory <garydgreg...@gmail.com
>> >
>> >> wrote:
>> >> >> It looks like the first thing that should happen before a 1.0 is a
>> >> >> repackage under o.a.c.
>> >>
>> >> >>
>> >> >> Gary
>> >> >
>> >> > http://people.apache.org/~simonetripodi/
>> >> > http://simonetripodi.livejournal.com/
>> >> > http://twitter.com/simonetripodi
>> >> > http://www.99soft.org/
>> >> >
>> >> > ---------------------------------------------------------------------
>> >> > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>> >> > For additional commands, e-mail: dev-h...@commons.apache.org
>> >> >
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>> >> For additional commands, e-mail: dev-h...@commons.apache.org
>> >>
>> >>
>> >
>> >
>> > --
>> > E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
>> > JUnit in Action, 2nd Ed: <http://goog_1249600977>http://bit.ly/ECvg0
>> > Spring Batch in Action: <http://s.apache.org/HOq>http://bit.ly/bqpbCK
>> > Blog: http://garygregory.wordpress.com
>> > Home: http://garygregory.com/
>> > Tweet! http://twitter.com/GaryGregory
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>> For additional commands, e-mail: dev-h...@commons.apache.org
>>
>>
>
>
> --
> E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
> JUnit in Action, 2nd Ed: <http://goog_1249600977>http://bit.ly/ECvg0
> Spring Batch in Action: <http://s.apache.org/HOq>http://bit.ly/bqpbCK
> Blog: http://garygregory.wordpress.com
> Home: http://garygregory.com/
> Tweet! http://twitter.com/GaryGregory

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Reply via email to