Skip to main content

Magnolia 5 project setup issue - Could not find artifact org.vaadin.addon

By

I have try to build magnolia 5 project with maven option (An archetype to create a Magnolia project (a parent pom and a webapp ). and this project can not build due to fallowing error.
[ERROR] Failed to execute goal on project magnolia-webapp: Could not resolve dependencies for project magnolia-webapp:war:1.0-SNAPSHOT: The following artifacts could not be resolved: org.vaadin.addon:easyuploads:jar:7.0.0, org.vaadin.addons:refresher:jar:1.2.1.7, org.vaadin.addons:cssinject:jar:2.0.3, org.vaadin.addons:icepush:jar:0.5.3, org.vaadin.addons:gwt-graphics:jar:1.0.0, org.vaadin.addons:ckeditor-wrapper-for-vaadin:jar:7.8.3: Could not find artifact org.vaadin.addon:easyuploads:jar:7.0.0 in magnolia.nexus.public (http://nexus.magnolia-cms.com/content/groups/public/) -> [Help 1]

Solution - add fallowing vaadin addons respository to project pom.xml

<repository>
   <id>vaadin-addons</id>
   <url>http://maven.vaadin.com/vaadin-addons</url> 
</repository>





Labels:

Comments

Post a Comment

Popular posts from this blog

is not a JMX compliant Standard MBean

By
I got the fallowing exception and issue solved. If your are using MBean , MBean Interface and Implementation should be in same package, Otherwise use MXBean. javax.management.NotCompliantMBeanException: MBean class comlanka.rest.controller.DataManagerController does not implement DynamicMBean, and neither follows the Standard MBean conventions (javax.management.NotCompliantMBeanException: Class comlanka.rest.controller.DataManagerController is not a JMX compliant Standard MBean) nor the MXBean conventions (javax.management.NotCompliantMBeanException: comlanka.rest.controller.DataManagerController: Class comlanka.rest.controller.DataManagerController is not a JMX compliant MXBean)         at com.sun.jmx.mbeanserver.Introspector.checkCompliance(Introspector.java:176)         at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:317)         at com.sun.jmx.mbeanserver.Jmx...
Post a Comment
Read more

AWS amplify hugo App build specification amplify.yml

By
 I needed a content-oriented site with solely static content for a little project I'm working on, so Hugo was an obvious choice. I looked into using AWS Amplify to host it, But the default amplify.yml not working for me and can't find the correct build file, I have modified the amplify.yml to build the Hugo cms. Hope this is helpful, Please comment. version : 1 frontend : phases : build : commands : - npm install - npm run build:webpack && npm run build:hugo artifacts : baseDirectory : dist files : - '**/*' cache : paths : []
Post a Comment
Read more

hamcrest and junit java.lang.NoSuchFieldError: NONE

By
Issue - When you using hemcrest with JUnit5 you may get  java.lang.NoSuchFieldError: NONE error. Solution - Add junit-vintage-engine to classpath           <dependency>             <groupId>org.junit.vintage</groupId>             <artifactId>junit-vintage-engine</artifactId>             <version>5.3.1</version>             <scope>test</scope>         </dependency>  Full Exception - java.lang.NoSuchFieldError: NONE at org.hamcrest.DiagnosingMatcher.matches(DiagnosingMatcher.java:12) at org.hamcrest.beans.SamePropertyValuesAs.hasMatchingValues(SamePropertyValuesAs.java:63) at org.hamcrest.beans.SamePropertyValuesAs.matchesSafely(SamePropertyValuesAs.java:31) at org.hamcrest.TypeSafeDiagnosingMatcher.matches(TypeSafeDiagnosing...
Post a Comment
Read more