I am trying to find what were my answers to the questions on an old Jhipster proyect and I can not find how to see them in the configuration of the project.
Is there a file were I can check if whether I choose to use JHipster Registry or not, Angular or React, Maven or Gradle? Of course, some of the choices can be found looking at the files, but is there any specific config file that saves the answers?
Thanks
In the .yo-rc.json file in your project
Related
I am trying to override the a template Entity.java.ejs in my custom blueprint to add some extra functionality. Unfortunately JHipster uses its default one if generate an entity. I don’t want to overwrite the whole writing. Is there a possibility to override only certain ones and use JHipster default templates for the rest?
Helo friend,
in this period I see an application jhipster with a partial custom .ejs defining a default for others components.
The problem is that the overriding is very huge, and cabled only for a specific version 6.9.1 of jhipster.
If this is a good idea to custom a particolar application with a particolar version and with a specific cabling code ok, but is not good if you want a generic custom generator jhipster context, where you can "inject" only custom files, giving overriding of all scope original generator.
I try to search some answers searching on web, and your question is anyway a good clue to define a better solution that I see now.
The problem that I see is that jhipster environment dont have a "handling" approach about .ejs templates, when is very strong and straighweird when you use .jdl file .
An easly customization of templates of any jhipster application created with command "jhipster", ad example.
And searching I see this link https://github.com/jhipster/generator-jhipster/issues/1749
an issue of original jhipster generator where someone consider a good idea to use "subgenerator" using yeoman to modulerize this templates and with all benefits.
This is a another clue to understand somethings.
good luck and thanks
I was wondering if somebody could help me with this issue, which hopefully will not be complicated.
I am running a project using Angular4, and I want to use this component.
https://www.npmjs.com/package/range-datepicker
I've tried to run bower install range-datepicker, but if then I use the <range-datepicker> tag in my project it won't recognise it.
In addition, I've added
"range-datepicker":"0.0.13"
to my package.json file, and running npm install it installs it and I can see the files in node_modules.
However, I still cannot use the <range-datepicker>, so I was wondering if someone can help me with this issue. I don't know if maybe I should add some script or style in my angular.json file
That library does not provide an Angular component, but rather a WebComponent.
WebComponents are usable in Angular, but you need to take care of a few extra things.
I suggest that you look for documentation on using WebComponents in Angular.
Here's one link to get you started: https://www.sitepen.com/blog/2017/09/14/using-web-components-with-angular/
Is there something similar to "maven site plugin (javadoc)" is available for node? To be more specific, we are looking for a node package which can covert .md files in a reactjs project into html files. By convention each folder of our project has a markdown file which holds detailed documentation. We are looking for a tool (cli) which we can fire during the build process to create a documentation folder in the build (destination directory)- specifically interested in static HTML generation.
Thanks,
San
What have you looked for so far? Just googling "node MD to HTML" gives plenty of potential modules like this one and this one.
Have you tried some and they haven't worked? What have you looked for?
Found https://react-styleguidist.js.org/docs/documenting.html for my project. Awesome tool (though it is not equivalent to Maven Site).
I have an instance of crafter running with crafter-studio-publishing-receiver-2.5.3-aio.jar, I need to locate the source code for the jar file.
Is this the right repository
What is the significance of the word "legacy" in the name of the project?
You can find the source code here:
https://github.com/craftercms/legacy-deployer
The specific version can be found by checking the manifest of the jar.
- unzip the jar
- open ./META-INF/MANIFEST.MF
- locate the property Implementation-Build: 87c84d58313b2bcbdca306de69758320aee174d0
This value can be placed in github to get the exact code you are looking for.
Example:
https://github.com/craftercms/legacy-deployer/blob/87c84d58313b2bcbdca306de69758320aee174d0/cstudio-publishing-receiver-zip/pom.xml
The reason we renamed the project "legacy-deployer" in github is that with Crafter 3.x we are moving to a new deployment system. Without going too deep on this: The new system is based on Git pulls, as you can imagine, this approach has many benefits. It will support the same concepts (callbacks etc) as the now "legacy" deployer.
In order to present a brand new way of developing a web application, our team decided to create an Angular 2 web application that will be integrated within an already existing Maven Project in Eclipse Mars which DOES NOT use NodeJS nor Angular.
We are currently using the frontend-maven-plugin belonging to com.github.eirslet and managed to download and install both node.exe and npm.
Now, here is the deal: our web application has its own package.json file with all the configuration required to run properly, BUT we would like to be able to differentiate between the web applications, as each one of them belongs to a different working directory (i.e. com.webapp.app01, com.webapp.app02, ...).
As the plugin does not let the user use the npm install command on different directories, we were wondering about how we could reach this goal... maybe using a general package.json, but generating all .js and dependency files in each project directories.
Would that be something even possible?
Could you give us some help?
Thank you.
Cheers!
What I would suggest is to have a multi-module maven project, with a common parent, and children, that would give you this kind of architecture:
parent-project
|-child-project1 (java project)
|-child-project2 (webapp1)
|-child-project3 (webapp2)
|....
|-child-projectn (webapp n-1)
This way you can have for each web-app the frontend plugin available. And you can handle the flow of the build from the parent project (for instance if webapp2 needs to be built before webapp1, you can orchestrate it from the parent)
We decided to generate all the libraries locally and upload them to SVN, due to the fact that the already existing structure cannot be changed and the maven plugin is too much limited for our purpose.
Thank you for your replies, though. :-)