Hello Kanchana,
thanks for the links. But aren't they handling wirh Geronimo 1.0?
I found out, that in Geronimo 1.1 are a little different Deployment
Descriptors. Is there a more deeply description of the tags used in the
Desciptors? If there is an overview for all the tags used in the XML's lik
Hi MikaHave a close look in http://cwiki.apache.org/GMOxDOC10/migrating-to-apache-geronimo.html and
http://cwiki.apache.org/GMOxDOC10/jboss-to-geronimo-jca-migration.html will give you better understandingRegardsKanchanaOn 7/25/06, mika
<[EMAIL PROTECTED]> wrote:
Hello,through reading some other
Hi Using the upgrade.jar I generated a following deployment plan for geronimov1.1.To gernerate the below I used an older version of geronimo-application.xml which was written for the
geronimov1.0.I'm Not sure whether it has generated the plan correctly because the "configId " property which is no
Jacob, that jar file should have been copied to your local maven repo
in an earlier stage of the build. Try typing "maven -o" in the
modules/installer-support directory and you should see this in the
output:
[echo] Copying standalone-compiler-custom-3.8.0 to local repo
If that fails for some r
Hi,
I believe to be following the wiki on building geronimo but I am running
into this problem on both the 1.1 branch and the trunk, build snippet
follows:
+
| geronimo and geronimo-plugins Geronimo :: IZPack Installer Build Plugin
| Memory: 22M/32M
+--
Sachin, thanks this is very helpful!
I started with a clean maven repo, redid a full build and followed your steps
in FAQ. I am not seeing any errors now in my eclipse.
Lin
From: Sachin Patel
[mailto:[EMAIL PROTECTED] On Behalf Of Sachin
Patel
Sent: Tuesday, July 25, 2006
Lin,There is nothing special that needs to be done. All you need to do is checkout the source, do a full build. Then launch a clean workspace, set your target platform, and then import the projects. At which point you should have no errors.On Jul 25, 2006, at 11:52 AM, Lin Sun wrote:Sachin,I fou
Sachin,
I found out most of the problems came from the Export-Package of different
plugins' manifest file. For example, in the
org.apache.geronimo.common.deployment.model.edit plugin, I had:
Export-Package: org.apache.geronimo.common.deployment.model.edit,
org.apache.geronimo.xml.ns.security.pr
Hello,
through reading some other threads I came to the conclusion that it maybe is
easier if I say that the EAR mentioned to deploy in Geronimo v1.1 has been
deployed in JBoss 4.0.4 already.
If it helps, which changes have to be made for getting the EAR deployed in
Geronimo ?
I will post the
