[JBoss JIRA] (JBTIS-166) Deploying BPEL project to a server is not working
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-166?page=com.atlassian.jira.plugin.... ]
Paul Leacu commented on JBTIS-166:
----------------------------------
[~apodhrad] [~bbrodt] - Hey - since this is exceedingly old but has already been re-opened - is there consensus that it can be closed?
> Deploying BPEL project to a server is not working
> -------------------------------------------------
>
> Key: JBTIS-166
> URL: https://issues.jboss.org/browse/JBTIS-166
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: BPEL
> Affects Versions: 4.1.2
> Environment: Eclipse 3.7.2 + JBoss AS 5.1.0 + RiftSaw 2.3.0
> Reporter: Andrej Podhradsky
> Assignee: Robert (Bob) Brodt
> Priority: Critical
> Attachments: deploying_as51.log, deploying_as51.png, running_as51.log, running_as51.png
>
>
> This bug was moved from JBIDE (from version 3.3) and is still present. The problem is as follows:
> Installing the BPEL feature from JBTIS 4.1.2 update site is not enough for full working with BPEL and JBoss AS.
> You need to install JBoss AS feature from JBT Core update site. Note that this doesn't happen in JBDS (there already is the AS plugin).
> Without explicit installing AS plugin I'm getting two erros (when starting the server and when trying to deploy bpel project).
> See the attachments.
> Original description:
> Deploying BPEL project to a server, which is created using JBoss AS 5.1 adapter, is not working - it seems that nothing happens.
> But if I try to deploy the same project to a server created using JBoss Application Platform 5.x, it works fine.
> In JBDS 4 and 5 it works fine for both adapters.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 6 months
[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 Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18995?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-18995:
----------------------------------------
Those files are better being updated manually on download.jboss.org. Release process shouldn't depend on this files from the discovery plugins, and should instead depend on the ones on download.jboss.org.
IMO, the simplest thing is to remove them, and to fix the release process accordingly so it doesn't need those files.
> 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: Nick Boldt
> Priority: Minor
> Fix For: 4.2.1.Final
>
> 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, 6 months
[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 Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18995?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-18995:
------------------------------------
As I started removing them I realized that this impacts the release process (because ide-config.properties points to the staging discovery site, which includes the earlyaccess.properties file), so maybe we should add these files into the EA site itself?
That way when we publish a new EA site + zip to staging or release, we'll just have the new file colocated in the update site, and publishing is simpler (ide-config.props can just point at the staging EA site, instead of the staging discovery site).
[~mickael_istria] If you agree, I can add this change/requirement to JBIDE-18984.
> 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: Nick Boldt
> Priority: Minor
> Fix For: 4.2.1.Final
>
> 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, 6 months