December 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-20491) "incompatibleImprovements" setting should be set

by Daniel Dekany (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20491?page=com.atlassian.jira.plugi... ] Daniel Dekany commented on JBIDE-20491: --------------------------------------- See https://github.com/jbosstools/jbosstools-freemarker/pull/55 > "incompatibleImprovements" setting should be set > ------------------------------------------------ > > Key: JBIDE-20491 > URL: https://issues.jboss.org/browse/JBIDE-20491 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: freemarker > Reporter: Daniel Dekany > Assignee: Denis Golovin > Fix For: 4.3.x, 4.4.x > > > Where the {{freemarker.template.Configuration}} is created, the {{incompatibleImprovements}} setting shouldn't be left on its default, 2.3.0. It should be set to {{Configuration.getVersion()}} (like {{new Configuration(Configuration.getVersion())}}, or with {{config.setIncompatibleImprovements(Configuration.getVersion())}}). > Why: The plugin doesn't execute the templates, just parses them. As of 2.3.24, all the "incompatible" fixes that affect the parser (not the execution) just makes it stricter by eliminating legacy parser glitches that let through things that are pretty much always just user oversights. Also when 2.3.24 is out, the new {{ftlh}} and {{ftlx}} file extensions, which affect parsing, will only have effect with {{incompatibleImprovements}} 2.3.24. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21233) remove need for a targetplatforms/jbosstoolstarget/neon site

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21233?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-21233: --------------------------------------------- a) I ask if this this will mean the sites we *build* against (which are *not* the /development, /stable etc. top level sites) will now have forcefully included the Target platform. If yes, that is bad since that means consuming builds can no longer control which TP they build against. b) I simply do not understand why we are back at again discussing categorized vs non-categorized. We solved that issue 2-3 years ago by stop using associate sites and have aggregates that link via p2 metadata (instead of associated sites) to sites to contact for getting TP content. You even wrote about it back then in 2011 (https://dzone.com/articles/simplifying-p2-process-part-3) - Is that something you are completely forgetting/ignoring now ? It is called "required sites" - your own article about it reminded me. c) You are conflating failed attempts on simplifying things to mean noone wants things to be simplified. I'll not discuss this more in here. So back, to my original question - is this going to mean our sites used for building will now forcefully have the TP included or not ? And why don't we use p2 required sites as in past for our updatesites ? > remove need for a targetplatforms/jbosstoolstarget/neon site > ------------------------------------------------------------ > > Key: JBIDE-21233 > URL: https://issues.jboss.org/browse/JBIDE-21233 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, target-platform > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.0.Alpha1 > > Attachments: jbt-creeping-update-sites.png > > > For the last few years, we've had an associate site ref inside the JBT agg site, pointing at "the latest maximum TP", eg., http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/mars/ > But since we now always co-release JBT with its TP in the same URL, this is only useful for someone who wants to do an OFFLINE install using the zip, which will then go ONLINE to resolve TP dependencies. It's at best a broken use case, and at worst it's unnecessary cruft to maintain. > Therefore I propose we stop linking to this site. > We can build the aggregates using a specific TP (the one in the parent pom, natch), and simply NOT use an associate site in the JBT aggregate site build. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-696) Support for the CDK in JBDS 9.1.beta1 should be more prominent in the release notes

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-696?page=com.atlassian.jira.plug... ] Max Rydahl Andersen commented on TOOLSDOC-696: ---------------------------------------------- CDK it self is not fully pushed yet so I think this is fine. > Support for the CDK in JBDS 9.1.beta1 should be more prominent in the release notes > ----------------------------------------------------------------------------------- > > Key: TOOLSDOC-696 > URL: https://issues.jboss.org/browse/TOOLSDOC-696 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Components: Release Notes > Environment: Build Name: 23115, 9.1 Beta1 Release Notes-9.1-Beta1 > Build Date: 18-12-2015 22:13:00 > Topic ID: 44506-773485 [Latest] > Reporter: Len DiMaggio > Assignee: Misha Ali > > Title: New Features > Describe the issue: > The text describing the new support fo rthe CDK in JBDS 9.1 is correct in the draft release notes: > '...Integration with Red Hat Container Development Kit: A new server adapter has been added to help start and stop the Red Hat Container Development Kit (CDK), a set of tools meant to quickly set up an OpenShift instance inside a Docker container running inside a virtual machine. While the server adapter itself has limited functionality, it is able to start and stop the CDK virtual machine via its Vagrantfile. Once started, Docker and OpenShift connections should appear in their respective views, allowing the user to quickly create a new OpenShift application and begin developing their AwesomeApp in a highly-replicatable environment...' > But - I'd suggest that this moved to a more prominent location in the release notes as it is a major reason for the creation of the beta1 release. > Can we also add a screenshot? > Suggestions for improvement: > Additional information: -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-699) Review: Update JBDS 9.1.0 Beta1 guide

by Supriya Bharadwaj (JIRA)

Supriya Bharadwaj created TOOLSDOC-699: ------------------------------------------ Summary: Review: Update JBDS 9.1.0 Beta1 guide Key: TOOLSDOC-699 URL: https://issues.jboss.org/browse/TOOLSDOC-699 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Feature Request Reporter: Supriya Bharadwaj Assignee: Martin Malina Please review the guide located at: http://docbuilder.usersys.redhat.com/23157/ -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-698) Review: JBDS 9.1.0 Beta1 Install guide

by Supriya Bharadwaj (JIRA)

Supriya Bharadwaj created TOOLSDOC-698: ------------------------------------------ Summary: Review: JBDS 9.1.0 Beta1 Install guide Key: TOOLSDOC-698 URL: https://issues.jboss.org/browse/TOOLSDOC-698 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Feature Request Reporter: Supriya Bharadwaj Assignee: Martin Malina Please review the guide at: http://docbuilder.usersys.redhat.com/23020/ Please note: > I have edited the version numbers, in the entire guide, to show 9.1.0 > In section 4 (Install JBoss Developer Studio BYOE when Online), I have omitted the screenshot for step 2, because the screnshot with 9.1.0 Beta1 will be available only after the release; I shall add this screenshot once the release is done -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-697) Review: Components & Suppported Configs page for JBDS 9.1 Beta1

by Supriya Bharadwaj (JIRA)

Supriya Bharadwaj created TOOLSDOC-697: ------------------------------------------ Summary: Review: Components & Suppported Configs page for JBDS 9.1 Beta1 Key: TOOLSDOC-697 URL: https://issues.jboss.org/browse/TOOLSDOC-697 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Feature Request Reporter: Supriya Bharadwaj Assignee: Martin Malina Pease review the page at: https://access.redhat.com/node/427493/draft -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21372) Server Adapter: implement automatic publishing

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21372?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21372: ------------------------------------- Description: Currently one has to create the OpenShift 3 server adapter manually by using the menu File > New > Server > OpenShift 3 (or context menu in the Server view). We should now also create the server adapter when one successfully finishes the new/import application wizard. To achieve this we'll have to include a page in the new/import-application wizard for the required server settings. (was: Currently the OpenShift 3 server adapter is only publishing when you manually triggering it to do so. We should now have fully automatic publishing that happens whenever the project that it is bound to changes on disk.) > Server Adapter: implement automatic publishing > ---------------------------------------------- > > Key: JBIDE-21372 > URL: https://issues.jboss.org/browse/JBIDE-21372 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Andre Dietisheim > Labels: openshift_v3, server_adapter > Fix For: 4.3.1.Beta2 > > > Currently one has to create the OpenShift 3 server adapter manually by using the menu File > New > Server > OpenShift 3 (or context menu in the Server view). We should now also create the server adapter when one successfully finishes the new/import application wizard. To achieve this we'll have to include a page in the new/import-application wizard for the required server settings. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21371) Server Adapter: implement automatic publishing

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21371?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21371: ------------------------------------- Labels: openshift_v3 server_adapter (was: ) > Server Adapter: implement automatic publishing > ---------------------------------------------- > > Key: JBIDE-21371 > URL: https://issues.jboss.org/browse/JBIDE-21371 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Andre Dietisheim > Labels: openshift_v3, server_adapter > Fix For: 4.3.1.Beta2 > > > Currently the OpenShift 3 server adapter is only publishing when you manually triggering it to do so. We should now have fully automatic publishing that happens whenever the project that it is bound to changes on disk. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21372) Server Adapter: implement automatic publishing

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-21372: ---------------------------------------- Summary: Server Adapter: implement automatic publishing Key: JBIDE-21372 URL: https://issues.jboss.org/browse/JBIDE-21372 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: openshift Affects Versions: 4.3.1.Beta1 Reporter: Andre Dietisheim Fix For: 4.3.1.Beta2 Currently the OpenShift 3 server adapter is only publishing when you manually triggering it to do so. We should now have fully automatic publishing that happens whenever the project that it is bound to changes on disk. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21371) Server Adapter: implement automatic publishing

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-21371: ---------------------------------------- Summary: Server Adapter: implement automatic publishing Key: JBIDE-21371 URL: https://issues.jboss.org/browse/JBIDE-21371 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: openshift Affects Versions: 4.3.1.Beta1 Reporter: Andre Dietisheim Currently the OpenShift 3 server adapter is only publishing when you manually triggering it to do so. We should now have fully automatic publishing that happens whenever the project that it is bound to changes on disk. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 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 2015