| 
 Hi, 
  
I followed the instructions and eclipse still showed errors 
in some projects. They were all that the packages exported in 
the manifest could not be found. However I found out that if one 
changes a property in the build path and then change it back, eclipse finds the 
packages. Seems that some error accurs during the check out itself. 
 
  
  
Greetings, 
Boyan. 
  
  
  
  
Hi,
I think you are mixing things up or I cannot properly express myself. Here 
are the steps: 
- clean workspace 
- checkout org.eclipse.riena.releng 
- open projectSet-pserver.psf in that project 
- load and replace all from the projectset editor 
- the resulting projects in your workplace should compile without 
errors. 
  
Now you can either check testcases, sourcecode. Or starting writing your 
own code based on Riena samples. We have a wiki with some getting started 
documentation for remote services that you can access from  www.eclipse.org/riena and then follow 
the wiki link.  
  
The build.cmd script contains references to directories. Thats true. 
However these directories are intentionally defined as environment vars at the 
beginning of the script and nowhere else. That allows you run the script from 
any windows shell. 
  
The good news is that we have done the build just yesterday and put the M1 
release up on the eclipse download server. There is currently just an issue with 
how that can be accessed by everybody. Once that is cleared. You can download 
the finished build from eclipse.org download server. 
  
hope that helps. 
  
christian 
Am 25.02.2008 um 18:21 schrieb Yurukov, Boyan: 
  
  
  Hi, 
    
  First I checked out org.eclipse.releng.equinox from 
  org.eclipse.equinox/phase1. Then I checked out the contents of 
  org.eclipse.riena/* in different projects. There is no change and the errors 
  persist.  
    
  Also it is impossible to run 
  org.eclipse.riena.build/scripts/build.cmd, because many paths are absolute and 
  would work only on the developer's machine. For example in several places the 
  workspace is set to "c:/projekte/riena2". I tried changing all 
  the wrong paths to fit my environment, but when I run it again, it tells me 
  that cvs cannot fetch some files from "org.eclipse.riena.build.feature", 
  while at the same time, it can from other projects. 
 
    
  Can 
  you please give me more details on how to import the project in Eclipse 
  and how to run it?  
    
  Greetings, 
  Boyan.  
  
  Hi Yurukov, 
   
  
  what you should do (as with most Eclipse projects) that you first check 
  out the *.releng project. This project contains projectsets with ALL 
  dependencies. There is one with called pserver (for people like you), and one 
  called ssh (for committers). This will automatically pick up equinox.log and 
  equinox.cm (both currently in equinox-incubator). 
  But you don't need to worry about those locations. The projectset knows 
  them all and should create a workspace with no compile errors. 
  
  
  cheers 
  christian 
  
  
  Am 25.02.2008 um 17:17 schrieb Yurukov, Boyan: 
  
    
    Hello all,  
    I just checked out the CVS and 
    imported all projects. It seems that most of them import  
    "org.eclipse.equinox.log.Logger" which cannot be found either in the 
    official releace of equinox (3.3.1.1), nor in the stream release (3.4). Also 
    it imports "org.eclipse.equinox.cm", which is marked as "coming soon". Does 
    anyone know where I can get those libraries and if there are any precompiled 
    ready-to-use Riena plugins so I can try the examples? 
    Greetings, 
     Boyan 
    Yurukov. 
      _______________________________________________ riena-dev 
    mailing list riena-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/riena-dev
     _______________________________________________ riena-dev 
  mailing list riena-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/riena-dev
    
 |