[JBoss JIRA] (JBIDE-13438) jboss-packaging-maven-plugin jboss-esb + m2e
by Manosh C (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13438?page=com.atlassian.jira.plugi... ]
Manosh C updated JBIDE-13438:
-----------------------------
Attachment: test-m2e-esb-sar.zip
jboss-tools-m2e-esb-sar-sources.zip
> jboss-packaging-maven-plugin jboss-esb + m2e
> --------------------------------------------
>
> Key: JBIDE-13438
> URL: https://issues.jboss.org/browse/JBIDE-13438
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: esb, integration-platform, maven
> Reporter: Manosh C
> Assignee: Brian Fitzpatrick
> Fix For: 4.2.x
>
> Attachments: jboss-tools-m2e-esb-sar-sources.zip, test-m2e-esb-sar.zip, testparent.zip
>
>
> Hi,
>
> Does jboss-packaging-maven-plugin m2e connector work for jboss-esb? When I import a maven jboss-esb project into eclipse (m2e installed), it does not covert it into an Eclipse JBoss ESB (facet is not enabled and dependecies are not set) project. I tried almost all versions of eclipse, m2e, jboss tools and jboss soa tools, to make it work, but no use. This is my work around for now
>
> 1. Turn on facet nature and enable JBOSS ESB nature.
> 2. Then it get recognized as a deployable artifact on JBoss server.
> 3. Manually add all dependencies in "Deployment and Assembly section".
>
> What I was expecting was all steps should have been done by m2e jboss esb (jboss-packaging-maven-plugin) connector. I could not find a relevant post or article related to it. Does this feature ever supported?
>
> Thank you in advance.
> Manosh
--
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-16280) VPE/XulRunner crashes workbench
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16280?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-16280 at 12/18/13 11:43 AM:
---------------------------------------------------------------
One idea:
https://github.com/jbosstools/jbosstools-xulrunner/pull/12
https://github.com/jbosstools/jbosstools-build-sites/pull/125
Will likely have to remove things from VPE too, such as:
https://github.com/jbosstools/jbosstools-vpe/blob/master/features/org.jbo...
https://github.com/jbosstools/jbosstools-vpe/blob/master/plugins/org.jbos...
https://github.com/jbosstools/jbosstools-vpe/blob/master/tests/pom.xml
plus, for swt/xulrunner these files may also be affected:
https://github.com/jbosstools/jbosstools-vpe/blob/master/plugins/org.jbos...
https://github.com/jbosstools/jbosstools-vpe/blob/master/plugins/org.jbos...
https://github.com/jbosstools/jbosstools-vpe/blob/master/plugins/org.jbos...
https://github.com/jbosstools/jbosstools-vpe/blob/master/plugins/org.jbos...
https://github.com/jbosstools/jbosstools-vpe/blob/master/products/browser...
---
When I built locally the Xulrunner site from master branch after applying the first PR, the plugins were missing from the site. Then I built the JBT aggregate site from master branch using the second PR above, but both lin_32 and lin_64 plugins were present in the resulting site (presumably pulled in from org.jboss.tools.xulrunner.feature and org.jboss.tools.vpe.xulrunner depending on them).
But when I installed the VPE feature (org.jboss.tools.vpe.xulrunner_3.5.100.Alpha1-v20131213-1617-B466.jar) into Eclipse 4.4.0.M3 Luna JEE bundle, it was OK - Eclipse didn't freeze or crash.
It wasn't until I then installed all the rest of JBT (including org.jboss.tools.vpe.browsersim.browser) that the crashing/halting behaviour came back (actually I'm running w/ export GTK3=0, and it means it takes forever for Eclipse to start, but when it does, it works).
So this test is inconclusive. Will have to rip more stuff out of VPE to do a more complete test, and disable the GTK3=0 workaround.
was (Author: nickboldt):
One idea:
https://github.com/jbosstools/jbosstools-xulrunner/pull/12
https://github.com/jbosstools/jbosstools-build-sites/pull/125
Will likely have to remove things from VPE too, such as:
https://github.com/jbosstools/jbosstools-vpe/blob/master/features/org.jbo...
plus:
./plugins/org.jboss.tools.vpe.browsersim.browser/src/org/jboss/tools/vpe/browsersim/browser/internal/WebKitBrowser_gtk_linux_x86_64.java
./plugins/org.jboss.tools.vpe.browsersim.browser/src/org/jboss/tools/vpe/browsersim/browser/internal/WebKitBrowser_gtk_linux_x86.java
./plugins/org.jboss.tools.vpe.browsersim.browser/src/org/jboss/tools/vpe/browsersim/browser/WebKitBrowserFactory.java
and
./plugins/org.jboss.tools.vpe.xulrunner/META-INF/MANIFEST.MF
./plugins/org.jboss.tools.vpe.xulrunner/src/org/jboss/tools/vpe/xulrunner/browser/XulRunnerBrowser.java
./products/browsersim-standalone/pom.xml
./tests/pom.xml
---
When I built locally the Xulrunner site from master branch after applying the first PR, the plugins were missing from the site. Then I built the JBT aggregate site from master branch using the second PR above, but both lin_32 and lin_64 plugins were present in the resulting site (presumably pulled in from org.jboss.tools.xulrunner.feature and org.jboss.tools.vpe.xulrunner depending on them).
But when I installed the VPE feature (org.jboss.tools.vpe.xulrunner_3.5.100.Alpha1-v20131213-1617-B466.jar) into Eclipse 4.4.0.M3 Luna JEE bundle, it was OK - Eclipse didn't freeze or crash.
It wasn't until I then installed all the rest of JBT (including org.jboss.tools.vpe.browsersim.browser) that the crashing/halting behaviour came back (actually I'm running w/ export GTK3=0, and it means it takes forever for Eclipse to start, but when it does, it works).
So this test is inconclusive. Will have to rip more stuff out of VPE to do a more complete test, and disable the GTK3=0 workaround.
> VPE/XulRunner crashes workbench
> -------------------------------
>
> Key: JBIDE-16280
> URL: https://issues.jboss.org/browse/JBIDE-16280
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: xulrunner
> Affects Versions: 4.2.0.Alpha1
> Reporter: Mickael Istria
> Priority: Critical
> Fix For: 4.2.0.Alpha2
>
> Attachments: hs_err_pid20688.log
>
>
> After an install of JBDS 8.0.0.Alpha1 from installer (built locally with fixes from JBDS-2861), the application crashes a few seconds after startup.
> JVM creates me a thread dump, that you can find attached. Here is the header:
> {code}
> #
> # A fatal error has been detected by the Java Runtime Environment:
> #
> # SIGSEGV (0xb) at pc=0x00007fdea49f3255, pid=18578, tid=140596949411584
> #
> # JRE version: 7.0_25-b30
> # Java VM: OpenJDK 64-Bit Server VM (23.7-b01 mixed mode linux-amd64 compressed oops)
> # Problematic frame:
> # C [libxul.so+0xc81255] JSD_DebuggerOnForUser+0x978a2
> #
> {code}
> I'm running on Ubuntu 12.04.
--
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-16280) VPE/XulRunner crashes workbench
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16280?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-16280 at 12/18/13 11:18 AM:
---------------------------------------------------------------
One idea:
https://github.com/jbosstools/jbosstools-xulrunner/pull/12
https://github.com/jbosstools/jbosstools-build-sites/pull/125
Will likely have to remove things from VPE too, such as:
https://github.com/jbosstools/jbosstools-vpe/blob/master/features/org.jbo...
plus:
./plugins/org.jboss.tools.vpe.browsersim.browser/src/org/jboss/tools/vpe/browsersim/browser/internal/WebKitBrowser_gtk_linux_x86_64.java
./plugins/org.jboss.tools.vpe.browsersim.browser/src/org/jboss/tools/vpe/browsersim/browser/internal/WebKitBrowser_gtk_linux_x86.java
./plugins/org.jboss.tools.vpe.browsersim.browser/src/org/jboss/tools/vpe/browsersim/browser/WebKitBrowserFactory.java
and
./plugins/org.jboss.tools.vpe.xulrunner/META-INF/MANIFEST.MF
./plugins/org.jboss.tools.vpe.xulrunner/src/org/jboss/tools/vpe/xulrunner/browser/XulRunnerBrowser.java
./products/browsersim-standalone/pom.xml
./tests/pom.xml
---
When I built locally the Xulrunner site from master branch after applying the first PR, the plugins were missing from the site. Then I built the JBT aggregate site from master branch using the second PR above, but both lin_32 and lin_64 plugins were present in the resulting site (presumably pulled in from org.jboss.tools.xulrunner.feature and org.jboss.tools.vpe.xulrunner depending on them).
But when I installed the VPE feature (org.jboss.tools.vpe.xulrunner_3.5.100.Alpha1-v20131213-1617-B466.jar) into Eclipse 4.4.0.M3 Luna JEE bundle, it was OK - Eclipse didn't freeze or crash.
It wasn't until I then installed all the rest of JBT (including org.jboss.tools.vpe.browsersim.browser) that the crashing/halting behaviour came back (actually I'm running w/ export GTK3=0, and it means it takes forever for Eclipse to start, but when it does, it works).
So this test is inconclusive. Will have to rip more stuff out of VPE to do a more complete test, and disable the GTK3=0 workaround.
was (Author: nickboldt):
One idea:
https://github.com/jbosstools/jbosstools-xulrunner/pull/12
https://github.com/jbosstools/jbosstools-build-sites/pull/125
Will likely have to remove things from VPE too, such as:
https://github.com/jbosstools/jbosstools-vpe/blob/master/features/org.jbo...
plus:
./plugins/org.jboss.tools.vpe.browsersim.browser/src/org/jboss/tools/vpe/browsersim/browser/internal/WebKitBrowser_gtk_linux_x86_64.java
./plugins/org.jboss.tools.vpe.browsersim.browser/src/org/jboss/tools/vpe/browsersim/browser/internal/WebKitBrowser_gtk_linux_x86.java
./plugins/org.jboss.tools.vpe.browsersim.browser/src/org/jboss/tools/vpe/browsersim/browser/WebKitBrowserFactory.java
and
./plugins/org.jboss.tools.vpe.xulrunner/META-INF/MANIFEST.MF
./plugins/org.jboss.tools.vpe.xulrunner/src/org/jboss/tools/vpe/xulrunner/browser/XulRunnerBrowser.java
./products/browsersim-standalone/pom.xml
./tests/pom.xml
---
When I built locally the Xulrunner site from master branch after applying the first PR, the plugins were missing from the site. Then I built the JBT aggregate site from master branch using the second PR above, but both lin_32 and lin_64 plugins were present in the resulting site (presumably pulled in from org.jboss.tools.xulrunner.feature and org.jboss.tools.vpe.xulrunner depending on them).
But when I installed the VPE feature (org.jboss.tools.vpe.xulrunner_3.5.100.Alpha1-v20131213-1617-B466.jar) into Eclipse 4.4.0.M3 Luna JEE bundle, it was OK - Eclipse didn't freeze or crash.
It wasn't until I then installed all the rest of JBT (including org.jboss.tools.vpe.browsersim.browser) that the crashing/halting behaviour came back. So this test is inconclusive. Will have to rip more stuff out of VPE to do a more complete test.
> VPE/XulRunner crashes workbench
> -------------------------------
>
> Key: JBIDE-16280
> URL: https://issues.jboss.org/browse/JBIDE-16280
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: xulrunner
> Affects Versions: 4.2.0.Alpha1
> Reporter: Mickael Istria
> Priority: Critical
> Fix For: 4.2.0.Alpha2
>
> Attachments: hs_err_pid20688.log
>
>
> After an install of JBDS 8.0.0.Alpha1 from installer (built locally with fixes from JBDS-2861), the application crashes a few seconds after startup.
> JVM creates me a thread dump, that you can find attached. Here is the header:
> {code}
> #
> # A fatal error has been detected by the Java Runtime Environment:
> #
> # SIGSEGV (0xb) at pc=0x00007fdea49f3255, pid=18578, tid=140596949411584
> #
> # JRE version: 7.0_25-b30
> # Java VM: OpenJDK 64-Bit Server VM (23.7-b01 mixed mode linux-amd64 compressed oops)
> # Problematic frame:
> # C [libxul.so+0xc81255] JSD_DebuggerOnForUser+0x978a2
> #
> {code}
> I'm running on Ubuntu 12.04.
--
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-16280) VPE/XulRunner crashes workbench
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16280?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-16280:
------------------------------------
One idea:
https://github.com/jbosstools/jbosstools-xulrunner/pull/12
https://github.com/jbosstools/jbosstools-build-sites/pull/125
Will likely have to remove things from VPE too, such as:
https://github.com/jbosstools/jbosstools-vpe/blob/master/features/org.jbo...
plus:
./plugins/org.jboss.tools.vpe.browsersim.browser/src/org/jboss/tools/vpe/browsersim/browser/internal/WebKitBrowser_gtk_linux_x86_64.java
./plugins/org.jboss.tools.vpe.browsersim.browser/src/org/jboss/tools/vpe/browsersim/browser/internal/WebKitBrowser_gtk_linux_x86.java
./plugins/org.jboss.tools.vpe.browsersim.browser/src/org/jboss/tools/vpe/browsersim/browser/WebKitBrowserFactory.java
and
./plugins/org.jboss.tools.vpe.xulrunner/META-INF/MANIFEST.MF
./plugins/org.jboss.tools.vpe.xulrunner/src/org/jboss/tools/vpe/xulrunner/browser/XulRunnerBrowser.java
./products/browsersim-standalone/pom.xml
./tests/pom.xml
---
When I built locally the Xulrunner site from master branch after applying the first PR, the plugins were missing from the site. Then I built the JBT aggregate site from master branch using the second PR above, but both lin_32 and lin_64 plugins were present in the resulting site (presumably pulled in from org.jboss.tools.xulrunner.feature and org.jboss.tools.vpe.xulrunner depending on them).
But when I installed the VPE feature (org.jboss.tools.vpe.xulrunner_3.5.100.Alpha1-v20131213-1617-B466.jar) into Eclipse 4.4.0.M3 Luna JEE bundle, it was OK - Eclipse didn't freeze or crash.
It wasn't until I then installed all the rest of JBT (including org.jboss.tools.vpe.browsersim.browser) that the crashing/halting behaviour came back. So this test is inconclusive. Will have to rip more stuff out of VPE to do a more complete test.
> VPE/XulRunner crashes workbench
> -------------------------------
>
> Key: JBIDE-16280
> URL: https://issues.jboss.org/browse/JBIDE-16280
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: xulrunner
> Affects Versions: 4.2.0.Alpha1
> Reporter: Mickael Istria
> Priority: Critical
> Fix For: 4.2.0.Alpha2
>
> Attachments: hs_err_pid20688.log
>
>
> After an install of JBDS 8.0.0.Alpha1 from installer (built locally with fixes from JBDS-2861), the application crashes a few seconds after startup.
> JVM creates me a thread dump, that you can find attached. Here is the header:
> {code}
> #
> # A fatal error has been detected by the Java Runtime Environment:
> #
> # SIGSEGV (0xb) at pc=0x00007fdea49f3255, pid=18578, tid=140596949411584
> #
> # JRE version: 7.0_25-b30
> # Java VM: OpenJDK 64-Bit Server VM (23.7-b01 mixed mode linux-amd64 compressed oops)
> # Problematic frame:
> # C [libxul.so+0xc81255] JSD_DebuggerOnForUser+0x978a2
> #
> {code}
> I'm running on Ubuntu 12.04.
--
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-16316) Add Hybrid Tools to Eclipse Marketplace
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16316?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-16316:
------------------------------------
Note too that as this is a deviation from what was agreed to when planning JBDS 7.1.0 / JBT 4.1.1, I'd like to see a few +1 signatures from [~maxandersen], [~jpallich], [~ldimaggio], [~mmurray], [~mmusaji] confirming :
* that it's acceptable to cause "Tech Preview" plugins to be installed as part of the default Marketplace experience, and
* that no screenshots in docs will need to be redone.
So say we all?
> Add Hybrid Tools to Eclipse Marketplace
> ---------------------------------------
>
> Key: JBIDE-16316
> URL: https://issues.jboss.org/browse/JBIDE-16316
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: marketplace
> Reporter: Burr Sutter
> Attachments: jbt-411-stable-site.png
>
>
> Hybrid Tools are currently not listed under Eclipse Marketplace.
> http://www.screencast.com/t/e3f4UOsEx
> and they should be a popular feature.
>
--
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