JBossAS7

This wiki page shows the progress of including JBoss AS dependencies.

People involved

Below is the list of currently involved people in the process.

Name	IRC	Current work	Additional info
Marek Goldmann	mgoldmann	Doing the dirty work of preparing jars to be packaged. See Current approach section for more info.	UTC+2

Current approach

The idea is to package minimal set of JAR's. This means that only core JARs required to run or build AS7 will be packaged. This will let us package AS7 in reasonable timeframe. All additional JARs can be added later, for example to improve/enable test execution.

I am (Marek Goldmann) now using following approach to select what needs to be packaged and what not:

• Create a spec file.
• Try to build the package.
  • Failure - see what what was the cause and:
    • Missing dependency? Comment it out and build.
      • Success - cool!
      • Failure - go to beginning and start with that dependency.
    • Issue in code? Create a patch.
  • Success - add spec file to queue for cleanup!

Cleanup queue

Cleanup queue location
Cleanup queue is located here: http://goldmann.fedorapeople.org/jboss_as/queue/.

Want to help us?
Cleaning up packages in cleanup queue and submitting them to Fedora is the easiest way you can help us! If you pick up a package - let us know on IRC and add you to the table below.

In cleanup queue you can find packages that are building fine, but the spec files needs cleanup. Cleanup can include (but is not limited to):

• License, description, url, name, version, changelog are correct.
• Make sure the spec files is following additional rules.

After cleanup - package can be submitted to Fedora.

Rules for JBoss-related packages

Additionally to Java packaging rules - please meet following instructions for JBoss-related packages, like jboss-dmr, jboss-logging and so on:

• JARs should be installed in $RPM_BUILD_ROOT%{_javadir}/jboss
• POM files should be installed in $RPM_BUILD_ROOT%{_mavenpomdir}/JPP.jboss-%{name}.pom
• Use %add_maven_depmap macro. It should look similar to this:

%add_maven_depmap JPP.jboss-%{name}.pom jboss/%{name}.jar

We need your help!

Feel free to grab dependency you want to package and add you to the list. You can talk to us on #fedora-java IRC or using mailing list.

Be fast!
Make sure you add the dependency immediately after you decide to pick it up so other can see what deps are available for packaging.

Current progress

Table below shows what is officially submitted to Fedora (after creating review request). This is not the cleanup queue content.

Package	Version	Maven groupID:artifactId	POM	Review request	Packager	Status	Comments
hibernate-commons-annotations	3.2.0	org.hibernate:hibernate-commons-annotations	POM	RHBZ #706832	goldmann	In Rawhide
hibernate-jpa-2.0-api	1.0.0	org.hibernate.javax.persistence:hibernate-jpa-2.0-api	POM	RHBZ #706846	goldmann	In review	License status cleaned up
fusesource-pom	1.5	org.fusesource:fusesource-pom	POM	RHBZ #708645	goldmann	In Rawhide
hawtjni	1.1	org.fusesource.hawtjni:hawtjni*	Parent POM	RHBZ #708670	goldmann	In Rawhide	Depends on RHBZ #708669
jansi-native	1.1	org.fusesource.jansi:jansi-native	POM	RHBZ #708836	goldmann	In review	Depends on RHBZ #708669 and RHBZ #708670
jansi	1.5	org.fusesource.jansi:jansi	POM	RHBZ #708842	goldmann	Waiting for review	Depends on RHBZ #708669 and RHBZ #708836
gossip	1.7	org.sonatype.gossip:gossip*	POM	RHBZ #709051	goldmann	Waiting for review	Depends on RHBZ #708842
jline2	2.5	org.sonatype.jline:jline	POM	RHBZ #709300	goldmann	Waiting for review	Depends on RHBZ #708842

Status legend

Status	Meaning
Issue	Package encountered a serious issue while packaging (license, etc) - see Comments field for more info
In review	Package is submitted for review and being reviewed by someone
After review, waiting for SCM	Package passed review and packages is waiting for creating git repo in Fedora for this package
In Rawhide	Package is available in Rawhide