[JBoss JIRA] (JBIDE-19795) Bower support
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19795?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-19795:
----------------------------------------
I pushed the PR to master. Looks good for initial commit but we must add some tests *before* we add this plugin to any feature/update site ;)
> 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-19882) Tests in SelectedAlternativeTest fail
by Viacheslav Kabanovich (JIRA)
Viacheslav Kabanovich created JBIDE-19882:
---------------------------------------------
Summary: Tests in SelectedAlternativeTest fail
Key: JBIDE-19882
URL: https://issues.jboss.org/browse/JBIDE-19882
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: cdi
Affects Versions: 4.3.0.Beta1
Reporter: Viacheslav Kabanovich
Assignee: Viacheslav Kabanovich
Fix For: 4.3.0.Beta1
These tests are influenced by DecoratorDefinitionTest and ResolutionByNameTest which replace beans.xml in tck project, but when restoring the initial state, miss that tck has 2 beans.xml resources (in JavaSource/META-INF and in WebContents/WEB-INF), and restore only one of them taken at random.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 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:
-------------------------------------
[~akazakov], PR with initial Bower support was sent to jst - https://github.com/jbosstools/jbosstools-jst/pull/488
> 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-19463) Cannot connect to remote server in JMX Navigator
by Jeff Bride (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19463?page=com.atlassian.jira.plugi... ]
Jeff Bride commented on JBIDE-19463:
------------------------------------
Hi Rob.
Thank you for elaborating. Your explanation makes a lot of sense.
As more and more development of middleware apps in remote public & on-premise cloud environments occurs, JBDS capabilities such as this become important.
Would be nice for a developer with only JBDS on his/her local workstation and creating an app on JBoss middleware hosted in a remote OSE installation to be able to capture JMX statistics for test/troubleshooting purposes.
Wondering if this could potentially be implemented as an optional (disabled by default) extension of JMX Navigator available only by selecting it from Help --> Check For Update ?
thank you!
jeff
> Cannot connect to remote server in JMX Navigator
> ------------------------------------------------
>
> Key: JBIDE-19463
> URL: https://issues.jboss.org/browse/JBIDE-19463
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jmx
> Affects Versions: 4.2.3.CR1, 4.3.0.Alpha1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.3.0.Beta1
>
>
> When you start a remote EAP 6.3 server with management enabled and set up and then want to connect in JMX Navigator, it does not work - double clicking the connection will not do anything and when you right-click, there is no Connect item.
> For local servers this works fine - there is a Connect item when you right-click the server in JMX Navigator.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19776) Create and use Mars RC2 target-platform
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19776?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-19776:
------------------------------------
+1 for "fast merge". Let's push it tomorrow so there's time to review on the mailing list. cc: [~maxandersen].
Note that I've added another commit to https://github.com/jbosstools/jbosstools-target-platforms/pull/146 because there's a newer version of e4.ui available today.
> Create and use Mars RC2 target-platform
> ---------------------------------------
>
> Key: JBIDE-19776
> URL: https://issues.jboss.org/browse/JBIDE-19776
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: target-platform
> Reporter: Nick Boldt
> Assignee: Mickael Istria
> Priority: Blocker
> Fix For: 4.3.0.Beta1
>
> Attachments: jbdevstudio.p2diff.txt, jbdevstudio.p2diff.v20150514.txt, jbdevstudio.p2diff.v3.txt, jbosstools.p2diff.txt, jbosstools.p2diff.v20150514.txt, jbosstools.p2diff.v3.txt
>
>
> Mars M7 was released and contains interesting changes.
> We need to start using it ASAP to leverage new functionalities and adapt to the most important changes.
> However, moving to RC1 or RC2 might be ever better as RC1 includes a fix for JBIDE-19773.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19881) Servertools local build failing with very strange errors
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19881?page=com.atlassian.jira.plugi... ]
Nick Boldt closed JBIDE-19881.
------------------------------
if (fixed && nothing.toQE()){ close(); }
> Servertools local build failing with very strange errors
> --------------------------------------------------------
>
> Key: JBIDE-19881
> URL: https://issues.jboss.org/browse/JBIDE-19881
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, server
> Reporter: Rob Stryker
> Assignee: Mickael Istria
> Priority: Blocker
> Fix For: 4.3.0.Beta1
>
>
> So I tried to run my servertools build while making a patch for https://issues.jboss.org/browse/JBIDE-19801
> And I started getting very very weird errors:
> http://fpaste.org/226368/32788687/
> Nick instructed me to check if my build was using Java8, and it wasn't. Somehow it was still using java7.
> So next, I export JAVA_HOME to a java8 installation, and I get a newer weirder error:
> {code}
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0
> Exception in thread "main" java.lang.reflect.InvocationTargetException
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:483)
> at sun.instrument.InstrumentationImpl.loadClassAndStartAgent(InstrumentationImpl.java:386)
> at sun.instrument.InstrumentationImpl.loadClassAndCallPremain(InstrumentationImpl.java:401)
> Caused by: java.lang.RuntimeException: Class java/util/UUID could not be instrumented.
> at org.jacoco.agent.rt_6l8m50.core.runtime.ModifiedSystemClassRuntime.createFor(ModifiedSystemClassRuntime.java:138)
> at org.jacoco.agent.rt_6l8m50.core.runtime.ModifiedSystemClassRuntime.createFor(ModifiedSystemClassRuntime.java:99)
> at org.jacoco.agent.rt_6l8m50.JacocoAgent.createRuntime(JacocoAgent.java:128)
> at org.jacoco.agent.rt_6l8m50.JacocoAgent.init(JacocoAgent.java:74)
> at org.jacoco.agent.rt_6l8m50.JacocoAgent.premain(JacocoAgent.java:165)
> ... 6 more
> Caused by: java.lang.NoSuchFieldException: $jacocoAccess
> at java.lang.Class.getField(Class.java:1690)
> at org.jacoco.agent.rt_6l8m50.core.runtime.ModifiedSystemClassRuntime.createFor(ModifiedSystemClassRuntime.java:136)
> ... 10 more
> FATAL ERROR in native method: processing of -javaagent failed
> {code}
> I come to find out that the jacoco we're using is org.jacoco.agent/0.6.1.201212231917. This was released, obviously by timestamp, in 2012. I find https://github.com/jacoco/jacoco/issues/74 which was a bug fixed in 2013, after our current jacoco. So if we must now run with java8, then clearly we need a newer jacoco.
> Either way, it seems that either my machine is very messed up, or there's a lot of weird stuff changing on build side that's not matching each other.
> No idea how to fix either bug ;)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBTIS-434) Some features are duplicated on Update Site in site.xml
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBTIS-434?page=com.atlassian.jira.plugin.... ]
Andrej Podhradsky closed JBTIS-434.
-----------------------------------
Verified with JBDS 8.1.0.GA + JBDS-IS 8.0.2.CR1
> Some features are duplicated on Update Site in site.xml
> -------------------------------------------------------
>
> Key: JBTIS-434
> URL: https://issues.jboss.org/browse/JBTIS-434
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: distribution
> Affects Versions: 4.2.2.Final
> Environment: JBDSIS 8.0.2.ER1
> Reporter: Tomáš Sedmík
> Assignee: Paul Leacu
> Priority: Minor
> Fix For: 8.0.1.CR1, 4.2.2.CR1
>
>
> Runtime detectors in _site.xml_ on Update Site are duplicated see:
> http://www.qa.jboss.com/binaries/RHDS/updates/development/luna/integratio...
> {code}
> ...
> <feature id="org.jboss.tools.runtime.drools.detector.feature" url="features/org.jboss.tools.runtime.drools.detector.feature_6.2.0.Final.jar" version="6.2.0.Final">
> <category name="BusinessLogic"/>
> <category name="SOADev"/>
> <category name="SOADev5"/>
> </feature>
> <feature id="org.jboss.tools.runtime.esb.detector.feature" url="features/org.jboss.tools.runtime.esb.detector.feature_1.5.530.Final-v20150310-1957-B70.jar" version="1.5.530.Final-v20150310-1957-B70">
> <category name="SOADev5"/>
> </feature>
> <feature id="org.jboss.tools.runtime.jbpm.detector.feature" url="features/org.jboss.tools.runtime.jbpm.detector.feature_4.5.200.Final-v20130815-1941-B2008.jar" version="4.5.200.Final-v20130815-1941-B2008">
> <category name="SOADev"/>
> <category name="SOADev5"/>
> </feature>
> ...
> <!-- runtime detectors -->
> <feature id="org.jboss.tools.runtime.drools.detector.feature"/>
> <feature id="org.jboss.tools.runtime.esb.detector.feature"/>
> <feature id="org.jboss.tools.runtime.jbpm.detector.feature"/>
> ...
> {code}
> IMHO there should be only one entry for one feature
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months