Maven is not packaging Robotium.jar into apk for testing???

[GoogleCodeExporter]

Maven is not packaging Robotium.jar into apk for testing???

[GoogleCodeExporter]

Hi John!

I have spent some time now trying to reproduce your error. Using your partial 
pom snippets above, I have recreated a two-module project which uses your exact 
parameters. Everything works fine with Maven.

Here is the code:
http://github.com/hugojosefson/robotium-issue13

You can run 'mvn install' from the root of that code repository, and it works. 
It runs the tests which depend on Robotium.

Note that when you set up your project with Maven, you should build it with 
Maven. IDE's such as IntelliJ IDEA and Eclipe may or may not do the things you 
expect. Maven is always the stable constant that you can rely on to build 
according to the pom.xml.

Since you only posted parts of your poms, and no code nor project contents, I 
guessed what the projects contained. (That is also the reason why this took so 
long; I had to set aside time to re-create these projects. I apologise for the 
wait.) If your projects differ from what I recreated, please fork my repo on 
github and commit+push changes to it so it exhibits the error you reported. Or 
simply attach a zip file to this issue with everything needed to build it and 
reproduce the error.

On the other hand, if you have found a solution, please let us know so we can 
close this issue!

Thanks,
Hugo

Original comment by [email protected] on 12 Aug 2010 at 1:51

• Changed state: Incomplete

[GoogleCodeExporter]

Hi Hugo,

I'm sorry, I thought I'd get some requests for more information, I will 
attached the Test project and the Apk and try to describe the setup in more 
details.

No, I haven't solved it yet.

I'll update this soon.

Thanks for your time.

Original comment by [email protected] on 13 Aug 2010 at 12:35

[GoogleCodeExporter]

Hi,

I've spent some time analyzing your changes and the differences between my 
setup and structure. It seems to me that the way I named the test packages were 
incorrect.

I loaded your project off git, ran perfectly - just replaced the submodules and 
spent some tiem using trial and error. 

The test package was overlord.test, instead of being inside the main overlord 
package which required me to import the source package. I think that was the 
screw up.

Everything works perfectly now.

Original comment by [email protected] on 13 Aug 2010 at 5:23

[GoogleCodeExporter]

Not valid and therefore closed.

Original comment by [email protected] on 24 Aug 2010 at 4:55

• Changed state: Invalid