I'm reviewing install4j (9.0.7, windows 10) and have created a simple java installer with some additional screens to enter custom variables that we use to configure our product.
The installer that is generated seems to work ok.
Because it is recommended for search purposes (to see were for example you are using custom variables) to generate a "project report" I tried this and to my surprise it generates an empty html file of 0kb in size.
Is this a "bug" or did I miss something that I should have done before generating the project report.
Any help is greatly appreciated.
This is a regression that can happen in 9.0.7, it will be fixed in the next bugfix release. Please contact support#ej-technologies.com to get a build where this is already fixed.
Related
I use github actions.
My gradle project use jacoco to produce a test coverage report, on the form of a website.
How can I display it directly on the browser ?
Actually when JaCoCo builds report in html format it produces a bunch of files and folders. So, there is no possibility to open that main html file directly in your browser. But here are possible solutions that might be useful for you:
Publish generated static files on some server, like GitHub Pages for
example. Where you can see generated report in a website mode (you
can configure notification with the link when published report is
ready).
Archive generated report and upload it as artifact. Then you
can easily find each report for each job if needed.
Build report as xml and just print it in output window.
Archive generated report and send it to some your running server.
Based on your needs maybe you find some of these suggestions useful but probably first option only directly answers your question.
I accidentally published Composite C1 from Visual Studio with "Precompile during publishing" when I first set it up and have now come to realize that several plugins do not work with precompile turned on. Unfortunately I have no idea how to reverse this. I've tried several things to no avail. I usually end up with a 500.0 error. If I go to the admin interface everything is working properly, and I can even preview the pages, but from the customer side all I get is a 500.0 error.
Of course I could republish from the Visual Studio project I have, but that project has the default template on it. I've tried copying what appears to be changed on the server to the original project but I end up with a 500 error. I've tried removing all the precompiled stuff on the server but I end up with a 500 error. I'm pretty lost.
At this point I'm willing to do anything. Is there a doc explaining how to copy the content to a newly downloaded copy, kind of like an upgrade doc but "side-grading"? I am using the most current version at the time of writing this 4.2 Update 1
Thank you
Solved use the PackageCreator suggested by wysocki's answer. It was not exactly straight forward to create the package. The errors can very cryptic at times. So here are some of the issues I encountered and how I got past them:
wysocki was correct to suggesting starting with a bare bones installation even though my original project was started with the Venus theme. I tried both ways.
I encountered issues with the MasterLayout and the Page Template Features which are currently not supported by the PackageCreator, although they may be supported in future versions. The solution was to add the missing elements to the fresh C1 project from the original C1 installation in the App_Data/PageTemplates and App_Data/PageTemplateFeatures folders.
A few times I ran into an issue where I added the same page or function twice to the PackageCreator. This was obviously my fault, but it should be mentioned that you can add the same site element twice which throws and error on import. Make sure you are careful to only getting one of each when creating the package to be exported.
If you are getting and error and it uses and Id like "4061397b-ee9e-4512-984d-f2b2d41eb654" I've found that it was very helpful to extract the zip file you are trying to import and then search the extracted folders for that Id. The lines with the Id usually have more information on them that will help you to identify exactly what content page or whatever the error is being generated from.
If you are using installed packages in your project like SimpleSearch for example, make sure you don't add it's functions to the PackageCreator. Install them separately.
I had an issue where I somehow had an element in the Data section that didn't have a "type". The error simply "The type cannot be empty". This was obviously tough to find so I suppose the lesson is, less is more. If you think your project might have a few elements that are unnecessary, don't add them at first and see if the project you import them into complains about missing them. It's much easier to troubleshoot missing elements than it is to figure out which element is causing the issue that you really didn't need.
Is there a doc explaining how to copy the content to a newly downloaded copy
You can try and export content / templates / anything else related to a "package" via Composite.Tools.PackageCreator.
Its latest version gives you quite a lot of flexibility in what you can export ("package") - please its user manual.
Once the package is made and downloaded, you can go on and install it on a new website. If you export / import a lot of content / templates etc, it makes sense to have a "Bare Bones" site as the new one.
All the starter sites like "Neptune", "Venus" are installed as a bunch of packages in specific order during Composite C1's initial setup.
I'm sure that I'm making some kind of rookie mistake, but I'm using EclEmma for the first time right now and can't figure out, despite checking numerous guides, how to export my coverage report. For reference, this is on Windows 8 x64 and using Eclipse Kepler (let me know if you need any more information than that).
I can see that the EclEmma has successfully run, and I can get into and play with the Coverage view as below:
However, right-clicking anywhere in the report offers only an option to "Export Session," never "Export Report," and going through my File -> Export dialog doesn't seem to do any better. I tried exporting the session as XML and a few different configurations, but it never got the code coverage report that I was looking for.
Is there something I'm doing wrong or need to ensure before I can export it? Thanks in advance.
As you do before, click right button and select "Export Session".
Type "report" and you can find the "coverage report" option.
Click "next"
You can get the Export report panel.
I built an Eclipse product. When I test the project in Eclipse everything works fine, I can do Help->Help Contents and see the help content my plugin contains.
If I export the product, and start it, everything works except that Help->Help Contents does nothing. I suspect that I am missing some plugins in my product dependencies. But I don't see which ?
I added all the org.eclipse.help* and the org.mortbay.jetty.* (since I noticed that when launching the Help Contents from my test in Eclipse, the content is served by jetty). But still no Help Content window after a product export.
Any idea what is missing in the product to display the Help Content ?
According to Lars Vogel it is
org.eclipse.help.ui
org.eclipse.help.webapp
org.eclipse.equinox.http.jetty
Another potential problem might be that you simply don't have your help content files in the product export. I would try setting a check mark for the help files in the "binary build" section of your build.properties, but I'm not sure here.
This thread is very useful for finding out which files in Netbeans should go into source countrol, but it doesn't cover all files.
In particular I'm wondering whether the following files should go into source control. Here are my assumptions/guesses:
nb-configuration.xml - easiest - the file itself in the comment says it should go into source control.
nbactions.xml - from what I see this file stores information typical to running the application. I.e. JVM arguments etc. So I suppose it is a question of taste - if you want other developers to have a "suggested" Run configuration - include it. Otherwise - don't. Correct?
catalog.xml - not sure what this does (I GUESS it's used by the editor to find out xml schemas and such to enable syntax coloring, but it's just a guess). Anyway - I see that this file has system-specific information (path) - so it shouldn't go into source control.
Can anyone confirm the above?
Thanks,
Piotr
I never put my IDE configuration files in the repository, for several reasons:
other colleagues may want to use theirs;
other colleagues may want to use other IDEs (such as Eclipse) and seeing those files (or even have to exclude them from the checkout) could be annoying for them;
some of these files are generally not related to a single project, others automatically generated, so no need to store them in the source code of every project.
In order to exclude them, our first solution was the .svnignore, but it was still logically wrong to modify some shared content for the specific needs of a single user, so we decided to be more strict:
in my ~/.subversion/config I have:
[miscellany]
global-ignores = nbactions.xml nbproject
Hope this helps,
Marcello
In my Maven based projects I put nbactions.xml into source control. Just make sure to change absolute paths to relative ones.
I put nbactions.xml into source control BUT there is a caveat: it's internal format can change so if your developers, for any reason, use different versions of NetBeans you could have to remove it because sharing it becomes nasty.
Recently I upgraded from NetBeans 7.3.1 to 7.4 and the "Run" action was giving a strange error message. I solved the problem by deleting and regenerating nbactions.xml: the old one had a custom Maven goal for the "Run" and "Debug" actions; it was org.codehaus.mevenide:netbeans-deploy-plugin:1.2.4:deploy it was not visible in the IDE v7.3.1 (perhaps it has been generated by an even older version for internal usage) and was generating a class not found for org.openide.util.Lookup in v7.4. I'm documenting the problem here because I found the solution by myself after an unsuccessful search on the Net. I hope this can help someone else.