[JBoss JIRA] (JBIDE-21105) Remove BIRT?
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21105?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov commented on JBIDE-21105:
------------------------------------------------
[~nickboldt] plugins you listed above are the plugins which you add, the plugins which we already have are not included?
{quote}Are you suggesting that we should help them add more Jetty plugins to their update site [1] ?{quote}
I wonder if we can help them and try to contribute moving to 9.3.5(also creating a list of jetty bundles that they need(including dependencies)).
Btw I have a question: We have some jetty dependencies listed in TP. Eclipse itself also have it. Some of this dependencies are the same(i.e. server). Does they "merges" automatically and as a result we have only one bundle installed?
> Remove BIRT?
> ------------
>
> Key: JBIDE-21105
> URL: https://issues.jboss.org/browse/JBIDE-21105
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: birt, target-platform
> Affects Versions: 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.4.0.Alpha1
>
> Attachments: birt-4.5-vs-mars-interim.txt, birt-4.5-vs-mars-interim_summary.txt, birt-depends-on-jetty-deploy-929.png, birt-depends-on-jetty-osgi-boot-929.png, birt-wizard-new-library.png, birt-wizard-new-library__NEON.png, birt-wizards.png, birt-wizards__NEON.png, eclipse-after-birt.png, install-jboss-birt-sites.png, install-jboss-birt-sites__NEON.png, install-jboss-birt.png, install-jboss-birt__NEON.png
>
>
> {quote}
> (2015-11-17 11:42:50) kmarmaliykov: nickboldt: I look into neon M3 and see that there is no jetty 9.2.9 there
> (2015-11-17 11:43:18) nickboldt: kmarmaliykov: yes, 9.2.9 is from Birt site
> (2015-11-17 11:43:21) nickboldt: because Birt needs it
> (2015-11-17 11:43:33) nickboldt: but there's no Birt for Neon yet so we have to include the Birt for Mars
> (2015-11-17 11:43:37) maxandersen: nickboldt: akazakov: are you talking about having birt in Neon ?
> (2015-11-17 11:43:44) maxandersen: afaik birt is dead.
> (2015-11-17 11:43:53) maxandersen: won't participate in neon release afaik.
> (2015-11-17 11:43:56) nickboldt: maxandersen: so we should remove birt from JBT 4.4?
> (2015-11-17 11:44:24) maxandersen: well, check first if birt is actually in neon. if it is not the decision is very easy.
> (2015-11-17 11:44:38) akazakov: +1
> (2015-11-17 11:45:36) maxandersen: if it is in, then lets talk options. but if birt requires us to jump through too many hoops its not worth keeping it in.
> (2015-11-17 11:45:55) nickboldt: birt 4.5.0.v201506092134 is in Neon from 201511131000 (M3) - http://download.eclipse.org/releases/neon/201511131000/
> (2015-11-17 11:47:08) nickboldt: and there's a newer birt 4.5.0.v201510231925 (same major.minor.service, newer datestamp) in http://download.eclipse.org/birt/update-site/mars-interim/
> {quote}
> So, yesterday as part of updates for JBIDE-20976, I pulled a new BIRT mirror here:
> http://download.jboss.org/jbosstools/updates/requirements/birt/4.5.0.v201...
> But we could also just use the old one from Mars.0:
> http://download.jboss.org/jbosstools/updates/requirements/birt/4.5.0.v201...
> Or we could remove support for BIRT and its webtools / charting integration entirely from JBT 4.4.0.Alpha1, since as Max says BIRT is at EOL.
> *DISCUSS*.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-20900) why do we need both zip and tar.gz for org.jboss.tools.releng:jbosstools-releng-publish ?
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20900?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-20900:
----------------------------------------
So you're about to tweak a pom to avoid publishing a file that does not harm; then to tweak job configs to use a .tar.gz instead of a zip; in order to replace ". foo.sh" by "./foo.sh". Well, up to you, but I know funnier ways to waste time :P
> why do we need both zip and tar.gz for org.jboss.tools.releng:jbosstools-releng-publish ?
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-20900
> URL: https://issues.jboss.org/browse/JBIDE-20900
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.3.0.Final, 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Minor
> Fix For: 4.4.0.Alpha1
>
>
> When publishing, we use this:
> {code}
> [jbosstools-build-sites.aggregate.site_4.3.mars] $ /qa/tools/opt/apache-maven-3.2.5/bin/mvn -DTARGET_PLATFORM_VERSION=4.50.0.Final
> -DTARGET_PLATFORM_VERSION_MAXIMUM=4.51.0.Final "-DMAVEN_FLAGS=-B -U -fae -e -P hudson,unified.target,pack200"
> -DskipRevisionCheckWhenPublishing=true "-Dupdate.site.description=Stable Release" -Djbosstools_site_stream=4.3.mars -DtrimVersion=true
> -Dmdep.stripClassifier=true -Dartifact=org.jboss.tools.releng:jbosstools-releng-publish:4.3.0.Final:zip
> -DoutputDirectory=/mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_4.3.mars/sources
> -Dmdep.stripVersion=true org.apache.maven.plugins:maven-dependency-plugin:2.9:unpack
> {code}
> But there's also this:
> {code}
> [INFO] Configured Artifact: org.jboss.tools.releng:jbosstools-releng-publish:4.3.0.Final:tar.gz
> [INFO] Downloading: https://repository.jboss.org/nexus/content/repositories/deprecated/org/jb...
> [INFO] Downloading: https://repository.jboss.org/nexus/content/groups/developer/org/jboss/too...
> [INFO] Downloaded: https://repository.jboss.org/nexus/content/groups/developer/org/jboss/too... (25 KB at 99.3 KB/sec)
> [INFO] Unpacking /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_4.3.mars/.repository/org/jboss/tools/releng/jbosstools-releng-publish/4.3.0.Final/jbosstools-releng-publish-4.3.0.Final.tar.gz to /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_4.3.mars/sources/aggregate/site/target/releng-scripts with includes "" and excludes ""
> [INFO] Expanding: /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_4.3.mars/.repository/org/jboss/tools/releng/jbosstools-releng-publish/4.3.0.Final/jbosstools-releng-publish-4.3.0.Final.tar.gz into /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_4.3.mars/sources/aggregate/site/target/releng-scripts{code}
> So... should we update jobs to fetch and use the .tar.gz because it retains exec perms? Then we can update the assembly.xml to only create the .tar.gz and stop wasting disk space w/ the extra zip.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-20900) why do we need both zip and tar.gz for org.jboss.tools.releng:jbosstools-releng-publish ?
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20900?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-20900:
------------------------------------
You're missing the point. We publish TWO types of artifact here, but we only need to publish ONE.
And yes, retaining exec perms for scripts is better than using a zip, since without proper exec permission, we would need to do this:
{code}. foo.sh{code}
or
{code}chmod +x foo.sh && ./foo.sh{code}
rather than just:
{code}./foo.sh{code}
So, it's simpler and it's more portable across systems. Therefore, rather than creating BOTH zips and tar.gzs, we should only create tar.gzs.
> why do we need both zip and tar.gz for org.jboss.tools.releng:jbosstools-releng-publish ?
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-20900
> URL: https://issues.jboss.org/browse/JBIDE-20900
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.3.0.Final, 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Mickael Istria
> Priority: Minor
> Fix For: 4.4.0.Alpha1
>
>
> When publishing, we use this:
> {code}
> [jbosstools-build-sites.aggregate.site_4.3.mars] $ /qa/tools/opt/apache-maven-3.2.5/bin/mvn -DTARGET_PLATFORM_VERSION=4.50.0.Final
> -DTARGET_PLATFORM_VERSION_MAXIMUM=4.51.0.Final "-DMAVEN_FLAGS=-B -U -fae -e -P hudson,unified.target,pack200"
> -DskipRevisionCheckWhenPublishing=true "-Dupdate.site.description=Stable Release" -Djbosstools_site_stream=4.3.mars -DtrimVersion=true
> -Dmdep.stripClassifier=true -Dartifact=org.jboss.tools.releng:jbosstools-releng-publish:4.3.0.Final:zip
> -DoutputDirectory=/mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_4.3.mars/sources
> -Dmdep.stripVersion=true org.apache.maven.plugins:maven-dependency-plugin:2.9:unpack
> {code}
> But there's also this:
> {code}
> [INFO] Configured Artifact: org.jboss.tools.releng:jbosstools-releng-publish:4.3.0.Final:tar.gz
> [INFO] Downloading: https://repository.jboss.org/nexus/content/repositories/deprecated/org/jb...
> [INFO] Downloading: https://repository.jboss.org/nexus/content/groups/developer/org/jboss/too...
> [INFO] Downloaded: https://repository.jboss.org/nexus/content/groups/developer/org/jboss/too... (25 KB at 99.3 KB/sec)
> [INFO] Unpacking /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_4.3.mars/.repository/org/jboss/tools/releng/jbosstools-releng-publish/4.3.0.Final/jbosstools-releng-publish-4.3.0.Final.tar.gz to /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_4.3.mars/sources/aggregate/site/target/releng-scripts with includes "" and excludes ""
> [INFO] Expanding: /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_4.3.mars/.repository/org/jboss/tools/releng/jbosstools-releng-publish/4.3.0.Final/jbosstools-releng-publish-4.3.0.Final.tar.gz into /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_4.3.mars/sources/aggregate/site/target/releng-scripts{code}
> So... should we update jobs to fetch and use the .tar.gz because it retains exec perms? Then we can update the assembly.xml to only create the .tar.gz and stop wasting disk space w/ the extra zip.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-20900) why do we need both zip and tar.gz for org.jboss.tools.releng:jbosstools-releng-publish ?
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20900?page=com.atlassian.jira.plugi... ]
Nick Boldt reassigned JBIDE-20900:
----------------------------------
Assignee: Nick Boldt (was: Mickael Istria)
> why do we need both zip and tar.gz for org.jboss.tools.releng:jbosstools-releng-publish ?
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-20900
> URL: https://issues.jboss.org/browse/JBIDE-20900
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.3.0.Final, 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Minor
> Fix For: 4.4.0.Alpha1
>
>
> When publishing, we use this:
> {code}
> [jbosstools-build-sites.aggregate.site_4.3.mars] $ /qa/tools/opt/apache-maven-3.2.5/bin/mvn -DTARGET_PLATFORM_VERSION=4.50.0.Final
> -DTARGET_PLATFORM_VERSION_MAXIMUM=4.51.0.Final "-DMAVEN_FLAGS=-B -U -fae -e -P hudson,unified.target,pack200"
> -DskipRevisionCheckWhenPublishing=true "-Dupdate.site.description=Stable Release" -Djbosstools_site_stream=4.3.mars -DtrimVersion=true
> -Dmdep.stripClassifier=true -Dartifact=org.jboss.tools.releng:jbosstools-releng-publish:4.3.0.Final:zip
> -DoutputDirectory=/mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_4.3.mars/sources
> -Dmdep.stripVersion=true org.apache.maven.plugins:maven-dependency-plugin:2.9:unpack
> {code}
> But there's also this:
> {code}
> [INFO] Configured Artifact: org.jboss.tools.releng:jbosstools-releng-publish:4.3.0.Final:tar.gz
> [INFO] Downloading: https://repository.jboss.org/nexus/content/repositories/deprecated/org/jb...
> [INFO] Downloading: https://repository.jboss.org/nexus/content/groups/developer/org/jboss/too...
> [INFO] Downloaded: https://repository.jboss.org/nexus/content/groups/developer/org/jboss/too... (25 KB at 99.3 KB/sec)
> [INFO] Unpacking /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_4.3.mars/.repository/org/jboss/tools/releng/jbosstools-releng-publish/4.3.0.Final/jbosstools-releng-publish-4.3.0.Final.tar.gz to /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_4.3.mars/sources/aggregate/site/target/releng-scripts with includes "" and excludes ""
> [INFO] Expanding: /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_4.3.mars/.repository/org/jboss/tools/releng/jbosstools-releng-publish/4.3.0.Final/jbosstools-releng-publish-4.3.0.Final.tar.gz into /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_4.3.mars/sources/aggregate/site/target/releng-scripts{code}
> So... should we update jobs to fetch and use the .tar.gz because it retains exec perms? Then we can update the assembly.xml to only create the .tar.gz and stop wasting disk space w/ the extra zip.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21105) Remove BIRT?
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21105?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-21105 at 11/23/15 9:35 AM:
--------------------------------------------------------------
[~maxandersen]: Yes, it's alive. As Snejana told me, and as I posted above, 6 days ago:
* https://issues.jboss.org/browse/JBIDE-21105?focusedCommentId=13129743&pag...
* https://issues.jboss.org/browse/JBIDE-21105?focusedCommentId=13129900&pag...
[~kmarmaliykov]: Yes, I provided the list of jetty plugins above, 3 days ago:
{code}
$➔ ls -la $(find . -maxdepth 2 -name "*jetty*" | sort) | grep "Nov 20"
-rw-rw-r-- 1 nboldt nboldt 90052 Nov 20 12:59 ./plugins/org.eclipse.jetty.annotations_9.3.5.v20151012.jar
-rw-rw-r-- 1 nboldt nboldt 59640 Nov 20 12:59 ./plugins/org.eclipse.jetty.deploy_9.3.5.v20151012.jar
-rw-rw-r-- 1 nboldt nboldt 48831 Nov 20 12:59 ./plugins/org.eclipse.jetty.jndi_9.3.5.v20151012.jar
-rw-rw-r-- 1 nboldt nboldt 126131 Nov 20 12:59 ./plugins/org.eclipse.jetty.osgi.boot_9.3.5.v20151012.jar
-rw-rw-r-- 1 nboldt nboldt 61762 Nov 20 12:59 ./plugins/org.eclipse.jetty.plus_9.3.5.v20151012.jar
-rw-rw-r-- 1 nboldt nboldt 118707 Nov 20 12:59 ./plugins/org.eclipse.jetty.webapp_9.3.5.v20151012.jar
-rw-rw-r-- 1 nboldt nboldt 57922 Nov 20 12:59 ./plugins/org.eclipse.jetty.xml_9.3.5.v20151012.jar
{code}
These have already been added to the latest Neon TP [0]:
[0] http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.6...
Are you suggesting that we should help them add more Jetty plugins to their update site [1] ?
[1] http://download.eclipse.org/birt/update-site/mars-interim/
If so, here's the list of missing ones, which 9.3.5 requires (9.2.9 does NOT require them):
{code}org.eclipse.jetty.annotations_9.3.5.v20151012.jar
org.eclipse.jetty.jndi_9.3.5.v20151012.jar
org.eclipse.jetty.plus_9.3.5.v20151012.jar{code}
was (Author: nickboldt):
[~maxandersen]: Yes, it's alive. As Snejana told me, and as I posted above, 5 days ago:
* https://issues.jboss.org/browse/JBIDE-21105?focusedCommentId=13129743&pag...
* https://issues.jboss.org/browse/JBIDE-21105?focusedCommentId=13129900&pag...
[~kmarmaliykov]: Yes, I provided the list of jetty plugins above, 2 days ago:
{code}
$➔ ls -la $(find . -maxdepth 2 -name "*jetty*" | sort) | grep "Nov 20"
-rw-rw-r-- 1 nboldt nboldt 90052 Nov 20 12:59 ./plugins/org.eclipse.jetty.annotations_9.3.5.v20151012.jar
-rw-rw-r-- 1 nboldt nboldt 59640 Nov 20 12:59 ./plugins/org.eclipse.jetty.deploy_9.3.5.v20151012.jar
-rw-rw-r-- 1 nboldt nboldt 48831 Nov 20 12:59 ./plugins/org.eclipse.jetty.jndi_9.3.5.v20151012.jar
-rw-rw-r-- 1 nboldt nboldt 126131 Nov 20 12:59 ./plugins/org.eclipse.jetty.osgi.boot_9.3.5.v20151012.jar
-rw-rw-r-- 1 nboldt nboldt 61762 Nov 20 12:59 ./plugins/org.eclipse.jetty.plus_9.3.5.v20151012.jar
-rw-rw-r-- 1 nboldt nboldt 118707 Nov 20 12:59 ./plugins/org.eclipse.jetty.webapp_9.3.5.v20151012.jar
-rw-rw-r-- 1 nboldt nboldt 57922 Nov 20 12:59 ./plugins/org.eclipse.jetty.xml_9.3.5.v20151012.jar
{code}
These have already been added to the latest Neon TP [0]:
[0] http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.6...
Are you suggesting that we should help them add more Jetty plugins to their update site [1] ?
[1] http://download.eclipse.org/birt/update-site/mars-interim/
If so, here's the list of missing ones, which 9.3.5 requires (9.2.9 does NOT require them):
{code}org.eclipse.jetty.annotations_9.3.5.v20151012.jar
org.eclipse.jetty.jndi_9.3.5.v20151012.jar
org.eclipse.jetty.plus_9.3.5.v20151012.jar{code}
> Remove BIRT?
> ------------
>
> Key: JBIDE-21105
> URL: https://issues.jboss.org/browse/JBIDE-21105
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: birt, target-platform
> Affects Versions: 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.4.0.Alpha1
>
> Attachments: birt-4.5-vs-mars-interim.txt, birt-4.5-vs-mars-interim_summary.txt, birt-depends-on-jetty-deploy-929.png, birt-depends-on-jetty-osgi-boot-929.png, birt-wizard-new-library.png, birt-wizard-new-library__NEON.png, birt-wizards.png, birt-wizards__NEON.png, eclipse-after-birt.png, install-jboss-birt-sites.png, install-jboss-birt-sites__NEON.png, install-jboss-birt.png, install-jboss-birt__NEON.png
>
>
> {quote}
> (2015-11-17 11:42:50) kmarmaliykov: nickboldt: I look into neon M3 and see that there is no jetty 9.2.9 there
> (2015-11-17 11:43:18) nickboldt: kmarmaliykov: yes, 9.2.9 is from Birt site
> (2015-11-17 11:43:21) nickboldt: because Birt needs it
> (2015-11-17 11:43:33) nickboldt: but there's no Birt for Neon yet so we have to include the Birt for Mars
> (2015-11-17 11:43:37) maxandersen: nickboldt: akazakov: are you talking about having birt in Neon ?
> (2015-11-17 11:43:44) maxandersen: afaik birt is dead.
> (2015-11-17 11:43:53) maxandersen: won't participate in neon release afaik.
> (2015-11-17 11:43:56) nickboldt: maxandersen: so we should remove birt from JBT 4.4?
> (2015-11-17 11:44:24) maxandersen: well, check first if birt is actually in neon. if it is not the decision is very easy.
> (2015-11-17 11:44:38) akazakov: +1
> (2015-11-17 11:45:36) maxandersen: if it is in, then lets talk options. but if birt requires us to jump through too many hoops its not worth keeping it in.
> (2015-11-17 11:45:55) nickboldt: birt 4.5.0.v201506092134 is in Neon from 201511131000 (M3) - http://download.eclipse.org/releases/neon/201511131000/
> (2015-11-17 11:47:08) nickboldt: and there's a newer birt 4.5.0.v201510231925 (same major.minor.service, newer datestamp) in http://download.eclipse.org/birt/update-site/mars-interim/
> {quote}
> So, yesterday as part of updates for JBIDE-20976, I pulled a new BIRT mirror here:
> http://download.jboss.org/jbosstools/updates/requirements/birt/4.5.0.v201...
> But we could also just use the old one from Mars.0:
> http://download.jboss.org/jbosstools/updates/requirements/birt/4.5.0.v201...
> Or we could remove support for BIRT and its webtools / charting integration entirely from JBT 4.4.0.Alpha1, since as Max says BIRT is at EOL.
> *DISCUSS*.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21105) Remove BIRT?
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21105?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-21105:
------------------------------------
[~maxandersen]: Yes, it's alive. As Snejana told me, and as I posted above, 5 days ago:
* https://issues.jboss.org/browse/JBIDE-21105?focusedCommentId=13129743&pag...
* https://issues.jboss.org/browse/JBIDE-21105?focusedCommentId=13129900&pag...
[~kmarmaliykov]: Yes, I provided the list of jetty plugins above, 2 days ago:
{code}
$➔ ls -la $(find . -maxdepth 2 -name "*jetty*" | sort) | grep "Nov 20"
-rw-rw-r-- 1 nboldt nboldt 90052 Nov 20 12:59 ./plugins/org.eclipse.jetty.annotations_9.3.5.v20151012.jar
-rw-rw-r-- 1 nboldt nboldt 59640 Nov 20 12:59 ./plugins/org.eclipse.jetty.deploy_9.3.5.v20151012.jar
-rw-rw-r-- 1 nboldt nboldt 48831 Nov 20 12:59 ./plugins/org.eclipse.jetty.jndi_9.3.5.v20151012.jar
-rw-rw-r-- 1 nboldt nboldt 126131 Nov 20 12:59 ./plugins/org.eclipse.jetty.osgi.boot_9.3.5.v20151012.jar
-rw-rw-r-- 1 nboldt nboldt 61762 Nov 20 12:59 ./plugins/org.eclipse.jetty.plus_9.3.5.v20151012.jar
-rw-rw-r-- 1 nboldt nboldt 118707 Nov 20 12:59 ./plugins/org.eclipse.jetty.webapp_9.3.5.v20151012.jar
-rw-rw-r-- 1 nboldt nboldt 57922 Nov 20 12:59 ./plugins/org.eclipse.jetty.xml_9.3.5.v20151012.jar
{code}
These have already been added to the latest Neon TP [0]:
[0] http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.6...
Are you suggesting that we should help them add more Jetty plugins to their update site [1] ?
[1] http://download.eclipse.org/birt/update-site/mars-interim/
If so, here's the list of missing ones, which 9.3.5 requires (9.2.9 does NOT require them):
{code}org.eclipse.jetty.annotations_9.3.5.v20151012.jar
org.eclipse.jetty.jndi_9.3.5.v20151012.jar
org.eclipse.jetty.plus_9.3.5.v20151012.jar{code}
> Remove BIRT?
> ------------
>
> Key: JBIDE-21105
> URL: https://issues.jboss.org/browse/JBIDE-21105
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: birt, target-platform
> Affects Versions: 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.4.0.Alpha1
>
> Attachments: birt-4.5-vs-mars-interim.txt, birt-4.5-vs-mars-interim_summary.txt, birt-depends-on-jetty-deploy-929.png, birt-depends-on-jetty-osgi-boot-929.png, birt-wizard-new-library.png, birt-wizard-new-library__NEON.png, birt-wizards.png, birt-wizards__NEON.png, eclipse-after-birt.png, install-jboss-birt-sites.png, install-jboss-birt-sites__NEON.png, install-jboss-birt.png, install-jboss-birt__NEON.png
>
>
> {quote}
> (2015-11-17 11:42:50) kmarmaliykov: nickboldt: I look into neon M3 and see that there is no jetty 9.2.9 there
> (2015-11-17 11:43:18) nickboldt: kmarmaliykov: yes, 9.2.9 is from Birt site
> (2015-11-17 11:43:21) nickboldt: because Birt needs it
> (2015-11-17 11:43:33) nickboldt: but there's no Birt for Neon yet so we have to include the Birt for Mars
> (2015-11-17 11:43:37) maxandersen: nickboldt: akazakov: are you talking about having birt in Neon ?
> (2015-11-17 11:43:44) maxandersen: afaik birt is dead.
> (2015-11-17 11:43:53) maxandersen: won't participate in neon release afaik.
> (2015-11-17 11:43:56) nickboldt: maxandersen: so we should remove birt from JBT 4.4?
> (2015-11-17 11:44:24) maxandersen: well, check first if birt is actually in neon. if it is not the decision is very easy.
> (2015-11-17 11:44:38) akazakov: +1
> (2015-11-17 11:45:36) maxandersen: if it is in, then lets talk options. but if birt requires us to jump through too many hoops its not worth keeping it in.
> (2015-11-17 11:45:55) nickboldt: birt 4.5.0.v201506092134 is in Neon from 201511131000 (M3) - http://download.eclipse.org/releases/neon/201511131000/
> (2015-11-17 11:47:08) nickboldt: and there's a newer birt 4.5.0.v201510231925 (same major.minor.service, newer datestamp) in http://download.eclipse.org/birt/update-site/mars-interim/
> {quote}
> So, yesterday as part of updates for JBIDE-20976, I pulled a new BIRT mirror here:
> http://download.jboss.org/jbosstools/updates/requirements/birt/4.5.0.v201...
> But we could also just use the old one from Mars.0:
> http://download.jboss.org/jbosstools/updates/requirements/birt/4.5.0.v201...
> Or we could remove support for BIRT and its webtools / charting integration entirely from JBT 4.4.0.Alpha1, since as Max says BIRT is at EOL.
> *DISCUSS*.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21121) Port Forwarding: Warning/error dialog should pop up if there is no oc binary when opening Port forwarding dialog
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21121?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-21121:
-------------------------------------
[~mlabuda] a missing oc binary warning is supposed to pop up when you open the port forwarding menu from openshift explorer. What are your steps to reproduce the problem?
> Port Forwarding: Warning/error dialog should pop up if there is no oc binary when opening Port forwarding dialog
> ----------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21121
> URL: https://issues.jboss.org/browse/JBIDE-21121
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Marián Labuda
> Priority: Minor
> Labels: openshift_v3, port_forwarding_wizard
> Fix For: 4.4.0.Alpha1
>
>
> OpenShift 3 port forwarding features requires 'oc' binary to be set up in tooling. It's done in Workbench preference dialog on page OpenShift 3. If there is no 'oc' binary set and user invokes a port forwarding dialog, it is opened and even Start All button is enabled. User finds out that it is not possible to perform only when he gets an error message upon clicking on Start All button describing the problem. There could be some warning/error dialog popped up before opening a port forwarding dialog if there is no 'oc' location set in preferences.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-20916) importing jbosstools-website results in error
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20916?page=com.atlassian.jira.plugi... ]
Mickael Istria resolved JBIDE-20916.
------------------------------------
Fix Version/s: 4.3.1.Beta1
Resolution: Cannot Reproduce
I didn't manage to reproduce this issue. It seems like that state of your jbosstools-website was inconsistent, and showing this error was actually quite meaningful
> importing jbosstools-website results in error
> ---------------------------------------------
>
> Key: JBIDE-20916
> URL: https://issues.jboss.org/browse/JBIDE-20916
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: easymport
> Reporter: Max Rydahl Andersen
> Assignee: Mickael Istria
> Priority: Minor
> Fix For: 4.3.1.Beta1, 4.4.0.Alpha1
>
>
> use import nested of jbosstools-website result in progress dialog showing error saying:
> {quote}
> bin | Could not import project located at /Users/max/code/jbosstools/jbosstools-website/bin
> {quote}
> No additional info provided.
> (note: this happened on second import so it might be when .project already there)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months