[jira] [Commented] (FELIX-4479) wrong MANIFEST.MF ends up in jar bundle file sometimes
[ https://issues.apache.org/jira/browse/FELIX-4479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13962646#comment-13962646 ] Bertrand Delacretaz commented on FELIX-4479: I think this is related to MIME4J-231 which has more details. wrong MANIFEST.MF ends up in jar bundle file sometimes -- Key: FELIX-4479 URL: https://issues.apache.org/jira/browse/FELIX-4479 Project: Felix Issue Type: Bug Components: Maven Bundle Plugin Affects Versions: maven-bundle-plugin-2.4.0 Reporter: Mark Priority: Blocker Fetch the sources from http://svn.apache.org/repos/asf/james/server/trunk/ and enter mvn clean install. At the end, there will be a few karaf integration tests that may sometimes fail because of a Bundle-SymbolicName missing error. It is pretty much random and my best guess is that after the MANIFEST.MF modification by the plugin, the file handle is not closed properly, the data is not flushed to disk properly etc. because the maven debug output tells me that the change is recognized and the MANIFEST.MF included in the jar after it has been updated by maven-bundle-plugin. But still, the old non-OSGi version ends up in the jar file sometimes. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (FELIX-4479) wrong MANIFEST.MF ends up in jar bundle file sometimes
[ https://issues.apache.org/jira/browse/FELIX-4479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13963137#comment-13963137 ] Mark commented on FELIX-4479: - Any simple solutions? wrong MANIFEST.MF ends up in jar bundle file sometimes -- Key: FELIX-4479 URL: https://issues.apache.org/jira/browse/FELIX-4479 Project: Felix Issue Type: Bug Components: Maven Bundle Plugin Affects Versions: maven-bundle-plugin-2.4.0 Reporter: Mark Priority: Blocker Fetch the sources from http://svn.apache.org/repos/asf/james/server/trunk/ and enter mvn clean install. At the end, there will be a few karaf integration tests that may sometimes fail because of a Bundle-SymbolicName missing error. It is pretty much random and my best guess is that after the MANIFEST.MF modification by the plugin, the file handle is not closed properly, the data is not flushed to disk properly etc. because the maven debug output tells me that the change is recognized and the MANIFEST.MF included in the jar after it has been updated by maven-bundle-plugin. But still, the old non-OSGi version ends up in the jar file sometimes. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (FELIX-4479) wrong MANIFEST.MF ends up in jar bundle file sometimes
[ https://issues.apache.org/jira/browse/FELIX-4479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13963150#comment-13963150 ] Mark commented on FELIX-4479: - I'll try useDefaultManifestFiletrue/useDefaultManifestFile. wrong MANIFEST.MF ends up in jar bundle file sometimes -- Key: FELIX-4479 URL: https://issues.apache.org/jira/browse/FELIX-4479 Project: Felix Issue Type: Bug Components: Maven Bundle Plugin Affects Versions: maven-bundle-plugin-2.4.0 Reporter: Mark Priority: Blocker Fetch the sources from http://svn.apache.org/repos/asf/james/server/trunk/ and enter mvn clean install. At the end, there will be a few karaf integration tests that may sometimes fail because of a Bundle-SymbolicName missing error. It is pretty much random and my best guess is that after the MANIFEST.MF modification by the plugin, the file handle is not closed properly, the data is not flushed to disk properly etc. because the maven debug output tells me that the change is recognized and the MANIFEST.MF included in the jar after it has been updated by maven-bundle-plugin. But still, the old non-OSGi version ends up in the jar file sometimes. [DEBUG] Final Manifest: #--- Manifest-Version: 1.0 Bnd-LastModified: 1396933143961 Build-Jdk: 1.7.0_51 Built-By: jenkins Bundle-Description: Apache James Mail Server Bundle-DocURL: http://www.apache.org/ Bundle-License: http://www.apache.org/licenses/LICENSE-2.0.txt Bundle-ManifestVersion: 2 Bundle-Name: Apache James :: Server :: Mailetcontainer API Bundle-SymbolicName: org.apache.james.server-mailetcontainer-api Bundle-Vendor: The Apache Software Foundation Bundle-Version: 3.0.0.beta5-SNAPSHOT Created-By: Apache Maven Bundle Plugin Export-Package: org.apache.james.mailetcontainer.api;uses:=javax.mail,o rg.apache.mailet;version=3.0.0.beta5-SNAPSHOT,org.apache.james.maile tcontainer.api.jmx;version=3.0.0.beta5-SNAPSHOT Implementation-Title: Apache James :: Server :: Mailetcontainer API Implementation-Vendor: The Apache Software Foundation Implementation-Vendor-Id: org.apache.james Implementation-Version: 3.0.0-beta5-SNAPSHOT Import-Package: javax.mail;version=[1.4,2),org.apache.mailet;version= [2.5,3) Specification-Title: Apache James :: Server :: Mailetcontainer API Specification-Vendor: The Apache Software Foundation Specification-Version: 3.0.0-beta5-SNAPSHOT Tool: Bnd-1.50.0 #--- [INFO] [INFO] --- maven-jar-plugin:2.4:jar (jar) @ james-server-mailetcontainer-api --- [DEBUG] isUp2date: false (Resource with newer modification date found.) [INFO] Building jar: /var/lib/jenkins/jobs/james-server-mark/workspace/mailet/mailetcontainer-api/target/james-server-mailetcontainer-api-3.0.0-beta5-SNAPSHOT.jar [DEBUG] adding directory META-INF/ [DEBUG] adding entry META-INF/MANIFEST.MF [DEBUG] adding directory org/ [DEBUG] adding directory org/apache/ [DEBUG] adding directory org/apache/james/ [DEBUG] adding directory org/apache/james/mailetcontainer/ [DEBUG] adding directory org/apache/james/mailetcontainer/api/ [DEBUG] adding directory org/apache/james/mailetcontainer/api/jmx/ [DEBUG] adding entry org/apache/james/mailetcontainer/api/MailetLoader.class [DEBUG] adding entry org/apache/james/mailetcontainer/api/MatcherLoader.class [DEBUG] adding entry org/apache/james/mailetcontainer/api/MailProcessor.class [DEBUG] adding entry org/apache/james/mailetcontainer/api/jmx/MailProcessorManagementMBean.class [DEBUG] adding entry org/apache/james/mailetcontainer/api/jmx/MailSpoolerMBean.class [DEBUG] adding entry org/apache/james/mailetcontainer/api/jmx/MatcherManagementMBean.class [DEBUG] adding entry org/apache/james/mailetcontainer/api/jmx/MailetManagementMBean.class [DEBUG] adding entry META-INF/NOTICE [DEBUG] adding entry META-INF/DEPENDENCIES [DEBUG] adding entry META-INF/LICENSE [DEBUG] adding entry mailetcontainer.xml [DEBUG] adding directory META-INF/maven/ [DEBUG] adding directory META-INF/maven/org.apache.james/ [DEBUG] adding directory META-INF/maven/org.apache.james/james-server-mailetcontainer-api/ [DEBUG] adding entry META-INF/maven/org.apache.james/james-server-mailetcontainer-api/pom.xml [DEBUG] adding entry META-INF/maven/org.apache.james/james-server-mailetcontainer-api/pom.properties -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (FELIX-4479) wrong MANIFEST.MF ends up in jar bundle file sometimes
[ https://issues.apache.org/jira/browse/FELIX-4479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13963195#comment-13963195 ] Mark commented on FELIX-4479: - Looks like that worked. Thx. wrong MANIFEST.MF ends up in jar bundle file sometimes -- Key: FELIX-4479 URL: https://issues.apache.org/jira/browse/FELIX-4479 Project: Felix Issue Type: Bug Components: Maven Bundle Plugin Affects Versions: maven-bundle-plugin-2.4.0 Reporter: Mark Priority: Blocker Fetch the sources from http://svn.apache.org/repos/asf/james/server/trunk/ and enter mvn clean install. At the end, there will be a few karaf integration tests that may sometimes fail because of a Bundle-SymbolicName missing error. It is pretty much random and my best guess is that after the MANIFEST.MF modification by the plugin, the file handle is not closed properly, the data is not flushed to disk properly etc. because the maven debug output tells me that the change is recognized and the MANIFEST.MF included in the jar after it has been updated by maven-bundle-plugin. But still, the old non-OSGi version ends up in the jar file sometimes. [DEBUG] Final Manifest: #--- Manifest-Version: 1.0 Bnd-LastModified: 1396933143961 Build-Jdk: 1.7.0_51 Built-By: jenkins Bundle-Description: Apache James Mail Server Bundle-DocURL: http://www.apache.org/ Bundle-License: http://www.apache.org/licenses/LICENSE-2.0.txt Bundle-ManifestVersion: 2 Bundle-Name: Apache James :: Server :: Mailetcontainer API Bundle-SymbolicName: org.apache.james.server-mailetcontainer-api Bundle-Vendor: The Apache Software Foundation Bundle-Version: 3.0.0.beta5-SNAPSHOT Created-By: Apache Maven Bundle Plugin Export-Package: org.apache.james.mailetcontainer.api;uses:=javax.mail,o rg.apache.mailet;version=3.0.0.beta5-SNAPSHOT,org.apache.james.maile tcontainer.api.jmx;version=3.0.0.beta5-SNAPSHOT Implementation-Title: Apache James :: Server :: Mailetcontainer API Implementation-Vendor: The Apache Software Foundation Implementation-Vendor-Id: org.apache.james Implementation-Version: 3.0.0-beta5-SNAPSHOT Import-Package: javax.mail;version=[1.4,2),org.apache.mailet;version= [2.5,3) Specification-Title: Apache James :: Server :: Mailetcontainer API Specification-Vendor: The Apache Software Foundation Specification-Version: 3.0.0-beta5-SNAPSHOT Tool: Bnd-1.50.0 #--- [INFO] [INFO] --- maven-jar-plugin:2.4:jar (jar) @ james-server-mailetcontainer-api --- [DEBUG] isUp2date: false (Resource with newer modification date found.) [INFO] Building jar: /var/lib/jenkins/jobs/james-server-mark/workspace/mailet/mailetcontainer-api/target/james-server-mailetcontainer-api-3.0.0-beta5-SNAPSHOT.jar [DEBUG] adding directory META-INF/ [DEBUG] adding entry META-INF/MANIFEST.MF [DEBUG] adding directory org/ [DEBUG] adding directory org/apache/ [DEBUG] adding directory org/apache/james/ [DEBUG] adding directory org/apache/james/mailetcontainer/ [DEBUG] adding directory org/apache/james/mailetcontainer/api/ [DEBUG] adding directory org/apache/james/mailetcontainer/api/jmx/ [DEBUG] adding entry org/apache/james/mailetcontainer/api/MailetLoader.class [DEBUG] adding entry org/apache/james/mailetcontainer/api/MatcherLoader.class [DEBUG] adding entry org/apache/james/mailetcontainer/api/MailProcessor.class [DEBUG] adding entry org/apache/james/mailetcontainer/api/jmx/MailProcessorManagementMBean.class [DEBUG] adding entry org/apache/james/mailetcontainer/api/jmx/MailSpoolerMBean.class [DEBUG] adding entry org/apache/james/mailetcontainer/api/jmx/MatcherManagementMBean.class [DEBUG] adding entry org/apache/james/mailetcontainer/api/jmx/MailetManagementMBean.class [DEBUG] adding entry META-INF/NOTICE [DEBUG] adding entry META-INF/DEPENDENCIES [DEBUG] adding entry META-INF/LICENSE [DEBUG] adding entry mailetcontainer.xml [DEBUG] adding directory META-INF/maven/ [DEBUG] adding directory META-INF/maven/org.apache.james/ [DEBUG] adding directory META-INF/maven/org.apache.james/james-server-mailetcontainer-api/ [DEBUG] adding entry META-INF/maven/org.apache.james/james-server-mailetcontainer-api/pom.xml [DEBUG] adding entry META-INF/maven/org.apache.james/james-server-mailetcontainer-api/pom.properties -- This message was sent by Atlassian JIRA (v6.2#6252)
