[JBoss JIRA] (JBDS-2837) Investigate adding Gradle tools to Central
by Mickael Istria (JIRA)
Mickael Istria created JBDS-2837:
------------------------------------
Summary: Investigate adding Gradle tools to Central
Key: JBDS-2837
URL: https://issues.jboss.org/browse/JBDS-2837
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Components: 3rd-party-certification, central
Reporter: Mickael Istria
More and more people are talking about Gradle. I'm starting to believe that JBT/JBDS could have interest in providing Eclipse Gradle integration to its users.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (JBIDE-16126) Publish component sites to Nexus
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16126?page=com.atlassian.jira.plugi... ]
Mickael Istria closed JBIDE-16126.
----------------------------------
Resolution: Duplicate Issue
Dup of JBIDE-16128
> Publish component sites to Nexus
> --------------------------------
>
> Key: JBIDE-16126
> URL: https://issues.jboss.org/browse/JBIDE-16126
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Fix For: 4.2.0.Alpha1
>
>
> In order to get a first idea of how easy/difficult it would be to rely on Nexus for publication,we could simply start by configuring CI jobs to also run a "mvn deploy" to deploy the output p2 repository onto Nexus.
> Then we'll see what are the pros/cons of this approach.
> Current publication process and locations will be kept. These p2 repo on Nexus won't be consumed by aggregator, at least not until we are sure it's worth it.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (JBIDE-16134) CordovaSim should start the livereload server
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16134?page=com.atlassian.jira.plugi... ]
Gorkem Ercan commented on JBIDE-16134:
--------------------------------------
BrowserSim/CordovaSim has a menu item that says enable livereload and AFAIK that menu item is visible and enabled even if the livereload plugins are not installed. In my opinion, the dependency already exists and BrowserSim/CordovaSim is just dodging it by being an external app.
I guess the dependency can be an optional one as long as the menu items are not enabled or visible when the livereload is not possible.
I think livereload server is just odd on the servers view but as long as a developer does not have to deal with it on default cases I am OK with it. Would it be too hard if someone enables livereload on BrowserSim the livereload server is created and started automagically so that they never even realise there is a server involved.
> CordovaSim should start the livereload server
> ---------------------------------------------
>
> Key: JBIDE-16134
> URL: https://issues.jboss.org/browse/JBIDE-16134
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: browsersim
> Affects Versions: 4.1.1.CR1
> Reporter: Gorkem Ercan
> Assignee: Konstantin Marmalyukov
>
> CordovaSim should configure and start the livereload server when the livereload is enabled.
> If starting the server from CordovaSim menu is a big problem, alternately, the server can always be configured and started before a CordovaSim launch.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months