[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [tycho-user] Getting started
|
I fixed the dead link on
https://www.eclipse.org/tycho/documentation.php
thanks for notifying.
Jan
From: tycho-user-bounces@xxxxxxxxxxx [mailto:tycho-user-bounces@xxxxxxxxxxx] On Behalf Of Jeremie Bresson
Sent: Dienstag, 16. Dezember 2014 08:11
To: Tycho user list
Subject: Re: [tycho-user] Getting started
Hi,
I think that the EclipseCon 2013 website is experiencing some URL rewrite errors, but everything is still online:
* EclipseCon 2013:
Building Eclipse Plug-ins and RCP Applications with Tycho
https://www.eclipsecon.org/2013/node/1277.html
* EclipseCon NA 2014:
Building Eclipse Plug-ins and RCP Applications with Tycho
https://www.eclipsecon.org/na2014/session/building-eclipse-plug-ins-and-rcp-applications-tycho
* GitHub repo:
https://github.com/jsievers/tycho-demo
(It would be nice if someone updates this demo application to the latest tycho version)
I hope it helps.
Jeremie.
From: tycho-user-bounces@xxxxxxxxxxx [mailto:tycho-user-bounces@xxxxxxxxxxx] On Behalf Of Timothy Vogel
Sent: Montag, 15. Dezember 2014 20:17
To: tycho-user@xxxxxxxxxxx
Subject: [tycho-user] Getting started
I am looking to switch from manual PDE builds to using Tycho. My targets are RCP applications and OSGi server bundles. Two questions:
1) What is the recommended way to get started for a non-maven user like me?
The wiki documentation page refers to a EclipseCon Tyco tutorial but it is a dead link. Google returned a result for EclipseCon tutorial but it had no working examples, only high level information.
2) Can a single Tycho build resolve dependencies from both a target environment and from a maven/nexus repository?
Example: An RCP application that uses Hibernate JPA as persistence engine. Hibernate does not maintain a p2 repo so I can't easily include it in target environment but can get it easily from standard maven repo. RCP does not maintain a maven repo (that I know of) but obviously does maintain p2 repo.
Thanks for your time,
Timothy Vogel