Srcdeps - some changes to come
by Peter Palaga
Hi *,
I was able to invest some time into srcdeps in the recent couple of
months. Srcdeps is now a bit more powerful - esp. it is able to handle
all kinds of dependencies incl. parents and BoM imports. The new
functionality was enabled by using the Maven Core Extensions API instead
of Maven Plugin API.
Technically, srcdeps now provides its own custom implementation of Maven
Local Repository [1]. In this way srcdeps is able to intercept every
single request to the Maven Local Repository and eventually build the
requested artifact from source and install it locally if necessary.
The convention to declare a source dependencies using
-SRC-revision-{sha1} suffix stayed unchanged. However, the mapping from
GAVs to git repositories now lives in .mvn/srcdeps.yaml file rather than
in pom.xml file.
In the coming weeks, I'll be preparing PRs to migrate from the old
srcdeps-maven-plugin to the new srcdeps core extension.
I'll also introduce mvnw (a.k.a. Maven Wrapper [2]) so that there is a
common way for developers, CI and srcdeps to get the same clearly
defined version of Maven.
Are there any concerns or questions?
[1] https://github.com/srcdeps/srcdeps-maven
[2] https://github.com/takari/maven-wrapper#maven-wrapper
Thanks,
Peter
6 years, 3 months
Hawkular
by Yogesh Vedpathak
Hi,
As per installation guide of Hawkular, we need to install CCM first. I have
python installed on my RHEL machine. But I am not able to install CCM. Can
someone give suggestions for installing CCM?
Regards,
Yogesh
6 years, 3 months
Hawkular Services as Middleware Manager and Ansible
by Thomas Heute
I'd like to resume the discussion as how we will enable the following
features:
- Start a server/domain
- Find Wildfly servers and instrument them with the agent
with Ansible in the Middleware Manager ?
I'm questioning the packaging and dependencies, Rubens spent some time a
while back and we need to resume/conclude:
https://github.com/hawkular/hawkular-commons/pull/83/files
If I read fast and correctly it seems that:
- we have a cyclic dependency(with commons and inventory)
- the code should not be in common (actually the whole commands-gateway
doesn't belong to commons if we consider that commons was supposed to be
shared among Alert/Metrics/APM/Services)
- The playbooks are not part of Hawkular-services so they would be added
separately ? Or hawkular-services would be less and less generic / more and
more related to the MW Manager ?
- The code is currently specific to Wildfly ? (Would not work for Fuse
on Karaf or should be modified ?)
https://github.com/hawkular/hawkular-commons/pull/83/files#diff-dd195df81...
Note: While I am not directly suggesting Hawkular Services to be more
specialized as the middleware manager, it may be something we would want.
Hawkular for Manage IQ (currently hawkular-services) and Hawkular for
Kubernetes/OpenShift (currently HAM), the first should extend the second so
that one could just use the first as MW Manager and solution for OpenShift.
It would simplify development and message.
Thomas
6 years, 3 months
Reminder - post changes to WF config on this list
by Jay Shaughnessy
Lately we've had a few changes that have resulted in some broken test
setups. Specifically, changes to ISPN cache definitions in the WF
configurations. This can affect ITests, QE tests, etc, outside of the
project initiating the change. Please take it into consideration when
pushing a change like this; make sure you let people know it's coming
and potentially generate PRs for affected builds.
6 years, 3 months
