Community

ejb3_1 and its relation with ejb3 bom

reply from jaikiran pai in EJB 3.0 Development - View the full discussion

The other option that I have been thinking of is to get rid of ejb3_1 entirely. That way we will have a bom which will both have dependencyManagement and dependencies specified. Effectively, that will act as the entity which manages the right versions and also let's the consuming projects (like AS) "depend" (so that dependencies are pulled in the CP) as well as import it. So we would probably end up having bom-as6 (multiple version), bom-as-6.1 (multiple versions) artifacts.

Reply to this message by going to Community

Start a new discussion in EJB 3.0 Development at Community