nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

stash plugin - ApplicationProperties

AbrahamA

I created stash plugin from archetype using "atlas-create-stash-plugin" and then followed atlas-mvn eclipse:eclipse and imported into eclipse.

Pointed MAVEN installation to atlassian maven.

When import project in eclipse I get error ApplicationProperties cannot resolve to type.

Added per this post maven dependency:

https://jira.atlassian.com/browse/STASH-4161

I get error runing mvn clean install

-------------------------------------------------------
 T E S T S
-------------------------------------------------------
Running it.com.collabconsulting.ndg.MyComponentWiredTest
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further detail
s.
[INFO] [talledLocalContainer] 2013-12-25 12:14:15,831 WARN  [http-bio-7990-exec-
8]  c.a.j.s.w.f.BypassableDelegatingFilterProxy Bypassing [requestAttributeFilte
r]; no Spring WebApplicationContext is available
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 1.126 sec &lt;&lt;&lt; FA
ILURE!

Results :

Tests in error:
  it.com.collabconsulting.ndg.MyComponentWiredTest

How do I resolve this, please let me know.

Abe

plan-9502726-BT-13.log

Accepted answers

cofarrell

Hi Abraham,

Honestly, the easiest thing to do is to delete "src/test/java/it/com/collabconsulting/ndg/MyComponentWiredTest.java" for now. Later on if you want to add integration tests for your components you may want to revisit why it was failing, but it's certainly not important at this stage.

Merry Christmas.

Charles

All comments

cofarrell

Hi Abraham,

Merry Christmas.

Charles

AbrahamA

Thanks Charles. I did that could successfully do the build

For sal-api, I added dependency

&lt;dependency&gt;
        &lt;groupId&gt;com.atlassian.sal&lt;/groupId&gt;
        &lt;artifactId&gt;sal-api&lt;/artifactId&gt;
        &lt;version&gt;2.10.9&lt;/version&gt;
        &lt;scope&gt;provided&lt;/scope&gt;
    &lt;/dependency&gt;

in pom.xml, but I had ApplicationProperties error, then I addded sal-api jar manually as external jar and it resolved, why did it not resolve and add to referenced libraries when I added pom.xml entry.

I cleaned project, restarted eclipse etc. Not that I am blocked because manually adding worked, just wanted to know why pom.xml entry did not make any difference.

cofarrell

Hi Abraham,

What do you mean it did not resolve? Was it not compiling in maven (ie clean install) or just Eclipse?

Charles

AbrahamA

I was expecting sal-api.jar as part of "Referenced Libraries" , since I added it as maven dependency in package explorer and it was not there..

I also added following entry in atlassian-plugin.xml

<component-import key="applicationProperties" interface="com.atlassian.sal.api.ApplicationProperties" />

But in eclipse I continued to see error, until I added sal-api jar as shown in attachment.