I am trying to extend the m2release plugin to free style project. So far I am able to get the "maven release build" option for the Build environment in the configuration of a free style project. But when I select this option for the free style project the "Perform maven release" button is not popping up in the left side menu.
My concern is am I trying something which is not feasible. I mean asking M2release-plugin to perform release for free style project.
If this is feasible, which class of the plugin should I look in to get the "perform maven release" enabled for free style project? I am currently trying to modify the M2ReleaseBuildWrapper class and M2ReleaseAction class.
Related
I'm currently working on a React App in visual studio code. However I need my friend to also work on the same project. I deployed it successfully to github but of course it only uploads the static build folder. How do I get the entire project across to my friend so he can work on it?
Follow this instruction link in their documentation on how to add an existing project to github. Or even simpler, VSCode has a built in "Publish to Github" command, use it. Make sure you don't ignore anything you don't want in the .gitignore file. You don't need to upload the static build folder though, ignore it in the .gitignore file. Your friend can build the project himself.
Open the Github repository settings and look for something called "Manage access". There you can see an option where you can invite a collaborator. That way your friend will have write access to the repo and can push change to the code.
Told him to clone the repo and accept the invite -> done.
Finally, I thought of moving my project from Eclipse to IDE to IntelliJ. So, I carried out the following steps:
1. Installed Codenameone plugin in IntelliJ.
2. Import existing project to IntelliJ. Now I project structure is as shown in the figure.
Here, CodenameOne-Project is the main project including source folders images and all. The common and barcode-common consists of java classes required for main project(i.e.CodenameOne-Project). So, I am able to import CodenameOne-Project in IntelliJ, and if I add other folder as module by adding dependency and all, it dont look like CodenameOne project anymore. I cant properly import complete project. Any help on this would be very helpful. Thanks
P.S: I want to maintain same project structure.
We don't support importing projects between IDE's as our project structure is IDE agnostic. The IDE won't recognize that and would fail. The right thing to do is create a new project with the same package name/main class name as your existing project then copy your src & res directories on top of the new project and copy codenameone_settings.properties on top of the new project file.
I created JHipsterApplication - at the time of the prompt "Would you like to enable translation support with Angular Translate? (Y/n)" - I provided "n". Now application is created and I want to add translation support to my application. Is there anyway to add translation support after the application is created or enable something which is disabled at the time of creating the application?
I tried "bower install angular translate" but it still says Translation is disabled for this project. Language can not be added". Thank you for your help.
Edit the .yo-rc.json file in your project folder and re-generate your app using jhipster --with-entities, it will ask you for overwriting some files and maybe you'll have to merge some others.
Alternatively, after having edited the .yo-rc.json file, you could use also run the upgrade generator jhipster upgrade --force, it will handle your custom changes better.
I've created a new Angularjs project using Yeoman.
yo angular
It create a huge project folder, near 190Mb of node_modules libraries.
Don't know if this is normal, but i've tried to import the created project in eclipse as a new JavaScript project and after that, eclipse become really slow, probably cause isn't able to validate/handle such a big project.
Is it normal that a new AngularJs project scaffolded with Yeoman take so much disk space?
If so, how can I make eclipse handle it?
Thanks for any information.
I had the same issue and it crashes Eclipse occasionally. My solution is to use Eclipse resource filter to ignore Yeoman related folders.
Right click on your project, select Properties.
Resource->Resource Filters
Click on "Add..."
Select "Exclude all" under "Filter type"
Select"Folders" under "Applies to"
Enter "node modules" in the text box and click on OK
Repeat 1-6 for the "bower-components" folder
After these two folders are ignore my Eclipse is running fine. I'm running Luna (4.4.1) btw.
The theming guide says to run Sencha Cmd to:
- setup the workspace
- generate a test app to test the custom theme
The test app created in the theming guide is located inside the workspace folder. My question is, does the app that will use the theme need to be located inside the workspace folder? Or can it reside elsewhere, and it simply uses the built custom theme?
We have an existing app that we now want to use a custom theme, so the app is not inside a workspace. Can I just create the workspace for the custom theme, and make changes for styling necessary to implement the theme? Do I need to make configuration changes in the generated workspace so it is aware of the location of the code for the app which is not in the workspace?
Thanks in advance!
As far as I know, your project, where you wanted to apply the theme, must be generated by Sencha CMD. After generating the project, copy everything from the existing project to the new sencha cmd-generated project.
On the terminal, execute sencha generate theme my-custom-theme on the application directory. Your my-custom-theme will be created on the packages directory of your project folder. In order to use this theme, edit sencha.cfg found on the [project folder]/.sencha/app/. Change the app-theme to app.theme=my-custom-theme.
In order for the changes to take effect, execute sencha app refresh.
The theme, i.e. .scss files, eventually converted into a CSS file. You need to include this generated CSS file in your index.html. This is regardless of how you get or generate the CSS file.
I do not think your existing project need to be inside your new 4.2 theme project. However, it is much easier to test if you are creating a new theme and they reside in the same project.
It is not difficult to put your existing .js files into 4.2 project. I had to replace the app directory from the old project and some update to files. You can find the details in the ExtJS upgrade guide.
In the new Sencha Architect 3, there's an added feature of Application Styling. See here: http://docs.sencha.com/architect/3/#!/guide/styling
I'm not sure but I think you can import your current ExtJS project into the Architect and start styling your application.