AW: [mevenide-user] Profiler uses compile classpath instead of runtime classpath

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:[email protected]]
> Gesendet: Montag, 18. August 2008 07:42
> An: [email protected]
> 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
> <[email protected]> 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