[
https://issues.jboss.org/browse/RF-11810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lukáš Fryč updated RF-11810:
----------------------------
Description:
(Issue reported by Lukas Fryc)
Marek Novotny (manaRH) has recently reported that sometimes RF build fails for
him since {{richfaces-components-ui}} module is generating JAR using
{{maven-assembly-plugin}} which has the same name as the standard
{{maven-jar-plugin}} artifact would be called.
This may lead into potential clash for bad timings, especially when these
plugins are ran on the same lifecycle phase.
The symptoms are failing applications (and functional tests) which are not able
to use any UI implementation classes.
We should either:
# change lifecycle mapping of plugins
# modify {{maven-jar-plugin}} settings
was:
(Issue reported by Lukas Fryc)
Marek Novotny (manaRH) has recently reported that sometimes RF build fails for
him since {{richfaces-components-ui}} module is generating JAR using
{{maven-assembly-plugin}} which has the same name as the standard
{{maven-jar-plugin}} artifact would be called.
The symptoms are failing applications (and functional tests) which are not able
to use any UI implementation classes.
This may lead into potential clash for bad timings, especially when these
plugins are ran on the same lifecycle phase.
We should either:
# change lifecycle mapping of plugins
# modify {{maven-jar-plugin}} settings
> Fix the richfaces-components-ui build to do not overwrite assemblied JAR
> ------------------------------------------------------------------------
>
> Key: RF-11810
> URL: https://issues.jboss.org/browse/RF-11810
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: build/distribution
> Affects Versions: 4.1.0.Final
> Reporter: Marek Novotny
>
> (Issue reported by Lukas Fryc)
> Marek Novotny (manaRH) has recently reported that sometimes RF build fails
> for him since {{richfaces-components-ui}} module is generating JAR using
> {{maven-assembly-plugin}} which has the same name as the standard
> {{maven-jar-plugin}} artifact would be called.
> This may lead into potential clash for bad timings, especially when these
> plugins are ran on the same lifecycle phase.
> The symptoms are failing applications (and functional tests) which are not
> able to use any UI implementation classes.
> We should either:
> # change lifecycle mapping of plugins
> # modify {{maven-jar-plugin}} settings
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
richfaces-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/richfaces-issues
