Yes, I was trying to quickly get to a point where Anissa could continue
her work on the console. I will move the elasticity config beans under
the elasticity module asap. I now understand how my code will get
invoked so I can back out my changes to the cluster create command and
work with her to get things done correctly.
Carla
On 9/2/11 8:28 AM, Tom Mueller wrote:
> Given that the config beans for modules under appserver have been
> moved to the the modules that actually use the config beans, should we
> expect that the same pattern would be followed within nucleus, i.e.,
> if there is a Virtualization config bean, then that config bean should
> be under a virtualization module rather than under admin/config-api?
>
> Tom
>
> On 9/1/2011 6:44 PM, Carla Mott wrote:
>> Just noticed that this change introduces a cyclic reference. Need to
>> clean that up.
>>
>> On 9/1/11 4:39 PM, Carla Mott wrote:
>>>
>>> Please review: I added a dependency in pom.xml under admin/config-api
>>>
>>> <version>${project.parent.version}</version>
>>> </dependency>
>>> <dependency>
>>> + <groupId>org.glassfish.virtualization</groupId>
>>> + <artifactId>libvirt</artifactId>
>>> + <version>${project.parent.version}</version>
>>> + </dependency>
>>> + <dependency>
>>> <groupId>org.glassfish.common</groupId>
>>> <artifactId>glassfish-api</artifactId>
>>> <version>${project.parent.version}</version>
>>