October 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-2797) .ini upgrade issue for 7.0.1 OSX users

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-2797?page=com.atlassian.jira.plugin.... ] Len DiMaggio updated JBDS-2797: ------------------------------- CDW qa_ack: + (was: ?) > .ini upgrade issue for 7.0.1 OSX users > -------------------------------------- > > Key: JBDS-2797 > URL: https://issues.jboss.org/browse/JBDS-2797 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build, installer > Affects Versions: 7.0.1.GA > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Priority: Critical > > User noticed issues with 7.0.0 to 7.0.1 updates at https://community.jboss.org/message/841477#841477 that needs investigation. > The post is about osx but I don't think this is limited to this OS, just that OSX has a different java behavior. > Worrisome issues are: > development url used in GA update: > -Djboss.discovery.directory.url=https://devstudio.jboss.com/updates/7.0-development/devstudio-directory.xml > startup/launcher directories are hardcoded in the .ini file: > -startup > ../../../plugins/org.eclipse.equinox.launcher_1.3.0.v20130327-1440.jar > --launcher.library > ../../../plugins/org.eclipse.equinox.launcher.cocoa.macosx.x86_64_1.1.200.v20130807-1835 > Have these been forgotten/set wrong in the update or is this some specific update path that is failing ? -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2797) .ini upgrade issue for 7.0.1 OSX users

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-2797?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-2797: ----------------------------- CDW release: + (was: ?) > .ini upgrade issue for 7.0.1 OSX users > -------------------------------------- > > Key: JBDS-2797 > URL: https://issues.jboss.org/browse/JBDS-2797 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build, installer > Affects Versions: 7.0.1.GA > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Priority: Critical > > User noticed issues with 7.0.0 to 7.0.1 updates at https://community.jboss.org/message/841477#841477 that needs investigation. > The post is about osx but I don't think this is limited to this OS, just that OSX has a different java behavior. > Worrisome issues are: > development url used in GA update: > -Djboss.discovery.directory.url=https://devstudio.jboss.com/updates/7.0-development/devstudio-directory.xml > startup/launcher directories are hardcoded in the .ini file: > -startup > ../../../plugins/org.eclipse.equinox.launcher_1.3.0.v20130327-1440.jar > --launcher.library > ../../../plugins/org.eclipse.equinox.launcher.cocoa.macosx.x86_64_1.1.200.v20130807-1835 > Have these been forgotten/set wrong in the update or is this some specific update path that is failing ? -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2250) Provide a "JBoss" CSS theme in JBT and enable it by default in JBDS

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-2250?page=com.atlassian.jira.plugin.... ] Mickael Istria commented on JBDS-2250: -------------------------------------- IMO, this is a weak branding. Seen from the outside, JBDS doesn't look different from Eclipse. Anyway, this issue has been closed and is not the right place to discuss it any more. Instead, it would help if someone could review PRs submitted for JBDS-2790 > Provide a "JBoss" CSS theme in JBT and enable it by default in JBDS > ------------------------------------------------------------------- > > Key: JBDS-2250 > URL: https://issues.jboss.org/browse/JBDS-2250 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: ui/branding > Reporter: Mickael Istria > Assignee: Mickael Istria > Priority: Optional > Fix For: 6.0.0.Alpha2 > > Attachments: failed-to-get-bundle-net.jeeeeyul.eclipse.themes.png, snapshot9.png > > > We could leverage Eclipse 4 CSS styling and theming abilities to provide a "JBoss Theme" in JBoss Tools, and make it the default CSS/theme in JBDS. -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15495) OpenShift server adapter: publish locks the whole workspace

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15495?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-15495: -------------------------------- Fix Version/s: 4.1.1.Beta1 > OpenShift server adapter: publish locks the whole workspace > ----------------------------------------------------------- > > Key: JBIDE-15495 > URL: https://issues.jboss.org/browse/JBIDE-15495 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift, server > Affects Versions: 4.1.0.Final > Reporter: Xavier Coulon > Assignee: Rob Stryker > Labels: openshift_server_adapter > Fix For: 4.1.1.Beta1, 4.2.0.Alpha1 > > Attachments: Screen Shot 2013-09-17 at 10.42.43 AM.png > > > Have 2 projects in a workspace, one of them is an OpenShift application > Deploy some changes on OpenShift, and while the publication is performed (git push, then OS restarts the server), go to the second (unrelated) project and try to move a file from a package to another package in the same project. > The 'Publish' operation locked the whoel workspace, which means that the move operation needs to wait. -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2250) Provide a "JBoss" CSS theme in JBT and enable it by default in JBDS

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2250?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-2250: ---------------------------------- Is not the icon in the top-left corner of the app (Eclipse ball vs. JBDS ball), or the Help > About dialog sufficient to know whether you're running Eclipse + JBDS BYOE or the JBDS branded product? -1 for any CSS changes that turn Eclipse pink. > Provide a "JBoss" CSS theme in JBT and enable it by default in JBDS > ------------------------------------------------------------------- > > Key: JBDS-2250 > URL: https://issues.jboss.org/browse/JBDS-2250 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: ui/branding > Reporter: Mickael Istria > Assignee: Mickael Istria > Priority: Optional > Fix For: 6.0.0.Alpha2 > > Attachments: failed-to-get-bundle-net.jeeeeyul.eclipse.themes.png, snapshot9.png > > > We could leverage Eclipse 4 CSS styling and theming abilities to provide a "JBoss Theme" in JBoss Tools, and make it the default CSS/theme in JBDS. -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15653) Import application wizard: Errors "Could not publish: Attempted to begin rule"

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15653?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-15653 at 10/15/13 12:49 PM: --------------------------------------------------------------------- The problem arises when the OpenShiftPublishMethod executes #refreshProject: {code} protected void refreshProject(final IProject project, IProgressMonitor monitor) throws CoreException { // Already inside a workspace scheduling rule project.refreshLocal(IResource.DEPTH_INFINITE, monitor); } {code} The cause to this rule conflict (the lock in Server#PublishJob does not include the project that we want to publish) is due to to the fact that our server adapter has no module: {code:title=OpenShiftServerAdapterFactory#getModules} private List<IModule> getModules(List<IProject> importedProjects) { Iterator<IProject> i = importedProjects.iterator(); ArrayList<IModule> toAdd = new ArrayList<IModule>(); while (i.hasNext()) { IProject p = i.next(); IModule[] m = ServerUtil.getModules(p); if (m != null && m.length > 0) { toAdd.addAll(Arrays.asList(m)); } } return toAdd; } {code} *ServerUtil.getModules(p)* returns *null*,The cause to this is that there's no module factory for OpenShift projects. The Server thus has therefore no locks on the project that is being published and that we want to refresh. The call to #refreshLocal will fail since the Server#PublishJon complains about the project not being included in its scheduling rule was (Author: adietish): The problem arises when the OpenShiftPublishMethod executes #refreshProject: {code} protected void refreshProject(final IProject project, IProgressMonitor monitor) throws CoreException { // Already inside a workspace scheduling rule project.refreshLocal(IResource.DEPTH_INFINITE, monitor); } {code} The call to #refreshLocal will fail since the Server#PublishJon complains about the project not being included in its scheduling rule > Import application wizard: Errors "Could not publish: Attempted to begin rule" > ------------------------------------------------------------------------------ > > Key: JBIDE-15653 > URL: https://issues.jboss.org/browse/JBIDE-15653 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.Alpha1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Blocker > Fix For: 4.2.0.Alpha1 > > Attachments: could-not-import.png, gitignore-committed-locally.png > > -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2797) .ini upgrade issue for 7.0.1 OSX users

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2797?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2797: ----------------------------- Summary: .ini upgrade issue for 7.0.1 OSX users (was: .ini upgrade issue for 7.0.1 users) > .ini upgrade issue for 7.0.1 OSX users > -------------------------------------- > > Key: JBDS-2797 > URL: https://issues.jboss.org/browse/JBDS-2797 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build, installer > Affects Versions: 7.0.1.GA > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Priority: Critical > > User noticed issues with 7.0.0 to 7.0.1 updates at https://community.jboss.org/message/841477#841477 that needs investigation. > The post is about osx but I don't think this is limited to this OS, just that OSX has a different java behavior. > Worrisome issues are: > development url used in GA update: > -Djboss.discovery.directory.url=https://devstudio.jboss.com/updates/7.0-development/devstudio-directory.xml > startup/launcher directories are hardcoded in the .ini file: > -startup > ../../../plugins/org.eclipse.equinox.launcher_1.3.0.v20130327-1440.jar > --launcher.library > ../../../plugins/org.eclipse.equinox.launcher.cocoa.macosx.x86_64_1.1.200.v20130807-1835 > Have these been forgotten/set wrong in the update or is this some specific update path that is failing ? -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2797) .ini upgrade issue for 7.0.1 users

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2797?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2797: ----------------------------- CDW devel_ack: + (was: ?) > .ini upgrade issue for 7.0.1 users > ---------------------------------- > > Key: JBDS-2797 > URL: https://issues.jboss.org/browse/JBDS-2797 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build, installer > Affects Versions: 7.0.1.GA > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Priority: Critical > > User noticed issues with 7.0.0 to 7.0.1 updates at https://community.jboss.org/message/841477#841477 that needs investigation. > The post is about osx but I don't think this is limited to this OS, just that OSX has a different java behavior. > Worrisome issues are: > development url used in GA update: > -Djboss.discovery.directory.url=https://devstudio.jboss.com/updates/7.0-development/devstudio-directory.xml > startup/launcher directories are hardcoded in the .ini file: > -startup > ../../../plugins/org.eclipse.equinox.launcher_1.3.0.v20130327-1440.jar > --launcher.library > ../../../plugins/org.eclipse.equinox.launcher.cocoa.macosx.x86_64_1.1.200.v20130807-1835 > Have these been forgotten/set wrong in the update or is this some specific update path that is failing ? -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15653) Import application wizard: Errors "Could not publish: Attempted to begin rule"

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15653?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-15653 at 10/15/13 12:44 PM: --------------------------------------------------------------------- The above code is perfectly correct. It will publish dirty-project and will check the non-dirty ones for being ahead of the remote. If the non-dirty projects are not-ahead either, no publishing will occurr. A project that we import from OpenShift gets a .gitignore that we commit: !gitignore-committed-locally.png! Thus the imported project is ahead of the remote by 1 commit. was (Author: adietish): The above code is perfectly correct. It will publish dirty-project and will check the non-dirty ones for being ahead of the remote. If the non-dirty projects are not-ahead either, no publishing will occurr. > Import application wizard: Errors "Could not publish: Attempted to begin rule" > ------------------------------------------------------------------------------ > > Key: JBIDE-15653 > URL: https://issues.jboss.org/browse/JBIDE-15653 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.Alpha1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Blocker > Fix For: 4.2.0.Alpha1 > > Attachments: could-not-import.png, gitignore-committed-locally.png > > -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15653) Import application wizard: Errors "Could not publish: Attempted to begin rule"

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15653?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-15653: ------------------------------------- Attachment: gitignore-committed-locally.png > Import application wizard: Errors "Could not publish: Attempted to begin rule" > ------------------------------------------------------------------------------ > > Key: JBIDE-15653 > URL: https://issues.jboss.org/browse/JBIDE-15653 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.Alpha1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Blocker > Fix For: 4.2.0.Alpha1 > > Attachments: could-not-import.png, gitignore-committed-locally.png > > -- 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

12 years, 8 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues October 2013