[JBoss JIRA] (JBIDE-19789) User Defined Modules are not loading in Eclipse
by Raj Kumar (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19789?page=com.atlassian.jira.plugi... ]
Raj Kumar commented on JBIDE-19789:
-----------------------------------
Thanks [~rob.stryker] , it is working now, Thanks [~maxandersen] ,
but i had an issue in runtime, that here is my log,
i have configure spring lib's as one module named "org.springframework",
while deploying in server am getting exception below,
17:47:46,979 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC0000
01: Failed to start service jboss.deployment.unit."Test_JB60_Testing.war"
.POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.u
nit."Test_JB60_Testing.war".POST_MODULE: JBAS018733: Failed to process ph
ase POST_MODULE of deployment "Test_JB60_Testing.war"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(Deplo
ymentUnitPhaseService.java:166) [wildfly-server-8.2.0.Final.jar:8.2.0.Final]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(Se
rviceControllerImpl.java:1948) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceCont
rollerImpl.java:1881) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.
java:1142) [rt.jar:1.8.0_40]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor
.java:617) [rt.jar:1.8.0_40]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_40]
Caused by: java.lang.RuntimeException: JBAS018757: Error getting reflective info
rmation for class org.springmodules.validation.commons.taglib.JavascriptValidato
rTag with ClassLoader ModuleClassLoader for Module "deployment.Test_JB60_
Testing.war:main" from Service Module Loader
at org.jboss.as.server.deployment.reflect.DeploymentReflectionIndex.getC
lassIndex(DeploymentReflectionIndex.java:72) [wildfly-server-8.2.0.Final.jar:8.2
.0.Final]
at org.jboss.as.ee.metadata.MethodAnnotationAggregator.runtimeAnnotation
Information(MethodAnnotationAggregator.java:58)
at org.jboss.as.ee.component.deployers.InterceptorAnnotationProcessor.ha
ndleAnnotations(InterceptorAnnotationProcessor.java:107)
at org.jboss.as.ee.component.deployers.InterceptorAnnotationProcessor.pr
ocessComponentConfig(InterceptorAnnotationProcessor.java:92)
at org.jboss.as.ee.component.deployers.InterceptorAnnotationProcessor.de
ploy(InterceptorAnnotationProcessor.java:77)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(Deplo
ymentUnitPhaseService.java:159) [wildfly-server-8.2.0.Final.jar:8.2.0.Final]
... 5 more
Caused by: java.lang.NoClassDefFoundError: org/springframework/beans/factory/Lis
tableBeanFactory
at java.lang.Class.getDeclaredFields0(Native Method) [rt.jar:1.8.0_40]
at java.lang.Class.privateGetDeclaredFields(Class.java:2583) [rt.jar:1.8
.0_40]
at java.lang.Class.getDeclaredFields(Class.java:1916) [rt.jar:1.8.0_40]
at org.jboss.as.server.deployment.reflect.ClassReflectionIndex.<init>(Cl
assReflectionIndex.java:57) [wildfly-server-8.2.0.Final.jar:8.2.0.Final]
at org.jboss.as.server.deployment.reflect.DeploymentReflectionIndex.getC
lassIndex(DeploymentReflectionIndex.java:68) [wildfly-server-8.2.0.Final.jar:8.2
.0.Final]
... 10 more
Caused by: java.lang.ClassNotFoundException: org.springframework.beans.factory.L
istableBeanFactory from [Module "deployment.Test_JB60_Testing.war:main" f
rom Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:
213) [jboss-modules.jar:1.3.3.Final]
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(Con
currentClassLoader.java:459) [jboss-modules.jar:1.3.3.Final]
at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(Concu
rrentClassLoader.java:408) [jboss-modules.jar:1.3.3.Final]
at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentCl
assLoader.java:389) [jboss-modules.jar:1.3.3.Final]
at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoad
er.java:134) [jboss-modules.jar:1.3.3.Final]
... 15 more
17:47:47,204 ERROR [org.jboss.as.controller.management-operation] (Controller Bo
ot Thread) JBAS014613: Operation ("deploy") failed - address: ([("deployment" =>
"Test_JB60_Testing.war")]) - failure description: {"JBAS014671: Failed s
ervices" => {"jboss.deployment.unit.\"Test_JB60_Testing.war\".POST_MODULE
" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"Ra
ngatelRWD_JB60_Testing.war\".POST_MODULE: JBAS018733: Failed to process phase PO
ST_MODULE of deployment \"Test_JB60_Testing.war\"
Caused by: java.lang.RuntimeException: JBAS018757: Error getting reflective
information for class org.springmodules.validation.commons.taglib.JavascriptVali
datorTag with ClassLoader ModuleClassLoader for Module \"deployment.Test_
JB60_Testing.war:main\" from Service Module Loader
Caused by: java.lang.NoClassDefFoundError: org/springframework/beans/factory
/ListableBeanFactory
Caused by: java.lang.ClassNotFoundException: org.springframework.beans.facto
ry.ListableBeanFactory from [Module \"deployment.Test_JB60_Testing.war:ma
in\" from Service Module Loader]"}}
17:47:47,837 INFO [org.jboss.as.server] (ServerService Thread Pool -- 28) JBAS0
18559: Deployed "Test_JB60_Testing.war" (runtime-name : "Test_JB60
_Testing.war")
17:47:47,857 INFO [org.jboss.as.server] (ServerService Thread Pool -- 28) JBAS0
18559: Deployed "mysql-connector-java-5.1.34.jar" (runtime-name : "mysql-connect
or-java-5.1.34.jar")
17:47:47,860 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774
: Service status report
JBAS014777: Services which failed to start: service jboss.deployment.unit
."Test_JB60_Testing.war".POST_MODULE: org.jboss.msc.service.StartExceptio
n in service jboss.deployment.unit."Test_JB60_Testing.war".POST_MODULE: J
BAS018733: Failed to process phase POST_MODULE of deployment "Test_JB60_T
esting.war"
17:47:48,059 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http mana
gement interface listening on http://127.0.0.1:9990/management
17:47:48,067 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin con
sole listening on http://127.0.0.1:9990
17:47:48,067 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: WildFly 8
.2.0.Final "Tweek" started (with errors) in 24882ms - Started 254 of 311 service
s (1 services failed or missing dependencies, 92 services are lazy, passive or o
n-demand)
17:47:48,565 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBA
S015877: Stopped deployment Test_JB60_Testing.war (runtime-name: Rangatel
RWD_JB60_Testing.war) in 437ms
17:47:49,277 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018
558: Undeployed "Test_JB60_Testing.war" (runtime-name: "Test_JB60_
Testing.war")
17:47:49,279 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) JBA
S014774: Service status report
JBAS014777: Services which failed to start: service jboss.deployment.unit
."Test_JB60_Testing.war".POST_MODULE
> User Defined Modules are not loading in Eclipse
> ------------------------------------------------
>
> Key: JBIDE-19789
> URL: https://issues.jboss.org/browse/JBIDE-19789
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: server
> Environment: java 1.8, wildfly 8.1 , Mysql
> Reporter: Raj Kumar
>
> Hi , i want to load the Application server Libraries in Java Build Path in eclipse,
>
> i have 5 applications in eclipse which shares common libraries,
> i can't put all the libraries in each project lib folder,
> so i want to add the libraries in Wildfly Application server using modules.
>
> This is my module.xml file add added the lib at WILDFLY_HOME/modules/system/layers/base/com/mysql/main/mysql-connector-java-5.1.23-bin.jar
>
> <?xml version="1.0" encoding="UTF-8"?>
> <module xmlns="urn:jboss:module:1.1" name="com.mysql">
> <resources>
> <resource-root path="mysql-connector-java-5.1.23-bin.jar"/>
> </resources>
> <dependencies>
> <module name="javax.api"/>
> <module name="javax.transaction.api"/>
> </dependencies>
> </module>
>
> After Restarting the server,this module is not loading in Eclipse Build path.
> Can any one knows what wrong with this modules ?
> In Wildfly i have some predefined modules, those are loading in build path successfully, but user-defined modules are not loading ?
> why ?
> - See more at: https://developer.jboss.org/thread/257825?sr=inbox#sthash.MWLbzbco.dpuf
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-19795) Bower support
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19795?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-19795:
---------------------------------------------
+1
> 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, 11 months
[JBoss JIRA] (JBIDE-19795) Bower support
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19795?page=com.atlassian.jira.plugi... ]
Ilya Buziuk commented on JBIDE-19795:
-------------------------------------
[~maxandersen], sounds good. So the first step would be "bower updade" Launch Shortcut for projects with bower.json
> 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, 11 months
[JBoss JIRA] (JBIDE-19795) Bower support
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19795?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-19795:
---------------------------------------------
I would start by just having support for "bower update" initially. The rest can be added on that.
#1 Yes.
#2 projects with js nature could have "bower init" available yes, bower install/uninstall/update shuold be on projects with js too - but if just plain porject then at least have these commands available on bower.json files directly too.
#3 I would start by simply assuming it is available in the path; secondly then yeah, we could have a global preferences for bower or simply "external tool" that could be overridden at project level. Note, these settings would need somehow to be made portable across platform (i.e. paths should not require to be machine specific nor should it assume all commands is the same on all os (ie.. bower.cmd on windows vs bower on linux/windows)
And yes, if failure to run/locate it provide basic info/tips on how to install it.
> 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, 11 months
[JBoss JIRA] (JBIDE-19795) Bower support
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19795?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-19795:
----------------------------------------
Description:
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"
was:
Need to have initial [Bower|http://bower.io/] tools support for JBDS 9:
*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"
> 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, 11 months
[JBoss JIRA] (JBIDE-19795) Bower support
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19795?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-19795:
----------------------------------------
Summary: Bower support (was: Bower support for JBDS 9)
> 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 for JBDS 9:
> *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, 11 months
[JBoss JIRA] (JBIDE-19795) Bower support for JBDS 9
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19795?page=com.atlassian.jira.plugi... ]
Ilya Buziuk updated JBIDE-19795:
--------------------------------
Description:
Need to have initial [Bower|http://bower.io/] tools support for JBDS 9:
*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"
was:
Need to have initial [Bower|http://bower.io/] tools support for JBDS 9:
*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 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"
> Bower support for JBDS 9
> ------------------------
>
> 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 for JBDS 9:
> *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, 11 months
[JBoss JIRA] (JBIDE-19795) Bower support for JBDS 9
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19795?page=com.atlassian.jira.plugi... ]
Ilya Buziuk updated JBIDE-19795:
--------------------------------
Description:
Need to have initial [Bower|http://bower.io/] tools support for JBDS 9:
*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 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"
was:
Need to have initial [Bower|http://bower.io/] tools support for JBDS 9:
*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 your 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 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"
> Bower support for JBDS 9
> ------------------------
>
> 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 for JBDS 9:
> *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 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, 11 months