Saul Farber a écrit :
> Anywhere that one uses a construct like this:
>
> public static final int TYPE_SMALLINT = 0;
>
> For example, in SeColumnDefinition.java, I *think* java compiles the
> value of a public static final <primitive> right into the code.
I confirm, this is clearly stated in the Sun's Java Language Specification.
This
means that if we want to distribute the Geotools SDE module, we really need to
compile it on a machine using the real SDE JAR, not the dummy one...
Right now the dummy JAR is "hard coded" in the pom.xml file; someone wanting to
build against the SDE JAR need to uncomment a specified section of the pom.xml
file. We should probably modify the pom.xml file in order to create a profile
instead, so a release manager with real SDE jar could build using this profile
instead of modifying locally their pom.xml file.
> Ok, so I'd suggest that we remove the "final" modifier from all the
> public static constants in the SDE Java API dummy sources. Otherwise
> stuff won't really work the way we want it to!
Nice workaround, I didn't though about that :). But a Maven profile instead of
current commented-out dependency would probably still be nice.
Martin.
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
