Try changing the version of your play plugin in project/plugins.sbt addSbtPlugin("play" % "sbt-plugin" % "2.1.3") 2.1.3 is the latest release, I dont see a 2.0 in http://repo.typesafe.com/typesafe/ivy-releases/play/sbt-plugin/scala_2.9.2/sbt_0.12/

This is covered in the HSQLDB Guide: http://www.hsqldb.org/doc/2.0/guide/deployment-chapt.html#dec_snapshot_repos The idea is to use the latest snapshot automatically.

Build your project using maven mvn clean install now all the dependencies downloaded to your local Maven repository.(you can define it.) Then all the dependencies are in one location. Go to module(project) properties in IntelliJ IDEA by right click on that project. set your local repository as maven repository. Then re import dependencies. Now you solved that issue. If you have more issues leave a comment here

I added some repos to ~/.sbt/repositories. This solved the problem. Now the file looks like this: [repositories] local sbt-releases-repo: http://repo.typesafe.com/typesafe/ivy-releases/, [organization]/[module]/(scala_[scalaVersion]/)(sbt_[sbtVersion]/)[revision]/[type]s/[artifact](-[classifier]).[ext] sbt-plugins-repo: http://repo.scala-sbt.org/scalasbt/sbt-plugin-releases/, [organization]/[module]/(scala_[scalaVersion]/)(sbt_[sbtVersion]/)[revision]/[type]s/[artifact](-[classifier]).[ext] maven-central: http://repo1.maven.org/maven2/ You should look at this, too: http://www.scala-sbt.org/0.13.0/docs/Detailed-Topics/Proxy-Repositories.html But what still worries me is the question if this is an individual case for me and my system or if others have such problems, too. Did I mi

ANT 1.6.5 is a very old version of ANT. The following example was tested with ANT 1.9.0: <project name="demo" default="build"> <target name="bootstrap"> <mkdir dir="${user.home}/.ant/lib"/> <get dest="${user.home}/.ant/lib/commons-net.jar" src="http://search.maven.org/remotecontent?filepath=commons-net/commons-net/3.3/commons-net-3.3.jar"/> <get dest="${user.home}/.ant/lib/oro.jar" src="http://search.maven.org/remotecontent?filepath=oro/oro/2.0.8/oro-2.0.8.jar"/> </target> <target name="build"> <ftp server="ftp.apache.org" userid="anonymous" password="me@myorg.com"> <fileset dir="htdocs/manual"/> </ftp> </target> </project> The bootstrap target installs the missi

Take a look at this buildpack that cleans snapshots for SBT based apps. heroku config:set BUILDPACK_URL=https://github.com/ethul/heroku-buildpack-scala.git#feature-clean-snapshots Originally mentioned here: https://github.com/heroku/heroku-buildpack-scala/issues/31

The Maven client does not true support dynamic revisions. The closest thing it supports are snapshot revisions, where a revision like 1.0-SNAPSHOT, is resolved to the latest time-stamped artifact. I think you may be confusing the Maven POM with the REST API used by Nexus. This the ability to specify a "LATEST" version: https://repository.sonatype.org/service/local/artifact/maven/redirect?r=central-proxy&g=log4j&a=log4j&v=LATEST&e=jar

The way it works well for us (in combination with the maven-android-sdk-deployer: <dependency> <groupId>com.viewpagerindicator</groupId> <artifactId>library</artifactId> <version>${viewpagerindicator.version}</version> <type>apklib</type> <exclusions> <exclusion> <groupId>com.google.android</groupId> <artifactId>android</artifactId> </exclusion> <exclusion> <groupId>com.google.android</groupId> <artifactId>support-v4</artifactId> </exclusion> </exclusions> </dependency> We are also building with IntelliJ. Usually by simply opening the pom.xml

Note that the contribution calendar only reflects contributions done on the master branch of repos. Pushes for other branches wouldn't appear. I do see a contribution on your calendar for your repo (the second one might take a bit of time to appear: the refresh might not be immediate) But... you still can hack the contribution calendar ;) As the OP Mikhail Erofeev's remarks, and as described in GitHub help page: You'll need to link your git email to your GitHub account, so that we'll know who to associate contributions with. Once you do this, you might need to contact support so that we can backfill your previous contributions. The other case is when you are pushing commits with the wrong email as author/committer: the GitHub script (git filter-branch) would allow you to rectify

First of all, the way you deal with standart events is confusing and overcomplicated. You dont need to pass events to constructor See my last edit in previous topic on how it can be simplified. Also, as i mentioned in previous topic, the common way to deal with complicated event network in large applications is to implement EventsAggregator pattern (http://codebetter.com/jeremymiller/2009/07/22/braindump-on-the-event-aggregator-pattern/). There are zillions of various implenetations availible on the web, so i leave it up to you to pick one. I will use this interface for example purposes: interface IEventsAggregator { //sends message to network void Publish(object message); //adds object to the list of handlers void Subscribe(object listener); //removes object from the

I had a similar issue which was resolved by disabling some of the checks made by the Java HttpUrlConnection which failed on the redirect. You can try the flag -Djsse.enableSNIExtension=false as suggested here

You are probably not activating the profile correctly before the profile in settings.xml put something like <activeProfiles> <activeProfile>default</activeProfile> </activeProfiles> Remember this about activeByDefault This profile will automatically be active for all builds unless another profile in the same POM is activated using one of the previously described methods. All profiles that are active by default are automatically deactivated when a profile in the POM is activated on the command line or through its activation config. if you want to confirm if this is the issue, look at the active profiles by running help:active-profiles

Since there seems to be no answer, I'll at-least describe my workaround: Instead of using <link href=@routes.Assets.at("stylesheets/style.css") rel="stylesheet" type="text/css" /> in my template HTML, I'm using <link href="assets/stylesheets/styles.css") rel="stylesheet" type="text/css" /> Since I'm not invoking routes.Assets.at, there is no issue with not finding the value routes. (However, I'm guessing this workaround will easily crumble when I would have need of more complex templates)

Can you paste the $cat .git/config output here for reference. Sometimes it is better to remove the remotes that are misbehaving from there and re-add it using the git remote add command again.

Make sure all slf4j-packages (slf4j-api, slf4j-log4j12, jcl-over-slf4j) are of the same version. Especially mismatches in the minor version (between the api and the jcl-bridge) are problematic and should be avoided. Since you use maven, it shouldn't be difficult to explicitly declare the same specific version for all those packages. See also here: http://www.slf4j.org/codes.html#version_mismatch

Check the dependency type. There are so called pom type of dependencies, which act as a list of other dependencies. To be able to fetch them, you have to mark them as pom dependencies in your pom.xml If you only need the server component, try searching for this string 'org.eclipse.jetty:jetty-server:9.0.3.v20130506'

I'm no Dagger expert, but you have 2 issues: you have a cyclical dependency: you helper want to have the activity injected, your activity wants to have the helper injected. I don't think Dagger can resolve this your activity tries to get injected twice, once with the activity-level graph, once with the application-level graph Here's what I did to get it to work: in ScbeHelper: remove the @Inject annotation in BaseActivity: remove ((protoApp)getApplication()).inject(this); in ActivityModule: remove your provideActivity method (it's not going to be used anymore), and add the following method: @Provides @Singleton ScbeHelper provideScbeHelper() { return new ScbeHelper(activity); } What this does is it provides your ScbeHelper with the context it needs, but leaves only 1 annotati

The closest approach to what you want to do is to use <classesClassifier> as <project> ... <artifactId>mywebapp</artifactId> <version>1.0-SNAPSHOT</version> ... <build> <plugins> <plugin> <artifactId>maven-war-plugin</artifactId> <version>2.3</version> <configuration> <attachClasses>true</attachClasses> <classesClassifier>someClassifier</classesClassifier> </configuration> </plugin> </plugins> </build> ... </project> but this approach will always put the classifier as your_jar-classifier.jar and if you create and empty or spaced tag, it will default to -classes

Ok it seems like the sequence in which keys are listed in ~/.ssh/config matters. Initially it was # User_A Host github.com-User_A HostName github.com User git PreferredAuthentications publickey IdentityFile ~/.ssh/id_rsa IdentitiesOnly yes # User_B Host github.com-User_B HostName github.com User git PreferredAuthentications publickey IdentityFile ~/.ssh/id_rsa_user_b IdentitiesOnly yes # http://serverfault.com/questions/400633/capistrano-deploying-to-different-servers-with-different-authentication-methods Host example.com IdentityFile ~/.ssh_keys/example_env.pem ForwardAgent yes Afterwards I did this: # User_B Host github.com-User_B HostName github.com User git PreferredAuthentications public

I've found two solutions for this problem. Since I am using Java configuration for Spring, I had to ensure that my contextConfigLocation was set properly. I am using a jar file that contains beans with Spring stereotypes, so I had to ensure that the jar file was being properly built in eclipse. When building the jar file, I had to ensure that the Add Directory entries options was checked. These two steps solved this problem. I hope this helps!

You can either commit the artifacts to a private source control repository, or push them to a private binary repository. The only suitable software-as-a-service binary repository that I'm aware of at this time is Artifactory Online. If you go with a binary repository, you'll also have to provide Travis with (temporary) credentials to download the artifacts. One way to do this would be to configure the Travis build to set an environment variable containing the necessary information.

Change @Service("CommonSQLService") to @Service("commonSQLService") or you can just use @Service if you're not implementing the CommonSQLService interface anywhere else.

I have this sorted I identified that there was a discrepancy between the plugins of the manually exported plugins in eclipse against the plugins that were being downloaded from the Juno repository using the maven tycho download. The org.w3c.dom.smil version 1.0.1 was being downloaded which had a missing dependency. While the manual export which was using the running platform target platform(Kerpler) was version 1.0.0. I discovered this by doing a diff on the plugins directory of both files. To get around this I created a tycho target platform file and used this as my target for my build instead of the repository.

I suppose the environment variables are lost in a classic node.js spaw() function, especially HOME (which isn't defined by default in windows, and is necessary for ssh to find its keys) Maybe a spawn like win-spawn would work better: Spawn for node.js but in a way that works regardless of which OS you're using. Use this if you want to use spawn with a JavaScript file. It works by explicitly invoking node on windows. It also shims support for environment variable setting by attempting to parse the command with a regex. Since all modification is wrapped in if (os === 'Windows_NT'), it can be safely used on non-windows systems and will not break anything.

This will reduce the disk usage, but the locking can occur (you will not be able to replace the jar files in the project when the application or IntelliJ IDEA is running). If you don't plan replacing the jars and locking doesn't break your workflow, feel free to set this option to true. Mac/Linux users do not have the locking issue, it's Windows specific.

Dependency analysis works as expected. Code in project C uses classes from project B but it does not directly depend on project B. It compiles only because it transitively depend on B through project A. Changing dependency of project A would break project C. This is what we are trying to avoid This is not good, if the code uses classes from B, it should directly depend on B.

A better approach would be to use a standard UIDatePicker and then configure it with minimumDate, maximumDate, minuteInterval if you need time, datePickerMode of UIDatePickerModeDate if you don't need a time.

Finally the problem was about artifacts naming and apklib not being generated in the apk library project. This is what was wrong: The groupId and artifactId in the library pom were wrong: they must fit the name specified in the error message (I should have read it more carefully). The right values: <groupId>com.google.android.gms</groupId> <artifactId>google-play-services</artifactId> Instead of the ones generated by eclipse when converting the project to maven, which were based on the project name: <groupId>google-play-services_lib</groupId> <artifactId>google-play-services_lib</artifactId> The apklib is not generated with mvn compile, the right instruction for that is mvn package. This way the apklib file gets generated in targe

This is similar to the msysgit issue (in progress) 25, with one only suggestion for now: replace msys-1.0.dll by a new one in "documents and settingsadministratorlocal settingapplication datagithubportablegit_xxxx..." Try first to commit with the msysgit included in GitHub for Windows, and see if the issue persists. Launch a session through C:UsersYourUsernameAppDataLocalGitHubPortableGit_93...git-cmd.bat Or through the icon "Git Shell", which launches: C:UsersYourUsernameAppDataLocalGitHubGitHub.appref-ms --open-shell

You can still have conflicts. If somebody makes a change to the project file and you make a change to the project file and you try to commit it at the same time as (or soon after) the other person, there's a good chance you'll see conflicts. Thankfully, the "project.pbxproj" project file is text which can you can open with your favorite editor (vi or emacs or whatever) and you can resolve the conflicts rather easily.

According to github support, "Currently the 'github' tab only shows repositories that are under your account or under an organization that you belong to." Maybe requested feature will be added later

You should be able to define your DEP as an "optional" dependency, as described in the following question and linked blog post: Best strategy for dealing with optional dependencies http://axelfontaine.com/blog/optional-dependencies.html Essentially just: <dependency> <groupId>org.foo.bar</groupId> <artifactId>DEP</artifactId> <version>1.8.6-09</version> <optiona>true</optional> </dependency> Now your users will have to explicitly add this dependency when using this plugin, otherwise, they will encounter errors. There might also be some way to accomplish the same result but with more informative error messages - using Maven Enforcer Plugi

During tests, the test output directory and main output directory are the first two things on the test classpath, respectively. Then come all of your direct and transitive dependencies of all scopes, following the rules for scopes and transitive dependencies in the link you mentioned and in the order you've declared them in the POM. Find details about each scope in "Dependency Scope" on the Maven site.

The problem is that medicine.o only depends on medicine.cpp, not on medicine.h. So you have to modify your rules to provide that missing dependency. It has absolutely nothing to do with "virtualness". You might also want to add the Makefile itself as a dependency, so if you change it and run make, things get re-built. To clarify, this generic rule: %.o:%.cpp g++ -c -o $@ $< means that any something.o depends on something.cpp only, and should be built with the following command: g++ -c -o something.o something.cpp i.e. $@ is the target name and $< is the first dependency. the format is target : <dependencies> command

Dependency management helps organizing your dependencies in a central place. In your case, that particular artifact is going to be used in different forms in different modules: Plain dependency Share the test code with the module that depends on it (test dependency) - Same for 3

There should be a better way, but if you run the command in debug mode (ie -X so the full command becomes mvn -X dependency:tree) then you'll see the trace printed out before the build dies: ... [DEBUG] org.springmodules:spring-modules-cache:jar:0.9:compile [DEBUG] opensymphony:oscache:jar:2.3:compile [DEBUG] tangosol:tangosol-coherence:jar:3.3-rc1:compile [DEBUG] oro:oro:jar:2.0.8:compile [DEBUG] org.apache.jcs:jcs:jar:1.3:compile [DEBUG] concurrent:concurrent:jar:1.0:compile ... better answers are welcome.

It's used when you display your README.md file on your repository front page, for example. Also, when you add comments it's GFM.

Well I did following steps Google the error Got to SO Links(here, here) which suggested the same thing, that I have to update the Git Config for proxy setting Damn, can not see proxy information from control panel. IT guys must have hidden it. I can not even change the setting to not to use proxy. Found this wonderful tutorial of finding which proxy your are connected to Updated the http.proxy key in git config by following command git config --global http.proxy http[s]://userName:password@proxyaddress:port Error - could not resolve proxy some@proxyaddress:port. It turned out my password had @ symbol in it. Encode @ in your password to %40 because git splits the proxy setting by @ git config --global http.proxy http[s]://userName:password(encoded)@proxyaddress:port B

Disclaimer: I don't know much about Netty, these are just some thoughts from reading your code: I don't see any problem with MyServerInitializer. MyServerInitializer does not have any dependenciesy on MyServerHandler or MyServer. That's fine. It would be worse if the constructor of MyServerInitializer would require MyServerHandler instead of ChannelInboundHandlerAdapter. If possible you should change the constructor parameter of MyServer from MyServerInitializer to ChannelInitializer<SocketChannel>. The problem is that MyServerHandler depends on MyServer while MyServer has a indirect runtime dependency on MyServerHandler. I would try to get rid of the MyServer dependency in MyServerHandler. To do this you can: Move the updateInteger() method from MyServer into another class, le

There are two possible solutions that I found for this issue: The first one is to specify an exact version requirement, or "hard requirement" for a specific version of a dependency, as shown below: <version>[1.5]</version> instead of: <version>1.5</version> The second one is to use the mvn dependency:tree Maven command to see exactly what dependencies are being pulled in, and in what hierarchy. In my case, this solved my problem when I noticed that one dependency was actually pulling in an older version of another dependency, as a sub-dependency. Despite the fact that the sub-dependency was specified on its own elsewhere in the POM, Maven used the older version that was pulled in as a sub-dependency. Sounds confusing I know, but either way, mvn dependency:tre