[JBoss JIRA] (JBIDE-19795) Bower support
by Victor Rubezhny (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19795?page=com.atlassian.jira.plugi... ]
Victor Rubezhny commented on JBIDE-19795:
-----------------------------------------
[~mickael_istria] Yes it's related. The difference is that Ilya's implementation uses native bower executable while the Stephane's one emulates it by uses JGit.
> Bower support
> -------------
>
> Key: JBIDE-19795
> URL: https://issues.jboss.org/browse/JBIDE-19795
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Affects Versions: 4.3.0.Alpha2
> Reporter: Ilya Buziuk
> Assignee: Ilya Buziuk
> Labels: new_and_noteworthy
> Fix For: 4.3.0.Final
>
>
> Need to have initial [Bower|http://bower.io/] tools support:
> *The gist*
> Bower tooling should initially support several bower API commands :
> |Command||Description|
> | *bower init* |creates a *bower.json* file|
> |*bower install <package>*|installs packages to *bower_components* folder|
> |*bower uninstall <package>*|uninstalls a package locally from *bower_components* directory|
> |*bower update* |updates installed packages to their newest version according to *bower.json*|
> Basically, the main idea of the implementation is the following:
> Eclipse plugin that will execute *external* bower commands - implementation will fall back on *native* bower installation via *ILaunchConfiguration*
> Native bower tools must be preinstalled
> *The main questions & proposals:*
> 1. https://github.com/jbosstools/jbosstools-playground is probably the best place for initial implementation of bower stuff (infrastructure / build etc.)
> 2. UI. should it be ILaunchShortcuts ("bower init" / "bower update" etc.) + launch configuration enabled for projects with js nature?
> 3. Implementation details:
> - the way of detecting bower? Should user point to it's installation dir and this location will be used for IExternalToolConstants.ATTR_LOCATION (windows case: *\user\AppData\Roaming\npm\node_modules\bower* )
> - if bower was not detected / installed - "Error message with a link to the bower website with installation details depending on the platform"
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19795) Bower support
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19795?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-19795:
----------------------------------------
Does this rely on the bower support contributed to JSDT ? http://git.eclipse.org/c/jsdt/webtools.jsdt.git/tree/bundles/org.eclipse....
/cc [~vrubezhny]
> Bower support
> -------------
>
> Key: JBIDE-19795
> URL: https://issues.jboss.org/browse/JBIDE-19795
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Affects Versions: 4.3.0.Alpha2
> Reporter: Ilya Buziuk
> Assignee: Ilya Buziuk
> Labels: new_and_noteworthy
> Fix For: 4.3.0.Final
>
>
> Need to have initial [Bower|http://bower.io/] tools support:
> *The gist*
> Bower tooling should initially support several bower API commands :
> |Command||Description|
> | *bower init* |creates a *bower.json* file|
> |*bower install <package>*|installs packages to *bower_components* folder|
> |*bower uninstall <package>*|uninstalls a package locally from *bower_components* directory|
> |*bower update* |updates installed packages to their newest version according to *bower.json*|
> Basically, the main idea of the implementation is the following:
> Eclipse plugin that will execute *external* bower commands - implementation will fall back on *native* bower installation via *ILaunchConfiguration*
> Native bower tools must be preinstalled
> *The main questions & proposals:*
> 1. https://github.com/jbosstools/jbosstools-playground is probably the best place for initial implementation of bower stuff (infrastructure / build etc.)
> 2. UI. should it be ILaunchShortcuts ("bower init" / "bower update" etc.) + launch configuration enabled for projects with js nature?
> 3. Implementation details:
> - the way of detecting bower? Should user point to it's installation dir and this location will be used for IExternalToolConstants.ATTR_LOCATION (windows case: *\user\AppData\Roaming\npm\node_modules\bower* )
> - if bower was not detected / installed - "Error message with a link to the bower website with installation details depending on the platform"
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19760) Add route support to OpenShift explorer
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19760?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-19760:
-------------------------------------
Description:
Add support for viewing routes in OpenShiftExplorer and property pane
steps to verify:
# ASSERT: have openshift origin cloned and available in your openshift server
# EXEC: in openshift server, cd to <origin>/examples/sample-app and do:
{code}osc process -f application-template-custombuild.json | osc create -f - -n test{code}
# EXEC: once the build is finished: open up OpenShift explorer
# ASSERT: you should see an entry: "OpenShift 3 Sample"
# EXEC: unfold "OpenShift 3 Sample"
# ASSERT: have a child entry "Routes" with an entry "route-edge"
# ASSERT: make sure you have properties view opened
# ASSERT: the properties view is displaying properties for the selected route "route-edge"
!route.png!
was:
Add support for viewing routes in OpenShiftExplorer and property pane
steps to verify:
# ASSERT: have openshift origin cloned and available in your openshift server
# EXEC: in openshift server in cmd line:
{code}osc process -f application-template-custombuild.json | osc create -f - -n test{code}
# EXEC: once the build is finished: open up OpenShift explorer
# ASSERT: you should see an entry: "OpenShift 3 Sample"
# EXEC: unfold "OpenShift 3 Sample"
# ASSERT: have a child entry "Routes" with an entry "route-edge"
# ASSERT: make sure you have properties view opened
# ASSERT: the properties view is displaying properties for the selected route "route-edge"
!route.png!
> Add route support to OpenShift explorer
> ---------------------------------------
>
> Key: JBIDE-19760
> URL: https://issues.jboss.org/browse/JBIDE-19760
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Jeff Cantrill
> Assignee: Jeff Cantrill
> Fix For: 4.3.0.Beta2
>
> Attachments: route.png
>
>
> Add support for viewing routes in OpenShiftExplorer and property pane
> steps to verify:
> # ASSERT: have openshift origin cloned and available in your openshift server
> # EXEC: in openshift server, cd to <origin>/examples/sample-app and do:
> {code}osc process -f application-template-custombuild.json | osc create -f - -n test{code}
> # EXEC: once the build is finished: open up OpenShift explorer
> # ASSERT: you should see an entry: "OpenShift 3 Sample"
> # EXEC: unfold "OpenShift 3 Sample"
> # ASSERT: have a child entry "Routes" with an entry "route-edge"
> # ASSERT: make sure you have properties view opened
> # ASSERT: the properties view is displaying properties for the selected route "route-edge"
> !route.png!
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19760) Add route support to OpenShift explorer
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19760?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-19760:
-------------------------------------
Description:
Add support for viewing routes in OpenShiftExplorer and property pane
steps to verify:
# ASSERT: have openshift origin cloned and available in your openshift server
# EXEC: in openshift server in cmd line:
{code}osc process -f application-template-custombuild.json | osc create -f - -n test{code}
# EXEC: once the build is finished: open up OpenShift explorer
# ASSERT: you should see an entry: "OpenShift 3 Sample"
# EXEC: unfold "OpenShift 3 Sample"
# ASSERT: have a child entry "Routes" with an entry "route-edge"
# ASSERT: make sure you have properties view opened
# ASSERT: the properties view is displaying properties for the selected route "route-edge"
!route.png!
was:
Add support for viewing routes in OpenShiftExplorer and property pane
steps to verify:
# ASSERT: have openshift origin cloned and available in your openshift server
# EXEC: in openshift server in cmd line: osc process -f application-template-custombuild.json | osc create -f - -n test
# EXEC: once the build is finished: open up OpenShift explorer
# ASSERT: you should see an entry: "OpenShift 3 Sample"
# EXEC: unfold "OpenShift 3 Sample"
# ASSERT: have a child entry "Routes" with an entry "route-edge"
# ASSERT: make sure you have properties view opened
# ASSERT: the properties view is displaying properties for the selected route "route-edge"
!route.png!
> Add route support to OpenShift explorer
> ---------------------------------------
>
> Key: JBIDE-19760
> URL: https://issues.jboss.org/browse/JBIDE-19760
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Jeff Cantrill
> Assignee: Jeff Cantrill
> Fix For: 4.3.0.Beta2
>
> Attachments: route.png
>
>
> Add support for viewing routes in OpenShiftExplorer and property pane
> steps to verify:
> # ASSERT: have openshift origin cloned and available in your openshift server
> # EXEC: in openshift server in cmd line:
> {code}osc process -f application-template-custombuild.json | osc create -f - -n test{code}
> # EXEC: once the build is finished: open up OpenShift explorer
> # ASSERT: you should see an entry: "OpenShift 3 Sample"
> # EXEC: unfold "OpenShift 3 Sample"
> # ASSERT: have a child entry "Routes" with an entry "route-edge"
> # ASSERT: make sure you have properties view opened
> # ASSERT: the properties view is displaying properties for the selected route "route-edge"
> !route.png!
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19760) Add route support to OpenShift explorer
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19760?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-19760:
------------------------------------------
rebased, merged and pushed to upstream/master
> Add route support to OpenShift explorer
> ---------------------------------------
>
> Key: JBIDE-19760
> URL: https://issues.jboss.org/browse/JBIDE-19760
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Jeff Cantrill
> Assignee: Jeff Cantrill
> Fix For: 4.3.0.Beta2
>
> Attachments: route.png
>
>
> Add support for viewing routes in OpenShiftExplorer and property pane
> steps to verify:
> # ASSERT: have openshift origin cloned and available in your openshift server
> # EXEC: in openshift server in cmd line: osc process -f application-template-custombuild.json | osc create -f - -n test
> # EXEC: once the build is finished: open up OpenShift explorer
> # ASSERT: you should see an entry: "OpenShift 3 Sample"
> # EXEC: unfold "OpenShift 3 Sample"
> # ASSERT: have a child entry "Routes" with an entry "route-edge"
> # ASSERT: make sure you have properties view opened
> # ASSERT: the properties view is displaying properties for the selected route "route-edge"
> !route.png!
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19760) Add route support to OpenShift explorer
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19760?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-19760:
-------------------------------------
Description:
Add support for viewing routes in OpenShiftExplorer and property pane
steps to verify:
# ASSERT: have openshift origin cloned and available in your openshift server
# EXEC: in openshift server in cmd line: osc process -f application-template-custombuild.json | osc create -f - -n test
# EXEC: once the build is finished: open up OpenShift explorer
# ASSERT: you should see an entry: "OpenShift 3 Sample"
# EXEC: unfold "OpenShift 3 Sample"
# ASSERT: have a child entry "Routes" with an entry "route-edge"
# ASSERT: make sure you have properties view opened
# ASSERT: the properties view is displaying properties for the selected route "route-edge"
!route.png!
was:
Add support for viewing routes in OpenShiftExplorer and property pane
steps to verify:
# ASSERT: have openshift origin cloned and available in your openshift server
# EXEC: in openshift server in cmd line: osc process -f application-template-custombuild.json | osc create -f - -n test
# EXEC: once the build is finished: open up OpenShift explorer
# ASSERT: you should see an entry: "OpenShift 3 Sample"
# EXEC: unfold "OpenShift 3 Sample"
# ASSERT: have a child entry "Routes" with an entry "route-edge"
# ASSERT: make sure you have properties view opened
# ASSERT: the properties view is displaying properties for the selected route "route-edge"
!routes.png!
> Add route support to OpenShift explorer
> ---------------------------------------
>
> Key: JBIDE-19760
> URL: https://issues.jboss.org/browse/JBIDE-19760
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Jeff Cantrill
> Assignee: Jeff Cantrill
> Fix For: 4.3.0.Beta2
>
> Attachments: route.png
>
>
> Add support for viewing routes in OpenShiftExplorer and property pane
> steps to verify:
> # ASSERT: have openshift origin cloned and available in your openshift server
> # EXEC: in openshift server in cmd line: osc process -f application-template-custombuild.json | osc create -f - -n test
> # EXEC: once the build is finished: open up OpenShift explorer
> # ASSERT: you should see an entry: "OpenShift 3 Sample"
> # EXEC: unfold "OpenShift 3 Sample"
> # ASSERT: have a child entry "Routes" with an entry "route-edge"
> # ASSERT: make sure you have properties view opened
> # ASSERT: the properties view is displaying properties for the selected route "route-edge"
> !route.png!
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19760) Add route support to OpenShift explorer
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19760?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-19760:
-------------------------------------
Description:
Add support for viewing routes in OpenShiftExplorer and property pane
steps to verify:
# ASSERT: have openshift origin cloned and available in your openshift server
# EXEC: in openshift server in cmd line: osc process -f application-template-custombuild.json | osc create -f - -n test
# EXEC: once the build is finished: open up OpenShift explorer
# ASSERT: you should see an entry: "OpenShift 3 Sample"
# EXEC: unfold "OpenShift 3 Sample"
# ASSERT: have a child entry "Routes" with an entry "route-edge"
# ASSERT: make sure you have properties view opened
# ASSERT: the properties view is displaying properties for the selected route "route-edge"
!routes.png!
was:Add support for viewing routes in OpenShiftExplorer and property pane
Sprint: Sprint #3 May 2015
> Add route support to OpenShift explorer
> ---------------------------------------
>
> Key: JBIDE-19760
> URL: https://issues.jboss.org/browse/JBIDE-19760
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Jeff Cantrill
> Assignee: Jeff Cantrill
> Fix For: 4.3.0.Beta2
>
> Attachments: route.png
>
>
> Add support for viewing routes in OpenShiftExplorer and property pane
> steps to verify:
> # ASSERT: have openshift origin cloned and available in your openshift server
> # EXEC: in openshift server in cmd line: osc process -f application-template-custombuild.json | osc create -f - -n test
> # EXEC: once the build is finished: open up OpenShift explorer
> # ASSERT: you should see an entry: "OpenShift 3 Sample"
> # EXEC: unfold "OpenShift 3 Sample"
> # ASSERT: have a child entry "Routes" with an entry "route-edge"
> # ASSERT: make sure you have properties view opened
> # ASSERT: the properties view is displaying properties for the selected route "route-edge"
> !routes.png!
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19760) Add route support to OpenShift explorer
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19760?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-19760:
-------------------------------------
Attachment: route.png
> Add route support to OpenShift explorer
> ---------------------------------------
>
> Key: JBIDE-19760
> URL: https://issues.jboss.org/browse/JBIDE-19760
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Jeff Cantrill
> Assignee: Jeff Cantrill
> Fix For: 4.3.0.Beta2
>
> Attachments: route.png
>
>
> Add support for viewing routes in OpenShiftExplorer and property pane
> steps to verify:
> # ASSERT: have openshift origin cloned and available in your openshift server
> # EXEC: in openshift server in cmd line: osc process -f application-template-custombuild.json | osc create -f - -n test
> # EXEC: once the build is finished: open up OpenShift explorer
> # ASSERT: you should see an entry: "OpenShift 3 Sample"
> # EXEC: unfold "OpenShift 3 Sample"
> # ASSERT: have a child entry "Routes" with an entry "route-edge"
> # ASSERT: make sure you have properties view opened
> # ASSERT: the properties view is displaying properties for the selected route "route-edge"
> !routes.png!
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months