1 2 3 Previous Next 42 Replies Latest reply on Apr 12, 2013 2:50 AM by henk53 Go to original post
      • 30. Re: I lost the 7.2
        ctomc
        Does anybody know where I can find the documentation on how to bump the version numbers in an automated way? (And does that documentation include the missed places?)

        Usualy this is done by maven release plugin. and it is automated, that is why it misses non pom changes...

        • 31. Re: I lost the 7.2
          b.eckenfels

          Hello,

           

          There are some more -SNAPSHOT mentioned (in assembly plugin xml namespace and readme), I will prepare a pull request for AS 8 for that.

           

          Done here:

           

           

          There is also a bug in the assembly descriptor in regards of the file permissions of the standalone/tmp/auth directory. Jira: AS7-6848

           

          Message was edited by: Bernd Eckenfels added Jira url

          • 32. Re: I lost the 7.2
            tomeicher

            Tomaz, thanks, disabling the tests worked, I now have a binary !

             

            Should we not have a 7.2.0.Final2 tag in git, where this problem is resolved ?

            (I release "Final2" is an oxymoron. But a non-building Final is even more so...)

             

            (Putting a feature request for this would be a waste of time, right ? ;-/

             

            Bernd, you mentioned a permission problem with the build target (in another thread). Will this affect me having built with -DskipTests ?

            • 33. Re: I lost the 7.2
              b.eckenfels

              Hello Tom,

               

              yes the 7.2.0.Final (build with no tests or with the testfix from my Branch) will create a distribution tar.gz with wrong directory permissions for standalone/tmp/auth. However this can be easily fixed after unpacking/installing.

               

              If you dont use standalone mode or if you do not have untrusted local users then it wont be a problem. Also I think for Windows you would have to fix/restrict file permissions manually anyway. (I think this is even mentioned somewhere in the documentation).

               

              Bernd

              • 34. Re: I lost the 7.2
                jaikiran

                Tom Eicher wrote:

                 

                except that 7.2.0.Final from github does not build out-of-the-box :-(

                 

                java.lang.RuntimeException: org.sonatype.aether.resolution.ArtifactResolutionException: Could not find artifact org.jboss.as:jboss-as-core-model-test-framework:jar:7.2.0.Alpha1-SNAPSHOT in jboss-developer (http://repository.jboss.org/nexus/content/groups/developer/)

                        at org.jboss.as.model.test.MavenUtil.createMavenGavURL(MavenUtil.java:112)

                        at org.jboss.as.model.test.ChildFirstClassLoaderBuilder.addMavenResourceURL(ChildFirstClassLoaderBuilder.java:79)

                        at org.jboss.as.core.model.test.CoreModelTestDelegate$LegacyKernelServicesInitializerImpl.install(CoreModelTestDelegate.java:553)

                        at org.jboss.as.core.model.test.CoreModelTestDelegate$LegacyKernelServicesInitializerImpl.access$300(CoreModelTestDelegate.java:526)

                        at org.jboss.as.core.model.test.CoreModelTestDelegate$KernelServicesBuilderImpl.build(CoreModelTestDelegate.java:493)

                        at org.jboss.as.core.model.test.deploymentoverlay.DomainDeploymentOverlayTransformersTestCase.testDeploymentOverlaysTransformer_7_1_x(DomainDeploymentOverlayTransformersTestCase.java:220)

                        at org.jboss.as.core.model.test.deploymentoverlay.DomainDeploymentOverlayTransformersTestCase.testDeploymentOverlaysTransformer(DomainDeploymentOverlayTransformersTestCase.java:82)

                Can some of you who have been running into this issue, please try building this branch (preferably against a clean maven repo) https://github.com/jaikiran/jboss-as/tree/7.2.0.Final-testsuite-fix. Let us know if that builds clean, we plan to push that testsuite fix to a new tag so that the (new) 7.2.0.Final-testsuite-fix tag is buildable without testsuite failures.

                • 35. Re: I lost the 7.2
                  tomeicher

                  Yes, the testsuite-fix builds successful :-) Great!

                  • 36. Re: I lost the 7.2
                    b.eckenfels

                    I tried your branch (each time with empty local repository) with -P release and with default/normal profile on Win7 with 64bit JDK1.7.0_11 and in both cases it suceeded to build and finish the (default) tests.

                     

                    C:\ws\jboss-as\> \apache-maven-3.0.4\bin\mvn -s \empty.xml -C -ff -Prelease install

                    C:\ws\jboss-as\> \apache-maven-3.0.4\bin\mvn -s \empty.xml -C -ff install

                     

                    I had a different fix, blindly using VERSION in the dynamic artifact names (https://github.com/ecki/jboss-as/commit/6cc16c02faf338936f0f49f7f57c6e8d1d87e97a). Do you have an idea where that VERSION was actually coming from - as it worked as well, at least for 7.2.0 with maven (not tested IDE).

                    • 37. Re: I lost the 7.2
                      jaikiran

                      Thank you for building and testing it. upstream now has a new tag which has the testsuite fix https://github.com/jbossas/jboss-as/tree/7.2.0.Final-testsuite-fix

                      • 38. Re: I lost the 7.2
                        jaikiran

                        Bernd Eckenfels wrote:

                         

                        Do you have an idea where that VERSION was actually coming from - as it worked as well, at least for 7.2.0 with maven (not tested IDE).

                        Bernd, sorry I don't understand what you are asking here. Are you asking where the 7.2.0.Final maven artifact comes from?

                        • 39. Re: I lost the 7.2
                          henk53

                          Something else that I'm curious about: will JBoss now only work towards releasing JBoss EAP 6.1, or will we still see a JBoss EAP 6.0.2 (based on an imaginary JBoss AS 7.1.4) that was planned earlier?

                           

                          As I understood the work being done correctly, before there was a branch for work on AS 7.1.4/EAP 6.0.2, and the alpha branch for AS 7.2 which was then released as EAP 6.1alpha. EAP 6.0.2 never got released, but is it still planned?

                          • 40. Re: I lost the 7.2
                            ctomc

                            henk de boer wrote:

                             

                            Something else that I'm curious about: will JBoss now only work towards releasing JBoss EAP 6.1, or will we still see a JBoss EAP 6.0.2 (based on an imaginary JBoss AS 7.1.4) that was planned earlier?

                             

                            As I understood the work being done correctly, before there was a branch for work on AS 7.1.4/EAP 6.0.2, and the alpha branch for AS 7.2 which was then released as EAP 6.1alpha. EAP 6.0.2 never got released, but is it still planned?

                            Current work is now split in two, releasing EAP 6.1 GA and working new features for AS8.

                             

                            As for 6.0.2 goes it might happen and if it does it would be from 7.1 branch (currently at 7.1.4-SNAPSHOST).

                            I cannot confirm or deny it as it is not up to developers to decide this , also in my opinion 6.1 that is coming out will have all the fixes from 6.0.x and more so there is no real need for micro release only with few patches.

                            6.1 is/will be fully backward compatible with 6.0 so there should be no reason not to upgrade to 6.1.

                             

                            --

                            tomaz

                            • 41. Re: I lost the 7.2
                              nickarls

                              I cannot confirm or deny it as it is not up to developers to decide this , also in my opinion 6.1 that is coming out will have all the fixes from 6.0.x and more so there is no real need for micro release only with few patches.

                              6.1 is/will be fully backward compatible with 6.0 so there should be no reason not to upgrade to 6.1.

                               

                              Our customers who use Oracle/WebLogic are usually a bit sceptic the first time I ask If I can upgrade our JBoss AS and I tell them it takes about 5 minutes (and if something goes wrong I can rollback in a few minutes, too).

                              They are used to full backups + one day of patching or installing

                              • 42. Re: I lost the 7.2
                                henk53

                                Tomaz Cerar wrote:

                                 

                                Current work is now split in two, releasing EAP 6.1 GA and working new features for AS8.

                                 

                                As for 6.0.2 goes it might happen and if it does it would be from 7.1 branch (currently at 7.1.4-SNAPSHOST).

                                 

                                Thanks for the answer! I guess we'll see what happens then. A 6.0.2 might have value in that it may *feel* as being more stable than a 6.1.0, which also has some new features which might take some time to stabalize. Whether that's actually true is another thing of course

                                1 2 3 Previous Next