midsuit
/
core-jgi
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
core-jgi/org.compiere.db.oracle.prov.../META-INF/MANIFEST.MF

21 lines
818 B
Plaintext
Raw Normal View History

Refactoring to make project and folder name the same as the bundle symbolic name. Migrate to use eclipse feature and product configuration ( build is broken, to fix later )
2010-09-29 14:25:34 +07:00
Manifest-Version: 1.0
Bundle-ManifestVersion: 2
IDEMPIERE-2245 Platform Upgrade for r3.
2014-10-13 10:05:19 +07:00
Bundle-Name: iDempiere Oracle Provider
Refactoring to make project and folder name the same as the bundle symbolic name. Migrate to use eclipse feature and product configuration ( build is broken, to fix later )
2010-09-29 14:25:34 +07:00
Bundle-SymbolicName: org.compiere.db.oracle.provider;singleton:=true
IDEMPIERE-5523 Release 10 Peace (#1624) - move master to release-11 development build
2022-12-24 06:20:49 +07:00
Bundle-Version: 11.0.0.qualifier
IDEMPIERE-5448 2023 June Platform Update (#1531) * IDEMPIERE-5448 Can't launch unit test with Eclipse 2022-09 - upgrade to tycho 3.1.0-SNAPSHOT - set maven compiler source and target level to 11 - upgrade to junit 5.9.1 * IDEMPIERE-5448 Can't launch unit test with Eclipse 2022-09 - Change tycho version to 3.0.3 * IDEMPIERE-5448 2023 June Platform Update * IDEMPIERE-5448 2023 June Platform Update - Explicitly set target, source and release level to JavaSE 11 * IDEMPIERE-5448 2023 June Platform Update - Use 3.0.5-SNAPSHOT to fix stack overflow error. * IDEMPIERE-5448 2023 June Platform Update - Change source, target and release level to JDK 17 - Update target platform name to idempiere-230620 * IDEMPIERE-5448 2023 June Platform Update - Fix LogFactory ClassNotFound exception with Eclipse 2023-06
2023-06-21 18:44:18 +07:00
Bundle-RequiredExecutionEnvironment: JavaSE-17
Require-Capability: osgi.ee;filter:="(&(osgi.ee=JavaSE)(version>=17))"
IDEMPIERE-3136:all stuff relate library of idempiere remove version of dependency bundle
2016-07-07 12:51:24 +07:00
Require-Bundle: org.adempiere.base;bundle-version="0.0.0",
IDEMPIERE-4635 Model Generator launch configuration broken (#515) * IDEMPIERE-4635 Model Generator launch configuration broken * IDEMPIERE-4635 Model Generator launch configuration broken fix other launch configuration
2021-01-08 22:56:21 +07:00
org.adempiere.install;bundle-version="0.0.0";resolution:=optional
Refactoring to make project and folder name the same as the bundle symbolic name. Migrate to use eclipse feature and product configuration ( build is broken, to fix later )
2010-09-29 14:25:34 +07:00
Bundle-ClassPath: .,
IDEMPIERE-5013 Implement HikariCP as a replacement for c3p0 (#926) * Replaced PostgreSQL and Oracle connection pools with HikariCP. Replaced C3P0 with HikariCP. HikariCP is a Apache licensed connection pool with substantially better performance and better resilience to failure (DB disconnects, etc.) then C3P0. Read more about it here: https://github.com/brettwooldridge/HikariCP . Cleaned up the `getCachedConnection` method. With HikariCP there is no need to retry to obtain a connection since getting an connection will block until a free connection is available or until a timeout is reached (default 30 seconds) at which point an `SQLException` is thrown. This also removed calling `Runtime.getRuntime().runFinalization();`. HikariCP is currently configured to detect / log leaks when a connection hasn't returned to the pool for longer then 5 minutes. Loading of pool config properties was cleaned up. Defaults are now loaded from a single file instead of defaults coming from both file and hardcoded properties. It is now also possible to specify any HikariCP property in the user pool property file. Initialization of the datasource must happen in the `getDataSource()` method because at object construction not all JDBC config is known. However this method could (as far as I could tell) be called concurrently from multiple threads but had no mechanism to prevent initializing the DB pool multiple times. The variable in which the pool itself was stored (`m_ds`) also was not marked volatile or immutable which could lead to visibility issues. Instead of lazy initialization of the pool in the `getDataSource()` method the pool could probably better be initialized at object construction. However I wasn't able to achieve that without breakage therefor I made the initialization mechanism work correctly with concurrent invocations. Various config options such as the `MaxStatementsPerConnection` options were removed because HikariCP doesn't support them. * (Re)added Sequence time-out.
2022-09-10 17:21:57 +07:00
lib/HikariCP.jar,
Idempiere-4492 update library (eclipse-4.17, jasper 6-15, jetty-9.4.33, atmosphere-2.6.4) (#331) * IDEMPIERE-4492 update jetty to 9.4.33.v20201020 update atmosphere to 2.5.15 * IDEMPIERE-4492 update jetty to 9.4.33.v20201020 (update configuration) update to default jetty configuration delete unused configuration (alpn, http2,..) * IDEMPIERE-4492 update orbit eclipse repository to 4.17 * IDEMPIERE-4492 update orbit eclipse repository to 4.17 (on parent pom) * IDEMPIERE-4492 update jasper to 6.15.0 * IDEMPIERE-4492 update jasper to 6.15.0 (IDEMPIERE-4504) get rid of bundle "org.w3c.dom.events version 3.0.0" by use old version of org.w3c.dom.smil note: on target platform a bundle has multi version then tycho can pickup correct version define on feature (tab included plugins, field version) but on eclipse when sync launching from .product it don't respect that value, always set highest version to bundle workaround: on target platform manual un-select bundle org.w3c.dom.smil 1.0.1 * IDEMPIERE-4492 update atmosphere to 2.6.4 * IDEMPIERE-4492 refine target platform use targetplatform-dsl to generate target platform https://github.com/eclipse-cbi/targetplatform-dsl + don't need to care update bundle version when update repository + at moment org.idempiere.eclipse.platform-feature include some feature form eclipse repository so target has to include that feature so target platform will include all bundler request by feature and bundle request by plugins of that feature and so on (ever optional so it make target content has more plugins than what we use on project next step will convert include feature to include plugins to define only what we used * IDEMPIERE-4492 refine target platform (continue) don't include framework feature, use include plugins to void load transitive dependency so minimize target flatform remove some unused feature from idempiere product * IDEMPIERE-4492 update c3p0 and database jdbc (patch from Carlos)
2020-10-31 05:53:36 +07:00
lib/ojdbc10.jar
IDEMPIERE-4136: Upgrading Jasper report to version 6.11.0
2019-12-25 21:58:37 +07:00
Import-Package: org.osgi.framework,
IDEMPIERE-2892:add config let out put log of c3p0
2015-10-19 19:37:01 +07:00
org.slf4j;version="1.7.2"
Implemented connection pool properties file support. Added convert statement cache for PostgreSQL. Enhance connection pool ability to survive under heavy load.
2010-11-29 10:35:13 +07:00
Bundle-ActivationPolicy: lazy
Bundle-Activator: org.adempiere.db.oracle.OracleBundleActivator
IDEMPIERE-3904 Harmonize list of component in MANIFEST.MF
2019-02-27 18:51:25 +07:00
Service-Component: OSGI-INF/*.xml
IDEMPIERE-3531: add manifest for java 9 warning
2018-09-11 09:04:49 +07:00
Automatic-Module-Name: org.compiere.db.oracle.provider
IDEMPIERE-3798:Move iDempiere default branch to openjdk 10 (add Vendor info to bundle)
2018-10-24 13:07:45 +07:00
Bundle-Vendor: iDempiere Community
IDEMPIERE-4933 Platform update for 9.x (#857) * IDEMPIERE-4933 Platform update for 9.x - WIP * IDEMPIERE-4933 Platform update for 9.x - project to repackaged some osgi bundles from maven * IDEMPIERE-4933 Platform update for 9.x - Fix target platform error * IDEMPIERE-4933 Platform update for 9.x * IDEMPIERE-4933 Platform update for 9.x - minor eclipse setting fix
2021-09-04 21:12:10 +07:00
Export-Package: org.adempiere.db.oracle.config