Jasper file not found when build with maven, working fine in eclipse
the prob im facing is, when Im running my project in eclipse its able to find my jasper file and showing the report but when im making jar of my project and running it, its not able to find my jasper file and throwing FileNotFoundException..
Path Im using :"jasperReport = "srccommyprojectjasperTestReportTamplate_V1.jasper";" -
I have attached My project structure image below:
Project Structure Image
Any help is appreciated.
maven jasper-reports file-not-found
add a comment |
the prob im facing is, when Im running my project in eclipse its able to find my jasper file and showing the report but when im making jar of my project and running it, its not able to find my jasper file and throwing FileNotFoundException..
Path Im using :"jasperReport = "srccommyprojectjasperTestReportTamplate_V1.jasper";" -
I have attached My project structure image below:
Project Structure Image
Any help is appreciated.
maven jasper-reports file-not-found
add a comment |
the prob im facing is, when Im running my project in eclipse its able to find my jasper file and showing the report but when im making jar of my project and running it, its not able to find my jasper file and throwing FileNotFoundException..
Path Im using :"jasperReport = "srccommyprojectjasperTestReportTamplate_V1.jasper";" -
I have attached My project structure image below:
Project Structure Image
Any help is appreciated.
maven jasper-reports file-not-found
the prob im facing is, when Im running my project in eclipse its able to find my jasper file and showing the report but when im making jar of my project and running it, its not able to find my jasper file and throwing FileNotFoundException..
Path Im using :"jasperReport = "srccommyprojectjasperTestReportTamplate_V1.jasper";" -
I have attached My project structure image below:
Project Structure Image
Any help is appreciated.
maven jasper-reports file-not-found
maven jasper-reports file-not-found
asked Jan 1 at 19:16
KrishKrish
44
44
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
This has nothing to do with jasper, it's a more general problem locating the files by their absolute path. When you create a jar, the folder structure is not the same. 'src' is not kept, as one example. Just open it like an archive with 7Z or something like that, and you can see.
Use relative paths when trying to locate files in the code. For example, if you are in the controller package, it should be something like "../jasper/TestReportTamplate_V1.jasper" ('..' represents the parent folder, '.' represents the current folder - go from there).
Sorry to say, but I read and get to know that '.' and '..' work in file system(in eclipse) but when its exported in jar, jar wont have the file system structure. so it wont work.
– Krish
Jan 17 at 7:37
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%2f53998250%2fjasper-file-not-found-when-build-with-maven-working-fine-in-eclipse%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
This has nothing to do with jasper, it's a more general problem locating the files by their absolute path. When you create a jar, the folder structure is not the same. 'src' is not kept, as one example. Just open it like an archive with 7Z or something like that, and you can see.
Use relative paths when trying to locate files in the code. For example, if you are in the controller package, it should be something like "../jasper/TestReportTamplate_V1.jasper" ('..' represents the parent folder, '.' represents the current folder - go from there).
Sorry to say, but I read and get to know that '.' and '..' work in file system(in eclipse) but when its exported in jar, jar wont have the file system structure. so it wont work.
– Krish
Jan 17 at 7:37
add a comment |
This has nothing to do with jasper, it's a more general problem locating the files by their absolute path. When you create a jar, the folder structure is not the same. 'src' is not kept, as one example. Just open it like an archive with 7Z or something like that, and you can see.
Use relative paths when trying to locate files in the code. For example, if you are in the controller package, it should be something like "../jasper/TestReportTamplate_V1.jasper" ('..' represents the parent folder, '.' represents the current folder - go from there).
Sorry to say, but I read and get to know that '.' and '..' work in file system(in eclipse) but when its exported in jar, jar wont have the file system structure. so it wont work.
– Krish
Jan 17 at 7:37
add a comment |
This has nothing to do with jasper, it's a more general problem locating the files by their absolute path. When you create a jar, the folder structure is not the same. 'src' is not kept, as one example. Just open it like an archive with 7Z or something like that, and you can see.
Use relative paths when trying to locate files in the code. For example, if you are in the controller package, it should be something like "../jasper/TestReportTamplate_V1.jasper" ('..' represents the parent folder, '.' represents the current folder - go from there).
This has nothing to do with jasper, it's a more general problem locating the files by their absolute path. When you create a jar, the folder structure is not the same. 'src' is not kept, as one example. Just open it like an archive with 7Z or something like that, and you can see.
Use relative paths when trying to locate files in the code. For example, if you are in the controller package, it should be something like "../jasper/TestReportTamplate_V1.jasper" ('..' represents the parent folder, '.' represents the current folder - go from there).
answered Jan 3 at 20:51


LauraLaura
1,328911
1,328911
Sorry to say, but I read and get to know that '.' and '..' work in file system(in eclipse) but when its exported in jar, jar wont have the file system structure. so it wont work.
– Krish
Jan 17 at 7:37
add a comment |
Sorry to say, but I read and get to know that '.' and '..' work in file system(in eclipse) but when its exported in jar, jar wont have the file system structure. so it wont work.
– Krish
Jan 17 at 7:37
Sorry to say, but I read and get to know that '.' and '..' work in file system(in eclipse) but when its exported in jar, jar wont have the file system structure. so it wont work.
– Krish
Jan 17 at 7:37
Sorry to say, but I read and get to know that '.' and '..' work in file system(in eclipse) but when its exported in jar, jar wont have the file system structure. so it wont work.
– Krish
Jan 17 at 7:37
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%2f53998250%2fjasper-file-not-found-when-build-with-maven-working-fine-in-eclipse%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