June 2016 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-2457) Broken Link in the Forge from scratch quickstart page

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2457?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-2457. ---------------------------------- Resolution: Out of Date > Broken Link in the Forge from scratch quickstart page > ----------------------------------------------------- > > Key: FORGE-2457 > URL: https://issues.jboss.org/browse/FORGE-2457 > Project: Forge > Issue Type: Bug > Reporter: Daniel Coughlin > > https://www.dropbox.com/s/opxabfe1sq2so1f/jboss-eap-quickstarts_forge-fro... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2508) No compiler is provided in this environment. Perhaps you are running on a JRE rather than a JDK?

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2508?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-2508. ---------------------------------- Resolution: Cannot Reproduce Bug Closing it as cannot reproduce. Please reopen if problem still persists > No compiler is provided in this environment. Perhaps you are running on a JRE rather than a JDK? > ------------------------------------------------------------------------------------------------ > > Key: FORGE-2508 > URL: https://issues.jboss.org/browse/FORGE-2508 > Project: Forge > Issue Type: Quality Risk > Components: Build Tools - Maven > Affects Versions: 2.20.0.Final > Reporter: Ashish Aggarwal > > while installing angular js addon for forge i am getting below error :- > [SEVERE] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.2:compile (default-compile) on project angularjs: Compilation failure > [SEVERE] No compiler is provided in this environment. Perhaps you are running on a JRE rather than a JDK? > [SEVERE] -> [Help 1] > [SEVERE] > [SEVERE] To see the full stack trace of the errors, re-run Maven with the -e switch. > [SEVERE] Re-run Maven using the -X switch to enable full debug logging. > [SEVERE] > [SEVERE] For more information about the errors and possible solutions, please read the following articles: > [SEVERE] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException > ***ERROR*** Error while executing 'addon-install-from-git' > ***INFO*** (type "export VERBOSE=true" to enable stack traces) > ***ERROR*** Unable to execute project build > [PracticeSession15Sep2015]$ addon-install-from-git --url https://github.com/forge/angularjs-addon.git > ***INFO*** Installing Addon from Git [1/4] ... > ***INFO*** Installing Addon from Git:Cloning repository in C:\Users\Ash\AppData\Local\Temp\tmpdir2956571090541956900 [1/4] ... > ***INFO*** Installing Addon from Git:Installing project into local repository [2/4] ... > [INFO] Scanning for projects... > [INFO] > [INFO] ------------------------------------------------------------------------ > [INFO] Building angularjs 2.1.6-SNAPSHOT > [INFO] ------------------------------------------------------------------------ > [INFO] > [INFO] --- maven-clean-plugin:2.6.1:clean (default-clean) @ angularjs --- > [INFO] > [INFO] --- maven-enforcer-plugin:1.3.1:enforce (enforce-java-version) @ angularjs --- > [INFO] > [INFO] --- maven-enforcer-plugin:1.3.1:enforce (enforce-maven-version) @ angularjs --- > [INFO] > [INFO] --- buildnumber-maven-plugin:1.3:create-timestamp (get-build-timestamp) @ angularjs --- > [INFO] > [INFO] --- buildnumber-maven-plugin:1.3:create (get-scm-revision) @ angularjs --- > [INFO] Executing: cmd.exe /X /C "git rev-parse --verify HEAD" > [INFO] Working directory: C:\Users\Ash\AppData\Local\Temp\tmpdir2956571090541956900 > [INFO] Storing buildNumber: 3e2248593380b724e205d2ab59e6fe307c037c2d at timestamp: 1445453834156 > [INFO] Storing buildScmBranch: master > [INFO] > [INFO] --- maven-resources-plugin:2.7:resources (default-resources) @ angularjs --- > [INFO] Using 'UTF-8' encoding to copy filtered resources. > [INFO] Copying 42 resources > [INFO] > [INFO] --- maven-compiler-plugin:3.2:compile (default-compile) @ angularjs --- > [INFO] Changes detected - recompiling the module! > [INFO] Compiling 15 source files to C:\Users\Ash\AppData\Local\Temp\tmpdir2956571090541956900\target\classes > [INFO] ------------------------------------------------------------- > [SEVERE] COMPILATION ERROR : > [INFO] ------------------------------------------------------------- > [SEVERE] No compiler is provided in this environment. Perhaps you are running on a JRE rather than a JDK? > [INFO] 1 error > [INFO] ------------------------------------------------------------- > [INFO] ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 7.113 s > [INFO] Finished at: 2015-10-21T11:57:17-07:00 > [INFO] Final Memory: 162M/398M > [INFO] ------------------------------------------------------------------------ > [SEVERE] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.2:compile (default-compile) on project angularjs: Compilation failure > [SEVERE] No compiler is provided in this environment. Perhaps you are running on a JRE rather than a JDK? > [SEVERE] -> [Help 1] > [SEVERE] > [SEVERE] To see the full stack trace of the errors, re-run Maven with the -e switch. > [SEVERE] Re-run Maven using the -X switch to enable full debug logging. > [SEVERE] > [SEVERE] For more information about the errors and possible solutions, please read the following articles: > [SEVERE] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException > ***ERROR*** Error while executing 'addon-install-from-git' > ***INFO*** (type "export VERBOSE=true" to enable stack traces) > ***ERROR*** Unable to execute project build > [PracticeSession15Sep2015]$ -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1093) Unit tests should not require "clean install" goals be set for build to succeed with dynamic versions

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1093?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1093. ---------------------------------- Fix Version/s: 3.0.0.Final (was: 3.x Future) Resolution: Done ClasspathWorkspaceReader seems to do the job > Unit tests should not require "clean install" goals be set for build to succeed with dynamic versions > ----------------------------------------------------------------------------------------------------- > > Key: FORGE-1093 > URL: https://issues.jboss.org/browse/FORGE-1093 > Project: Forge > Issue Type: Bug > Components: Forge Build > Affects Versions: 2.0.0.Alpha10 > Reporter: Lincoln Baxter III > Fix For: 3.0.0.Final > > > See FORGE-1045 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-991) Create a plugin/addon repository application for Forge

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-991?page=com.atlassian.jira.plugin.... ] George Gastaldi closed FORGE-991. --------------------------------- Fix Version/s: (was: 3.x Future) Resolution: Done http://forge.jboss.org/addons > Create a plugin/addon repository application for Forge > ------------------------------------------------------ > > Key: FORGE-991 > URL: https://issues.jboss.org/browse/FORGE-991 > Project: Forge > Issue Type: Feature Request > Components: Plugin Repository > Reporter: George Gastaldi > > From [~dan.j.allen]: > {quote} > I know that Forge has a plugin repository, but there's always room for new ideas. > The jQuery foundation recently rebooted their plugin registry to drive all contributions to it out of git. I thought you might be interested in reviewing how they set it up and see if any ideas might apply to Forge plugin registry, both in terms of how a plugin is registered and plugin discovery. > Announcement: > http://blog.jquery.com/2013/01/16/announcing-the-jquery-plugin-registry/ > Plugin Registry: > http://plugins.jquery.com/ > GitHub repo: > https://github.com/jquery/plugins.jquery.com > As they put it: > "The goal is to make sharing and browsing quality jQuery plugins a pleasant experience for everyone!" > Replace jQuery w/ Forge and we have the same goal. > {quote} > {quote} > Oh, and one more thing. I think this is the killer feature: > "To register and publish your plugin, you’ll need to push your code to a public repository on GitHub, and add our post-recieve webhook URL (http://plugins.jquery.com/postreceive-hook) to your repository. The next time you push a semver tag, we’ll take care of registering the plugin name and updating its page on the site. When you’re ready to release the next version of your plugin, just tag and push again!" > {quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1302) Provide Eclipse CheatSheets as a quickstart for some Forge plugins

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1302?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1302. ---------------------------------- Fix Version/s: (was: 3.x Future) Resolution: Won't Do That's up to the addon developer > Provide Eclipse CheatSheets as a quickstart for some Forge plugins > ------------------------------------------------------------------ > > Key: FORGE-1302 > URL: https://issues.jboss.org/browse/FORGE-1302 > Project: Forge > Issue Type: Feature Request > Components: Brainstorming, UI - Eclipse > Affects Versions: 2.0.0.Alpha14 > Reporter: George Gastaldi > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1286) Support auto-update feature in Forge 2

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1286?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1286. ---------------------------------- Fix Version/s: 3.0.0.Final (was: 3.x Future) Resolution: Done > Support auto-update feature in Forge 2 > -------------------------------------- > > Key: FORGE-1286 > URL: https://issues.jboss.org/browse/FORGE-1286 > Project: Forge > Issue Type: Feature Request > Components: Builtin Plugins, Forge Build, Usability > Affects Versions: 2.0.0.Alpha14 > Reporter: Lincoln Baxter III > Fix For: 3.0.0.Final > > > This should allow searching for new versions of selected addons (or all addons) and either asking to update each one, or doing the update as a batch job -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1691) Create JavaCompiledResource to support Roaster class file parsing

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1691?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1691. ---------------------------------- Resolution: Won't Do Roaster works only on Java Source files. No plans to support compiled classes so far. > Create JavaCompiledResource to support Roaster class file parsing > ------------------------------------------------------------------ > > Key: FORGE-1691 > URL: https://issues.jboss.org/browse/FORGE-1691 > Project: Forge > Issue Type: Feature Request > Components: Parsers / File Manipulation > Affects Versions: 2.2.0.Final > Reporter: Lincoln Baxter III > Fix For: 3.x Future > > > lincolnthree, here is the final JavaResource interface: http://paste2.org/cIKJ48Hm > lincolnthree > 6:08 gastaldi: why accept javasource and return T extends javatype? > gastaldi > 6:09 because JavaSource is a Source and JavaType can be anything > 6:09 hmm > 6:09 yeah, that's weird > 6:09 a JavaType should allow its contents to be saved > 6:10 even if it's a binary one > lincolnthree > 6:10 gastaldi: ah makes sense! > 6:10 very good > mbenson > 6:11 but then does a JavaResource *not* necessarily correspond to a .java file? > gastaldi > 6:12 now it can correspond to a .class file > 6:12 also > 6:12 hmmm > 6:13 perhaps we should have a JavaBinaryResource instead > lincolnthree > 6:13 yeah probably > gastaldi > 6:13 JavaCompiledResource > lincolnthree > 6:13 +1 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1829) setItemLabelConverter cause NullPointerException in Eclipse

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1829?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1829. ---------------------------------- Fix Version/s: 3.0.0.Final (was: 3.x Future) Assignee: George Gastaldi Resolution: Done > setItemLabelConverter cause NullPointerException in Eclipse > ----------------------------------------------------------- > > Key: FORGE-1829 > URL: https://issues.jboss.org/browse/FORGE-1829 > Project: Forge > Issue Type: Bug > Components: UI - Eclipse > Reporter: Aslak Knutsen > Assignee: George Gastaldi > Fix For: 3.0.0.Final > > > {code} > containerAdapter.setItemLabelConverter(new Converter<Container, String>() { > @Override > public String convert(Container source) { > return source.getId(); > } > }); > {code} > In Eclipse, the Converter is called with a "null" argument during Step/Command initialization. Unless the user specifically checks for null a NullPointerException is thrown. > This is especially odd in the case where the user provide a Set of ValueChoices to convert and none of those are null. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1850) Annotation proxies cannot be created for annotations not present in the scaffold addon or it's dependent addons

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1850?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1850. ---------------------------------- Fix Version/s: (was: 3.x Future) Resolution: Out of Date Doesn't seem to happen anymore. Closing it > Annotation proxies cannot be created for annotations not present in the scaffold addon or it's dependent addons > --------------------------------------------------------------------------------------------------------------- > > Key: FORGE-1850 > URL: https://issues.jboss.org/browse/FORGE-1850 > Project: Forge > Issue Type: Bug > Components: Scaffold > Affects Versions: 2.5.0.Final > Reporter: Vineet Reynolds > > The following exception is reported when running tests ported from Forge 1: > {noformat} > org.metawidget.inspector.iface.InspectorException: java.lang.ClassNotFoundException: org.jboss.forge.addon.scaffold.faces.metawidget.inspector.propertystyle.MockAnnotationSimple from [Module "org.jboss.forge.addon.scaffold-faces:2.5.1-SNAPSHOT_88be45bb-a55d-47fa-ba76-5fa429c6f568" from AddonModuleLoader] > at org.metawidget.inspector.iface.InspectorException.newException(InspectorException.java:45) > at org.jboss.forge.addon.scaffold.faces.metawidget.inspector.propertystyle.ForgePropertyStyle$AnnotationProxy.newInstance(ForgePropertyStyle.java:625) > at org.jboss.forge.addon.scaffold.faces.metawidget.inspector.propertystyle.ForgePropertyStyle$ForgeProperty.getAnnotation(ForgePropertyStyle.java:531) > at org.jboss.forge.addon.scaffold.faces.metawidget.inspector.propertystyle.ForgePropertyStyleTest.testAnnotationProxy(ForgePropertyStyleTest.java:97) > 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.jboss.forge.furnace.proxy.ClassLoaderInterceptor$1.call(ClassLoaderInterceptor.java:65) > at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:34) > at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor.invoke(ClassLoaderInterceptor.java:81) > at org.jboss.forge.addon.scaffold.faces.metawidget.inspector.propertystyle.ForgePropertyStyleTest_$$_javassist_78d992ab-ee23-42b3-912f-fc24195c1bb4.testAnnotationProxy(ForgePropertyStyleTest_$$_javassist_78d992ab-ee23-42b3-912f-fc24195c1bb4.java) > 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.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback$1.call(ClassLoaderAdapterCallback.java:103) > at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:34) > at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.invoke(ClassLoaderAdapterCallback.java:76) > at org.jboss.forge.addon.scaffold.faces.metawidget.inspector.propertystyle.ForgePropertyStyleTest_$$_javassist_cbde15ca-4b5c-4425-9c40-aeae0319c708.testAnnotationProxy(ForgePropertyStyleTest_$$_javassist_cbde15ca-4b5c-4425-9c40-aeae0319c708.java) > 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.jboss.forge.arquillian.ForgeTestMethodExecutor.invoke(ForgeTestMethodExecutor.java:143) > at org.jboss.arquillian.container.test.impl.execution.RemoteTestExecuter.execute(RemoteTestExecuter.java:109) > 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.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.container.test.impl.execution.ClientTestExecuter.execute(ClientTestExecuter.java:57) > 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.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createTestContext(ContainerEventController.java:129) > 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.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:102) > 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.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:84) > 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.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:65) > 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.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.test(EventTestRunnerAdaptor.java:111) > at org.jboss.arquillian.junit.Arquillian$6.evaluate(Arquillian.java:266) > at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:229) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:317) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:243) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:188) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:317) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:202) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:150) > at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50) > at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:675) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:192) > Caused by: org.metawidget.inspector.iface.InspectorException: java.lang.ClassNotFoundException: org.jboss.forge.addon.scaffold.faces.metawidget.inspector.propertystyle.MockAnnotationSimple from [Module "org.jboss.forge.addon.scaffold-faces:2.5.1-SNAPSHOT_88be45bb-a55d-47fa-ba76-5fa429c6f568" from AddonModuleLoader] > ... 100 more > Caused by: java.lang.ClassNotFoundException: org.jboss.forge.addon.scaffold.faces.metawidget.inspector.propertystyle.MockAnnotationSimple from [Module "org.jboss.forge.addon.scaffold-faces:2.5.1-SNAPSHOT_88be45bb-a55d-47fa-ba76-5fa429c6f568" from AddonModuleLoader] > at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:197) > at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:443) > at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:431) > at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:373) > at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:118) > at java.lang.Class.forName0(Native Method) > at java.lang.Class.forName(Class.java:259) > at org.jboss.forge.addon.scaffold.faces.metawidget.inspector.propertystyle.ForgePropertyStyle$AnnotationProxy.newInstance(ForgePropertyStyle.java:614) > ... 98 more > {noformat} > The {{MockAnnotationSimple}} class in this instance is present in the addon runinng the test, and the scaffold-faces addon attempts to load the class. The addon running the test depends on scaffold-faces and not vice versa, thus causing the class loading exception. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1868) addon-build-and-install (and related build commands) should display output in console.

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1868?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1868. ---------------------------------- Fix Version/s: 3.0.0.Final (was: 3.x Future) Assignee: George Gastaldi Resolution: Done > addon-build-and-install (and related build commands) should display output in console. > -------------------------------------------------------------------------------------- > > Key: FORGE-1868 > URL: https://issues.jboss.org/browse/FORGE-1868 > Project: Forge > Issue Type: Feature Request > Components: Addon Development > Affects Versions: 2.6.0.Final > Reporter: Lincoln Baxter III > Assignee: George Gastaldi > Fix For: 3.0.0.Final > > > Currently the build-and-install and build commands do not display any output and the user is left wondering what is going on. This should be displayed in the console. UIOutput -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues June 2016