[JBoss JIRA] (JBIDE-13851) Add source lookup classes to Java Search
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13851?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-13851:
-------------------------------------
Stacktraces fill up the .log if you have non-jboss servers in your workspace:
{noformat}
!MESSAGE Cannot prepare server Tomcat v7.0 Server at localhost for launch because it is not a proper JBoss Server
!STACK 1
org.eclipse.core.runtime.CoreException: Cannot prepare server Tomcat v7.0 Server at localhost for launch because it is not a proper JBoss Server
at org.jboss.ide.eclipse.as.core.util.ServerConverter.checkedConvertServer(ServerConverter.java:71)
at org.jboss.ide.eclipse.as.core.util.ServerConverter.checkedGetJBossServer(ServerConverter.java:93)
at org.jboss.tools.maven.sourcelookup.ui.preferences.SourceLookupPreferencePage.getServers(SourceLookupPreferencePage.java:279)
at org.jboss.tools.maven.sourcelookup.ui.preferences.SourceLookupPreferencePage.createContents(SourceLookupPreferencePage.java:203)
at org.eclipse.jface.preference.PreferencePage.createControl(PreferencePage.java:231)
at org.eclipse.jface.preference.PreferenceDialog.createPageControl(PreferenceDialog.java:1519)
[...cropped]
{noformat}
> Add source lookup classes to Java Search
> ----------------------------------------
>
> Key: JBIDE-13851
> URL: https://issues.jboss.org/browse/JBIDE-13851
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: maven
> Affects Versions: 4.1.0.Alpha1
> Reporter: Snjezana Peco
> Assignee: Snjezana Peco
> Fix For: 4.2.x
>
>
> This feature would be implemented in a similar way to adding PDE plugins to the Java Search.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 2 months
[JBoss JIRA] (JBIDE-15324) Add an option to regenerate project files
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15324?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-15324:
-------------------------------------
I'm not overly thrilled about that idea, rather the opposite.
- This would require changes in m2e core, where the import logic is defined, before calling any configurators; and m2e ui, to enable that option
- we can't know in advance what files to delete. The most common ones being .project, .classpath, .settings/. But other config files can be generated by eclipse plugins at the root of the project that would be ignored. Also blindly wiping .settings/ out would delete some config files for stuff not necessarily integrated with m2e, forcing users to reconfigure some projects settings manually after each import. And since m2e core knows nothing about JDT for instance, we would need to have a pluggable approach (extension points and all) to let each individual plugin from the m2e ecosystem tell what files to delete on import.
Not sure we'd have much to gain from all that. And that idea would still need to be vetted by the m2e project lead which is another story...
> Add an option to regenerate project files
> -----------------------------------------
>
> Key: JBIDE-15324
> URL: https://issues.jboss.org/browse/JBIDE-15324
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: maven
> Reporter: George Gastaldi
>
> JBIDE-15322 was caused due to a malformed .project file. It would be nice to have an option when updating (or importing) the Maven project to allow regeneration of these files (.project, .classpath, .settings/).
> Here is a chat transcript from [~akazakov] and [~gastaldi] in the #jbosstools channel:
> {quote}
> <akazakov> can you remove this project, pull it again and re-import?
> <gastaldi> I deleted my .project, .classpath, .settings and .external-builders and it works now
> <gastaldi> is it possible to add an option to regenerate these files on import ?
> <gastaldi> this may be garbage from older m2 versions
> <akazakov> when you import the project as a maven project then these files should be generated
> <gastaldi> in my case these files already existed
> <gastaldi> but they were screwed
> <akazakov> yes the maven tooling just updates them if they exist.
> <akazakov> it can't remove the old one since it can have some custom settings you don't want to loose
> <gastaldi> I know, that's why I asked for an option to regenerate it :)
> <gastaldi> I think that the majority of use-cases will not have any custom settings
> <akazakov> ah. got it. I'm not sure.. Maybe Fred knows anything about it.
> <gastaldi> is he on PTO ?
> <akazakov> yes
> <gastaldi> ok, perhaps it may be worth talking with him about this, since it may save some headaches in the future :)
> <akazakov> yes. you are right
> <gastaldi> thanks for your time akazakov
> <akazakov> no problem )
> <akazakov> can you create an issue about the option to regenerate .project .classpath etc when importing a maven project? Just not to forget it when Fred is back
> <gastaldi> ok
> {quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 2 months
[JBoss JIRA] (JBIDE-15367) JBoss Knowledge Base Builder hangs up
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15367?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-15367:
----------------------------------------
Fix Version/s: 4.1.1.Alpha1
Priority: Blocker (was: Major)
All eclipse builders will be running concurrently so it is expected those models are threadsafe!
Marking as blocker on 4.1.1 too since assumed this is present in both branch and master.
> JBoss Knowledge Base Builder hangs up
> -------------------------------------
>
> Key: JBIDE-15367
> URL: https://issues.jboss.org/browse/JBIDE-15367
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common/jst/core
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Priority: Blocker
> Fix For: 4.1.1.Alpha1, 4.2.0.Alpha1
>
>
> https://community.jboss.org/message/833488
> The cause is thread unsafe code in org.jboss.tools.jsf.jsf2.bean.model.impl.DefinitionContext. When one thread reads from HashSet while another modifies it, sometimes reading slips into eternal cycle. That is a feature of implementation of java.util.HashSet, and the only way to avoid it is to provide thread safety. I will open an issue.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 2 months