December 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-16317) Tag projects for jbosstools-4.2.0.Alpha1

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16317?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-16317: ------------------------------------------ done for OpenShift: {code} To git@github.com:jbosstools/jbosstools-openshift.git * [new tag] jbosstools-4.2.0.Alpha1 -> jbosstools-4.2.0.Alpha1 {code} > Tag projects for jbosstools-4.2.0.Alpha1 > ---------------------------------------- > > Key: JBIDE-16317 > URL: https://issues.jboss.org/browse/JBIDE-16317 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.2.0.Alpha1 > Reporter: Nick Boldt > Fix For: 4.2.0.Alpha1 > > > Project leads, please tag your projects! > {code} > co jbosstools-4.2.0.Alpha1x > git tag jbosstools-4.2.0.Alpha1 > git push origin jbosstools-4.2.0.Alpha1 > {code} -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15135) Attach metadata during assembly instead of publish time

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15135?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-15135: ---------------------------------------- Even easier would be to put build metadata directly in p2 repo (or vice-versa) so we're publication-agnostic (can publish site with any mechanism and this would still work). > Attach metadata during assembly instead of publish time > ------------------------------------------------------- > > Key: JBIDE-15135 > URL: https://issues.jboss.org/browse/JBIDE-15135 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Mickael Istria > Fix For: 4.2.x > > > In order to make it easier to deal with Nexus and to have an homogeneous way to access build metadata (commit id), it would be interesting to move creation of metadata at assembly time (same time as when we create index and so on), and put it directly into the site. > Then whether we use Nexus or a home-made publication, we are sure that we can access metadata whenever we can access the binaries. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-3628) Plugins should be .jar's not directories for efficiency sake

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-3628?page=com.atlassian.jira.plugin... ] Mickael Istria commented on JBIDE-3628: --------------------------------------- While hibernate.libs , xpcom or xulrunner contains some resources (jar, .o or .dll) that may need to be directly accessible in filesystem, there is IMO no obvious reason for other bundles to be unpacked. > Plugins should be .jar's not directories for efficiency sake > ------------------------------------------------------------ > > Key: JBIDE-3628 > URL: https://issues.jboss.org/browse/JBIDE-3628 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build, common/jst/core, freemarker, hibernate, jsf, visual-page-editor-core > Reporter: Max Rydahl Andersen > Assignee: Denis Golovin > Priority: Critical > Fix For: 4.2.0.Alpha2 > > Attachments: exception.log > > > 65 of our plugins are bundled exploded instead of a .jar > Some are probably just mistakes and can easily be packed others are because of legacy code assuming it can access the files directly and even store data in the plugins - that should be fixed. > What should be fixed: > 1. The way how plug-ins use images in plugin.xml, in java code and in .meta xmodel files > 2. Plug-ins that loads resources should be aware that they are in jar now (VPE should be able to load templates from plugin jar files) > 3. Some plug-ins contain resources registered in XML catalog > 4. common.projecttemplates contains resources that is used as template for new projects > 5. Help content that is stored in zip files should be unpacked > 6. TBD -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-80) "JavaBuilder handling CoreException while building: " appeares after import Spring project as existing project into workspace

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-80?page=com.atlassian.jira.plugin.sy... ] Mickael Istria commented on JBDS-80: ------------------------------------ Can we make this issue as "Out of Date" ? > "JavaBuilder handling CoreException while building: " appeares after import Spring project as existing project into workspace > ----------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-80 > URL: https://issues.jboss.org/browse/JBDS-80 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: 3rd-party-dependencies > Affects Versions: 1.0.0.GA > Reporter: Anton Klimkovich > Priority: Optional > Fix For: LATER > > Attachments: 111.txt > > > Take Spring project for import from http://jira.jboss.com/jira/browse/RHDS-114 (Pizza.zip) > Import Spring project as existing project into workspace > Log attached. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-63) Add Spring project nature in right click menu is cluttering

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-63?page=com.atlassian.jira.plugin.sy... ] Mickael Istria commented on JBDS-63: ------------------------------------ Is the issue still here with more recent JBDS and Spring IDE ? > Add Spring project nature in right click menu is cluttering > ----------------------------------------------------------- > > Key: JBDS-63 > URL: https://issues.jboss.org/browse/JBDS-63 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: 3rd-party-dependencies > Affects Versions: 1.0.0.GA > Reporter: Max Rydahl Andersen > Priority: Optional > Fix For: LATER > > > issue with springide but affects us -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-631) Reverse Step filtering in Dev. studio

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-631?page=com.atlassian.jira.plugin.s... ] Mickael Istria commented on JBDS-631: ------------------------------------- [~maxandersen] I don't understand the context of this issue? Should it be moved to a JBoss Tools component, or upstream to Eclipse? > Reverse Step filtering in Dev. studio > ------------------------------------- > > Key: JBDS-631 > URL: https://issues.jboss.org/browse/JBDS-631 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: 3rd-party-dependencies > Affects Versions: 2.0.0.cr2 > Reporter: Shaun Appleton > Fix For: LATER > > > Would it be possible to have an option to reverse the step filtering? Ie. to have the filters be inclusion instead of exclusion filters? > I am unsure about the normal case in enterprise development but in our case at least all packages are prefixed dk.telenor.* > It would be very useful if it where possible to specify just one debugging step filter (ie. include dk.telenor packages). > Workaround is to add all possible packages, select all then un-select the ones you are interested in. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-1205) uninstall and launch icon is directly in Development instead of Folder

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-1205?page=com.atlassian.jira.plugin.... ] Mickael Istria commented on JBDS-1205: -------------------------------------- Is it still true with more recent version of JBDS & Fedora/RHEL ? > uninstall and launch icon is directly in Development instead of Folder > ---------------------------------------------------------------------- > > Key: JBDS-1205 > URL: https://issues.jboss.org/browse/JBDS-1205 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: installer > Affects Versions: 3.0.0.GA > Reporter: Max Rydahl Andersen > Priority: Minor > Fix For: LATER > > > Before we had the launcher and uninstaller in a folder; now they are both directly in the Develoment menu. > Is that intentional ? -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-1221) Add right tray to dialogs to have some extra space for documentation an links to external documents

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-1221?page=com.atlassian.jira.plugin.... ] Mickael Istria commented on JBDS-1221: -------------------------------------- What's the context of this issue? It seems very old and it doesn't seem to relate to anything still relevant in JBDS 6 and later. Should it be closed as Out Of Date? > Add right tray to dialogs to have some extra space for documentation an links to external documents > --------------------------------------------------------------------------------------------------- > > Key: JBDS-1221 > URL: https://issues.jboss.org/browse/JBDS-1221 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: installer > Affects Versions: 3.0.1.GA > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 4.x > > -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-1230) JBoss Developer 3.0 Installing in a a newly installed RHEL 5.4 does not show up in the applications menu

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-1230?page=com.atlassian.jira.plugin.... ] Mickael Istria closed JBDS-1230. -------------------------------- Resolution: Out of Date > JBoss Developer 3.0 Installing in a a newly installed RHEL 5.4 does not show up in the applications menu > -------------------------------------------------------------------------------------------------------- > > Key: JBDS-1230 > URL: https://issues.jboss.org/browse/JBDS-1230 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: installer > Affects Versions: 3.0.0.GA > Environment: RHEL 5.4 with Sun JDK 5.4 > Reporter: Jim Tyrrell > Assignee: Denis Golovin > Priority: Minor > Fix For: 4.x > > Attachments: Starting JBDS.png > > > When going through the installer on a clean RHEL 5.4 system, the Programming Tools Listing under the Applications in the main menu bar does not show up until a reboot. Once it has been installed at least once, this does not seem to be a problem -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-1609) Installer should check system prerequisites and warn user if they are not fullfilled

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-1609?page=com.atlassian.jira.plugin.... ] Mickael Istria commented on JBDS-1609: -------------------------------------- Reducing priority because it seems to me we didn't have many complaints on this topic. Not sure it's worth the effort. > Installer should check system prerequisites and warn user if they are not fullfilled > ------------------------------------------------------------------------------------ > > Key: JBDS-1609 > URL: https://issues.jboss.org/browse/JBDS-1609 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: installer > Affects Versions: 4.0.0.GA > Reporter: Jiri Peterka > Assignee: Denis Golovin > Priority: Minor > Fix For: 8.0.0.Alpha2 > > > To prevent insufficient machine parameters or setting installer should do basic check for some parameters like: > - memory amount > - maximum open file limit > - maximum thread count limit > - internet connection > - others reasonable criteria should be added here > If these criteria aren't met, installer should display add warning page before further installation saying that requirements aren't satisfied and tools may not work properly. Reason for this is that sometimes JBDS is used in very strict environment (typically training rooms, universities, etc where many system resources are limited or blocked) but user isn't warned and after install user can see after that lots of runtime errors and got bad feeling about the tool. This should be avoided and user should be at least warn that he is running JBDS in inappropriate environment. -- 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, 3 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 December 2013