[JBoss JIRA] (RFPL-727) Metamer on Hudson: configure Code Coverage analysis
by Pavol Pitonak (JIRA)
[ https://issues.jboss.org/browse/RFPL-727?page=com.atlassian.jira.plugin.s... ]
Pavol Pitonak resolved RFPL-727.
--------------------------------
Resolution: Deferred
We agreed with Jan that it's better idea to focus on code coverage in framework tests than in Metamer.
> Metamer on Hudson: configure Code Coverage analysis
> ---------------------------------------------------
>
> Key: RFPL-727
> URL: https://issues.jboss.org/browse/RFPL-727
> Project: RichFaces Planning
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: QE
> Environment: Hudson
> Reporter: Lukáš Fryč
> Assignee: Jan Papousek
> Labels: hudson, metamer
> Fix For: 5-Future
>
>
> Configure two new jobs Hudson, which will implement Code Coverage mechanisms integrated to Hudson/Maven environment:
> Investigate following options: Clover, Emma, Cobertura
> Configure following setups:
> 1. Metamer Ftest coverage of Metamer Application's code
> 2. Metamer Ftest coverage of RichFaces Framework code itself
> *code coverage in JBoss AS 7*: [AS-2022|https://issues.jboss.org/browse/AS7-2022]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 10 months
[JBoss JIRA] (RFPL-2982) Not all RichFaces 5.0.0.Alpha1 artifacts are published to Maven Central
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RFPL-2982?page=com.atlassian.jira.plugin.... ]
Brian Leathem updated RFPL-2982:
--------------------------------
Description:
In the Maven Central there is only these artifacts for version *5.0.0.Alpha1*:
* {{richfaces-bom}}
* {{richfaces-archetype-kitchensink}}
* {{richfaces-archetype-simpleapp}}
We are missing for example:
* {{org.richfaces:richfaces:jar}}
* {{org.richfaces:richfaces-build}}
* {{org.richfaces:richfaces-distribution}}
* {{org.richfaces:richfaces-parent}}
* {{org.richfaces:richfaces-push-depchain}}
* {{org.richfaces:richfaces-resource-optimizer-maven-plugin:maven-plugin}}
Basically I would say everything which can be found [here|https://repository.jboss.org/nexus/content/groups/public-jboss/org/r...] with the {{5.0.0.Alpha1}} version.
was:
In the Maven Central there is only these artifacts for version *5.0.0.Alpha1*:
* {{richfaces-bom}}
* {{richfaces-archetype-kitchensink}}
* {{richfaces-archetype-simpleapp}}
We are missing for example:
* {{org.richfaces:richfaces:jar}}
* {{richfaces-build}}
* {{richfaces-distribution}}
* {{richfaces-parent}}
* {{richfaces-push-depchain}}
* {{richfaces-resource-optimizer-maven-plugin}}
Basically I would say everything which can be found [here|https://repository.jboss.org/nexus/content/groups/public-jboss/org/r...] with the {{5.0.0.Alpha1}} version.
> Not all RichFaces 5.0.0.Alpha1 artifacts are published to Maven Central
> -----------------------------------------------------------------------
>
> Key: RFPL-2982
> URL: https://issues.jboss.org/browse/RFPL-2982
> Project: RichFaces Planning
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: release
> Affects Versions: 5.0.0.Alpha1
> Reporter: Juraj Húska
> Assignee: Brian Leathem
> Priority: Critical
>
> In the Maven Central there is only these artifacts for version *5.0.0.Alpha1*:
> * {{richfaces-bom}}
> * {{richfaces-archetype-kitchensink}}
> * {{richfaces-archetype-simpleapp}}
> We are missing for example:
> * {{org.richfaces:richfaces:jar}}
> * {{org.richfaces:richfaces-build}}
> * {{org.richfaces:richfaces-distribution}}
> * {{org.richfaces:richfaces-parent}}
> * {{org.richfaces:richfaces-push-depchain}}
> * {{org.richfaces:richfaces-resource-optimizer-maven-plugin:maven-plugin}}
> Basically I would say everything which can be found [here|https://repository.jboss.org/nexus/content/groups/public-jboss/org/r...] with the {{5.0.0.Alpha1}} version.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 10 months