[JBoss JIRA] (JBIDE-19458) Use jbosstools_site_update in Jenkins jobs and jbosstools-site-update in parent pom for "consistency" & "less confusion"
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19458?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-19458 at 3/17/15 3:15 PM:
-------------------------------------------------------------
{quote}[2:12:49 PM] Max Andersen / conf# 592-775-2520: so looked at the prs again.
[2:13:38 PM] Max Andersen / conf# 592-775-2520: make jbosstools_stream jbosstools_site_stream (i.e. old name, but just with _) and my complaints are not enough to warrant rolling it back since it stays backwards compatible.
[2:14:29 PM] Max Andersen / conf# 592-775-2520: i still dont like it but at least then you dont get to feel bad doing jbosstools-site-stream=$\{jbosstools_site_stream}
{quote}
was (Author: nickboldt):
{quote}[2:12:49 PM] Max Andersen / conf# 592-775-2520: so looked at the prs again.
[2:13:38 PM] Max Andersen / conf# 592-775-2520: make jbosstools_stream jbosstools_site_stream (i.e. old name, but just with _) and my complaints are not enough to warrant rolling it back since it stays backwards compatible.
[2:14:29 PM] Max Andersen / conf# 592-775-2520: i still dont like it but at least then you dont get to feel bad doing jbosstools-site-stream=${jbosstools_site_stream}
{quote}
> Use jbosstools_site_update in Jenkins jobs and jbosstools-site-update in parent pom for "consistency" & "less confusion"
> ------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-19458
> URL: https://issues.jboss.org/browse/JBIDE-19458
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.3.0.Alpha2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
>
> Max wants that:
> * the parameter we use in Jenkins be *jbosstools_site_stream* (underscores) and that
> * the maven processes all use *jbosstools-site-stream* (dashes)
> Because
> * Max feels that using a different parameter in Jenkins than the value in the parent pom is more consistent & less likely to cause problems, vs.
> * renaming the variable so that both use the same underscored name of jbosstools_stream.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 1 month
[JBoss JIRA] (JBIDE-19458) Use jbosstools_site_update in Jenkins jobs and jbosstools-site-update in parent pom for "consistency" & "less confusion"
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19458?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-19458:
------------------------------------
{quote}[2:12:49 PM] Max Andersen / conf# 592-775-2520: so looked at the prs again.
[2:13:38 PM] Max Andersen / conf# 592-775-2520: make jbosstools_stream jbosstools_site_stream (i.e. old name, but just with _) and my complaints are not enough to warrant rolling it back since it stays backwards compatible.
[2:14:29 PM] Max Andersen / conf# 592-775-2520: i still dont like it but at least then you dont get to feel bad doing jbosstools-site-stream=${jbosstools_site_stream}
{quote}
> Use jbosstools_site_update in Jenkins jobs and jbosstools-site-update in parent pom for "consistency" & "less confusion"
> ------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-19458
> URL: https://issues.jboss.org/browse/JBIDE-19458
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.3.0.Alpha2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
>
> Max wants that:
> * the parameter we use in Jenkins be *jbosstools_site_stream* (underscores) and that
> * the maven processes all use *jbosstools-site-stream* (dashes)
> Because
> * Max feels that using a different parameter in Jenkins than the value in the parent pom is more consistent & less likely to cause problems, vs.
> * renaming the variable so that both use the same underscored name of jbosstools_stream.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 1 month
[JBoss JIRA] (JBTIS-414) SOA 5 tooling shows up in early access
by Len DiMaggio (JIRA)
Len DiMaggio created JBTIS-414:
----------------------------------
Summary: SOA 5 tooling shows up in early access
Key: JBTIS-414
URL: https://issues.jboss.org/browse/JBTIS-414
Project: JBoss Tools Integration Stack
Issue Type: Bug
Components: ESB
Affects Versions: 8.0.0.CR1
Reporter: Len DiMaggio
Assignee: Paul Leacu
Fix For: 8.0.1.CR1
The legacy ESB/SOA tooling shows up under early access. This is misleading as it implies that we are doing new development on this tooling - which we are not. Can we move this out from early access? Thx!
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 1 month