June 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-20157) Under GTK2 at first start Webkit is used as a default browser, but in preferences JSF mode is selected

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20157?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov reassigned JBIDE-20157: ---------------------------------------------- Assignee: Konstantin Marmalyukov > Under GTK2 at first start Webkit is used as a default browser, but in preferences JSF mode is selected > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-20157 > URL: https://issues.jboss.org/browse/JBIDE-20157 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core > Affects Versions: 4.3.0.Beta1 > Reporter: Konstantin Marmalyukov > Assignee: Konstantin Marmalyukov > Fix For: 4.3.0.Beta2 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20157) Under GTK2 at first start Webkit is used as a default browser, but in preferences JSF mode is selected

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20157?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov updated JBIDE-20157: ------------------------------------------- Fix Version/s: 4.3.0.Beta2 > Under GTK2 at first start Webkit is used as a default browser, but in preferences JSF mode is selected > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-20157 > URL: https://issues.jboss.org/browse/JBIDE-20157 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core > Affects Versions: 4.3.0.Beta1 > Reporter: Konstantin Marmalyukov > Assignee: Konstantin Marmalyukov > Fix For: 4.3.0.Beta2 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18848) setup tests for ide-config.properties

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18848?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-18848: ------------------------------------- I can't guarantee taking care of that one before beta2. Someone else would need to take ownership > setup tests for ide-config.properties > ------------------------------------- > > Key: JBIDE-18848 > URL: https://issues.jboss.org/browse/JBIDE-18848 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build, common/jst/core > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Fix For: 4.3.0.CR1 > > > JBIDE-18837 and other jiras showed that ide-config.properties risk having errors introduced into it. > we should have a test that runs every day to check if it is still consistent. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18848) setup tests for ide-config.properties

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18848?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-18848: ------------------------------------ Any more thoughts on this? If we're going to do it, we need to get it into Beta2 soon. cc: [~fbricon] [~maxandersen] [~mickael_istria] [~dgolovin] > setup tests for ide-config.properties > ------------------------------------- > > Key: JBIDE-18848 > URL: https://issues.jboss.org/browse/JBIDE-18848 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build, common/jst/core > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Fix For: 4.3.0.CR1 > > > JBIDE-18837 and other jiras showed that ide-config.properties risk having errors introduced into it. > we should have a test that runs every day to check if it is still consistent. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19757) Use jbosstools aggregate site instead of special webtools-site for WTP's AS server discovery

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19757?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-19757: ------------------------------------ Release guide updated: https://github.com/jbdevstudio/jbdevstudio-devdoc/commit/50fc16d0ecfcec0c... Closing. > Use jbosstools aggregate site instead of special webtools-site for WTP's AS server discovery > -------------------------------------------------------------------------------------------- > > Key: JBIDE-19757 > URL: https://issues.jboss.org/browse/JBIDE-19757 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build, server > Reporter: Mickael Istria > Assignee: Nick Boldt > Priority: Minor > Labels: releasework > Fix For: 4.3.0.Beta1 > > > With https://bugs.eclipse.org/bugs/show_bug.cgi?id=434185 , WTP Server Discovery mechanism was granted a new strategy which allows to rely on regular p2 metadata instead of a site.xml. > Support for this was already merged in server ( https://github.com/jbosstools/jbosstools-server/commit/2d3cc63a9b67753ad9... ) > In order to save an artifact to manage (the webtools p2 repository), we could use this mechanism and consider contributing directly the main JBT URL to webtools discovery. > However, server discovery also keeps older strategies and since we produce invalid site.xml files, this is currently failing > {code} > !ENTRY org.eclipse.equinox.p2.updatesite 2 0 2015-05-04 09:40:58.088 > !MESSAGE Error parsing feature stream. The unique identifier or the version is null or empty for the State: "Category": unique identifier="minimal-json" version="null". > {code} > because we are lines specifying bundle but no version in the site.xml. > [~nickboldt] What are those site.xml useful for? Could we get rid of them? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3191) Improve the way we switch between development and GA

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-3191?page=com.atlassian.jira.plugin.... ] Fred Bricon updated JBDS-3191: ------------------------------ Fix Version/s: 9.0.0.CR1 (was: 9.0.0.Beta2) > Improve the way we switch between development and GA > ---------------------------------------------------- > > Key: JBDS-3191 > URL: https://issues.jboss.org/browse/JBDS-3191 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: build > Reporter: Mickael Istria > Assignee: Fred Bricon > Fix For: 9.0.0.CR1 > > > JBDS-3190 has shown that there are too many changes to perform when willing to create a GA candidate, and it's almost certain that we'll forever forget to change one or some of them when switching between GA and development stream. > We need to improve that. > Changes are necessary in: > * features/com.jboss.devstudio.core/feature/p2.inf > * site/associate.properties > * results/pom.xml > As an alternative, I suggest that the final site be ALWAYS added to the referenced site, even if it's empty. This has no cost for build nor user, and this would simplify a few things here and there. > Also, instead of a p2.inf, we could think a a "startup" extension that would add reference to development site in case qualifier for the feature doesn't contain GA. > The property to the "current site" (GA or development) could be factorized in JBDS parent pom. so that both results/pom.xml and site/pom.xml could use it (instead of associateSites.properties). > CC [~nickboldt] [~maxandersen] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19757) Use jbosstools aggregate site instead of special webtools-site for WTP's AS server discovery

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19757?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-19757. ------------------------------ Resolution: Done > Use jbosstools aggregate site instead of special webtools-site for WTP's AS server discovery > -------------------------------------------------------------------------------------------- > > Key: JBIDE-19757 > URL: https://issues.jboss.org/browse/JBIDE-19757 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build, server > Reporter: Mickael Istria > Assignee: Nick Boldt > Priority: Minor > Labels: releasework > Fix For: 4.3.0.Beta1 > > > With https://bugs.eclipse.org/bugs/show_bug.cgi?id=434185 , WTP Server Discovery mechanism was granted a new strategy which allows to rely on regular p2 metadata instead of a site.xml. > Support for this was already merged in server ( https://github.com/jbosstools/jbosstools-server/commit/2d3cc63a9b67753ad9... ) > In order to save an artifact to manage (the webtools p2 repository), we could use this mechanism and consider contributing directly the main JBT URL to webtools discovery. > However, server discovery also keeps older strategies and since we produce invalid site.xml files, this is currently failing > {code} > !ENTRY org.eclipse.equinox.p2.updatesite 2 0 2015-05-04 09:40:58.088 > !MESSAGE Error parsing feature stream. The unique identifier or the version is null or empty for the State: "Category": unique identifier="minimal-json" version="null". > {code} > because we are lines specifying bundle but no version in the site.xml. > [~nickboldt] What are those site.xml useful for? Could we get rid of them? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20152) script the process of branching and tagging based on buildinfo.json

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20152?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-20152: ------------------------------- Git Pull Request: https://github.com/jbdevstudio/jbdevstudio-ci/pull/152, https://github.com/jbosstools/jbosstools-build-ci/pull/132 (was: https://github.com/jbdevstudio/jbdevstudio-ci/pull/152) > script the process of branching and tagging based on buildinfo.json > ------------------------------------------------------------------- > > Key: JBIDE-20152 > URL: https://issues.jboss.org/browse/JBIDE-20152 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Beta1 > Reporter: Nick Boldt > Assignee: Max Rydahl Andersen > Fix For: 4.3.0.Beta2 > > > {quote} > Last time I suggested we created a file with a line for each repo, like: > {code}jbosstools/jbosstools-hibernate, 13asd123asd232, jbosstools-4.3.0.Beta1{code} > You had a txt file before that had this information but in a hard-to-parse format. > I can try parse the buildinfo.json too but thought if you had the simpler one I could use that instead. > /max {quote} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20152) script the process of branching and tagging based on buildinfo.json

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20152?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-20152: ------------------------------------ Max's response: https://github.com/jbosstools/jbosstools-build-ci/pull/132 > script the process of branching and tagging based on buildinfo.json > ------------------------------------------------------------------- > > Key: JBIDE-20152 > URL: https://issues.jboss.org/browse/JBIDE-20152 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Beta1 > Reporter: Nick Boldt > Assignee: Max Rydahl Andersen > Fix For: 4.3.0.Beta2 > > > {quote} > Last time I suggested we created a file with a line for each repo, like: > {code}jbosstools/jbosstools-hibernate, 13asd123asd232, jbosstools-4.3.0.Beta1{code} > You had a txt file before that had this information but in a hard-to-parse format. > I can try parse the buildinfo.json too but thought if you had the simpler one I could use that instead. > /max {quote} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[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 reassigned JBIDE-20100: ----------------------------------- Assignee: Mickael Istria > 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 > > [~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, 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