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

Upgrade to Karaf 4.2.0 #260

Merged
merged 4 commits into from
Jun 16, 2018
Merged

Upgrade to Karaf 4.2.0 #260

merged 4 commits into from
Jun 16, 2018

Conversation

wiiitek
Copy link
Contributor

@wiiitek wiiitek commented Jun 4, 2018

Description

Karaf 4.2.0 works with both JAVA 8 and JAVA 9. For Active MQ v 5.15.x to work we need to provide Spring legacy repository for Aries blueprint. See also http://mail-archives.apache.org/mod_mbox/karaf-user/201805.mbox/%[email protected]%3E

After this is accepted we could update the cookbook to make new Karaf version default there.

Motivation and Context

We want to use newest possible version of Karaf so that it is easier for us to upgrade other System components (i.e. JAVA).

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.

I hereby agree to the terms of the AET Contributor License Agreement.

@@ -86,8 +86,10 @@ Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
}
},
"aet" => {
"base_link" => "https://www.kubiczak.pl/aet",
Copy link
Contributor

Choose a reason for hiding this comment

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

How about using maven staging repository?
You could easily deploy snapshot version there without having custom links: https://oss.sonatype.org/content/groups/staging/

Copy link
Contributor Author

@wiiitek wiiitek Jun 4, 2018

Choose a reason for hiding this comment

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

Maven artifacts are something different than "release artifacts" that we use in cookbook.

"Release artifacts":

  • zip packages that groups similar AET stuff: bundles, configs, report app.

Maven artifacts:

  • are not grouped in any archives.

We could adjust AET cookbook to use Maven artifacts only (some work needed).
Or we could create new Maven artifacts - ZIP archives needed by cookbook.
Or maybe we just prepare some RC version that could be consumed from GitHub?
What do you think?

# Conflicts (resolved):
#	CHANGELOG.md
#	osgi-dependencies/aet-features.xml
#	vagrant/Vagrantfile
@wiiitek wiiitek merged commit f0f6451 into master Jun 16, 2018
@wiiitek wiiitek deleted the karaf-4.2.0 branch June 16, 2018 10:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants