Our recommended package naming conventions are: http://appfuse.org/display/APF/FAQ#FAQ-packagenaming
However, I've seen people change this to be more domain specific (rather than pattern specific) when creating large projects. Personally, I think it might be better to create several small projects that interoperate rather than one huge project. Matt On Wed, Jul 30, 2008 at 5:27 AM, Kinski <[EMAIL PROTECTED]> wrote: > > When creating a Modular application the following is contained in the > contents of a read me file which is created... > > NOTE: Maven is currently unable to fully support multi-module archetypes. > Because of this limitation, the Java files are in the default package of > each module. It's recommended you follow AppFuse conventions for package > naming when you create your own source files. > > Please could you clarify why this is recommended? > > (I don't mean in relation Maven limitations but rather in terms of Appfuse > class use tucked away in the jar file) > > ----- > Regards, > > Matthew > -- > View this message in context: > http://www.nabble.com/AppFuse-conventions-for-package-naming-tp18731156s2369p18731156.html > Sent from the AppFuse - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
