[
https://issues.apache.org/jira/browse/GERONIMO-2742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12474529
]
Aman Nanner commented on GERONIMO-2742:
---------------------------------------
An Eclipse-aware repository is a possibility, although the solution for this
issue doesn't have to be that heavy. If the maven-style layout could be
modified such that a folder with a maven-style name, rather than a JAR, could
be used, then that would solve the problem as I could create a symlink for that
folder.
Example:
In the repository, consider
org/apache/geronimo/modules/geronimo-connector/1.2-beta/geronimo-connector-1.2-beta.jar.
The "geronimo-connector-1.2-beta.jar" could be a folder name instead of a JAR
archive, and the classes would be in exploded format within this folder. Then
"geronimo-connector-1.2-beta.jar" could be made into a symlink that points to a
folder within the Eclipse workspace.
I'm not sure how doable this is, since I don't know if you use a third-party
library (Maven?) for repository classloading. But this is along the lines of
what I was thinking.
> Deployer cannot access libaries in shared/lib and shared/classes
> ----------------------------------------------------------------
>
> Key: GERONIMO-2742
> URL: https://issues.apache.org/jira/browse/GERONIMO-2742
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: deployment
> Affects Versions: 1.2
> Environment: Windows XP, Geronimo 1.2-beta
> Reporter: Aman Nanner
> Attachments: sharedlib-2.0.zip, sharedlib.zip, testing.ear.zip
>
>
> It seems that when running the deployer to deploy my EAR file, the
> classloaders during deployment cannot access the shared/lib and
> shared/classes directory. My app has dependencies on libraries that are
> stored in both shared/classes and shared/lib. Because these libraries cannot
> be found, the deployment fails.
> Neither regular deployment nor hot deployment works. My EAR file used to hot
> deploy properly in Geronimo 1.1.1 (I never used the regular deployer in
> 1.1.1, so I don't know if that would have worked too).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
