I am trying to upload a test using maven on AWS device farm , But while uploading the test error coming that
"There was a problem processing your file. Could not find test jar."
Have added all the dependencies/jars , don't know why this error is coming .If anyone have solution or idea about this it would be really helpful.
Thanks
Please package your tests using the documented instructions for TestNG or JUnit. You can also watch our webinar that walks through the maven configuration.
The command to use for packaging tests is mvn clean package --DskipTests=true.
Related
I am trying to follow, https://github.com/qubole/s3-sqs-connector and trying to load the connector but seems like the connector is not available on maven and while generating the buiold manually the sqs classes are not loaded.
Can some1 guide me on this.
Thanks,
Dipesh
Update:
S3-SQS connector is now released on maven central.
https://mvnrepository.com/artifact/com.qubole/spark-sql-streaming-sqs
You should be able to use it now. Get back to us if you face any problems.
Unfortunately, registration of the s3-sqs-connector in spark-packages is still pending. We'll try to release the package in maven central directly as soon as possible but it should take a few days at the very least.
In the meantime, you can clone the repository and build the jar yourself if required.
My application is developed in Grails 2.4.4. It uses MongoDB-3.0.2 plugin. I use Hudson as my CI system.
Sometimes when the job in hudson tries to build the application war, I get the below error.
Error | Resolve error obtaining dependencies: Failed to read artifact
descriptor for
org.grails:grails-datastore-gorm-plugin-support:jar:3.1.3.BUILD-SNAPSHOT
(Use --stacktrace to see the full trace)
It doesn't happen all the time. Many times the war was built successfully. Recently I am facing this problem more frequently.
In one of the question similar to this this, someone has suggested to change the Snapshot version to Release version. I tried it but didn't help me.
I also faced this problem in dev environment few times.
Can anyone let me know what could be the issuse? Could it be connectivity problem between the repository and my system?
Our SSL certificate expired this morning. We are working to get it addressed. An option to use as a workaround would be to use http instead of https. See comments at https://github.com/grails/grails-core/issues/9200.
The process is almost complete to get the new cert in place. Sorry for the trouble.
I have installed Eclipse Java EE Luna Release (4.4.0) and App Engine SDK 1.9.10
I have created a new Google - Web Application Project and selected the Generate Project Sample Code option. I changed nothing about the project.
The generated project successfully deploys and runs locally. However when I deploy this to AppSpot I get an error message "Remote Procedure Call - Failure" when clicking on the "Send" button on the sample form.
Are there other steps I need to perform in order for the generated project to be successfully deployed to AppSpot?
My goal is to have a starting application that deploys so I can start learning to use Objectify and GWT to build applications. If there is a better way to go about this please suggest it.
Kind regards
Sean
I think seem to remember that sample code for the GWT builds a RPC-based HelloWorld or greeting example. In the auto-generated sample interface you type a name, a RPC call is made to server side and you get "Hello"+yourName or similar as a callback.
Check this link:
http://www.gwtproject.org/doc/latest/tutorial/appengine.html
This is a more advanced app, StockWatcher, from the GWT tutorials which is also RPC based and adapted for the GAE. You could start here: http://www.gwtproject.org/doc/latest/tutorial/gettingstarted.html to build this app (is really easy) and follow to the link above to deploy StockWatcher on the GAE, or check directly the steps on the first link and try to deploy the GWT "Greetings" example.
If you have already tried this or you do and there's still a problem, please provide the full stack trace, or the code you think might be causing the problem, so we have a better insight of the problem.
I have installed magento test Automation framework in local machine as below reference PDF.
http://www.magentocommerce.com/images/uploads/download/MagentoTestAutomationFrameworkInstallationGuide.pdf
All the installation setup has completed as per the reference.
After that i have added my project to netbeans. When i try to add the project in netbeans it seems error.
Below is the error message, which is i got from netbeans.
magento\app\design\adminhtml\default\default\template\catalog\product\attribute\js.phtml
This is my first try of Magento test automation tools. i don't know what was went to wrong.
Any help my appreciation.
Perhaps you can try changing a bit the directory structure
From
magento\app\design\adminhtml\default\default\template\catalog\product\attribute\js.phtml
To
magento\app\design\adminhtml\default\template\catalog\product\attribute\js.phtml
In my experience, Magento directory structure changes across its versions.
I have to Work with WorkerRole project to deploy some services to perform the data sync with the other databses. i tried to publish but stuck, Internalization, Starting, Preparing, Recovering and finally aborted.
After getting the above stituation i build a simple workerrole project and tried to upload the result is same.
And i am not able to find out the problem with the same.
Please provide some help.
A typical problem, when deploying, is having a connection string pointing to the local emulated storage. This is the first thing I'd check if the worker role code runs locally in the emulator but fails when being published to Windows Azure.