Using the maven-archetype-plugin is the simplest way. First lets reproduce the problem on a sample project.The version of maven-source-plugin used was 2.1.1. I've tested the following instructions with Maven 2.0.11, 2.2.1 and 3.0-beta-1. Until the problem is permanently addressed, here I outline a workaround that prevents the duplicate generate-sources phase from running. So what this means is that when using the maven-release-plugin or activating the release-profile manually by setting the releaseProfile property, source:jar goal gets called during the build, which will trigger the execution of generate-sources lifecycle phase to run, even if it already did in the same build.Ĭhanging the Maven Super POM to instead call source:jar-no-fork would fix this issue, yet changing the Super POM is not something taken lightly, and in fact may have never been proposed for this case. The profile defines a maven-source-plugin and maven-javadoc-plugin configuration that attaches the jar goals of those plugins to the package phase. This was/is a way for the release plugin to activate the creation of source and javadoc jars for a release by default.
It can be activated by the releaseProfile property being set, in this case to true. Here I attempt to explain what is really going on and provide you a real workaround for it.Īn old relic of the maven-release-plugin is that in Maven's Super POM there is defined a profile with id of release-profile. Suprisingly these issues are marked fix or mention what looks like a workaround and no matter what you do, the plugin goals you have attached to the generate-sources phase are still being executed twice. You find several complaints and reports open that mention a similar problem related to the maven-sources-plugin sources:jar goal causing the generate-sources phase to execute twice. You predictably do a google search and scan the Maven issues. You are now trying to figure out why your sources are being generated twice, or more specifically why the generate-sources lifecycle phase is being executed twice. When you decide to finally release your project using the maven-release-plugin, you notice that your source generation plugin executes twice, slowing your build and possibly even breaking it. This looks like it works great for a while running mvn package.
You require to generate some sources, so you've figured out how to attach a plugin goal to the generate-sources lifecycle phase. So, you've been using Maven to build your project. com.install4j.5517-2803-0637-4585.7502 This process is and was re-exec'd from, but for some reason we are trying re-exec to. Relaunching in 32-bit, and tagging sub-processes to prefer 32-bit with $JAVA_ARCH=i386. Some nasty log messages from trying to log an install4j based app that suffered this problem $cp /System/Library/Frameworks/amework/Resources/MacOS/JavaApplicationStub
Sudo /Volumes/SeeTest/SeeTestAutomation\ Installer.If you see this in your OSX Console log after trying to launch a Java application, the problem is obvious - you've been given an application with a Java stub launcher that cannot be run on your version of OSX. var files you have copied.Įxample: hdiutil mount /Users/Experitest/SeeTest_macos.dmg Step 9: Navigate to the library containing the. Step 8: A terminal window will open, enter username and password. Step 7: Open Putty (DoubleClick), enter the Remote Mac's IP, select SSH and click open.
Step 5 (Optional): This step is necessary only if you want to install SeeTest Automation in a different folder then the current installation folder of SeeTest Automation, or if SeeTest Automation was never installed on this Mac.
Pscp pscp 4: Enter your password and wait for the copying process to finish. Step 3: Run the following command from cmd in order to copy the installer (.dmg file) to the destination folder:
Step2: Open CMD and navigate to the folder containing pscp. In order to enable remote login, go to System Preferences > Sharing, and check the option "Remote Login" Remote Login must be enabled in the destination Mac.