[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[List Home]
|
[tycho-user] Tycho in a Client Server Environment
|
- From: Sebastian Janisch <sebastian.janisch@xxxxxxxxxxxxxx>
- Date: Tue, 6 Dec 2011 15:54:17 +0100
- Delivered-to: tycho-user@eclipse.org
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=from:content-type:content-transfer-encoding:subject:date:message-id :to:mime-version:x-mailer; bh=Q2LJesJOJkx9AnHvC8O/xmKc5KhatDKNL8WhVFqpySY=; b=d6n7fgOwAYVTe252PtwUBsnOuxaEvlaer/u7xEi4QnXpGos5LUQpb9pCoGbYXBBWnw +mQ5zeKQOjjfCLKs5mZy2hNTtKB8UvlP9ODuJNsCzZJk1LV1NN6IWqTanpi2QmAqCiIy F3bnngcWljipP+deMONNe24iia++E6fMlR1Hk=
Hey,
I am facing some uncertainties regarding the use of Tycho in a client server environment.
Here is the setting.
The client is built in Eclipse RCP. The server is a plain maven webapp, that sets up webservices consumed by the client.
Now the tricky part: the domain projects need to be deployed on both server and client. What we have so far are Domain-Maven Projects and we use Apache Felix to convert them into OSGI Bundles. This approach works, but is very cumbersome. Apart from that, we do not have a headless build for the client yet.
I have played around with Tycho today. Feels pretty neat to me. I am still uncertain as to how to work around the problem with the domain projects.
Expert advice would be much appreciated.
Best regards
Sebastian Janisch