[ https://issues.jboss.org/browse/ISPN-1177?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-1177: ----------------------------------- Fix Version/s: 5.0.0.CR7 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/ISPN-1177?page=com.atlassian.jira.plugin.... ] Jeff Ramsdale commented on ISPN-1177: ------------------------------------- I have a simple class with a main method for testing. Currently I'm running with a launch configuration in Eclipse using m2eclipse to resolve my classpath based on my Maven pom. As it turns out I was blocked by https://issues.jboss.org/browse/ISPN-1148 in using CR4, So I built Infinispan from HEAD (29e3ef7df9cfc13a700b16d1a559196f33a3413d). My classpath contains the following (from mvn dependency:list): [INFO] The following files have been resolved: [INFO] cglib:cglib-nodep:jar:2.2:compile [INFO] ch.qos.logback:logback-classic:jar:0.9.28:compile [INFO] ch.qos.logback:logback-core:jar:0.9.28:compile [INFO] commons-pool:commons-pool:jar:1.5.4:compile [INFO] i18nlog:i18nlog:jar:1.0.10:compile [INFO] jline:jline:jar:0.9.94:compile [INFO] net.jini:jsk-dl:jar:2.1:compile [INFO] net.jini:jsk-lib:jar:2.1:compile [INFO] net.jini:jsk-platform:jar:2.1:compile [INFO] net.jini:start:jar:2.1:compile [INFO] net.jini.lookup:jmx-lookup:jar:2.1:compile [INFO] net.jini.lookup:serviceui:jar:2.1:compile [INFO] org.apache.commons:commons-compress:jar:1.0:compile [INFO] org.codehaus.groovy:groovy-all:jar:1.7.0:compile [INFO] org.infinispan:infinispan-client-hotrod:jar:5.0.0-SNAPSHOT:compile [INFO] org.infinispan:infinispan-core:jar:5.0.0-SNAPSHOT:compile [INFO] org.jboss.javaee:jboss-transaction-api:jar:1.0.1.GA:compile [INFO] org.jboss.logging:jboss-logging:jar:3.0.0.Beta5:compile [INFO] org.jboss.marshalling:jboss-marshalling:jar:1.3.0.CR9:compile [INFO] org.jboss.marshalling:jboss-marshalling-river:jar:1.3.0.CR9:compile [INFO] org.jgroups:jgroups:jar:2.12.0.Final:compile [INFO] org.rhq.helpers:rhq-pluginAnnotations:jar:3.0.1:compile [INFO] org.rioproject:boot:jar:4.3-SNAPSHOT:compile [INFO] org.rioproject:rio:jar:4.3-SNAPSHOT:compile [INFO] org.rioproject.substrates.riospan:hotrod-api:jar:1.0.0-SNAPSHOT:compile [INFO] org.rioproject.substrates.riospan:hotrod-proxy:jar:1.0.0-SNAPSHOT:compile [INFO] org.rioproject.substrates.riospan:riospan-api:jar:1.0.0-SNAPSHOT:compile [INFO] org.rioproject.substrates.riospan:riospan-core:jar:1.0.0-SNAPSHOT:compile [INFO] org.slf4j:jcl-over-slf4j:jar:1.6.1:compile [INFO] org.slf4j:jul-to-slf4j:jar:1.6.1:compile [INFO] org.slf4j:log4j-over-slf4j:jar:1.6.1:compile [INFO] org.slf4j:slf4j-api:jar:1.6.1:compile -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/ISPN-1177?page=com.atlassian.jira.plugin.... ] Galder Zamarreño commented on ISPN-1177: ---------------------------------------- @Jeff, I'm closing this for the moment, since it appears to be more of an issue of how you built Infinispan jars rather than a problem with one of the jars we ship. Feel free to re-open if you encounter this issue with a jar we built. If you built it yourself, it'd be interesting to find out why annotation processing didn't work in the build, cos that's creates the implementation that cannot be found. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/ISPN-1177?page=com.atlassian.jira.plugin.... ] Jeff Ramsdale commented on ISPN-1177: ------------------------------------- I was looking for you on IRC yesterday but should have commented here. I have no local changes, so the only variable I can think of is my Maven version. I'm using 2.2.1, but I also have Maven 3.0.3. Is there a Maven 3 dependency? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/ISPN-1177?page=com.atlassian.jira.plugin.... ] Jeff Ramsdale commented on ISPN-1177: ------------------------------------- That seemed to do it--build worked with Maven 3. I would suggest someone else do the experiment to verify my findings? If someone else can show the same thing I can post a Jira ticket, or they can. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/ISPN-1177?page=com.atlassian.jira.plugin.... ] Manik Surtani updated ISPN-1177: -------------------------------- Environment: Maven 2.2.x Workaround Description: Use Maven 3.x Workaround: [Workaround Exists] -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/ISPN-1177?page=com.atlassian.jira.plugin.... ] Manik Surtani resolved ISPN-1177. --------------------------------- Resolution: Won't Fix See workaround -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/ISPN-1177?page=com.atlassian.jira.plugin.... ] Dan Berindei commented on ISPN-1177: ------------------------------------ I'm building Infinispan with Maven 2.2.1 on Fedora 14 and it works fine. I do get the error from time to time when I build from IntelliJ, because the IntelliJ compiler doesn't do annotation processing (or at least I haven't been able to configure it properly). Then when you run 'mvn install' maven sees that the class is up to date and doesn't run annotation processing either. Running 'mvn clean install' usually sorts everything out. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/ISPN-1177?page=com.atlassian.jira.plugin.... ] Galder Zamarreño commented on ISPN-1177: ---------------------------------------- Btw, shouldn't just force Maven 3 for the build? We no longer need to have Infinispan working w/ old AS/EAP 4.x builds which might have had issues with M3. WDYT? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/ISPN-1177?page=com.atlassian.jira.plugin.... ] Dan Berindei commented on ISPN-1177: ------------------------------------ @Galder, I just tried again with Maven 3 and mvn clean + compile with IntelliJ + mvn install gave me this: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.4.3-JBOSS:test (default-test) on project infinispan-core: null; nested exception is java.lang.ExceptionInInitializerError: null: Invalid logger interface org.infinispan.util.logging.Log (implementation not found) -> [Help 1] I don't have any opinion on Maven 3 vs Maven 2, I think we specify the plugin versions in the parent pom anyway so it shouldn't make a big difference. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira