Local/proxy dependency resolution when the artifact's metadata is the same
In our team we are using a Proxy repository where the artifacts are uploaded on mvn deploy. Let's consider the following artifact : groupIdcom.acme/groupId artifactIdfoo/artifactId version1.0/version I have it in my local repository, and it's also on the proxy repo. My colleague decides to do a very minor change to the corresponding foo Maven project, and redeploys this artifact to the proxy repository, but without changing the artifact's version. Does this mean that as long as this artifact is in my local repo, I will never be using the latest version (the one on the proxy) when resolving dependencies? -- View this message in context: http://www.nabble.com/Local-proxy-dependency-resolution-when-the-artifact%27s-metadata-is-the-same-tp24216134p24216134.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Backslash colon problem with ${basedir} using maven-plugin-tools-ant
Hasn't anyone faced this problem? I really need some help there.. -- View this message in context: http://www.nabble.com/Backslash-colon-problem-with-%24%7Bbasedir%7D-using-maven-plugin-tools-ant-tp24111308p24142465.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Backslash colon problem with ${basedir} using maven-plugin-tools-ant
=== Problem solved ===
The ${basedir} variable was replaced because in the project's POM I had
specified filteringtrue/filtering for the directory enclosing the Ant
script file.
I still think there is a bug in the Ant plugin (adding the backslash before
the colon).
--
View this message in context:
http://www.nabble.com/Backslash-colon-problem-with-%24%7Bbasedir%7D-using-maven-plugin-tools-ant-tp24111308p24149242.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Backslash colon problem with ${basedir} using maven-plugin-tools-ant
I'm calling an Ant target using Java. I'm using the:
groupIdorg.apache.maven.plugin-tools/groupId
artifactIdmaven-plugin-tools-ant/artifactId
version2.4/version
plugin.
I have the following build_foo.xml Ant script in my Maven source dir:
project name=build_foo default=info basedir=.
target name=info
mkdir dir=${basedir}/foo /
/target
/project
Upon calling mvn clean package, this file is copied in the
target/classes directory, with the following content:
project name=build_foo default=info basedir=.
target name=info
mkdir dir=C\:\\Program
Files\\eclipse-3.4\\workspace\\maven-agp-plugin/foo /
/target
/project
Then, doing ant -f target/classes/build_foo.xml fails with this error:
C:\Program
Files\eclipse-3.4\workspace\maven-agp-plugin\target\classes\build_foo.xml:4:
Directory C:\Program
Files\eclipse-3.4\workspace\maven-agp-plugin\target\classes\C\:\Program
Files\eclipse-3.4\workspace\maven-agp-plugin\foo creation was not successful
for an unknown reason
Basically, it fails because of the backslash before the colon (C\:).
Is this a bug in the Ant Maven plugin?
--
View this message in context:
http://www.nabble.com/Backslash-colon-problem-with-%24%7Bbasedir%7D-using-maven-plugin-tools-ant-tp24111308p24111308.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Backslash colon problem with ${basedir} using maven-plugin-tools-ant
Why does mvn package transform ${basedir} to a hard-coded directory
anyway? I don't see any particular reason for doing this...
--
View this message in context:
http://www.nabble.com/Backslash-colon-problem-with-%24%7Bbasedir%7D-using-maven-plugin-tools-ant-tp24111308p24111587.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: automatically calling install target for projects which are not in the repository
One solution is simple: create a Maven meta-project: project modelVersion4.0.0/modelVersion groupIdcom.agipi/groupId artifactIdmetaproject-extranet/artifactId packagingpom/packaging version1.0.0/version modules module../project1/module module../project2/module [...] module../project10/module /modules /project - Calling mvn clean on this meta-project cleans all modules - Calling mvn package on this meta-project calls mvn package on all specified modules, and in the correct dependency order, regardless of the order in which the modules are declared in the meta-project/pom.xml (which is very nice) -- View this message in context: http://www.nabble.com/automatically-calling-%22install%22-target-for-projects-which-are-not-in-the-repository-tp23403861p23426642.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven2 - Where to put script files?
I guess I'll have to write my own plugin.. Nick Stolwijk-4 wrote: To put the files in src/main/scripts is the convention. It is then up to the plugins to do something with them. Which plugin did you expect to take your files? Hth, Nick Stolwijk ~Java Developer~ Iprofs BV. Claus Sluterweg 125 2012 WS Haarlem www.iprofs.nl -- View this message in context: http://www.nabble.com/Maven2---Where-to-put-script-files--tp5594755p23403655.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
automatically calling install target for projects which are not in the repository
Hi, I have an application composed of 10 Eclipse projects, which depend on each other. One of them is a webapp and it depends on several Eclipse projects, and some of these Eclipse projects depend on others, so the dependency tree is quite complex. In good-old Eclipse build, I don't have to care about that dependencies tree: as long as the necessary projects are specified in the Required projects on the build path section, my webapp will build successfully in 1 user task. In Maven even though the dependencies are defined in the POM, if the required projects don't exist in the local repository, calling mvn clean install for my webapp will fail. As a result, I have to mvn install every single Maven project on the build path first. Is there a way of calling mvn install on projects if they don't exist in the local repository? -- View this message in context: http://www.nabble.com/automatically-calling-%22install%22-target-for-projects-which-are-not-in-the-repository-tp23403861p23403861.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven2 - Where to put script files?
I've put a file in this directory, ran mvn clean install, but the script file isn't copied anywhere in target. What am I supposed to do after adding a file to src/main/scripts? Nick Stolwijk-4 wrote: If you take a look at the superpom [1] you'll see there is a default script directory: scriptSourceDirectorysrc/main/scripts/scriptSourceDirectory So I would say convention over configuration and use that one. (If you'll write a maven plugin to handle the scripts, use the scriptSourceDirectory instead of making your own variable setting. Hth, [1] http://maven.apache.org/guides/introduction/introduction-to-the-pom.html Nick Stolwijk ~Java Developer~ Iprofs BV. Claus Sluterweg 125 2012 WS Haarlem www.iprofs.nl -- View this message in context: http://www.nabble.com/Maven2---Where-to-put-script-files--tp5594755p23389966.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
