• Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • maven-plugin
    • None

      I recently upgraded from Hudson to Jenkins and found that the Manifest file in my jars no longer have the build/version related information in them.

      Contents of manifest file with hudson that are missing after upgrading to Jenkins
      ...
      Hudson-Build-Number: 11
      Hudson-Project: XXXX
      Hudson-Version: 1.357

          [JENKINS-11784] Build numbers not getting into manifest file

          Peter Hayes added a comment -

          I see this as well, but it is when I changed my Jenkins Maven job to use Maven 3 instead of Maven 2.

          Peter Hayes added a comment - I see this as well, but it is when I changed my Jenkins Maven job to use Maven 3 instead of Maven 2.

          Right, it could very well be that to. We recently updated our projects to use maven 3.

          vinod mahalingam added a comment - Right, it could very well be that to. We recently updated our projects to use maven 3.

          Oded Maimon added a comment -

          Actually this is something that i would be very happy if it was configurable.
          i for instant don't wish jenkins to add the manifest data, it makes each build artifact to have different md5sum even if the code wasn't changed.

          Oded Maimon added a comment - Actually this is something that i would be very happy if it was configurable. i for instant don't wish jenkins to add the manifest data, it makes each build artifact to have different md5sum even if the code wasn't changed.

          persyval added a comment -

          We have the same problem after upgrading to maven 3.
          Would love to see this issue fixed.

          persyval added a comment - We have the same problem after upgrading to maven 3. Would love to see this issue fixed.

          Daniel Beck added a comment -

          Seems related to Maven project plugin rather than core (which only provides the 'Top-level Maven targets' build step)

          Daniel Beck added a comment - Seems related to Maven project plugin rather than core (which only provides the 'Top-level Maven targets' build step)

          Cristiano Fontes added a comment - - edited

          Having the same problem, it worked with maven 3.0.5 and this in my POM

                                 <plugin>
          				<groupId>org.apache.maven.plugins</groupId>
          				<artifactId>maven-jar-plugin</artifactId>
          				<configuration>
          					<archive>
          						<manifestEntries>
          							<Svn-Revision>${SVN_REVISION}</Svn-Revision>
          							<Build-Tag>${BUILD_TAG}</Build-Tag>
          							<Build-Number>${BUILD_NUMBER}</Build-Number>
          							<Build-Id>${BUILD_ID}</Build-Id>
          							<Build-Time>${timestamp}</Build-Time>
          						</manifestEntries>
          					</archive>
          				</configuration>
          			</plugin>
          

          Now, Jenkins 1.643 and maven 3.3.9 it only updates the timestamp

          Cristiano Fontes added a comment - - edited Having the same problem, it worked with maven 3.0.5 and this in my POM <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-jar-plugin</artifactId> <configuration> <archive> <manifestEntries> <Svn-Revision>${SVN_REVISION}</Svn-Revision> <Build-Tag>${BUILD_TAG}</Build-Tag> <Build-Number>${BUILD_NUMBER}</Build-Number> <Build-Id>${BUILD_ID}</Build-Id> <Build-Time>${timestamp}</Build-Time> </manifestEntries> </archive> </configuration> </plugin> Now, Jenkins 1.643 and maven 3.3.9 it only updates the timestamp

            Unassigned Unassigned
            vinzy vinod mahalingam
            Votes:
            7 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated: