Can someone explain to me how to upgrade taxonomies-module? Im currently running version 1.4 of taxonomy-module and I see that the current version is 1.4.2.
Must i disable the module in backend and clone the new source for contrib.taxonomies and rebuild in VS?
I am running 1.6 of Orchard.
Unless stated otherwise in a module's release notes you can simply overwrite the old source with the new (or over-install it with the new version from the Gallery or you have it as a cloned repository then just updating to tip). DB migrations will take care of themselves and you don't necessarily have to rebuild the solution as dynamic compilation will compile the new code on the next page load. (That is, unless you have a deployed Orchard site with dynamic compilation disabled.)
Related
Hallo I've failed to bind both versions of a LiteDB library to my project. There's a necessity to consume both versions to access old and new databases from GUI though.
Nothing, I've found on internet, functioned. The project took the newest one, 4.1.5.0 every time. Can You post the abrupts from .csproj and .config files which succeed?
I noticed that runtime version of both versions is identical. Can it be the cause?
I have published a global node package via npm to generate boilerplate templates for projects at my company.
I would like to compare the current version with the latest published in order to exit the process if it’s not the latest.
What node libraries would you recommend to check for the latest version.
Is there a way to auto update the global package if a new version is detected.
Remember this is an internal tool for my company so It’s critical they are creating projects with the latest templates and I’d like them to be able to update as automatically or easily as possible
Personal Suggestion
Instead of forcing the user to upgrade, another option is to publish your templates (as zip) on remote static server (e.g. S3). In such case, you can often update the zip to the latest template without upgrading the template generator.
generate-template angularjs-template:latest
generate-template angularjs-template:4.3
Answering Your Questions
What node libraries would you recommend to check for the latest version.
I am not sure if there is a library for this. However, you can build one very easily.
Create a JSON file which contains the package information (e.g. latest stable version, deprecation message, etc.).
Upload the JSON file to a remote static server.
Whenever the user runs your program, download the JSON file and check against the current package.json.
Show a deprecation warning if the user should upgrade.
process.exit() the application if the user must upgrade.
Is there a way to auto update the global package if a new version is detected.
I think it is better to leave the control to the user, because there could be some reasons why he doesn't prefer upgrade. For example, if the user has a bunch of projects started 10 months ago, he might want to use the same template for newer projects.
But if you really want to automate it, you might use the following code (not tested).
const { execSync } = require('child_process');
const pkg = require('./package.json')
execSync(`npm update -g ${pkg.name}`)
process.exit()
This question is about the usage of jhipster-generator.
I noticed that the react support (namely generator-jhipster-react) has been merged into generator-jhipster, but I found no guide on how to generate react projects by generator-jhipster.
Could anyone identify how to create react projects with generator-jhipster?
As of today (2017-11-23) this has just been merged into the master branch, so you can use it by using the project directly from GitHub.
This should be released very soon, as it will be included in our next version 4.11.0. As this is still in development, you will need to run it with the --experimental flag. This will be documented in the release notes (this is a new flag).
I am currently working on liferay upgradation from 6.0 to 6.2.2 GA3. I tried upgrading the services portlet. The services portlet of 6.0 version is built using mvn services-portlet-archetype whereas for 6.2 version the archetype is liferay-servicebuilder-archetype. The difference is that in 6.2 liferay-servicebuilder-archetype there are two modules:
Module 1: is a portlet which has our code logic
Module 2: is the services-portlet which has the class files generated during liferay:build-service. These files are archived into jar file which is later used inside the portlet(Module 1) module for the creation of the WAR file.
Whereas in 6.0, there is no concept of modules. The services class files generated during liferay:build-service are generated inside services folder under src/.
This liferay-servicebuilder-archetype is available only from Liferay 6.1+ versions as seen in mvnrepository. My guesses for the need of this new archetype from 6.1 version are:
1. To avoid committing the auto generated services files by mistake to our version control repo.
2. To be more modular.
But with this new archetype I found out that the build process consumes lot of permgen space and heap space(I have to double the heap and permgen space everytime I run the mvn clean package liferay:build-service as observed through jvisualvm). I was able to create the same portlet with services-portlet-archetype successfully deployed and working in 6.2 GA3 server(without extra permgen space and heapspace). But did not find any memory issues during its build.
My questions are:
1. Which of these two archetypes(liferay-servicebuilder-archetype or services-portlet-archetype) is a good practice for liferay 6.2 GA3.
2. Going forward if I need to upgrade all the 20+ portlets which I am using in my project should I need to create from archetype? (Takes lot of time and effort).
3. How to fix this issue of extra memory consumption if using liferay-servicebuilder-archetype is the best practice. The target folder seems to produce more class files than in services-portlet-archetype target folder.
4. The need for this new archetype is for the two benefits mentioned above(which I guessed) or is there anything else?
After waiting for 2+ weeks for an answer to this question, I am assuming that my following guesses are the correct answer to this question.
The need for this new archetype from 6.1 version is:
1. To avoid committing the auto generated services files by mistake to our version control repo.
2. To be more modular.
If there is a more convincing answer, I will choose that to be the best answer.
EDIT::::
Found this link useful
https://www.liferay.com/community/forums/-/message_boards/message/51303796
I'm using Orchard 1.6 and have a question regarding the build batch file.
When run, some default modules (Lucene, Content Permissions, Messages) do not get published. I cannot see any difference in file permissions between these modules and the modules that are included in the publish.
Dropping the DLL's in the dependencies folder works, but, I'd like to fix this issue with the build script. No errors are reported by the build script.
If it makes a difference, I'm using TFS 2010 for version control.
Really appreciate any pointers...
Open the orchard.proj file. That's what the build script is using.