Re: [m2.2.1] BUILD ERROR -- (attached a test case)
PING! Adrian Herscu wrote: Test case attached in root.7z Adrian. Adrian Herscu wrote: Hi all, I have the following multi-project structure: root +my-maven-plugin +my-component My component requires my Maven plugin in order to build. Hence it declares: build ... plugins plugin groupIdorg.foo/groupId artifactIdmy-maven-plugin/artifactId version1.0-beta-1-SNAPSHOT/version extensionstrue/extensions /plugin ... After deleting the org/foo hive in my local repository I ran mvn -o validate on the root and got: [INFO] NOTE: Maven is executing in offline mode. Any artifacts not already in your local repository will be inaccessible. [INFO] Scanning for projects... [INFO] Reactor build order: [INFO] root [INFO] my-maven-plugin [INFO] my-component [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Plugin could not be found - check that the goal name is correct: System is offline. Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.foo -DartifactId =my-maven-plugin -Dversion=1.0-beta-1-SNAPSHOT -Dpackaging=maven-plugin -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.foo -DartifactId=my-maven-plugin -Dversion=1.0-beta-1-SNAPSHOT -Dpackaging=maven-plugin -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] org.foo:my-maven-plugin:maven-plugin:1.0-beta-1-SNAPSHOT org.foo:my-maven-plugin:maven-plugin:1.0-beta-1-SNAPSHOT [INFO] [INFO] For more information, run Maven with the -e switch [INFO] Shouldn't it build my-maven-plugin before?! Adrian. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[m2] multi-project with plugin dependencies fails to build
Hi all, I am trying to set up a multi-project build in which one module depends on the Maven plugin created by other module. So far, the only way I could build the project is by building the Maven plugin module and then activate the multi-project build. Is there any possibility to define the plugin dependency? Adrian. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Plexus Component 1.1.7 for Maven 2.2.1
Thanks for the quick reply. And that is what I was looking for. Thanks very much. I'm gonna try and add this repository to the default list. Which, by the way, I don't know how. So I'll be googling it. :) Thanks again. wayne wrote: Is this the artifact you're looking for? http://repo2.maven.org/maven2/org/codehaus/plexus/plexus-components/1.1.7/ If so, which mirrors don't have these files? They are dated Dec 2006 so they're quite old. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- View this message in context: http://www.nabble.com/Plexus-Component-1.1.7-for-Maven-2.2.1-tp25830488p25832334.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: [m2] multi-project with plugin dependencies fails to build
afaik, no you can use a previous version of the plugin, but not the same version as is built in your reactor. the reason is that maven needs do determine the build plan before it starts, and your (as yet uncompiled) plugin in the reactor therefore has an unknown effect on the build, resulting in a circular reference at which point maven bombs out Sent from my [rhymes with tryPod] ;-) On 10 Oct 2009, at 07:50, Adrian Herscu adrian.her...@gmail.com wrote: Hi all, I am trying to set up a multi-project build in which one module depends on the Maven plugin created by other module. So far, the only way I could build the project is by building the Maven plugin module and then activate the multi-project build. Is there any possibility to define the plugin dependency? Adrian. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Plexus Component 1.1.7 for Maven 2.2.1
Hello, Here is what happened. I added the given list to the list of repositories and plugin-repositories. However, I'm still facing the original problem that I was facing. When it is about to download the .pom file it hangs there. Doing nothing. So I need to figure out what exactly causes it to stop downloading. Earlier the repo1 subdomain didn't have 1.1.7 version. This repo2 does have it. Still its not being downloaded. Any ideas why? Really appreciate the help. Thanks kenshin1733 wrote: Thanks for the quick reply. And that is what I was looking for. Thanks very much. I'm gonna try and add this repository to the default list. Which, by the way, I don't know how. So I'll be googling it. :) Thanks again. wayne wrote: Is this the artifact you're looking for? http://repo2.maven.org/maven2/org/codehaus/plexus/plexus-components/1.1.7/ If so, which mirrors don't have these files? They are dated Dec 2006 so they're quite old. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- View this message in context: http://www.nabble.com/Plexus-Component-1.1.7-for-Maven-2.2.1-tp25830488p25832441.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: Why doesn't maven look for dependency in the local repo?
Are you referring to this entry: classpathentry kind=src path=/myco-oit-governor-citizen-assistanceUtility-webapp/classpathentry If so, try changing it to reference: /myco-oit-governor-citizen-assistanceUtility-webapp/WEB-INF/classes Unless Maven notices it's a WAR, and transforms the classpath entry to reference the classes directory, it won't work. Maybe there is a different kind attribute? something like kind=war? I tried to find the documentation for classpathentry, but was unsuccessful. Quintin Beukes On Fri, Oct 9, 2009 at 8:50 PM, laredotornado laredotorn...@gmail.com wrote: First off, thanks so much for taking the time to respond. To answer your questions ... In your classpath, is that in fact where the files are put? Can you confirm, from your project root, whether or not you can access those classes using the relative/absolute paths specified in your classpath. No where do I explicitly list a classpath . I thought that the classpath was built from the dependency list. Is this not correct, or is there some exception for war dependencies? Does it return anything? No. there is nothing in the target/classes directory. The class in question is in the war's WEB-INF/classes directory. But if maven ignores wars, then I should resort to something else? Thanks ,- Dave Quintin Beukes-2 wrote: In your classpath, is that in fact where the files are put? Can you confirm, from your project root, whether or not you can access those classes using the relative/absolute paths specified in your classpath. Specifically, when in your project's root, type: ls -ld target/classes/myco/oit/governor/citizen/assistanceUtility/Constants.class Does it return anything? Quintin Beukes On Fri, Oct 9, 2009 at 6:59 PM, laredotornado laredotorn...@gmail.com wrote: Thanks, for now, I hard-coded the version to make this error go away. Problem now is that it doesn't seem the dependency is getting included in my classpath, because I get compilation errors (for classes that are included in the dependency in question) now when I try to run, such as ... maven test:test __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.1 build:start: test:test: java:prepare-filesystem: java:init: java:compile: [echo] No java source files to compile. java:jar-resources: test:prepare-filesystem: test:test-resources: Copying 4 files to /Users/dalvarado/source/assistanceUtility.cvs/test/target/test-classes test:compile: [javac] Compiling 8 source files to /Users/dalvarado/source/assistanceUtility.cvs/test/target/test-classes [javac] /Users/dalvarado/source/assistanceUtility.cvs/test/src/test/myco/oit/governor/citizen/assistanceUtility/test/env/BaseEnvTest.java:16: cannot find symbol [javac] symbol : class Constants [javac] location: package myco.oit.governor.citizen.assistanceUtility [javac] import myco.oit.governor.citizen.assistanceUtility.Constants; I still don't think maven is looking in the right place because when I run the command maven eclipse:generate-classpath, the generated .classpath file is looking for the repo in question, myco-oit-governor-citizen-assistanceUtility-webapp, in another directory besides MAVEN_REPO (contents of .classpath below). Any ideas why? classpath classpathentry kind=con path=org.eclipse.jdt.launching.JRE_CONTAINER/classpathentry classpathentry output=target/test-classes kind=src path=src/test/classpathentry classpathentry kind=var path=MAVEN_REPO/junit/jars/junit-3.8.1.jar/classpathentry classpathentry kind=src path=/myco-oit-governor-citizen-assistanceUtility-webapp/classpathentry classpathentry kind=var path=MAVEN_REPO/org.springframework/jars/spring-1.2.8.jar/classpathentry classpathentry kind=var path=MAVEN_REPO/org.springframework/jars/spring-mock-1.2.8.jar/classpathentry classpathentry kind=var path=MAVEN_REPO/commons-digester/jars/commons-digester-1.7.jar/classpathentry classpathentry kind=var path=MAVEN_REPO/commons-logging/jars/commons-logging-1.0.4.jar/classpathentry classpathentry kind=var path=MAVEN_REPO/commons-lang/jars/commons-lang-2.3.jar/classpathentry classpathentry kind=var path=MAVEN_REPO/net.sourceforge.jwebunit/jars/jwebunit-core-1.4.jar/classpathentry classpathentry kind=var path=MAVEN_REPO/net.sourceforge.jwebunit/jars/htmlunit-1.11.jar/classpathentry classpathentry kind=var path=MAVEN_REPO/net.sourceforge.jwebunit/jars/jwebunit-htmlunit-plugin-1.4.jar/classpathentry classpathentry kind=var path=MAVEN_REPO/org.apache.regexp/jars/regexp-1.3.jar/classpathentry classpathentry kind=var path=MAVEN_REPO/jaxen/jars/jaxen-1.1.jar/classpathentry classpathentry kind=var path=MAVEN_REPO/commons-httpclient/jars/commons-httpclient-3.0.1.jar/classpathentry classpathentry kind=var path=MAVEN_REPO/commons-io/jars/commons-io-1.3.jar/classpathentry classpathentry kind=var
Re: Why doesn't maven look for dependency in the local repo?
Hey, This might help: http://is.gd/4bPYH If you have 2.1 of the WAR maven plugin, then it would work. Otherwise you can just use the SNAPSHOT (all described on the thread). Then, when you build it, the WAR will be installed into your local repo, as well as an additional JAR (which only has the classes). Then you can reference the WAR as a dependency in your POM, by adding the classifierclasses/classifier element into the dependency element. Quintin Beukes On Sat, Oct 10, 2009 at 12:49 PM, Quintin Beukes quin...@skywalk.co.za wrote: Are you referring to this entry: classpathentry kind=src path=/myco-oit-governor-citizen-assistanceUtility-webapp/classpathentry If so, try changing it to reference: /myco-oit-governor-citizen-assistanceUtility-webapp/WEB-INF/classes Unless Maven notices it's a WAR, and transforms the classpath entry to reference the classes directory, it won't work. Maybe there is a different kind attribute? something like kind=war? I tried to find the documentation for classpathentry, but was unsuccessful. Quintin Beukes On Fri, Oct 9, 2009 at 8:50 PM, laredotornado laredotorn...@gmail.com wrote: First off, thanks so much for taking the time to respond. To answer your questions ... In your classpath, is that in fact where the files are put? Can you confirm, from your project root, whether or not you can access those classes using the relative/absolute paths specified in your classpath. No where do I explicitly list a classpath . I thought that the classpath was built from the dependency list. Is this not correct, or is there some exception for war dependencies? Does it return anything? No. there is nothing in the target/classes directory. The class in question is in the war's WEB-INF/classes directory. But if maven ignores wars, then I should resort to something else? Thanks ,- Dave Quintin Beukes-2 wrote: In your classpath, is that in fact where the files are put? Can you confirm, from your project root, whether or not you can access those classes using the relative/absolute paths specified in your classpath. Specifically, when in your project's root, type: ls -ld target/classes/myco/oit/governor/citizen/assistanceUtility/Constants.class Does it return anything? Quintin Beukes On Fri, Oct 9, 2009 at 6:59 PM, laredotornado laredotorn...@gmail.com wrote: Thanks, for now, I hard-coded the version to make this error go away. Problem now is that it doesn't seem the dependency is getting included in my classpath, because I get compilation errors (for classes that are included in the dependency in question) now when I try to run, such as ... maven test:test __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.1 build:start: test:test: java:prepare-filesystem: java:init: java:compile: [echo] No java source files to compile. java:jar-resources: test:prepare-filesystem: test:test-resources: Copying 4 files to /Users/dalvarado/source/assistanceUtility.cvs/test/target/test-classes test:compile: [javac] Compiling 8 source files to /Users/dalvarado/source/assistanceUtility.cvs/test/target/test-classes [javac] /Users/dalvarado/source/assistanceUtility.cvs/test/src/test/myco/oit/governor/citizen/assistanceUtility/test/env/BaseEnvTest.java:16: cannot find symbol [javac] symbol : class Constants [javac] location: package myco.oit.governor.citizen.assistanceUtility [javac] import myco.oit.governor.citizen.assistanceUtility.Constants; I still don't think maven is looking in the right place because when I run the command maven eclipse:generate-classpath, the generated .classpath file is looking for the repo in question, myco-oit-governor-citizen-assistanceUtility-webapp, in another directory besides MAVEN_REPO (contents of .classpath below). Any ideas why? classpath classpathentry kind=con path=org.eclipse.jdt.launching.JRE_CONTAINER/classpathentry classpathentry output=target/test-classes kind=src path=src/test/classpathentry classpathentry kind=var path=MAVEN_REPO/junit/jars/junit-3.8.1.jar/classpathentry classpathentry kind=src path=/myco-oit-governor-citizen-assistanceUtility-webapp/classpathentry classpathentry kind=var path=MAVEN_REPO/org.springframework/jars/spring-1.2.8.jar/classpathentry classpathentry kind=var path=MAVEN_REPO/org.springframework/jars/spring-mock-1.2.8.jar/classpathentry classpathentry kind=var path=MAVEN_REPO/commons-digester/jars/commons-digester-1.7.jar/classpathentry classpathentry kind=var path=MAVEN_REPO/commons-logging/jars/commons-logging-1.0.4.jar/classpathentry classpathentry kind=var path=MAVEN_REPO/commons-lang/jars/commons-lang-2.3.jar/classpathentry classpathentry kind=var path=MAVEN_REPO/net.sourceforge.jwebunit/jars/jwebunit-core-1.4.jar/classpathentry classpathentry kind=var
Re: Plexus Component 1.1.7 for Maven 2.2.1
repo1 has it as well ( http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-components/). Not sure what the difference is between repo1 and repo2. What groupId and artifactId have you defined in your dependency? /A On Sat, Oct 10, 2009 at 11:23, kenshin1733 kenshin1...@gmail.com wrote: Hello, Here is what happened. I added the given list to the list of repositories and plugin-repositories. However, I'm still facing the original problem that I was facing. When it is about to download the .pom file it hangs there. Doing nothing. So I need to figure out what exactly causes it to stop downloading. Earlier the repo1 subdomain didn't have 1.1.7 version. This repo2 does have it. Still its not being downloaded. Any ideas why? Really appreciate the help. Thanks kenshin1733 wrote: Thanks for the quick reply. And that is what I was looking for. Thanks very much. I'm gonna try and add this repository to the default list. Which, by the way, I don't know how. So I'll be googling it. :) Thanks again. wayne wrote: Is this the artifact you're looking for? http://repo2.maven.org/maven2/org/codehaus/plexus/plexus-components/1.1.7/ If so, which mirrors don't have these files? They are dated Dec 2006 so they're quite old. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- View this message in context: http://www.nabble.com/Plexus-Component-1.1.7-for-Maven-2.2.1-tp25830488p25832441.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: Plexus Component 1.1.7 for Maven 2.2.1
A quick check tells me that repo1 and repo2 has the same ip address, so most likely they are the same. But to be honest, I haven't heard of the repo2 address before. /A On Sat, Oct 10, 2009 at 13:03, Anders Hammar and...@hammar.net wrote: repo1 has it as well ( http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-components/). Not sure what the difference is between repo1 and repo2. What groupId and artifactId have you defined in your dependency? /A On Sat, Oct 10, 2009 at 11:23, kenshin1733 kenshin1...@gmail.com wrote: Hello, Here is what happened. I added the given list to the list of repositories and plugin-repositories. However, I'm still facing the original problem that I was facing. When it is about to download the .pom file it hangs there. Doing nothing. So I need to figure out what exactly causes it to stop downloading. Earlier the repo1 subdomain didn't have 1.1.7 version. This repo2 does have it. Still its not being downloaded. Any ideas why? Really appreciate the help. Thanks kenshin1733 wrote: Thanks for the quick reply. And that is what I was looking for. Thanks very much. I'm gonna try and add this repository to the default list. Which, by the way, I don't know how. So I'll be googling it. :) Thanks again. wayne wrote: Is this the artifact you're looking for? http://repo2.maven.org/maven2/org/codehaus/plexus/plexus-components/1.1.7/ If so, which mirrors don't have these files? They are dated Dec 2006 so they're quite old. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- View this message in context: http://www.nabble.com/Plexus-Component-1.1.7-for-Maven-2.2.1-tp25830488p25832441.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: [maven-dependency-plugin] Issues with multiple invocations of dependency:upack goal (readonly local parameter)
This is likely because there is some conflict from calling the plugin
from your plugin. You can have multiple invocations of the dependency
plugin from the pom without issues. Calling and extending plugins in
M2 is essentially a grey area, looks like you found the edge to black
;-)
On Fri, Oct 9, 2009 at 4:55 AM, kkarad kka...@gmail.com wrote:
Hi all,
I 've got a pom type parent project which includes 4 modules (child
projects)
Each module produces a jar file and during the deployment phase the
maven-dependency-plugin unpacks it to a specific location (the
dependency:unpack goal is called indirectly from my own custom plugin).
At the 2nd dependency:unpack call (module2) build fails with error message:
Error configuring: org.apache.maven.plugins:maven-dependency-plugin. Reason:
ERROR: Cannot override read-only parameter: local in goal: dependency:unpack
My understanding is that the read-only parameter local (which I dont
use/set it) is initialised by the 1st dependency:unpack call (in module1).
Therefore the 2nd dependency:unpack invocation fails because the local
parameter is already set.
Do you know if this is a bug or a problem on my side? How can I fix it?
The mave-dependency-plugin version is 2.1
The flow of the build is as follows:
clean deploy
[module1:clean]
[module1:deploy]
[module1:myplugin:mygoal] -- calls indirectly dependency:unpack using
@execute lifecycle=my-lifecycle phase=deploy
[module2:clean]
[module2:deploy]
[module2:dependency:unpack] -- -- calls indirectly dependency:unpack using
@execute lifecycle=my-lifecycle phase=deploy but build fails
...
The custom lifecycle xml is :
lifecycles
lifecycle
idmy-lifecycle/id
phases
phase
iddeploy/id
executions
execution
goals
goalcom.mycomp.myapp:maven-my-plugin:get/goal
/goals
configuration
...
/configuration
/execution
execution
goals
goalorg.apache.maven.plugins:maven-dependency-plugin:unpack/goal
/goals
configuration
artifactItems
artifactItem
groupId${deployedGroupId}/groupId
artifactId${deployedArtifactId}/artifactId
version${deployedVersion}/version
classifier${deployedClassifier}/classifier
type${deployedType}/type
overWrite${deploymentOverwrite}/overWrite
outputDirectory${deploymentFolder}/outputDirectory
/artifactItem
/artifactItems
/configuration
/execution
/executions
/phase
/phases
/lifecycle
/lifecycles
--
View this message in context:
http://www.nabble.com/-maven-dependency-plugin--Issues-with-multiple-invocations-of-dependency%3Aupack-goal-%28readonly-%22local%22-parameter%29-tp25817744p25817744.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
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Global dependency version property
Hey, We have certain dependencies like OpenEJB, Geronimo and Hibernate being used throughout our project. When we upgrade the version (especially with minor revisions) it's merely a process of changing all the version elements to the new version. Though, being many projects this is a tedious process, and you sometimes miss one/two. Isn't there a way to define some properties in the parent POM and have them propagate to the children, to be referenced from there? Or to maybe declare some dependency groups in the parent POM, and then reference them by group in the child projects? Quintin Beukes - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Global dependency version property
You really need to read the book. http://www.sonatype.com/books/maven-book/reference/optimizing-sect-dependencies.html On 2009-10-10, at 9:29 AM, Quintin Beukes wrote: Hey, We have certain dependencies like OpenEJB, Geronimo and Hibernate being used throughout our project. When we upgrade the version (especially with minor revisions) it's merely a process of changing all the version elements to the new version. Though, being many projects this is a tedious process, and you sometimes miss one/two. Isn't there a way to define some properties in the parent POM and have them propagate to the children, to be referenced from there? Or to maybe declare some dependency groups in the parent POM, and then reference them by group in the child projects? Quintin Beukes - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl -- - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Global dependency version property
Thanks, that looks good. Re. the dependencyManagement element. When I include a set of dependencies in my parent POM, they won't be included in the child POMs unless I excplicitely list them there? Meaning it's effect is only when the dependency is listed in a child without a version? Quintin Beukes On Sat, Oct 10, 2009 at 7:44 PM, Jason van Zyl ja...@sonatype.com wrote: You really need to read the book. http://www.sonatype.com/books/maven-book/reference/optimizing-sect-dependencies.html On 2009-10-10, at 9:29 AM, Quintin Beukes wrote: Hey, We have certain dependencies like OpenEJB, Geronimo and Hibernate being used throughout our project. When we upgrade the version (especially with minor revisions) it's merely a process of changing all the version elements to the new version. Though, being many projects this is a tedious process, and you sometimes miss one/two. Isn't there a way to define some properties in the parent POM and have them propagate to the children, to be referenced from there? Or to maybe declare some dependency groups in the parent POM, and then reference them by group in the child projects? Quintin Beukes - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl -- - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Global dependency version property
Yes. You use the dependencyManagement to specify stuff like version and scope. Each project where you have the dependency you still need to specify it. However, you just state groupId and artifactId. /Anders On Sat, Oct 10, 2009 at 20:02, Quintin Beukes quin...@skywalk.co.za wrote: Thanks, that looks good. Re. the dependencyManagement element. When I include a set of dependencies in my parent POM, they won't be included in the child POMs unless I excplicitely list them there? Meaning it's effect is only when the dependency is listed in a child without a version? Quintin Beukes On Sat, Oct 10, 2009 at 7:44 PM, Jason van Zyl ja...@sonatype.com wrote: You really need to read the book. http://www.sonatype.com/books/maven-book/reference/optimizing-sect-dependencies.html On 2009-10-10, at 9:29 AM, Quintin Beukes wrote: Hey, We have certain dependencies like OpenEJB, Geronimo and Hibernate being used throughout our project. When we upgrade the version (especially with minor revisions) it's merely a process of changing all the version elements to the new version. Though, being many projects this is a tedious process, and you sometimes miss one/two. Isn't there a way to define some properties in the parent POM and have them propagate to the children, to be referenced from there? Or to maybe declare some dependency groups in the parent POM, and then reference them by group in the child projects? Quintin Beukes - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl -- - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Global dependency version property
And you override where necessary? Quintin Beukes On Sat, Oct 10, 2009 at 8:36 PM, Anders Hammar and...@hammar.net wrote: Yes. You use the dependencyManagement to specify stuff like version and scope. Each project where you have the dependency you still need to specify it. However, you just state groupId and artifactId. /Anders On Sat, Oct 10, 2009 at 20:02, Quintin Beukes quin...@skywalk.co.za wrote: Thanks, that looks good. Re. the dependencyManagement element. When I include a set of dependencies in my parent POM, they won't be included in the child POMs unless I excplicitely list them there? Meaning it's effect is only when the dependency is listed in a child without a version? Quintin Beukes On Sat, Oct 10, 2009 at 7:44 PM, Jason van Zyl ja...@sonatype.com wrote: You really need to read the book. http://www.sonatype.com/books/maven-book/reference/optimizing-sect-dependencies.html On 2009-10-10, at 9:29 AM, Quintin Beukes wrote: Hey, We have certain dependencies like OpenEJB, Geronimo and Hibernate being used throughout our project. When we upgrade the version (especially with minor revisions) it's merely a process of changing all the version elements to the new version. Though, being many projects this is a tedious process, and you sometimes miss one/two. Isn't there a way to define some properties in the parent POM and have them propagate to the children, to be referenced from there? Or to maybe declare some dependency groups in the parent POM, and then reference them by group in the child projects? Quintin Beukes - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl -- - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
JavaDoc Plugin: Custom frameset?
Is it possible to use this plugin to provide a custom frameset page? I see several companies publish API with page-wide logos at the top of the frameset, or additional frames. Paul - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
