Maven: How to add a patched dependency
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
I am building eclipse plugins with maven, for eclipse oxygen 3.
My maven configuration uses following repository.
<repository>
<id>eclipse</id>
<url>http://download.eclipse.org/releases/neon/201705151400/</url>
<layout>p2</layout>
</repository>
And one of my plugins depends on our custom patched version of org.eclipse.tcf.te.tcf.launch.cdt that exists in this repository.
I would like to specify in my maven to use patched version of this plugin for solving it's dependency.
How should I do it? Suppose I have a local separated P2 repo that has this only patch.
If I am adding a new repository, the build still fails.
<repository>
<id>TCF</id>
<url>file:<my_path>/tcf_patch-1.5.0.v20181116</url>
<layout>p2</layout>
</repository>
java eclipse maven tycho p2
asked Nov 16 '18 at 18:12
LidiaLidia
1711215
add a comment |
I am building eclipse plugins with maven, for eclipse oxygen 3.
My maven configuration uses following repository.
<repository>
<id>eclipse</id>
<url>http://download.eclipse.org/releases/neon/201705151400/</url>
<layout>p2</layout>
</repository>
And one of my plugins depends on our custom patched version of org.eclipse.tcf.te.tcf.launch.cdt that exists in this repository.
I would like to specify in my maven to use patched version of this plugin for solving it's dependency.
How should I do it? Suppose I have a local separated P2 repo that has this only patch.
If I am adding a new repository, the build still fails.
<repository>
<id>TCF</id>
<url>file:<my_path>/tcf_patch-1.5.0.v20181116</url>
<layout>p2</layout>
</repository>
java eclipse maven tycho p2
asked Nov 16 '18 at 18:12
LidiaLidia
1711215
You mistake the idea of Eclipse repository with Maven repository
– user10639668
Nov 16 '18 at 18:25
If you have a patched dependency you would more likely benefit from including it within the project and installing it manually.
– Compass
Nov 16 '18 at 18:34
That's what I wouldn't like to do 'Compass', if I understood correctly. I am integrating the workflow in jenkins, I will have a jenkins job that will checkout sources and run maven for build, and during build it should know to use patched plugin for solving dependency. I can not add sources for tcf open sources plugin in my repo.
– Lidia
Nov 16 '18 at 18:41
add a comment |
I am building eclipse plugins with maven, for eclipse oxygen 3.
My maven configuration uses following repository.
<repository>
<id>eclipse</id>
<url>http://download.eclipse.org/releases/neon/201705151400/</url>
<layout>p2</layout>
</repository>
And one of my plugins depends on our custom patched version of org.eclipse.tcf.te.tcf.launch.cdt that exists in this repository.
I would like to specify in my maven to use patched version of this plugin for solving it's dependency.
How should I do it? Suppose I have a local separated P2 repo that has this only patch.
If I am adding a new repository, the build still fails.
<repository>
<id>TCF</id>
<url>file:<my_path>/tcf_patch-1.5.0.v20181116</url>
<layout>p2</layout>
</repository>
java eclipse maven tycho p2
asked Nov 16 '18 at 18:12
LidiaLidia
1711215
I am building eclipse plugins with maven, for eclipse oxygen 3.
My maven configuration uses following repository.
<repository>
<id>eclipse</id>
<url>http://download.eclipse.org/releases/neon/201705151400/</url>
<layout>p2</layout>
</repository>
And one of my plugins depends on our custom patched version of org.eclipse.tcf.te.tcf.launch.cdt that exists in this repository.
I would like to specify in my maven to use patched version of this plugin for solving it's dependency.
How should I do it? Suppose I have a local separated P2 repo that has this only patch.
If I am adding a new repository, the build still fails.
<repository>
<id>TCF</id>
<url>file:<my_path>/tcf_patch-1.5.0.v20181116</url>
<layout>p2</layout>
</repository>
java eclipse maven tycho p2
java eclipse maven tycho p2
asked Nov 16 '18 at 18:12
LidiaLidia
1711215
asked Nov 16 '18 at 18:12
LidiaLidia
1711215
edited Nov 16 '18 at 18:31
Lidia
asked Nov 16 '18 at 18:12
LidiaLidia
1711215
asked Nov 16 '18 at 18:12
LidiaLidia
1711215
asked Nov 16 '18 at 18:12
LidiaLidia
1711215
1711215
You mistake the idea of Eclipse repository with Maven repository
– user10639668
Nov 16 '18 at 18:25
If you have a patched dependency you would more likely benefit from including it within the project and installing it manually.
– Compass
Nov 16 '18 at 18:34
That's what I wouldn't like to do 'Compass', if I understood correctly. I am integrating the workflow in jenkins, I will have a jenkins job that will checkout sources and run maven for build, and during build it should know to use patched plugin for solving dependency. I can not add sources for tcf open sources plugin in my repo.
– Lidia
Nov 16 '18 at 18:41
add a comment |
You mistake the idea of Eclipse repository with Maven repository
– user10639668
Nov 16 '18 at 18:25
If you have a patched dependency you would more likely benefit from including it within the project and installing it manually.
– Compass
Nov 16 '18 at 18:34
That's what I wouldn't like to do 'Compass', if I understood correctly. I am integrating the workflow in jenkins, I will have a jenkins job that will checkout sources and run maven for build, and during build it should know to use patched plugin for solving dependency. I can not add sources for tcf open sources plugin in my repo.
– Lidia
Nov 16 '18 at 18:41
You mistake the idea of Eclipse repository with Maven repository
– user10639668
Nov 16 '18 at 18:25
You mistake the idea of Eclipse repository with Maven repository
– user10639668
Nov 16 '18 at 18:25
If you have a patched dependency you would more likely benefit from including it within the project and installing it manually.
– Compass
Nov 16 '18 at 18:34
If you have a patched dependency you would more likely benefit from including it within the project and installing it manually.
– Compass
Nov 16 '18 at 18:34
That's what I wouldn't like to do 'Compass', if I understood correctly. I am integrating the workflow in jenkins, I will have a jenkins job that will checkout sources and run maven for build, and during build it should know to use patched plugin for solving dependency. I can not add sources for tcf open sources plugin in my repo.
– Lidia
Nov 16 '18 at 18:41
That's what I wouldn't like to do 'Compass', if I understood correctly. I am integrating the workflow in jenkins, I will have a jenkins job that will checkout sources and run maven for build, and during build it should know to use patched plugin for solving dependency. I can not add sources for tcf open sources plugin in my repo.
– Lidia
Nov 16 '18 at 18:41
add a comment |
1 Answer
1
active
oldest
votes
Update
I have solved my problem, and my original attempt to solve it was correct. Just the patch I used was wrong.
So, basically it is sufficient for maven.
If Original plugins are accessible from
<repository>
<id>eclipse</id>
<url>http://download.eclipse.org/releases/oxygen/201804111000</url>
<layout>p2</layout>
</repository>
And my patch resides in
<repository>
<id>TCF</id>
<url>file: ../TCF_PATCH_20181116</url>
<layout>p2</layout>
</repository>
Maven is able to apply latest version of eclipse plugins available from provided repositories for solving dependencies. Cool ;)
answered Nov 16 '18 at 23:01
LidiaLidia
1711215
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
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%2f53343295%2fmaven-how-to-add-a-patched-dependency%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Update
I have solved my problem, and my original attempt to solve it was correct. Just the patch I used was wrong.
So, basically it is sufficient for maven.
If Original plugins are accessible from
<repository>
<id>eclipse</id>
<url>http://download.eclipse.org/releases/oxygen/201804111000</url>
<layout>p2</layout>
</repository>
And my patch resides in
<repository>
<id>TCF</id>
<url>file: ../TCF_PATCH_20181116</url>
<layout>p2</layout>
</repository>
Maven is able to apply latest version of eclipse plugins available from provided repositories for solving dependencies. Cool ;)
answered Nov 16 '18 at 23:01
LidiaLidia
1711215
add a comment |
Update
I have solved my problem, and my original attempt to solve it was correct. Just the patch I used was wrong.
So, basically it is sufficient for maven.
If Original plugins are accessible from
<repository>
<id>eclipse</id>
<url>http://download.eclipse.org/releases/oxygen/201804111000</url>
<layout>p2</layout>
</repository>
And my patch resides in
<repository>
<id>TCF</id>
<url>file: ../TCF_PATCH_20181116</url>
<layout>p2</layout>
</repository>
Maven is able to apply latest version of eclipse plugins available from provided repositories for solving dependencies. Cool ;)
answered Nov 16 '18 at 23:01
LidiaLidia
1711215
add a comment |
Update
I have solved my problem, and my original attempt to solve it was correct. Just the patch I used was wrong.
So, basically it is sufficient for maven.
If Original plugins are accessible from
<repository>
<id>eclipse</id>
<url>http://download.eclipse.org/releases/oxygen/201804111000</url>
<layout>p2</layout>
</repository>
And my patch resides in
<repository>
<id>TCF</id>
<url>file: ../TCF_PATCH_20181116</url>
<layout>p2</layout>
</repository>
Maven is able to apply latest version of eclipse plugins available from provided repositories for solving dependencies. Cool ;)
answered Nov 16 '18 at 23:01
LidiaLidia
1711215
Update
I have solved my problem, and my original attempt to solve it was correct. Just the patch I used was wrong.
So, basically it is sufficient for maven.
If Original plugins are accessible from
<repository>
<id>eclipse</id>
<url>http://download.eclipse.org/releases/oxygen/201804111000</url>
<layout>p2</layout>
</repository>
And my patch resides in
<repository>
<id>TCF</id>
<url>file: ../TCF_PATCH_20181116</url>
<layout>p2</layout>
</repository>
Maven is able to apply latest version of eclipse plugins available from provided repositories for solving dependencies. Cool ;)
answered Nov 16 '18 at 23:01
LidiaLidia
1711215
answered Nov 16 '18 at 23:01
LidiaLidia
1711215
answered Nov 16 '18 at 23:01
LidiaLidia
1711215
answered Nov 16 '18 at 23:01
LidiaLidia
1711215
1711215
add a comment |
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.
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%2f53343295%2fmaven-how-to-add-a-patched-dependency%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
You mistake the idea of Eclipse repository with Maven repository
– user10639668
Nov 16 '18 at 18:25
If you have a patched dependency you would more likely benefit from including it within the project and installing it manually.
– Compass
Nov 16 '18 at 18:34
That's what I wouldn't like to do 'Compass', if I understood correctly. I am integrating the workflow in jenkins, I will have a jenkins job that will checkout sources and run maven for build, and during build it should know to use patched plugin for solving dependency. I can not add sources for tcf open sources plugin in my repo.
– Lidia
Nov 16 '18 at 18:41