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
<[email protected]>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:[email protected]
P.S. A good JDO? O, Gasp!
