Having trouble with Maven artifact / dependency classifier.


I'm currently using a custom assembly descriptor with Maven to share flex configuration files between a few Maven modules.  It's very similar to what is described here (near the bottom):


The theory is to create a custom assembly that packages the needed configuration files into a zip file with a classifier of 'resources'.  The artifact it produces ends up having the classifier appended to the name.  For example, 'blazeds-config-1.0-SNAPSHOT-resources.zip'.  Other modules can then use the unpack-dependencies goal of the maven-dependency-plugin to uncompress the needed configuration files at compile time.

I have a dependency management section in the parent POM for my project and have the following dependency defined:


IDEA always highlights the artifactId and version and complains the dependency doesn't exist.  Is there a way I can make it take the classifier into account?  My project builds fine, so it's only a minor annoyance at the moment.

Edit: After a restart of IDEA and a fresh checkout of my project I'm no longer having this issue.  I'm not sure what caused it, but don't care as long as it's working now :-)

Message was edited by: Ryan J

1 comment
Comment actions Permalink

After doing a bit more work with my POMs / local Nexus repository I think my issue may have been related to a bug in the maven-deploy-plugin version 2.4 that was keeping my .pom files from being deployed to my local repo.  See: http://jira.codehaus.org/browse/MDEPLOY-78


Please sign in to leave a comment.