# Accessing java API within an own module from perspectives **URL:** \ **Category:** Module Development\ **Tags:** perspective, scripting, ignition81\ **Created:** [July 11, 2024, 8:32am UTC](https://forum.inductiveautomation.com/t/accessing-java-api-within-an-own-module-from-perspectives/93064 "2024-07-11T08:32:14Z")\ **Posts on this page:** 1\ **Showing post:** 8
**Author:** ![Christoph\_Schauer](https://avatars.discourse-cdn.com/v4/letter/c/22d042/32.png) [@Christoph\_Schauer](https://forum.inductiveautomation.com/u/Christoph_Schauer)\ **Post date:** [July 15, 2024, 2:31pm UTC](https://forum.inductiveautomation.com/t/accessing-java-api-within-an-own-module-from-perspectives/93064/8 "2024-07-15T14:31:52Z")
I found the issue. You are right, the transitive dependencies are bundled. I forgot about to change the version of the **ignition-maven-plugin** to version **1.2.0** after creating it with the archetype. I just checked, because I would update the version and create a PR. But there is already one: [Upgraded Archetype Dependency Versions by cmwarre · Pull Request #7 · inductiveautomation/ignition-sdk-archetypes · GitHub](https://github.com/inductiveautomation/ignition-sdk-archetypes/pull/7) Thanks a lot for testing it. --- _[View the full topic](https://forum.inductiveautomation.com/t/accessing-java-api-within-an-own-module-from-perspectives/93064)._