[ 
https://issues.apache.org/jira/browse/TAVERNA-1001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15569133#comment-15569133
 ] 

Stian Soiland-Reyes commented on TAVERNA-1001:
----------------------------------------------

It happens only with <packaging>jar</packaging> (the default) as 
<packaging>taverna-application</packaging> is commented out. Changing to 
<packaging>bundle</packaging> also works.

> Command line build fails with maven-jar-plugin 3.0
> --------------------------------------------------
>
>                 Key: TAVERNA-1001
>                 URL: https://issues.apache.org/jira/browse/TAVERNA-1001
>             Project: Apache Taverna
>          Issue Type: Bug
>          Components: Taverna Command-line Tool
>            Reporter: Stian Soiland-Reyes
>            Priority: Critical
>              Labels: maven
>             Fix For: command-line 3.2.0
>
>
> Bumping taverna-commandline pom to use newer Maven parents have caused a new 
> bug with a newer maven-jar-plugin:
> {code}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-jar-plugin:3.0.0:jar (default-jar) on project 
> taverna-commandline-product: You have to use a classifier to attach 
> supplemental artifacts to the project instead of replacing them. -> [Help 1]
> [ERROR] 
> {code}
> This has something to do with the assembly plugin. I've seen this mention on 
> dev@maven - need to investigate what is the good fix. 
> (Disabling the <attach> in the src/main/assembly config is not good, as it 
> would mean taverna-server can't use the newer command lines - but that could 
> be a short-term workaround)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to