JBoss AS 7 packaging effort update
 

Hi all,

If you're interested in JBoss Application Server I'm forwarding the
current status of the packaging effort.


--Marek

-------- Original Message --------
Subject: [jboss-rpm] jboss-as is alive and on the road to next update
Date: Wed, 27 Jun 2012 10:23:01 +0200
From: Marek Goldmann <mgoldman@redhat.com>
To: jboss-rpm@lists.jboss.org <jboss-rpm@lists.jboss.org>

Hi,

You may be wondering what's happening in the jboss-as package world :) I
know I haven't updated you since some time, but finally there is a bunch
of news!

I'm working on jboss-as-7.1.1-4. This will be a pretty big update, a lot
of new subsystems will be enabled and the way I work on the spec will be
changed.

1. New subsystems.

Compared to 7.1.1-3, following new subsystems will be enabled:

- org.jboss.as.arquillian
- org.jboss.as.osgi
- org.jboss.as.configadmin
- org.jboss.as.spec-api

As you can see, 7.1.1-4 is focusing on OSGi stuff. This involved
packaging a lot of new JBoss OSGi dependencies (12 packages). As usual,
you can watch the table for latest packaging info:

https://fedoraproject.org/wiki/JBossAS7#Current_progress

2. New way of working with AS7 patches

With 7.1.1-3 we reached more than 80 patches to the AS7 codebase to
compile it and make it run on Fedora. The amount of patches was pretty
close to what RHEL5 had :) It wasn't fun to manage it.

So far I moved new subsystems to minimalistic profile and afterwards I
build it. Over the time, when I added more and more subsystems - the
patch set was growing.

Since we have only a few modules not available in Fedora, starting from
now - I'm building default profile and commenting out modules which are
still not available. This simple step will save me a lot of work and
make the development more stable.

I think 7.1.1-4 is going to have about 25 patches.

Once we'll have all AS7 deps available, the goal is to rebase one more
time and leave only patches that are necessary and remove everything
else. This will decrease the patch amount one more time.

3. New linked modules

The new way of building mentioned in #3 showed me that I forgot to link
some modules. This will be fixed and about 35 additional modules
(/usr/share/jboss-as/modules/...) will be added.

4. ExampleDS available

There was one issue hanging since some time in BZ:

https://bugzilla.redhat.com/show_bug.cgi?id=812522

In 7.1.1-4 we'll have the ExampleDS finally available!

That's all!

If you want to help me pushing 7.1.1-4 out, please take some packages
for review:

- https://bugzilla.redhat.com/show_bug.cgi?id=830763 (free to review)
- https://bugzilla.redhat.com/show_bug.cgi?id=832446
- https://bugzilla.redhat.com/show_bug.cgi?id=832443

High priority is #830763, since it blocks everything else... If you have
questions or need help, please join #fedora-java IRC channel on freenode.

Thanks!

P.S. If you have time, please consider also commenting on this bug report:

https://bugzilla.redhat.com/show_bug.cgi?id=827584

--Marek
_______________________________________________
jboss-rpm mailing list
jboss-rpm@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-rpm


--
java-devel mailing list
java-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/java-devel

JBoss AS 7 packaging effort update
 

That's great news Marek! The sample datasource, especially, should help
when demonstrating the capabilities of the package as it's used in most
of the quickstarts we use.


Of course, I'm also very excited about the inclusion of Arquillian. My
vision here is to eventually run the Arquillian-based tests as part of
the rpm build so that we are confident it's in good working order. We
can perhaps add a supplemental build (not sure how such a thing is
organized in rpm world, so I'm speaking generally) to use Arquillian
tests to verify the installed version of JBoss AS is in good working
order too.


Will the Arquillian support include the container adapters for
standalone remote and managed?


I have one other question about the JBoss AS package. I noticed that
RESTeasy is packaged, but the JAX-RS module in JBoss AS is not currently
working. Is this a known issue? If so, what's the blocker for getting it
to work? JAX-RS is another key service to help demonstrating the
capabilities of the package.


Btw, I'll be demoing JBoss AS on Fedora at JAX (next week) and OSCON
(the following week). I'll use -4 if it's available.


-Dan

On 06/27/2012 04:35 AM, Marek Goldmann wrote:

Hi all,

If you're interested in JBoss Application Server I'm forwarding the
current status of the packaging effort.


--Marek

-------- Original Message --------
Subject: [jboss-rpm] jboss-as is alive and on the road to next update
Date: Wed, 27 Jun 2012 10:23:01 +0200
From: Marek Goldmann <mgoldman@redhat.com>
To: jboss-rpm@lists.jboss.org <jboss-rpm@lists.jboss.org>

Hi,

You may be wondering what's happening in the jboss-as package world :) I
know I haven't updated you since some time, but finally there is a bunch
of news!

I'm working on jboss-as-7.1.1-4. This will be a pretty big update, a lot
of new subsystems will be enabled and the way I work on the spec will be
changed.

1. New subsystems.

Compared to 7.1.1-3, following new subsystems will be enabled:

- org.jboss.as.arquillian
- org.jboss.as.osgi
- org.jboss.as.configadmin
- org.jboss.as.spec-api

As you can see, 7.1.1-4 is focusing on OSGi stuff. This involved
packaging a lot of new JBoss OSGi dependencies (12 packages). As usual,
you can watch the table for latest packaging info:

https://fedoraproject.org/wiki/JBossAS7#Current_progress

2. New way of working with AS7 patches

With 7.1.1-3 we reached more than 80 patches to the AS7 codebase to
compile it and make it run on Fedora. The amount of patches was pretty
close to what RHEL5 had :) It wasn't fun to manage it.

So far I moved new subsystems to minimalistic profile and afterwards I
build it. Over the time, when I added more and more subsystems - the
patch set was growing.

Since we have only a few modules not available in Fedora, starting from
now - I'm building default profile and commenting out modules which are
still not available. This simple step will save me a lot of work and
make the development more stable.

I think 7.1.1-4 is going to have about 25 patches.

Once we'll have all AS7 deps available, the goal is to rebase one more
time and leave only patches that are necessary and remove everything
else. This will decrease the patch amount one more time.

3. New linked modules

The new way of building mentioned in #3 showed me that I forgot to link
some modules. This will be fixed and about 35 additional modules
(/usr/share/jboss-as/modules/...) will be added.

4. ExampleDS available

There was one issue hanging since some time in BZ:

https://bugzilla.redhat.com/show_bug.cgi?id=812522

In 7.1.1-4 we'll have the ExampleDS finally available!

That's all!

If you want to help me pushing 7.1.1-4 out, please take some packages
for review:

- https://bugzilla.redhat.com/show_bug.cgi?id=830763 (free to review)
- https://bugzilla.redhat.com/show_bug.cgi?id=832446
- https://bugzilla.redhat.com/show_bug.cgi?id=832443

High priority is #830763, since it blocks everything else... If you have
questions or need help, please join #fedora-java IRC channel on freenode.

Thanks!

P.S. If you have time, please consider also commenting on this bug
report:


https://bugzilla.redhat.com/show_bug.cgi?id=827584

--Marek
_______________________________________________
jboss-rpm mailing list
jboss-rpm@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-rpm






--
Dan Allen
Principal Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597

http://google.com/profiles/dan.j.allen
http://mojavelinux.com
http://mojavelinux.com/seaminaction

--
java-devel mailing list
java-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/java-devel