-
1. Re: Ant Requirement for JBossWeb HttpService
How does mvn report the missing dependency? At runtime or compile time?
The reason is likely that jbossweb provides insufficient metadata in its pom (e.g. https://repository.jboss.org/nexus/content/groups/public/jboss/web/jbossweb/3.0.0-beta-5/jbossweb-3.0.0-beta-5.pom)
There is no information given on transitive dependencies. This should be addressed in jbossweb so that this can get fixed in future. Could you please create a jira for that and post the link here? The point is that a consumer of jbossweb (i.e. jbosgi-http) should not be forced to know the complete set of jbossweb's transitive dependencies. It breaks the rules of modularity when you force clients to include your transitive dependencies as their top-level dependencies.
To give an example: project foo-1.0 depends on bar-2.0 but does not declare it in the pom. Project baz wants to use foo but cant without also declaring a dependency on bar, the version of which can only be guessed and is likely to get outdated or incorrect when baz updates foo to a later version.
I'd like to know whether the dependency on ant is in scope compile, provided, test or something else. Naturally, I'd get this info from the pom, which in the case of jbossweb is insufficient.
-
2. Re: Ant Requirement for JBossWeb HttpService
The dependency first came to notice during compile. It is reported as a Constraint error.
A JIRA for this is at https://jira.jboss.org/browse/JBWEB-170