10:40 a.m.
Hi All,
I've just updated my pom replacing 3.0.0.Alpha3 with 3.0.0.Final and I've
got a couple of errors.
I've fixed the first error just adding
<dependency>
<groupId>joda-time</groupId>
<artifactId>joda-time</artifactId>
<version>1.6.2</version>
</dependency>
is is ok to define seam dependencies manually ? should not that dependency
been part of seam ?
the second error that I'm getting is
org.glassfish.deployment.common.DeploymentException:
java.lang.NoClassDefFoundError: Lorg/jboss/logmanager/Logger$AttachmentKey;
at org.glassfish.weld.WeldDeployer.event(WeldDeployer.java:167)
at org.glassfish.kernel.event.EventsImpl.send(EventsImpl.java:125)
at
org.glassfish.internal.data.ApplicationInfo.load(ApplicationInfo.java:224)
at
com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:338)
at
com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:183)
any ideas ?
(using Glassfish 3.0)
thanks
--
Sebastian E. Ovide
10:58 a.m.
On Thu, Mar 31, 2011 at 11:40, Sebastian E. Ovide <sebastian.ovide(a)gmail.com
wrote:
Hi All,
I've just updated my pom replacing 3.0.0.Alpha3 with 3.0.0.Final and I've
got a couple of errors.
I've fixed the first error just adding
<dependency>
<groupId>joda-time</groupId>
<artifactId>joda-time</artifactId>
<version>1.6.2</version>
</dependency>
is is ok to define seam dependencies manually ? should not that dependency
been part of seam ?
Absolutely you can define dependencies manually. The seam-bom is there to
save you from having to worry about the versions (and for us to communicate
the recommended versions). Joda time is in the seam-bom:
<properties>
...
<joda.time.version>1.6</joda.time.version>
...
</properties>
<dependency>
<groupId>joda-time</groupId>
<artifactId>joda-time</artifactId>
<version>${joda.time.version}</version>
</dependency>
the second error that I'm getting is
org.glassfish.deployment.common.DeploymentException:
java.lang.NoClassDefFoundError: Lorg/jboss/logmanager/Logger$AttachmentKey;
at org.glassfish.weld.WeldDeployer.event(WeldDeployer.java:167)
at org.glassfish.kernel.event.EventsImpl.send(EventsImpl.java:125)
at
org.glassfish.internal.data.ApplicationInfo.load(ApplicationInfo.java:224)
at
com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:338)
at
com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:183)
any ideas ?
(using Glassfish 3.0)
You can't use Seam 3 on GlassFish for reasons explained here
http://seamframework.org/Seam3/Compatibility. GlassFish 3.0 just has too
many compliance issues that are out of our hands. We recommend moving to 3.1
with the latest Weld snapshot. The instructions for updating Weld are on
that page.
-Dan
--
Dan Allen
Principal Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597
http://www.google.com/profiles/dan.j.allen#about
http://mojavelinux.com
http://mojavelinux.com/seaminaction
11:03 a.m.
On Thu, Mar 31, 2011 at 11:58, Dan Allen <dan.j.allen(a)gmail.com> wrote:
On Thu, Mar 31, 2011 at 11:40, Sebastian E. Ovide <
sebastian.ovide(a)gmail.com> wrote:
> Hi All,
>
> I've just updated my pom replacing 3.0.0.Alpha3 with 3.0.0.Final and I've
> got a couple of errors.
>
> I've fixed the first error just adding
>
> <dependency>
> <groupId>joda-time</groupId>
> <artifactId>joda-time</artifactId>
> <version>1.6.2</version>
> </dependency>
>
>
> is is ok to define seam dependencies manually ? should not that dependency
> been part of seam ?
>
Absolutely you can define dependencies manually. The seam-bom is there to
save you from having to worry about the versions (and for us to communicate
the recommended versions). Joda time is in the seam-bom:
<properties>
...
<joda.time.version>1.6</joda.time.version>
...
</properties>
<dependency>
<groupId>joda-time</groupId>
<artifactId>joda-time</artifactId>
<version>${joda.time.version}</version>
</dependency>
Meaning you can put this in your pom.xml:
<dependency>
<groupId>joda-time</groupId>
<artifactId>joda-time</groupId>
</dependency>
Joda time is an optional dependency of Seam International, which is why you
have to specify it.
-Dan
--
Dan Allen
Principal Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597
http://www.google.com/profiles/dan.j.allen#about
http://mojavelinux.com
http://mojavelinux.com/seaminaction
11:04 a.m.
On 03/31/2011 08:40 AM, Sebastian E. Ovide wrote:
Hi All,
I've just updated my pom replacing 3.0.0.Alpha3 with 3.0.0.Final and
I've got a couple of errors.
I've fixed the first error just adding
<dependency>
<groupId>joda-time</groupId>
<artifactId>joda-time</artifactId>
<version>1.6.2</version>
</dependency>
is is ok to define seam dependencies manually ? should not that
dependency been part of seam ?
Seam Faces pulls in the joda time dependency from Seam International.
See SEAMINTL-27 [1] and the Seam Compatibility page [2] for details on
why this dependency is necessary to define when using Glassfish.
And as Dan mentioned, use Glassfish 3.1 over Glassfish 3.0
[1] https://issues.jboss.org/browse/SEAMINTL-27
[2]
http://seamframework.org/Seam3/CompatibilityHome#H-OverzealousClassScanner
11:53 a.m.
Seam Faces pulls in the joda time dependency from Seam International.
See SEAMINTL-27 [1] and the Seam Compatibility page [2] for details on
why this dependency is necessary to define when using Glassfish.
If I remove version from
<dependency>
<groupId>joda-time</groupId>
<artifactId>joda-time</artifactId>
<version>1.6.2</version>
</dependency>
I cannot build.
NetBeans: Executing '/home/sebas/opt/apache-maven-3.0.2/bin/mvn
-Dnetbeans.execution=true clean'
NetBeans: JAVA_HOME=/usr/lib/jvm/default-java
Scanning for projects...
[ERROR]The build could not read 1 project -> [Help 1]
[ERROR]
[ERROR] The project com.mapflow.com:core:0.0.5-SNAPSHOT
(/home/sebas/dev/OneView/CONSOLE/trunk/core/pom.xml) has 1 error
[ERROR] 'dependencies.dependency.version' for joda-time:joda-time:jar is
missing. @ line 149, column 21
[ERROR]
[ERROR]To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR]Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR]For more information about the errors and possible solutions, please
read the following articles:
[ERROR][Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
and if I remove joda dependency and add
<dependency>
<groupId>org.jboss.seam.international</groupId>
<artifactId>seam-international</artifactId>
<version>3.0.0.Final</version>
</dependency>
I still get
java.lang.ClassNotFoundException: org.joda.time.DateTimeZone
And as Dan mentioned, use Glassfish 3.1 over Glassfish 3.0
yes. It works fine on Glassfish 3.1
--
Sebastian E. Ovide
5072
days inactive
5072
days old
4 comments
3 participants
participants (3)
-
Brian Leathem -
Dan Allen -
Sebastian E. Ovide