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

Woonsan Ko commented on JS2-1366:
---------------------------------

Hi [~anydoby],

Just out of curiosity, regarding "... we are using just the jetspeed's 
excellent unpack plugins ...", if you're using the plugin in other projects of 
yours, then why don't you simply use the Maven Dependency Plugin (which was 
mentioned as well in \[1\])? 
The custom maven plugins of Jetspeed-2 have been a hurdle to maintain or 
improve. So, I wonder if you have any strong reason not to move to the maven 
standard practices.

Regards,

Woonsan

\[1\] 
http://portals.apache.org/jetspeed-2/buildguide/jetspeed-unpack-plugin.html

>  org.apache.portals.jetspeed-2:jetspeed-unpack-maven-plugin:2.3.1:unpack Does 
> work with Maven 3.6.0
> ---------------------------------------------------------------------------------------------------
>
>                 Key: JS2-1366
>                 URL: https://issues.apache.org/jira/browse/JS2-1366
>             Project: Jetspeed 2
>          Issue Type: Bug
>    Affects Versions: 2.3.1
>            Reporter: Karl Heinz Marbaise
>            Priority: Blocker
>         Attachments: JS2-1366.patch
>
>
> Copied the issue message from MNG-6504
> Reproduced on different machines. Reproduced on same machine, changing only 
> the maven version.
> Command to build:  mvn clean compile 
> {code}
> [ERROR] Failed to execute goal 
> org.apache.portals.jetspeed-2:jetspeed-unpack-maven-plugin:2.3.1:unpack 
> (copy-hsac-baseline) on project sample-fitnesse-project-using-hsac-fixtures: 
> Unable to parse configuration of mojo 
> org.apache.portals.jetspeed-2:jetspeed-unpack-maven-plugin:2.3.1:unpack for 
> parameter pluginArtifacts: Cannot assign configuration entry 
> 'pluginArtifacts' with value '${plugin.artifacts}' of type 
> java.util.Collections.UnmodifiableRandomAccessList to property of type 
> java.util.ArrayList -> [Help 1]
> {code}
> Currently the maven plugins Maven 2.0 based and also uses old style plugins 
> definition and not annotation based plugin and parameter definition.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to