1:19 a.m.
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
----- "Scott Stark" <sstark(a)redhat.com> wrote:
The jobr/modules/plugins/pom.xml does not have the jboss-as5 plugin
enabled:
<!-- NOTE: The jboss-as5 plugin is not included for now, because
all its deps are
snapshots, which the maven release plugin would
deeply
frown upon.-->
</modules>
If I go into modules/plugins/jboss-as-5 it builds fine, but the
eclipse
project settings are wrong because the modules/plugins/jboss-as-5 is
not
included as a source path. So I'm wondering how its being built and
developed?
Charles Crouch wrote:
> The JBAS 5 plugin was building fine as of this morning. Take a look
at the settings we use to generated the snapshots:
>
>
http://hudson.qa.jboss.com/hudson/view/jon-2.x/job/rhq-jopr-nightly/confi...
>
> What errors are you seeing?
> Cheers
> Charles
> ----- "Scott Stark" <sstark(a)redhat.com> wrote:
>
>
>> Did you see the question I posted to this list about how the plugin
is
>> getting built?
>>
>> -------- Original Message --------
>> Subject: [JBoss JIRA] Updated: (JBAS-5370) Deploy an ear/war app
>> through ProfileService
>> Date: Mon, 10 Nov 2008 14:49:41 -0500 (EST)
>> From: Charles Crouch (JIRA) <jira-events(a)lists.jboss.org>
>> To: scott.stark(a)jboss.org
>>
>> [
>>
https://jira.jboss.org/jira/browse/JBAS-5370?page=com.atlassian.jira.plug...
>> ]
>>
>> Charles Crouch updated JBAS-5370:
>> ---------------------------------
>>
>> Fix Version/s: JBossAS-5.0.0.GA
>> Priority: Critical (was: Major)
>>
>>
>>
>>> Deploy an ear/war app through ProfileService
>>> --------------------------------------------
>>>
>>> Key: JBAS-5370
>>> URL: https://jira.jboss.org/jira/browse/JBAS-5370
>
>>>
>> Project: JBoss Application Server
>>
>>> Issue Type: Sub-task
>>> Security Level: Public(Everyone can see)
>>> Reporter: Mark Spritzler
>>> Assignee: Scott M Stark
>>> Priority: Critical
>>> Fix For: JBossAS-5.0.0.GA
>>>
>>>
>>>
>> --
>> This message is automatically generated by JIRA.
>> -
>> If you think it was sent incorrectly contact one of the
>> administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
>> -
>> For more information on JIRA, see:
>> http://www.atlassian.com/software/jira
>>
1:22 a.m.
New subject: [Fwd: [JBoss JIRA] Updated: (JBAS-5370) Deploy an ear/war app through ProfileService]
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
1:42 a.m.
New subject: [Fwd: [JBoss JIRA] Updated: (JBAS-5370) Deploy an ear/war app through ProfileService]
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
>
>
2:03 a.m.
New subject: [Fwd: [JBoss JIRA] Updated: (JBAS-5370) Deploy an ear/war app through ProfileService]
The problem is that the jboss-managed snapshots are not being updated
since we started CR releases. The last snapshot was two months ago:
https://snapshots.jboss.org/maven2/org/jboss/man/jboss-managed/2.0.0-SNAP...
I'm surprised something has not broken!
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
>>
>>
>>
5:58 a.m.
New subject: [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
>>
>>
>>
5645
days inactive
5645
days old
4 comments
2 participants
participants (2)
-
Charles Crouch -
Scott Stark