mhisoft / evault Goto Github PK

search
right click to bring up the context menu
export the item
Export from the search result does not work

The export menu item in the right click context menu font size is off. too small. not adjusted per the font size.

Hi,

for scientific purposes I tried to clone eVault and build it from source code. I realize that the configuration is a little bit more complex, so I thought I should get your help instead of spending a lot of time figuring out how to do it by myself.

If I got it right, at least I also need to clone the common-utils and deploy them on my local maven repo, right? Is there anything else you can tell me about the build process which might help?
I am not an IntelliJ user (usually running Eclipse) nor do I work with gradle and maven that much. The combination of both together with multiple IntelliJ modules scared me off a bit.

My biggest struggle is, to get the parent maven module.

<parent>
  <groupId>org.mhisoft.java.apps.common</groupId>
  <artifactId>common-parent</artifactId>
  <version>1.0</version>
  <relativePath>../parent-pom/pom.xml</relativePath>
</parent>

Is does not seem to be accessible in your Github.

Best wishes,
Stefan

Hi again,

vfsjfilechooser will not build with new Java versions anymore as the javadoc-plugin does not accept the current doc without specifying the correct -tag specifying the java version of the code (6 in this case).

MavenReportException: Error while creating archive:
[ERROR] Exit code: 1 - javadoc: error - The code being documented uses modules but the packages defined in http://download.oracle.com/javase/6/docs/api/ are in the unnamed module.

Obviously, this issue is just relevant for building with Maven. If you don't use Maven but just import and build the project with IntelliJ (without triggering Maven) no errors will occur.

Best wishes,
Stefan

Allow to export item to existing vault separately. so that you can ship that export vault and the receiving user can import multiple items at once.

remember the pass to the export vault so use don't need to repeatedly enter it while exporting multiple items.

Hi,

as your imageviewer fork does not offer an issue tracker, please allow me to mention here that the compiler compliance level of imageviewer is set to 1.6 (for the maven-compiler-plugin in pom.xml as well as in imageviewer.iml).
On line 160 of ImageComponent.java, however, you use a method which is documented to be used with 1.7+.
...
if (c.isValidateRoot()) {
...

Consider updating the compliance level of the artifact.

Best wishes,
Stefan

when importing an vault to the current vault, try to use the current vault password first. if they are the same, allow to open the to-be-imported vault directly without need to enter the password again.

just save it quietly and close the vault.