maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Casey (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (MASSEMBLY-316) useProjectArtifact is documented but not in schema
Date Wed, 03 Sep 2008 19:22:49 GMT

    [ http://jira.codehaus.org/browse/MASSEMBLY-316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=146874#action_146874
] 

John Casey commented on MASSEMBLY-316:
--------------------------------------

I'm confused; you seem to be expecting useProjectArtifact to be configurable from within the
POM, when it's an option on a dependencySet within the assembly descriptor and/or component
descriptor file.

Can you providing a test project that displays the problem you're having, so we can reproduce
it?

> useProjectArtifact is documented but not in schema
> --------------------------------------------------
>
>                 Key: MASSEMBLY-316
>                 URL: http://jira.codehaus.org/browse/MASSEMBLY-316
>             Project: Maven 2.x Assembly Plugin
>          Issue Type: Bug
>            Reporter: Thomas Diesler
>
> I like to include a module's dependencies, but not the projectArtifact itself. This functionality
seem to be provided by 'useProjectArtifact'
> http://maven.apache.org/plugins/maven-assembly-plugin/assembly.html
> which is not defined in http://maven.apache.org/xsd/assembly-1.1.0-SNAPSHOT.xsd
> and does not seem to work anymore. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message