Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Archived » Maven Integration (M2E) » Project struture
Project struture [message #23730] Wed, 25 March 2009 07:29 Go to next message
Patrik Schalin is currently offline Patrik Schalin
Messages: 2
Registered: July 2009
Junior Member
Hi,

Sorry if double posting, I've searched the list but don't think I've found
the answer... =/

Just wondering what would be the best project layout for tycho enabled
projects. Lets say we have a RCP app with several features and plugins.
Should the features be maven projects with its plugins as modules? Is
mapping features with mvn projects a good idea? Of course you then need
additional mvn projects for products...

...or is the eclipse layout with ./features and ./plugins dirs useful?

Oh...and here's another one...when "tychonizing" existing RCP projects
with a flat structure how would one gain most in the long run? By keeping
the flat structure or by re-arranging into a mvn structure with project
and modules....?

Any hint is appreciated.

/Patrik
Re: Project struture [message #23772 is a reply to message #23730] Wed, 25 March 2009 13:45 Go to previous message
Eclipse User
Originally posted by: igor.ifedorenko.com

There are couple of (semi-)hard constraints to keep in mind.

First, in Maven, only projects with packaging=pom can have modules, so
nesting plugins into features in not going to work.

Second, we strongly recommend using separate projects with
packaging=eclipse-application to build RCP applications. Tyhco will not
be able to guarantee correct build order, if feature-based .product file
is included in a bundle project, for example.

Also, keep in mind that there is currently no integration between tycho
and m2e, so you won't be able to import all projects into Eclipse if you
choose non-flat layout. We do plan to provide m2e/tycho integration, but
exact timeframe is blurry.

As for the long term, I think layout really depends on actual codebase.
For m2e, for example, we've been talking about separating m2e core and
project configurators (i.e. integration with wtp, ajdt, subclipse, etc).
Current flat layout is just too big and diverse. It makes it hard for
somebody new to checkout just wtp-related code, for example. I am
currently thinking about something similar to the "old" wtp structure
(see [1]) but do not know if it will actually work yet.

We've recently setup separate mailing list dedicated to tycho [2], lets
continue this discussion on the new list.

--
Regards,
Igor

[1] http://wiki.eclipse.org/WTP_CVS_Restructuring
[2]
http://www.sonatype.com/people/2009/03/the-future-of-maven-o sgi-join-the-tycho-users-mailing-list/



Patrik Schalin wrote:
> Hi,
>
> Sorry if double posting, I've searched the list but don't think I've
> found the answer... =/
>
> Just wondering what would be the best project layout for tycho enabled
> projects. Lets say we have a RCP app with several features and plugins.
> Should the features be maven projects with its plugins as modules? Is
> mapping features with mvn projects a good idea? Of course you then need
> additional mvn projects for products...
>
> ..or is the eclipse layout with ./features and ./plugins dirs useful?
>
> Oh...and here's another one...when "tychonizing" existing RCP projects
> with a flat structure how would one gain most in the long run? By
> keeping the flat structure or by re-arranging into a mvn structure with
> project and modules....?
>
> Any hint is appreciated.
>
> /Patrik
>
Previous Topic:Downloading from repository for each test?
Next Topic:Installing M2E Source & Development Environment
Goto Forum:
  


Current Time: Wed Sep 03 07:07:27 GMT 2014

Powered by FUDForum. Page generated in 0.12573 seconds