[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 reassigned JBIDE-19017:
----------------------------------
Assignee: Mickael Istria (was: Nick Boldt)
> 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
> 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 & parent pom
> 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, 2 months
[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 updated JBIDE-19017:
-------------------------------
Fix Version/s: 4.2.2.Final
> 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
> 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 & parent pom
> 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, 2 months
[JBoss JIRA] (JBIDE-19017) Prepare for 4.2.2.Final release
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-19017:
----------------------------------
Summary: 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
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 & parent pom
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, 2 months
[JBoss JIRA] (JBDS-2864) Support explicit deployments
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBDS-2864?page=com.atlassian.jira.plugin.... ]
Andre Dietisheim commented on JBDS-2864:
----------------------------------------
I can only look at PRODMGT-1043 I have no salesforce access (afaik). You could be right, I'm not sure though since I didnt fully understand the referred item in PRODMGT-1043 (commented the issue).
I btw. prefer to have separate items for the requested enhancement. I therefore appreciate we have this one and link PRODMGT-1043.
> Support explicit deployments
> ----------------------------
>
> Key: JBDS-2864
> URL: https://issues.jboss.org/browse/JBDS-2864
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: openshift, requirements
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: JBDS80_Approved_Scope
> Fix For: 8.0.x
>
>
> Currently the turnarounds are far to heavy, it takes far too much time to redeploy java applications to OpenShift.
> We just discovered today that *rhc app config* and *rhc app deploy* allow you to avoid builds upon git push and manually triggering (hot-deploys) deploy
> There's a blog post that is discussing parts of this: https://www.openshift.com/blogs/introduction-to-deployments-and-rollbacks...
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-18678) Make dependencies to org.jboss.tools.usage optional
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18678?page=com.atlassian.jira.plugi... ]
Ilya Buziuk commented on JBIDE-18678:
-------------------------------------
As I recall, I have tested the last PR and everything seemed to work fine for BrowserSim without any updates.
> Make dependencies to org.jboss.tools.usage optional
> ---------------------------------------------------
>
> Key: JBIDE-18678
> URL: https://issues.jboss.org/browse/JBIDE-18678
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: browsersim, usage
> Affects Versions: 4.2.0.CR1
> Reporter: Kaloyan Raev
> Assignee: Alexey Kazakov
> Fix For: 4.3.x
>
>
> I am interested in adopting the CordovaSim feature in our product. However, most of the browsersim bundles have a strong dependency to org.jboss.tools.usage bundle, which force a Usage Reporting popup on startup. I want to avoid this and have the org.jboss.tools.usage excluded from my build.
> Is it possible to make the dependencies to org.jboss.tools.usage optional?
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months