[JBoss JIRA] (JBIDE-19879) Add o.e.remote and o.e.launchbar to TP
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19879?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-19879 at 5/27/15 1:06 PM:
-------------------------------------------------------------
TL;DR, here's a PR:
https://github.com/jbosstools/jbosstools-target-platforms/pull/145
p2diff:
{code}
p2diff -onlylatest http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.5... file:///home/nboldt/tru/targetplatforms/jbosstools/multiple/target/jbosstools-multiple.target.repo/
> org.eclipse.launchbar.core [1.0.0.201505051901]
> org.eclipse.remote.ui [2.0.0.201505042103]
> org.eclipse.launchbar.ui [1.0.0.201505051901]
> org.eclipse.remote.core [2.0.0.201505042103]
=== Summary ===
file:///home/nboldt/tru/targetplatforms/jbosstools/multiple/target/jbosstools-multiple.target.repo/ contains 4 unique IUs
{code}
was (Author: nickboldt):
TL;DR, here's a PR:
https://github.com/jbosstools/jbosstools-target-platforms/pull/145
> Add o.e.remote and o.e.launchbar to TP
> --------------------------------------
>
> Key: JBIDE-19879
> URL: https://issues.jboss.org/browse/JBIDE-19879
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: server, target-platform
> Affects Versions: 4.3.0.Beta2
> Reporter: Rob Stryker
> Assignee: Nick Boldt
>
> *Reason:* JBIDE-19711 - WTP servertools integration with CDT launchbar
> *Project page/sources:* ... Requires dependencies on CDT and Launchbar. Launchbar is in http://www.eclipse.org/cdt/ and o.e.remote is in http://www.eclipse.org/ptp/
> *Version:* - Required launchbar is 1.0.0 found in MASTER at their repository. There is no released version yet with the stable API required. Required o.e.remote version is 2.0.0 in MASTER at their repository. There is no released version yet with the stable API required.
> *License and owner:* ... Both are eclipse projects licensed under EPL
> *Original p2 repo:* I am unable to locate the original update sites / p2 repos. PTP does not seem to have an update site URL to the best of my searching (http://download.eclipse.org/tools/ptp/builds/9.0.0/ does not list an update site url, but does have a zip containing an update site). CDT does not list update sites for mars at https://eclipse.org/cdt/downloads.php
> *JBoss mirror:* - Not sure what's applicable here. http://download.jboss.org/jbosstools/updates/requirements/mars/2015050810... does have all plugins needed, but none are the API required, as we require the code from Master.
> *Include Sources: - It's always nice to include sources for devs who build tp locally with the fetch-sources flag ;)
> *Affected projects: - jbosstools-server
> *Include in JBDS:* - No, for now.
> *Type of dependency:* distribution
> *List of bundles added/removed:* - At this time, I expect to require org.eclipse.launchbar.core, org.eclipse.launchbar.ui, org.eclipse.remote.core, org.eclipse.remote.ui.
> Unfortunately I'm unable to test if this is sufficient, at the moment. There may be other plugins that are transient deps somehow that I'm not seeing since I don't have a TP to build against that works.
> If applicable:
> *non-p2 repository:* ???
> *non-p2 ids:* ???
> Suggested Patch for TP: - At this point, I have no suggested patch. I do not know how to add a dependency on nightly builds for these two blocks of code. Also, I'm a bit confused why http://download.jboss.org/jbosstools/updates/requirements/mars/2015050810... will list a plugin (for example org.eclipse.cdt.core.native_5.8.0.201505050312.jar) but the .target file references a feature group (?) which is not present in the requirements/mars folder, such as <unit id="org.eclipse.cdt.native.feature.group" version="8.7.0.201505050312"/>
> I'm also a bit confused where you're pulling the feature group name / id from, or its version, as the version of the feature group does not seem to match the version of the plugin. Furthermore, the mars repo mentioned above does not seem to include any file matching the string org.eclipse.cdt.native.feature.group
> So I'm not sure how you're converting a required plugin id to a feature group. The devdoc also provides no assistance in this matter.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years, 1 month
[JBoss JIRA] (JBIDE-19879) Add o.e.remote and o.e.launchbar to TP
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19879?page=com.atlassian.jira.plugi... ]
Nick Boldt reassigned JBIDE-19879:
----------------------------------
Assignee: Nick Boldt
> Add o.e.remote and o.e.launchbar to TP
> --------------------------------------
>
> Key: JBIDE-19879
> URL: https://issues.jboss.org/browse/JBIDE-19879
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: server, target-platform
> Affects Versions: 4.3.0.Beta2
> Reporter: Rob Stryker
> Assignee: Nick Boldt
>
> *Reason:* JBIDE-19711 - WTP servertools integration with CDT launchbar
> *Project page/sources:* ... Requires dependencies on CDT and Launchbar. Launchbar is in http://www.eclipse.org/cdt/ and o.e.remote is in http://www.eclipse.org/ptp/
> *Version:* - Required launchbar is 1.0.0 found in MASTER at their repository. There is no released version yet with the stable API required. Required o.e.remote version is 2.0.0 in MASTER at their repository. There is no released version yet with the stable API required.
> *License and owner:* ... Both are eclipse projects licensed under EPL
> *Original p2 repo:* I am unable to locate the original update sites / p2 repos. PTP does not seem to have an update site URL to the best of my searching (http://download.eclipse.org/tools/ptp/builds/9.0.0/ does not list an update site url, but does have a zip containing an update site). CDT does not list update sites for mars at https://eclipse.org/cdt/downloads.php
> *JBoss mirror:* - Not sure what's applicable here. http://download.jboss.org/jbosstools/updates/requirements/mars/2015050810... does have all plugins needed, but none are the API required, as we require the code from Master.
> *Include Sources: - It's always nice to include sources for devs who build tp locally with the fetch-sources flag ;)
> *Affected projects: - jbosstools-server
> *Include in JBDS:* - No, for now.
> *Type of dependency:* distribution
> *List of bundles added/removed:* - At this time, I expect to require org.eclipse.launchbar.core, org.eclipse.launchbar.ui, org.eclipse.remote.core, org.eclipse.remote.ui.
> Unfortunately I'm unable to test if this is sufficient, at the moment. There may be other plugins that are transient deps somehow that I'm not seeing since I don't have a TP to build against that works.
> If applicable:
> *non-p2 repository:* ???
> *non-p2 ids:* ???
> Suggested Patch for TP: - At this point, I have no suggested patch. I do not know how to add a dependency on nightly builds for these two blocks of code. Also, I'm a bit confused why http://download.jboss.org/jbosstools/updates/requirements/mars/2015050810... will list a plugin (for example org.eclipse.cdt.core.native_5.8.0.201505050312.jar) but the .target file references a feature group (?) which is not present in the requirements/mars folder, such as <unit id="org.eclipse.cdt.native.feature.group" version="8.7.0.201505050312"/>
> I'm also a bit confused where you're pulling the feature group name / id from, or its version, as the version of the feature group does not seem to match the version of the plugin. Furthermore, the mars repo mentioned above does not seem to include any file matching the string org.eclipse.cdt.native.feature.group
> So I'm not sure how you're converting a required plugin id to a feature group. The devdoc also provides no assistance in this matter.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years, 1 month
[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:
------------------------------------
Depends on JBIDE-19879
> 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)
11 years, 1 month
[JBoss JIRA] (JBIDE-19879) Add o.e.remote and o.e.launchbar to TP
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19879?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-19879:
------------------------------------
All four requested plugins are here:
http://download.jboss.org/jbosstools/updates/requirements/mars/2015050810...
> Add o.e.remote and o.e.launchbar to TP
> --------------------------------------
>
> Key: JBIDE-19879
> URL: https://issues.jboss.org/browse/JBIDE-19879
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: server, target-platform
> Affects Versions: 4.3.0.Beta2
> Reporter: Rob Stryker
>
> *Reason:* JBIDE-19711 - WTP servertools integration with CDT launchbar
> *Project page/sources:* ... Requires dependencies on CDT and Launchbar. Launchbar is in http://www.eclipse.org/cdt/ and o.e.remote is in http://www.eclipse.org/ptp/
> *Version:* - Required launchbar is 1.0.0 found in MASTER at their repository. There is no released version yet with the stable API required. Required o.e.remote version is 2.0.0 in MASTER at their repository. There is no released version yet with the stable API required.
> *License and owner:* ... Both are eclipse projects licensed under EPL
> *Original p2 repo:* I am unable to locate the original update sites / p2 repos. PTP does not seem to have an update site URL to the best of my searching (http://download.eclipse.org/tools/ptp/builds/9.0.0/ does not list an update site url, but does have a zip containing an update site). CDT does not list update sites for mars at https://eclipse.org/cdt/downloads.php
> *JBoss mirror:* - Not sure what's applicable here. http://download.jboss.org/jbosstools/updates/requirements/mars/2015050810... does have all plugins needed, but none are the API required, as we require the code from Master.
> *Include Sources: - It's always nice to include sources for devs who build tp locally with the fetch-sources flag ;)
> *Affected projects: - jbosstools-server
> *Include in JBDS:* - No, for now.
> *Type of dependency:* distribution
> *List of bundles added/removed:* - At this time, I expect to require org.eclipse.launchbar.core, org.eclipse.launchbar.ui, org.eclipse.remote.core, org.eclipse.remote.ui.
> Unfortunately I'm unable to test if this is sufficient, at the moment. There may be other plugins that are transient deps somehow that I'm not seeing since I don't have a TP to build against that works.
> If applicable:
> *non-p2 repository:* ???
> *non-p2 ids:* ???
> Suggested Patch for TP: - At this point, I have no suggested patch. I do not know how to add a dependency on nightly builds for these two blocks of code. Also, I'm a bit confused why http://download.jboss.org/jbosstools/updates/requirements/mars/2015050810... will list a plugin (for example org.eclipse.cdt.core.native_5.8.0.201505050312.jar) but the .target file references a feature group (?) which is not present in the requirements/mars folder, such as <unit id="org.eclipse.cdt.native.feature.group" version="8.7.0.201505050312"/>
> I'm also a bit confused where you're pulling the feature group name / id from, or its version, as the version of the feature group does not seem to match the version of the plugin. Furthermore, the mars repo mentioned above does not seem to include any file matching the string org.eclipse.cdt.native.feature.group
> So I'm not sure how you're converting a required plugin id to a feature group. The devdoc also provides no assistance in this matter.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years, 1 month
[JBoss JIRA] (JBIDE-19641) Big war deployment via management API gets stuck
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19641?page=com.atlassian.jira.plugi... ]
Martin Malina updated JBIDE-19641:
----------------------------------
Attachment: stuck-deploy-eap-jstack-rhel.log
stuck-deploy-jstack-rhel.log
stuck-deploy-eap-jstack-osx.log
stuck-deploy-jstack-osx.log
OK, here are the logs. I kept it running all the time since my last comment. On both OS's it stalled at 72 % and it still says Publishing to JBoss EAP 6.4...
I think you're interested in the IDE process, but I also attach logs for the server in case it's useful.
> Big war deployment via management API gets stuck
> ------------------------------------------------
>
> Key: JBIDE-19641
> URL: https://issues.jboss.org/browse/JBIDE-19641
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.3.0.Alpha2
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.3.0.Beta1
>
> Attachments: stuck-deploy-eap-jstack-osx.log, stuck-deploy-eap-jstack-rhel.log, stuck-deploy-jstack-osx.log, stuck-deploy-jstack-rhel.log
>
>
> When you try to deploy some really big war (~500 MB) to EAP 6.3 via management api, it will not go through.
> This is a follow-up of JBIDE-19350 which previously reported this, but Rob eventually used that JIRA to fix a side issue - the stuck operation could not be canceled.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years, 1 month
[JBoss JIRA] (JBIDE-19792) antlr packages and lib not exported in Hibernate Tools 4.0.1
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19792?page=com.atlassian.jira.plugi... ]
Koen Aers commented on JBIDE-19792:
-----------------------------------
Hi Bastian,
You should be able to not use the org.hibernate.eclipse.libs plugin by depending on org.jboss.tools.hibernate3_5 in your case. When you move to Mars the classes are in org.jboss.tools.hibernate.runtime.v_3_5 instead. However, depending on those plugins limits your code to only support Hibernate 3.5. Maybe that is what you want, but if it's not, you probably need to use introspection to not use a particular version of Hibernate.
Including the antlr and Hibernate libraries in your plugin is also an option but obviously in this case you will also only support the included Hibernate version.
Cheers,
Koen
> antlr packages and lib not exported in Hibernate Tools 4.0.1
> ------------------------------------------------------------
>
> Key: JBIDE-19792
> URL: https://issues.jboss.org/browse/JBIDE-19792
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Affects Versions: 4.2.3.Final
> Environment: Eclipse Luna SR2
> Reporter: Bastian Ulke
> Assignee: Koen Aers
> Attachments: B82_MANIFEST.MF, B95_MANIFEST.MF
>
>
> I am currently working on an Eclipse-Plugin that is built on top of the
> Hibernate Tools project. For example, I am using the following statements
> to get the AST of a named query:
> {code}
> try {
> HqlParser parser = HqlParser.getInstance(statementString);
> parser.statement();
> } catch (RecognitionException | TokenStreamException e) {
> e.printStackTrace();
> }
> AST statementAst = parser.getAST();
> {code}
> For this to work well with Hibernate Tools Version 4.0.0, I added bundle
> org.hibernate.eclipse.libs as required bundle to my plug-in configuration
> (which resolved to
> org.hibernate.eclipse.libs_4.0.0.Final-v20141016-1911-B82 so far).
> However, I now updated to Hiberate Tools 4.0.1
> (org.hibernate.eclipse.libs_4.0.1.Final-v20150324-2307-B95). The problem I
> have now is that the following imports cannot be resolved:
> import antlr.RecognitionException;
> import antlr.TokenStreamException;
> import antlr.collections.AST;
> The problem seems to arise from the fact, that in the new version's
> MANIFEST.MF, the antlr... packages are not exported and
> lib/hibernate/antlr-2.7.6.jar is not listed in the Bundle-ClassPath any
> more (I reformatted both MANIFEST.MFs, that you can find attached, to allow
> a convenient comparison). After manually adding the antlr-related entries
> to the new version's MANIFEST.MF, my code works pretty well again.
> I agree, that internal libraries should generally not be exported. However,
> org.hibernate.hql.ast.HqlParser is exported -- so why not its prerequesites?
> (By the way, I'd be fine with integrating another library into my project.
> However, I tried to manally add antlr-2.7.6.jar as library to
> my project, which solved the compilation error, but yields a
> java.lang.ClassNotFoundException: antlr.LLkParser cannot be found by
> org.hibernate.eclipse.libs_4.0.1.Final-v20150324-2307-B95.)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years, 1 month