Description Juergen Kremp 2002-11-29 03:53:30 EST

Version: 2.0.2
Build id: 200211071448


Dear experts,

I have a situation where automatical adding of an import statement creates 
syntactically incorrect code. 

My code initially has these import statements:

import java.io.File;

import com.sap.engine.frame.ApplicationFrameAdaptor;
import com.sap.engine.frame.ApplicationServiceContext;
import com.sap.engine.frame.ServiceException;
import com.sap.engine.frame.ServiceRuntimeException;
import com.sap.engine.frame.core.configuration.ConfigurationHandler;
import com.sap.security.api.saml.service.LoggingCategories;
import com.sap.security.api.saml.service.exception.SAMLServiceException;
import com
    .sap
    .security
    .core
    .server
    .saml
    .service
    .configuration
    .SAMLConfiguration;
import com.sap.tc.logging.Location;
import com.sap.tc.logging.PropertiesConfigurator;

Note that I use the code formatter and have a line width of 80 maximum. The 
code above is the result of automatic code formatiing.

Now I let the system add an import for the following class:

  com.sap.security.core.server.util0.LogUtil


The result is this:

import java.io.File;

import com.sap.engine.frame.ApplicationFrameAdaptor;
import com.sap.engine.frame.ApplicationServiceContext;
import com.sap.engine.frame.ServiceException;
import com.sap.engine.frame.ServiceRuntimeException;
import com.sap.engine.frame.core.configuration.ConfigurationHandler;
import com.sap.security.api.saml.service.LoggingCategories;
import com.sap.security.api.saml.service.exception.SAMLServiceException;
import com
import com.sap.security.core.server.util0.LogUtil;
    .sap
    .security
    .core
    .server
    .saml
    .service
    .configuration
    .SAMLConfiguration;
import com.sap.tc.logging.Location;
import com.sap.tc.logging.PropertiesConfigurator;



It seems that the algorithm that creates the order of imports by alphabet has 
problems with the import statements altered by the code formatter.


Juergen