Source code package name changes

[Les Hazlewood <lh...@apache.org>]

I think it would be smart to change from org.jsecurity.* to org.apache.ki.*
only immediately before our first Apache release.  This allows our existing
user community to avoid changing source code dependencies until absolutely
necessary.

I'm recommending this because there are a few people that regularly build
snapshots for trunk for integration testing (Grails plugin, et. al), and I'd
like to avoid any headache for them until absolutely required.

Would this be ok?  Any objections?  What does everyone think?

Re: Source code package name changes

[Les Hazlewood <lh...@apache.org>]

Cool Kalle, thanks for the update.  Believe me, if I run in to any bumps,
I'll definitely reach out to you if I have any issues at all.

Also, once all the directory changes are done, I'd appreciate any feedback
on the poms to see if we're missing something or if you have any tricks that
we haven't covered yet.

Cheers,

Les

On Fri, Mar 6, 2009 at 2:58 PM, Kalle Korhonen
<ka...@gmail.com>wrote:

> While I used the issue I opened as an example, I didn't mean that
> specifically. It's relatively easy to do search and replace on the dir
> paths
> in the patch, but even simpler to apply them before. I got lots of
> experience with Maven and releasing via Maven so let me know if I can help
> (though granted, the kind of package and source directory refactoring is
> easier to do with direct commits).
>
> Kalle
>
>
> On Fri, Mar 6, 2009 at 11:32 AM, Les Hazlewood <lhazlewood@apache.org
> >wrote:
>
> > I can do that after moving things over to the Maven standard directory
> > structure (which will unfortunately validate the patch).  But it is easy
> to
> > recreate after the move anyway...
> >
> > On Fri, Mar 6, 2009 at 12:43 PM, Kalle Korhonen
> > <ka...@gmail.com>wrote:
> >
> > > Before renaming the packages, one of the devs should go through the
> JIRAs
> > > and apply the patches that are safe and non-controversial (at least
> > > https://issues.apache.org/jira/browse/KI-42 comes to mind). Later,
> it's
> > > going to be more work for everybody.
> > >
> > > Kalle
> > >
> > >
> > > On Fri, Mar 6, 2009 at 9:03 AM, Emmanuel Lecharny <
> elecharny@apache.org
> > > >wrote:
> > >
> > > > David Jencks wrote:
> > > >
> > > >>
> > > >> On Mar 6, 2009, at 8:30 AM, Les Hazlewood wrote:
> > > >>
> > > >>  I think it would be smart to change from org.jsecurity.* to
> > > >>> org.apache.ki.*
> > > >>> only immediately before our first Apache release.  This allows our
> > > >>> existing
> > > >>> user community to avoid changing source code dependencies until
> > > >>> absolutely
> > > >>> necessary.
> > > >>>
> > > >>> I'm recommending this because there are a few people that regularly
> > > build
> > > >>> snapshots for trunk for integration testing (Grails plugin, et.
> al),
> > > and
> > > >>> I'd
> > > >>> like to avoid any headache for them until absolutely required.
> > > >>>
> > > >>> Would this be ok?  Any objections?  What does everyone think?
> > > >>>
> > > >>
> > > >> I'm inclined to think that changing the package names will result in
> a
> > > >> great deal of breakage all over the place and doing it as soon as
> > > possible
> > > >> is more likely to result in a working first release.
> > > >>
> > > > Yeah, I share David vision... Recalls me the last time I differed a
> > > dentist
> > > > appointment :/
> > > >
> > > > --
> > > > --
> > > > cordialement, regards,
> > > > Emmanuel Lécharny
> > > > www.iktek.com
> > > > directory.apache.org
> > > >
> > > >
> > > >
> > >
> >
>

Re: Source code package name changes

[Kalle Korhonen <ka...@gmail.com>]

While I used the issue I opened as an example, I didn't mean that
specifically. It's relatively easy to do search and replace on the dir paths
in the patch, but even simpler to apply them before. I got lots of
experience with Maven and releasing via Maven so let me know if I can help
(though granted, the kind of package and source directory refactoring is
easier to do with direct commits).

Kalle


On Fri, Mar 6, 2009 at 11:32 AM, Les Hazlewood <lh...@apache.org>wrote:

> I can do that after moving things over to the Maven standard directory
> structure (which will unfortunately validate the patch).  But it is easy to
> recreate after the move anyway...
>
> On Fri, Mar 6, 2009 at 12:43 PM, Kalle Korhonen
> <ka...@gmail.com>wrote:
>
> > Before renaming the packages, one of the devs should go through the JIRAs
> > and apply the patches that are safe and non-controversial (at least
> > https://issues.apache.org/jira/browse/KI-42 comes to mind). Later, it's
> > going to be more work for everybody.
> >
> > Kalle
> >
> >
> > On Fri, Mar 6, 2009 at 9:03 AM, Emmanuel Lecharny <elecharny@apache.org
> > >wrote:
> >
> > > David Jencks wrote:
> > >
> > >>
> > >> On Mar 6, 2009, at 8:30 AM, Les Hazlewood wrote:
> > >>
> > >>  I think it would be smart to change from org.jsecurity.* to
> > >>> org.apache.ki.*
> > >>> only immediately before our first Apache release.  This allows our
> > >>> existing
> > >>> user community to avoid changing source code dependencies until
> > >>> absolutely
> > >>> necessary.
> > >>>
> > >>> I'm recommending this because there are a few people that regularly
> > build
> > >>> snapshots for trunk for integration testing (Grails plugin, et. al),
> > and
> > >>> I'd
> > >>> like to avoid any headache for them until absolutely required.
> > >>>
> > >>> Would this be ok?  Any objections?  What does everyone think?
> > >>>
> > >>
> > >> I'm inclined to think that changing the package names will result in a
> > >> great deal of breakage all over the place and doing it as soon as
> > possible
> > >> is more likely to result in a working first release.
> > >>
> > > Yeah, I share David vision... Recalls me the last time I differed a
> > dentist
> > > appointment :/
> > >
> > > --
> > > --
> > > cordialement, regards,
> > > Emmanuel Lécharny
> > > www.iktek.com
> > > directory.apache.org
> > >
> > >
> > >
> >
>

Re: Source code package name changes

[Les Hazlewood <lh...@apache.org>]

I can do that after moving things over to the Maven standard directory
structure (which will unfortunately validate the patch).  But it is easy to
recreate after the move anyway...

On Fri, Mar 6, 2009 at 12:43 PM, Kalle Korhonen
<ka...@gmail.com>wrote:

> Before renaming the packages, one of the devs should go through the JIRAs
> and apply the patches that are safe and non-controversial (at least
> https://issues.apache.org/jira/browse/KI-42 comes to mind). Later, it's
> going to be more work for everybody.
>
> Kalle
>
>
> On Fri, Mar 6, 2009 at 9:03 AM, Emmanuel Lecharny <elecharny@apache.org
> >wrote:
>
> > David Jencks wrote:
> >
> >>
> >> On Mar 6, 2009, at 8:30 AM, Les Hazlewood wrote:
> >>
> >>  I think it would be smart to change from org.jsecurity.* to
> >>> org.apache.ki.*
> >>> only immediately before our first Apache release.  This allows our
> >>> existing
> >>> user community to avoid changing source code dependencies until
> >>> absolutely
> >>> necessary.
> >>>
> >>> I'm recommending this because there are a few people that regularly
> build
> >>> snapshots for trunk for integration testing (Grails plugin, et. al),
> and
> >>> I'd
> >>> like to avoid any headache for them until absolutely required.
> >>>
> >>> Would this be ok?  Any objections?  What does everyone think?
> >>>
> >>
> >> I'm inclined to think that changing the package names will result in a
> >> great deal of breakage all over the place and doing it as soon as
> possible
> >> is more likely to result in a working first release.
> >>
> > Yeah, I share David vision... Recalls me the last time I differed a
> dentist
> > appointment :/
> >
> > --
> > --
> > cordialement, regards,
> > Emmanuel Lécharny
> > www.iktek.com
> > directory.apache.org
> >
> >
> >
>

Re: Source code package name changes

[Kalle Korhonen <ka...@gmail.com>]

Before renaming the packages, one of the devs should go through the JIRAs
and apply the patches that are safe and non-controversial (at least
https://issues.apache.org/jira/browse/KI-42 comes to mind). Later, it's
going to be more work for everybody.

Kalle


On Fri, Mar 6, 2009 at 9:03 AM, Emmanuel Lecharny <el...@apache.org>wrote:

> David Jencks wrote:
>
>>
>> On Mar 6, 2009, at 8:30 AM, Les Hazlewood wrote:
>>
>>  I think it would be smart to change from org.jsecurity.* to
>>> org.apache.ki.*
>>> only immediately before our first Apache release.  This allows our
>>> existing
>>> user community to avoid changing source code dependencies until
>>> absolutely
>>> necessary.
>>>
>>> I'm recommending this because there are a few people that regularly build
>>> snapshots for trunk for integration testing (Grails plugin, et. al), and
>>> I'd
>>> like to avoid any headache for them until absolutely required.
>>>
>>> Would this be ok?  Any objections?  What does everyone think?
>>>
>>
>> I'm inclined to think that changing the package names will result in a
>> great deal of breakage all over the place and doing it as soon as possible
>> is more likely to result in a working first release.
>>
> Yeah, I share David vision... Recalls me the last time I differed a dentist
> appointment :/
>
> --
> --
> cordialement, regards,
> Emmanuel Lécharny
> www.iktek.com
> directory.apache.org
>
>
>

Re: Source code package name changes

[Emmanuel Lecharny <el...@apache.org>]

David Jencks wrote:
>
> On Mar 6, 2009, at 8:30 AM, Les Hazlewood wrote:
>
>> I think it would be smart to change from org.jsecurity.* to 
>> org.apache.ki.*
>> only immediately before our first Apache release.  This allows our 
>> existing
>> user community to avoid changing source code dependencies until 
>> absolutely
>> necessary.
>>
>> I'm recommending this because there are a few people that regularly 
>> build
>> snapshots for trunk for integration testing (Grails plugin, et. al), 
>> and I'd
>> like to avoid any headache for them until absolutely required.
>>
>> Would this be ok?  Any objections?  What does everyone think?
>
> I'm inclined to think that changing the package names will result in a 
> great deal of breakage all over the place and doing it as soon as 
> possible is more likely to result in a working first release.
Yeah, I share David vision... Recalls me the last time I differed a 
dentist appointment :/

-- 
--
cordialement, regards,
Emmanuel Lécharny
www.iktek.com
directory.apache.org

Re: Source code package name changes

["Alan D. Cabrera" <li...@toolazydogs.com>]

On Mar 6, 2009, at 6:11 PM, Craig L Russell wrote:

>
> On Mar 6, 2009, at 9:01 AM, Les Hazlewood wrote:
>
>> Hi David,
>>
>> That's a good point - I hadn't really thought of it that way.  I'm  
>> happy
>> with us converting the package names at any time based on how  
>> people feel.
>
> I'm not a developer, but I'd also recommend that the name change and  
> the switch to use Maven would best be done quickly.
>
> It's a group decision. I'd like others on the team to also express  
> their opinions to see if there is consensus as to how (quickly) to  
> proceed.

I'll also update the Maven POMs this weekend as well.  I can also do  
the packaging if no one else wants to do it.


Regards,
Alan


>
>
> Craig
>
>
>>
>>
>> And yes, I think that the dev team as a whole feels that, given that
>> JSecurity's build environment is not complex at all, that Maven  
>> would be
>> good to incorporate asap for the inter-team benefits in the ASF as  
>> well as
>> for our user community.  Our existing releases aren't published to  
>> a Maven
>> repo yet, but that will change shortly, I'm sure.
>>
>> Best,
>>
>> Les
>>
>> On Fri, Mar 6, 2009 at 11:54 AM, David Jencks  
>> <da...@yahoo.com>wrote:
>>
>>>
>>> On Mar 6, 2009, at 8:30 AM, Les Hazlewood wrote:
>>>
>>> I think it would be smart to change from org.jsecurity.* to
>>>> org.apache.ki.*
>>>> only immediately before our first Apache release.  This allows our
>>>> existing
>>>> user community to avoid changing source code dependencies until  
>>>> absolutely
>>>> necessary.
>>>>
>>>> I'm recommending this because there are a few people that  
>>>> regularly build
>>>> snapshots for trunk for integration testing (Grails plugin, et.  
>>>> al), and
>>>> I'd
>>>> like to avoid any headache for them until absolutely required.
>>>>
>>>> Would this be ok?  Any objections?  What does everyone think?
>>>>
>>>
>>> I'm inclined to think that changing the package names will result  
>>> in a
>>> great deal of breakage all over the place and doing it as soon as  
>>> possible
>>> is more likely to result in a working first release.
>>>
>>> I'm not sure if you are using maven style artifact ids.... I hope  
>>> so... but
>>> these will be changing too at the same time so at least with maven  
>>> built
>>> projects people will still be getting the old package named jars  
>>> until they
>>> explicitly upgrade.
>>>
>>> thanks
>>> david jencks
>>>
>>>
>>>
>
> Craig L Russell
> Architect, Sun Java Enterprise System http://db.apache.org/jdo
> 408 276-5638 mailto:Craig.Russell@sun.com
> P.S. A good JDO? O, Gasp!
>

Re: Source code package name changes

[Craig L Russell <Cr...@Sun.COM>]

On Mar 6, 2009, at 9:01 AM, Les Hazlewood wrote:

> Hi David,
>
> That's a good point - I hadn't really thought of it that way.  I'm  
> happy
> with us converting the package names at any time based on how people  
> feel.

I'm not a developer, but I'd also recommend that the name change and  
the switch to use Maven would best be done quickly.

It's a group decision. I'd like others on the team to also express  
their opinions to see if there is consensus as to how (quickly) to  
proceed.

Craig


>
>
> And yes, I think that the dev team as a whole feels that, given that
> JSecurity's build environment is not complex at all, that Maven  
> would be
> good to incorporate asap for the inter-team benefits in the ASF as  
> well as
> for our user community.  Our existing releases aren't published to a  
> Maven
> repo yet, but that will change shortly, I'm sure.
>
> Best,
>
> Les
>
> On Fri, Mar 6, 2009 at 11:54 AM, David Jencks  
> <da...@yahoo.com>wrote:
>
>>
>> On Mar 6, 2009, at 8:30 AM, Les Hazlewood wrote:
>>
>> I think it would be smart to change from org.jsecurity.* to
>>> org.apache.ki.*
>>> only immediately before our first Apache release.  This allows our
>>> existing
>>> user community to avoid changing source code dependencies until  
>>> absolutely
>>> necessary.
>>>
>>> I'm recommending this because there are a few people that  
>>> regularly build
>>> snapshots for trunk for integration testing (Grails plugin, et.  
>>> al), and
>>> I'd
>>> like to avoid any headache for them until absolutely required.
>>>
>>> Would this be ok?  Any objections?  What does everyone think?
>>>
>>
>> I'm inclined to think that changing the package names will result  
>> in a
>> great deal of breakage all over the place and doing it as soon as  
>> possible
>> is more likely to result in a working first release.
>>
>> I'm not sure if you are using maven style artifact ids.... I hope  
>> so... but
>> these will be changing too at the same time so at least with maven  
>> built
>> projects people will still be getting the old package named jars  
>> until they
>> explicitly upgrade.
>>
>> thanks
>> david jencks
>>
>>
>>

Craig L Russell
Architect, Sun Java Enterprise System http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!

Re: Source code package name changes

[Les Hazlewood <lh...@apache.org>]

Hi David,

That's a good point - I hadn't really thought of it that way.  I'm happy
with us converting the package names at any time based on how people feel.

And yes, I think that the dev team as a whole feels that, given that
JSecurity's build environment is not complex at all, that Maven would be
good to incorporate asap for the inter-team benefits in the ASF as well as
for our user community.  Our existing releases aren't published to a Maven
repo yet, but that will change shortly, I'm sure.

Best,

Les

On Fri, Mar 6, 2009 at 11:54 AM, David Jencks <da...@yahoo.com>wrote:

>
> On Mar 6, 2009, at 8:30 AM, Les Hazlewood wrote:
>
>  I think it would be smart to change from org.jsecurity.* to
>> org.apache.ki.*
>> only immediately before our first Apache release.  This allows our
>> existing
>> user community to avoid changing source code dependencies until absolutely
>> necessary.
>>
>> I'm recommending this because there are a few people that regularly build
>> snapshots for trunk for integration testing (Grails plugin, et. al), and
>> I'd
>> like to avoid any headache for them until absolutely required.
>>
>> Would this be ok?  Any objections?  What does everyone think?
>>
>
> I'm inclined to think that changing the package names will result in a
> great deal of breakage all over the place and doing it as soon as possible
> is more likely to result in a working first release.
>
> I'm not sure if you are using maven style artifact ids.... I hope so... but
> these will be changing too at the same time so at least with maven built
> projects people will still be getting the old package named jars until they
> explicitly upgrade.
>
> thanks
> david jencks
>
>
>

Re: Source code package name changes

[David Jencks <da...@yahoo.com>]

On Mar 6, 2009, at 8:30 AM, Les Hazlewood wrote:

> I think it would be smart to change from org.jsecurity.* to  
> org.apache.ki.*
> only immediately before our first Apache release.  This allows our  
> existing
> user community to avoid changing source code dependencies until  
> absolutely
> necessary.
>
> I'm recommending this because there are a few people that regularly  
> build
> snapshots for trunk for integration testing (Grails plugin, et. al),  
> and I'd
> like to avoid any headache for them until absolutely required.
>
> Would this be ok?  Any objections?  What does everyone think?

I'm inclined to think that changing the package names will result in a  
great deal of breakage all over the place and doing it as soon as  
possible is more likely to result in a working first release.

I'm not sure if you are using maven style artifact ids.... I hope  
so... but these will be changing too at the same time so at least with  
maven built projects people will still be getting the old package  
named jars until they explicitly upgrade.

thanks
david jencks