Skip to content

Commit b177f99

Browse files
committed
feat: Add PropertyTreeBuilder and RequirementsResolver for YAML export
- Implemented PropertyTreeBuilder to construct YAML property trees from model elements, supporting nested structures and proper formatting. - Developed RequirementsResolver to handle requirements for node templates, including rendering requirements as YAML and resolving targets. - Introduced YamlFormatter utility for consistent YAML scalar formatting. - Added various Jython scripts for Modelio, including tools for managing associations and duplicating nodes. - Created README documentation for tools directory, detailing available scripts and their functionalities.
1 parent 377babe commit b177f99

43 files changed

Lines changed: 2232 additions & 1632 deletions

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.
Lines changed: 34 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,34 @@
1+
---
2+
name: Bug report
3+
about: Report a bug to help us improve
4+
labels: bug
5+
---
6+
7+
## Summary
8+
9+
A clear and concise description of the bug.
10+
11+
## Steps to Reproduce
12+
13+
1.
14+
2.
15+
3.
16+
17+
## Expected Behavior
18+
19+
What you expected to happen.
20+
21+
## Actual Behavior
22+
23+
What actually happened.
24+
25+
## Environment
26+
27+
- OS:
28+
- Java version:
29+
- Modelio version:
30+
- Module version:
31+
32+
## Additional Context
33+
34+
Add any other context, logs, or screenshots here.

.github/ISSUE_TEMPLATE/config.yml

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
blank_issues_enabled: false
2+
contact_links:
3+
- name: Security policy
4+
url: https://github.com/Modelio-R-D/ToscaDesigner/security/policy
5+
about: Please report security vulnerabilities here.
Lines changed: 25 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,25 @@
1+
---
2+
name: Feature request
3+
about: Suggest an idea or enhancement
4+
labels: enhancement
5+
---
6+
7+
## Summary
8+
9+
A clear and concise description of the feature.
10+
11+
## Problem Statement
12+
13+
What problem does this solve? Why is it needed?
14+
15+
## Proposed Solution
16+
17+
Describe the solution you would like to see.
18+
19+
## Alternatives Considered
20+
21+
Describe any alternatives you have considered.
22+
23+
## Additional Context
24+
25+
Add any other context or screenshots here.

.github/PULL_REQUEST_TEMPLATE.md

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,15 @@
1+
## Summary
2+
3+
Describe the changes and the motivation.
4+
5+
## Testing
6+
7+
- [ ] Not run (explain why)
8+
- [ ] `mvn -B -DskipTests package`
9+
- [ ] Other (describe)
10+
11+
## Checklist
12+
13+
- [ ] I have read the contributing guidelines
14+
- [ ] I have updated documentation as needed
15+
- [ ] I have verified new or changed behavior

.gitignore

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1 +1,19 @@
1+
# Maven build output
12
/target/
3+
**/target/
4+
5+
# Java artifacts
6+
*.class
7+
*.log
8+
9+
# IDE files
10+
.idea/
11+
*.iml
12+
.vscode/
13+
.classpath
14+
.project
15+
.settings/
16+
17+
# OS files
18+
.DS_Store
19+
Thumbs.db

CODE_OF_CONDUCT.md

Lines changed: 114 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,114 @@
1+
# Contributor Covenant Code of Conduct
2+
3+
## Our Pledge
4+
5+
We as members, contributors, and leaders pledge to make participation in our
6+
community a harassment-free experience for everyone, regardless of age, body
7+
size, visible or invisible disability, ethnicity, sex characteristics, gender
8+
identity and expression, level of experience, education, socio-economic status,
9+
nationality, personal appearance, race, religion, or sexual identity
10+
and orientation.
11+
12+
We pledge to act and interact in ways that contribute to an open, welcoming,
13+
diverse, inclusive, and healthy community.
14+
15+
## Our Standards
16+
17+
Examples of behavior that contributes to a positive environment for our
18+
community include:
19+
20+
- Demonstrating empathy and kindness toward other people
21+
- Being respectful of differing opinions, viewpoints, and experiences
22+
- Giving and gracefully accepting constructive feedback
23+
- Accepting responsibility and apologizing to those affected by our mistakes,
24+
and learning from the experience
25+
- Focusing on what is best not just for us as individuals, but for the
26+
overall community
27+
28+
Examples of unacceptable behavior include:
29+
30+
- The use of sexualized language or imagery, and sexual attention or advances
31+
- Trolling, insulting or derogatory comments, and personal or political attacks
32+
- Public or private harassment
33+
- Publishing others' private information, such as a physical or email address,
34+
without their explicit permission
35+
- Other conduct which could reasonably be considered inappropriate in a
36+
professional setting
37+
38+
## Enforcement Responsibilities
39+
40+
Community leaders are responsible for clarifying and enforcing our standards of
41+
acceptable behavior and will take appropriate and fair corrective action in
42+
response to any behavior that they deem inappropriate, threatening, offensive,
43+
or harmful.
44+
45+
Community leaders have the right and responsibility to remove, edit, or reject
46+
comments, commits, code, wiki edits, issues, and other contributions that are
47+
not aligned to this Code of Conduct, and will communicate reasons for
48+
moderation decisions when appropriate.
49+
50+
## Scope
51+
52+
This Code of Conduct applies within all community spaces, and also applies when
53+
an individual is officially representing the community in public spaces.
54+
Examples of representing our community include using an official e-mail address,
55+
posting via an official social media account, or acting as an appointed
56+
representative at an online or offline event.
57+
58+
## Enforcement
59+
60+
Instances of abusive, harassing, or otherwise unacceptable behavior may be
61+
reported to the community leaders via the repository communication channels.
62+
If you need a private reporting path, use GitHub's private reporting feature
63+
(if enabled) or open a security advisory as described in SECURITY.md.
64+
65+
Community leaders will follow these Community Impact Guidelines in determining
66+
consequences for any action they deem in violation of this Code of Conduct:
67+
68+
### 1. Correction
69+
70+
**Community Impact**: Use of inappropriate language or other behavior deemed
71+
unprofessional or unwelcome in the community.
72+
73+
**Consequence**: A private, written warning from community leaders, providing
74+
clarity around the nature of the violation and an explanation of why the
75+
behavior was inappropriate. A public apology may be requested.
76+
77+
### 2. Warning
78+
79+
**Community Impact**: A violation through a single incident or series of
80+
actions.
81+
82+
**Consequence**: A warning with consequences for continued behavior. No
83+
interaction with the people involved, including unsolicited interaction with
84+
those enforcing the Code of Conduct, for a specified period of time. This
85+
includes avoiding interactions in community spaces as well as external channels
86+
like social media. Violating these terms may lead to a temporary or
87+
permanent ban.
88+
89+
### 3. Temporary Ban
90+
91+
**Community Impact**: A serious violation of community standards, including
92+
sustained inappropriate behavior.
93+
94+
**Consequence**: A temporary ban from any sort of interaction or public
95+
communication with the community for a specified period of time. No public or
96+
private interaction with the people involved, including unsolicited interaction
97+
with those enforcing the Code of Conduct, is allowed during this period.
98+
99+
### 4. Permanent Ban
100+
101+
**Community Impact**: Demonstrating a pattern of violation of community
102+
standards, including sustained inappropriate behavior, harassment of an
103+
individual, or aggression toward or disparagement of classes of individuals.
104+
105+
**Consequence**: A permanent ban from any sort of public interaction within the
106+
community.
107+
108+
## Attribution
109+
110+
This Code of Conduct is adapted from the Contributor Covenant, version 2.1,
111+
available at https://www.contributor-covenant.org/version/2/1/code_of_conduct.html.
112+
113+
Community Impact Guidelines were inspired by Mozilla's code of conduct
114+
enforcement ladder.

CONTRIBUTING.md

Lines changed: 21 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -1,15 +1,18 @@
1-
CONTRIBUTING
1+
# Contributing
2+
3+
Thanks for considering contributing to TOSCA Designer.
4+
5+
## Development Setup
26

3-
Development setup
4-
-----------------
57
This repository builds a Modelio 5.4.1 module (ToscaDesigner) and requires Java 8 for runtime compatibility with Modelio.
68

7-
Requirements
9+
### Requirements
10+
811
- Java 8 JDK (for running Modelio and for building modules targeting Modelio)
912
- Maven 3.6+
1013

11-
Build instructions
12-
------------------
14+
### Build
15+
1316
From the project root:
1417

1518
```powershell
@@ -18,18 +21,23 @@ mvn -B -DskipTests package
1821

1922
This produces `target/toscadesigner-<version>.jar` and `target/ToscaDesigner_<version>.jmdac`.
2023

21-
Notes
22-
-----
24+
### Notes
25+
2326
- The project compiles with `maven-compiler-plugin` configured to `<release>8` to ensure bytecode compatibility with Modelio 5.4.1.
2427
- The `MDAKit` dependency is provided by the Modelio runtime; it is declared with `scope=provided` in `pom.xml`.
2528
- If you need to run checks that require the Modelio API, install Modelio and run integration steps inside its environment.
2629

27-
Contributing
28-
------------
30+
### Scripts and Utilities
31+
32+
- Modelio Jython helper scripts live in [tools/modelio](tools/modelio).
33+
- Dev utilities (like import fixups) live in [tools/dev](tools/dev).
34+
35+
## Contribution Workflow
36+
2937
- Fork the repo and create a feature branch.
3038
- Run the build locally and open a pull request.
3139
- For major changes, open an issue first to discuss the design.
3240

33-
CI
34-
--
35-
A GitHub Actions workflow (maven-java8.yml) is included to build with Java 8 on push and pull requests.
41+
## CI
42+
43+
A GitHub Actions workflow ([.github/workflows/maven-java8.yml](.github/workflows/maven-java8.yml)) builds with Java 8 on push and pull requests.

0 commit comments

Comments
 (0)