[seam-issues] [JBoss JIRA] Resolved: (SOLDER-100) Missing deps running in Weld SE

[Stuart Douglas (JIRA)]

     [ https://issues.jboss.org/browse/SOLDER-100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stuart Douglas resolved SOLDER-100.
-----------------------------------

      Assignee: Stuart Douglas
    Resolution: Won't Fix


This is an issue in Weld SE 1.0.1, not a solder issue. Using a more recent weld should fix the problem.

> Missing deps running in Weld SE
> -------------------------------
>
>                 Key: SOLDER-100
>                 URL: https://issues.jboss.org/browse/SOLDER-100
>             Project: Seam Solder
>          Issue Type: Enhancement
>    Affects Versions: 3.0.0.CR4
>            Reporter: Peter Royle
>            Assignee: Stuart Douglas
>            Priority: Minor
>              Labels: dependencies, runtime, weld, weld-se
>
> My main concern is the runtime dependency on javax.servlet API when run in Weld SE (1.0.1). Not sure if it's one of your goals but if you *do* wish to target SE it would be cool if Solder didn't bomb out when Servlet is not present. We had a similar issue with Weld SE at the beginning as well, and Pete Muir sorted it out. Unfortunately this problem doesn't occur when using Arquillian's Weld SE configuration, so I don't have a sample test to give you.
> This was the dependency I added to solve that particular problem:
> <dependency>
>          <groupId>javax.servlet</groupId>
>          <artifactId>servlet-api</artifactId>
>          <version>2.5</version>
>       </dependency>
> There were also other runtime dependencies which weren't satisfied when running in Weld SE. These solved them:
>       <dependency>
>          <groupId>org.jboss.logmanager</groupId>
>          <artifactId>jboss-logmanager</artifactId>
>          <version>1.2.0.CR9</version>
>       </dependency>
>       <dependency>
>          <groupId>log4j</groupId>
>          <artifactId>log4j</artifactId>
>          <version>1.2.14</version>
>       </dependency>
> I'll provide stack traces for each of the individual errors in separate comments.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira