[Design the new POJO MicroContainer] - Re: Using MAVEN2_CLASSPATH_CONTAINER
by wolfc
I would also say to make an eclipse profile mandatory which puts the classes in 'eclipse-target/...' instead of 'target'. I've seen some cases where JDT would create class files that where wrong and those ended up in the (snapshot) repository.
<build>
| <!-- based on the profile we switch directories -->
| <outputDirectory>${myproject.outputDirectory}</outputDirectory>
| <testOutputDirectory>${myproject.testOutputDirectory}</testOutputDirectory>
| </build>
|
| <profiles>
| <!--
| To make sure we don't end up with Eclipse compiled classes
| in the repo we use different output directories when running
| under Eclipse.
| -->
| <profile>
| <id>default</id>
| <activation>
| <activeByDefault>true</activeByDefault>
| </activation>
| <properties>
| <myproject.outputDirectory>target/classes</myproject.outputDirectory>
| <myproject.testOutputDirectory>
| target/test-classes
| </myproject.testOutputDirectory>
| </properties>
| </profile>
|
| <profile>
| <id>eclipse</id>
| <build>
| <defaultGoal>process-test-resources</defaultGoal>
| <plugins>
| <plugin>
| <artifactId>maven-eclipse-plugin</artifactId>
| <version>2.6</version>
| <configuration>
| <downloadSources>true</downloadSources>
| <buildOutputDirectory>eclipse-target/classes</buildOutputDirectory>
| </configuration>
| </plugin>
| </plugins>
| </build>
| <properties>
| <myproject.outputDirectory>eclipse-target/classes</myproject.outputDirectory>
| <myproject.testOutputDirectory>
| eclipse-target/test-classes
| </myproject.testOutputDirectory>
| </properties>
| </profile>
| </profiles>
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4238414#4238414
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4238414
16 years, 9 months
[Design the new POJO MicroContainer] - Using MAVEN2_CLASSPATH_CONTAINER
by thomas.diesler＠jboss.com
Folks,
I noticed that the kernel eclipse setup does not leverage the projects dependencies defined by the pom.
Instead of manually maintaining the dependency list like this
| <classpath>
| <classpathentry kind="src" path="src/main/java"/>
| <classpathentry kind="src" path="src/main/resources" excluding="**/*.java"/>
| <classpathentry kind="src" path="src/test/java" output="target/test-classes"/>
| <classpathentry kind="src" path="src/test/resources" output="target/test-classes" excluding="**/*.java"/>
| <classpathentry kind="output" path="target/classes"/>
| <classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER"/>
| <classpathentry kind="var" path="M2_REPO/javax/activation/activation/1.1.1/activation-1.1.1.jar"/>
| <classpathentry kind="var" path="M2_REPO/org/apache/ant/ant/1.7.0/ant-1.7.0.jar"/>
| <classpathentry kind="var" path="M2_REPO/org/apache/ant/ant-junit/1.7.0/ant-junit-1.7.0.jar"/>
| <classpathentry kind="var" path="M2_REPO/org/apache/ant/ant-launcher/1.7.0/ant-launcher-1.7.0.jar"/>
| <classpathentry kind="var" path="M2_REPO/wutka-dtdparser/dtdparser121/1.2.1/dtdparser121-1.2.1.jar"/>
| <classpathentry kind="var" path="M2_REPO/sun-jaxb/jaxb-api/2.1.4/jaxb-api-2.1.4.jar" sourcepath="M2_REPO/sun-jaxb/jaxb-api/2.1.4/jaxb-api-2.1.4-sources.jar"/>
| <classpathentry kind="var" path="M2_REPO/org/jboss/jboss-common-core/2.2.13.GA/jboss-common-core-2.2.13.GA.jar" sourcepath="M2_REPO/org/jboss/jboss-common-core/2.2.13.GA/jboss-common-core-2.2.13.GA-sources.jar"/>
| <classpathentry kind="src" path="/jboss-dependency"/>
| <classpathentry kind="src" path="/jboss-kernel"/>
| <classpathentry kind="var" path="M2_REPO/org/jboss/logging/jboss-logging-log4j/2.0.5.GA/jboss-logging-log4j-2.0.5.GA.jar" sourcepath="M2_REPO/org/jboss/logging/jboss-logging-log4j/2.0.5.GA/jboss-logging-log4j-2.0.5.GA-sources.jar"/>
| <classpathentry kind="var" path="M2_REPO/org/jboss/logging/jboss-logging-spi/2.0.5.GA/jboss-logging-spi-2.0.5.GA.jar" sourcepath="M2_REPO/org/jboss/logging/jboss-logging-spi/2.0.5.GA/jboss-logging-spi-2.0.5.GA-sources.jar"/>
| <classpathentry kind="var" path="M2_REPO/org/jboss/man/jboss-managed/2.1.0.CR8/jboss-managed-2.1.0.CR8.jar" sourcepath="M2_REPO/org/jboss/man/jboss-managed/2.1.0.CR8/jboss-managed-2.1.0.CR8-sources.jar"/>
| <classpathentry kind="var" path="M2_REPO/org/jboss/jboss-mdr/2.0.1.GA/jboss-mdr-2.0.1.GA.jar" sourcepath="M2_REPO/org/jboss/jboss-mdr/2.0.1.GA/jboss-mdr-2.0.1.GA-sources.jar"/>
| <classpathentry kind="var" path="M2_REPO/org/jboss/man/jboss-metatype/2.1.0.CR8/jboss-metatype-2.1.0.CR8.jar" sourcepath="M2_REPO/org/jboss/man/jboss-metatype/2.1.0.CR8/jboss-metatype-2.1.0.CR8-sources.jar"/>
| <classpathentry kind="var" path="M2_REPO/jboss/profiler/jvmti/jboss-profiler-jvmti/1.0.0.CR5/jboss-profiler-jvmti-1.0.0.CR5.jar"/>
| <classpathentry kind="var" path="M2_REPO/org/jboss/jboss-reflect/2.0.2.GA/jboss-reflect-2.0.2.GA.jar" sourcepath="M2_REPO/org/jboss/jboss-reflect/2.0.2.GA/jboss-reflect-2.0.2.GA-sources.jar"/>
| <classpathentry kind="var" path="M2_REPO/org/jboss/jbossas/jboss-server-manager/0.1.1.GA/jboss-server-manager-0.1.1.GA.jar" sourcepath="M2_REPO/org/jboss/jbossas/jboss-server-manager/0.1.1.GA/jboss-server-manager-0.1.1.GA-sources.jar"/>
| <classpathentry kind="var" path="M2_REPO/org/jboss/test/jboss-test/1.1.1.GA/jboss-test-1.1.1.GA.jar" sourcepath="M2_REPO/org/jboss/test/jboss-test/1.1.1.GA/jboss-test-1.1.1.GA-sources.jar"/>
| <classpathentry kind="var" path="M2_REPO/org/jboss/jbossxb/2.0.1.GA/jbossxb-2.0.1.GA.jar" sourcepath="M2_REPO/org/jboss/jbossxb/2.0.1.GA/jbossxb-2.0.1.GA-sources.jar"/>
| <classpathentry kind="var" path="M2_REPO/junit/junit/4.4/junit-4.4.jar" sourcepath="M2_REPO/junit/junit/4.4/junit-4.4-sources.jar"/>
| <classpathentry kind="var" path="M2_REPO/apache-log4j/log4j/1.2.14/log4j-1.2.14.jar" sourcepath="M2_REPO/apache-log4j/log4j/1.2.14/log4j-1.2.14-sources.jar"/>
| <classpathentry kind="var" path="M2_REPO/apache-xerces/xercesImpl/2.9.1/xercesImpl-2.9.1.jar"/>
| <classpathentry kind="var" path="M2_REPO/apache-xerces/xml-apis/2.9.1/xml-apis-2.9.1.jar"/>
| </classpath>
|
it would be possible to delegate to the eclipse maven plugin, like this
| <classpath>
| <classpathentry kind="src" output="target/classes" path="src/main/java"/>
| <classpathentry excluding="**" kind="src" output="target/classes" path="src/main/resources"/>
| <classpathentry kind="src" output="target/test-classes" path="src/test/java"/>
| <classpathentry excluding="**" kind="src" output="target/test-classes" path="src/test/resources"/>
| <classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/J2SE-1.5"/>
| <classpathentry kind="con" path="org.maven.ide.eclipse.MAVEN2_CLASSPATH_CONTAINER"/>
| <classpathentry kind="output" path="target/classes"/>
| </classpath>
|
in which case eclipse reads the dependencies from the pom.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4238404#4238404
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4238404
16 years, 9 months
[Design of Embedded JBoss] - External Contribution to AS Embedded
by ALRubinger
With the jboss-bootstrap:2.0.0 series now integrated into Branch_5_x, we can start to entertain external contributions as we've got greater focus. I had some conversations over email with Josh Davis, who raised on the dev-list:
http://lists.jboss.org/pipermail/jboss-development/2009-June/014609.html
"Josh Davis" wrote : I'm game for doing some development, or at least seeing if I can deploy my app and run unit tests with a snapshot build and report problems. I've checked out http://anonsvn.jboss.org/repos/jbossas/projects/embedded/trunk, but I think I need some help getting it to build. I'm not sure which Maven repository I'm supposed to use to get it to build. I'm guessing the instructions for the JBoss AS project don't apply?
You're coming in at a great time, though it might be a bit early if your goals are just to "get things working" for you. The first prototype of the new Embedded stuff I'd committed sometime last week, and it's the most ugly code I've ever put into svn.
Your SVN location is correct, however, we still need to massage this all into some working form. The general idea is:
* Bring in all of the AS Dependencies
* Start up AS by using the bootstrap APIs, and point it at a JBOSS_HOME installed somewhere on your system
* Watch everything break
This is because AS itself still makes a series of assumptions about the runtime environment, and I've been addressing these one-by-one. Not necessarily a wonderful place for a newbie to start (==frustrating AS legacy stuff).
A great place for you to begin would actually be from within the Bootstrap project:
https://jira.jboss.org/jira/browse/JBBOOT
http://anonsvn.jboss.org/repos/jbossas/projects/bootstrap/trunk/
This is the component responsible for obtaining all AS configuration, starting up Microcontainer, pointing it to the root bootstrap XML, and running. It's the thing that AS Main now calls to startup everything.
Would recommend you have a look at some of the open issues in JBBOOT JIRA. The whole project should be fully JavaDoc'd and tested; the unit tests for each projects are meant to be self-documenting as well. You can learn how to setup/start the server, fire lifecycle events, etc.
Real Embedded work that you may dive into is about 1-2 weeks away from now, I'd say. If you wanna dig into Bootstrap (which is a prereq for learning AS startup anyway), try for patches on some of the easier issues.
As to the Maven repo:
http://www.jboss.org/community/wiki/MavenSettings
It's the same repo as all of JBoss; http://repository.jboss.org/maven2.
These settings upon a fresh checkout of jboss-bootstrap should get you on your way.
S,
ALR
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4238387#4238387
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4238387
16 years, 9 months