Craig M. asked:
>
> I thought the convention for SF-based Java projects was net.sf.<package>
> or something like that?
>
> If the code is later migrated into Struts and/or Axis, package names
> changes are pretty trivial, and shouldn't require fixing anything more
> than some import statements.
>
Taking for example the project "strutstestcase", Deryl chose the package
structure:
servletunit.struts
- as in -
servletunit.struts.MockStrutsTestCase
so the net.sf... package structure isn't strictly enforced.
And to be honest, I like the idea of starting it as "org.something" since
it helps identify the project as open source.
So, how about:
"org.axis4struts"
with Axis code in:
"org.axis4struts.axis"
and Struts code in:
"org.axis4struts.struts"
>
> > Comments?
>
> Craig
>
---------------------------------------------------------------------------
This e-mail message (including attachments, if any) is intended for the use
of the individual or entity to which it is addressed and may contain
information that is privileged, proprietary , confidential and exempt from
disclosure. If you are not the intended recipient, you are notified that
any dissemination, distribution or copying of this communication is
strictly prohibited. If you have received this communication in error,
please notify the sender and erase this e-mail message immediately.
---------------------------------------------------------------------------
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
