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

properties files are doubled in non-existing path #235

Closed
wofrank opened this Issue Mar 2, 2015 · 7 comments

Comments

Projects
None yet
3 participants
@wofrank

wofrank commented Mar 2, 2015

Description
In my installation I have all properties files doubled within a non-existing folder.
The right location is product-lib/resources/* but jabylon also offers the translations in resources/*.

Version

  • 1.1.3
  • both: Windows and Linux
  • using git team provider

More details
After adding a git project to jabylon and doing a scan, I have all properties files twice in the system:

See the structure in jabylon:
structure_jabylon

So I am able to navigate to the non existing file:
Home /workspace /MTP /master /fr /resources /level2 /level2_fr.properties /

The following (correct) file is also available in jabylon:
Home /workspace /MTP /master /fr /product-lib /resources /level2 /level2_fr.properties /

The following screenshot shows the project structure in file system:
project_structure

I also get some messages on scanning the directory:
DEBUG o.j.p.i.PropertyFileDescriptorImpl Tried to load non-existing property file. Path: /$WORKSPACE_PATH/MTP/master/resources/level2/2level2_fr.properties

@jutzig

This comment has been minimized.

Owner

jutzig commented Mar 2, 2015

I think this problem was solved in this commit:
4f6d820
I did not release this version yet but if you want I can produce a snapshot build that includes the fix so you can confirm if this solves the issue for you

@wofrank

This comment has been minimized.

wofrank commented Mar 2, 2015

Thanks for the fast feedback.
A snapshot would be nice, if there is not an easy workaround.

@svogt

This comment has been minimized.

@jutzig

This comment has been minimized.

Owner

jutzig commented Mar 2, 2015

This won't help. The fix is not in master but in a topic branch. I'll either post a link to a custom build or merge the changes to master...

@jutzig

This comment has been minimized.

Owner

jutzig commented Mar 2, 2015

I merged the changes back to master so the snapshot build now contains this fix and several others.
http://jenkins-jabylon.rhcloud.com/job/jabylon/lastSuccessfulBuild/artifact/releng/standalone/target/jabylon-standalone.zip
Please let me know if this solves the issue for you. If so, I will create a new release this week.

@wofrank

This comment has been minimized.

wofrank commented Mar 3, 2015

Great. Solves the Problem. Many thanks.
It solves also an issue that it was not possible to create a terminology project. I guess it was the same issue, as the exception was in fixed calulate... method.

@wofrank wofrank closed this Mar 3, 2015

@jutzig

This comment has been minimized.

Owner

jutzig commented Mar 3, 2015

Great, then I will create a new release

@jutzig jutzig added this to the 1.1.4 milestone Mar 4, 2015

@jutzig jutzig self-assigned this Mar 4, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment