[JBoss JIRA] (FORGE-2604) IDEA/Eclipse development - Make it possible to log to log/eventlog
by Claus Ibsen (JIRA)
[ https://issues.jboss.org/browse/FORGE-2604?page=com.atlassian.jira.plugin... ]
Claus Ibsen commented on FORGE-2604:
------------------------------------
Also maybe for trouble shooting then any logs from forge itself would be nice to turn on | off. Maybe if you can change logging levels or something.
Or if forge itself had a preference or something where you can configure these settings. Also in GUI it can be non trivial to find our what versions of the addons are installed. As there …
[View More]command addon-list is not there.
So maybe if forge has a preference, then there is a button / tab or something that shows all the addons.
> IDEA/Eclipse development - Make it possible to log to log/eventlog
> ------------------------------------------------------------------
>
> Key: FORGE-2604
> URL: https://issues.jboss.org/browse/FORGE-2604
> Project: Forge
> Issue Type: Feature Request
> Components: UI - API
> Affects Versions: 3.0.0.CR1
> Reporter: Claus Ibsen
>
> Developing forge addons is really painful when developing and testing for GUIs such as IDEA or Eclipse.
> There is no logging or visibility what happens. And logging on IDEA or Eclipse is different, and you as a forge addon developed dont really know where the log files of IDEA/Eclipse are stored and how to log to them.
> Forge should have an easy API that you can use to
> - log in IDEA/Eclipse log
> - log to custom log file which you can easily configure
> - log to IDEA/Eclipse event log / console.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
[View Less]
9 years, 1 month
[JBoss JIRA] (FORGE-2604) IDEA/Eclipse development - Make it possible to log to log/eventlog
by Claus Ibsen (JIRA)
[ https://issues.jboss.org/browse/FORGE-2604?page=com.atlassian.jira.plugin... ]
Claus Ibsen commented on FORGE-2604:
------------------------------------
I had a chat with gastaldi
{code}
[13:10:32] <gastaldi> I agree with your logging idea. Right now we rely on JUL but that doesn't really work well inside the plugins (eg. Forge.log is not used).
[13:11:09] <davsclaus> yeah i found this
[13:11:09] <davsclaus> https://github.com/JetBrains/intellij-community/blob/master/…
[View More]platform/util...
[13:11:18] <gastaldi> Perhaps the UIOutput.error method could log to the event log?
[13:11:21] <davsclaus> but i couldnt get that to work initially
[13:11:25] <davsclaus> so i just wrote a poor man
[13:11:40] <davsclaus> yeah
[13:12:07] <davsclaus> so what i see is that often there is either 1 log line in event log
[13:12:25] <davsclaus> if there was an error that would be the exception message
[13:12:32] <davsclaus> very seldom i see a full stacktrace
[13:12:33] <gastaldi> We generally log exceptions in the Eclipse event log
[13:12:49] <davsclaus> yeah if you can figure out to get them in idea event log
[13:12:57] <davsclaus> also i have seen that
[13:13:00] <davsclaus> if i teturn
[13:13:05] <davsclaus> Results.fail("xxx")
[13:13:10] <davsclaus> then that is not shown either
[13:13:18] <gastaldi> Right
[13:13:20] <davsclaus> but it could be my command that is a wizard
[13:13:22] <davsclaus> so it has some steps
[13:13:27] <gastaldi> Oh
[13:13:34] <davsclaus> but the command sad "success"
[13:13:37] <davsclaus> when i ran
[13:13:38] <davsclaus> it
[13:13:40] <gastaldi> Yeah. It returns as a CompositeResult
[13:13:50] <gastaldi> Hmm
[13:13:54] <davsclaus> so dont you check if any of those is a fail
[13:13:57] <davsclaus> and then show that
[13:14:01] <davsclaus> over an success
[13:14:18] <gastaldi> We do, it might have a bug in it
[13:14:24] <davsclaus> also there is little confusion if you should return null or Results.success
[13:14:28] <davsclaus> when you have a wizard
[13:14:35] <gastaldi> That's indifferent
[13:14:51] <gastaldi> Forge considers success when null is returned
[13:14:54] <davsclaus> ah ok so a null is like a success
[13:15:08] <gastaldi> Yeap
[13:17:54] <gastaldi> Mind copying this chat log to the JIRA? My mobile app doesn't support it. Will move to my laptop in a few mins
[13:18:14] <davsclaus> k
{code}
> IDEA/Eclipse development - Make it possible to log to log/eventlog
> ------------------------------------------------------------------
>
> Key: FORGE-2604
> URL: https://issues.jboss.org/browse/FORGE-2604
> Project: Forge
> Issue Type: Feature Request
> Components: UI - API
> Affects Versions: 3.0.0.CR1
> Reporter: Claus Ibsen
>
> Developing forge addons is really painful when developing and testing for GUIs such as IDEA or Eclipse.
> There is no logging or visibility what happens. And logging on IDEA or Eclipse is different, and you as a forge addon developed dont really know where the log files of IDEA/Eclipse are stored and how to log to them.
> Forge should have an easy API that you can use to
> - log in IDEA/Eclipse log
> - log to custom log file which you can easily configure
> - log to IDEA/Eclipse event log / console.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
[View Less]
9 years, 1 month
[JBoss JIRA] (FORGE-2604) IDEA/Eclipse development - Make it possible to log to log/eventlog
by Claus Ibsen (JIRA)
[ https://issues.jboss.org/browse/FORGE-2604?page=com.atlassian.jira.plugin... ]
Claus Ibsen updated FORGE-2604:
-------------------------------
Priority: Major (was: Critical)
> IDEA/Eclipse development - Make it possible to log to log/eventlog
> ------------------------------------------------------------------
>
> Key: FORGE-2604
> URL: https://issues.jboss.org/browse/FORGE-2604
> Project: Forge
> Issue Type: …
[View More]Feature Request
> Components: UI - API
> Affects Versions: 3.0.0.CR1
> Reporter: Claus Ibsen
>
> Developing forge addons is really painful when developing and testing for GUIs such as IDEA or Eclipse.
> There is no logging or visibility what happens. And logging on IDEA or Eclipse is different, and you as a forge addon developed dont really know where the log files of IDEA/Eclipse are stored and how to log to them.
> Forge should have an easy API that you can use to
> - log in IDEA/Eclipse log
> - log to custom log file which you can easily configure
> - log to IDEA/Eclipse event log / console.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
[View Less]
9 years, 1 month
[JBoss JIRA] (FORGE-2604) IDEA/Eclipse development - Make it possible to log to log/eventlog
by Claus Ibsen (JIRA)
[ https://issues.jboss.org/browse/FORGE-2604?page=com.atlassian.jira.plugin... ]
Claus Ibsen commented on FORGE-2604:
------------------------------------
Took me a while to track down that this results.fail in my addon is not logged anywhere, and my command complete with success it says
https://github.com/fabric8io/fabric8-forge/blob/master/addons/camel/src/m...
In the IDEA event log all I see is
9:17:17 AM Command executed successfully
With my poor man logger I could see the facet.…
[View More]getResource returned null, and the reason is that the name of the resource was the absolute name and not relative.
> IDEA/Eclipse development - Make it possible to log to log/eventlog
> ------------------------------------------------------------------
>
> Key: FORGE-2604
> URL: https://issues.jboss.org/browse/FORGE-2604
> Project: Forge
> Issue Type: Feature Request
> Components: UI - API
> Affects Versions: 3.0.0.CR1
> Reporter: Claus Ibsen
> Priority: Critical
>
> Developing forge addons is really painful when developing and testing for GUIs such as IDEA or Eclipse.
> There is no logging or visibility what happens. And logging on IDEA or Eclipse is different, and you as a forge addon developed dont really know where the log files of IDEA/Eclipse are stored and how to log to them.
> Forge should have an easy API that you can use to
> - log in IDEA/Eclipse log
> - log to custom log file which you can easily configure
> - log to IDEA/Eclipse event log / console.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
[View Less]
9 years, 1 month
[JBoss JIRA] (FORGE-2604) IDEA/Eclipse development - Make it possible to log to log/eventlog
by Claus Ibsen (JIRA)
[ https://issues.jboss.org/browse/FORGE-2604?page=com.atlassian.jira.plugin... ]
Claus Ibsen commented on FORGE-2604:
------------------------------------
As a fallback I am doing my own poor mans logger with writing to a file manually.
> IDEA/Eclipse development - Make it possible to log to log/eventlog
> ------------------------------------------------------------------
>
> Key: FORGE-2604
> URL: https://issues.jboss.org/browse/FORGE-2604
&…
[View More]gt; Project: Forge
> Issue Type: Feature Request
> Components: UI - API
> Affects Versions: 3.0.0.CR1
> Reporter: Claus Ibsen
> Priority: Critical
>
> Developing forge addons is really painful when developing and testing for GUIs such as IDEA or Eclipse.
> There is no logging or visibility what happens. And logging on IDEA or Eclipse is different, and you as a forge addon developed dont really know where the log files of IDEA/Eclipse are stored and how to log to them.
> Forge should have an easy API that you can use to
> - log in IDEA/Eclipse log
> - log to custom log file which you can easily configure
> - log to IDEA/Eclipse event log / console.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
[View Less]
9 years, 1 month
[JBoss JIRA] (FORGE-2604) IDEA/Eclipse development - Make it possible to log to log/eventlog
by Claus Ibsen (JIRA)
Claus Ibsen created FORGE-2604:
----------------------------------
Summary: IDEA/Eclipse development - Make it possible to log to log/eventlog
Key: FORGE-2604
URL: https://issues.jboss.org/browse/FORGE-2604
Project: Forge
Issue Type: Feature Request
Components: UI - API
Affects Versions: 3.0.0.CR1
Reporter: Claus Ibsen
Priority: Critical
Developing forge addons is really painful when …
[View More]developing and testing for GUIs such as IDEA or Eclipse.
There is no logging or visibility what happens. And logging on IDEA or Eclipse is different, and you as a forge addon developed dont really know where the log files of IDEA/Eclipse are stored and how to log to them.
Forge should have an easy API that you can use to
- log in IDEA/Eclipse log
- log to custom log file which you can easily configure
- log to IDEA/Eclipse event log / console.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
[View Less]
9 years, 1 month
[JBoss JIRA] (FURNACE-106) LinuxWatchService: "Too many open files"
by Ondrej Zizka (JIRA)
[ https://issues.jboss.org/browse/FURNACE-106?page=com.atlassian.jira.plugi... ]
Ondrej Zizka commented on FURNACE-106:
--------------------------------------
The minimal test case could be the Maven plugin project, running itself in after the package phase, and installing Windup addons which are in Maven central repo.
> LinuxWatchService: "Too many open files"
> ----------------------------------------
>
> Key: FURNACE-106
> URL: https://…
[View More]issues.jboss.org/browse/FURNACE-106
> Project: Forge: Furnace
> Issue Type: Bug
> Components: Runtime
> Affects Versions: 2.22.10.Final
> Reporter: Ondrej Zizka
> Attachments: strace.log.9838
>
>
> When running Windup in a Maven plugin, I get the exception below.
> I have increased all linux limits to 1 000 000.
> STR:
> git clone https://github.com/OndraZizka/windup
> cd windup
> git co
> mvn clean install -DskipTests
> cd ..
> git clone https://github.com/OndraZizka/windup-maven-plugin.git
> cd windup-maven-plugin
> git co bfaa7b6
> mvn clean install
> cd ..
> git clone https://github.com/OndraZizka/windup-quickstarts.git
> cd windup-quickstarts
> git co 9b991fc8db1
> mvn clean install
>
> git clone https://github.com/OndraZizka/windup.git
> {code}
> 2016-01-28 17:46:52 WARNING org.jboss.forge.furnace.impl.FurnaceImpl <init>() File monitoring could not be started.
> java.io.IOException: Too many open files
> at sun.nio.fs.LinuxWatchService.<init>(LinuxWatchService.java:61)
> at sun.nio.fs.LinuxFileSystem.newWatchService(LinuxFileSystem.java:47)
> at org.jboss.forge.furnace.impl.FurnaceImpl.<init>(FurnaceImpl.java:152)
> at org.jboss.forge.furnace.impl.FurnaceImpl_$$_javassist_9290627c-c1d3-4961-b1cd-6bd226307dc3.<init>(FurnaceImpl_$$_javassist_9290627c-c1d3-4961-b1cd-6bd226307dc3.java)
> at sun.reflect.GeneratedConstructorAccessor65.newInstance(Unknown Source)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
> at java.lang.Class.newInstance(Class.java:383)
> at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback$3.call(ClassLoaderAdapterCallback.java:992)
> at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42)
> at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.enhance(ClassLoaderAdapterCallback.java:900)
> at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.enhance(ClassLoaderAdapterCallback.java:880)
> at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.enhanceSingleParameterValue(ClassLoaderAdapterCallback.java:776)
> at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.enhanceParameterValues(ClassLoaderAdapterCallback.java:648)
> at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.access$000(ClassLoaderAdapterCallback.java:37)
> at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback$2.call(ClassLoaderAdapterCallback.java:117)
> at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42)
> at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.invoke(ClassLoaderAdapterCallback.java:96)
> at org.jboss.forge.furnace.spi.ContainerLifecycleListener_$$_javassist_ad6baef1-d99b-4e97-8f1e-324f98eb5edf.afterConfigurationScan(ContainerLifecycleListener_$$_javassist_ad6baef1-d99b-4e97-8f1e-324f98eb5edf.java)
> at org.jboss.forge.furnace.impl.FurnaceImpl.fireAfterConfigurationScanEvent(FurnaceImpl.java:657)
> at org.jboss.forge.furnace.impl.FurnaceImpl.reloadConfiguration(FurnaceImpl.java:606)
> at org.jboss.forge.furnace.impl.FurnaceImpl.access$500(FurnaceImpl.java:59)
> at org.jboss.forge.furnace.impl.FurnaceImpl$2.call(FurnaceImpl.java:276)
> at org.jboss.forge.furnace.impl.FurnaceImpl$2.call(FurnaceImpl.java:241)
> at org.jboss.forge.furnace.impl.lock.LockManagerImpl.performLocked(LockManagerImpl.java:55)
> at org.jboss.forge.furnace.impl.FurnaceImpl.start(FurnaceImpl.java:240)
> at org.jboss.forge.furnace.impl.FurnaceImpl$1$1.run(FurnaceImpl.java:199)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
[View Less]
9 years, 1 month