7 Replies Latest reply on Apr 12, 2008 2:00 PM by Andrew Rubinger

    jboss-parent 4-beta-2

    Adrian Brock Master

      I did a new release of jboss parent which will generate release poms during the tagging
      part of the release process.

      I also noticed 4-beta-1 didn't have the correct compiler settings like version 3 had.

        • 1. Re: jboss-parent 4-beta-2
          Ales Justin Master

          This is what I get when running dry release:prepare

          [INFO] Scanning for projects...
           [INFO] NOTE: Using release-pom: C:\projects\microcontainer\mdr\release-pom.xml in reactor build.
           [INFO] ------------------------------------------------------------------------
           [INFO] Building JBoss MetaData Repository
           [INFO] task-segment: [clean, verify]
           [INFO] ------------------------------------------------------------------------
           [INFO] artifact org.apache.maven.plugins:maven-clean-plugin: checking for updates from repository.jboss.org
           [INFO] artifact org.apache.maven.plugins:maven-clean-plugin: checking for updates from snapshots.jboss.org
           [INFO] ------------------------------------------------------------------------
           [ERROR] BUILD ERROR
           [INFO] ------------------------------------------------------------------------
           [INFO] Failed to resolve artifact.
          
           GroupId: org.apache.maven.plugins
           ArtifactId: maven-assembly-plugin
           Version: RELEASE
          
           Reason: Unable to determine the release version
          
           org.apache.maven.plugins:maven-assembly-plugin:pom:RELEASE
          


          There is this line in release-pom.xml:
           <artifactId>maven-assembly-plugin</artifactId>
           <version>RELEASE</version>
          


          • 3. Re: jboss-parent 4-beta-2
            Ales Justin Master

            Now I'm getting compilation error, due to 1.3 jdk usage:

             [ERROR] BUILD FAILURE
             [INFO] ------------------------------------------------------------------------
             [INFO] Compilation failure
            
             C:\projects\microcontainer\mdr\src\main\org\jboss\metadata\spi\retrieval\helper\MetaDataToAnnotationBridge.java:[36,39] generics are not supported in -source 1.3
             (try -source 1.5 to enable generics)
             public class MetaDataToAnnotationBridge<T extends Annotation> implements AnnotationItem<T>
            

            Where is this 1.3 jdk creeping in?

            • 4. Re: jboss-parent 4-beta-2
              Paul Gier Master

              jdk 1.3 is the default that the maven compiler plugin uses if you don't specify anything. I had removed this from the new version of the parent so that projects would have to specify what java version they want to use, but we can add it back if it's better that way.

              • 5. Re: jboss-parent 4-beta-2
                Paul Gier Master

                Here's the relevant configuration for the compiler plugin.

                 <plugins>
                 <plugin>
                 <groupId>org.apache.maven.plugins</groupId>
                 <artifactId>maven-compiler-plugin</artifactId>
                 <configuration>
                 <source>1.5</source>
                 <target>1.5</target>
                 </configuration>
                 </plugin>
                 </plugins>
                


                • 6. Re: jboss-parent 4-beta-2
                  Andrew Rubinger Master

                  We have the compiler plugin correctly set in the EJB3 Build Parent. However, when performing releases, the configuration is not set in the release POM, preventing release (as compilation fails).

                  This is easily tested:

                  mvn -f release-pom.xml clean verify


                  Where you then see:

                  ...generics are not supported in -source 1.3
                   (try -source 1.5 to enable generics)


                  A relevant issue is:

                  http://jira.codehaus.org/browse/MRELEASE-283

                  ...but I don't find the "inherited" property noted in te above JIRA having any bearing on the result.

                  So for now, I cannot use jboss-parent:4-beta-2

                  S,
                  ALR

                  • 7. Re: jboss-parent 4-beta-2
                    Andrew Rubinger Master

                     

                    "ALRubinger" wrote:
                    A relevant issue is:

                    http://jira.codehaus.org/browse/MRELEASE-283

                    ...but I don't find the "inherited" property noted in te above JIRA having any bearing on the result.


                    The difference between my use case and that JIRA appears to be that our plugin configuration is defined in a parent, not the project proper.

                    This would explain how Ales was able to push through with the last MC release.

                    S,
                    ALR