struts-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Burton Rhodes <burtonrho...@gmail.com>
Subject Re: Camel Case Package Names
Date Sat, 08 Sep 2012 19:12:44 GMT
Dave, if you could please post your '2Girls1Cup' package that would be
great.

On Saturday, September 8, 2012, Dave Newton wrote:

> This doesn't seem to be Struts-related at all.
>
> In any case, as Bruno says, of course camelCase package names are
> *allowed*.
>
> If the classes exist as files on the filesystem, and you're using a
> degenerate OS that doesn't believe case matters, I could see there being
> potential conflicts between the OS and Java. This is most-often encountered
> on Windows-like machines.
>
> As far as package naming convention goes, the current JLS says more or less
> the same as the one I referred to in the linked post. The first segment
> *should* be all lowercase, but does not *have* to be. It goes on to suggest
> using underscores in package names when a segment would violate Java naming
> conventions.
>
> It doesn't appear to directly reference camelCasing, but package segment
> names need only adhere to Java naming conventions--beyond that, it's at the
> user's discretion. *I* don't like camel-cased package names (or
> underscores) but if naming needs (e.g., a company like "2Girls1Cup")
> dictate a naming tweak to be legal, there's nothing in the spec that
> disallows it.
>
> Dave
>
> On Sat, Sep 8, 2012 at 9:07 AM, Bruno Borges <bruno.borges@gmail.com<javascript:;>>
> wrote:
>
> > From what I recall, they are allowed. It's just that under Windows, the
> > mess occurs... unless you are not running Windows, then I have no idea
> why
> > is that happening
> > On Sep 8, 2012 9:03 AM, "Martin Gainty" <mgainty@hotmail.com<javascript:;>>
> wrote:
> >
> > >
> > > Landing in NY with 6 hours before my next flight out i decided to
> finish
> > > off compiling and packaging the latest and greatest SAAS re-factoring
> > > I encounter this bit of package-name nastiness?
> > >
> > > Number of foreign imports: 1
> > > import: Entry[import  from realm
> > > ClassRealm[project>org.apache.axis2:axis2.eclipse.codegen.plugin:1.6.2,
> > > parent: ClassRealm[maven.api, parent: null]]]
> > > -----------------------------------------------------
> > >         at
> > >
> >
> org.apache.maven.plugin.internal.DefaultMavenPluginManager.getConfiguredMojo(DefaultMavenPluginManager.java:470)
> > >         at
> > >
> >
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:98)
> > >         ... 20 more
> > > Caused by: java.lang.NoClassDefFoundError: aQute/libg/reporter/Reporter
> > > i pull down the aqute library and start to compile here are the package
> > > names
> > > package aQute.libg.reporter;
> > >
> > > I found this post from struts-user
> > >
> > >
> >
> http://grokbase.com/p/struts/user/117b44gfqr/how-to-display-data-from-database-to-jsp-page-in-struts2
> > >
> > > The query from Dale Newfield says the package name I am compiling is
> > > camelcase and he is experiencing difficulty
> > > respondent Dave Newton said Ive seen it once in a while but majority of
> > > package names are always lowercase
> > >
> > > I cannot get my Java 1_6.0.16 compiler to compile camelcase package
> names
> > > Are camelcase packagenames allowed in Java?
> > > If so what version of  Java do i use and which parameters do I use in
> > that
> > > javac invocation to allow camelcase packagenames in a Java Compile?
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message