I'm searching for a longer time, but without any solution.
My problem:
I configured my Grails project (1.2.4) with Maven and my own Nexus Repo. That seems to be working well. But can I also put the Grails plugins, which I am using, also to the Nexus Repo?
At the momement the plugin dependencies are resolved over the Grails Plugin repository.
Any ideas?
with regards
Fabian
Grails 1.3 has got support for dependency managing plugins. Details are here:
http://blog.springsource.com/2010/05/18/managing-plugins-with-grails-1-3/
The article discusses some of the problems that existing in previous versions of Grails.
Understand this thread is old, but posting a link in which the author explains the configuration of grails to fetch plugins and dependencies from Nexus:
Nexus Configuration for Grails plugins and other dependencies
This worked great for grails 2.2.2.
Related
I am trying to deploying CF application available as the part of OpenSap course from this GitHub URL https://github.com/raepple/cfsectest.git . When I do maven clean install, I got the error as in the screenshot.It tells that it is unable to download some maven dependencies.Any solution to this issue?
There is a partial answer as these Maven dependencies are not available no longer. Please refer this blog for an alternative fix.
Some of our new projects have been migrated to maven3 and some of the older projects are still using the maven2 compliant pom.xml files.
Can maven3 runtime execute maven2 compatible pom.xml files also?
maven 3 is mostly compatible with maven 2 configuration. But there is still some incompatibilities.
For a full list you should check here there is also sometime problems with plugins (as Torsten suggested).
Resources:
Maven 3.x Plugin Compatibility Matrix
On the same topic:
switching to maven3
Typically yes, but it may depend on the plugin version you are using.
Please note that e.g. the maven site plugin is different for maven 2 and maven 3 or some options of the maven enforcer plugin are no longer valid for maven 3. There might be others.
Yes, it is.
At first you may be alarmed by the fact that it reports a bunch of warnings and sometimes refuses to build before you take care of the problems, but this is actually better for you as (if you run into this) it simply tells you what was wrong with your project so far.
Other than that, the site plugin is completely re-written and you need to use the version for Maven 3. (Check here)
I am upgrading an system I have been developing for some time now to JBoss AS 6 (6.0.0-Final). Everything works well with JBoss but I can't find a maven repository. I read the information on their web-site which directs me to: https://repository.jboss.org/nexus/content/repositories/releases
However it only contains Jboss 4.2.3.GA?!
I believe that my question is incorrect. This is what I believe is the correct answer:
Maven2 always uses http://repo1.maven.org/maven2/ as a fallback when packages are not found in the repositories supplied. So one should supply the jboss repository, https://repository.jboss.org/nexus/content/groups/public-jboss/, but it will only contain jboss specific packages. For everything else (javaee packages and so on) the maven2 fallback reposity should be used.
I didn't understand that a Maven2 repository was always used as a fallback. So I got confused when I couldn't find the packages I needed in the Jboss repository.
The groupId has changed to org.jboss.as
Here are some 7.x Alpha releases
And here are some 6.x release links through nexus (couldn't find a browsable version of these)
Is there a way to use the ivy cache grails dependency DSL creates within an IDE like eclipse or netbeans? Or must I manually add all dependencies to the IDE lib folder?
I've looked into plugins like ivybeans and ivyde, but they seem to require ivy.xml and ivysettings.xml files, which grails does not produce.
The Grails tooling provided by the SpringSource Tool Suite plugin for Eclipse has the functionality you desire. It reads BuildConfig.groovy and modifies the project classpath accordingly.
I just attached the following to the Jira bug.
In snooping around the STS distribution, I found the following code in
C:\springsource\sts-2.3.2.RELEASE\configuration\org.eclipse.osgi\bundles\898\1.cp\src\com\springsource\sts\grails\core\model\GrailsBuildConfig.java
// make sure that we use the Ivy dependency resolution strategy for Grails 1.2
// TODO CD make version number detection more flexible
if (settings.getGrailsVersion().startsWith("1.2")) {
jarFiles.addAll(settings.getTestDependencies());
jarFiles.addAll(settings.getProvidedDependencies());
Based on this find, I tried downgrading my project from Grails 1.3.2 to Grails 1.2 and ran "refresh dependencies". Sure enough, the dependencies were correctly loaded from Ivy.
Looks like someone needs to do the TODO. I can take a stab at it once I figure out how to check out the source code...
IntelliJ syncs dependencies between Grails (form application.properties and BuildConfig.groovy) and the IDE very nicely.
I am working on converting websphere portal project to maven framework for CI build. I am wondering if there is a way to reference websphere jars other than via dependencies in pom.xml and loading them all to maven repository? I cannot imagine loading them ALL to the repository...
Please advice! Thanks!
When using Maven, it is advisable that all dependent jars are installed in the repository. Even Websphere ones.
Ideally a corporate repository will come in handy here, so that you keep a separate repository for all the Websphere jars accessible to all the users in your project. See http://maven.apache.org/repository-management.html for more.
If this is not an option, then use the local file repository explained on a previous questions - here.
You'll still need to add each dependency in POM.
Also read http://sdudzin.blogspot.com/2007/09/maven-2-and-websphere-automated-build.html
if you have a lot of projects that require this, you can also create a parent pom that would have all the dependencies so your project/module/portlet poms are cleaner.