First of all, thanks for considering to contribute. We appreciate the time and effort you want to spend helping to improve things around here. And help we can use :-)
Here is a (non-exclusive, non-prioritized) list of things you might be able to help us with:
- bug reports
- bug fixes
- improvements regarding code quality, e.g. improving readability, performance, modularity etc.
- documentation
- features (both ideas and code are welcome)
- tests
A proper header must be in place for any file contributed to the project. For a new contribution, please add the below header:
/*
* Copyright (c) <year> <legal entity> and others
*
* Licensed under the Apache License, Version 2.0 (the "License");
* you may not use this file except in compliance with the License.
* You may obtain a copy of the License at
*
* http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing, software
* distributed under the License is distributed on an "AS IS" BASIS,
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
* See the License for the specific language governing permissions and
* limitations under the License.
*/
Please ensure <year>
is replaced with the current year or range (e.g. 2017 or 2015, 2017).
Please ensure <legal entity>
is replaced with the relevant information. If you are editing an existing contribution, feel free
to create or add your legal entity to the contributors section as such:
/*
* Copyright (c) <year> <legal entity> and others
*
* Licensed under the Apache License, Version 2.0 (the "License");
* you may not use this file except in compliance with the License.
* You may obtain a copy of the License at
*
* http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing, software
* distributed under the License is distributed on an "AS IS" BASIS,
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
* See the License for the specific language governing permissions and
* limitations under the License.
*
* Contributors:
* <legal entity>
*/
The easiest way to contribute code/patches/whatever is by creating a GitHub pull request (PR). When you do make sure that you Sign-off your commits.
You do this by adding the -s
flag when you make the commit(s), e.g.
$> git commit -s -m "Let's do it."
- Fork the repository on GitHub
- Create a new branch for your changes
- Configure your IDE
- Make your changes
- Make sure copyright headers are included in (all) files including updated year(s)
- Make sure proper headers are in place for each file (see above Legal Requirements)
- Commit your changes to that branch
- Use descriptive and meaningful commit messages
- If you have a lot of commits squash them into a single commit
- Make sure you use the
-s
flag when committing as explained above - Push your changes to your branch in your forked repository
- Install
Java 17
JDK Distribution (including JavaFX modules) in your machine (Currently I am using Zulu Distribution that includes JavaFX modules already) - Set the newly installed
Java 17
to yourJAVA_HOME
- Install
Eclipse IDE for RCP/RAP Developers
and make sure your Eclipse installation uses the currently installedJava 17
to start with - Install
Bndtools
,e(fx)clipse
, andSonarLint
from Eclipse Marketplace - Go to
Java ⇢ Compiler
inEclipse Preferences
and setCompiler Compliance Level
to17
- Go to
Java ⇢ Installed JREs
and select the newly installed JDK with JavaFX modules - Go to
Java ⇢ Installed JREs ⇢ Execution Environments
and selectJavaSE-17
and choose the recently installedJava 17 JRE
that includesJavaFX
modules - Go to
Java ⇢ Code Style ⇢ Formatter ⇢ Import
and select theformatter.xml
stored in the project's root directory - Import all the projects (
File ⇢ Import ⇢ General ⇢ Existing Projects into Workspace
and selectSearch for nested projects
)
- To start the application inside IDE, go to
com.osgifx.console.product
and double click onosgifx.bndrun
. This will open thebndrun editor
and then click onDebug OSGi
from the top right corner.
Submit a pull request via the normal GitHub UI
- Do not use your branch for any other development, otherwise further changes that you make will be visible in the PR.