RE: [m2] How to avoid running CPD when using maven-pmd-plugin?
maven-pmd-plugin pmd > -Original Message- > From: Hilco Wijbenga [mailto:[EMAIL PROTECTED] > Sent: Saturday, July 01, 2006 4:00 PM > To: Maven Users List > Subject: [m2] How to avoid running CPD when using maven-pmd-plugin? > > Hi all, > > I'm using the maven-pmd-plugin to check my code. I am now finding, > however, that CPD (that's 'CPD' not 'PMD') is not as useful as I had > hoped so I would like to exclude it. > > I tried adding > > > > > org.apache.maven.plugins > maven-pmd-plugin > > > verify (I also tried test) > > pmd > > > > ... > > > > > I had hoped this would mean to *only* run PMD but CPD still runs. > > I used help:describe to see if there were any properties I could set > to not run CPD but couldn't find anything. The source of > maven-pmd-plugin also didn't reveal anything. > > Someone please enlighten me, how do I do this? > > Cheers, > Hilco > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Newbie question
There is no other way. You will need to deploy them to your internal remove repository. If you already have internal repository setup ( do you have one? ) this is one one time setup. Just curious, you have 50 non public jars? If you are not willing to do that, i would suggest to stay with your current build. I got burned try to port a legacy intact to maven with file structure intact before. -D On 7/1/06, Punit Rathore <[EMAIL PROTECTED]> wrote: This is another one of the "classpath question". Here is my problem. In my project I have to include a set of jar files that have been produced by another project(s) and have traditionally been deployed in nfs mounted path like /common/libs/prj1/lib. Now this path contains more than 50 jars that I need to include. After much googling and reading up on this mailing list, i found one potential solution was to dependency with system scope. However this means that I will have to define the dependency of each of the more than 50 jars. I find that very impractical. Another was to import it in to repository using mvn install:install-file. This approach had the same problem ( importing each of 50 jars). Is there another way of easily doing this ? Thanks, Punit
Re: Emacs Support/Compiler Plugin
"Chris Hilton" <[EMAIL PROTECTED]> writes: > Wasn't your original problem with grabbing compilation errors from the > output? You should probably take a look at the following message: > > http://www.nabble.com/forum/ViewPost.jtp?post=4125504&framed=y > > It should be as easy as modifying your emacs setup. And right you are. Thanks for the lead. I've included my adaptation (of Philip Lord's solution) which does not require JDE hence may be of some value to other Emacs/Maven hackers out there: ;;; Support for Maven 2 for GNU Emacs (require 'compile) ;; Add the following to support Emacs' compile mode: (add-to-list 'compilation-error-regexp-alist-alist '(mvn "^\\(.*\\):\\[\\([0-9]*\\),\\([0-9]*\\)\\]" 1 2 3)) (add-to-list 'compilation-error-regexp-alist 'mvn) (provide 'maven-support) Enjoy, -pmr - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Newbie question
This is another one of the "classpath question". Here is my problem. In my project I have to include a set of jar files that have been produced by another project(s) and have traditionally been deployed in nfs mounted path like /common/libs/prj1/lib. Now this path contains more than 50 jars that I need to include. After much googling and reading up on this mailing list, i found one potential solution was to dependency with system scope. However this means that I will have to define the dependency of each of the more than 50 jars. I find that very impractical. Another was to import it in to repository using mvn install:install-file. This approach had the same problem ( importing each of 50 jars). Is there another way of easily doing this ? Thanks, Punit
Re: List of Maven Archetypes?
On 7/1/06, siegfried <[EMAIL PROTECTED]> wrote: Now what? I tried "mvn war" and that did not work! How can I automate the process of creating a war file and copy it to the deployment directory of tomcat or jboss or jetty? It would usually be 'mvn package' or 'mvn install'. To deploy it, I would use Cargo, which has a Maven 2 plugin. http://cargo.codehaus.org -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: List of Maven Archetypes?
On 7/1/06, siegfried <[EMAIL PROTECTED]> wrote: >IMO the projects themselves should provide the archetypes. What projects? Is there a list of starter projects I can start from? Somewhere on my very long list of things to do is to start a wiki page listing the known available archetypes. It can go under this space: http://docs.codehaus.org/display/MAVENUSER/Home Right now we have a half-dozen or so between Struts, Shale, and MyFaces. I'm not completely happy with any of mine, I'm still struggling with how best to create multi-module archetypes. -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Does Maven2 have support for Maven1 POMS (specifically Id vs ArtifactId
Maven 2 have support for Maven 1 Repositories (use legacy layout when specifying the m1 repo) But a Maven 2 repository is expected to have only Maven 2 poms. So an m2 repo with an m1 pom is not valid and maven will report this but however, will not fail the build. To report such occurrences, please see: http://maven.apache.org/guides/mini/guide-maven-evangelism.html Colin Sampaleanu wrote: Inside the Maven2 repo, this pom for SLF4J 1.0 appears to be in Maven2 format: http://www.ibiblio.org/maven2/org/slf4j/slf4j-log4j12/1.0/slf4j-log4j12-1.0.pom but this one for SLF4J 1.0.1 appears to be in Maven1 format: http://www.ibiblio.org/maven2/org/slf4j/slf4j-log4j12/1.0.1/slf4j-log4j12-1.0.1.pom I'm trying to figure out if Maven2 is still capable of using the Maven1 format (I presume not, it's not legal according to the XSD), or if somebody messed up and just checked in a Maven1 format POM in the Maven 2 repo. Colin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] How to know which artifact ships a given resource?
Repository indexing is a known feature and there are apps (i.e. MRM) and websites (www.mavenregistry.com) that provide them. Alessio Pace wrote: Hi, does anybody ever had the need, given a resource name (i.e.: a class name), to know which maven2 artifact(s), and in which versions, contain that resource? So, essentially just a maven2 repository(or repositeries) inverted index (resource name->[artifacts list with versions]) , that could be useful also for an IDE perhaps: you write a class name in the code, the autocompletion looks into the compile classpath, if it can't find it anywhere, it queries the inverted index and eventually suggests to add a dependency to the pom.xml ... Unnecessary and stupid idea (maybe caused by the tropical weather in Rome)? Or is it an already existing service? Well, let me know something :-) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Does Maven2 have support for Maven1 POMS (specifically Id vs ArtifactId
Inside the Maven2 repo, this pom for SLF4J 1.0 appears to be in Maven2 format: http://www.ibiblio.org/maven2/org/slf4j/slf4j-log4j12/1.0/slf4j-log4j12-1.0.pom but this one for SLF4J 1.0.1 appears to be in Maven1 format: http://www.ibiblio.org/maven2/org/slf4j/slf4j-log4j12/1.0.1/slf4j-log4j12-1.0.1.pom I'm trying to figure out if Maven2 is still capable of using the Maven1 format (I presume not, it's not legal according to the XSD), or if somebody messed up and just checked in a Maven1 format POM in the Maven 2 repo. Colin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: List of Maven Archetypes?
Hi there, To use the WAR plugin for Maven 2 you must execute the following war goal: mvn war:war This will then create a war projet within the target directory. As for using tomcat and jetty you can find out more on the appropriate plugin from the following site http://mojo.codehaus.org/ I had trouble downloading the plugings out of the sandbox so I checked out the source code from the mojo SVN and executed a mvn intall on the project. Hope this helps Trent On 01/07/06, siegfried <[EMAIL PROTECTED]> wrote: I tried your (pete's) example: mvn archetype:create -DartifactId=test -DgroupId=org.test -DarchetypeArtifactId=maven-archetype-webapp -DarchetypeGroupId=org.apache.maven.archetypes -DarchetypeVersion=1.0-alpha-4 Now what? I tried "mvn war" and that did not work! How can I automate the process of creating a war file and copy it to the deployment directory of tomcat or jboss or jetty? Thanks, Siegfried - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: List of Maven Archetypes?
I tried your (pete's) example: mvn archetype:create -DartifactId=test -DgroupId=org.test -DarchetypeArtifactId=maven-archetype-webapp -DarchetypeGroupId=org.apache.maven.archetypes -DarchetypeVersion=1.0-alpha-4 Now what? I tried "mvn war" and that did not work! How can I automate the process of creating a war file and copy it to the deployment directory of tomcat or jboss or jetty? Thanks, Siegfried - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Wanted: Jelly script for deploying maven 1.0 web app to tomcat
On 7/1/06, siegfried <[EMAIL PROTECTED]> wrote: Now build.xml scripts usually have a deploy target for them. Is there a jelly or some other script for maven 1.0 to do that last step of copying the war file to the web server? There's a dedictaed plugin that may help you with deploying to tomcat: http://www.codeczar.com/products/maven-tomcat-plugin/ Regards, Tomek - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Wanted: Jelly script for deploying maven 1.0 web app to tomcat
> try checking http://www.ibiblio.org/maven2/org/apache/maven/archetypes >for the latest version of the archetypes > and if you feel the urge to write a guide on how to use them, the >Maven community will greatly appreciate it. =) I'll try out the mvn 2 webapp archetype soon but your comments are not encouraging (but nevertheless appreciated). How about maven 1 genapp? Is there any documentation on that? I guessed tried "maven war" and bash-3.00$ cp target/id_hello.war /c/Program\ Files/Apache\ Software\Foundation/Tomcat\ 5.5/webapps/ Lo and behold it worked! Are there any other maven targets I relevant to web apps that I would like to know about? Now build.xml scripts usually have a deploy target for them. Is there a jelly or some other script for maven 1.0 to do that last step of copying the war file to the web server? Thanks, Siegfried - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] How to avoid running CPD when using maven-pmd-plugin?
Hi all, I'm using the maven-pmd-plugin to check my code. I am now finding, however, that CPD (that's 'CPD' not 'PMD') is not as useful as I had hoped so I would like to exclude it. I tried adding org.apache.maven.plugins maven-pmd-plugin verify (I also tried test) pmd ... I had hoped this would mean to *only* run PMD but CPD still runs. I used help:describe to see if there were any properties I could set to not run CPD but couldn't find anything. The source of maven-pmd-plugin also didn't reveal anything. Someone please enlighten me, how do I do this? Cheers, Hilco - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: List of Maven Archetypes?
>IMO the projects themselves should provide the archetypes. What projects? Is there a list of starter projects I can start from? >This >proves to be more difficult than it sounds... for Struts I didn't go >beyond turning the "Struts Blank" webapp into an archetype, because >after that, how should I know whether you want Hibernate, iBatis, >Spring, etc? Hmmm... well, maven 1.0.2 justed asked a lot of questions. I could go for that. >At that point, it's not an archetype, it's AppFuse. That is not so bad. The problem with AppFuse is that there is no dialog asking you what you want and don't want. For something as complex as AppFuse, one should really have a GUI. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] How to know which artifact ships a given resource?
Hi, does anybody ever had the need, given a resource name (i.e.: a class name), to know which maven2 artifact(s), and in which versions, contain that resource? So, essentially just a maven2 repository(or repositeries) inverted index (resource name->[artifacts list with versions]) , that could be useful also for an IDE perhaps: you write a class name in the code, the autocompletion looks into the compile classpath, if it can't find it anywhere, it queries the inverted index and eventually suggests to add a dependency to the pom.xml ... Unnecessary and stupid idea (maybe caused by the tropical weather in Rome)? Or is it an already existing service? Well, let me know something :-) -- Alessio Pace. http://www.jroller.com/page/alessiopace
Re: idea plugin and general plugin q
Hi, what version of the idea plugin are you using? Mine is working just fine. For plugin information, you can look here: http://maven.apache.org/plugins/index.html More IDEA plugin specific would be: http://maven.apache.org/plugins/maven-idea-plugin/plugin-info.html Anton Katernoga wrote: Hi, I have some problems with idea plugin, when i do idea:idea, the project, generated out of .. src/main/resources true src/main/config true ... doesn't have resources and config folders marked as Sources! (their contents is not copied to jar) While running task mvn says: [INFO] Not adding resource directory as it has an incompatible target path or filtering: e:\work\search\search -kernel\src\main\resources [INFO] Not adding resource directory as it has an incompatible target path or filtering: e:\work\search\search -kernel\src\main\config Is it a bug in plugin (v2.0)? Another question is how to see a list of plugin goals and their meaning, like what other idea:XXX exist? And where's the plugin config info available (for example what params idea plugin accept, how to set jdk, etc)? Thanks! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
idea plugin and general plugin q
Hi, I have some problems with idea plugin, when i do idea:idea, the project, generated out of .. src/main/resources true src/main/config true ... doesn't have resources and config folders marked as Sources! (their contents is not copied to jar) While running task mvn says: [INFO] Not adding resource directory as it has an incompatible target path or filtering: e:\work\search\search -kernel\src\main\resources [INFO] Not adding resource directory as it has an incompatible target path or filtering: e:\work\search\search -kernel\src\main\config Is it a bug in plugin (v2.0)? Another question is how to see a list of plugin goals and their meaning, like what other idea:XXX exist? And where's the plugin config info available (for example what params idea plugin accept, how to set jdk, etc)? Thanks! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Plugin built and used in the same build
Hi, It's been brought up in Geronimo dev mailing list and I'm asking for clarification. Geronimo build is migrating to M2 and we run into a problem with a Geronimo M2 plugin that's an integral part of the build itself. Geronimo provides its own tailor-made M2 plugins that are part of the build. Is it true that a plugin that's built in a M2 execution and is part of the build (is used later in the build) is not used but the one that's been downloaded? If so, how should a project proceed where it provides its own M2 plugin that's an integral part of the M2-based build? Since the build blows up when the plugin is not found, but its sources are about to be built during M2 execution, what is the trick to build it before M2 will need it? Any help appreciated. Jacek -- Jacek Laskowski http://www.laskowski.net.pl - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] individual log4j config in team environment?
I think your first idea was the best one. Just use a different profile at deploy time to change the log4j.properties filename. If you want to stick with your second idea, a basic ant task should do the trick. On 6/30/06, Adam Hardy <[EMAIL PROTECTED]> wrote: Hi, I would like to configure our m2 setup so that each developer can work with his/her own log4j.properties file, in testing and in deploy. One approach I looked at meant filtering the web.xml and appending the username to the log4j.properties setting, but this requires log4j.properties files for every user going into the final war, which I would like to avoid. Is there a plugin that will do copies, i.e. taking the username-log4j.properties, renaming it to 'log4j.properties' and moving it to the WEB-INF/classes dir? I can then exclude the 'username-lo4j.properties' files. Thanks, Adam - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: assembly plugin problem
Should help you : http://maven.apache.org/plugins/maven-assembly-plugin/assembly.html On 6/30/06, nazim chakik <[EMAIL PROTECTED]> wrote: Hello, I use the maven's assembly plugin and I have the following problem: I have several projects which are modules of one main project containing the pom root. Each module has its own dependencies , When I run the command: (mvn assembly:assembly) on the root pom, I recover the sub projects's .jar but without dependences. If you have a good documentation about assembly or an example, that would help me . thank you in advance PS:I use -> maven-assembly-plugin 2.2-SNAPSHOT Nazim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Project structure and releasing
very good point, yes - it raises 2 questions
1) Do we need to start pushing the continuum heirarchy build idea
faster? (trygvis, kenny and I had a brief talk about this yesterday)
2) should ${project.version} for SNAPSHOT perhaps insert SNAPSHOT rather
than the dated stamp, perhaps providing ${project.snapshotversion} for
the origional system?
Thoughts anyone?
Andy
On Sat, 2006-07-01 at 21:41 +0930, Barrie Treloar wrote:
> > of course in your parent pom.xml you can happily use ${project.version}
> > to specify the dependencies on child modules which saves you worrying
> > about that part :)
>
> I had problems with using ${project.version} as when the artifacts are
> deployed to a snapshot repository the pom metadata is using the
> resolved timestamped snapshot version and not just the latest snapshot
> available.
>
> I have continuum re-building the system hourly and since the parent
> pom and modules are built individually by continuum I had to change
> from ${project.version} in the parent pom dependency management
> section to -SNAPSHOT and all started working as I expected.
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Deploying the site
You can also use "file:". On 6/30/06, Martin Gilday <[EMAIL PROTECTED]> wrote: You will need to add a element under distribution management in your POM. From what I understand you cannot use FTP to deploy the site, as Wagon does not support directory uploading, so I am using SCP. POM.xml-- webdev-site scp://10.0.0.3/var/www/html/projects/ - You will also need to add your login details to the site in either your local settings.xml or in a profile settings.xml- webdev-site myUsername myPassword 664 775 Then run mvn site:deploy. Hope this helps. - Original message - From: "Srinivasan, Nithya (Cognizant)" <[EMAIL PROTECTED]> To: users@maven.apache.org Date: Fri, 30 Jun 2006 10:49:21 +0530 Subject: Deploying the site Hi, Am Nithya, I am a fresh user of maven.I would like to know which url should I give in pom.xml when I deploy my site using mvn site-deploy I would be glad if any of you could help with this issue Thanks and regards Nithya This e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email or any action taken in reliance on this e-mail is strictly prohibited and may be unlawful. Visit us at http://www.cognizant.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Project structure and releasing
of course in your parent pom.xml you can happily use ${project.version}
to specify the dependencies on child modules which saves you worrying
about that part :)
I had problems with using ${project.version} as when the artifacts are
deployed to a snapshot repository the pom metadata is using the
resolved timestamped snapshot version and not just the latest snapshot
available.
I have continuum re-building the system hourly and since the parent
pom and modules are built individually by continuum I had to change
from ${project.version} in the parent pom dependency management
section to -SNAPSHOT and all started working as I expected.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Project structure and releasing
yes and yes.
When running a release cycle a parent pom's upgrading version will be
cascaded to the "parent" section of child modules, replacing the current
version with the new one.
It is currently necessary to specify the parent version in your child
pom.xml, however, this will be removed in the next major release, I
believe.
of course in your parent pom.xml you can happily use ${project.version}
to specify the dependencies on child modules which saves you worrying
about that part :)
Andy
On Sat, 2006-07-01 at 11:29 +0200, Stefan Hübner wrote:
> Andy,
>
> are you saying, that deploying the multiproject-pom as 1.2.1 would
> automatically update the submodule's dependency on their parent from
> 1.2-SNAPSHOT to 1.2.1? Is it even necessary to declare the parent's
> version the submodules refer to?
>
> -Stefan
>
> 2006/7/1, Andrew Williams <[EMAIL PROTECTED]>:
> > I may be wrong, but if your parent is, as in the book, a pom packaged
> > artifact with a module list then doing a release at that level should
> > prompt (with sensible defaults) the release of all the modules.
> >
> > Andy
> >
> > On Fri, 2006-06-30 at 21:29 +0200, Martijn Dashorst wrote:
> > > All,
> > >
> > > I've updated the structure of my projects that depend on one another
> > > to the structure as proposed in the better builds with maven book.
> > >
> > > The one problem I have with this way of building is the link to the
> > > parent project:
> > >
> > >
> > > wicket
> > > wicket-parent
> > > 1.2-SNAPSHOT
> > >
> > >
> > > Now I have to update all projects to perform a release of say version
> > > 1.2.1. Or is there a better way?
> > >
> > > BTW. All projects use snapshot dependencies as adviced earlier on this
> > > mailinglist.
> > >
> > > Martijn
> > >
> >
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Project structure and releasing
Andy, are you saying, that deploying the multiproject-pom as 1.2.1 would automatically update the submodule's dependency on their parent from 1.2-SNAPSHOT to 1.2.1? Is it even necessary to declare the parent's version the submodules refer to? -Stefan 2006/7/1, Andrew Williams <[EMAIL PROTECTED]>: I may be wrong, but if your parent is, as in the book, a pom packaged artifact with a module list then doing a release at that level should prompt (with sensible defaults) the release of all the modules. Andy On Fri, 2006-06-30 at 21:29 +0200, Martijn Dashorst wrote: > All, > > I've updated the structure of my projects that depend on one another > to the structure as proposed in the better builds with maven book. > > The one problem I have with this way of building is the link to the > parent project: > > > wicket > wicket-parent > 1.2-SNAPSHOT > > > Now I have to update all projects to perform a release of say version > 1.2.1. Or is there a better way? > > BTW. All projects use snapshot dependencies as adviced earlier on this > mailinglist. > > Martijn > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] Transitive Dependency Questions
Wendy, 2006/7/1, Wendy Smoak <[EMAIL PROTECTED]>: On 6/30/06, Stephen Duncan <[EMAIL PROTECTED]> wrote: > In either case, with Maven 2, the solution (as far as I know) is > simply to directly declare your dependency on Bob's Ace Logger v1.0.1. > Then you'll get that version. In addition, in Scenario One, even if Sally did know about Bob's 1.0.1 version, she should not *change* her v2.0 pom. She would need to release a 2.0.1 version of her framework with the new dependency. Would Sally be really in need to release a new version of v2.0's pom, if she had used version ranges in the first place? She could just declare the dependency to Bob's framework as [1.0,) (or maybe [1.0,2.0) considering major changes probably won't be interoperable) -Stefan -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
