Re: [dtp-dev] DTP Migration from CVS to Git

[Brian Payton <bpayton@xxxxxxxxxx>]

Hi Pierre,

I see the same compilation errors.  The
problems only occur when you build the plugins under Eclipse 3.7; they
do not occur when building with Eclipse 3.6.2.  Apparently the PDE
for Eclipse 3.7 is pickier when it comes to resolving indirect bundle references
than 3.6 was.

I'll update the MANIFEST.MF files to
fix the problems.

Regards,
Brian

Brian Payton
DTP PMC Lead
Data Tools Development
IBM Silicon Valley Laboratory





From:      
 Pierre Queinnec <pierre.queinnec@xxxxxxxxxx>
To:      
 DTP development mailing
list <dtp-dev@xxxxxxxxxxx>
Date:      
 08/10/2011 02:15 AM
Subject:    
   Re: [dtp-dev]
DTP Migration from CVS to Git
Sent by:    
   dtp-dev-bounces@xxxxxxxxxxx

---

Hi Brian,

I can confirm that when setting up my workspace from Git, I had to move aside these top-level .project files for the import.

By the way, I also had to add some missing dependencies on some enablement plugins (mostly EMF Core) but it strikes me as odd, so maybe it's my mistake due to a different target environment or something (I tried to follow the developer guide with the exception of LPG which I got from Orbit as I think the documentation wasn't up-to-date on that aspect). I've attached the patch here for review [2].

Kind regards,

-- Pierre

 

[2]  https://bugs.eclipse.org/bugs/show_bug.cgi?id=353609

 

 

----- Original message ----- From: Brian Payton <bpayton@xxxxxxxxxx> Date: Tue, 9 Aug 2011 18:17:39 -0700 Subject: Re: [dtp-dev] DTP Migration from CVS to Git To: DTP development mailing list <dtp-dev@xxxxxxxxxxx> FYI, I discovered an minor issue when trying to load all the DTP projects from Git into my workspace.  In the SQLDevTools Git repository (that is, ssh://<userid>@git.eclipse.org/gitroot/datatools/org.eclipse.datatools.sqltools.git ) The issue is that the plugins folder inside the Working directory of the repository has a ".project" file.  This makes the Import Projects... action on the repository want to import the plugins directory itself as a project into the workspace, rather than the projects that it contains.  To get around this, I need to select and import each project into my workspace one at a time, which is quite tedious, since there are 30 of them. If nobody objects, I think as my first Git operation I'll try to remove that .project file :-) Regards, Brian Brian Payton DTP PMC Lead Data Tools Development IBM Silicon Valley Laboratory

_______________________________________________
dtp-dev mailing list
dtp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dtp-dev