[JBoss JIRA] (JBIDE-19645) Remove seam 3 features from JBDS install
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19645?page=com.atlassian.jira.plugi... ]
Alexey Kazakov closed JBIDE-19645.
----------------------------------
Resolution: Done
To be clear. We actually removed Seam3 features from JBDS install. There is no Seam3 connectors in central. The only way it so install Seam3 features in JBDS is to use JBDS update site.
We decided not to remove it but it seems that nobody noticed that we actually removed it and taking into account that Seam3 is dead I would keep it removed.
> Remove seam 3 features from JBDS install
> ----------------------------------------
>
> Key: JBIDE-19645
> URL: https://issues.jboss.org/browse/JBIDE-19645
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi-extensions, central, updatesite
> Affects Versions: 4.3.0.Alpha2
> Reporter: Nick Boldt
> Assignee: Alexey Kazakov
> Fix For: 4.3.1.Beta1
>
> Attachments: jbds8alpha2-features-cdi-seam.png, jbds8alpha2-plugins-cdi.png, jbds8alpha2-plugins-seam.png, jbt43alpha2-features-cdi.png, jbt43alpha2-features-seam.png, jbt43alpha2-plugins-cdi.png, jbt43alpha2-plugins-seam-3-and-seam3.png, validation.png
>
>
> Burr has requested we also remove Seam 3. So I've assumed we'll do it the same way we did for Seam 2:
> * remove from CoreTools categories on update sites
> * remove from JBDS core.feature
> * create new connectors in JBT and JBDS Central
> [~burrsutter] [~maxandersen] please confirm this is the path you want taken for all the renaming features with "seam" in their name.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-19645) Remove seam 3 features from JBDS install
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19645?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-19645:
-----------------------------------
Summary: Remove seam 3 features from JBDS install (was: Remove seam 3 features from JBDS, JBT default install; add new connector to Central)
> Remove seam 3 features from JBDS install
> ----------------------------------------
>
> Key: JBIDE-19645
> URL: https://issues.jboss.org/browse/JBIDE-19645
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi-extensions, central, updatesite
> Affects Versions: 4.3.0.Alpha2
> Reporter: Nick Boldt
> Assignee: Alexey Kazakov
> Fix For: 4.3.1.Beta1
>
> Attachments: jbds8alpha2-features-cdi-seam.png, jbds8alpha2-plugins-cdi.png, jbds8alpha2-plugins-seam.png, jbt43alpha2-features-cdi.png, jbt43alpha2-features-seam.png, jbt43alpha2-plugins-cdi.png, jbt43alpha2-plugins-seam-3-and-seam3.png, validation.png
>
>
> Burr has requested we also remove Seam 3. So I've assumed we'll do it the same way we did for Seam 2:
> * remove from CoreTools categories on update sites
> * remove from JBDS core.feature
> * create new connectors in JBT and JBDS Central
> [~burrsutter] [~maxandersen] please confirm this is the path you want taken for all the renaming features with "seam" in their name.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBDS-3562) Prepare for 9.0.1 / 9.1.0
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3562?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-3562:
----------------------------------
"eclipse plugins aren't known to be vulnerable"
and
"Eclipse.org plugins need released too."
Seem to state opposite things. Why would Eclipse.org plugins need [to be] released too if they're not vulnerable?
Related: jpa & m2e both have open bugzillas/JIRAs about this problem, so I'm going to assume your second statement was the correct one.
I would also bet that just because the jpa feature requires apache.commons.collections 3.2.0, we will likely be able to install 3.2.2 on top too, possibly even replacing / deactivating the older version.
> Prepare for 9.0.1 / 9.1.0
> --------------------------
>
> Key: JBDS-3562
> URL: https://issues.jboss.org/browse/JBDS-3562
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: build
> Affects Versions: 9.0.1.GA
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 9.0.1.GA
>
>
> Tracker JIRA to house things to do to prepare for 9.0.1 / 9.1.0 branches & builds.
> Because JBDS 9.0.0 includes the compromised version of
> apache.commons.collections (JBDS-3560, JBDS-3561), we need to at some point respin it, which
> will include:
> a) updated JBT/JBDS target platforms 4.50.1.* and 4.51.1.*
> b) repin of JBDS update sites and installer jars
> To that end, I've created the following new branches:
> https://github.com/jbosstools/jbosstools-target-platforms/commits/4.50.1.x
> https://github.com/jbosstools/jbosstools-target-platforms/commits/4.51.1.x
> And I've bumped the version of the target platforms in the 4.50.x and
> 4.51.x branches to 4.50.2.Beta1-SNAPSHOT and 4.51.2.Beta1-SNAPSHOT,
> respectively.
> JBDS is now at version 9.1.0 in the 4.3.x branch and 9.0.1 in the
> 4.3.1.x branch.
> https://github.com/jbdevstudio/jbdevstudio-product/commits/jbosstools-4.3...
> (new, 9.0.1)
> https://github.com/jbdevstudio/jbdevstudio-product/commits/jbosstools-4.3.x
> (updated to 9.1.0)
> So, now we just need to ensure that the correct BUILD_ALIAS (CR1 for
> 9.0.1, Beta1 for 9.1.0) and target platforms are used.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21105) Deprecate BIRT
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21105?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-21105:
-----------------------------------
Description:
{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*.
*Alexey Kazakov:* I changed the title from "Remove Birt?" to "Deprecate Birt" as we agreed to deprecate/sunset it for JBDS 10 / JBT 4.4 / Neon.
was:
{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*.
> Deprecate 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*.
> *Alexey Kazakov:* I changed the title from "Remove Birt?" to "Deprecate Birt" as we agreed to deprecate/sunset it for JBDS 10 / JBT 4.4 / Neon.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-19645) Remove seam 3 features from JBDS, JBT default install; add new connector to Central
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19645?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-19645:
------------------------------------
Should anyone be looking for it, the cdi.seam.feature (Seam 3 Tools) is available:
* in JBDS 9 from Help > Install new > https://devstudio.redhat.com/9.0/stable/updates/ and
* in JBT 4.3 from Help > Install new > http://download.jboss.org/jbosstools/mars/stable/updates/
> Remove seam 3 features from JBDS, JBT default install; add new connector to Central
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-19645
> URL: https://issues.jboss.org/browse/JBIDE-19645
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi-extensions, central, updatesite
> Affects Versions: 4.3.0.Alpha2
> Reporter: Nick Boldt
> Assignee: Alexey Kazakov
> Fix For: 4.3.1.Beta1
>
> Attachments: jbds8alpha2-features-cdi-seam.png, jbds8alpha2-plugins-cdi.png, jbds8alpha2-plugins-seam.png, jbt43alpha2-features-cdi.png, jbt43alpha2-features-seam.png, jbt43alpha2-plugins-cdi.png, jbt43alpha2-plugins-seam-3-and-seam3.png, validation.png
>
>
> Burr has requested we also remove Seam 3. So I've assumed we'll do it the same way we did for Seam 2:
> * remove from CoreTools categories on update sites
> * remove from JBDS core.feature
> * create new connectors in JBT and JBDS Central
> [~burrsutter] [~maxandersen] please confirm this is the path you want taken for all the renaming features with "seam" in their name.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21105) Deprecate BIRT
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21105?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-21105:
-----------------------------------
Summary: Deprecate BIRT (was: Remove BIRT?)
> Deprecate 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-21012) Why do we deploy JBT components to Nexus snapshots repo?
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21012?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-21012:
------------------------------------
No, there was nothing in here which found an issue about bad versioning, only problems with Nexus supporting the idea of versioning things like 1.5.1.Beta1-SNAPSHOT. Workaround was to use 1.5.151-SNAPSHOT.
Conclusions were:
* To support pushing update site zips to Nexus, we need to replace alphabetic BUILD_ALIAS = Beta1 with numeric BUILD_ALIAS_NUM = 51. (More examples/details above - https://issues.jboss.org/browse/JBIDE-21012?focusedCommentId=13125499&pag... )
* BUT, to support composite sites containing the Nth and N-1th builds of a given component, we can not use Nexus since it only supports a "latest" or Nth build in /unzip/unzip/ URLs. This means downstream builds will fail should an upstream component republish DURING that downstream component's build. These failures are not "CI builds fail faster" but rather "nuissance failures", since a simple respin would fix them.
---
Re: features that detect bad versioning, we have two:
a) compare with baselines - JBIDE-21052
b) versionwatch - JBIDE-20976
> Why do we deploy JBT components to Nexus snapshots repo?
> --------------------------------------------------------
>
> Key: JBIDE-21012
> URL: https://issues.jboss.org/browse/JBIDE-21012
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, updatesite
> Affects Versions: 4.3.0.Final, 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.3.1.Beta1, 4.4.0.Alpha1
>
>
> Currently, we deploy our x.y.z-SNAPSHOT update sites to the JBoss Nexus snapshots repo.
> But other than Locus and the Browsersim Standalone zip, we don't ever use these artifacts, so they just:
> * eat disk space in Nexus
> * consume time/resources in Jenkins
> Since we have the custom profile deploy-to-jboss.org in place for all our artifacts, why don't we set *maven.deploy.skip=true* in the parent pom for all the projects (except of course Locus and Browsersim Standalone, which would use maven.deploy.skip=false) ?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-19645) Remove seam 3 features from JBDS, JBT default install; add new connector to Central
by Rastislav Wagner (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19645?page=com.atlassian.jira.plugi... ]
Rastislav Wagner closed JBIDE-19645.
------------------------------------
Resolution: Done
Closing again, nobody is missing seam3 in default install so it will stay as it is
> Remove seam 3 features from JBDS, JBT default install; add new connector to Central
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-19645
> URL: https://issues.jboss.org/browse/JBIDE-19645
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi-extensions, central, updatesite
> Affects Versions: 4.3.0.Alpha2
> Reporter: Nick Boldt
> Assignee: Alexey Kazakov
> Fix For: 4.3.1.Beta1
>
> Attachments: jbds8alpha2-features-cdi-seam.png, jbds8alpha2-plugins-cdi.png, jbds8alpha2-plugins-seam.png, jbt43alpha2-features-cdi.png, jbt43alpha2-features-seam.png, jbt43alpha2-plugins-cdi.png, jbt43alpha2-plugins-seam-3-and-seam3.png, validation.png
>
>
> Burr has requested we also remove Seam 3. So I've assumed we'll do it the same way we did for Seam 2:
> * remove from CoreTools categories on update sites
> * remove from JBDS core.feature
> * create new connectors in JBT and JBDS Central
> [~burrsutter] [~maxandersen] please confirm this is the path you want taken for all the renaming features with "seam" in their name.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months