views:

129

answers:

2

I am taking on a project where all the Exceptions have been placed in a separate package com.myco.myproj.exceptions.

Is this good practice?

+12  A: 

I would expect the exceptions for a package to exist within that package. e.g.

com.oopsconsultancy.models.pricing

would contain pricing models and related exceptions. Anything else seems a bit counter-intuitive.

Brian Agnew
+1: Exception is co-located with the things that cause the Exception.
S.Lott
+8  A: 

It is a bad practice.

It is a coincidental grouping. Packages should be coherent. Don't group exceptions, interfaces, enum, abstract classes, etc., into their own package. Group related concepts instead.

Tom Hawtin - tackline