Yeah I guess this won't work since when running local in the web/app
module there is no way for maven to activate the profile from
extensions/arcsde. I guess this means that maven won't active profiles
unless the module is in the reactor, and not just referenced from the
local maven repository. So this is an issue with all extensions that
have a profile that activate additional libs like oracle and sqlserver.
Gabriel Roldan wrote:
> I just committed a patch to extension/arcsde/pom.xml so the sdeLibs
> profile in both the extension and web/app names it the same.
> But it seems I can't get rid of the sdeLibs profile declaration in
> web/app though that's what I first thought too.
>
> If I do, running mvn jetty:run -Parcsde,sdeLibs does not work, I get a
> NoClassDefFoundError: com/esri/sde/sdk/client/SeConnection when trying
> to access an sde raster, or a disabled datastore at startup
>
> Do you know if it is possible to inherit the sdeLibs profile from the
> extension at all when running jetty? and if so, how?
>
> Cheers,
> Gabriel
>
> Andrea Aime wrote:
>> Hi,
>> I'm looking into the sdeLibs profiles contained in the
>> sde extension and in the web-app modules.
>>
>> The one in sde extension says:
>>
>> <profile>
>> <id>sdeLibs</id>
>> <dependencies>
>> <dependency>
>> <groupId>com.esri</groupId>
>> <artifactId>jsde_sdk</artifactId>
>> <version>${sde.version}</version>
>> </dependency>
>> <dependency>
>> <groupId>com.esri</groupId>
>> <artifactId>jsde_jpe_sdk</artifactId>
>> <version>${sde.version}</version>
>> </dependency>
>> </dependencies>
>> </profile>
>>
>> whilst web-app contains:
>>
>> <profile>
>> <id>arcsde</id>
>> <dependencies>
>> <dependency>
>> <groupId>org.geoserver.extension</groupId>
>> <artifactId>arcsde</artifactId>
>> <version>2.0.2-SNAPSHOT</version>
>> </dependency>
>> </dependencies>
>> </profile>
>> <profile>
>> <id>sdeLibs</id>
>> <dependencies>
>> <dependency>
>> <groupId>com.esri</groupId>
>> <artifactId>jsde_sdk</artifactId>
>> <version>${sde.version}</version>
>> </dependency>
>> <dependency>
>> <groupId>com.esri</groupId>
>> <artifactId>jsde_jpe_sdk</artifactId>
>> <version>${sde.version}</version>
>> </dependency>
>> <dependency>
>> <groupId>com.ibm.icu</groupId>
>> <artifactId>icu4j</artifactId>
>> <version>3.4.4</version>
>> </dependency>
>> </dependencies>
>> </profile>
>>
>> Notice how the jpe artifact ides are different.
>> Plus, is there any need to duplicate the sdeLibs profile?
>> It's used in conjuction with the arcsde profile so in theory
>> the declarations inside extensions/arcsde/pom.xml should
>> be sufficient, no?
>>
>> The result of the current situation is that the projects
>> generated look for both versions of the jpe jar.
>>
>> Cheers
>> Andrea
>>
>>
>
>
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
