Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Building the Higgins I-Card Manager Service"
(→I-Card Manager Projects) |
(→I-Card Manager Projects) |
||
| Line 33: | Line 33: | ||
|- | |- | ||
| [http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.higgins/app/org.eclipse.higgins.icm/committer.psf?root=Technology_Project&view=co committer] | | [http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.higgins/app/org.eclipse.higgins.icm/committer.psf?root=Technology_Project&view=co committer] | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
|- | |- | ||
|} | |} | ||
Revision as of 04:44, 2 April 2007
General CVS Information
| Connection Type | Committers | :ext: |
| Anonymous access | :pserver: | |
| Host | dev.eclipse.org | |
| Repository Path | /cvsroot/technology | |
I-Card Manager Projects
Main I-Card Manager project is
| Project | Module Location | Eclipse PSF | ViewCVS |
|---|---|---|---|
| I-Card Manager | org.eclipse.higgins/app/org.eclipse.higgins.icm | anonymous | viewcvs |
| committer |
Build Instructions
- Building within Eclipse IDE:
- The normal project build method will compile the source
- How to produce an Eclipse plugin:
- Run->External Tools->Build RPPS Core plugin. This will run Ant build script to produce Eclipse plugin. Resulting plugin's jar along with the build's log file will be placed in "build/plugins" folder. See also: 1.
- How to produce a standalone jar:
- Run->External Tools->Build RPPS Core jar. This will run Ant build script to produce standalone jar. Resulting jar file will be placed in "build/lib" folder. See also: 1.
- How to produce javadoc:
- Run->External Tools->Build RPPS Core javadoc. This will run Ant build script to produce javadoc. Javadocs will be generated in "build/doc" folder. See also: 1.
- Command-line builds:
- How to produce an Eclipse plugin:
- From the project directory, run "ant plugin -Declipse.home=<path to eclipse installation>" Resulting plugin's jar along with the build's log file will be placed in "build/plugins" folder.
- How to produce a standalone jar:
- From the project directory, run "ant". Resulting jar file will be placed in "build/lib" folder. See also: 2.
- How to produce javadoc:
- From the project directory, run "ant javadoc". Javadoc will be generated in "build/doc" folder. See also: 2.
- How to produce an Eclipse plugin:
- Builds notes:
- 1 Provided Eclipse launch configuration runs ant using the same JRE as the workspace. If you need to change JRE for some reason you will need to provide "-Declipse.home=<path to eclipse installation>" VM argument.
- 2 In order to process plugin specific files you will need to add "-Declipse.home=<path to eclipse installation>" option to the command line.