That did it! The ordering of the dependencies made the difference. (I learn something new everyday :) Thanks
On Sat, Mar 3, 2012 at 8:49 AM, Frank Fock <[email protected]> wrote: > Hi, > > I am not sure what could be causing the specific error you > are getting below, but an important detail to keep in mind > is the following: > > In the agenpro-mvn-task\pom.xml the order of dependencies > has to be changed, if you use newer versions of SNMP4J > or SNMP4J-Agent than those that came with your AgenPro > release. Thus, in general it is better to change the order > as follows: > > <dependencies> > <dependency> > <groupId>org.snmp4j</groupId> > <artifactId>snmp4j</artifactId> > <version>2.0.3</version> > </dependency> > <dependency> > <groupId>org.snmp4j</groupId> > <artifactId>snmp4j-agent</artifactId> > <version>2.0.5</version> > </dependency> > <dependency> > <groupId>com.oosnmp.agenpro.maven.plugins</groupId> > <artifactId>agenpro-plugin</artifactId> > <version>3.1.2</version> > <scope>provided</scope> > </dependency> > </dependencies> > > I will update the pom.xml for the next plugin release (coming up soon). > > Best regards, > Frank > > > Am 03.03.2012 03:58, schrieb agenpro log4j: > > In case anyone can easily see what i am doing wrong, i am getting > > "cannot find symbol" using the agenpro-mvn-task\pom.xml : > > > > ...oosnmp\agenpro\Agent.java:[186,20] cannot find symbol > > symbol : constructor > > DefaultMOQuery(org.snmp4j.agent.DefaultMOContextScope,bool > > ean,com.oosnmp.agenpro.Agent) > > > > usually i thought the<dependencies> in pom.xml automate into class paths > > when compiling the generated files with Agent.java, to resolve symbols > from > > jar files. > > > > Are others getting the example pom.xml (with version fixes) working? Or > is > > it easier to try a different way to build an Agent from files generated > > from agenpro3? > > > _______________________________________________ SNMP4J mailing list [email protected] http://lists.agentpp.org/mailman/listinfo/snmp4j
