August 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-20100) how to make users aware of fuse and other tooling only being available from earlyaccess?

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20100?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-20100: ------------------------------------- With the current code in master, when EA is enabled, I can see the AngularJS for Web Tools is available in the software page. With the suggested PR, clicking on the Manage Early Access link, it opens !http://content.screencast.com/users/fbricon/folders/Jing/media/117c37a7-b095-444a-b54b-c862a561321e/00000170.png|width=600! No EA plugin in sight despite EA being enabled. Where is AngularJS? > how to make users aware of fuse and other tooling only being available from earlyaccess? > ----------------------------------------------------------------------------------------- > > Key: JBIDE-20100 > URL: https://issues.jboss.org/browse/JBIDE-20100 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Fix For: 4.3.0.CR1 > > > [~jtyrrell] find it confusing when he cannot see Fuse and other earlyaccess features immediately on the install page. > Some comments: > "I install JBDS 8.1 and click on the JBoss Integration and SOA Development, but where is the Fuse tooling in that list." > "<without earlyaccess> why doesn’t my screen shot tell me to use an older version of JBDS or something." > Suggestion: > "when I picked the Integration Stack a greyed out Fuse IDE thingy in the list of choices, and something like (Select early Access) to enable this feature." > I'm fine exploring options to show early access features more prominently but would prefer we would not need to treat Fuse "special" so maybe we should have a "Early Access" section at the bottom instead of filtered in between everything else ? > and for any connectors that has additional/different features just add a "Extra features available in Early access " comment ? > But what to do when Fuse or others dont even have an earlyaccess out yet ? (like is currently the state for devstudio 9) > [~crobson], [~aileenc] and [~lhein] got any suggestions ? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20476) "File may be locked" warning if EAR is deployed to multiple Servers

by The Alchemist (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20476?page=com.atlassian.jira.plugi... ] The Alchemist commented on JBIDE-20476: --------------------------------------- Thanks, [~rob.stryker]. I'm on Mac OS X 10.10.5, BTW. I have a bit more information, as I was just able to reproduce it: * My WF 8.2 Server is set to "use workspace metadata" * My WF 9.0.1 Server is set to "use the JBoss deploy folder" 1. I had disabled "Build Automatically" in Eclipse and built my project in Maven from the command line. 2. Forgetting to re-check "Build Automatically", I clicked on Synchronize, which produced the "File may be locked" errors. 3. After checking "Build Automatically", some Maven auto-generated files were still missing, so I Cleaned my projects. 4. Still, Synchronize gave some errors, so I Removed the modules from the WF 8.2 Server, and then Publish gave no errors. Very strange and I don't think I'll be able to produce a small project to reproduce it. I was just hoping it was an easy fix. > "File may be locked" warning if EAR is deployed to multiple Servers > ------------------------------------------------------------------- > > Key: JBIDE-20476 > URL: https://issues.jboss.org/browse/JBIDE-20476 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.0.Beta2 > Environment: Eclipse Mars > Reporter: The Alchemist > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.3.x > > > I have multiple Server's in my Eclipse: > * Wildfly 8.2 > * Wildfly 9.0.1 > I have my application (two EARs) deployed to both of them, but when I try to Publish my changes, it complains in the Eclipse error log that some files might be locked so the publish was not completely successful. > Perhaps I shouldn't have the same EARs in two apps? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-486) FuseIDE - Migrate to use new license feature in JBTIS 4.3 / JBDS IS 9

by Lars Heinemann (JIRA)

[ https://issues.jboss.org/browse/JBTIS-486?page=com.atlassian.jira.plugin.... ] Lars Heinemann commented on JBTIS-486: -------------------------------------- Already applied to master (Mars) branch of Fuse Tooling when Nick sent this notification out. Should be fixed if the documentation did not change meanwhile. > FuseIDE - Migrate to use new license feature in JBTIS 4.3 / JBDS IS 9 > --------------------------------------------------------------------- > > Key: JBTIS-486 > URL: https://issues.jboss.org/browse/JBTIS-486 > Project: JBoss Tools Integration Stack > Issue Type: Sub-task > Components: Fuse IDE > Affects Versions: 9.0.0.Alpha1 > Reporter: Paul Leacu > Assignee: Paul Leacu > Priority: Blocker > Fix For: 4.3.0.Beta1 > > > Please make sure that Fuse Tooling is including the new license feature. See parent Jira description for details. > ref: https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3507) Extra step in opening terminal in git perspective?

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-3507?page=com.atlassian.jira.plugin.... ] Len DiMaggio updated JBDS-3507: ------------------------------- CDW qa_ack: + (was: ?) > Extra step in opening terminal in git perspective? > -------------------------------------------------- > > Key: JBDS-3507 > URL: https://issues.jboss.org/browse/JBDS-3507 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: 3rd-party-certification > Affects Versions: 9.0.0.Beta2 > Reporter: Len DiMaggio > Fix For: 9.0.0.CR1 > > Attachments: terminal.png > > > If a user opens a terminal view from the git perspective - for example, by performing "show in" for a local repo, an empty terminal view is displayed. The user must then click on the terminal icon to actually open the terminal. This seems like an extra step - why wouldn't we open a terminal when we open the terminal view? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20524) Opening xhtml with VPE ends up with the eclipse crash (Mars 4.5.0)

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20524?page=com.atlassian.jira.plugi... ] Ilya Buziuk commented on JBIDE-20524: ------------------------------------- PR for VPE FAQ was sent - https://github.com/jbosstools/jbosstools-website/pull/464 > Opening xhtml with VPE ends up with the eclipse crash (Mars 4.5.0) > ------------------------------------------------------------------ > > Key: JBIDE-20524 > URL: https://issues.jboss.org/browse/JBIDE-20524 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream, visual-page-editor-core, xulrunner > Affects Versions: 4.3.0.Beta2 > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Priority: Blocker > Labels: upstream > Fix For: 4.3.0.CR1 > > > Upstream regression Mars 4.5.0 XULRunner [Bug 472956|https://bugs.eclipse.org/bugs/show_bug.cgi?id=472956] > Basically, XULRunner crashes when profile path does not exist. The workaround is to create profile folder `C:\Users\<USER_NAME>\AppData\Roaming\Mozilla\eclipse` manually. More details can be found in the reply to the original upstream issue and in the related developer.jboss.org discussion - https://developer.jboss.org/message/938755 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-487) SwitchYard - Migrate to use new license feature in JBTIS 4.3 / JBDS IS 9

by Paul Leacu (JIRA)

Paul Leacu created JBTIS-487: -------------------------------- Summary: SwitchYard - Migrate to use new license feature in JBTIS 4.3 / JBDS IS 9 Key: JBTIS-487 URL: https://issues.jboss.org/browse/JBTIS-487 Project: JBoss Tools Integration Stack Issue Type: Sub-task Components: switchyard Affects Versions: 9.0.0.Alpha1 Reporter: Paul Leacu Assignee: Brian Fitzpatrick Priority: Blocker Please make sure that SwitchYard is including the new license feature. See parent Jira description for details. ref: https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-486) FuseIDE - Migrate to use new license feature in JBTIS 4.3 / JBDS IS 9

by Paul Leacu (JIRA)

Paul Leacu created JBTIS-486: -------------------------------- Summary: FuseIDE - Migrate to use new license feature in JBTIS 4.3 / JBDS IS 9 Key: JBTIS-486 URL: https://issues.jboss.org/browse/JBTIS-486 Project: JBoss Tools Integration Stack Issue Type: Sub-task Components: Fuse IDE Affects Versions: 9.0.0.Alpha1 Reporter: Paul Leacu Assignee: Paul Leacu Priority: Blocker Please make sure that Fuse Tooling is including the new license feature. See parent Jira description for details. ref: https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-485) ModeShape - Migrate to use new license feature in JBTIS 4.3 / JBDS IS 9

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-485?page=com.atlassian.jira.plugin.... ] Paul Leacu updated JBTIS-485: ----------------------------- Parent: JBTIS-482 Issue Type: Sub-task (was: Feature Request) > ModeShape - Migrate to use new license feature in JBTIS 4.3 / JBDS IS 9 > ----------------------------------------------------------------------- > > Key: JBTIS-485 > URL: https://issues.jboss.org/browse/JBTIS-485 > Project: JBoss Tools Integration Stack > Issue Type: Sub-task > Components: modeshape > Affects Versions: 9.0.0.Alpha1 > Reporter: Paul Leacu > Assignee: Dan Florian > Priority: Blocker > > Please make sure that ModeShape is including the new license feature. See parent Jira description for details. > ref: https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-485) ModeShape - Migrate to use new license feature in JBTIS 4.3 / JBDS IS 9

by Paul Leacu (JIRA)

Paul Leacu created JBTIS-485: -------------------------------- Summary: ModeShape - Migrate to use new license feature in JBTIS 4.3 / JBDS IS 9 Key: JBTIS-485 URL: https://issues.jboss.org/browse/JBTIS-485 Project: JBoss Tools Integration Stack Issue Type: Feature Request Components: modeshape Affects Versions: 9.0.0.Alpha1 Reporter: Paul Leacu Assignee: Dan Florian Priority: Blocker Please make sure that ModeShape is including the new license feature. See parent Jira description for details. ref: https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20519) Internal model fails when multiple instances of Studio are opened

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20519?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-20519: ---------------------------------------- Yes, exactly. And Slava's PR moves those files to workspace. > Internal model fails when multiple instances of Studio are opened > ----------------------------------------------------------------- > > Key: JBIDE-20519 > URL: https://issues.jboss.org/browse/JBIDE-20519 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core > Affects Versions: 4.3.0.Beta2 > Reporter: Viacheslav Kabanovich > Assignee: Viacheslav Kabanovich > Fix For: 4.3.0.CR1 > > > To save memory, the internal model stores long text in temporal files with prefix efs_, created in delete-on-exit mode. Since Studio may crash or be killed in the task manager, these files may remain for ever, and to prevent it, model plugin removes files with prefix efs_ during normal exit. > That produces the following problem: > 1. Open Studio in a new workspace, create a jsf project and build it. > 2. Open second instance of Studio in another new workspace, create exactly the same jsf project and build it. > 3. Close the second instance of Studio. > 4. In the first instance of Studio, try clean/build. > Failure: Logged messages like > java.lang.IllegalStateException: Cannot read /tmp/efs_2500225045660665987.sp.txt for object -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 2 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues August 2015