| clone existing project [message #1697222] |
Tue, 02 June 2015 09:54  |
Eclipse User |
|
|
|
|
Hi all, I just run these days into Oomph and am looking for a starting point: can I take my existing Eclipse-based project, clone it somehow into a team-wide catalogue, and have my team mates install it as a readily-configured environment? Any wiki/forum/doc around describing this? Many thanks!
|
|
|
|
|
| Re: clone existing project [message #1697309 is a reply to message #1697273] |
Wed, 03 June 2015 01:26  |
| Eclipse User |
|
|
|
Mario,
Comments below.
On 02/06/2015 11:03 PM, Mario L wrote:
> Thank you for your fast reply. I have seen before that page and
> dismissed immediately because of the "outdated" warning there. But
> because you recommended it now, I gave it a try.
Given it's all we have, it's the only thing I can refer to...
>
> Unfortunately what I read there is too little to reach my goal.
> Already step 2.2 is incorrect, and starting with 3 nothing matches
> reality anymore... so the "outdated" label is totally deserved.
:-P
> But because I already installed Oomph SDK (and got over the usual
> Eclipse update sites fup) I thought I try it on my own. Hmm, it's not
> clear why I need a git path (which makes me wonder what about other
> versioning systems?).
The best support is for git; for other VCS you'd have to use a project
set file and import the projects via that task.
> Then comes the folder selection which opens a window "container
> selection" - is folder=container or not?
I'm not sure what you refer to, but the Eclipse workspace has IProject,
IFolder, and IFile, where the first two are IContainers, so a dialog to
create a new file or a new folder will typically offer an IContainer
(IProject or IFolder) as the target.
> Do I open there an existing project as template, or a new one
> container-whatever-that-is to store the new stuff I'm about to create?
Use the wizard to choose one of the three templates as a starting point...
> Anyway, that container selection offers to take only
> RemoteSystemsTempFiles (which nobody on earth really knows what is
> for), and clicking to create a new one will create only subfolders of it.
You can put the new file anywhere in your workspace....
> Whatever, I create a subfolder and voila I got the .setup file open. I
> cannot see any place to "use an existing Eclipse project" and have no
> idea what all those trees are for so my adventure with Oomph must stop
> here.
You must define the information about your project, it's never about
creating an Eclipse project, it's about creating a setup description of
how to work with an existing project...
>
> I came with the expectation to create a central repository with our
> web application project(s) from where the team can always download to
> install (or update) a ready-made environment for developing that
> particular application.
You can create a project description that can be used to install an
Eclipse development environment with the necessary tools for working
with the application projects and which ensures that those projects are
automatically available in the workspace.
> I thought I shouldn't need to learn EMF and a DSL and more just to
> reach what a plain ZIP already can do for me, so I think I understood
> the use case for Oomph COMPLETELY wrong.
If you want to download and unzip something, rather than create an
Eclipse installation fully configured with the right tools and
preferences to work with the projects from some source code repository,
that's indeed beside the point.
> Sorry for wasting your time and thanks again for the prompt reply!
No problem.
|
|
|
| Re: clone existing project [message #1697338 is a reply to message #1697309] |
Wed, 03 June 2015 05:30 |
| Eclipse User |
|
|
|
Ed Merks wrote on Wed, 03 June 2015 01:26You must define the information about your project, it's never about
creating an Eclipse project, it's about creating a setup description of
how to work with an existing project...
That would be great indeed. I already have that project up and running and hoped to get somehow the setup description "pre-filled" based on it - so I would be only required to configure where to save the central setup and maybe some update rules. That's my "ideal" case (with not much learning needed, eh). Zip can do the following for me: I can zip my "template" project, save it someplace and email my folks to grab it. What I hoped a tool would achieve is to analyze my existing project and generate that central setup PLUS giving the possibility for pushing updates to everybody when I update the central repo. And adding real versioning of the setup _template_ (not just timestamps on the dumb zips)...
|
|
|
Powered by
FUDForum. Page generated in 0.03736 seconds
Home