| Re: [ecf-dev] Importing Ecf source code using Project Set file |
I think I may have found the root cause of these problems. There are two projects, org.eclipse.ecf.releng and org.eclipse.ecf.releng.bm. The project name for both these files is org.eclipse.ecf.releng. So now we have two projects in a single workspace with the same name. I stumbled across a forum post from John Arthone on another issue, but he stated clearly that:1. All projects in the default workspace tree must have unique names.2. In the default workspace tree, the project name and the name of the directory containing the project must be the same.If these rules are not followed, software that collects project names from a workspace can get confused or generate errors such as "duplicate project" or "project already exists" as I was experiencing.Should I raise a bug report for this problem?On Sun, Apr 25, 2010 at 3:36 PM, Scott Lewis <slewis@xxxxxxxxxxxxx> wrote:
Hi Jonathan,
I think your analysis is right wrt timing. In my opinion, this would constitute a bug in JDT, PDE, and/or core resources (I'm not certain where).
Please consider reporting these problems to one or more of those projects (and attaching logs). I would start with jdt and the platform:
https://bugs.eclipse.org/bugs/
Sorry this affected your experience with importing ECF's project set.
Scott
Jonathan Gossage wrote:
I believe that there may be timing and/or dependency problems. If you try downloading several times, each time into an empty workspace, you will get errors every time, but not necessarily the same errors on the same projects. If you do a clean/build procedure after downloading, initially you will see errors in the error log, but eventually (mostly) Eclipse will report that all projects are OK.
My machine is a dual-core machine so there is ample opportunity for exposure to various synchronization problems.
Some of the problems seem to be dependency problems where dependency prerequisites have not yet been built but others such as the problems deleting files from bin directories look like synchronization problems.
When importing using the .psf file, as I understand it, the projects are processed by the builder after downloading in the order they appear in the .psf file. This suggests the possibility that the .psf export process generated a bad dependency order. However, errors during a clean build suggest that the Java builder process may also be generating dependency problems.
ecf-dev@xxxxxxxxxxx <mailto:ecf-dev@xxxxxxxxxxx>On Sun, Apr 25, 2010 at 3:03 PM, Scott Lewis <slewis@xxxxxxxxxxxxx <mailto:slewis@xxxxxxxxxxxxx>> wrote:
Hi Jonathan,
I looked at your log, and unfortunately I'm not quite sure what is
going wrong. There seem to be a number of errors with
core.resources that look like this (with different resource names):
!MESSAGE Problems encountered while deleting resources.
!SUBENTRY 2 org.eclipse.core.resources 4 273 2010-04-25 12:29:55.711
!MESSAGE Could not delete '/org.eclipse.ecf.discovery/bin/org'.
<stack trace>
These errors are occurring on ecf project and on emf projects.
I don't immediately understand why this would be happening...as it
should be possible for any project in the workspace to have it's
bin directories deleted (by the java/plugin project builder). It
could be something new wrong with the Eclipse 3.6M6 resources
system (i.e. regression)...but I'm not sure about that. It
doesn't look to me like anything wrong specifically with our
project set file or projects.
In the past, I've had success by using a new and empty workspace
to import to...and then after importing sometimes repeatedly
cleaning/building all projects (sometimes more than once).
If anyone else has seen errors like these that Jonathan is seeing
and knows what's causing it please speak up.
Thanks,
Scott
Jonathan Gossage wrote:
When I try to import the ECF source code using the .psf file
in org.eclipse.ecf.releng.projectSet-anonymous.psf, I get the
error recorded in the attached Eclipse log file
"Ecf-source.log. If, after, I do Project->Clean to clean the
workspace and rebuild the workspace, I get the errors shown in
the Eclipse log file "ECF-source2.log".
I am running Eclipse 3.6 M6 using the RCP/RAP 32 bit package
as my base. I use the Sun JDK 1.6.0_20 (32 bit) and I am
running on Windows 7 Professional 64 bit.
I am prepared to try to dig into this problem, but I may need
a little guidance getting started as I am not familiar with
the innards of the Eclipse Java build process.
------------------------------------------------------------------------
_______________________________________________
ecf-dev mailing listecf-dev@xxxxxxxxxxx <mailto:ecf-dev@xxxxxxxxxxx>
https://dev.eclipse.org/mailman/listinfo/ecf-dev
_______________________________________________
ecf-dev mailing list
https://dev.eclipse.org/mailman/listinfo/ecf-dev
------------------------------------------------------------------------
_______________________________________________
ecf-dev mailing list
ecf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ecf-dev
_______________________________________________
ecf-dev mailing list
ecf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ecf-dev