« Return to Thread: Profiler uses compile classpath instead of runtime classpath
AW: Profiler uses compile classpath instead of runtime classpath
by Mohni, Daniel
::
Rate this Message:
I now changed the plugin Version in nbactions.xml to 1.1-beta-1 and now it works..
Thanks
Daniel
> -----Ursprüngliche Nachricht-----
> Von: Milos Kleint [mailto:mkleint@...]
> Gesendet: Dienstag, 19. August 2008 10:38
> An: user@...
> Betreff: Re: [mevenide-user] Profiler uses compile classpath instead of runtime
> classpath
>
> I see, you nailed the problem I think.
>
> I've checked the codebase and the current default mappings for
> debug/run/profile all use version 1.1. So the 1.1-beta-1 has to be
> coming from your nbactions.xml file as you edited the project
> configuration in the project properties dialog a while ago.
> the default mappings upgraded since, but the custom ones didn't.
> I guess the run/debug actions will start failing once you change the
> mapping to 1.1 as well. The "fix" could be to make the profile action
> to use 1.1-beta-1 as well.
>
> On a more general level, I'm not very happy with the way changes in
> action mapping configuration get dumped to the nbactions.xml file, but
> so far I didn't have time to look into it. specifically I imagine the
> correct behaviour would be that debug and profile actions by default
> inherit the custom settings from run and just add the debug/profile
> specifics..
>
>
> Milos
>
> Milos
>
> On Tue, Aug 19, 2008 at 10:21 AM, Mohni, Daniel
> <daniel.mohni@...> wrote:
> > Hi Milos
> >
> > I tried again with the mysql connector as runtime lib
> >
> > Debug: OK
> > Run: OK
> > Profile: NOK
> >
> > the driver is not in the classpath
> >
> > [ERROR]The following mojo encountered an error while executing:
> > [ERROR]Group-Id: org.codehaus.mojo
> > [ERROR]Artifact-Id: exec-maven-plugin
> > [ERROR]Version: 1.1
> > [ERROR]Mojo: exec
> > [ERROR]brought in via: Direct invocation
> > [ERROR]While building project:
> > [ERROR]Group-Id: net.mohni
> > [ERROR]Artifact-Id: JBallTimer
> > [ERROR]Version: 1.0-SNAPSHOT
> > [ERROR]From file: C:\Development\workDir\JBallTimer\pom.xml
> > [ERROR]Reason: Result of cmd.exe /X /C ""C:\Program
> Files\Java\jdk1.6.0_07\bin\java.exe" -XX:+HeapDumpOnOutOfMemoryError -
> XX:HeapDumpPath=C:DevelopmentworkDirJBallTimernbprojectprivateprofiler -
> agentpath:D:/ide/netbeans/nb65b/ide/profiler3/lib/deployed/jdk16/windows/profileri
> nterface.dll=D:/ide/netbeans/nb65b/ide/profiler3/lib,5140,10 -classpath
> C:\Development\workDir\JBallTimer\target\classes;D:\mvnrepo\org\hibernate\hibernat
> e-entitymanager\3.3.2.GA\hibernate-entitymanager-
> 3.3.2.GA.jar;D:\mvnrepo\org\hibernate\hibernate\3.2.6.ga\hibernate-
> 3.2.6.ga.jar;D:\mvnrepo\net\sf\ehcache\ehcache\1.2.3\ehcache-
> 1.2.3.jar;D:\mvnrepo\commons-logging\commons-logging\1.0.4\commons-logging-
> 1.0.4.jar;D:\mvnrepo\commons-collections\commons-collections\2.1.1\commons-
> collections-2.1.1.jar;D:\mvnrepo\javax\transaction\jta\1.0.1B\jta-
> 1.0.1B.jar;D:\mvnrepo\asm\asm-attrs\1.5.3\asm-attrs-
> 1.5.3.jar;D:\mvnrepo\dom4j\dom4j\1.6.1\dom4j-
> 1.6.1.jar;D:\mvnrepo\antlr\antlr\2.7.6\antlr-
> 2.7.6.jar;D:\mvnrepo\cglib\cglib\2.1_3\cglib-
> 2.1_3.jar;D:\mvnrepo\asm\asm\1.5.3\asm-
> 1.5.3.jar;D:\mvnrepo\org\hibernate\hibernate-annotations\3.3.1.GA\hibernate-
> annotations-3.3.1.GA.jar;D:\mvnrepo\org\hibernate\hibernate-commons-
> annotations\3.0.0.ga\hibernate-commons-annotations-
> 3.0.0.ga.jar;D:\mvnrepo\org\hibernate\ejb3-persistence\1.0.1.GA\ejb3-persistence-
> 1.0.1.GA.jar;D:\mvnrepo\javassist\javassist\3.4.GA\javassist-
> 3.4.GA.jar;D:\mvnrepo\org\jdesktop\beansbinding\1.2.1\beansbinding-1.2.1.jar
> net.mohni.JBallTimer.BallTimer" execution is: '1'.
> >
> > when I stop mysql server i got this error when running:
> >
> > [ERROR]The following mojo encountered an error while executing:
> > [ERROR]Group-Id: org.codehaus.mojo
> > [ERROR]Artifact-Id: exec-maven-plugin
> > [ERROR]Version: 1.1-beta-1
> > [ERROR]Mojo: exec
> > [ERROR]brought in via: Direct invocation
> > [ERROR]While building project:
> > [ERROR]Group-Id: net.mohni
> > [ERROR]Artifact-Id: JBallTimer
> > [ERROR]Version: 1.0-SNAPSHOT
> > [ERROR]From file: C:\Development\workDir\JBallTimer\pom.xml
> > [ERROR]Reason: Result of "C:\Program Files\Java\jdk1.6.0_07\bin\java.exe" -
> classpath D:\mvnrepo\org\hibernate\hibernate-entitymanager\3.3.2.GA\hibernate-
> entitymanager-3.3.2.GA.jar;D:\mvnrepo\org\hibernate\hibernate\3.2.6.ga\hibernate-
> 3.2.6.ga.jar;D:\mvnrepo\net\sf\ehcache\ehcache\1.2.3\ehcache-
> 1.2.3.jar;D:\mvnrepo\commons-logging\commons-logging\1.0.4\commons-logging-
> 1.0.4.jar;D:\mvnrepo\commons-collections\commons-collections\2.1.1\commons-
> collections-2.1.1.jar;D:\mvnrepo\javax\transaction\jta\1.0.1B\jta-
> 1.0.1B.jar;D:\mvnrepo\asm\asm-attrs\1.5.3\asm-attrs-
> 1.5.3.jar;D:\mvnrepo\dom4j\dom4j\1.6.1\dom4j-
> 1.6.1.jar;D:\mvnrepo\antlr\antlr\2.7.6\antlr-
> 2.7.6.jar;D:\mvnrepo\cglib\cglib\2.1_3\cglib-
> 2.1_3.jar;D:\mvnrepo\asm\asm\1.5.3\asm-
> 1.5.3.jar;D:\mvnrepo\org\hibernate\hibernate-annotations\3.3.1.GA\hibernate-
> annotations-3.3.1.GA.jar;D:\mvnrepo\org\hibernate\hibernate-commons-
> annotations\3.0.0.ga\hibernate-commons-annotations-
> 3.0.0.ga.jar;D:\mvnrepo\org\hibernate\ejb3-persistence\1.0.1.GA\ejb3-persistence-
> 1.0.1.GA.jar;D:\mvnrepo\javassist\javassist\3.4.GA\javassist-
> 3.4.GA.jar;D:\mvnrepo\org\jdesktop\beansbinding\1.2.1\beansbinding-
> 1.2.1.jar;D:\mvnrepo\mysql\mysql-connector-java\5.1.6\mysql-connector-java-
> 5.1.6.jar;C:\Development\workDir\JBallTimer\target\classes
> net.mohni.JBallTimer.BallTimer execution is: '1'.
> >
> > what I see in the log is, that the profiler uses version 1.1 of the exec-maven-
> plugin and run/debug uses 1.1-beta-1
> >
> > any hints ?
> >
> > Regards
> > Daniel
> >
> >> -----Ursprüngliche Nachricht-----
> >> Von: Milos Kleint [mailto:mkleint@...]
> >> Gesendet: Montag, 18. August 2008 15:21
> >> An: user@...
> >> Betreff: Re: [mevenide-user] Profiler uses compile classpath instead of runtime
> >> classpath
> >>
> >> that's rather strange. I've checked the profiler related codebase and
> >> it shall be using the same exec:exec configuration as the run/debug
> >> actions are using.
> >>
> >> Milos
> >>
> >> On Mon, Aug 18, 2008 at 7:53 AM, Mohni, Daniel
> >> <daniel.mohni@...> wrote:
> >> > Hm,
> >> >
> >> > when I run the application without profiling it, it works without problems.
> >> > ...therefore I think this could be a different issue.
> >> >
> >> > btw: I'm using NB6.5Beta...
> >> >
> >> > Daniel
> >> >
> >> >> -----Ursprüngliche Nachricht-----
> >> >> Von: Milos Kleint [mailto:mkleint@...]
> >> >> Gesendet: Montag, 18. August 2008 07:42
> >> >> An: user@...
> >> >> Betreff: Re: [mevenide-user] Profiler uses compile classpath instead of
> runtime
> >> >> classpath
> >> >>
> >> >> AFAIK an issue primarily with the exec-maven-plugin.
> >> >>
> >> >> http://www.netbeans.org/issues/show_bug.cgi?id=137824
> >> >> http://jira.codehaus.org/browse/MEXEC-49
> >> >>
> >> >>
> >> >> Milos
> >> >>
> >> >> On Mon, Aug 18, 2008 at 7:39 AM, Mohni, Daniel
> >> >> <daniel.mohni@...> wrote:
> >> >> > Hello Milos
> >> >> >
> >> >> > just tried to Profile one of my small Maven2 Projects and found that the
> >> >> > Profiler is
> >> >> > using the compile classpath, instead of the runtime classpath.
> >> >> >
> >> >> > when I put the mysql/connector JAR as a runtime dependency, I get a
> >> >> > 'class not found',
> >> >> > changing dependency scope to 'compile' works fine
> >> >> >
> >> >> > Regards
> >> >> > Daniel
> >> >> >
> >> >> >
> >> >> >
> >> >> >
> >> >> >
> >> >> > ---------------------------------------------------------------------
> >> >> > To unsubscribe from this list, please visit:
> >> >> >
> >> >> > http://xircles.codehaus.org/manage_email
> >> >> >
> >> >> >
> >> >> >
> >> >>
> >> >> ---------------------------------------------------------------------
> >> >> To unsubscribe from this list, please visit:
> >> >>
> >> >> http://xircles.codehaus.org/manage_email
> >> >>
> >> >
> >> >
> >> > ---------------------------------------------------------------------
> >> > To unsubscribe from this list, please visit:
> >> >
> >> > http://xircles.codehaus.org/manage_email
> >> >
> >> >
> >> >
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe from this list, please visit:
> >>
> >> http://xircles.codehaus.org/manage_email
> >>
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe from this list, please visit:
> >
> > http://xircles.codehaus.org/manage_email
> >
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
> http://xircles.codehaus.org/manage_email
>
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
Thanks
Daniel
> -----Ursprüngliche Nachricht-----
> Von: Milos Kleint [mailto:mkleint@...]
> Gesendet: Dienstag, 19. August 2008 10:38
> An: user@...
> Betreff: Re: [mevenide-user] Profiler uses compile classpath instead of runtime
> classpath
>
> I see, you nailed the problem I think.
>
> I've checked the codebase and the current default mappings for
> debug/run/profile all use version 1.1. So the 1.1-beta-1 has to be
> coming from your nbactions.xml file as you edited the project
> configuration in the project properties dialog a while ago.
> the default mappings upgraded since, but the custom ones didn't.
> I guess the run/debug actions will start failing once you change the
> mapping to 1.1 as well. The "fix" could be to make the profile action
> to use 1.1-beta-1 as well.
>
> On a more general level, I'm not very happy with the way changes in
> action mapping configuration get dumped to the nbactions.xml file, but
> so far I didn't have time to look into it. specifically I imagine the
> correct behaviour would be that debug and profile actions by default
> inherit the custom settings from run and just add the debug/profile
> specifics..
>
>
> Milos
>
> Milos
>
> On Tue, Aug 19, 2008 at 10:21 AM, Mohni, Daniel
> <daniel.mohni@...> wrote:
> > Hi Milos
> >
> > I tried again with the mysql connector as runtime lib
> >
> > Debug: OK
> > Run: OK
> > Profile: NOK
> >
> > the driver is not in the classpath
> >
> > [ERROR]The following mojo encountered an error while executing:
> > [ERROR]Group-Id: org.codehaus.mojo
> > [ERROR]Artifact-Id: exec-maven-plugin
> > [ERROR]Version: 1.1
> > [ERROR]Mojo: exec
> > [ERROR]brought in via: Direct invocation
> > [ERROR]While building project:
> > [ERROR]Group-Id: net.mohni
> > [ERROR]Artifact-Id: JBallTimer
> > [ERROR]Version: 1.0-SNAPSHOT
> > [ERROR]From file: C:\Development\workDir\JBallTimer\pom.xml
> > [ERROR]Reason: Result of cmd.exe /X /C ""C:\Program
> Files\Java\jdk1.6.0_07\bin\java.exe" -XX:+HeapDumpOnOutOfMemoryError -
> XX:HeapDumpPath=C:DevelopmentworkDirJBallTimernbprojectprivateprofiler -
> agentpath:D:/ide/netbeans/nb65b/ide/profiler3/lib/deployed/jdk16/windows/profileri
> nterface.dll=D:/ide/netbeans/nb65b/ide/profiler3/lib,5140,10 -classpath
> C:\Development\workDir\JBallTimer\target\classes;D:\mvnrepo\org\hibernate\hibernat
> e-entitymanager\3.3.2.GA\hibernate-entitymanager-
> 3.3.2.GA.jar;D:\mvnrepo\org\hibernate\hibernate\3.2.6.ga\hibernate-
> 3.2.6.ga.jar;D:\mvnrepo\net\sf\ehcache\ehcache\1.2.3\ehcache-
> 1.2.3.jar;D:\mvnrepo\commons-logging\commons-logging\1.0.4\commons-logging-
> 1.0.4.jar;D:\mvnrepo\commons-collections\commons-collections\2.1.1\commons-
> collections-2.1.1.jar;D:\mvnrepo\javax\transaction\jta\1.0.1B\jta-
> 1.0.1B.jar;D:\mvnrepo\asm\asm-attrs\1.5.3\asm-attrs-
> 1.5.3.jar;D:\mvnrepo\dom4j\dom4j\1.6.1\dom4j-
> 1.6.1.jar;D:\mvnrepo\antlr\antlr\2.7.6\antlr-
> 2.7.6.jar;D:\mvnrepo\cglib\cglib\2.1_3\cglib-
> 2.1_3.jar;D:\mvnrepo\asm\asm\1.5.3\asm-
> 1.5.3.jar;D:\mvnrepo\org\hibernate\hibernate-annotations\3.3.1.GA\hibernate-
> annotations-3.3.1.GA.jar;D:\mvnrepo\org\hibernate\hibernate-commons-
> annotations\3.0.0.ga\hibernate-commons-annotations-
> 3.0.0.ga.jar;D:\mvnrepo\org\hibernate\ejb3-persistence\1.0.1.GA\ejb3-persistence-
> 1.0.1.GA.jar;D:\mvnrepo\javassist\javassist\3.4.GA\javassist-
> 3.4.GA.jar;D:\mvnrepo\org\jdesktop\beansbinding\1.2.1\beansbinding-1.2.1.jar
> net.mohni.JBallTimer.BallTimer" execution is: '1'.
> >
> > when I stop mysql server i got this error when running:
> >
> > [ERROR]The following mojo encountered an error while executing:
> > [ERROR]Group-Id: org.codehaus.mojo
> > [ERROR]Artifact-Id: exec-maven-plugin
> > [ERROR]Version: 1.1-beta-1
> > [ERROR]Mojo: exec
> > [ERROR]brought in via: Direct invocation
> > [ERROR]While building project:
> > [ERROR]Group-Id: net.mohni
> > [ERROR]Artifact-Id: JBallTimer
> > [ERROR]Version: 1.0-SNAPSHOT
> > [ERROR]From file: C:\Development\workDir\JBallTimer\pom.xml
> > [ERROR]Reason: Result of "C:\Program Files\Java\jdk1.6.0_07\bin\java.exe" -
> classpath D:\mvnrepo\org\hibernate\hibernate-entitymanager\3.3.2.GA\hibernate-
> entitymanager-3.3.2.GA.jar;D:\mvnrepo\org\hibernate\hibernate\3.2.6.ga\hibernate-
> 3.2.6.ga.jar;D:\mvnrepo\net\sf\ehcache\ehcache\1.2.3\ehcache-
> 1.2.3.jar;D:\mvnrepo\commons-logging\commons-logging\1.0.4\commons-logging-
> 1.0.4.jar;D:\mvnrepo\commons-collections\commons-collections\2.1.1\commons-
> collections-2.1.1.jar;D:\mvnrepo\javax\transaction\jta\1.0.1B\jta-
> 1.0.1B.jar;D:\mvnrepo\asm\asm-attrs\1.5.3\asm-attrs-
> 1.5.3.jar;D:\mvnrepo\dom4j\dom4j\1.6.1\dom4j-
> 1.6.1.jar;D:\mvnrepo\antlr\antlr\2.7.6\antlr-
> 2.7.6.jar;D:\mvnrepo\cglib\cglib\2.1_3\cglib-
> 2.1_3.jar;D:\mvnrepo\asm\asm\1.5.3\asm-
> 1.5.3.jar;D:\mvnrepo\org\hibernate\hibernate-annotations\3.3.1.GA\hibernate-
> annotations-3.3.1.GA.jar;D:\mvnrepo\org\hibernate\hibernate-commons-
> annotations\3.0.0.ga\hibernate-commons-annotations-
> 3.0.0.ga.jar;D:\mvnrepo\org\hibernate\ejb3-persistence\1.0.1.GA\ejb3-persistence-
> 1.0.1.GA.jar;D:\mvnrepo\javassist\javassist\3.4.GA\javassist-
> 3.4.GA.jar;D:\mvnrepo\org\jdesktop\beansbinding\1.2.1\beansbinding-
> 1.2.1.jar;D:\mvnrepo\mysql\mysql-connector-java\5.1.6\mysql-connector-java-
> 5.1.6.jar;C:\Development\workDir\JBallTimer\target\classes
> net.mohni.JBallTimer.BallTimer execution is: '1'.
> >
> > what I see in the log is, that the profiler uses version 1.1 of the exec-maven-
> plugin and run/debug uses 1.1-beta-1
> >
> > any hints ?
> >
> > Regards
> > Daniel
> >
> >> -----Ursprüngliche Nachricht-----
> >> Von: Milos Kleint [mailto:mkleint@...]
> >> Gesendet: Montag, 18. August 2008 15:21
> >> An: user@...
> >> Betreff: Re: [mevenide-user] Profiler uses compile classpath instead of runtime
> >> classpath
> >>
> >> that's rather strange. I've checked the profiler related codebase and
> >> it shall be using the same exec:exec configuration as the run/debug
> >> actions are using.
> >>
> >> Milos
> >>
> >> On Mon, Aug 18, 2008 at 7:53 AM, Mohni, Daniel
> >> <daniel.mohni@...> wrote:
> >> > Hm,
> >> >
> >> > when I run the application without profiling it, it works without problems.
> >> > ...therefore I think this could be a different issue.
> >> >
> >> > btw: I'm using NB6.5Beta...
> >> >
> >> > Daniel
> >> >
> >> >> -----Ursprüngliche Nachricht-----
> >> >> Von: Milos Kleint [mailto:mkleint@...]
> >> >> Gesendet: Montag, 18. August 2008 07:42
> >> >> An: user@...
> >> >> Betreff: Re: [mevenide-user] Profiler uses compile classpath instead of
> runtime
> >> >> classpath
> >> >>
> >> >> AFAIK an issue primarily with the exec-maven-plugin.
> >> >>
> >> >> http://www.netbeans.org/issues/show_bug.cgi?id=137824
> >> >> http://jira.codehaus.org/browse/MEXEC-49
> >> >>
> >> >>
> >> >> Milos
> >> >>
> >> >> On Mon, Aug 18, 2008 at 7:39 AM, Mohni, Daniel
> >> >> <daniel.mohni@...> wrote:
> >> >> > Hello Milos
> >> >> >
> >> >> > just tried to Profile one of my small Maven2 Projects and found that the
> >> >> > Profiler is
> >> >> > using the compile classpath, instead of the runtime classpath.
> >> >> >
> >> >> > when I put the mysql/connector JAR as a runtime dependency, I get a
> >> >> > 'class not found',
> >> >> > changing dependency scope to 'compile' works fine
> >> >> >
> >> >> > Regards
> >> >> > Daniel
> >> >> >
> >> >> >
> >> >> >
> >> >> >
> >> >> >
> >> >> > ---------------------------------------------------------------------
> >> >> > To unsubscribe from this list, please visit:
> >> >> >
> >> >> > http://xircles.codehaus.org/manage_email
> >> >> >
> >> >> >
> >> >> >
> >> >>
> >> >> ---------------------------------------------------------------------
> >> >> To unsubscribe from this list, please visit:
> >> >>
> >> >> http://xircles.codehaus.org/manage_email
> >> >>
> >> >
> >> >
> >> > ---------------------------------------------------------------------
> >> > To unsubscribe from this list, please visit:
> >> >
> >> > http://xircles.codehaus.org/manage_email
> >> >
> >> >
> >> >
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe from this list, please visit:
> >>
> >> http://xircles.codehaus.org/manage_email
> >>
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe from this list, please visit:
> >
> > http://xircles.codehaus.org/manage_email
> >
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
> http://xircles.codehaus.org/manage_email
>
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
« Return to Thread: Profiler uses compile classpath instead of runtime classpath
| Free embeddable forum powered by Nabble | Forum Help |
