June 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3446) Add support for IzPack INSTALL_PATH property to predefine installation path

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3446?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3446: ----------------------------- CDW pm_ack: ? > Add support for IzPack INSTALL_PATH property to predefine installation path > --------------------------------------------------------------------------- > > Key: JBDS-3446 > URL: https://issues.jboss.org/browse/JBDS-3446 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 8.1.0.GA > Reporter: Martin Malina > Assignee: Denis Golovin > Fix For: 9.0.0.Beta2 > > > In a recent discussion around JBIDE-19852 , it was pointed out that IzPack supports supplying properties to the installer, so that some values are predefined. > Details are here: > http://docs.codehaus.org/display/IZPACK/Unattended+Installations > The idea is that you could run this: > java -DINSTALL_PATH=/default/path -jar installer.jar > And this would pre-fill the installation path to the path given in the command. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3446) Add support for IzPack INSTALL_PATH property to predefine installation path

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3446?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3446: -------------------------------- CDW release: ? Status: New (was: New) Target Release: 9.0.0.GA > Add support for IzPack INSTALL_PATH property to predefine installation path > --------------------------------------------------------------------------- > > Key: JBDS-3446 > URL: https://issues.jboss.org/browse/JBDS-3446 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 8.1.0.GA > Reporter: Martin Malina > Assignee: Denis Golovin > Fix For: 9.0.0.Beta2 > > > In a recent discussion around JBIDE-19852 , it was pointed out that IzPack supports supplying properties to the installer, so that some values are predefined. > Details are here: > http://docs.codehaus.org/display/IZPACK/Unattended+Installations > The idea is that you could run this: > java -DINSTALL_PATH=/default/path -jar installer.jar > And this would pre-fill the installation path to the path given in the command. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3446) Add support for IzPack INSTALL_PATH property to predefine installation path

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3446?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-3446: ------------------------------------- There are three modes available for installer: 1. GUI 2. Console 3. Automated Current installer supports only (1) and (2). To run in console mode use: {code}java -jar insatller.jar -console {code} It shows license text on console and prompts for input {code}press 1 to accept, 2 to reject, 3 to redisplay{code} after answering (1) it goes further but fails because our panels do not support console mode. {code}[ Starting to unpack ] [ Processing package: P2 Director Application (1/4) ] [ Processing package: Red Hat JBoss Developer Studio 9.0.0.Beta1 (2/4) ] [ Processing package: Red Hat JBoss Developer Studio 9.0.0.Beta1 Metadata Generation (3/4) ] [ Processing package: JBoss Enterprise Application Platform (4/4) ] [ WARNING: Error executing /bin/chmod a+x /home/eskimo/jbdevstudio/runtimes/jboss-eap/bin/init.d/jboss-as-standalone.sh ] [ ERROR: The installation was not completed ] [ Unpacking finished ]{code} > Add support for IzPack INSTALL_PATH property to predefine installation path > --------------------------------------------------------------------------- > > Key: JBDS-3446 > URL: https://issues.jboss.org/browse/JBDS-3446 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 8.1.0.GA > Reporter: Martin Malina > Assignee: Denis Golovin > Fix For: 9.0.0.Beta2 > > > In a recent discussion around JBIDE-19852 , it was pointed out that IzPack supports supplying properties to the installer, so that some values are predefined. > Details are here: > http://docs.codehaus.org/display/IZPACK/Unattended+Installations > The idea is that you could run this: > java -DINSTALL_PATH=/default/path -jar installer.jar > And this would pre-fill the installation path to the path given in the command. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3446) Add support for IzPack INSTALL_PATH property to predefine installation path

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3446?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3446: -------------------------------- Fix Version/s: 9.0.0.Beta2 > Add support for IzPack INSTALL_PATH property to predefine installation path > --------------------------------------------------------------------------- > > Key: JBDS-3446 > URL: https://issues.jboss.org/browse/JBDS-3446 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 8.1.0.GA > Reporter: Martin Malina > Assignee: Denis Golovin > Fix For: 9.0.0.Beta2 > > > In a recent discussion around JBIDE-19852 , it was pointed out that IzPack supports supplying properties to the installer, so that some values are predefined. > Details are here: > http://docs.codehaus.org/display/IZPACK/Unattended+Installations > The idea is that you could run this: > java -DINSTALL_PATH=/default/path -jar installer.jar > And this would pre-fill the installation path to the path given in the command. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (LOCUS-42) Update locus to include jsonschema2pojo-core jar, jaxb-xjc.jar and jaxb-impl.jar.

by Keith Babo (JIRA)

[ https://issues.jboss.org/browse/LOCUS-42?page=com.atlassian.jira.plugin.s... ] Keith Babo edited comment on LOCUS-42 at 6/2/15 12:45 PM: ---------------------------------------------------------- We rely on JAXB for annotations but also for XJC to generate Java classes from XML schema. We also use JCodeModel, which happens to be packaged with jaxb-xjc, but I think that's also available as an independent jar. I should mention that jsonschema2pojo is independent of jaxb, so the they can be treated independently in terms of adding them to Locus (add jsonschema2pojo now and figure out what to do with jaxb separately). was (Author: kcbabo): We rely on JAXB for annotations but also for XJC to generate Java classes from XML schema. We also use JCodeModel, which happens to be packaged with jaxb-xjc, but I think that's also available as an independent jar. I should mention that jsonschema2pojo is independent of jaxb-*, so the they can be treated independently in terms of adding them to Locus (add jsonschema2pojo now and figure out what to do with jaxb-* separately). > Update locus to include jsonschema2pojo-core jar, jaxb-xjc.jar and jaxb-impl.jar. > --------------------------------------------------------------------------------- > > Key: LOCUS-42 > URL: https://issues.jboss.org/browse/LOCUS-42 > Project: JBoss Tools Locus > Issue Type: Feature Request > Affects Versions: 1.2.0 > Reporter: Paul Leacu > Assignee: Mickael Istria > Fix For: 1.3.0 > > > Request three new jars in Locus 1.3.0: > jsonschema2pojo-core jar > jaxb-xjc jar > jaxb-impl jar > Fuse Data Transformation tooling relies on jsonschema2pojo to generate model classes from JSON schema and JSON instance documents. Need to capture the jar in locus for inclusion into JBTIS target platform and ultimately Data Transformation tooling (Fuse). > https://repo1.maven.org/maven2/org/jsonschema2pojo/jsonschema2pojo-core/0... > https://repo1.maven.org/maven2/org/jsonschema2pojo/jsonschema2pojo-core/0... > https://repo1.maven.org/maven2/com/sun/xml/bind/jaxb-xjc/2.2.7/jaxb-xjc-2... > https://repo1.maven.org/maven2/com/sun/xml/bind/jaxb-xjc/2.2.7/jaxb-xjc-2... > https://repo1.maven.org/maven2/com/sun/xml/bind/jaxb-impl/2.2.7/jaxb-impl... > https://repo1.maven.org/maven2/com/sun/xml/bind/jaxb-impl/2.2.7/jaxb-impl... > This is needed for Mars/ 9.0.x JBDSIS target platform inclusion. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (LOCUS-42) Update locus to include jsonschema2pojo-core jar, jaxb-xjc.jar and jaxb-impl.jar.

by Keith Babo (JIRA)

[ https://issues.jboss.org/browse/LOCUS-42?page=com.atlassian.jira.plugin.s... ] Keith Babo commented on LOCUS-42: --------------------------------- We rely on JAXB for annotations but also for XJC to generate Java classes from XML schema. We also use JCodeModel, which happens to be packaged with jaxb-xjc, but I think that's also available as an independent jar. I should mention that jsonschema2pojo is independent of jaxb-*, so the they can be treated independently in terms of adding them to Locus (add jsonschema2pojo now and figure out what to do with jaxb-* separately). > Update locus to include jsonschema2pojo-core jar, jaxb-xjc.jar and jaxb-impl.jar. > --------------------------------------------------------------------------------- > > Key: LOCUS-42 > URL: https://issues.jboss.org/browse/LOCUS-42 > Project: JBoss Tools Locus > Issue Type: Feature Request > Affects Versions: 1.2.0 > Reporter: Paul Leacu > Assignee: Mickael Istria > Fix For: 1.3.0 > > > Request three new jars in Locus 1.3.0: > jsonschema2pojo-core jar > jaxb-xjc jar > jaxb-impl jar > Fuse Data Transformation tooling relies on jsonschema2pojo to generate model classes from JSON schema and JSON instance documents. Need to capture the jar in locus for inclusion into JBTIS target platform and ultimately Data Transformation tooling (Fuse). > https://repo1.maven.org/maven2/org/jsonschema2pojo/jsonschema2pojo-core/0... > https://repo1.maven.org/maven2/org/jsonschema2pojo/jsonschema2pojo-core/0... > https://repo1.maven.org/maven2/com/sun/xml/bind/jaxb-xjc/2.2.7/jaxb-xjc-2... > https://repo1.maven.org/maven2/com/sun/xml/bind/jaxb-xjc/2.2.7/jaxb-xjc-2... > https://repo1.maven.org/maven2/com/sun/xml/bind/jaxb-impl/2.2.7/jaxb-impl... > https://repo1.maven.org/maven2/com/sun/xml/bind/jaxb-impl/2.2.7/jaxb-impl... > This is needed for Mars/ 9.0.x JBDSIS target platform inclusion. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19853) GTK3 (only): Erroneous labels in application wizard tree

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19853?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-19853: --------------------------------------- I have created a workaround that is limited to GTK3 because it disables styled cell label provider (ApplicationTemplateViewLabelProvider). We would need to remove it after apply the fix for https://bugs.eclipse.org/bugs/show_bug.cgi?id=466499. > GTK3 (only): Erroneous labels in application wizard tree > -------------------------------------------------------- > > Key: JBIDE-19853 > URL: https://issues.jboss.org/browse/JBIDE-19853 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, upstream > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Max Rydahl Andersen > Priority: Blocker > Labels: application_wizard > Fix For: 4.3.0.Beta1 > > Attachments: gtk2-new-app-wizard-1.png, gtk2-new-app-wizard-2.png, gtk3-new-app-wizard-1.png, gtk3-new-app-wizard-2.png > > > When run in GTK3 the tree in the v2 application wizard is showing completely erroneous labels. The labels even switch content when the tree items are unfolded. > When running Eclipse using (export SWT_GTK3=0) the tree in the application wizard looks in the following correct way: > !gtk2-new-app-wizard-1.png! > unfolding the "Basic Cartridges" produces the following: > !gtk2-new-app-wizard-2.png! > Without the above env variable, which makes Eclipse use GTK3, the application wizard looks as follows: > !gtk3-new-app-wizard-1.png! > ... and when unfolding "Basic Cartridges" the labels for the 3 main cathegories and all the children change to display the same: > !gtk3-new-app-wizard-2.png! -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19820) Batch feature makes wildfly import way slower

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19820?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-19820: ----------------------------------- Fix Version/s: 4.3.0.Beta2 (was: 4.3.0.Beta1) Thanks for testing! So, It's better in Beta1 now but let's see what we can do else. Moving to Beta2. > Batch feature makes wildfly import way slower > --------------------------------------------- > > Key: JBIDE-19820 > URL: https://issues.jboss.org/browse/JBIDE-19820 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: batch > Affects Versions: 4.3.0.Alpha2 > Reporter: Rastislav Wagner > Assignee: Viacheslav Kabanovich > Priority: Critical > Fix For: 4.3.0.Beta2 > > > I made a comparison between Eclipse M6 and Eclipse M6 with batch feature installed while importing wildfly. WF is imported as maven project, maven is set to offline mode and local repository contains all needed dependencies. > I did a 4 runs with following results: > M6 was able to import WF 628,575,577,612 (in seconds) = average 598s > M6 with batch feature: 843,832,924,877 (in seconds) = average 869s -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3446) Add support for IzPack INSTALL_PATH property to predefine installation path

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3446?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-3446: ------------------------------------- IMO this feature is easy to implement, but it is really useless. There is no difference if one type location in console or in PathSelectionPanel field, it still typing :) It might be good idea to implement support for this as simple way to do headless installation. For example if -DINSTALL_PATH=/path/to/target is added in to java cmd it would skip UI and just do automated install into provided directory without automated install xml file. > Add support for IzPack INSTALL_PATH property to predefine installation path > --------------------------------------------------------------------------- > > Key: JBDS-3446 > URL: https://issues.jboss.org/browse/JBDS-3446 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 8.1.0.GA > Reporter: Martin Malina > Assignee: Denis Golovin > > In a recent discussion around JBIDE-19852 , it was pointed out that IzPack supports supplying properties to the installer, so that some values are predefined. > Details are here: > http://docs.codehaus.org/display/IZPACK/Unattended+Installations > The idea is that you could run this: > java -DINSTALL_PATH=/default/path -jar installer.jar > And this would pre-fill the installation path to the path given in the command. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19899) Add usage tracking of which browser name and version is used

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19899?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-19899: ----------------------------------- Labels: new_and_noteworthy (was: ) > Add usage tracking of which browser name and version is used > ------------------------------------------------------------ > > Key: JBIDE-19899 > URL: https://issues.jboss.org/browse/JBIDE-19899 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central, usage > Affects Versions: 4.3.0.Beta1 > Reporter: Konstantin Marmalyukov > Assignee: Konstantin Marmalyukov > Labels: new_and_noteworthy > Fix For: 4.3.0.Beta1 > > > There will be good to know which browser our users have. Central is the best place for that: it will be opened at least at the first start and already has an API which detects browser name and version. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 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 June 2015