[jopr-dev] Re: [Fwd: [JBoss JIRA] Updated: (JBAS-5370) Deploy an ear/war app through ProfileService]
Another problem I'm seeing in the eclipse project is that there is a
jboss-ejb3-all-1.0.0.Alpha9.jar that includes out of date profileservice
ManagementView interfaces:
embjopr/jbas5/target/admin-console/rhq-core-domain/META-INF/maven/org.rhq/rhq-core-domain/pom.xml
<dependency>
<groupId>jboss.jboss-embeddable-ejb3</groupId>
<artifactId>jboss-ejb3-all</artifactId>
<version>${jboss-embeddable-ejb3.version}</version>
<scope>test</scope>
</dependency>
[659][valkyrie: profileservice]$ jar -tf
/home/svn/repository.jboss.org/maven2/jboss/jboss-embeddable-ejb3/jboss-ejb3-all/1.0.0.Alpha9/jboss-ejb3-all-1.0.0.Alpha9.jar
| grep ManagementView
org/jboss/deployers/spi/management/ManagementView.class
org/jboss/system/server/profileservice/ManagementViewImpl.class
I can workaround this by moving the rhq project to the last dependency
in the jopr project library/projects ordering.
Charles Crouch wrote:
Ok I can update the jboss-managed component version.
Just out of interest, whats going into the 2.0.0 snapshot versions that we don't want
to pickup? Surely those changes are going to end up in the 2.0.0.GA version that we'll
eventually be running with anyway? Or is it that stuff is still unstable in /trunk of this
component?
----- "Scott Stark" <sstark(a)redhat.com> wrote:
> The deployment manager api is only available in the jbossas snapshots.
>
> The jboss-managed version should now be 2.0.0.CR4 rather than a
> snapshot
> though.
>
> Charles Crouch wrote:
>
>> From the regular hudson build...
>>
>> cd ${JOPR}/modules/plugins/jboss-as-5
>> mvn ${MAVEN_ARGS}
>>
>> So its being built specifically, rather than being pulled in
>>
> automatically as part of jopr/modules/plugins
>
>> Given the faster turnaround we should be able to get using snapshots
>>
> of JBAS components, I presume we're going to want to continue using
> those while there is still dev work going on in there?
>
>> Cheers
>> Charles
>>
>>
>>