[JBoss JIRA] (JBIDE-18010) For JBIDE 4.2.0.CR1: Ensure copyrights and provider names are correct in all plugins and features
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-18010:
----------------------------------
Summary: For JBIDE 4.2.0.CR1: Ensure copyrights and provider names are correct in all plugins and features
Key: JBIDE-18010
URL: https://issues.jboss.org/browse/JBIDE-18010
Project: Tools (JBoss Tools)
Issue Type: Task
Components: build
Reporter: Nick Boldt
Priority: Blocker
Fix For: 4.2.0.CR1
For JBIDE 4.2.0.CR1: Please perform the following *2* tasks:
1. Verify that all your plugin and feature copyright dates end in 2014, and that the copyright holder is *{color:red}Red Hat, Inc.{color}* or a variation similar to the examples below.
Be sure to also include *translated* files, where they exist.
*java files*
{code:title=*.java}
Copyright (c) 2010-2014 Red Hat, Inc. and others.
{code}
*html files*
{code:title=about.html}
© 2014 Red Hat, Inc. All rights reserved
{code}
*properties files*
{code:title=about.properties}
Copyright (c) Red Hat, Inc., contributors and others 2004 - 2014. All rights reserved
{code}
{code:title=about_fr.properties}
Copyright (c) Red Hat, Inc., contributors and others 2004 - 2014. Tous droits r\u00E9serv\u00E9s.
{code}
{code:title=feature.properties}
Copyright (c) 2010-2014 Red Hat, Inc. and others.
{code}
{code:title=Messages.properties}
# Copyright (c) 2014 Red Hat, Inc. and others.
{code}
*xsd files*
{code:title=jboss-as-naming_1_3.xsd}
Copyright 2014, Red Hat, Inc., and individual contributors
{code}
2. Verify that all your plugin and feature provider names are *{color:red}JBoss by Red Hat{color}*.
Be sure to also include *translated* files, where they exist.
*This step is particularly important for new plugins and features that have been added recently.*
Depending on how your plugin is configured you should see something like this in your *plugin.properties* files:
{code}BundleName = JMX Resources Bundle
BundleProvider = JBoss by Red Hat{code}
or
{code}Bundle-Name.0 = JBossTools Archives Core Plugin
Bundle-Vendor.0 = JBoss by Red Hat{code}
Then in your MANIFEST.MF files, you will reference these variables like this.
*Bundle-Localization* is required or your plugin won't see the values in your *plugin.properties* file!
{code}Bundle-Localization: plugin
Bundle-Name: %BundleName
Bundle-Vendor: %BundleProvider{code}
or
{code}Bundle-Localization: plugin
Bundle-Name: %Bundle-Name.0
Bundle-Vendor: %Bundle-Vendor.0{code}
For features, check that your *feature.properties* file contains good values too:
{code}featureName=JMX Console
featureProvider=JBoss by Red Hat{code}
or
{code}featureName=JBoss Archives Tools
providerName=JBoss by Red Hat{code}
Then in your feature.xml files, you will reference these variables like this:
{code}<feature label="%featureName" provider-name="%featureProvider" ...>{code}
or
{code}<feature label="%featureName" provider-name="%providerName" ...>{code}
3. If you would like QE to review your changes, please *Resolve* this JIRA when done.
4. If you do not require QE to review your changes, please *Close* this JIRA when done.
5. If you have any questions, please contact [~nickboldt].
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
See also: JBDS-3114
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBIDE-15884) Allow the runBrowserSim command to accept a URL as a parameter
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15884?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov updated JBIDE-15884:
-------------------------------------------
Assignee: Ilya Buziuk (was: Konstantin Marmalyukov)
> Allow the runBrowserSim command to accept a URL as a parameter
> --------------------------------------------------------------
>
> Key: JBIDE-15884
> URL: https://issues.jboss.org/browse/JBIDE-15884
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: browsersim
> Affects Versions: 4.1.0.Final
> Reporter: Vineet Reynolds
> Assignee: Ilya Buziuk
> Priority: Minor
> Fix For: 4.2.0.CR1
>
>
> Apologies for not setting the Affect version; I'm not sure which JBIDE version is affected.
> When creating a cheatsheet in JBDS 7.0.1.GA (for JDF-497), I'm using the {{org.jboss.tools.vpe.browsersim.eclipse.commands.runBrowserSim}} command in the cheatsheet. This launches BrowserSim successfully (when I'm in the correct perspective). However, BrowserSim navigates to about:blank so the cheatsheet requires users to manually key in the URL. It would be nice to have the launch URL specified as a configurable value.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBIDE-17881) Publishing jobs are hanging in Progress view and in bottom right corner.
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17881?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-17881:
-------------------------------------
Estimated Difficulty: Medium
> Publishing jobs are hanging in Progress view and in bottom right corner.
> ------------------------------------------------------------------------
>
> Key: JBIDE-17881
> URL: https://issues.jboss.org/browse/JBIDE-17881
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.Beta3
> Reporter: Marián Labuda
> Priority: Critical
> Fix For: 4.2.0.CR1
>
> Attachments: finished_job.png, hanging_finished_job.png
>
>
> Publishing jobs are shown in Progress view. In previous versions they were removed from this view after finishing the job. Now they are still hanging there with status "Finished" and after removal and reopen Progress view they are still here. Instead of reopen view also Remove all Finished Jobs (double gray crosses in view) works fine too.
> !finished_job.png!
> Running job is also shown in bottom right corner. After finishing it is still hanging there.
> !hanging_finished_job.png!
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBIDE-17881) Publishing jobs are hanging in Progress view and in bottom right corner.
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17881?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-17881:
---------------------------------------------
bumping to critical since you as a user have no idea if your app is actually published or not.
> Publishing jobs are hanging in Progress view and in bottom right corner.
> ------------------------------------------------------------------------
>
> Key: JBIDE-17881
> URL: https://issues.jboss.org/browse/JBIDE-17881
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.Beta3
> Reporter: Marián Labuda
> Priority: Critical
> Fix For: 4.2.0.CR1
>
> Attachments: finished_job.png, hanging_finished_job.png
>
>
> Publishing jobs are shown in Progress view. In previous versions they were removed from this view after finishing the job. Now they are still hanging there with status "Finished" and after removal and reopen Progress view they are still here. Instead of reopen view also Remove all Finished Jobs (double gray crosses in view) works fine too.
> !finished_job.png!
> Running job is also shown in bottom right corner. After finishing it is still hanging there.
> !hanging_finished_job.png!
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBIDE-17881) Publishing jobs are hanging in Progress view and in bottom right corner.
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17881?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-17881:
----------------------------------------
Priority: Critical (was: Major)
> Publishing jobs are hanging in Progress view and in bottom right corner.
> ------------------------------------------------------------------------
>
> Key: JBIDE-17881
> URL: https://issues.jboss.org/browse/JBIDE-17881
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.Beta3
> Reporter: Marián Labuda
> Priority: Critical
> Fix For: 4.2.0.CR1
>
> Attachments: finished_job.png, hanging_finished_job.png
>
>
> Publishing jobs are shown in Progress view. In previous versions they were removed from this view after finishing the job. Now they are still hanging there with status "Finished" and after removal and reopen Progress view they are still here. Instead of reopen view also Remove all Finished Jobs (double gray crosses in view) works fine too.
> !finished_job.png!
> Running job is also shown in bottom right corner. After finishing it is still hanging there.
> !hanging_finished_job.png!
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBIDE-17498) Can't run default hybrid project on device
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17498?page=com.atlassian.jira.plugi... ]
Gorkem Ercan commented on JBIDE-17498:
--------------------------------------
[~ibuziuk] are you able to reproduce this constantly also on Beta3? I have not been able to so far.
> Can't run default hybrid project on device
> ------------------------------------------
>
> Key: JBIDE-17498
> URL: https://issues.jboss.org/browse/JBIDE-17498
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.2.0.Beta1
> Environment: windows
> Reporter: Ilya Buziuk
> Assignee: Gorkem Ercan
> Fix For: 4.2.0.CR1
>
>
> After choosing *Run As.. -> Run on Android Device* getting exception:
> {code}
> !ENTRY org.eclipse.ant.launching 4 0 2014-06-02 13:03:42.618
> !MESSAGE Ant Build Failed
> !STACK 1
> org.eclipse.core.runtime.CoreException: E:\AllEclipses\Installations\ADT\adt-bundle-windows-x86-20140321\sdk\tools\ant\build.xml:397: Problem: failed to create task or type checkenv
> Cause: The name is undefined.
> Action: Check the spelling.
> Action: Check that any custom tasks/types have been declared.
> Action: Check that any <presetdef>/<macrodef> declarations have taken place.
> at org.eclipse.ant.core.AntRunner.handleInvocationTargetException(AntRunner.java:448)
> at org.eclipse.ant.core.AntRunner.run(AntRunner.java:380)
> at org.eclipse.ant.internal.launching.launchConfigurations.AntLaunchDelegate.runInSameVM(AntLaunchDelegate.java:265)
> at org.eclipse.ant.internal.launching.launchConfigurations.AntLaunchDelegate.launch(AntLaunchDelegate.java:224)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:884)
> at org.jboss.tools.aerogear.hybrid.android.core.adt.BuildDelegate.doBuildProject(BuildDelegate.java:97)
> at org.jboss.tools.aerogear.hybrid.android.core.adt.BuildDelegate.buildProject(BuildDelegate.java:58)
> at org.jboss.tools.aerogear.hybrid.android.core.adt.BuildDelegate.buildNow(BuildDelegate.java:53)
> at org.jboss.tools.aerogear.hybrid.android.core.adt.AndroidLaunchDelegate.buildForLaunch(AndroidLaunchDelegate.java:77)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:852)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039)
> at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> Caused by: E:\AllEclipses\Installations\ADT\adt-bundle-windows-x86-20140321\sdk\tools\ant\build.xml:397: Problem: failed to create task or type checkenv
> Cause: The name is undefined.
> Action: Check the spelling.
> Action: Check that any custom tasks/types have been declared.
> Action: Check that any <presetdef>/<macrodef> declarations have taken place.
> at org.apache.tools.ant.UnknownElement.getNotFoundException(UnknownElement.java:499)
> at org.apache.tools.ant.UnknownElement.makeObject(UnknownElement.java:431)
> at org.apache.tools.ant.UnknownElement.maybeConfigure(UnknownElement.java:163)
> at org.apache.tools.ant.Task.perform(Task.java:347)
> at org.apache.tools.ant.Target.execute(Target.java:435)
> at org.apache.tools.ant.Target.performTasks(Target.java:456)
> at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1393)
> at org.apache.tools.ant.Project.executeTarget(Project.java:1364)
> at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
> at org.eclipse.ant.internal.core.ant.EclipseDefaultExecutor.executeTargets(EclipseDefaultExecutor.java:36)
> at org.apache.tools.ant.Project.executeTargets(Project.java:1248)
> at org.eclipse.ant.internal.core.ant.InternalAntRunner.run(InternalAntRunner.java:703)
> at org.eclipse.ant.internal.core.ant.InternalAntRunner.run(InternalAntRunner.java:525)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:483)
> at org.eclipse.ant.core.AntRunner.run(AntRunner.java:371)
> ... 12 more
> !SUBENTRY 1 org.eclipse.ant.core 4 1 2014-06-02 13:03:42.618
> !MESSAGE E:\AllEclipses\Installations\ADT\adt-bundle-windows-x86-20140321\sdk\tools\ant\build.xml:397: Problem: failed to create task or type checkenv
> Cause: The name is undefined.
> Action: Check the spelling.
> Action: Check that any custom tasks/types have been declared.
> Action: Check that any <presetdef>/<macrodef> declarations have taken place.
> !STACK 0
> E:\AllEclipses\Installations\ADT\adt-bundle-windows-x86-20140321\sdk\tools\ant\build.xml:397: Problem: failed to create task or type checkenv
> Cause: The name is undefined.
> Action: Check the spelling.
> Action: Check that any custom tasks/types have been declared.
> Action: Check that any <presetdef>/<macrodef> declarations have taken place.
> at org.apache.tools.ant.UnknownElement.getNotFoundException(UnknownElement.java:499)
> at org.apache.tools.ant.UnknownElement.makeObject(UnknownElement.java:431)
> at org.apache.tools.ant.UnknownElement.maybeConfigure(UnknownElement.java:163)
> at org.apache.tools.ant.Task.perform(Task.java:347)
> at org.apache.tools.ant.Target.execute(Target.java:435)
> at org.apache.tools.ant.Target.performTasks(Target.java:456)
> at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1393)
> at org.apache.tools.ant.Project.executeTarget(Project.java:1364)
> at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
> at org.eclipse.ant.internal.core.ant.EclipseDefaultExecutor.executeTargets(EclipseDefaultExecutor.java:36)
> at org.apache.tools.ant.Project.executeTargets(Project.java:1248)
> at org.eclipse.ant.internal.core.ant.InternalAntRunner.run(InternalAntRunner.java:703)
> at org.eclipse.ant.internal.core.ant.InternalAntRunner.run(InternalAntRunner.java:525)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:483)
> at org.eclipse.ant.core.AntRunner.run(AntRunner.java:371)
> at org.eclipse.ant.internal.launching.launchConfigurations.AntLaunchDelegate.runInSameVM(AntLaunchDelegate.java:265)
> at org.eclipse.ant.internal.launching.launchConfigurations.AntLaunchDelegate.launch(AntLaunchDelegate.java:224)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:884)
> at org.jboss.tools.aerogear.hybrid.android.core.adt.BuildDelegate.doBuildProject(BuildDelegate.java:97)
> at org.jboss.tools.aerogear.hybrid.android.core.adt.BuildDelegate.buildProject(BuildDelegate.java:58)
> at org.jboss.tools.aerogear.hybrid.android.core.adt.BuildDelegate.buildNow(BuildDelegate.java:53)
> at org.jboss.tools.aerogear.hybrid.android.core.adt.AndroidLaunchDelegate.buildForLaunch(AndroidLaunchDelegate.java:77)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:852)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039)
> at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> !ENTRY org.jboss.tools.aerogear.hybrid.android.core 4 0 2014-06-02 13:03:42.620
> !MESSAGE Build failed... Build artifact does not exist
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBIDE-17830) ResourceException: Resource '<projectName>/plugins' does not exist
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17830?page=com.atlassian.jira.plugi... ]
Gorkem Ercan resolved JBIDE-17830.
----------------------------------
Resolution: Done
Fixed on upstream
> ResourceException: Resource '<projectName>/plugins' does not exist
> ------------------------------------------------------------------
>
> Key: JBIDE-17830
> URL: https://issues.jboss.org/browse/JBIDE-17830
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.2.0.CR1
> Reporter: Alexey Kazakov
> Assignee: Gorkem Ercan
> Priority: Critical
> Fix For: 4.2.0.CR1
>
>
> I cloned and imported https://github.com/sebastienblanc/testionic
> Every time I run Eclipse I see the following exception in the log:
> {code}
> org.eclipse.core.internal.resources.ResourceException: Resource '/testionic/plugins' does not exist.
> at org.eclipse.core.internal.resources.Resource.checkExists(Resource.java:341)
> at org.eclipse.core.internal.resources.Resource.checkAccessible(Resource.java:215)
> at org.eclipse.core.internal.resources.Resource.accept(Resource.java:136)
> at org.eclipse.core.internal.resources.Resource.accept(Resource.java:115)
> at org.jboss.tools.aerogear.hybrid.core.plugin.CordovaPluginManager.updatePluginList(CordovaPluginManager.java:428)
> at org.jboss.tools.aerogear.hybrid.core.plugin.CordovaPluginManager.getInstalledPlugins(CordovaPluginManager.java:271)
> at org.jboss.tools.aerogear.hybrid.core.plugin.CordovaPluginManager.getCordovaPluginJSContent(CordovaPluginManager.java:300)
> at org.jboss.tools.aerogear.hybrid.core.internal.libraries.CordovaLibraryJsContainerInitializer.getPluginJsIncludePathEntry(CordovaLibraryJsContainerInitializer.java:99)
> at org.jboss.tools.aerogear.hybrid.core.internal.libraries.CordovaLibraryJsContainerInitializer.getIncludepathEntries(CordovaLibraryJsContainerInitializer.java:84)
> at org.eclipse.wst.jsdt.internal.core.JavaProject.resolveClasspath(JavaProject.java:2753)
> at org.eclipse.wst.jsdt.internal.core.ClasspathChange.generateDelta(ClasspathChange.java:206)
> at org.eclipse.wst.jsdt.internal.core.DeltaProcessor.resourceChanged(DeltaProcessor.java:1909)
> at org.eclipse.wst.jsdt.internal.core.DeltaProcessingState.resourceChanged(DeltaProcessingState.java:389)
> at org.eclipse.core.internal.events.NotificationManager$1.run(NotificationManager.java:291)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.NotificationManager.notify(NotificationManager.java:285)
> at org.eclipse.core.internal.events.NotificationManager.broadcastChanges(NotificationManager.java:149)
> at org.eclipse.core.internal.resources.Workspace.broadcastPostChange(Workspace.java:378)
> at org.eclipse.core.internal.resources.Workspace.endOperation(Workspace.java:1498)
> at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:156)
> at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBIDE-18008) Nested jars prevent SonarQube/FindBugs from running
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18008?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-18008:
----------------------------------------
Will you have the opportunity to get rid of this use-case soon? Changing packages is something that would be doable for CR1 (if it works).
> Nested jars prevent SonarQube/FindBugs from running
> ---------------------------------------------------
>
> Key: JBIDE-18008
> URL: https://issues.jboss.org/browse/JBIDE-18008
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: archives
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Fix For: 4.2.0.CR1
>
>
> Bundle org.jboss.ide.eclipse.archives.core makes SonarQube analysis fail because it's classes get included in some nested jar (and get to different location that target/classes).
> Cf https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
> {code}
> [ERROR] Failed to execute goal org.codehaus.mojo:sonar-maven-plugin:2.4:sonar (default-cli) on project server.all: Can not execute SonarQube analysis: Can not execute Findbugs: Findbugs needs sources to be compiled. Please build project before executing sonar and check the location of compiled classes. -> [Help 1]
> {code}
> This is an exploded bundles with nested jars, we should investigate whether it's possible to turn it into a more standard jar, which would still be usable in its Ant version. Cf ./archives/tests/org.jboss.ide.eclipse.archives.test/inputs/projects/SimpleAntTest
> Also, the jvmmonitor bundles use nested jars. We should avoid that too.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBIDE-18008) Nested jars prevent SonarQube/FindBugs from running
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18008?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-18008:
-------------------------------------
1) create java project, add some folders and files and junk
2) Show view -> project archives
3) select project, right-click, new archive
4) fill in all required info
5) do optional additional stuff, like add folders inside your archive, or nested archives, or filesets
6) .packages file exists
I would honestly suggest NOT changing the packaging here. Seriously. If I can get rid of, or deprecate, the external ant usecase, I can turn this into a standard plugin which would automatically simplify the plugin structure. I feel you're just duplicating effort.
> Nested jars prevent SonarQube/FindBugs from running
> ---------------------------------------------------
>
> Key: JBIDE-18008
> URL: https://issues.jboss.org/browse/JBIDE-18008
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: archives
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Fix For: 4.2.0.CR1
>
>
> Bundle org.jboss.ide.eclipse.archives.core makes SonarQube analysis fail because it's classes get included in some nested jar (and get to different location that target/classes).
> Cf https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
> {code}
> [ERROR] Failed to execute goal org.codehaus.mojo:sonar-maven-plugin:2.4:sonar (default-cli) on project server.all: Can not execute SonarQube analysis: Can not execute Findbugs: Findbugs needs sources to be compiled. Please build project before executing sonar and check the location of compiled classes. -> [Help 1]
> {code}
> This is an exploded bundles with nested jars, we should investigate whether it's possible to turn it into a more standard jar, which would still be usable in its Ant version. Cf ./archives/tests/org.jboss.ide.eclipse.archives.test/inputs/projects/SimpleAntTest
> Also, the jvmmonitor bundles use nested jars. We should avoid that too.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months