Re: Cannot find ArtifactResolver with hint: project-cache-aware...NoSuchElementException

I found my issue. User error. org.apache.maven.plugins maven-assembly-plugin 2.2.1 + + +src/main/assembly/dist.xml + + - - -src/main/assembly/dist.xml -

Cannot find ArtifactResolver with hint: project-cache-aware...NoSuchElementException

Greetings, Please excuse my ignorance surely on display in my email below. I am fairly new to maven. I am getting the error below: [DEBUG] Cannot find ArtifactResolver with hint: project-cache-aware org.codehaus.plexus.component.repository.exception.ComponentLookupException: java.util.NoSuchElem

Re: Problems with MAVEN's-ANT on OpenVMS

> Thank you Wayne for this excellent Analysis. If a routine belonging to the > file system returns something badly, > there is a little chance to influence by a logical JAVA$FILENAME_CONTROL > which can be set to so many values > used to control filename encodings, particular how to deal with dot

RE: Profile activation based on property absence OR property value of "false"

Yes you can, try: !true See http://svn.codehaus.org/mojo/trunk/mojo/sql-maven-plugin/pom.xml > Date: Mon, 24 Oct 2011 17:30:24 -0400 > Subject: Profile activation based on property absence OR property value of > "false" > From: ljnel...@gmail.com > To

Profile activation based on property absence OR property value of "false"

It looks like activating a profile based on EITHER the absence of a property OR the presence of that property with a particular value is not possible. Is that correct? For example, suppose I wanted to add in a bunch of plugins if the "skipTests" property was (a) specified with a value of "false" o

Expected behavior of the -f command line flag and working directories

Hi All, I am curious what the expected behavior with is when using the -f command line option with respect to the working directory. I am running 'mvn -f /pom.xml' and it seems Maven will change the working directory to '' before executing the actual build. Is this intentional and by desi

Re: where to put common dependecies in multi-module project

On 24/10/2011 10:43 AM, codingplayer wrote: Hi Jan, i get it now, declaring the dependencies in the parent-pom (or directly in each module's pom, where it will be used) leads to a proper binding of the library to the modules, and everybody who changes this dependency, should then be aware of the

Re: where to put common dependecies in multi-module project

Hi Jan, i get it now, declaring the dependencies in the parent-pom (or directly in each module's pom, where it will be used) leads to a proper binding of the library to the modules, and everybody who changes this dependency, should then be aware of the influences on the code. While using transiti

Re: where to put common dependecies in multi-module project

This is how we solve this problem in our case with a 70+ module project with many 3rd party tools (Apache, JasperSoft, Spring, JBoss-Hibernate). http://blog.artifact-software.com/tech/?p=121 Ron On 24/10/2011 3:58 AM, codingplayer wrote: Hi, i'm wondering where to put my common dependenies

Central repository full index

Hi, We're using maven indexer formerly Nexus Indexer in our application. We used to have a ~0.5Gb index holding list of classes in each artifact. This information is not available anymore. Is there any chance of making such kind of index available again ? Many 10x, Edo Shor -- View this messa

Re: where to put common dependecies in multi-module project

If you actually use a dependency (in code) in a module, that dependency should always be a direct dependency of the module, either declared in the module itself or in a parent POM. From my experience, declaring dependencies (not dependencyManagement) in parent POMs comes with some disadvantages, bu

Re: where to put common dependecies in multi-module project

Hi Martin, thanks for your hint to the section. But actually, that is not exaclty what i want. Since i do not want to repeat defining each common dependency separately for each sub-module. This approach would be ideal, if i want to use this dependency in many sub-modules (but not all), so i cou

Re: where to put common dependecies in multi-module project

Hi! Define the versions of your dependencies in the parent's section. Define the actual dependency in every submodule where you use it. Without the version! The analyze goal of the maven-dependency-plugin can help you to find out if you should declare a dependency or not. hth, - martin On M

where to put common dependecies in multi-module project

Hi, i'm wondering where to put my common dependenies in my multimodule project. Let's say, we have a project called sandbox, with three submodules. - sandbox-core - sandbox-service - sandbox-web Existing dependencies: - sandbox-service has a dependency to sandbox-core - sandbox-web has a depende

AW: Problems with MAVEN's-ANT on OpenVMS

Hi Wayne Thank you Wayne for this excellent Analysis. If a routine belonging to the file system returns something badly, there is a little chance to influence by a logical JAVA$FILENAME_CONTROL which can be set to so many values used to control filename encodings, particular how to deal with do