#1001457
- Created on2013-01-21 13:05
- Reported by
- StatusWon't Fix
- PriorityNormal (3)
- Assigned to-
- Milestone
- Plan Level-
- Due Date-
Organize imports should keep top-level imports and non-top-level imports separated
When I have
and then I do
as a shorthand for
I do not want such shorthand imports to mixed together with the ordinary, top-level imports, because that makes the imports more confusing to read.
package com.company.fooand then I do
import bar.Thingas a shorthand for
import com.company.foo.bar.ThingI do not want such shorthand imports to mixed together with the ordinary, top-level imports, because that makes the imports more confusing to read.
Leave a comment
on 2015-09-23 04:31 *
By wpopielarski769697
Version changed from 2.1.0-M3-29 to 4.1.1
Milestone set to Lithium 4.2.1
Move ticket to next milestone.
on 2016-09-19 04:26 *
By wpopielarski769697
general strategy is to use full package path unless import is done from same package as declared in file or import is done from stable identifier.
