January 2015 - jbosstools-issues - Jboss List Archives

[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: ---------------------------------------- {quote}When is it available? How is it made available? How do you test this offline? How does the mojo know about upstream projects, since none of the jobs are linked in Jenkins?{quote} The mojo looks at the site referenced as "repositories" with layout type "p2" in the current reactor. Then it looks for a file ${repositoryUrl}/buildinfo.json for each referenced repository. To test it, generate for example a site for openshift module with the mojo, so that buildinfo.json exists, then try to build central similarily, but overriding the location for openshift to local one on filesystem. You'll see the upstream block will include some data from openshift. {quote}Why not also dump variables we know are important which are resolved from parent pom? Why only worry about CLI variables, not defaults too?{quote} The default ones can be deduced from that parent pom so I don't believe it's necessary to repeat them here. But if you think it's important, we can have a "cliOptions" block with the current behaviour, and a resolvedMavenProperties block with the main properties. {quote} Is it a lot of work to collect that information? {quote} I'm not concerned about the difficulty of collecting information, but more about giving interesting and easy to read reports. Being greedy in reports makes them more difficult to read. My strategy is to put them in only if we use them regularly, not if we may need it sometimes. But if it's a blocker for you, I'm fine with adding JVM and OS info to the report. > 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 > Assignee: 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 was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3302) Multiple org.eclipse.jdt.annotation plugins present in JBDS

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3302?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3302: ----------------------------- Attachment: jbds3302.png Both versions of jdt.annotation are in Luna R and SR1 and therefore also in our JBT and JBDS target platforms for JBDS 8.0.1. I'm not sure if we need both, but at least that's why they're there. > Multiple org.eclipse.jdt.annotation plugins present in JBDS > ----------------------------------------------------------- > > Key: JBDS-3302 > URL: https://issues.jboss.org/browse/JBDS-3302 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build > Affects Versions: 8.0.1.GA > Environment: JBDS 8.0.1.GA > Reporter: Jiri Peterka > Priority: Minor > Attachments: jbds3302.png > > > Since JBDS 8.0.0 there are multiple plugins for org.eclipse.jdt.annotation present, specifically 1.1.0 and 2.0.0 > Is there any reason for that? If yes, let's add it to known exceptions, if not older version should be probably removed. I haven't found any directly depending bundles after quick search. > Discovered by vwatch - http://download.jboss.org/jbosstools/builds/staging/devstudio.versionwatc... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18995) Early Access features can be installed from JBoss Tools p2 repository even if 'Enable Early Access' is disabled in Central

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18995?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-18995: ----------------------------------- Assignee: Mickael Istria > Early Access features can be installed from JBoss Tools p2 repository even if 'Enable Early Access' is disabled in Central > -------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-18995 > URL: https://issues.jboss.org/browse/JBIDE-18995 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: updatesite > Affects Versions: 4.2.1.Final > Reporter: Denis Golovin > Assignee: Mickael Istria > Priority: Minor > Attachments: ea-disabled.png, ea-installed.png > > > I noticed central has "(Early Access Installed)" sign in after I installed everything from JBos Tools stable p2 repository. > !ea-installed.png! > "Enable Early Access" checkbox is not set by default in Central Editor > !ea-disabled.png! > This means I bypassed warning dialog in this scenario. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-3235) Missing properties view for servers elements

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-3235?page=com.atlassian.jira.plugin... ] Rob Stryker commented on JBIDE-3235: ------------------------------------ The current double-click behavior is to run the "editFileAction", which opens the file for editing. Are you suggesting you would prefer the double-click action to be the "changeValueAction" instead, and if the user wishes to edit the file, he should right-click and select "Edit File"? I can make this happen easily with a 1 line patch. > Missing properties view for servers elements > -------------------------------------------- > > Key: JBIDE-3235 > URL: https://issues.jboss.org/browse/JBIDE-3235 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Priority: Minor > Fix For: 3.3.x > > > Before I could directly edit properties for ports in properties view. > Now I need to right click and choose Change Value and get a non-standard edit in the tree. > This I could probably live with if I could just double click the value and edit it like in properties view. > Properties view was though also nice to give other details than just access to edit. > i.e.. I could copy values to get the value of file names etc. I can't copy elements from the tree and get a textual representation. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18995) Early Access features can be installed from JBoss Tools p2 repository even if 'Enable Early Access' is disabled in Central

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18995?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-18995: --------------------------------------- Should we stop publishing EA features to stable update site? > Early Access features can be installed from JBoss Tools p2 repository even if 'Enable Early Access' is disabled in Central > -------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-18995 > URL: https://issues.jboss.org/browse/JBIDE-18995 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: updatesite > Affects Versions: 4.2.1.Final > Reporter: Denis Golovin > Priority: Minor > Attachments: ea-disabled.png, ea-installed.png > > > I noticed central has "(Early Access Installed)" sign in after I installed everything from JBos Tools stable p2 repository. > !ea-installed.png! > "Enable Early Access" checkbox is not set by default in Central Editor > !ea-disabled.png! > This means I bypassed warning dialog in this scenario. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18995) Early Access features can be installed from JBoss Tools p2 repository even if 'Enable Early Access' is disabled in Central

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18995?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-18995: ---------------------------------- Attachment: ea-disabled.png ea-installed.png > Early Access features can be installed from JBoss Tools p2 repository even if 'Enable Early Access' is disabled in Central > -------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-18995 > URL: https://issues.jboss.org/browse/JBIDE-18995 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: updatesite > Affects Versions: 4.2.1.Final > Reporter: Denis Golovin > Priority: Minor > Attachments: ea-disabled.png, ea-installed.png > > > I noticed central has "(Early Access Installed)" sign in after I installed everything from JBos Tools stable p2 repository. > !ea-installed.png! > "Enable Early Access" checkbox is not set by default in Central Editor > !ea-disabled.png! > This means I bypassed warning dialog in this scenario. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3289) JBoss Central proxy wizards need to recognize early access.

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3289?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-3289: ------------------------------------- Similar problem is JBIDE-18995, when early access features installed from stable update site without "Enable Early Access" warning dialog. > JBoss Central proxy wizards need to recognize early access. > ----------------------------------------------------------- > > Key: JBDS-3289 > URL: https://issues.jboss.org/browse/JBDS-3289 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central > Affects Versions: 8.0.2.GA > Reporter: Paul Leacu > Assignee: Fred Bricon > Priority: Blocker > Fix For: 8.0.2.GA > > Attachments: ea1.png > > > Using a JBoss Central proxy wizard that references an early access feature will install that feature correctly even if the "Early Access Enabled" checkbox is unchecked. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18991) New Menuitem wizard for HTML5 palette

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18991?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-18991: ----------------------------------------------- [~dazarov], please create icons for Menuitem palette item and wizard. > New Menuitem wizard for HTML5 palette > ------------------------------------- > > Key: JBIDE-18991 > URL: https://issues.jboss.org/browse/JBIDE-18991 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.3.0.Alpha1 > Reporter: Viacheslav Kabanovich > Assignee: Viacheslav Kabanovich > Labels: new_and_noteworthy > Fix For: 4.3.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18992) New Menu wizard for HTML5 palette

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18992?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-18992: ----------------------------------------------- [~dazarov], please create icons for Menu palette item and wizard. > New Menu wizard for HTML5 palette > --------------------------------- > > Key: JBIDE-18992 > URL: https://issues.jboss.org/browse/JBIDE-18992 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.3.0.Alpha1 > Reporter: Viacheslav Kabanovich > Assignee: Viacheslav Kabanovich > Labels: new_and_noteworthy > Fix For: 4.3.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18948) Include new jbosstools-javaee/batch component into aggregated update site

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18948?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-18948: ---------------------------------------- CoreTools and GeneralTools I guess. [~maxandersen], wdyt? > Include new jbosstools-javaee/batch component into aggregated update site > ------------------------------------------------------------------------- > > Key: JBIDE-18948 > URL: https://issues.jboss.org/browse/JBIDE-18948 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Priority: Critical > Fix For: 4.3.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues January 2015