ARIES-2162: Add jmx and blueprint workflows #297
Conversation
alien11689
force-pushed
the
add-jmx-build-workflow
branch
2 times, most recently
from
8382fba to
fc264cf
Compare
alien11689
force-pushed
the
add-jmx-build-workflow
branch
2 times, most recently
from
1b4a95a to
c28e364
Compare
alien11689
force-pushed
the
add-jmx-build-workflow
branch
from
574b403 to
62fca6e
Compare
alien11689
force-pushed
the
add-jmx-build-workflow
branch
from
3bbfa2e to
5016f86
Compare
alien11689
force-pushed
the
add-jmx-build-workflow
branch
from
5016f86 to
4ad4d27
Compare
alien11689
changed the title
| @@ -24,7 +24,7 @@ | |||
| <parent> | |||
| <groupId>org.apache.aries.jmx</groupId> | |||
| <artifactId>org.apache.aries.jmx.parent</artifactId> | |||
| <version>1.1.6-SNAPSHOT</version> | |||
| <version>1.1.5</version> | |||
There was a problem hiding this comment.
Out of curiosity, why did you switch back to a release version for this module?
There was a problem hiding this comment.
The parent artifact has its parent updated (by you in #295 ) and I tested it during creation of workflows.
My goal is to prepare green workflows before making any changes, so the solution may not be perfect but... it works :)
Without changing the version here to the last published version there are test errors in itest:
java.lang.ClassNotFoundException: org.osgi.jmx.framework.*
I wrote about the root reason in #296 (comment)
There was a problem hiding this comment.
Ah, I missed that this is about the parent pom, sorry. So no concerns here.
Final comment from me - would it make sense to build the whole reactor instead of all the ITs and dependant projects?
There was a problem hiding this comment.
I am not able to force jmx/jmx-whiteboard to pass tests in reactor from zero:
- current code has problems to fetch artifacts because of http addresses
- With upgraded parent, pax url and added javax.inject the code compiles but tests failes and btw artifacts are downloaded via https so...
- when removing upgrades and running build again the tests passes
I think that many other tests needs changes for new parent :(
For your @rombert tests it should be fine to add new tests to itest and -am option should include your new bundle build and test.
No description provided.