Trails

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Won't Fix
• Affects Version/s: None
• Fix Version/s: None
• Component/s: trails-core
• Labels:

  None

I'm using Trails with a model that is also used by another application. Since I use some Trails annotations, the Maven module that contains the entities must have a dependency on trails-core. This introduces lots of transitive dependencies that are not used by the other application. Of course I can use exclusions to get exactly the dependencies I want, but this is fairly ugly.

Ideally the annotations defined by Trails should be in their own Maven artifact that has no dependencies on other Trails modules. I think this could be easily done, except for an issue with @DescriptorAnnotation which links the annotation to the annotation handler (which obviously should stay in trails-core). This could be solved by using the class name instead of the class.

• Assignee:

  Unassigned

  Reporter:

  Andreas Veithen

• Created:

  23/Sep/09 6:56 AM

  Updated:

  14/Oct/09 11:06 AM

  Resolved:

  14/Oct/09 11:06 AM