[JBoss JIRA] (JBTIS-437) Add jsonschema2pojo to TP
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-437?page=com.atlassian.jira.plugin.... ]
Paul Leacu resolved JBTIS-437.
------------------------------
Fix Version/s: 4.3.0.Beta1c-TP
(was: 4.3.0.Final-TP)
Resolution: Done
jsonschema2pojo now referenced through the locus 1.3.0-SNAPSHOT repo
See https://issues.jboss.org/browse/LOCUS-42
> Add jsonschema2pojo to TP
> -------------------------
>
> Key: JBTIS-437
> URL: https://issues.jboss.org/browse/JBTIS-437
> Project: JBoss Tools Integration Stack
> Issue Type: Feature Request
> Components: Fuse IDE, target-platform
> Reporter: Keith Babo
> Assignee: Paul Leacu
> Fix For: 4.3.0.Beta1c-TP
>
>
> Fuse Data Transformation tooling relies on jsonschema2pojo to generate model classes from JSON schema and JSON instance documents. At present, this dependency is bundled directly inside the data transformation plugin for Fuse IDE.
> *Project page/sources:* http://www.jsonschema2pojo.org/
> *Version:* 0.4.5 (this is a bit old - current is 0.4.11 and happy to try that if we want to be on the latest/greatest)
> *License and owner:* ALv2
> *Original p2 repo:* unknown
> *JBoss mirror:* unknown
> *Include Sources:* Yes
> *Affected projects:* Fuse IDE
> *Include in JBDS:* unknown
> *Type of dependency:* unknown
> *non-p2 repository:* https://repo1.maven.org/maven2/org/jsonschema2pojo/jsonschema2pojo-core/0...
> There are additional dependencies (see the POM) beyond jsonschema2pojo that will need to be included depending on which parts of jsonschema2pojo are used. For us, that includes:
> - commons-lang3 (although we should be able to use the v2 version which is already present in the TP - need to confirm)
> - jackson-annotations.jar (2.2.0)
> - jackson-core.jar (2.2.0)
> - jackson-databind.jar (2.2.0)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBTIS-464) Add javax.validation as a transient dependency for JBTIS TP (Fuse Tooling)
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-464?page=com.atlassian.jira.plugin.... ]
Paul Leacu updated JBTIS-464:
-----------------------------
Description:
Needed dependency of jsonschema2pojo.
*Reason:* Add javax.validation as a transient dependency for JBTIS TP. Needed by Data Trans/Fuse Tooling
*Project page/sources:*
*Version:* .4.3.0.Beta1c-SNAPSHOT
*License and owner:* EPL
*Original p2 repo:*
*JBoss mirror:*
*Include Sources:* Yes
*Affected JBoss Tools components:* Fuse Tooling - Data Transformation
*Include in JBDS:* Yes (JBDSIS)
*Type of dependency:* distribution
*List of bundles added/removed:*
{code}
> javax.validation [1.0.0.GA_v201205091237]
=== Summary ===
file:///home/pleacu/git-clone/jbosstools-integration-stack/target-platform/target/target-platform-ea.target.repo contains 1 unique IUs
{code}
was:
Needed dependency of jsonschema2pojo.
*Reason:* Add javax.validation as a transient dependency for JBTIS TP. Needed by Data Trans/Fuse Tooling
*Project page/sources:*
*Version:* .4.3.0.Beta1c-SNAPSHOT
*License and owner:* EPL
*Original p2 repo:*
*JBoss mirror:*
*Include Sources:* Yes
*Affected JBoss Tools components:* Fuse Tooling - Data Transformation
*Include in JBDS:* Yes (JBDSIS)
*Type of dependency:* distribution
*List of bundles added/removed:*
{code}
suggested diff on the .target files
{code}
> Add javax.validation as a transient dependency for JBTIS TP (Fuse Tooling)
> --------------------------------------------------------------------------
>
> Key: JBTIS-464
> URL: https://issues.jboss.org/browse/JBTIS-464
> Project: JBoss Tools Integration Stack
> Issue Type: Feature Request
> Components: target-platform
> Affects Versions: 4.3.0.Beta1b-TP
> Reporter: Paul Leacu
> Assignee: Paul Leacu
>
> Needed dependency of jsonschema2pojo.
> *Reason:* Add javax.validation as a transient dependency for JBTIS TP. Needed by Data Trans/Fuse Tooling
> *Project page/sources:*
> *Version:* .4.3.0.Beta1c-SNAPSHOT
> *License and owner:* EPL
> *Original p2 repo:*
> *JBoss mirror:*
> *Include Sources:* Yes
> *Affected JBoss Tools components:* Fuse Tooling - Data Transformation
> *Include in JBDS:* Yes (JBDSIS)
> *Type of dependency:* distribution
> *List of bundles added/removed:*
> {code}
> > javax.validation [1.0.0.GA_v201205091237]
> === Summary ===
> file:///home/pleacu/git-clone/jbosstools-integration-stack/target-platform/target/target-platform-ea.target.repo contains 1 unique IUs
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-19694) Angular Explorer doesn't show anything
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19694?page=com.atlassian.jira.plugi... ]
Denis Golovin reassigned JBIDE-19694:
-------------------------------------
Assignee: Denis Golovin (was: Victor Rubezhny)
> Angular Explorer doesn't show anything
> --------------------------------------
>
> Key: JBIDE-19694
> URL: https://issues.jboss.org/browse/JBIDE-19694
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html-source-editing
> Affects Versions: 4.3.0.Alpha2
> Environment: JBDS 9.0.0.Alpha2-v20150421-1151-B25, Linux 64bit, Oracle Java 1.7
> Reporter: Vlado Pakan
> Assignee: Denis Golovin
> Priority: Blocker
> Labels: respin-b
> Fix For: 4.3.0.Beta2
>
> Attachments: empty-modules.png, filled-modules.png, tern-java-revisions.png
>
>
> # Import https://github.com/angular/angular-phonecat as New JavaScript project from existing source
> # Checkout step-12 branch of imported project
> # Open Angular Explorer
> # Open index.html file of angular-phonecat project
> ERROR: Angular Explorer is empty. It should contain angular controllers and modules
> Was working fine with JBDS 8.1.0.GA and the same project configuration
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-19694) Angular Explorer doesn't show anything
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19694?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-19694:
----------------------------------
Priority: Blocker (was: Critical)
> Angular Explorer doesn't show anything
> --------------------------------------
>
> Key: JBIDE-19694
> URL: https://issues.jboss.org/browse/JBIDE-19694
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html-source-editing
> Affects Versions: 4.3.0.Alpha2
> Environment: JBDS 9.0.0.Alpha2-v20150421-1151-B25, Linux 64bit, Oracle Java 1.7
> Reporter: Vlado Pakan
> Assignee: Victor Rubezhny
> Priority: Blocker
> Labels: respin-b
> Fix For: 4.3.0.Beta2
>
> Attachments: empty-modules.png, filled-modules.png, tern-java-revisions.png
>
>
> # Import https://github.com/angular/angular-phonecat as New JavaScript project from existing source
> # Checkout step-12 branch of imported project
> # Open Angular Explorer
> # Open index.html file of angular-phonecat project
> ERROR: Angular Explorer is empty. It should contain angular controllers and modules
> Was working fine with JBDS 8.1.0.GA and the same project configuration
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-19694) Angular Explorer doesn't show anything
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19694?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-19694:
----------------------------------
Fix Version/s: 4.3.0.Beta2
(was: 4.3.0.CR1)
> Angular Explorer doesn't show anything
> --------------------------------------
>
> Key: JBIDE-19694
> URL: https://issues.jboss.org/browse/JBIDE-19694
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html-source-editing
> Affects Versions: 4.3.0.Alpha2
> Environment: JBDS 9.0.0.Alpha2-v20150421-1151-B25, Linux 64bit, Oracle Java 1.7
> Reporter: Vlado Pakan
> Assignee: Victor Rubezhny
> Priority: Critical
> Labels: respin-b
> Fix For: 4.3.0.Beta2
>
> Attachments: empty-modules.png, filled-modules.png, tern-java-revisions.png
>
>
> # Import https://github.com/angular/angular-phonecat as New JavaScript project from existing source
> # Checkout step-12 branch of imported project
> # Open Angular Explorer
> # Open index.html file of angular-phonecat project
> ERROR: Angular Explorer is empty. It should contain angular controllers and modules
> Was working fine with JBDS 8.1.0.GA and the same project configuration
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-19694) Angular Explorer doesn't show anything
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19694?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-19694:
----------------------------------
Labels: respin-b (was: )
> Angular Explorer doesn't show anything
> --------------------------------------
>
> Key: JBIDE-19694
> URL: https://issues.jboss.org/browse/JBIDE-19694
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html-source-editing
> Affects Versions: 4.3.0.Alpha2
> Environment: JBDS 9.0.0.Alpha2-v20150421-1151-B25, Linux 64bit, Oracle Java 1.7
> Reporter: Vlado Pakan
> Assignee: Victor Rubezhny
> Priority: Critical
> Labels: respin-b
> Fix For: 4.3.0.Beta2
>
> Attachments: empty-modules.png, filled-modules.png, tern-java-revisions.png
>
>
> # Import https://github.com/angular/angular-phonecat as New JavaScript project from existing source
> # Checkout step-12 branch of imported project
> # Open Angular Explorer
> # Open index.html file of angular-phonecat project
> ERROR: Angular Explorer is empty. It should contain angular controllers and modules
> Was working fine with JBDS 8.1.0.GA and the same project configuration
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-20375) Investigate possibility of reading Download Manager data from a REST service instead of YAML
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20375?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-20375:
---------------------------------------------
Hi [~dhladky] I understand the consideration, but I don't think the loss of being able to add values/associations without changing a server, not being able to easily cache the .yml nor be able to test in isolation and not be able to add non-product downloads is worth it.
> Investigate possibility of reading Download Manager data from a REST service instead of YAML
> --------------------------------------------------------------------------------------------
>
> Key: JBIDE-20375
> URL: https://issues.jboss.org/browse/JBIDE-20375
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: build, server, updatesite, upstream, website
> Reporter: David Hladky
>
> Download Manager has a rest service, that contains information about all downloads on developers.redhat.com web page (and also many projects on www.jboss.org product pages). In the next year it will start also showing content from ITs unified Download Manager so the number of downloads it describes will become even higher.
> Because our productization team (I think [~pmuir], [~cobrien_redhat]), has to fill the information about existing downloads to many places (from what I know they must upload it to access.cdn, they must enter information about it to Download Manager, they must mention it in Yaml files, they must upload it to customer portal, some of those to Unified download manager as well...). In my opinion it is quite tedious process that we have a chance to make less complicated.
> Download manager will be a source for the product web pages and as it already contains most of the necessary information [~wesbos] is working on it an he is fairly close to this goal.
> And if we have enough information about that why not use it and replicate the information in a different process?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-20384) Need public API for internal m2e function currently used via reflection
by Brian Fitzpatrick (JIRA)
Brian Fitzpatrick created JBIDE-20384:
-----------------------------------------
Summary: Need public API for internal m2e function currently used via reflection
Key: JBIDE-20384
URL: https://issues.jboss.org/browse/JBIDE-20384
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: maven
Affects Versions: 4.3.0.Beta1
Reporter: Brian Fitzpatrick
In the SwitchYard code for m2e support we have some code that references an internal method.
This is the line causing me grief - https://github.com/jboss-switchyard/tools/blob/master/eclipse/plugins/org...
Does anybody know if this internal method has changed in the latest version of m2e for Mars? I know Rob C used the internal method for a reason, but am wondering if there's a cleaner way to do this.
It's generating this exception in my tests:
{code}
$ mvn -U clean install > build2.log
Picked up _JAVA_OPTIONS: -XX:-UseGCOverheadLimit -Xmx512m -Xmx1024m -XX:MaxMetas
paceSize=256m
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
java.lang.NoSuchMethodException: org.eclipse.m2e.core.internal.builder.plexusbuildapi.EclipseEmptyBuildContext.getFiles()
at java.lang.Class.getMethod(Class.java:1786)
at org.switchyard.tools.m2e.SwitchYardBuildParticipant.getRefreshedFiles(SwitchYardBuildParticipant.java:181)
at org.switchyard.tools.m2e.SwitchYardBuildParticipant.checkRefreshedFiles(SwitchYardBuildParticipant.java:151)
at org.switchyard.tools.m2e.SwitchYardBuildParticipant.build(SwitchYardBuildParticipant.java:97)
at org.eclipse.m2e.core.internal.builder.MavenBuilderImpl.build(MavenBuilderImpl.java:137)
at org.eclipse.m2e.core.project.configurator.AbstractLifecycleMapping.configure(AbstractLifecycleMapping.java:111)
at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$3.call(ProjectConfigurationManager.java:501)
at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$3.call(ProjectConfigurationManager.java:1)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:151)
at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:494)
at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.configureNewMavenProjects(ProjectConfigurationManager.java:281)
at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$1.call(ProjectConfigurationManager.java:168)
at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$1.call(ProjectConfigurationManager.java:1)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:151)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:99)
at org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:1355)
at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.importProjects(ProjectConfigurationManager.java:136)
at org.eclipse.m2e.tests.common.AbstractMavenProjectTestCase$4.run(AbstractMavenProjectTestCase.java:371)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2241)
at org.eclipse.m2e.tests.common.AbstractMavenProjectTestCase.importProjects(AbstractMavenProjectTestCase.java:369)
at org.eclipse.m2e.tests.common.AbstractMavenProjectTestCase.importProjects(AbstractMavenProjectTestCase.java:344)
at org.eclipse.m2e.tests.common.AbstractMavenProjectTestCase.importProject(AbstractMavenProjectTestCase.java:331)
at org.switchyard.tools.m2e.tests.SwitchYardConfigurationTest.runProjectTest(SwitchYardConfigurationTest.java:59)
at org.switchyard.tools.m2e.tests.SwitchYardConfigurationTest.testBeanServiceQuickstart(SwitchYardConfigurationTest.java:42)
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:497)
at junit.framework.TestCase.runTest(TestCase.java:176)
at org.eclipse.m2e.tests.common.AbstractMavenProjectTestCase.runTest(AbstractMavenProjectTestCase.java:576)
at junit.framework.TestCase.runBare(TestCase.java:141)
at junit.framework.TestResult$1.protect(TestResult.java:122)
at junit.framework.TestResult.runProtected(TestResult.java:142)
at junit.framework.TestResult.run(TestResult.java:125)
at junit.framework.TestCase.run(TestCase.java:129)
at junit.framework.TestSuite.runTest(TestSuite.java:252)
at junit.framework.TestSuite.run(TestSuite.java:247)
at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86)
at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264)
at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153)
at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124)
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:497)
at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray2(ReflectionUtils.java:208)
at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:156)
at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:82)
at org.eclipse.tycho.surefire.osgibooter.OsgiSurefireBooter.run(OsgiSurefireBooter.java:91)
at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication$1.run(AbstractUITestApplication.java:35)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4155)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3772)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139)
at org.eclipse.tycho.surefire.osgibooter.UITestApplication.runApplication(UITestApplication.java:31)
at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication.run(AbstractUITestApplication.java:120)
at org.eclipse.tycho.surefire.osgibooter.UITestApplication.start(UITestApplication.java:37)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
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:497)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)
at org.eclipse.equinox.launcher.Main.run(Main.java:1515)
at org.eclipse.equinox.launcher.Main.main(Main.java:1488)
{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-20384) Need public API for internal m2e function currently used via reflection
by Brian Fitzpatrick (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20384?page=com.atlassian.jira.plugi... ]
Brian Fitzpatrick reassigned JBIDE-20384:
-----------------------------------------
Assignee: Fred Bricon
> Need public API for internal m2e function currently used via reflection
> -----------------------------------------------------------------------
>
> Key: JBIDE-20384
> URL: https://issues.jboss.org/browse/JBIDE-20384
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven
> Affects Versions: 4.3.0.Beta1
> Reporter: Brian Fitzpatrick
> Assignee: Fred Bricon
>
> In the SwitchYard code for m2e support we have some code that references an internal method.
> This is the line causing me grief - https://github.com/jboss-switchyard/tools/blob/master/eclipse/plugins/org...
> Does anybody know if this internal method has changed in the latest version of m2e for Mars? I know Rob C used the internal method for a reason, but am wondering if there's a cleaner way to do this.
> It's generating this exception in my tests:
> {code}
> $ mvn -U clean install > build2.log
> Picked up _JAVA_OPTIONS: -XX:-UseGCOverheadLimit -Xmx512m -Xmx1024m -XX:MaxMetas
> paceSize=256m
> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
> SLF4J: Defaulting to no-operation (NOP) logger implementation
> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
> java.lang.NoSuchMethodException: org.eclipse.m2e.core.internal.builder.plexusbuildapi.EclipseEmptyBuildContext.getFiles()
> at java.lang.Class.getMethod(Class.java:1786)
> at org.switchyard.tools.m2e.SwitchYardBuildParticipant.getRefreshedFiles(SwitchYardBuildParticipant.java:181)
> at org.switchyard.tools.m2e.SwitchYardBuildParticipant.checkRefreshedFiles(SwitchYardBuildParticipant.java:151)
> at org.switchyard.tools.m2e.SwitchYardBuildParticipant.build(SwitchYardBuildParticipant.java:97)
> at org.eclipse.m2e.core.internal.builder.MavenBuilderImpl.build(MavenBuilderImpl.java:137)
> at org.eclipse.m2e.core.project.configurator.AbstractLifecycleMapping.configure(AbstractLifecycleMapping.java:111)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$3.call(ProjectConfigurationManager.java:501)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$3.call(ProjectConfigurationManager.java:1)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:151)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:494)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.configureNewMavenProjects(ProjectConfigurationManager.java:281)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$1.call(ProjectConfigurationManager.java:168)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$1.call(ProjectConfigurationManager.java:1)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:151)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:99)
> at org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:1355)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.importProjects(ProjectConfigurationManager.java:136)
> at org.eclipse.m2e.tests.common.AbstractMavenProjectTestCase$4.run(AbstractMavenProjectTestCase.java:371)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2241)
> at org.eclipse.m2e.tests.common.AbstractMavenProjectTestCase.importProjects(AbstractMavenProjectTestCase.java:369)
> at org.eclipse.m2e.tests.common.AbstractMavenProjectTestCase.importProjects(AbstractMavenProjectTestCase.java:344)
> at org.eclipse.m2e.tests.common.AbstractMavenProjectTestCase.importProject(AbstractMavenProjectTestCase.java:331)
> at org.switchyard.tools.m2e.tests.SwitchYardConfigurationTest.runProjectTest(SwitchYardConfigurationTest.java:59)
> at org.switchyard.tools.m2e.tests.SwitchYardConfigurationTest.testBeanServiceQuickstart(SwitchYardConfigurationTest.java:42)
> 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:497)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at org.eclipse.m2e.tests.common.AbstractMavenProjectTestCase.runTest(AbstractMavenProjectTestCase.java:576)
> at junit.framework.TestCase.runBare(TestCase.java:141)
> at junit.framework.TestResult$1.protect(TestResult.java:122)
> at junit.framework.TestResult.runProtected(TestResult.java:142)
> at junit.framework.TestResult.run(TestResult.java:125)
> at junit.framework.TestCase.run(TestCase.java:129)
> at junit.framework.TestSuite.runTest(TestSuite.java:252)
> at junit.framework.TestSuite.run(TestSuite.java:247)
> at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86)
> at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124)
> 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:497)
> at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray2(ReflectionUtils.java:208)
> at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:156)
> at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:82)
> at org.eclipse.tycho.surefire.osgibooter.OsgiSurefireBooter.run(OsgiSurefireBooter.java:91)
> at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication$1.run(AbstractUITestApplication.java:35)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4155)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3772)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139)
> at org.eclipse.tycho.surefire.osgibooter.UITestApplication.runApplication(UITestApplication.java:31)
> at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication.run(AbstractUITestApplication.java:120)
> at org.eclipse.tycho.surefire.osgibooter.UITestApplication.start(UITestApplication.java:37)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
> 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:497)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1515)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1488)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months