Re: [lyo-dev] OSLC jars and dependencies

[Michael Fiedler <fiedler.mf@xxxxxxxxx>]

One other thing - exporting a Maven project from Eclipse as a runnable jar will also package all runtime dependencies.  It will not package dependencies marked as "provided".

On Tue, Apr 10, 2012 at 8:38 AM, Samuel Padgett <spadgett@xxxxxxxxxx> wrote:

Hi, Jean-Luc. I suspect Maven has something built-in to help. For instance, you should be able to use dependency:copy-dependencies mojo to get all the dependent JARs for a particular project.

http://maven.apache.org/plugins/maven-dependency-plugin/examples/copying-project-dependencies.html

Hope this helps.
--
Samuel Padgett | IBM Rational | spadgett@xxxxxxxxxx

Michael Fiedler ---04/10/2012 08:06:09 AM---Hi,  You can find the jar dependencies in the pom.xml for the projects. I'll try to get this list on

From:	Michael Fiedler <fiedler.mf@xxxxxxxxx>
To:	Lyo project developer discussions <lyo-dev@xxxxxxxxxxx>,
Date:	04/10/2012 08:06 AM
Subject:	Re: [lyo-dev] OSLC jars and dependencies
Sent by:	lyo-dev-bounces@xxxxxxxxxxx

---

Hi,  You can find the jar dependencies in the pom.xml for the projects.   I'll try to get this list on the wiki, but here it is:

OSLC4J

jsr311-api-1.1.1.jar
javax.servlet-api-3.0.1.jar
log4j-1.2.16.jar

OSLC4JJenaProvider

jena-2.6.4.jar  (will change to jena 2.7.0)
iri-0.8.jar
icu4j-4.8.1.1.jar
slf4j-api-1.6.0.jar
slf4j-log4j12-1.6.0.jar
xercesImpl-2.7.1.jar
javax.servlet-api-3.0.1.jar

OSLC4JJson4JProvider

wink-json4j-1.1.3-incubating.jar
javax.servlet-api-3.0.1.jar

OSLC4JWink

wink-j1.1.3-incubating.jar
wink-json4j-1.1.3-incubating.jar
wink-json4j-provider-1.1.3-incubating.jar
wink-client-1.1.3-incubating.jar
wink-server-1.1.3-incubating.jar
javax.servlet-api-3.0.1.jar


Regards,
Mike

On Tue, Apr 10, 2012 at 6:15 AM, Johnson, Jean-Luc <Jean-Luc.Johnson@xxxxxxxx> wrote:

Dear All,

 

I have been using the OSLC SDK these days and I realise that it could be difficult to re-use the SDK in non maven-based projects or existing projects such as RCP applications. So I come up with this suggestion. Since everybody doesn’t use the apache maven tool,  I think it will be useful  to the OSLC community if the committers could list the jar files to resolve the dependencies – done automatically by maven – to be added to the classpath of a java project.

 

Regards,

 

Jean-Luc Johnson

_______________________________________________
lyo-dev mailing list
lyo-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/lyo-dev

r
_______________________________________________
lyo-dev mailing list
lyo-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/lyo-dev

_______________________________________________
lyo-dev mailing list
lyo-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/lyo-dev

-- 
Regards,
Mike Fiedler