JVM and Intellij uses the avro generated classes, not imported ones
up vote
0
down vote
favorite
While generating java code from Avro scheme using commerce hub Gradle plugin, it takes the object which has a field such as
"name": "ruleKey",
"type": [
"null",
{
"type": "enum",
"name": “Rule”,
"namespace": "com.testing.common.rules.api",
"symbols": [
"MIN_AGE",
“MAX_AGE”
]
}
]
, and generates Java class from the scheme, including enum fields such as Rule. In the same time, I am importing common rules(com.testing.common.rules.api) and it imports Rule as well. I would like to use methods from the common library, however, Avro generated model has a higher priority. ( The Java interpreter will look for classes in the directories in the order they appear in the classpath variable. In this case, the ones generated from the scheme) and it doesn’t let me use the imported class from the common library, because Avro already generated Rule enum class with the same package and name.
The used technologies are spring boot 2, Java 10 and commercehub.gradle plugin.
java spring spring-boot serialization avro
add a comment |
up vote
0
down vote
favorite
While generating java code from Avro scheme using commerce hub Gradle plugin, it takes the object which has a field such as
"name": "ruleKey",
"type": [
"null",
{
"type": "enum",
"name": “Rule”,
"namespace": "com.testing.common.rules.api",
"symbols": [
"MIN_AGE",
“MAX_AGE”
]
}
]
, and generates Java class from the scheme, including enum fields such as Rule. In the same time, I am importing common rules(com.testing.common.rules.api) and it imports Rule as well. I would like to use methods from the common library, however, Avro generated model has a higher priority. ( The Java interpreter will look for classes in the directories in the order they appear in the classpath variable. In this case, the ones generated from the scheme) and it doesn’t let me use the imported class from the common library, because Avro already generated Rule enum class with the same package and name.
The used technologies are spring boot 2, Java 10 and commercehub.gradle plugin.
java spring spring-boot serialization avro
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
While generating java code from Avro scheme using commerce hub Gradle plugin, it takes the object which has a field such as
"name": "ruleKey",
"type": [
"null",
{
"type": "enum",
"name": “Rule”,
"namespace": "com.testing.common.rules.api",
"symbols": [
"MIN_AGE",
“MAX_AGE”
]
}
]
, and generates Java class from the scheme, including enum fields such as Rule. In the same time, I am importing common rules(com.testing.common.rules.api) and it imports Rule as well. I would like to use methods from the common library, however, Avro generated model has a higher priority. ( The Java interpreter will look for classes in the directories in the order they appear in the classpath variable. In this case, the ones generated from the scheme) and it doesn’t let me use the imported class from the common library, because Avro already generated Rule enum class with the same package and name.
The used technologies are spring boot 2, Java 10 and commercehub.gradle plugin.
java spring spring-boot serialization avro
While generating java code from Avro scheme using commerce hub Gradle plugin, it takes the object which has a field such as
"name": "ruleKey",
"type": [
"null",
{
"type": "enum",
"name": “Rule”,
"namespace": "com.testing.common.rules.api",
"symbols": [
"MIN_AGE",
“MAX_AGE”
]
}
]
, and generates Java class from the scheme, including enum fields such as Rule. In the same time, I am importing common rules(com.testing.common.rules.api) and it imports Rule as well. I would like to use methods from the common library, however, Avro generated model has a higher priority. ( The Java interpreter will look for classes in the directories in the order they appear in the classpath variable. In this case, the ones generated from the scheme) and it doesn’t let me use the imported class from the common library, because Avro already generated Rule enum class with the same package and name.
The used technologies are spring boot 2, Java 10 and commercehub.gradle plugin.
java spring spring-boot serialization avro
java spring spring-boot serialization avro
edited Nov 20 at 10:11
asked Nov 20 at 8:36
Etibar Hasanov
9662721
9662721
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
up vote
0
down vote
IDEA honors class path ordering. First match wins ( as you already found out ) - so you have to reorder classpath elements in your project / module classpath setting.
add a comment |
up vote
0
down vote
Actually, none of the things you listed in your question really matter. As in: you have two classes x.y.Z, with the same name, and the package.
And that doesn't work. When you import x.y.Z, the JVM starts searching the class path, and will pick the first class it find. And there is nothing you can do about that.
Thus, the only solution: make sure that your class path only contains the class you intend to use. This is also a good preparation for the future, as Java9 will not allow you to have two modules with conflicting x.y.Z classes (in the same layer).
Actually, I didn't say out one part, in my case field Rule comes from a common library . Rule is a field in the scheme and in the same time it is imported by the project. When we generate java code from the scheme, then JVM understands it as two classes with the same name, and the package. However, it is basically the same, one generated from Avro scheme, another one imported from the common library. If there was a way to 'tell' avro plugin not generate the field, use existing ones, it would solve the issue.
– Etibar Hasanov
Nov 20 at 10:30
add a comment |
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
IDEA honors class path ordering. First match wins ( as you already found out ) - so you have to reorder classpath elements in your project / module classpath setting.
add a comment |
up vote
0
down vote
IDEA honors class path ordering. First match wins ( as you already found out ) - so you have to reorder classpath elements in your project / module classpath setting.
add a comment |
up vote
0
down vote
up vote
0
down vote
IDEA honors class path ordering. First match wins ( as you already found out ) - so you have to reorder classpath elements in your project / module classpath setting.
IDEA honors class path ordering. First match wins ( as you already found out ) - so you have to reorder classpath elements in your project / module classpath setting.
answered Nov 20 at 10:15
Konstantin Pribluda
11k12133
11k12133
add a comment |
add a comment |
up vote
0
down vote
Actually, none of the things you listed in your question really matter. As in: you have two classes x.y.Z, with the same name, and the package.
And that doesn't work. When you import x.y.Z, the JVM starts searching the class path, and will pick the first class it find. And there is nothing you can do about that.
Thus, the only solution: make sure that your class path only contains the class you intend to use. This is also a good preparation for the future, as Java9 will not allow you to have two modules with conflicting x.y.Z classes (in the same layer).
Actually, I didn't say out one part, in my case field Rule comes from a common library . Rule is a field in the scheme and in the same time it is imported by the project. When we generate java code from the scheme, then JVM understands it as two classes with the same name, and the package. However, it is basically the same, one generated from Avro scheme, another one imported from the common library. If there was a way to 'tell' avro plugin not generate the field, use existing ones, it would solve the issue.
– Etibar Hasanov
Nov 20 at 10:30
add a comment |
up vote
0
down vote
Actually, none of the things you listed in your question really matter. As in: you have two classes x.y.Z, with the same name, and the package.
And that doesn't work. When you import x.y.Z, the JVM starts searching the class path, and will pick the first class it find. And there is nothing you can do about that.
Thus, the only solution: make sure that your class path only contains the class you intend to use. This is also a good preparation for the future, as Java9 will not allow you to have two modules with conflicting x.y.Z classes (in the same layer).
Actually, I didn't say out one part, in my case field Rule comes from a common library . Rule is a field in the scheme and in the same time it is imported by the project. When we generate java code from the scheme, then JVM understands it as two classes with the same name, and the package. However, it is basically the same, one generated from Avro scheme, another one imported from the common library. If there was a way to 'tell' avro plugin not generate the field, use existing ones, it would solve the issue.
– Etibar Hasanov
Nov 20 at 10:30
add a comment |
up vote
0
down vote
up vote
0
down vote
Actually, none of the things you listed in your question really matter. As in: you have two classes x.y.Z, with the same name, and the package.
And that doesn't work. When you import x.y.Z, the JVM starts searching the class path, and will pick the first class it find. And there is nothing you can do about that.
Thus, the only solution: make sure that your class path only contains the class you intend to use. This is also a good preparation for the future, as Java9 will not allow you to have two modules with conflicting x.y.Z classes (in the same layer).
Actually, none of the things you listed in your question really matter. As in: you have two classes x.y.Z, with the same name, and the package.
And that doesn't work. When you import x.y.Z, the JVM starts searching the class path, and will pick the first class it find. And there is nothing you can do about that.
Thus, the only solution: make sure that your class path only contains the class you intend to use. This is also a good preparation for the future, as Java9 will not allow you to have two modules with conflicting x.y.Z classes (in the same layer).
answered Nov 20 at 10:20
GhostCat
87.4k1684144
87.4k1684144
Actually, I didn't say out one part, in my case field Rule comes from a common library . Rule is a field in the scheme and in the same time it is imported by the project. When we generate java code from the scheme, then JVM understands it as two classes with the same name, and the package. However, it is basically the same, one generated from Avro scheme, another one imported from the common library. If there was a way to 'tell' avro plugin not generate the field, use existing ones, it would solve the issue.
– Etibar Hasanov
Nov 20 at 10:30
add a comment |
Actually, I didn't say out one part, in my case field Rule comes from a common library . Rule is a field in the scheme and in the same time it is imported by the project. When we generate java code from the scheme, then JVM understands it as two classes with the same name, and the package. However, it is basically the same, one generated from Avro scheme, another one imported from the common library. If there was a way to 'tell' avro plugin not generate the field, use existing ones, it would solve the issue.
– Etibar Hasanov
Nov 20 at 10:30
Actually, I didn't say out one part, in my case field Rule comes from a common library . Rule is a field in the scheme and in the same time it is imported by the project. When we generate java code from the scheme, then JVM understands it as two classes with the same name, and the package. However, it is basically the same, one generated from Avro scheme, another one imported from the common library. If there was a way to 'tell' avro plugin not generate the field, use existing ones, it would solve the issue.
– Etibar Hasanov
Nov 20 at 10:30
Actually, I didn't say out one part, in my case field Rule comes from a common library . Rule is a field in the scheme and in the same time it is imported by the project. When we generate java code from the scheme, then JVM understands it as two classes with the same name, and the package. However, it is basically the same, one generated from Avro scheme, another one imported from the common library. If there was a way to 'tell' avro plugin not generate the field, use existing ones, it would solve the issue.
– Etibar Hasanov
Nov 20 at 10:30
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53389044%2fjvm-and-intellij-uses-the-avro-generated-classes-not-imported-ones%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown