Ok, maybe I'm interpreting something wrong, but I believe I now should
be able to go to GeoTools 2.3.x and run 'mvn install' with maven 2.0.4
with no -Pnojai and no JAI installed and it should work? Or was this
change just made on trunk?
Because I just checked out gt and ran mvn install on 2.3.x and it failed
with jai stuff. If this could work then that would be great.
thanks,
Chris
Martin Desruisseaux wrote:
Hello Adrian
Adrian Custer a écrit :
You are playing fast and loose with the build system again. I hope
nothing breaks with these changes but am skeptical about the never
ending saga of the nojai profile.
"nojai" do not exists anymore. I made the "nojai" profile permanent. This topic
was raised on the mailing list last week. If I remember right, we also raised
the topic in a IRC meeting a few weeks ago (but I'm not completly sure).
Why are you targeting maven 2.0.6? I thought gt had settled on 2.0.5.
Are these changes needed only for 2.0.6 or needed more generally?
The "nojai" profile was mandatory for Maven 2.0.6, and optional for Maven 2.0.5
and 2.0.4 (providing that the user installed JAI in his jre/lib/ext directory).
Maven 2.0.6 is stricter about classpath than Maven 2.0.5 was; it ignores totally
the content of jre/lib/ext. So the standard build (without "nojai" profile) is
useless with Maven 2.0.6.
The "nojai" profile was added in order to avoid the "symbol not found:
javax.media.jai.whatever" compiler error that numerous users meet. Prior to the
change I just made, the user had to specify the "-Pnojai" flag explicitly. Now
they don't need to specify this flag anymore.
Again, this is in reaction to the fact that "mvn install" without the "-Pnojai"
flag do not work anymore starting with Maven 2.0.6. So I though that it is
better to make the "nojai" profile permanent.
Is this the end of the road for the nojai profile? If so, what's the end
result for users: can they simply skip installing in the vm now?
User don't need to install JAI for building and testing with Maven. However they
still need to install JAI for running their own application with Geotools. This
is because JAI is declared with "provided" scope in Maven, meaning that it is
expected to already exists on the target desktop.
"provided" was the scope declared by the "nojai" profile and I didn't changed
that for "jai_core". I downgraded "jai_codec" from "provided" to "test" scope
when it was suffisient for Maven build. It make no difference for deployed
applications.
Martin
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Geotools-devel mailing list
Geotools-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel
--
Chris Holmes
The Open Planning Project
http://topp.openplans.org
begin:vcard
fn:Chris Holmes
n:Holmes;Chris
org:The Open Planning Project
adr:;;349 W. 12th Street, #3;New York;NY;10014;USA
email;internet:[EMAIL PROTECTED]
title:Managing Director, Strategic Development
x-mozilla-html:FALSE
url:http://topp.openplans.org
version:2.1
end:vcard
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Geotools-devel mailing list
Geotools-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel
