JBossDeveloper

The above is the answer from Gavin ;)

To get a more complete list we simply just need to go through the thirdparty-all.jar and figure out what is in there precisly; I could do that, but you could do it too (hint hint ;)

If you generate the list then I can verify it for you. I think that will be the most efficient way of doing it.

Simply look at the packages in the .jar and find the corresponding one in hibernate3/lib.

I put up my best guesses on hibernate-all and jboss-ejb3-all.jar. Version wise, I think they are probably JBoss AS 4.0.5 versions. jboss-ejb3-all.jar looks to me like the contents of a new ejb3 project in eclipse, less persistence and commons logging. HTH

I am extremely happy to see a serious interest in the maven2 integration.
I am also confident that Gavin will love this ;-)


I am not sure that it is something new for you people. May be it will be helpful.
This is the POM I have used for building SEAM 1.1.1.BETA2

POM.XML

<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
 <modelVersion>4.0.0</modelVersion>
 <groupId>org.jboss.seam</groupId>
 <artifactId>jboss-seam</artifactId>
 <packaging>jar</packaging>
 <version>1.1.0.BETA2</version>
 <description>qqq</description>
 <dependencies>
 <!--dependency>
 <groupId>org.hibernate</groupId>
 <artifactId>hibernateAll</artifactId>
 <version>SEAM.1.1.0.BETA2</version>
 </dependency-->
 <dependency>
 <groupId>org.hibernate</groupId>
 <artifactId>hibernate</artifactId>
 <version>3.2.0.ga</version>
 </dependency>
 <dependency>
 <groupId>org.hibernate</groupId>
 <artifactId>hibernate-annotations</artifactId>
 <version>3.2.0.ga</version>
 </dependency>
 <dependency>
 <groupId>org.hibernate</groupId>
 <artifactId>hibernate-entitymanager</artifactId>
 <version>3.2.0.ga</version>
 </dependency>
 <dependency>
 <groupId>org.jboss.ejb3</groupId>
 <artifactId>jboss-ejb3-all</artifactId>
 <version>SEAM.1.1.0.BETA2</version>
 </dependency>
 <dependency>
 <groupId>org.jboss.jbpm</groupId>
 <artifactId>jbpm</artifactId>
 <version>3.1.2</version>
 </dependency>
 <dependency>
 <groupId>org.jboss.drools</groupId>
 <artifactId>drools-core</artifactId>
 <version>3.0.1</version>
 </dependency>
 <dependency>
 <groupId>org.jboss.drools</groupId>
 <artifactId>drools-compiler</artifactId>
 <version>3.0.1</version>
 </dependency>
 <dependency>
 <groupId>org.jboss.cache</groupId>
 <artifactId>jboss-cache</artifactId>
 <version>SEAM.1.1.0.BETA2</version>
 </dependency>
 <dependency>
 <groupId>javax.portlet</groupId>
 <artifactId>portlet-api</artifactId>
 <version>1.0</version>
 </dependency>
 <dependency>
 <groupId>org.testng</groupId>
 <artifactId>testng</artifactId>
 <classifier>jdk15</classifier>
 <version>5.1</version>
 </dependency>
 <dependency>
 <groupId>log4j</groupId>
 <artifactId>log4j</artifactId>
 <version>1.2.13</version>
 </dependency>
 <dependency>
 <groupId>commons-logging</groupId>
 <artifactId>commons-logging</artifactId>
 <version>1.1</version>
 </dependency>
 <dependency>
 <groupId>commons-collections</groupId>
 <artifactId>commons-collections</artifactId>
 <version>3.2</version>
 </dependency>
 <dependency>
 <groupId>org.apache.myfaces.core</groupId>
 <artifactId>myfaces-api</artifactId>
 <version>1.1.4</version>
 </dependency>
 <dependency>
 <groupId>javax.el</groupId>
 <artifactId>el-api</artifactId>
 <version>1.2</version>
 </dependency>
 <dependency>
 <groupId>javax.el</groupId>
 <artifactId>el-ri</artifactId>
 <version>1.2</version>
 </dependency>
 <dependency>
 <groupId>javax.servlet</groupId>
 <artifactId>jstl</artifactId>
 <version>1.1.2</version>
 </dependency>
 <dependency>
 <groupId>javax.servlet</groupId>
 <artifactId>servlet-api</artifactId>
 <version>2.5</version>
 </dependency>
 </dependencies>
 <build>
 <plugins>
 <plugin>
 <groupId>org.apache.maven.plugins</groupId>
 <artifactId>maven-compiler-plugin</artifactId>
 <version>2.0</version>
 <configuration>
 <source>1.5</source>
 <target>1.5</target>
 </configuration>
 </plugin>
 </plugins>
 <outputDirectory>target/jboss-seam.jar</outputDirectory>
 </build>
</project>

mvn install:install-file -Dfile=c:\javaprogs\new\jboss-seam-1.1.0.BETA2\lib\jboss-ejb3-all.jar -DgroupId=org.jboss.ejb3 -DartifactId=jboss-ejb3-all -Dversion=SEAM.1.1.0.BETA2 -Dpackaging=jar

mvn install:install-file -Dfile=c:\javaprogs\new\jboss-seam-1.1.0.BETA2\lib\jbpm-3.1.2.jar -DgroupId=org.jboss.jbpm -DartifactId=jbpm -Dversion=3.1.2 -Dpackaging=jar

mvn install:install-file -Dfile=c:\javaprogs\new\jboss-seam-1.1.0.BETA2\drools\lib\drools-core-3.0.3.jar -DgroupId=org.jboss.drools -DartifactId=drools-core -Dversion=3.0.3 -Dpackaging=jar

mvn install:install-file -Dfile=c:\javaprogs\new\jboss-seam-1.1.0.BETA2\drools\lib\drools-compiler-3.0.3.jar -DgroupId=org.jboss.drools -DartifactId=drools-compiler -Dversion=3.0.3 -Dpackaging=jar

mvn install:install-file
 -Dfile=c:\javaprogs\new\jboss-seam-1.1.0.BETA2\lib\jboss-cache-jdk50.jar
 -DgroupId=org.jboss.cache -DartifactId=jboss-cache
 -Dversion=SEAM.1.1.0.BETA2 -Dpackaging=jar

mvn install:install-file -Dfile=c:\javaprogs\new\hibernate-3.2\lib\jta.jar
 -DgroupId=javax.transaction -DartifactId=jta -Dversion=1.0.1B
 -Dpackaging=jar

mvn install:install-file
 -Dfile=c:\javaprogs\new\jboss-seam-1.1.0.BETA2\lib\el-api.jar
 -DgroupId=javax.el -DartifactId=el-api -Dversion=1.2 -Dpackaging=jar

mvn install:install-file
 -Dfile=c:\javaprogs\new\jboss-seam-1.1.0.BETA2\lib\el-ri.jar
 -DgroupId=javax.el -DartifactId=el-ri -Dversion=1.2
 -Dpackaging=jar

So is the plan here to be able to create maven support for building Seam itself, documentation, and example apps?

Or is the plan just to have something which people can use for building their own projects?

Or both?

Actually most of the jars in the lib directory come from:

jboss-EJB-3.0_Embeddable_ALPHA_8-patch2.zip

Because of a bad bug in ALPHA_9, Seam was never updated to use it.

I think we are going to try to do both.

I would recommend you start out doing the POM for something that can be used by *users* of Seam.

Then afterwards we can begin having "fun" with trying to "bend" either seam buildstructure or Maven to be compatible.

It depends how much time you have to put into this. I'd love to see a mavenized build of the Seam dist, assuming it made the build simpler, and not more complex. But this could turn out to be a pretty major undertaking. I would much rather see *something* useful come out of this process, than see you guys give up due to lack of time....

OK, cool.

A first step on (5) would be to try to retrospectively apply the unified maven build to the Seam examples directory. I think it would be perfectly reasonable to use Ant for building Seam, and maven for building the examples.

Again, assuming that Maven actually makes things simpler and not more complex - which I'm withholding judgment on for now :-)

Yeah, just after I get through the first chapter of that Rails book a bought 6 months ago ;-)

Are you saying I need to take a Maven book with me on vacation :-)