[JBoss JIRA] (JBIDE-19879) Add o.e.remote and o.e.launchbar to TP
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19879?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-19879:
----------------------------------------
{quote}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"/>
Furthermore, the mars repo mentioned above does not seem to include any file matching the string org.eclipse.cdt.native.feature.group{quote}
The Mars repository does contain the feature: http://download.jboss.org/jbosstools/updates/requirements/mars/2015050810... . You got confused because p2 artifact name for a feature is suffixed with .feature.group.
{quote}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.{quote}
Many Eclipse projects (Platform, WebTools, CDT...) use semantic versioning and last-modification timestamp as qualifiers, so that it's often the case that the plugin version differs from the version of the features containing it. There is nothing to worry on this topic.
{quote}So I'm not sure how you're converting a required plugin id to a feature group{quote}
We usually just investigate which feature contains the required plugin, and we reference it. Or, if it's only for a few autonomous bundles, we can also directly reference those bundles in the .target, so we may avoid some useless artifacts provided by features.
> 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)
10 years, 10 months
[JBoss JIRA] (JBIDE-19878) devdoc for Requesting changes to TP needs clarifications
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19878?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-19878:
----------------------------------------
Apparently, documentation should also state that for TP, we usually don't allow to rebuild from source and consume directly 3rd-party binaries. So it means that having 3rd-party binaries is a requirement before requesting inclusion in our TP.
> devdoc for Requesting changes to TP needs clarifications
> --------------------------------------------------------
>
> Key: JBIDE-19878
> URL: https://issues.jboss.org/browse/JBIDE-19878
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: build
> Reporter: Rob Stryker
> Assignee: Nick Boldt
>
> The devdoc page building/target_platforms/target_platforms_updates.adoc#update-the-target-files is very confusing for someone who's just trying to get something added to TP. If build team insists on regular devs following this workflow / policy, it must be organized properly so as not to confuse average devs.
> 1) Checking if requirements is currently mirrored already should be very high up in the ToC of the page
> 2) Page should indicate that all of Mars is already duplicated, and does not need its own special folder with a build.xml
> 3) Page should then indicate if the IU you need is not in the 'mars' folder, it must have its own folder with a build.xml
> 4) Page should prioritize creation of the build.xml higher above making changes to the .target file
> Basically, the entire page needs to be revisted and seen through the eyes of someone who hasn't made TP updates before. You need to direct the dev in what they need to do first, especially if you intend to keep linking this document
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19879) Add o.e.remote and o.e.launchbar to TP
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19879?page=com.atlassian.jira.plugi... ]
Mickael Istria edited comment on JBIDE-19879 at 5/27/15 3:20 AM:
-----------------------------------------------------------------
PTP doesn't include the org.eclipse.remote bundle or feature.
For CDT, please get in touch with them to find out what's the URL of their snapshot or milestone repository which would include the launchbar. I'd rather avoid to maintain a parallel build of CDT. The best thing would be that the launchbar gets published in their regular site or in an alternative one ASAP.
We cannot process the TP change until those 2 points are resolved.
was (Author: mickael_istria):
For PTP, we can use the zip and make our mirror from it.
For CDT, please get in touch with them to find out what's the URL of their snapshot or milestone repository which would include the launchbar. I'd rather avoid to maintain a parallel build of CDT. The best thing would be that the launchbar gets published in their regular site or in an alternative one ASAP.
> 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)
10 years, 10 months
[JBoss JIRA] (JBDS-3261) JSR-356: Websockets. Import, build, run on server
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBDS-3261?page=com.atlassian.jira.plugin.... ]
Marián Labuda commented on JBDS-3261:
-------------------------------------
Well, after importing websocket examples there is prompt to install m2e connectors. First one is maven-compiler-plugin:3.1, which is OK. Second one is groovy-eclipse-compiler:2.8.0 which is causing issues. There are errors on imported projects because specific maven structure of source code is not recognized (maven compiler plugin has dependency on groovy eclipse compiler). The issue is described as following
{code}
The declared package "org.javaee7.websocket.endpoint.security" does not match the expected package "main.java.org.javaee7.websocket.endpoint.security"
{code}
Maven build runs OK. Result is same as build from command line. Used "mvn clean install" to get .war.
Another issue raise during the deployment. Deployment from jboss-cli works OK. Deploy by copying *.war file to deployments folder of a server works OK. But deployment from IDE (JBT 4.3.0.Nightly) "Run As - Run on Server" does not deploy project properly. After deployment, the page of deployed project is openable and it display some content, but content related to websockets is shown as error (e.g. "ERROR: undefined").
> JSR-356: Websockets. Import, build, run on server
> -------------------------------------------------
>
> Key: JBDS-3261
> URL: https://issues.jboss.org/browse/JBDS-3261
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: requirements, webservices
> Reporter: Burr Sutter
> Assignee: Xavier Coulon
> Priority: Critical
> Labels: websockets
> Fix For: 9.0.0.Beta1
>
>
> Support for import (without error), build, Run on Server and Debug on Server.
> https://github.com/javaee-samples/javaee7-samples/tree/master/websocket
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19879) Add o.e.remote and o.e.launchbar to TP
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19879?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-19879:
----------------------------------------
For PTP, we can use the zip and make our mirror from it.
For CDT, please get in touch with them to find out what's the URL of their snapshot or milestone repository which would include the launchbar. I'd rather avoid to maintain a parallel build of CDT. The best thing would be that the launchbar gets published in their regular site or in an alternative one ASAP.
> 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)
10 years, 10 months
[JBoss JIRA] (JBIDE-19879) Add o.e.remote and o.e.launchbar to TP
by Rob Stryker (JIRA)
Rob Stryker created JBIDE-19879:
-----------------------------------
Summary: 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)
10 years, 10 months
[JBoss JIRA] (JBIDE-19878) devdoc for Requesting changes to TP needs clarifications
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19878?page=com.atlassian.jira.plugi... ]
Rob Stryker reassigned JBIDE-19878:
-----------------------------------
Assignee: Nick Boldt
> devdoc for Requesting changes to TP needs clarifications
> --------------------------------------------------------
>
> Key: JBIDE-19878
> URL: https://issues.jboss.org/browse/JBIDE-19878
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: build
> Reporter: Rob Stryker
> Assignee: Nick Boldt
>
> The devdoc page building/target_platforms/target_platforms_updates.adoc#update-the-target-files is very confusing for someone who's just trying to get something added to TP. If build team insists on regular devs following this workflow / policy, it must be organized properly so as not to confuse average devs.
> 1) Checking if requirements is currently mirrored already should be very high up in the ToC of the page
> 2) Page should indicate that all of Mars is already duplicated, and does not need its own special folder with a build.xml
> 3) Page should then indicate if the IU you need is not in the 'mars' folder, it must have its own folder with a build.xml
> 4) Page should prioritize creation of the build.xml higher above making changes to the .target file
> Basically, the entire page needs to be revisted and seen through the eyes of someone who hasn't made TP updates before. You need to direct the dev in what they need to do first, especially if you intend to keep linking this document
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19878) devdoc for Requesting changes to TP needs clarifications
by Rob Stryker (JIRA)
Rob Stryker created JBIDE-19878:
-----------------------------------
Summary: devdoc for Requesting changes to TP needs clarifications
Key: JBIDE-19878
URL: https://issues.jboss.org/browse/JBIDE-19878
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: build
Reporter: Rob Stryker
The devdoc page building/target_platforms/target_platforms_updates.adoc#update-the-target-files is very confusing for someone who's just trying to get something added to TP. If build team insists on regular devs following this workflow / policy, it must be organized properly so as not to confuse average devs.
1) Checking if requirements is currently mirrored already should be very high up in the ToC of the page
2) Page should indicate that all of Mars is already duplicated, and does not need its own special folder with a build.xml
3) Page should then indicate if the IU you need is not in the 'mars' folder, it must have its own folder with a build.xml
4) Page should prioritize creation of the build.xml higher above making changes to the .target file
Basically, the entire page needs to be revisted and seen through the eyes of someone who hasn't made TP updates before. You need to direct the dev in what they need to do first, especially if you intend to keep linking this document
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months