Although this is an acceptable workaround for getting rid of the
warning, I am not sure that's the right thing eventually. We should
probably have the javax.management API bundle becoming a full OSGi
module with its dependencies set correctly and then the warning will
disappear. I am not too keen to have every single GlassFish bundle
depend on the entire Java EE Api set as it will make the Java EE 6
distro building a lot more difficult.
so Lloyd, feel free to change it if you cannot stand the warning, but
eventually I will ask you to change it back...
Jerome
On Jun 2, 2008, at 10:58 AM, Sahoo wrote:
> Lloyd L Chambers wrote:
>> It's been 2 weeks or so since I've built v3. Something has changed.
> Yes, v3 now uses hk2 version 0.3.1 and the new hk2 plugin now warns
> developers about potential missing dependencies
> (NoClassdefFoundError).
>> amx-api pom.xml has this declaration:
>>
>> <dependencies>
>> <dependency>
>> <groupId>javax.management.j2ee</groupId>
>> <artifactId>management-api</artifactId>
>> <version>${management-api.version}</version>
>> <scope>provided</scope>
>> </dependency>
> Instead of depending on javax.management.j2ee:management-api, depend
> on org.glassfish:javax.javaee like this:
> <dependency>
> <groupId>org.glassfish</groupId>
> <artifactId>javax.javaee</artifactId>
> <version>${project.version}</version>
> <scope>provided</scope>
> </dependency>
>
> Thanks,
> Sahoo
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>