Home » Eclipse Projects » Oomph » How to import .epf file for SVN checkout(Import an .epf file during an Oomph! eclipse installation, to check out an svn repository)
How to import .epf file for SVN checkout [message #1740620] |
Tue, 16 August 2016 11:44 |
David Israel Messages: 3 Registered: August 2016 |
Junior Member |
|
|
Hello,
I'm very new in the eclipse/java context, and I want to configure an eclipse installation by Oomph! setup files (product and project setup files).
My goal is to install an eclipse IDE with an base product.setup installation, and an optional project specific installation. After the installation, the developer should be able to start working, without configuring his IDE, checking out code from SVN manually - and so on.
The base installation works very fine, all required plugins are installed.
The second step is to install project specific preferences, including SVN checkout, but I have no idea how I could solve this issue. If I export my preferences from my own eclipse into a .epf file, I have seen, that there is a lot of information in it - in addition to this, I have read that an SVN checkout is possible, if the .epf file is imported during the eclipse installation.
The first try was to define a 'Project Set Import' task within my product.setup file - maybe I configured this item not correctly?
project.setup setupTask:
<setupTask
xsi:type="projectset:ProjectSetImportTask"
predecessor="//@setupTasks.5 //@setupTasks.4 //@setupTasks.6"
successor="//@setupTasks.8"
filter=""
uRL="D:\blabla\bla\setup\myPrefsWithSVNRepo.epf">
<description>File location of the *.epf preferences file</description>
</setupTask>
repo from .epf file snippet: (I have removed ids and repository-folders)
/instance/org.eclipse.team.svn.core/repositories/bla-id=bla-id;http\://repo/repo/trunk;http\://repo/repo/trunk;branches;tags;trunk;true;some-guid;http\://repo/repo/trunk;;false;;;0
Maybe I am on the wrong track?
FYI:
- On the operating system, there is TortoiseSVN installed, the eclipse installation includes the SVN Plugin svnKit18
- I use the free oomph plugins in eclipse to configure the setup files in the eclipse IDE
It will be great, if I could import these preferences!
One of the open points is the CheckStyle configuration - maybe it will be done by the .epf import?
The last open point is to set the target .tpd file for the project. (maybe also done by the .epf import?)
Thank you in advance for your help!
|
|
|
Re: How to import .epf file for SVN checkout [message #1742047 is a reply to message #1740620] |
Tue, 16 August 2016 13:58 |
Ed Merks Messages: 33137 Registered: July 2009 |
Senior Member |
|
|
David,
Comments below.
On 16.08.2016 14:50, David Israel wrote:
> Hello,
>
> I'm very new in the eclipse/java context, and I want to configure an
> eclipse installation by Oomph! setup files (product and project setup
> files).
>
> My goal is to install an eclipse IDE with an base product.setup
> installation, and an optional project specific installation. After the
> installation, the developer should be able to start working, without
> configuring his IDE, checking out code from SVN manually - and so on.
>
> The base installation works very fine, all required plugins are
> installed.
>
> The second step is to install project specific preferences, including
> SVN checkout, but I have no idea how I could solve this issue. If I
> export my preferences from my own eclipse into a .epf file, I have
> seen, that there is a lot of information in it - in addition to this,
> I have read that an SVN checkout is possible, if the .epf file is
> imported during the eclipse installation.
It is better, in my opinion, to use Preference Tasks, not to import a
*.epf. The setup editor has two convenient tool bar buttons to help
with the authoring. A Capture Preferences button where you can look at
the current preferences of your IDE and selectively convert them to
preference tasks. There's also an Import Preference button where you
can import a *.epf and selectively convert them to preference tasks.
This would give you far better and more fine grained control. Note that
there is also a Record Preference button so you can record changes you
make into the setup file you have open.
>
> The first try was to define a 'Project Set Import' task within my
> product.setup file - maybe I configured this item not correctly?
>
> project.setup setupTask:
>
> <setupTask
> xsi:type="projectset:ProjectSetImportTask"
> predecessor="//@setupTasks.5 //@setupTasks.4 //@setupTasks.6"
> successor="//@setupTasks.8"
> filter=""
> uRL="D:\blabla\bla\setup\myPrefsWithSVNRepo.epf">
This is not a URL, it's a file system path. It should be
file:/D:/blabla/bla/setup/myPrefsWithSVNRepo.epf. But how do you plan
to ensure that this resource is available at this fixed location for all
developers?
> <description>File location of the *.epf preferences file</description>
It looks like you're trying to point to a preferences file when you
should be pointing at a project set file. Importing the project set
file will probably set the SVN repository preference as a side effect...
> </setupTask>
>
>
> repo from .epf file snippet: (I have removed ids and repository-folders)
> /instance/org.eclipse.team.svn.core/repositories/bla-id=bla-id;http\://repo/repo/trunk;http\://repo/repo/trunk;branches;tags;trunk;true;some-guid;http\://repo/repo/trunk;;false;;;0
>
>
> Maybe I am on the wrong track?
Kind of.
>
>
> FYI:
> - On the operating system, there is TortoiseSVN installed, the eclipse
> installation includes the SVN Plugin svnKit18
> - I use the free oomph plugins in eclipse to configure the setup files
> in the eclipse IDE
>
>
> It will be great, if I could import these preferences!
No, it's better to use preference tasks.
> One of the open points is the CheckStyle configuration - maybe it will
> be done by the .epf import?
You can look at how other people do this. E.g.,
<?xml version="1.0" encoding="UTF-8"?>
<setup:ResourceCreationTask
xmi:version="2.0"
xmlns:xmi="http://www.omg.org/XMI"
xmlns:setup="http://www.eclipse.org/oomph/setup/1.0"
content="<?xml version="1.0"
encoding="UTF-8"?>

<checkstyle-configurations
file-format-version="5.0.0"
default-check-configuration="Code Recommenders Checkstyle
Configuration">
 <check-configuration name="Code
Recommenders Checkstyle Configuration"
location="/coding-conventions/resources/checkstyle/config.xml"
type="project" description="">

<additional-data name="protect-config-file"
value="false"/>

</check-configuration>
</checkstyle-configurations>
"
targetURL="${workspace.location|uri}/.metadata/.plugins/net.sf.eclipsecs.core/checkstyle-config.xml"/>
I.e., other projects appear to copy what they want in the
checkstyle-config.xml to the right place in the workspace metadata.
> The last open point is to set the target .tpd file for the project. :)
> (maybe also done by the .epf import?)
A Target Platform task can be used to set the active target platform
(based on the its name). Far better would be to use a Targlet Task,
because it reuses the bundle pool. But you might not want to duplicate
the information you have in your *.tpd. Do you use the .target file for
your build? Even if you do, Oomph can generate a .target file while
resolving the targlet... That's what we use for Oomph's own setup to
produce the .target file that's needed for our Maven/Tycho build.
>
>
> Thank you in advance for your help!
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
| | | |
Goto Forum:
Current Time: Sat Apr 20 05:29:51 GMT 2024
Powered by FUDForum. Page generated in 0.03734 seconds
|