December 2013 - jbosstools-issues

[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 updated JBDS-1609: --------------------------------- Priority: Minor (was: Critical) > 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

[JBoss JIRA] (JBDS-1991) Migrate IzPack Installer Build to maven

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-1991?page=com.atlassian.jira.plugin.... ] Mickael Istria updated JBDS-1991: --------------------------------- Fix Version/s: 8.0.0.Alpha2 (was: 8.0.0.Alpha1) > Migrate IzPack Installer Build to maven > --------------------------------------- > > Key: JBDS-1991 > URL: https://issues.jboss.org/browse/JBDS-1991 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: build, installer > Affects Versions: 5.0.0.Beta1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 8.0.0.Alpha2 > > -- 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 updated JBDS-1609: --------------------------------- Fix Version/s: 8.0.0.Alpha2 (was: 8.0.0.Alpha1) > 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: Critical > 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

[JBoss JIRA] (JBDS-2258) Console log output gone with "Run as Java Application" and using org.apache.commons.logging.LogFactory

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-2258?page=com.atlassian.jira.plugin.... ] Mickael Istria commented on JBDS-2258: -------------------------------------- Is this still true in the recent (or supported) versions of JBDS? > Console log output gone with "Run as Java Application" and using org.apache.commons.logging.LogFactory > ------------------------------------------------------------------------------------------------------ > > Key: JBDS-2258 > URL: https://issues.jboss.org/browse/JBDS-2258 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build > Affects Versions: 5.0.1.GA > Reporter: Denis Golovin > Assignee: Denis Golovin > Priority: Minor > Fix For: LATER > > Attachments: logTest.zip > > > It seems problem appears only in JBDS 5 started on workspace prior used in JBDS 4. -- 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-2065) Installer doesn't let add locations to detect runtimes if started with -DTRACE=TRUE

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-2065?page=com.atlassian.jira.plugin.... ] Mickael Istria updated JBDS-2065: --------------------------------- Fix Version/s: 8.0.0.Alpha2 (was: 8.0.0.Alpha1) > Installer doesn't let add locations to detect runtimes if started with -DTRACE=TRUE > ----------------------------------------------------------------------------------- > > Key: JBDS-2065 > URL: https://issues.jboss.org/browse/JBDS-2065 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: installer, upstream > Affects Versions: 5.0.0.M5 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 8.0.0.Alpha2 > > Attachments: Screen Shot 2012-03-09 at 10.05.17.jpg > > -- 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-16317) Tag projects for jbosstools-4.2.0.Alpha1

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16317?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-16317: --------------------------------------- done for LiveReload and WebServices > 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] (JBDS-2293) deprecation warning in installer build - warning: sun.swing.DefaultLookup is Sun proprietary API and may be removed in a future release

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-2293?page=com.atlassian.jira.plugin.... ] Mickael Istria updated JBDS-2293: --------------------------------- Fix Version/s: 8.0.0.Alpha2 (was: 8.0.0.Alpha1) > deprecation warning in installer build - warning: sun.swing.DefaultLookup is Sun proprietary API and may be removed in a future release > --------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-2293 > URL: https://issues.jboss.org/browse/JBDS-2293 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: installer > Affects Versions: 6.0.0.Beta1 > Reporter: Nick Boldt > Assignee: Denis Golovin > Fix For: 8.0.0.Alpha2 > > > {code} > cd ~/trunk/product > mvn clean install > ... > buildcustompanels: > [echo] Building panels ... > [echo] Build properties written to /home/nboldt/eclipse/workspace-jboss/devstudio_trunk/product/installer/target/../../jbds-echoproperties.txt > [mkdir] Created dir: /home/nboldt/eclipse/workspace-jboss/devstudio_trunk/product/installer/target/classes > [mkdir] Created dir: /home/nboldt/eclipse/workspace-jboss/devstudio_trunk/product/installer/target/izpack-panels > [unjar] Expanding: /home/nboldt/eclipse/workspace-jboss/devstudio_trunk/product/installer/target/IzPack-4.3.4/lib/standalone-compiler.jar into /home/nboldt/eclipse/workspace-jboss/devstudio_trunk/product/installer/target/izpack-panels > [javac] Compiling 29 source files to /home/nboldt/eclipse/workspace-jboss/devstudio_trunk/product/installer/target/classes > /home/nboldt/eclipse/workspace-jboss/devstudio_trunk/product/installer/src/panels/com/jboss/jbds/installer/ErrorUtils.java:21: warning: sun.swing.DefaultLookup is Sun proprietary API and may be removed in a future release > import sun.swing.DefaultLookup; > ^ > /home/nboldt/eclipse/workspace-jboss/devstudio_trunk/product/installer/src/panels/com/jboss/jbds/installer/ErrorUtils.java:32: warning: sun.swing.DefaultLookup is Sun proprietary API and may be removed in a future release > Icon icon = (Icon)DefaultLookup.get(label, label.getUI(), "OptionPane.errorIcon"); > ^ > Note: Some input files use unchecked or unsafe operations. > Note: Recompile with -Xlint:unchecked for details. > 2 warnings > {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] (JBDS-2623) Create target platform for mirrored parts of Central / 3rd Party Extras

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-2623?page=com.atlassian.jira.plugin.... ] Mickael Istria commented on JBDS-2623: -------------------------------------- [~nickboldt] Isn't this issue resolved? > Create target platform for mirrored parts of Central / 3rd Party Extras > ----------------------------------------------------------------------- > > Key: JBDS-2623 > URL: https://issues.jboss.org/browse/JBDS-2623 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: 3rd-party-certification, 3rd-party-dependencies, central, requirements, updatesite, upstream > Affects Versions: 7.0.0.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 7.1.0.GA > > Attachments: 2623-manual-hack.png, 2623-p2browser-shows-datanucleus-missing.png, 2623-remove-and-regen.png > > > As discussed in JBDS-2486 ( https://issues.jboss.org/browse/JBDS-2486?focusedCommentId=12770186&page=... ) we need to produce a target file for use with Central. > Goal here would be to build the Extras site (used by Central) as a TP update site rather than a composite of mirrors, which would provide us with a manifest of exactly which versions of these duped IUs were to be contained in the Extras site. If something bad happens, we can add duplicate versions of IUs to the TP and know exactly why we include both Jetty 8.1.3 and 8.1.9 (for example) or two different spins of WindowBuilder. This would mean it wouldn't matter if we filtered content out of the mirrors, because we'd be handling the filtering in a single place (extras.target) rather than multiple build.xml files. > In future, we would: > * mirror the individual upstream projects into /updates/requirements/<project> [on dl.jb.org] > * mirror the individual upstream projects into /updates/requirements/<project> [on www.qa] > * produce an aggregate of the stuff that Central needs, and publish that instead of the composite [on dl.jb.org] > * produce an aggregate of the stuff that Central needs, and publish that instead of the composite [on www.qa] > * produce an aggregate of the stuff that Central needs, and publish that instead of the composite [on ds.jb.com] > * add a whole new aggregate for old + new content -- 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-2649) Installer shouldn't contain Google Eclipse features/plugins

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-2649?page=com.atlassian.jira.plugin.... ] Mickael Istria updated JBDS-2649: --------------------------------- Priority: Minor (was: Major) > Installer shouldn't contain Google Eclipse features/plugins > ----------------------------------------------------------- > > Key: JBDS-2649 > URL: https://issues.jboss.org/browse/JBDS-2649 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: installer > Affects Versions: 6.0.1.GA > Reporter: Fred Bricon > Assignee: Denis Golovin > Priority: Minor > Fix For: 8.0.0.Alpha2 > > Attachments: jbds2649-maven-gwt-no-longer-installed-by-default.png, JBDS2649.patch.txt > > > jbdevstudio-product-eap-universal-7.0.0.Beta1-v20130526-0839-B241.jar contains the google plugins, it shouldn't : > !http://content.screencast.com/users/fbricon/folders/Jing/media/a7764301-6ad0-4631-b289-1e35683e3fb2/2013-05-29_0949.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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2635) Installation sometimes fail with bundle was not found on Windows

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-2635?page=com.atlassian.jira.plugin.... ] Mickael Istria updated JBDS-2635: --------------------------------- Fix Version/s: 8.0.0.Alpha2 (was: 8.0.0.Alpha1) > Installation sometimes fail with bundle was not found on Windows > ---------------------------------------------------------------- > > Key: JBDS-2635 > URL: https://issues.jboss.org/browse/JBDS-2635 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: installer > Affects Versions: 7.0.0.Beta1 > Environment: JBDS 7.0.0.Beta1, W8_64, Java 1.7.0_07 > Reporter: Jiri Peterka > Assignee: Denis Golovin > Fix For: 8.0.0.Alpha2 > > Attachments: 1369261136479.log, 1372203584223.log, 1372203590931.bak_0.log, 1372203590931.bak_1.log, 1372203590931.bak_2.log, 1372203590931.log, 1372355790692.log > > > For the first time JBDS 7.0.0.Beta1 failed on windows8: > {code} > An error occurred while installing the items > session context was:(profile=jbds, phase=org.eclipse.equinox.internal.p2.engine.phases.Install, operand=null --> [R]org.eclipse.jst.common.frameworks 1.1.601.v201208160700, action=org.eclipse.equinox.internal.p2.touchpoint.eclipse.actions.InstallBundleAction). > The artifact file for osgi.bundle,org.eclipse.jst.common.frameworks,1.1.601.v201208160700 was not found. > Application failed, log file location: C:\vw\jbds-7.0.0-beta1\studio\p2\director\configuration\1369261136579.log > {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

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