Hi Bjorn!

This manual step is only required since the OAuth lib is currently in 
incubator. So right now if you do not take the latest code from the source and 
build it yourself then you have to do this workaround.

Once the Oauth lib is part of the official extensions you will just be able to 
have you pom and the latest will be fetched for the Restlet build repository.

Check if you Eclipse project you created did discover the pom.xml file. If it 
did there should be an "M" icon next to your project name. If not you can right 
click on the project and Choose Maven-> Enable Dependency Management.

Since the oauth artifact is not part of any repository your maven client will 
search and find a local version since you did install it. Then you should be 
good to go.

Here is a sample what I have in my pom files.

<!-- does nothing for OAuth now but once moved from incubator it will kick in 
-->
<repository>
                        <id>restlet</id>
                        <name>Restlet public</name>
                        <url>http://maven.restlet.org/</url>
</repository>

<properties>
                <restlet.version>2.1-SNAPSHOT</restlet.version>
                
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
</properties>

<dependency>
                        <groupId>org.restlet.dev</groupId>
                        <artifactId>org.restlet.ext.oauth</artifactId>
                        <version>${restlet.version}</version>
</dependency>

<dependency>
                        <groupId>org.restlet.dev</groupId>
                        <artifactId>org.restlet.ext.openid</artifactId>
                        <version>${restlet.version}</version>
</dependency>

The OpenId is only for building Auth server side with openId as the 
authentication technology.

The UTF-8 encoding line in properties seems only be needed if you build on Mac 
OSX not to get strange character encoding warnings.

I hope this helps!

BR Stoffe

------------------------------------------------------
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2701220

Reply via email to