If I include this in my pom:
validate
process-resources
features-validate-descriptor
target/features.xml
src/main/resources/config.pr
Hi,
1. yes, I agree. I will create a Jira and fix that. More over, for
backward compatibility purpose, it makes sense to support resolver
attribute even if we don't use it.
https://issues.apache.org/jira/browse/KARAF-4109
2. No problem ;)
Do you use feature validation (made by the K
Hi, thanks for the help.
1. So it's an error in the archetype?
2. Sorry. Rookie mistake. I forgot to include my minimum distribution
features.
What is the best way to do it in my own feature or in the distribution?
--
View this message in context:
http://karaf.922171.n3.nabble.com/Beginning-wi
Hi,
1. yes OBR resolver is now deprecated as we have the FeaturesResolver now.
2. Features are missing for your feature (it's not closed feature). In
your case, it looks like aries-blueprint feature is missing.
Regards
JB
On 11/13/2015 09:19 AM, conejo wrote:
Hello.
I have several problems
Hello.
I have several problems with version 4.0.3, possibly caused by my
inexperience with Karaf
1. I created a feature and a distribution using the archetypes of karaf
4.0.3.
When generating the feature I get the next item in the pom.xml:
(OBR)
And to start the distribution which includes that f
