[JBoss JIRA] (JBIDE-19017) Prepare for 4.2.2.Final release
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19017?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-19017:
------------------------------------
*Note:* because we're not using 4.2.1 or 4.2.2 in ide-config.properties, we don't have to rebuild Base to update this file:
{code:title=https://github.com/jbosstools/jbosstools-base/blob/jbosstools-4.2.x/foundation/plugins/org.jboss.tools.foundation.core/src/org/jboss/tools/foundation/core/properties/internal/currentversion.properties#L11}
default.version=4.2.1.Final
version=${jbosstools.version}
{code}
But I have updated the matching config in JBDS for 8.0.2:
{code:title=https://github.com/jbdevstudio/jbdevstudio-product/pull/254/files#diff-58c9bc2461e193f4fafd8d4983e335e7R11}
default.version=8.0.2.GA
version=${devstudio.version}
{code}
> Prepare for 4.2.2.Final release
> -------------------------------
>
> Key: JBIDE-19017
> URL: https://issues.jboss.org/browse/JBIDE-19017
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.2.2.Final
> Reporter: Nick Boldt
> Assignee: Mickael Istria
> Priority: Blocker
> Fix For: 4.2.2.Final
>
>
> TODOs for preparing for the 4.2.2 release.
> For components that contribute to this release (and only these): Central, WS, Forge, JBT aggregates, JBDS:
> a) ensure we're all using the right TP (4.40.0.Final, 4.41.1.Final) & parent pom version 4.2.1.Final-SNAPSHOT - NO CHANGE SINCE 4.2.1 release; all projects OK
> b) ensure components have properly upversioned to 4.2.2/8.0.2, etc.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (JBIDE-13862) Server adapter wizard: When creating adapter manually, the deploying project should be added automatically
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13862?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-13862:
-------------------------------------
Fix Version/s: 4.3.x
(was: 4.2.x)
> Server adapter wizard: When creating adapter manually, the deploying project should be added automatically
> ----------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-13862
> URL: https://issues.jboss.org/browse/JBIDE-13862
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.0.Alpha1
> Reporter: Stefan Bunciak
> Priority: Minor
> Labels: server_adapter_wizard
> Fix For: 4.3.x
>
> Attachments: server.png, server1.png, server2.png
>
>
> Deploying project is automatically added to OpenShift Server adapter after application import:
> * after application import contains the deploying project: !server.png|thumbnail!
> When created manually via OpenShift Explorer (Application - Create Server Adapter), the deploying project is not automatically added, even though I'm selecting the deploying project:
> * !server2.png|thumbnail! *->* !server1.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (JBDS-3289) JBoss Central proxy wizards need to recognize early access.
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBDS-3289?page=com.atlassian.jira.plugin.... ]
Fred Bricon edited comment on JBDS-3289 at 1/8/15 4:34 PM:
-----------------------------------------------------------
That would be inconsistent with the software page where connectors are only shown when EA is enabled. At this point, the current PR, even though not ideal, is the safest solution to this issue given the time we have left.
We can revisit the whole mechanism for 9.0
was (Author: fbricon):
That would be inconsistent with the software page where connectors are only shown when EA is enabled. At this point, the current PR, even though not ideal, is the safest solution to this issue given the time we have left
> 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)
11 years, 3 months
[JBoss JIRA] (JBDS-3289) JBoss Central proxy wizards need to recognize early access.
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBDS-3289?page=com.atlassian.jira.plugin.... ]
Fred Bricon commented on JBDS-3289:
-----------------------------------
That would be inconsistent with the software page where connectors are only shown when EA is enabled. At this point, the current PR, even though not ideal, is the safest solution to this issue given the time we have left
> 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)
11 years, 3 months
[JBoss JIRA] (JBIDE-12803) Server Adapter: Cannot publish after I renamed the maven artifact
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12803?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-12803 at 1/8/15 4:33 PM:
------------------------------------------------------------------
setting to Minor and 4.1.x since this is an edge case (happens when you rename a project) while an easy workaround (open server editor and set the project again) exists.
was (Author: adietish):
setting to Minor and 4.1.x since this is an edge case (happens when you rename a project) which an easy workaround (open server editor and set the project again) exists.
> Server Adapter: Cannot publish after I renamed the maven artifact
> -----------------------------------------------------------------
>
> Key: JBIDE-12803
> URL: https://issues.jboss.org/browse/JBIDE-12803
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Reporter: Burr Sutter
> Priority: Minor
> Labels: server_adapter
> Fix For: 4.3.x
>
> Attachments: 2012-10-04_1859.png
>
>
> Using JBDS, I used
> * Refactor - Rename Maven Artifact
> * Refactor - Rename
> to change my project name - this project had previously been deployed to Openshift and now the Full Publish fails.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months