Re: injecting symbols in QA mode

2014-08-12 Thread Ilya Obshadko
The situation is even more weird: are not supported by surefire plugin, while are not supported by jetty plugin. Maybe this is going to be useful for someone else - I spent a lot of time to figure it out. On Thu, Aug 7, 2014 at 9:51 PM, Ilya Obshadko wrote: > I finally found the answer. > >

Re: injecting symbols in QA mode

2014-08-07 Thread Ilya Obshadko
I finally found the answer. In fact, deprecated maven tag is not just deprecated, it's now ignored. When I've changed that to everything started to work as expected. On Fri, Aug 8, 2014 at 2:00 AM, Ilya Obshadko wrote: > I don't have any problems with module classes (yet). The problem is onl

Re: injecting symbols in QA mode

2014-08-07 Thread Ilya Obshadko
I don't have any problems with module classes (yet). The problem is only with injected configuration symbols. When I'm running 'mvn test', I can see that module binding works fine, but when it comes to service contribution methods, I receive an error. So I have a method in my main application mod

Re: injecting symbols in QA mode

2014-08-07 Thread Lance Java
As I mentioned, there's a PageTester constructor which accepts module classes. You can explicitly pass the modules you want to test. Please ignore my earlier comments regarding pom.xml. I was assuming you were talking about the jar manifest when you were discussing maven surefire properties. It's

Re: injecting symbols in QA mode

2014-08-06 Thread Ilya Obshadko
Unfortunately that didn't work either. Probably I'm missing something important. QaModule doesn't even seem to be loaded on startup. On Wed, Aug 6, 2014 at 9:44 PM, Ilya Obshadko wrote: > I'm running the test using 'mvn test'. That's why I expect all system > properties defined in the maven-sur

Re: injecting symbols in QA mode

2014-08-06 Thread Ilya Obshadko
I'm running the test using 'mvn test'. That's why I expect all system properties defined in the maven-surefire-plugin section to be available at runtime. But contributing them using QaModule makes sense, I'll try that. On Wed, Aug 6, 2014 at 6:19 PM, Lance Java wrote: > AFAIK the page tester d

Re: injecting symbols in QA mode

2014-08-06 Thread Lance Java
AFAIK the page tester does not reference web.xml. Depending how you are running your test, it might not "see" the jar manifest generated by pom.xml either (if the classes are on the classpath rather than the jar). You might need to use the second PageTester constructor where you explicitly pass an