really magic....
Karsten tried my Source Files and they work well (for him)
I did some more tests and found out, that Hybridlabs calculates the
Insert Point of Import Statements wrong,
after inserting 4 empty Lines before /**
the Imports are correct placed before /**
I can live with this workaround because the JDT JavaBeautifier running
as next step removes these lines
perhaps the reason of wrong position is something like
OS (I'm using OSX)
FileEncoding (ISO 8859-I)
or something like CR, CR/LF....
but as said: my workaround works for me, so I can continue tomorrow my
move from oaw to eclipse
ekke
ekke schrieb:
I'm in the process of moving my huge projects from oaw.org to eclipse.
I need Hybridlabs in my projects as beautifier (only for Import
Statements)
oaw 4.3.1 code:
<postprocessor
class="org.hybridlabs.source.formatter.JavaImportBeautifier"
conventionFilePath="src/eg-convention.xml"
organizeImports="true"
format="false"/>
<postprocessor
class="org.openarchitectureware.xpand2.output.JavaBeautifier"
configFile="format_profile.xml"/>
---------------------------
changed from hybridlabs 1.1.9 to hybridlabs-beautifier-2.0.0-SNAPSHOT
from google code project.
now Hybridlabs generates the Import Statements inside the JavaDoc
directly behind /** instead before.
something like this:
package org.ekkehard.abc.entitybean.adress;
/**
import java.beans.PropertyChangeListener;
import java.beans.PropertyChangeSupport;
instead of
package org.ekkehard.abc.entitybean.adress;
import java.beans.PropertyChangeListener;
import java.beans.PropertyChangeSupport;
/**
this blocks my move.
I have opened an Issue on Google Code
thx if someone can help
ekke
_______________________________________________
oaw-wg mailing list
oaw-wg@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/oaw-wg
|
