I am following AEM tutorial wknd tutorial. I have created the project using archetype and installed it on local AEM instance. Unlike the tutorial when i create a new page i do not get the option to drag and drop components and neither am i able to find any components in side rail.
I went to the template to edit it in design mode and enable components but could not find design mode to edit it to enable components.
I am not sure what to do to follow along with the tutorial. Any help is much appreciated.
I was able to resolve the issue by installing the wknd project again using -Pclassic option in the maven command. The project was designed for Cloud service but after reading the description in github for AEM 6.x.x it worked.
Building for AEM 6.x.x
The project has been designed for AEM as a Cloud Service. The project is also backward compatible with AEM 6.4.8 and 6.5.5 by adding the classic profile when executing a build, i.e:
mvn clean install -PautoInstallSinglePackage -Pclassic
Related
TL;DR -> How to integrate a local Opendaylight Karaf App in the Opendaylight integration/distribution project, for local use? I am not looking to publish my code to upstream to official opendaylight repositories.
I am trying to understand how to make changes to source code of certain features in Opendaylight to fulfill my custom use-cases.
For this, I downloaded the Netconf Source code from "https://git.opendaylight.org/gerrit/netconf" and the distribution source code from "https://git.opendaylight.org/gerrit/integration/distribution".
I made certain modifications in the Netconf Code and built it using mvn clean install -Pq -Dcheckstyle.skip.
Now, how do I go about integrating these updates in the integration/distribution project?
FYI:
I am working on ODL "release/oxygen-sr2". However, I realise that newer versions are available and I am open to shifting to them.
Using Java 8 and Maven 3.6.0
I had been suggested that I could just maven build the Netconf Project code and run Apache Karaf from there. Any other feature could then be installed via the Karaf CLI. But, my use case would require modifications on multiple existing features and even creating a new feature. Therefore, this solution also doesn't work for me as I would still need to integrate everything in one central project.
Actually, it's pretty simple, but maybe not obvious. Build all the projects you
want locally, then build the integration/distribution project. Any artifacts it
finds in the local m2 repo will be used for the final int/dist karaf that will
get created.
in other words, for every project you want to customize, pull that repo, make
your changes, build it. Then as a last step, build the int/dist project.
I want to embed chrome inside a SWT application. I was trying with JCEF. But not able to succeed.
I came across the following link: How to integrate Chromium Embedded Framework (CEF) with java
But I don't want to use maven as mentioned in step3.
I need a step by step details of how to embed a chrome.
If you can't build JCEF you can use some maven builds and forks like:
GitHub: Pandomium - fork with maven builds and natvies
Maven: JavaCef - clean maven builds
~ I dont want to use maven
Maven just hosts jar files so you can download it and add to your project manually but it's not recommended at all.
Since you're using SWT, I think that you should checkout this: Browser implement Chromium support
This request lead to this project: Chromium for SWT
Currently is working on version 59 of chormium and uses the SWT Browser API.
I'm trying to migrate a netbeans/ant gwt project to an eclipse/maven gwt project.
For that I used the archetype gwt-maven-archetypes, to create a maven project, and after that I copied the sources.
I had succesfully been able to run codeserver and the application itself, using maven comands, as suggested by the archetype author. I even can debug on chrome dev console.
The problem, is that I want to debug from eclipse, and it seems eclipse gwt plugin, doesn't support the current structure.
Any ideas?
Thanks
I ended up, giving up this archetype, and I'm using now simple webapp maven archetype. I figured it out, but still a little tricky on my project.
So, as #ElHoss, has suggested I'm using SDBG. Besides that, I'm not using jetty, but my own tomcat installation, so I've followed this video instructions, together with the SDBG page video's instruction.
At the end, I have 3 Running Configuration items:
The one that starts Tomcat;
The one that starts codeserver;
Chrome Launcher, as instructed on SDBG page.
If you need plus information, please comment.
Thanks.
I'm new to Java EE development and I heard that If I have to learn the Java EE then the Spring MVC is best choice to learn and get Command of.
After downloading STS 3.6 bundle I'm having some troubles/issues in creating Maven Project. My STEPS are
1- Create new project
2- Error Dialog
It appears that you either don't have Maven installed, or your IDE is not aware of the installation. For the former problem, have a look here. For the latter problem, view this page for IDE you are using:
Eclipse
I would also like to recommend to get started with Spring using the Spring Tool Suite by using Spring Boot and the guides at http://spring.io/guides. You can import those guides directly into STS and start from there.
I also face with this thing too, but I found a solution that just update Maven project by right click on project -> Maven-> Update Project... or (Alt+F5) then check on force to update as image below :
It works perfect for me.
NOTE** internet connection is required
I have created project using Spring Tool Suite IDE, with below navigation.
New -> Spring Starter Project
But outcome was always simple maven M2 project with error symbol.
After project build completion I have updated maven project with option "Force Update of Snapshots/Release".
It turned my project M2 project into M2S Project
Thanks
Eclipse Vaadin plugin has cool autobuild feature. Just clicking "restart application" in debug console will bring up to date application version to live.
Unfortunately importing maven generated vaadin project(using m2e) and copy-pasting .project buildCommands and natures from vaadin eclipse plugin generated project does not works.
I'm unnable to "Run on server...", tomcat does not deploy app for unknown reason. I can see app in wtpapps folder but it still does not deploys.
You can build your Vaadin app as a regular Java library, by itself (not as a WAR, or anything complicated). Then do two things: Create another project that builds the actual WAR file, and create another project that sets up Jetty for direct execution (google for details on how to get Vaadin operating under Jetty standalone, using Jetty as a library). With that in place you can treat your Vaadin UI like a regular java program (fast, direct restart through the standard debug window), and still have it be a WAR file for deployment.
See this thread for details on how to set up Jetty (look for Launcher).
I have also stumbled upon this problem some time ago and eventually found this:
http://www.streamhead.com/maven-spring-vaadin-appengine/
It eventually helped me to get up and running after a scenario that has been very similar to what you have described.