1 2 Previous Next 26 Replies Latest reply on Sep 7, 2007 11:26 AM by Scott Stark

    mc release prep

    Scott Stark Master

      In preparation for the mc release I'm going to update jboss5 trunk to use the current mc snapshot. This also requires an update of the jboss-common-core to the 2.2.1-SNAPSHOT. Both the mc and jboss-common-core will need to be released once the testsuite and cts are verified.

        • 1. Re: mc release prep
          Scott Stark Master

          I'll be looking to do the mc release tomorrow after validating the ManagedOperation behavior.

          • 2. Re: mc release prep
            Scott Stark Master

            I just copied the current trunk into the https://svn.jboss.org/repos/jbossas/projects/microcontainer/branches/2_0/ branch in prep for the beta4 release.

            • 3. Re: mc release prep
              Scott Stark Master

              There are several snapshot dependencies that need to be cleaned up to do the mc release. One is the integration project spis.

               <plugin>
               <groupId>jboss.maven-plugins</groupId>
               <artifactId>jboss-deploy-maven-plugin</artifactId>
               <version>1.3-SNAPSHOT</version>
               </plugin>
              ...
              [INFO] Can't release project due to non released dependencies :
               jboss.maven-plugins:jboss-deploy-maven-plugin:maven-plugin:1.3-SNAPSHOT:runtime
              in project 'JBoss Integration 5.0 Build' (org.jboss:jboss-integration:pom:5.0.0-SNAPSHOT)
              

              The mc uses version 1.3 which I assume will be fine. Was there a need for this to use the snapshot plugin?


              • 4. Re: mc release prep
                Scott Stark Master

                The integration project does not appear to be setup correctly to release. If I try to prepare the jboss-classloading-spi release, its failing because it expects a tags dir under /repos/jbossas/projects/integration/jboss-classloading-spi/tags:

                The svn tag command failed.
                Command output:
                svn: Commit failed (details follow):
                svn: PROPFIND request failed on '/repos/jbossas/projects/integration/jboss-classloading-spi/tags'
                svn: '/repos/jbossas/projects/integration/jboss-classloading-spi/tags' path not found
                


                Is this project going to have separate pieces like the common project with a trunks dir to pull together the various integration project trunks?


                • 5. Re: mc release prep
                  Adrian Brock Master

                  I copied the structure from the javaee project,
                  the idea being that JBossAS will consume the assembly, but other projects
                  can consume only the pieces they need.

                  I'd guess that we should really tag the integration or javaee project as a whole.
                  e.g. for javaee there is a javax.jms:1.1 but obviously the real version is more like
                  org.jboss.javaee:5.0

                  • 6. Re: mc release prep
                    Scott Stark Master

                    Ok, then non-snapshot releases of javaee, and integration are needed to do the mc release. I have asked Kabir to do an aop release as well.

                    There seems to be a circular reference between javaee and integration as javaee depends on integration/jboss-transaction-api and integration/jboss-transaction-api depends on javaee/jboss-jca.

                    javaee should just be the ee interfaces should it not?

                    • 7. Re: mc release prep
                      Scott Stark Master

                      Nevermind. I was confusing jboss-transaction-api with jboss-transaction-spi.

                      • 8. Re: mc release prep
                        Adrian Brock Master

                        I think you're confusing?

                        transaction-api == javax.transaction
                        with
                        transaction-spi == org.jboss.tm

                        transaction-spi obviously depends on transaction-api
                        but it also defines an extension to jca's XATerminator.

                        • 9. Re: mc release prep
                          Scott Stark Master

                          There is quite the torturous dependency graph in getting rid of the snapshots for the mc release. aop depends on jboss-container, so that need to be released to do the aop release.

                          I'm working on getting non-snapshot releases of:

                          jboss-common 2.2.1.GA (done)
                          jboss-vfs 2.0.0.Beta4 (done)
                          jboss-test 1.0.4.GA (done)
                          javaee 5.0.0.Beta3 (done, and used by jboss5)
                          integration 5.0.0.Beta3 (done, and used by jboss5)
                          jboss-container 2.0.0.Beta4
                          jboss.aop 2.0.0.alpha6 Kabir, https://svn.jboss.org/repos/jbossas/projects/aop/tags/JBoss_AOP_2_0_0_alpha6/aop)

                          • 10. Re: mc release prep
                            Scott Stark Master

                            So there is a circular dependencies between mc and aop at least in terms of how the mc is now setup as an assembly type of project. If I try to release jboss-container, it depends on the parent jboss-microcontainer from build/pom.xml and does not have a container/{trunk,tags} structure for an individual release.

                            aop depends on jboss-container. I can manually release jboss-container, but how should these projects bet setup so that the mvn release process works for such interdependent projects?

                            • 11. Re: mc release prep
                              Scott Stark Master

                              The aop 2.0.0.alpha6 and mc 2.0.0.Beta4 release are ready, but there is a temp AspectDeployer that is broken. I assume this is due to the class loading being in flux. I have commented out the JBossScopedClassLoaderHelper usage.

                               [javac] Compiling 43 source files to /home/svn/JBossHead/jboss-head/system/output/classes
                              /home/svn/JBossHead/jboss-head/system/src/main/org/jboss/aop/deployers/temp/AspectDeployer.java:36: package org.jboss.aop.deployment does not exist
                              import org.jboss.aop.deployment.JBossScopedClassLoaderHelper;
                               ^
                              /home/svn/JBossHead/jboss-head/system/src/main/org/jboss/aop/deployers/temp/AspectDeployer.java:39: warning: [deprecation] org.jboss.deployers.vfs.spi.deployer.AbstractVFSRealDeployer in org.jboss.deployers.vfs.spi.deployer has been deprecated
                              import org.jboss.deployers.vfs.spi.deployer.AbstractVFSRealDeployer;
                               ^
                              /home/svn/JBossHead/jboss-head/system/src/main/org/jboss/aop/deployers/temp/AspectDeployer.java:56: warning: [deprecation] org.jboss.deployers.vfs.spi.deployer.AbstractVFSRealDeployer in org.jboss.deployers.vfs.spi.deployer has been deprecated
                              public class AspectDeployer extends AbstractVFSRealDeployer
                               ^
                              /home/svn/JBossHead/jboss-head/system/src/main/org/jboss/aop/deployers/temp/AspectDeployer.java:368: cannot find symbol
                              symbol : variable JBossScopedClassLoaderHelper
                              location: class org.jboss.aop.deployers.temp.AspectDeployer
                               if (JBossScopedClassLoaderHelper.isScopedClassLoader(unit.getClassLoader()))
                               ^
                              2 errors
                              2 warnings
                              



                              • 12. Re: mc release prep
                                Scott Stark Master

                                The basic mc 2.0.0.Beta4 is released and is now used by jboss5. The aggregate assembly seems broken so I don't know if we are putting out a standalone release as well.

                                • 13. Re: mc release prep
                                  Adrian Brock Master

                                   

                                  "scott.stark@jboss.org" wrote:
                                  So there is a circular dependencies between mc and aop at least in terms of how the mc is now setup as an assembly type of project. If I try to release jboss-container, it depends on the parent jboss-microcontainer from build/pom.xml and does not have a container/{trunk,tags} structure for an individual release.

                                  aop depends on jboss-container. I can manually release jboss-container, but how should these projects bet setup so that the mvn release process works for such interdependent projects?


                                  Like I said before. The container project (and the classloader project)
                                  shouldn't be in the MC build. They are only there because the MC was initially
                                  the major consumer while we developed them.

                                  • 14. Re: mc release prep
                                    Adrian Brock Master

                                     

                                    "scott.stark@jboss.org" wrote:
                                    The aop 2.0.0.alpha6 and mc 2.0.0.Beta4 release are ready, but there is a temp AspectDeployer that is broken. I assume this is due to the class loading being in flux. I have commented out the JBossScopedClassLoaderHelper usage.


                                    The latest version of AOP contains an updated AspectDeployer in the
                                    asintegration project. The temp version in "system" is then redundant and should
                                    be deleted with the configuration changed in the bootstrap-beans.xml, etc.


                                    1 2 Previous Next