Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[CLOUD-2235] add reference to kie-modules #35

Conversation

jmtd
Copy link
Member

@jmtd jmtd commented Feb 27, 2018

https://issues.jboss.org/browse/CLOUD-2235

KIE modules are moving repositories; make sure we reference the new location.

  • [✓] Pull Request title is properly formatted: [CLOUD-XYA] Subject
  • [✓] Pull Request contains link to the JIRA issue
  • [✓] Pull Request contains description of the issue
  • [✓] Pull Request does not include fixes for issues other than the main ticket
  • [✓] Attached commits represent units of work and are properly formatted
  • [✓] You have read and agreed to the Developer Certificate of Origin (DCO) (see CONTRIBUTING.md)
  • [✓] Every commit contains Signed-off-by: Your Name <yourname@example.com> - use git commit -s

Signed-off-by: Jonathan Dowland jdowland@redhat.com

Signed-off-by: Jonathan Dowland <jdowland@redhat.com>
spolti
spolti previously approved these changes Feb 27, 2018
Name scheme change to avoid clashes with the same modules in the
older repository.

Signed-off-by: Jonathan Dowland <jdowland@redhat.com>
Copy link
Contributor

@errantepiphany errantepiphany left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jmtd Looks good to me.

- name: os-kieserver-s2i
- name: os-kieserver-webapp
- name: os-kieserver-chmod
- name: os.kieserver.launch
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we use a more descriptive name, e.g. like Java package name for these? The goal being to be able to easily identify from which repository the module is pulled, e.g. jboss.kie.kieserver.launch: kieserver.launch module from jboss-kie repsoitory. If you have a better idea for naming, feel free to adjust as necessary. With the example I provided, you might also want to add a name to the repo, e.g. jboss.kie.repo. Having a name is a critical piece required to override the module location for development purposes, e.g. overrides.yaml:

modules:
  repositories:
  - name: jboss.kie.repo
    path: /home/me/src/git/jboss-container-images/jboss-kie-modules

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@rcernich I like this idea (changing the names), but can we do this as follow-up PRs? There's already a lot in this jira...

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

After speaking with @rcernich on IRC, the renaming of modules (and adding repo names) will be done in subsequent PRs. We need to move these PRs so other work can progress.

@errantepiphany errantepiphany merged commit bdd3496 into jboss-container-images:kieserver64-dev Feb 27, 2018
@jmtd jmtd deleted the cloud-2235-split-cct-module branch February 28, 2018 11:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
4 participants