[
https://issues.apache.org/jira/browse/EMPIREDB-376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
PJ Fanning updated EMPIREDB-376:
--------------------------------
Description:
[https://github.com/apache/empire-db/pull/10] has been open for 2 years - it's
possible that the issue has been fixed already and that the pull request can be
closed (at least for master)
The issue still appears to affect
[https://github.com/apache/empire-db/blob/version2-legacy/empire-db-eclipse-codegen/pom.xml]
- and version2-legacy still still seems to be used for build - see
https://lists.apache.org/thread/3fh7djnh62o24xzvbhcqwbnsc5nd8mkx
was:
[https://github.com/apache/empire-db/pull/10] has been open for 2 years - it's
possible that the issue has been fixed already and that the pull request can be
closed (at least for master)
The issue still appears to affect
[https://github.com/apache/empire-db/blob/version2-legacy/empire-db-eclipse-codegen/pom.xml]
- is version2-legacy still supported?
> do not use insecure http endpoints when doing maven build
> ---------------------------------------------------------
>
> Key: EMPIREDB-376
> URL: https://issues.apache.org/jira/browse/EMPIREDB-376
> Project: Empire-DB
> Issue Type: Improvement
> Reporter: PJ Fanning
> Priority: Major
>
> [https://github.com/apache/empire-db/pull/10] has been open for 2 years -
> it's possible that the issue has been fixed already and that the pull request
> can be closed (at least for master)
> The issue still appears to affect
> [https://github.com/apache/empire-db/blob/version2-legacy/empire-db-eclipse-codegen/pom.xml]
> - and version2-legacy still still seems to be used for build - see
> https://lists.apache.org/thread/3fh7djnh62o24xzvbhcqwbnsc5nd8mkx
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
