RE: How to update CSS version 3.x to 4.x ?

[Patard Charles-Henri <charles-henri.patard@ganil.fr>]

Hello,
Indeed thanks to Marcus for mentioning the CS-Studio book !! We need next time to think about this book. It's often updated with new content and Chapter 4 is very helpful.
I finally managed my CSS update. I choice to use the p2 update site from http://controlsystemstudio.org/controlsystemstudio/current.html in version 4.1 (http://download.controlsystemstudio.org/updates/4.1). Add this p2 update site in my target platform and download missing plugins from it. Be careful some plugins can't be downloaded like (Mockito and Hibernate). Others are twice in some categories like (Rap ui tools).
After that I import the CSS source code in my workspace by the git repository clone of https://github.com/ControlSystemStudio/cs-studio.git in 4.1 branch.

Thanks a lot,
Now we can start coding some new features for PVTable. We will get you a feedback of it and some proposal for a pull request as soon as possible.


-----Message d'origine-----
De : Kasemir, Kay [mailto:kasemirk@ornl.gov] 
Envoyé : mardi 3 novembre 2015 14:29
À : Florian Feldbauer
Cc : Patard Charles-Henri; Philippe Laurent; tech-talk@aps.anl.gov
Objet : Re: How to update CSS version 3.x to 4.x ?

Hi:

Thanks to Marcus for mentioning the CS-Studio book: 
http://cs-studio.sourceforge.net/docbook/
Esp. Chapter 4: Compiling, Running, Debugging CSS.

Yes, that’s where I continue to try to describe how to build CSS.
If you follow that to build diirt, maven-osgi-bundles, cs-studio-thirdparty, cs-studio and the org.csstudio.sns.product, you’ll get the RDB-based archive engine as well.
.. but the diirt config may right now be incomplete, and the section on loading a *.target file into the IDE doesn’t apply any more because of the ongoing changes.
Once I’m again able to build functioning products for SNS, I’ll try to update the dokbook.

Thanks,
Kay


> On Nov 3, 2015, at 5:03 AM, Florian Feldbauer <florian@ep1.ruhr-uni-bochum.de> wrote:
> 
> Dear Kay,
> 
> I'm also interested in this topic.
> For the PANDA experiment I build a CSS Product based on version 3.1.1 
> during my PhD thesis.
> Now we also would like to upgrade to the new version.
> 
> Unfortunately I have no idea how to use maven.
> Is there some documentation on how to build the individual packages, 
> like diirt, maven-osgi-bundles,... ?
> I looked on github but could not find anything.
> 
> Another question: With cs-studio 3.1.1 we always used the BEAUTY 
> ArchiveEngine.
> I have not found it in the current master branch of any of the 
> packages you mentioned below.
> Did I miss it, or was it removed?
> 
> Best regards,
> Florian
> 
> On 11/02/2015 03:41 PM, Kasemir, Kay wrote:
>> On Nov 2, 2015, at 2:45 AM, Patard Charles-Henri <charles-henri.patard@ganil.fr> wrote:
>>> Hello,
>>> I’m trying to update CSS from version 3 to version 4. I need to update my CSS Spiral2 products from 3.x to 4.x.
>>> I created a clone from 4.1.x branch on git and import plugins into my workspace with Maven import. Some of needed plugins are missing in version 4.1 :
>>> ·         org.epics.util
>>> ·         org.epics.vtype
>>> ·         org.csstudio.platform.libs.jms
>>> Do I need to create a clone from  3.x branch and add missing plugins in my workspace ? Did plugins were replaced by others ? How can I do this update ?
>> Hello Charles-Henri:
>> 
>> Good question.
>> Unfortunately, I don’t have a good answer.
>> Half of the time I’m wondering myself how to build CSS.
>> 
>> For the 3.x sources, it was pretty straight forward:
>> * Get the CSS sources, either from the source repository or from a site-specific zip of a 3.x version.
>> * Start appropriate version of Eclipse RCP IDE, “Import existing project into workspace”
>> * Open one of the *.product files to launch, debug, export
>> 
>> As we moved to 4.x, two things changed:
>> 
>> We decided to remove 3rd party binaries like the jar files for JMS, JDBC, JCA/CAJ from the primary cs-studio repository. The org.csstudio.platform.libs.jms plugin for example is now in a cs-studio-thirdparty repo.
>> And we use maven for the headless build.
>> 
>> In combination, several pieces of 3rd party code were completely removed from our repositories and we instead depend on maven to download them from somewhere. The jython or org.epics.util plugins for example are only listed in https://github.com/ControlSystemStudio/maven-osgi-bundles/blob/4.1.x/repository/pom.xml so that maven downloads them for us.
>> The complete build process became this:
>> * Get the sources for maven-osgi-bundles, cs-studio-thirdparty, 
>> cs-studio and for example org.csstudio.product
>> * Build everything with maven on the command line. Maven fetches the missing pieces.
>> You could then use the resulting product binaries as a “target” for the Eclipse IDE, import the sources, continue as before.
>> 
>> The part where maven fetches the missing pieces has not been without problems. Even when it all “works”, my time for a complete rebuild went from 20 to 60 minutes. Since build errors tend to happen in the later stages, I’m easily loosing days every month working through build problems.
>> 
>> As for org.epics.util & org.epics.vtype, they have just been renamed to org.diirt.*, and their code is in https://github.com/ControlSystemStudio/diirt, so the build process is right now:
>> * Get the sources for diirt, maven-osgi-bundles, 
>> cs-studio-thirdparty, cs-studio and for example org.csstudio.product
>> * Build everything with maven on the command line.
>> .. and there are some configuration details of diirt that require the addition of certain xml files to your product, since it’s no longer tied to the Eclipse preferences. The org.csstudio.product should include an example.
>> 
>> At the recent EPICS/ICALEPCS, the present CS-Studio developers agreed 
>> that it’d be good to have a better handle on the 3rd party libraries (https://github.com/ControlSystemStudio/cs-studio/issues/1417 ) For example, offering a zipped cs-studio-target would allow you to do this:
>> 
>> * Get the current cs-studio-target.zip, unpack
>> * Get the CSS sources, either from the source repository or from a site-specific zip of a 3.x version.
>> * Start appropriate version of Eclipse RCP IDE, set the RCP target to 
>> the cs-studio-target, “Import existing project into workspace” to 
>> load the sources
>> * Open one of the *.product files to launch, debug, export
>> 
>> This would remove the sometimes unpredictable or fragile and always slow dependency on maven to locate and successfully download the correct dependencies. Everybody who uses the same cs-studio-target.zip will get the same results.
>> 
>> Meanwhile, if you’re updating from 3.x it might be best to skip 4.1 (with org.epics.*) and instead start with the current master (with org.diirt.*), except that I’m still trying to create functional SNS products from that myself.
>> 
>> Thanks,
>> Kay
>> 
>> 
> 
> 
> --
> ----------------------------------------
> | Dr. Florian Feldbauer                |
> |                                      |
> | Helmholtz-Institut Mainz /           |
> | Johannes Gutenberg-Universität Mainz |
> | Johann-Joachim-Becher-Weg 36         |
> | D-55128 Mainz                        |
> |                                      |
> | Office: SB1 / 00-213                 |
> | Phone:  (+49)6131 / 39-29608         |
> ----------------------------------------
> 
>