Publish to artifactory and overwrite existing version with SBT - sbt

Does anyone know how I overwrite a version when publishing to artifactory using sbt? When I currently run sbt publish it gives the below error but I don't know how to set it to true
java.io.IOException: destination file exists and overwrite == false
I've also tried setting isSnapshot := true but then I get the below error
PUT operation to URL <url> failed with status code 409: Conflict
Any help would be greatly appreciated

You may need to give your Artifactory user Overwrite permissions. See the Managing Permissions documentation for details.

Related

Memcachier add-on for cloudcontrol is failing

I followed the installation guide at https://www.cloudcontrol.com/dev-center/Add-on%20Documentation/Data%20Storage/MemCachier. The memcachier server is up and running, I tested it from the command line. But my cloudcontrol app isn't able to access it.
Here's the error in our logs:
Info MemcachedError: error 40 from memcached_set: FAILED TO SEND AUTHENTICATION TO SERVER, no mechanism available, host: [my-memcachier-server-url]:11211 -> libmemcached/sasl.cc:221
Notice No worthy mechs found
This seems to be a SASL-related issue. Is it possible that cctrl does not have the correct sasl2 libraries installed? Did anyone else experience this problem?
Further info:
django-pylibmc==0.5.0 and pylibmc==1.4.1 in requirements.txt
url and credentials are read from the cctrl environment correctly
This is caused by the libmemched version bundled with the buildpack missing a patch (https://bugs.launchpad.net/libmemcached/+bug/1381160). Because it is a stackoverflow bug, it can work systematically on your machine while it systematically breaks in the container. I will update the python buildpack to use the patched libmemcached library from the stack.
In the meantime you can try to achieve this manually by setting the LD_LIBRARY_PATH environment variable to /usr/local/lib either via config add-on or web: env LD_LIBRARY_PATH=/usr/local/lib <your_command> in the Procfile.

Karaf cannot install war feature

Recently I need to deploy something on Karaf. I use Karaf 3.0.2 and event try 4.0.0M1. Both are not able to install war feature. Once I type feature:install war in console after Karaf start-up.
3.0.2 gives me:
Error executing command: Error resolving artifact org.apache.servicemix.specs:org.apache.servicemix.specs.activation-api-1.1:jar:2.2.0: Could not find artifact org.apache.servicemix.specs:org.apache.servicemix.specs.activation-api-1.1:jar:2.2.0
4.0.0M! gives me:
Erroe executing command: Error
I try to delete Maven and reinstall it. The issue is still there. It's not happened on other machine.
It's a strange issue. Could anyone meet it ever? Could anyone help me out?
As it works on the other machines, it's something on that certain machine.
Without much more details on the setup I'm using assumptions here.
1) No Network connection to the central repo
2) Using a Proxy wich isn't configured or configured wrong on the server
3) Using a nexus with credentials and those aren't configured or configured wrong
I encountered the same issue and it was because there were mirrors defined in my Maven settings.xml (due to usage in another project). After I commented them out I was able to install the karaf war deployer.

Unable install webconsole in ServiceMix 4.5.3

I deleted Cache and tmp directory of my serviceMix.
I'm trying to reinstall webconsole on using
features:install webconsole. I'm getting following error
Error executing command: Manifest not present in the first entry of the zip mvn:org.apache.felix/org.apache.felix.metatype/1.0.4
How can I solve this problem
There was a known problem with reorganization of maven repositories which caused some troubles. Please make sure that your local repository does not contain malformed JAR file (it happens sometimes with various gateways which redirects you to login page), then reconfigure repositories in etc/org.ops4j.pax.url.mvn.cfg and make entry
http://repo1.maven.org/maven2#id=central
First in list.

Symfony2 Composer Install

I am trying to install Symfony 2.1.3 (latest). I am running composer and installs everything okay. The only error that I get is:
Script Sensio\Bundle\DistributionBundle\Composer\ScriptHandler::clearCache
handling the post-install-cmd event terminated with an exception
[RuntimeException]
An error occurred when executing the "'cache:clear --no-warmup'" command.
It's being installed under www folder. I am running nginx and followed the composer approach. I read on internet that apache should be run manually not as a service, however I am using nginx instead. Does apache still have any bearing on it? I'm using debian squeeze.
Edit: As per AdrienBrault's suggestion the error was because the timezone was not set in the php.ini. Only with --verbose I could see the warning. Thanks guys.
Apache is not related - PHP is called via command line.
Most likely is the permission in the cache folder: did you check if the user that runs the composer update can actually write the cache folder?
Try to manually run rm -Rf app/cache/dev (for production environment replace dev with prod) and see if you get any permission error.
Also you will get this error if the default.timezone setting is not configured in php when running in CLI. To verify just run
php --info | grep timezone
and check that the setting date.timezone is correctly configured.
On the security side, setting 777 to the folder is not the optimal solution - if you have ACL enabled you could use that to correctly set up the permission for the cache and logs folder. Read more at the Symfony2 official installation page
I had this same issue for a while and after hours of face to brick wall pounding I realized... I have a .gitmodule in my project, and on initial checkout these submodules are NOT initialized and as such are not there for your composer to update, which results in the above error.
Make sure you run the following
git submodule update --init src/Acme/Sadness/Bundle
of course replace src/Acme/Sadness/Bundle with YOUR project namespace.
Hope this helps someone not go through the same pain I just did.
If you have vendor folder already I would remove it and install symfony 2.1.3 again via "composer.phar install". Problem might be coming from outdated version of composer
I had the same problem and I resolve in this way.
execute this on the console
and you should see something like this
$ locate php.ini
/etc/php5/apache2/php.ini
/etc/php5/cli/php.ini
/etc/php5/fpm/php.ini
the first line is probably your php.ini that appear when you do a phpinfo();
the problem is that when you execute composer update this no check the same php.ini
in my case the second line
all my sites work fine but always I had problems not now
after edit the second file and put the same time zone that you set in the first one
run
$ sudo service apache2 reload
and now
$ composer update
I hope that this work for you like work for me
regards
Emiliano

Artifactory remote repos and Terracota

I want to setup my maven settings.xml file to download all the external dependencies from Artifactory cache instead of download them directly from any of the public repositories like repo1, repo2 or Jboss. I followed the instructions at http://wiki.jfrog.org/confluence/display/RTF/Configuring+Artifacts+Resolution at but I'm stuck with an error with the terracota library, the error is:
Could not find artifact net.sf.ehcache:ehcache-terracotta:jar:2.5.0 in remote-repos
I tried adding terracota repository at the remote repositories section but this didn't worked either.
Please advice.
I can think of a couple of possibilities:
Your remote-repos cache isn't configured to point to the remote repository that contains the Terracotta files
Your build isn't using the correct organization or module name when resolving the dependency on Terracotta.
Could you add some info to your question detailing where exactly you are seeing the error message, and whether you can browse to ehcache-terracotta version 2.5.0 in Artifactory ?
Please add the terracotta repository to your artifactory
This is the URL= http://www.terracotta.org/download/reflector/releases
Don't worry if the test of the repo doesn't work...
The last step is to go to Edit Virtual Repository and add the new terracotta repo to the virtual repository called "Remote Repo".

Resources