dependency-management

I compile my programm against javaee-api. But for Junit testing I must use a specific implementation like glassfish's javaee.jar to avoid errors like java.lang.ClassFormatError: Absent Code attribute in method that is not native or abstract in class file javax/persistence/Persistence (see also 1 ). So avoid using methods, that are only available in glassfish implementation, I want to compile my artifact with the general api, but run junit with the implementation jar. But both provide equal named classes and inferfaces, so the class loader gets in trouble. What is the best way to solve this

I am using postgresql 9.2 with play framework 2.1 I downloaded the driver here: http://jdbc.postgresql.org/download.html (JDBC4 Postgresql Driver, Version 9.2-1002) My project/Build.scala file is as follows: import sbt._ import Keys._ import play.Project._ object ApplicationBuild extends Build { val appName = "myApp" val appVersion = "0.1" val appDependencies = Seq( "postgresql" % "postgresql" % "9.2-1002.jdbc4") val main = play.Project(appName, appVersion, appDependencies) } I have placed the jdbc driver in the following locations in the play directory structure: myApp/lib/postgresql-9.2-1002

As you probablu know, new versions of SBT (as 0.11) are designed to maintain a common libraries cache in ~/.ivy2/cache instead of copying the full set of dependencies inside a project directory. But IntelliJ Idea (I use the SBT plugin to generate an Idea project) default seems to be ignoring the common cache and only see the libraries put under the project directory (so, I have to configure SBT to act this legacy way). How to fix this? There are some Ivy plugins in the Idea plugin repository, but I don't know which (if any) of them can solve the problem (note that I don't want it to manage the

I am currently working on a larger scale Maven-based project in IntelliJIdea 12.1.6 Ultimate. I have been working with IntelliJIdea since about 5 months. An included module has dependencies on another module. The dependent module's source was also part of my project until recently. Since I removed the dependent module from my project, I get compile errors whenever I am trying to compile the source without maven. The pom.xml of removed modules in Intellij seem to be placed onto the Settings->Maven->Ignored Files. I cant seem to remove it from there, only check or uncheck it. It's not possible

Dependencies to other python libraries can be declared by pip's requirements.txt . But is it possible to declare a dependency to a pure js library? The library is available from github. The files should be downloaded an made available for django static file handling. Background: setting up new development environments of a custom django application should be easy. How do you handle this in your development environment? dnozay As pointed out by @guettli you can use fanstatic packages . E.g. requirements.txt django js.jquery js.bootstrap js.underscore # ... without django-fanstatic: Then in your

I am using a legacy Spring application and want to migrate to Spring Boot. My intention is to use the spring-boot-starter-data-jpa . For this reason I have added following section in pom.xml (which manages all spring-boot-dependencies ): <parent> <groupId>org.springframework.boot</groupId> <artifactId>spring-boot-starter-parent</artifactId> <version>2.0.3.RELEASE</version> </parent> But this is screwing up certain dependencies which I need to retain for time being. I am currently using Selenium dependencies (version 2.53.0 ; added transitively from another project) but spring-boot is fetching

I have Grails plugin that do some job (precompiles static files) at build time (before war is built). To do its job some jar dependencies are required. So this dependencies are required only at build time. How can I exclude them from final WAR? Add to your BuildConfig.groovy : grails.war.resources = { stagingDir -> delete(file:"${stagingDir}/WEB-INF/lib/whatever.jar") } This is best done using script. I had to employ this when deploying a WAR for a production that required excluding jar files. Create a script file called _Event.groovy under the script directory. Inside the _Event.groovy file,