[JBoss JIRA] (JBIDE-10777) Use Sonar for Code Quality Analysis
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-10777?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-10777:
----------------------------------------
Other example:
* job https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.1_trunk...
* reports http://sonar.mw.lab.eng.bos.redhat.com/sonar/dashboard/index/org.jboss.to...
> Any ETA Sonar reports being available from the outside ?
No ETA. I don't think this is currently planned. Sonar does not provide a "public mirror" thing as Jenkins does, so if we want to make reports public, it means we have to make Sonar public... So far, the JBoss infrastructure does not allow to do that.
> Use Sonar for Code Quality Analysis
> -----------------------------------
>
> Key: JBIDE-10777
> URL: https://issues.jboss.org/browse/JBIDE-10777
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: Build/Releng
> Affects Versions: 3.1.2
> Environment: any
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Priority: Minor
> Fix For: LATER
>
> Original Estimate: 1 week
> Remaining Estimate: 1 week
>
> Sonar provides a very powerful tool to get report about tests, code coverage, and static analysis in a project (errors, duplications...). It is easy to use, there is a nice integration with Maven and Hudson/Jenkins. It provides reporting tools for everything existing in the Java world, and more.
> Adding Sonar to Hudson really helps to make code better.
> http://www.sonarsource.org/
--
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
13 years, 2 months
[JBoss JIRA] (JBIDE-13417) Maven plugin org.jboss.tools.tycho-plugins:repository-utils fails to update p2repository archive in full jbosstools build
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13417?page=com.atlassian.jira.plugi... ]
Mickael Istria resolved JBIDE-13417.
------------------------------------
Resolution: Cannot Reproduce Bug
I did try several combinations (with a maven repo in which one I removed org/jboss/tools/*) and could not reproduce.
Please re-open this issue in case you meet it again and can reproduce it.
However, this issue made us understand that our Tycho plugins are better following the versioning of Tycho, and they were update consequently. Current version is 0.16.0-SNAPSHOT, but parent pom still use the 0.0.1-SNAPSHOT, which is still working fine.
> Maven plugin org.jboss.tools.tycho-plugins:repository-utils fails to update p2repository archive in full jbosstools build
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-13417
> URL: https://issues.jboss.org/browse/JBIDE-13417
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Build/Releng
> Reporter: Denis Golovin
> Assignee: Mickael Istria
> Fix For: 4.1.0.Alpha1
>
>
> Noticed that base/site build fails with error during the full jbosstools build with error below, but it is fine for component build. The problem is that jbosstools-maven-plugins module is not using jbosstools/parent and thus using tycho version 0.15.0 which is defined in jbosstools-maven-plugins/pom.xml After setting it to the same version as in jbosstools/parent/pom.xml problem is gone.
> {code}[ERROR] Failed to execute goal org.jboss.tools.tycho-plugins:repository-utils:0.0.1-SNAPSHOT:generate-repository-facade (generate-facade) on project server.site: Execution generate-facade of goal org.jboss.tools.tycho-plugins:repository-utils:0.0.1-SNAPSHOT:generate-repository-facade failed: A required class was missing while executing org.jboss.tools.tycho-plugins:repository-utils:0.0.1-SNAPSHOT:generate-repository-facade: org/jboss/tools/tycho/sitegenerator/GenerateRepositoryFacadeMojo$2
> [ERROR] -----------------------------------------------------
> [ERROR] realm = plugin>org.jboss.tools.tycho-plugins:repository-utils:0.0.1-SNAPSHOT
> [ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
> [ERROR] urls[0] = file:/home/eskimo/Projects/jbds/jbosstools-fork-submodules/../.m2/jbosstools-fork-submodules-maximum1/master/org/jboss/tools/tycho-plugins/repository-utils/0.0.1-SNAPSHOT/repository-utils-0.0.1-SNAPSHOT.jar
> [ERROR] urls[1] = file:/home/eskimo/Projects/jbds/jbosstools-fork-submodules/../.m2/jbosstools-fork-submodules-maximum1/master/org/codehaus/plexus/plexus-component-annotations/1.5.5/plexus-component-annotations-1.5.5.jar
> [ERROR] urls[2] = file:/home/eskimo/Projects/jbds/jbosstools-fork-submodules/../.m2/jbosstools-fork-submodules-maximum1/master/org/sonatype/sisu/sisu-inject-bean/1.4.2/sisu-inject-bean-1.4.2.jar
> [ERROR] urls[3] = file:/home/eskimo/Projects/jbds/jbosstools-fork-submodules/../.m2/jbosstools-fork-submodules-maximum1/master/org/sonatype/sisu/sisu-guice/2.1.7/sisu-guice-2.1.7-noaop.jar
> [ERROR] urls[4] = file:/home/eskimo/Projects/jbds/jbosstools-fork-submodules/../.m2/jbosstools-fork-submodules-maximum1/master/org/eclipse/tycho/tycho-packaging-plugin/0.15.0/tycho-packaging-plugin-0.15.0.jar
> [ERROR] urls[5] = file:/home/eskimo/Projects/jbds/jbosstools-fork-submodules/../.m2/jbosstools-fork-submodules-maximum1/master/org/sonatype/aether/aether-util/1.7/aether-util-1.7.jar
> [ERROR] urls[6] = file:/home/eskimo/Projects/jbds/jbosstools-fork-submodules/../.m2/jbosstools-fork-submodules-maximum1/master/org/codehaus/plexus/plexus-interpolation/1.14/plexus-interpolation-1.14.jar
> [ERROR] urls[7] = file:/home/eskimo/Projects/jbds/jbosstools-fork-submodules/../.m2/jbosstools-fork-submodules-maximum1/master/org/sonatype/plexus/plexus-sec-dispatcher/1.3/plexus-sec-dispatcher-1.3.jar
> [ERROR] urls[8] = file:/home/eskimo/Projects/jbds/jbosstools-fork-submodules/../.m2/jbosstools-fork-submodules-maximum1/master/org/sonatype/plexus/plexus-cipher/1.4/plexus-cipher-1.4.jar
> [ERROR] urls[9] = file:/home/eskimo/Projects/jbds/jbosstools-fork-submodules/../.m2/jbosstools-fork-submodules-maximum1/master/org/codehaus/plexus/plexus-utils/2.0.4/plexus-utils-2.0.4.jar
> [ERROR] urls[10] = file:/home/eskimo/Projects/jbds/jbosstools-fork-submodules/../.m2/jbosstools-fork-submodules-maximum1/master/org/apache/maven/maven-archiver/2.4/maven-archiver-2.4.jar
> [ERROR] urls[11] = file:/home/eskimo/Projects/jbds/jbosstools-fork-submodules/../.m2/jbosstools-fork-submodules-maximum1/master/org/codehaus/plexus/plexus-archiver/1.2/plexus-archiver-1.2.jar
> [ERROR] urls[12] = file:/home/eskimo/Projects/jbds/jbosstools-fork-submodules/../.m2/jbosstools-fork-submodules-maximum1/master/org/codehaus/plexus/plexus-io/1.0.1/plexus-io-1.0.1.jar
> [ERROR] urls[13] = file:/home/eskimo/Projects/jbds/jbosstools-fork-submodules/../.m2/jbosstools-fork-submodules-maximum1/master/net/sf/saxon/saxon/8.7/saxon-8.7.jar
> [ERROR] urls[14] = file:/home/eskimo/Projects/jbds/jbosstools-fork-submodules/../.m2/jbosstools-fork-submodules-maximum1/master/net/sf/saxon/saxon-dom/8.7/saxon-dom-8.7.jar
> [ERROR] Number of foreign imports: 1
> [ERROR] import: Entry[import from realm ClassRealm[project>org.jboss.tools:base:4.0.0-SNAPSHOT, parent: ClassRealm[maven.api, parent: null]]]
> [ERROR]
> [ERROR] -----------------------------------------------------: org.jboss.tools.tycho.sitegenerator.GenerateRepositoryFacadeMojo$2
> {code}
--
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
13 years, 2 months
[JBoss JIRA] (JBIDE-13459) 64 test failures in org.jboss.tools.as.test.core since switching to build w/ Kepler M4 target platform
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13459?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-13459:
-------------------------------------
Switching my dev env over immediately.
> 64 test failures in org.jboss.tools.as.test.core since switching to build w/ Kepler M4 target platform
> -------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-13459
> URL: https://issues.jboss.org/browse/JBIDE-13459
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JBossAS/Servers
> Affects Versions: 4.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Rob Stryker
> Fix For: 4.1.0.Alpha1
>
>
> {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.1_trunk.component--server/165/testReport/}
> Failing for 6 builds (age = 6):
> Test Name Duration Age
> >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[60] 3.3 sec 6
> >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[61] 2.4 sec 6
> >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[62] 2.4 sec 6
> >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[63] 2.4 sec 6
> >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[64] 2.3 sec 6
> >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[65] 2.4 sec 6
> >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[66] 2.4 sec 6
> >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[67] 2.4 sec 6
> >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[68] 2.3 sec 6
> >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[69] 2.9 sec 6
> >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[70] 2.4 sec 6
> >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[71] 2.4 sec 6
> >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[72] 2.4 sec 6
> >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[73] 2.4 sec 6
> >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[74] 2.4 sec 6
> >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[75] 2.4 sec 6
> >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[76] 2.4 sec 6
> >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[77] 2.4 sec 6
> >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[78] 2.3 sec 6
> >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[79] 2.3 sec 6
> >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[80] 2.4 sec 6
> >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[81] 2.4 sec 6
> >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[82] 2.3 sec 6
> >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[83] 2.4 sec 6
> >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[84] 2.4 sec 6
> >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[85] 2.9 sec 6
> >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[86] 2.4 sec 6
> >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[87] 2.4 sec 6
> >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[88] 2.4 sec 6
> >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[89] 2.4 sec 6
> >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[60] 3.4 sec 6
> >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[61] 4.2 sec 6
> >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[62] 3.5 sec 6
> >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[63] 4.2 sec 6
> >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[64] 3.6 sec 6
> >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[65] 3.5 sec 6
> >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[66] 4.1 sec 6
> >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[67] 3.5 sec 6
> >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[68] 3.5 sec 6
> >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[69] 4.7 sec 6
> >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[70] 3.6 sec 6
> >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[71] 3.5 sec 6
> >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[72] 4 sec 6
> >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[73] 4.2 sec 6
> >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[74] 4.2 sec 6
> >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[75] 4.1 sec 6
> >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[76] 3.6 sec 6
> >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[77] 3.6 sec 6
> >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[78] 3.6 sec 6
> >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[79] 4 sec 6
> >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[80] 3.6 sec 6
> >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[81] 3.6 sec 6
> >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[82] 3.6 sec 6
> >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[83] 3.5 sec 6
> >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[84] 3.5 sec 6
> >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[85] 3.6 sec 6
> >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[86] 4.2 sec 6
> >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[87] 3.6 sec 6
> >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[88] 4.2 sec 6
> >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[89] 3.7 sec 6
> >>> org.jboss.tools.as.test.core.parametized.server.XPathModelTest.serverTestImpl[0] 15 ms 6
> >>> org.jboss.tools.as.test.core.launch.MockArgsTests.initializationError 2 ms 6
> >>> org.jboss.tools.as.test.core.launch.MockArgsTests.initializationError 1 ms 6
> >>> org.jboss.tools.as.test.core.classpath.EJB3SupportVerifierTest.testEJB30Support[11] 20 ms 6
> {code}
--
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
13 years, 2 months
[JBoss JIRA] (JBIDE-13413) jQuery Mobile Widget Palette
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13413?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-13413:
----------------------------------
Labels: new_and_noteworthy (was: )
> jQuery Mobile Widget Palette
> ----------------------------
>
> Key: JBIDE-13413
> URL: https://issues.jboss.org/browse/JBIDE-13413
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: jsp/jsf/xml/html source editing
> Reporter: Alexey Kazakov
> Assignee: Alexey Kazakov
> Labels: new_and_noteworthy
> Fix For: 4.1.x
>
> Attachments: CSS-Preview.png, NewBlock.bmml, NewBlock.bmml, NewBlock.png, NewButton.bmml, NewButton.png, NewCheckBox.bmml, NewCheckBox.png, NewDialog.bmml, NewDialog.bmml, NewDialog.png, NewFlip.bmml, NewFlip.png, NewGrid.bmml, NewGrid.png, NewGroupedCheckBoxes.bmml, NewGroupedCheckBoxes.png, NewHeaderBar.bmml, NewHeaderBar.png, NewListview.bmml, NewListview.png, NewNavbar.bmml, NewNavbar.png, NewPage.bmml, NewPage.png, NewPopup.bmml, NewPopup.png, NewRadioButton.bmml, NewRadioButton.png, withwithoutpreview.bmml, withwithoutpreview.png
>
>
> http://jquerymobile.com/test/
> See my proposal regarding the content of jQuery Mobile palette below.
> Also I have an idea to add a live preview into each wizard.
> We could try to add a browser to the wizard which will show how the widget is going to look.
--
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
13 years, 2 months