Maven is using SNAPSHOT versions of plugins
Hi all, trying to create a project using the archetype-plugin fails because maven tries to use a SNAPSHOT version of the plugin: [INFO] Unable to find resource 'org.apache.maven.plugins:maven-archetype-plugin:maven-plugin:2.3-SNAPSHOT' in repository central (http://central) [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] A required plugin was not found: Plugin could not be found - check that the goal name is correct: Unable to download the artifact from any repository Same happens when trying to perform the maven-eclipse-plugin. So my question is: why does maven try to use SNAPSHOT versions which do not exist? Can the cause of the problem be in my local configuration? Regards, Abid -- NEU: FreePhone - 0ct/min Handyspartarif mit Geld-zurück-Garantie! Jetzt informieren: http://www.gmx.net/de/go/freephone - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Problem resolving property
Hi all,
I have a problem that maven doesn't resolve a property.
In a project A we have the following dependency:
dependency
groupIdcomponents/groupId
artifactIdlibrary-bundle/artifactId
version3.12/version
typepom/type
/dependency
In dependent project library-bundle (Version 3.12) we have the following
property declared:
profile
idutilization/id
activation
activeByDefaulttrue/activeByDefault
/activation
dependency
groupIdmy.jdbc.driver/groupId
artifactIdmydriver/artifactId
version${oracle.jdbc.driver.version}/version
/dependency
/profile
Project A and project library-bundle have a common parent POM in which the
variable ${oracle.jdbc.driver.version} is declared:
profile
idcontext_x/id
activation
property
nameenv.PROJECT/name
valuecontext_x/value
/property
/activation
properties
oracle.jdbc.driver.version11.1.0.7.0/oracle.jdbc.driver.version
/properties
/profile
When trying to build project A under profile 'context_x' (with the correct
environment variable PROJECT set to 'context_x') it fails:
[INFO] Failed to resolve artifact.
Missing:
--
1) component.oracle.jdbc.driver:ojdbc6:jar:${oracle.jdbc.driver.version}
The missing artifact is definetly existing with the specified in the local
repository.
Anybody has an idea why maven can't resolve the dependency?
Regards,
Abid
--
Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir
belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Parallel development on multiple dependent projects
Hi all, I wonder if maven can handle the scenario when multiple projects (which are dependent on each other) are developed concurrently. E.g. we have a project A which is dependent on projects B and C. All projects are at development stage. When developing on A one wants to use the latest features in dependent projects B and C at current development stage. As one has to declare a certain version number in A's pom.xml there is no way to tell maven always to use the development-version (or trunk-version) of B and C which haven't been released so far. So, is there a way to declare dependencies on modules which haven't been released so far? Regards, Abid -- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Usage of Enforcer Plugin 1.1-SNAPSHOT
Hi, we have problems with maven using a wrong version of enforcer plugin. In the project's pom the enforcer plugin is specified like this: plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-enforcer-plugin/artifactId executions execution idenforce-versions/id goals goalenforce/goal /goals configuration !-- ... -- /configuration /execution /executions /plugin /plugins As you can see, no version number of the plugin is declared nor is it in any parent pom of this project. Building the project fails as maven tries to use the 1.1-SNAPSHOT version of enforcer plugin which doesn't exisit in our repository. Most recent version in maven central is currently 1.0.1. I wonder why maven uses a SNAPSHOT version of the plugin? And furthermore, how does maven determine the version number of a plugin/dependency when no version number is specified? Regards, Abid -- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Usage of Enforcer Plugin 1.1-SNAPSHOT
Thanks. We fixed the problem by locking down the version number of enforcer plugin. We're using maven 2.2.1. But still I wonder about the behaviour when no version number has been specified... How are the version numbers determined by maven? How can it happen that maven uses a snapshot version as it is a maven convention that snapshot projects are at a development stage? Regards, Abid On Thu, Nov 10, 2011 at 8:42 PM, Guo Du mrdu...@duguo.org wrote: I wonder why maven uses a SNAPSHOT version of the plugin? Which maven version you use? A build log will helps to understand your problem. And best practice is to lock down the version numbers, which ironically enforcer will tell you to do. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
release plugin flat multi module
Hi, I know the issue of using the release plugin in a multi module project with a flat directory structure has been discussed many times. I'm using maven 2.2.1 and I couldn't determine if it has been solved or not. Trying to prepare a release fails with svn: 'D:\eclipse-workspaces\test' is not a working copy When using the option -DcommitByProject it succeeds but only for the parent project a tag is created in scm. So, does the release plugin finally work using maven 2.2.1 with a flat structure? Regards, Abid -- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: release transitive SNAPSHOT dependency
It's simply to save time. Let's say you have a project containing of several components. Instead of releasing every component separate, you perform the release only for the main component and in a transitive way maven performs automatically releases of all dependent SNAPSHOT components. Naturally this process includes compiling and running tests. But maybe it is better to use a multi module project (in which SNAPSHOT dependencies between submodules are resolved by maven) for this kind of project structure. Regards, Abid Original-Nachricht Datum: Fri, 23 Sep 2011 12:23:21 -0400 Von: Ron Wheeler rwhee...@artifact-software.com An: Maven Users List users@maven.apache.org Betreff: Re: release transitive SNAPSHOT dependency I hope not! Sounds like a really bad thing to do. How does maven know that B is release quality? Ron On 23/09/2011 11:58 AM, Abid Hussain wrote: Hello, e.g. there is a project A (e.g. 1.0-SNAPSHOT) which has a dependency to another non-released project B (e.g. 2.3-SNAPSHOT). AFAIK performing a release which has SNAPSHOT versions is not possible. Is there a way to tell maven that when a release of project A should be performed to automatically - perform a release of B (e.g. 2.3) - update the dependency from A to B (so that A is dependent to B 2.3) - and then actually perform the release of A (resulting in A 1.0)? Regards, Abid -- Ron Wheeler President Artifact Software Inc email: rwhee...@artifact-software.com skype: ronaldmwheeler phone: 866-970-2435, ext 102 -- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Incremet SNAPSHOT dependency when release
Hello, my question is about how SNAPSHOT dependencies between submodules in multi module projects can be automatically incremented when performing a release. Let's give an example: I've a multi module project P with two sub modules A and B. Current version is 1.0-SNAPSHOT. The version number is only declared in P. A and B inherit P's version. A is dependent on B 1.0-SNAPSHOT: A - B (1.0-SNAPSHOT). Now I prepare a release of P by calling mvn release:prepare in the root directory of P. The release preparation is done and the dependency from A to B is changed to 1.0 in the tagged version. On my local machine the version of P is incremented to 1.1-SNAPSHOT, same is done with the parent version declaration in A and B (incremented to 1.1-SNAPSHOT). But, on my local machine the dependency from A to B is still of version 1.0-SNAPSHOT. Is there a way to configure that also the dependencies between modules in a multi-module project is to be incremented after a release? Regards, Abid -- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
release transitive SNAPSHOT dependency
Hello, e.g. there is a project A (e.g. 1.0-SNAPSHOT) which has a dependency to another non-released project B (e.g. 2.3-SNAPSHOT). AFAIK performing a release which has SNAPSHOT versions is not possible. Is there a way to tell maven that when a release of project A should be performed to automatically - perform a release of B (e.g. 2.3) - update the dependency from A to B (so that A is dependent to B 2.3) - and then actually perform the release of A (resulting in A 1.0)? Regards, Abid -- NEU: FreePhone - 0ct/min Handyspartarif mit Geld-zurück-Garantie! Jetzt informieren: http://www.gmx.net/de/go/freephone - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
