Alternative of using of snaps with Virgo 3.7.0.M3 [message #1744538] |
Tue, 27 September 2016 19:17  |
Eclipse User |
|
|
|
I would like to know how can I replace the snaps that are not support by version 3.7.0M3.
Currently I have a modular web application that uses Snaps in their architecture, but during the upgrade of virgo I notice that snaps are not supported anymore.
Dependencies such as org.eclipse.virgo.snaps.api-3.6.4.RELEASE.jar and org.eclipse.virgo.snaps.core-3.6.4.RELEASE.jar are not available, how can I deal with filters like org.eclipse.virgo.snaps.core.SnapHostFilter and references into template.mf like org.eclipse.virgo.snaps.core
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Re: Alternative of using of snaps with Virgo 3.7.0.M3 [message #1748679 is a reply to message #1748529] |
Sat, 26 November 2016 10:58  |
Eclipse User |
|
|
|
Junior Sousa wrote on Thu, 24 November 2016 03:32I checkout the code to branch origin/gradle-build and build project over packaging project and the whole project was build with success.
What do you mean, "over packaging project", you should run the scripts from root of the repo. Pls see my previous reply on how-to build Virgo.
Junior Sousa wrote on Thu, 24 November 2016 03:32
Now, I would like to understand the project bases and their dependencies, such as spring. How you store and build the spring into http://build.eclipse.org/rt/virgo/ivy/bundles/release/org.eclipse.virgo.mirrored/ repository and how the manifest.mf of these dependencies is built?
Well, the 3rd party dependencies hosted in "build.eclipse.org/.../mirrored" are built and pushed there manually from us.
For detailed understanding of the project you will need to have a look at the project itself, it is simply not possible for me to explain all the details here. So please com back with specific questions if you have any.
Regards,
Dani
|
|
|
Powered by
FUDForum. Page generated in 0.06029 seconds