[JBoss JIRA] (JBIDE-16214) Code Coverage jobs needs to have locally available measured plugins
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16214?page=com.atlassian.jira.plugi... ]
Vlado Pakan edited comment on JBIDE-16214 at 1/10/14 10:19 AM:
---------------------------------------------------------------
I'm getting lot of these exceptions:
{noformat}
Caught: Error while creating report
Error while creating report
at org.jacoco.ant.ReportTask.execute(ReportTask.java:498)
at org.jacoco.ant.ReportTask$execute.call(Unknown Source)
at jacoco.run(jacoco.groovy:61)
Caused by: java.io.IOException: Error while analyzing class org.jboss.tools.common.core-3.5.2.Final-v20131204-1734-B141.jar(a)org/jboss/tools/common/java/impl/Values.class.
at org.jacoco.core.analysis.Analyzer.analyzerError(Analyzer.java:139)
at org.jacoco.core.analysis.Analyzer.analyzeClass(Analyzer.java:133)
at org.jacoco.core.analysis.Analyzer.analyzeAll(Analyzer.java:164)
at org.jacoco.core.analysis.Analyzer.analyzeZip(Analyzer.java:235)
at org.jacoco.core.analysis.Analyzer.analyzeAll(Analyzer.java:167)
at org.jacoco.ant.ReportTask.createBundle(ReportTask.java:570)
at org.jacoco.ant.ReportTask.createReport(ReportTask.java:545)
at org.jacoco.ant.ReportTask.createReport(ReportTask.java:542)
at org.jacoco.ant.ReportTask.execute(ReportTask.java:492)
... 2 more
Caused by: java.lang.IllegalStateException: Can't add different class with same name: org/jboss/tools/common/java/impl/Values
at org.jacoco.core.analysis.CoverageBuilder.visitCoverage(CoverageBuilder.java:89)
at org.jacoco.core.analysis.Analyzer$1.visitEnd(Analyzer.java:81)
at org.jacoco.asm.ClassVisitor.visitEnd(Unknown Source)
at org.jacoco.core.internal.flow.ClassProbesAdapter.visitEnd(ClassProbesAdapter.java:135)
at org.jacoco.asm.ClassReader.accept(Unknown Source)
at org.jacoco.asm.ClassReader.accept(Unknown Source)
at org.jacoco.core.analysis.Analyzer.analyzeClass(Analyzer.java:96)
at org.jacoco.core.analysis.Analyzer.analyzeClass(Analyzer.java:131)
... 9 more
{noformat}
In case pattern not causing this exception is used report looks fine.
But anyways we need code coverage report generated by jacoco jenkins plugins and code coverage results published to sonar via sonar jenkins plugin and for this your script will not help will he?
was (Author: vpakan):
I'm getting lot of these exceptions:
{nofromat}
Caught: Error while creating report
Error while creating report
at org.jacoco.ant.ReportTask.execute(ReportTask.java:498)
at org.jacoco.ant.ReportTask$execute.call(Unknown Source)
at jacoco.run(jacoco.groovy:61)
Caused by: java.io.IOException: Error while analyzing class org.jboss.tools.common.core-3.5.2.Final-v20131204-1734-B141.jar(a)org/jboss/tools/common/java/impl/Values.class.
at org.jacoco.core.analysis.Analyzer.analyzerError(Analyzer.java:139)
at org.jacoco.core.analysis.Analyzer.analyzeClass(Analyzer.java:133)
at org.jacoco.core.analysis.Analyzer.analyzeAll(Analyzer.java:164)
at org.jacoco.core.analysis.Analyzer.analyzeZip(Analyzer.java:235)
at org.jacoco.core.analysis.Analyzer.analyzeAll(Analyzer.java:167)
at org.jacoco.ant.ReportTask.createBundle(ReportTask.java:570)
at org.jacoco.ant.ReportTask.createReport(ReportTask.java:545)
at org.jacoco.ant.ReportTask.createReport(ReportTask.java:542)
at org.jacoco.ant.ReportTask.execute(ReportTask.java:492)
... 2 more
Caused by: java.lang.IllegalStateException: Can't add different class with same name: org/jboss/tools/common/java/impl/Values
at org.jacoco.core.analysis.CoverageBuilder.visitCoverage(CoverageBuilder.java:89)
at org.jacoco.core.analysis.Analyzer$1.visitEnd(Analyzer.java:81)
at org.jacoco.asm.ClassVisitor.visitEnd(Unknown Source)
at org.jacoco.core.internal.flow.ClassProbesAdapter.visitEnd(ClassProbesAdapter.java:135)
at org.jacoco.asm.ClassReader.accept(Unknown Source)
at org.jacoco.asm.ClassReader.accept(Unknown Source)
at org.jacoco.core.analysis.Analyzer.analyzeClass(Analyzer.java:96)
at org.jacoco.core.analysis.Analyzer.analyzeClass(Analyzer.java:131)
... 9 more
{nofromat}
> Code Coverage jobs needs to have locally available measured plugins
> -------------------------------------------------------------------
>
> Key: JBIDE-16214
> URL: https://issues.jboss.org/browse/JBIDE-16214
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: build
> Affects Versions: 4.1.1.CR1
> Reporter: Vlado Pakan
> Assignee: Mickael Istria
> Fix For: 4.1.x
>
>
> Code Coverage calculating via maven build returns 0% coverage because it's using source code and binary plugins installed from update site.
> When these are built locally prior to build calculating code coverage it returns correct results.
> Unfortunately sometimes maven build used plugins installed from update site instead of those which are locally build.
> We need to find way how to fix this.
> It's already reported here https://bugs.eclipse.org/bugs/show_bug.cgi?id=352560
--
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
12 years, 2 months
[JBoss JIRA] (JBIDE-16214) Code Coverage jobs needs to have locally available measured plugins
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16214?page=com.atlassian.jira.plugi... ]
Vlado Pakan commented on JBIDE-16214:
-------------------------------------
I'm getting lot of these exceptions:
{nofromat}
Caught: Error while creating report
Error while creating report
at org.jacoco.ant.ReportTask.execute(ReportTask.java:498)
at org.jacoco.ant.ReportTask$execute.call(Unknown Source)
at jacoco.run(jacoco.groovy:61)
Caused by: java.io.IOException: Error while analyzing class org.jboss.tools.common.core-3.5.2.Final-v20131204-1734-B141.jar(a)org/jboss/tools/common/java/impl/Values.class.
at org.jacoco.core.analysis.Analyzer.analyzerError(Analyzer.java:139)
at org.jacoco.core.analysis.Analyzer.analyzeClass(Analyzer.java:133)
at org.jacoco.core.analysis.Analyzer.analyzeAll(Analyzer.java:164)
at org.jacoco.core.analysis.Analyzer.analyzeZip(Analyzer.java:235)
at org.jacoco.core.analysis.Analyzer.analyzeAll(Analyzer.java:167)
at org.jacoco.ant.ReportTask.createBundle(ReportTask.java:570)
at org.jacoco.ant.ReportTask.createReport(ReportTask.java:545)
at org.jacoco.ant.ReportTask.createReport(ReportTask.java:542)
at org.jacoco.ant.ReportTask.execute(ReportTask.java:492)
... 2 more
Caused by: java.lang.IllegalStateException: Can't add different class with same name: org/jboss/tools/common/java/impl/Values
at org.jacoco.core.analysis.CoverageBuilder.visitCoverage(CoverageBuilder.java:89)
at org.jacoco.core.analysis.Analyzer$1.visitEnd(Analyzer.java:81)
at org.jacoco.asm.ClassVisitor.visitEnd(Unknown Source)
at org.jacoco.core.internal.flow.ClassProbesAdapter.visitEnd(ClassProbesAdapter.java:135)
at org.jacoco.asm.ClassReader.accept(Unknown Source)
at org.jacoco.asm.ClassReader.accept(Unknown Source)
at org.jacoco.core.analysis.Analyzer.analyzeClass(Analyzer.java:96)
at org.jacoco.core.analysis.Analyzer.analyzeClass(Analyzer.java:131)
... 9 more
{nofromat}
> Code Coverage jobs needs to have locally available measured plugins
> -------------------------------------------------------------------
>
> Key: JBIDE-16214
> URL: https://issues.jboss.org/browse/JBIDE-16214
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: build
> Affects Versions: 4.1.1.CR1
> Reporter: Vlado Pakan
> Assignee: Mickael Istria
> Fix For: 4.1.x
>
>
> Code Coverage calculating via maven build returns 0% coverage because it's using source code and binary plugins installed from update site.
> When these are built locally prior to build calculating code coverage it returns correct results.
> Unfortunately sometimes maven build used plugins installed from update site instead of those which are locally build.
> We need to find way how to fix this.
> It's already reported here https://bugs.eclipse.org/bugs/show_bug.cgi?id=352560
--
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
12 years, 2 months
[JBoss JIRA] (JBDS-1169) PicketLink Integration with SOA-P5 (JBDS ESB XML Tooling plus Action design)
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-1169?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen resolved JBDS-1169.
---------------------------------------
Resolution: Out of Date
This issue have not seen any updates for a year thus we are resolving it as "out of date".
If you believe this jira is still relevant please reopen the issue or open a new one mentioning this jira.
> PicketLink Integration with SOA-P5 (JBDS ESB XML Tooling plus Action design)
> ----------------------------------------------------------------------------
>
> Key: JBDS-1169
> URL: https://issues.jboss.org/browse/JBDS-1169
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: integration-platform
> Reporter: Gary Lamperillo
> Assignee: Brian Fitzpatrick
> Fix For: LATER
>
> Attachments: SequenceDiagram_PicketLink.pdf
>
>
> With the PicketLink and SOA-P 5 quickstart sample (security_saml), a client requests a web service and immediately receives an acknowledgement back. A more realistic use case would be to request a token and use it for the request using a chainhandler. SOA-P 5 can still be utilized as the intermediate. There are a few additional pieces that are needed. The SOA-P 5 needs a Service which forwards issue requests to PicketLink and then sends the Token client. SOA-P 5 needs another service that validates the tokens in the requests and either forwards the request or logs the exception and send error to the client. Both of these services should be implemented as new actions, and should be available in the ESB Actions as "Security Services". In addition, the current implementation requires smooks to add the assertion to the out going message. While the internal implementation using smooks is fine, it should not be required by the user to deal with these internals. In the new "Security Services" section a "Add Assertion" should be available.
--
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
12 years, 2 months
[JBoss JIRA] (JBDS-1171) Schema Tooling in Relation to Web Service Development
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-1171?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen resolved JBDS-1171.
---------------------------------------
Resolution: Out of Date
This issue have not seen any updates for a year thus we are resolving it as "out of date".
If you believe this jira is still relevant please reopen the issue or open a new one mentioning this jira.
> Schema Tooling in Relation to Web Service Development
> -----------------------------------------------------
>
> Key: JBDS-1171
> URL: https://issues.jboss.org/browse/JBDS-1171
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: integration-platform
> Affects Versions: 3.0.0.CR1
> Reporter: Gary Lamperillo
> Assignee: Brian Fitzpatrick
> Fix For: LATER
>
>
> In JBDS 3.0, tooling is needed to convert xml to schema and schema to JAXB classes. I have used Trang(http://www.thaiopensource.com/download/) to handle the schema creation, but there are other tools as well and this is an implementation detail. Developers should not need to run a command line tools to get this done and then copy the schema back to JBDS. For the JAXB classes creation, EAP 5 ships with the necessary binaries for this , that is the JAXB-XJC.jar. Again, a command line java -jar jaxb-xjc.jar <schema file> should not be needed. These tasks are very common for web service developers.
--
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
12 years, 2 months
[JBoss JIRA] (JBDS-1345) Be able to expand the location field
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-1345?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen resolved JBDS-1345.
---------------------------------------
Resolution: Out of Date
This issue have not seen any updates for a year thus we are resolving it as "out of date".
If you believe this jira is still relevant please reopen the issue or open a new one mentioning this jira.
> Be able to expand the location field
> ------------------------------------
>
> Key: JBDS-1345
> URL: https://issues.jboss.org/browse/JBDS-1345
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: installer
> Affects Versions: 4.0.0.M2
> Environment: Mac JBDS installer
> Reporter: Jim Tyrrell
> Assignee: Denis Golovin
> Priority: Minor
> Fix For: LATER
>
> Attachments: Screen shot 2010-09-29 at 10.22.24 AM.png
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> It would be nice if I could get a slider/expander so that I can expand/view the entire Location tab. Note in the attached screen shot I can not expand that to see the full path to my Servers instances.
--
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
12 years, 2 months
[JBoss JIRA] (JBDS-1307) Unable to reverse engineer entities from database for Seam project
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-1307?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen resolved JBDS-1307.
---------------------------------------
Resolution: Out of Date
This issue have not seen any updates for a year thus we are resolving it as "out of date".
If you believe this jira is still relevant please reopen the issue or open a new one mentioning this jira.
> Unable to reverse engineer entities from database for Seam project
> ------------------------------------------------------------------
>
> Key: JBDS-1307
> URL: https://issues.jboss.org/browse/JBDS-1307
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: seam
> Affects Versions: 4.0.0.M2
> Environment: I tried it with these configurations:
> * jbdevstudio-eap-linux-gtk-x86_64-4.0.0.v201009011720R-H437-M2.jar
> * jbdevstudio-linux-gtk-x86_64-4.0.0.v201009011720R-H437-M2.jar with Seam in EAP 5.1.0.CR3
> Reporter: Martin Gencur
> Fix For: LATER
>
> Attachments: JBDS_cropped, JBDS_cropped.png
>
>
> I'm attaching a screenshot with the error.
> Steps to reproduce:
> 1) Create a new Seam web project
> - configure the Mysql connection with these parameters:
> hibernate.connection.password=seam
> hibernate.connection.username=seam
> hibernate.connection.driver_class=com.mysql.jdbc.Driver
> hibernate.dialect=org.hibernate.dialect.MySQL5Dialect
> hibernate.connection.url=jdbc\:mysql\://vmg08.mw.lab.eng.bos.redhat.com\:3306/seam
> hibernate.connection.provider_class=org.hibernate.connection.DriverManagerConnectionProvider
> hibernate.datasource=
> hibernate.transaction.manager_lookup_class=
> 2) Choose Generate entities, refresh, add Person and Vehicle and click finish (or something like that)
> If you're abou to make this JIRA publicly available, please remove the username and password.
--
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
12 years, 2 months
[JBoss JIRA] (JBDS-1146) Faces-config.xml editor has different popup menu than is described in JSF Tools Tutorial
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-1146?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen resolved JBDS-1146.
---------------------------------------
Resolution: Out of Date
This issue have not seen any updates for a year thus we are resolving it as "out of date".
If you believe this jira is still relevant please reopen the issue or open a new one mentioning this jira.
> Faces-config.xml editor has different popup menu than is described in JSF Tools Tutorial
> ----------------------------------------------------------------------------------------
>
> Key: JBDS-1146
> URL: https://issues.jboss.org/browse/JBDS-1146
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: z - Legacy - Doc - JSFTools
> Affects Versions: 3.0.0.CR3
> Environment: JBDS: jbdevstudio-linux-gtk-x86_64-3.0.0.v201003050335M-H45-CR3
> Documentation: http://download.exadel.com/jboss_demos/JBDS_3.0.0.GA.zip
> Reporter: Vlado Pakan
> Assignee: Svetlana Mukhina
> Fix For: LATER
>
> Attachments: faces-config-popup-menu.png
>
>
> There is no possibility to Add View to daces-config.xml diagram using popup menu as is written in JBDS Tutorial. User hase to choose button "View Template" from Diagram Editor Toolbar.
> Attached is screenshot of Diagram Editor popup menu.
> Documentation file: JBDS_2guidesversions/en/jsf_tools_tutorial/html_single/index.html
> Chapter: 3.1. Adding Two Views (JSP Pages)
--
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
12 years, 2 months