« Return to Thread: problems after update netbeans maven plugin to 3.1.4
Re: problems after update netbeans maven plugin to 3.1.4
by Bugzilla from mkleint@gmail.com
::
Rate this Message:
Unfortunately I don't plan any more updates for 6.1, the 3.1.4 is the
final release for 6.1 as far as I'm concerned (currently).
For the upcoming version in 6.5 timeframe, I've recently completely
redesigned how build execution works. I've grown impatient with the
speed at which the 2.1-SNAPSHOT embedder was moving towards a stable,
backward compatible release. IMHO it's still months or years away from
release and the backward compatibility might not be in the package.
I've made the command line execution the default now. If mvn binary
can be found on PATH or is set by user, thein it's used. the embedded
build is used only as fallback and a warning is given in output
window.
(Soon to be part of binaries released on netbeans 6.5 beta update center)
The workaround for 6.1 is the same, use the command line maven for
execution (unfortunately it's not possible for stuff like run action
on webapps)
Regards
Milos
On Fri, Aug 15, 2008 at 6:37 PM, Marcelo Morales
<marcelomorales.name@...> wrote:
> Same here... I was about to ask the same. You beat me to it.
>
>
> On Fri, Aug 15, 2008 at 10:52 AM, brad hadfield
> <brad.hadfield@...> wrote:
>>
>> If anyone is having the same problem ( a few developers in my shop are ) until it is fixed...
>>
>> I've found that closing output windows after build or run file prevents the call to reset() and the resulting freeze.
>>
>> Thanks
>>
>> Brad Hadfield
>>
>> -----Original Message-----
>> From: Milos Kleint [mailto:mkleint@...]
>> Sent: August 7, 2008 2:04 AM
>> To: user@...
>> Subject: Re: [mevenide-user] problems after update netbeans maven plugin to 3.1.4
>>
>> exception should be enough.
>>
>> Thanks.
>>
>> Milos
>>
>> On Thu, Aug 7, 2008 at 8:01 AM, Hartmut Lang <hartmut.lang@...> wrote:
>>> Do you need the whole debug output or just the exception like this:
>>> [ERROR]Runtime Exception thrown during execution [ERROR]null
>>> [ERROR]Error stacktrace:
>>> [ERROR]java.lang.NullPointerException
>>> [ERROR] at
>>> org.apache.maven.plugin.DefaultPluginManager.setDescriptorClassAndArti
>>> fa
>>> ctInfo(DefaultPluginManager.java:933)
>>> [ERROR] at
>>> org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(Def
>>> au
>>> ltPluginManager.java:247)
>>> [ERROR] at
>>> org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPlugi
>>> nM
>>> anager.java:186)
>>> [ERROR] at
>>> org.apache.maven.plugin.loader.DefaultPluginLoader.loadPlugin(DefaultP
>>> lu
>>> ginLoader.java:79)
>>> [ERROR] at
>>> org.apache.maven.plugin.loader.DefaultPluginLoader.loadPlugin(DefaultP
>>> lu
>>> ginLoader.java:52)
>>> [ERROR] at
>>> org.apache.maven.lifecycle.plan.DefaultBuildPlanner.loadPluginDescript
>>> or
>>> (DefaultBuildPlanner.java:322)
>>> [ERROR] at
>>> org.apache.maven.lifecycle.plan.DefaultBuildPlanner.addReportingLifecy
>>> cl
>>> eModifiers(DefaultBuildPlanner.java:245)
>>> [ERROR] at
>>> org.apache.maven.lifecycle.plan.DefaultBuildPlanner.constructBuildPlan
>>> _a
>>> roundBody0(DefaultBuildPlanner.java:118)
>>> [ERROR] at
>>> org.apache.maven.lifecycle.plan.DefaultBuildPlanner.constructBuildPlan
>>> _a
>>> roundBody1$advice(DefaultBuildPlanner.java:403)
>>> [ERROR] at
>>> org.apache.maven.lifecycle.plan.DefaultBuildPlanner.constructBuildPlan
>>> (D
>>> efaultBuildPlanner.java:1)
>>> [ERROR] at
>>> org.codehaus.mevenide.netbeans.embedder.exec.NBBuildPlanner.constructB
>>> ui
>>> ldPlan(NBBuildPlanner.java:65)
>>> [ERROR] at
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.getLifecycleBindin
>>> gs
>>> (DefaultLifecycleExecutor.java:400)
>>> [ERROR] at
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegment
>>> Fo
>>> rProject(DefaultLifecycleExecutor.java:235)
>>> [ERROR] at
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegment
>>> s(
>>> DefaultLifecycleExecutor.java:191)
>>> [ERROR] at
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLif
>>> ec
>>> ycleExecutor.java:149)
>>> [ERROR] at
>>> org.codehaus.mevenide.netbeans.embedder.exec.MyLifecycleExecutor.execu
>>> te
>>> (MyLifecycleExecutor.java:72)
>>> [ERROR] at
>>> org.apache.maven.DefaultMaven.execute_aroundBody0(DefaultMaven.java:22
>>> 3)
>>> [ERROR] at
>>> org.apache.maven.DefaultMaven.execute_aroundBody1$advice(DefaultMaven.
>>> ja
>>> va:304)
>>> [ERROR] at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:1)
>>> [ERROR] at
>>> org.apache.maven.embedder.MavenEmbedder.execute_aroundBody2(MavenEmbed
>>> de
>>> r.java:904)
>>> [ERROR] at
>>> org.apache.maven.embedder.MavenEmbedder.execute_aroundBody3$advice(Mav
>>> en
>>> Embedder.java:304)
>>> [ERROR] at
>>> org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:1)
>>> [ERROR] at
>>> org.codehaus.mevenide.netbeans.execute.MavenJavaExecutor.run(MavenJava
>>> Ex
>>> ecutor.java:215)
>>> [ERROR] at
>>> org.netbeans.core.execution.RunClassThread.run(RunClassThread.java:151
>>> )
>>>
>>>
>>> Hartmut Lang
>>>
>>> --
>>>
>>> hartmut.lang@...
>>>
>>>
>>> -----Original Message-----
>>> From: Milos Kleint [mailto:mkleint@...]
>>> Sent: Donnerstag, 7. August 2008 07:57
>>> To: user@...
>>> Subject: Re: [mevenide-user] problems after update netbeans maven
>>> plugin to 3.1.4
>>>
>>> we did upgrade the maven embedder between 3.1.3 and 3.1.4. It was to
>>> fix a different issue (long dependency version caused
>>> NumberFormatException)
>>> Can you file a bug report at
>>> http://www.netbeans.org/issues/enter_bug.cgi?component=maven
>>> and also attach the debug maven output. That should show what the
>>> exception is about.
>>>
>>> as a workaround, you can setup netbeans to run with command line maven.
>>>
>>> Hope that helps.
>>>
>>> Milos
>>>
>>> On Thu, Aug 7, 2008 at 7:40 AM, Hartmut Lang
>>> <hartmut.lang@...>
>>> wrote:
>>>>
>>>>
>>>> I have updated to maven plugin 3.1.4 in netbeans.
>>>>
>>>>
>>>>
>>>> After this my build for an unchanged projects fails with:
>>>>
>>>> Scanning for projects...
>>>>
>>>> project-execute
>>>>
>>>> [ERROR]Runtime Exception thrown during execution
>>>>
>>>> [ERROR]null
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> I use the cxf-codegen-plugin which seems to cause the problem. But it
>>>> does/did work with the 3.1.3 version of the maven plugin.
>>>>
>>>>
>>>>
>>>> <plugin>
>>>>
>>>> <groupId>org.apache.cxf</groupId>
>>>>
>>>> <artifactId>cxf-codegen-plugin</artifactId>
>>>>
>>>> <version>2.1.1</version>
>>>>
>>>> <dependencies>
>>>>
>>>> <dependency>
>>>>
>>>> <groupId>org.apache.cxf</groupId>
>>>>
>>>> <artifactId>cxf-codegen-plugin</artifactId>
>>>>
>>>> <version>2.1.1</version>
>>>>
>>>> </dependency>
>>>>
>>>> <dependency>
>>>>
>>>> <groupId>org.apache.cxf</groupId>
>>>>
>>>> <artifactId>cxf-xjc-ts</artifactId>
>>>>
>>>> <version>2.1.1</version>
>>>>
>>>> </dependency>
>>>>
>>>> </dependencies>
>>>>
>>>> <executions>
>>>>
>>>> <execution>
>>>>
>>>> <id>generate-sources</id>
>>>>
>>>> <phase>generate-sources</phase>
>>>>
>>>> <goals>
>>>>
>>>> <goal>wsdl2java</goal>
>>>>
>>>> </goals>
>>>>
>>>> </execution>
>>>>
>>>> </executions>
>>>>
>>>> </plugin>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> Product Version = NetBeans IDE 6.1 (Build 080707)
>>>>
>>>> Operating System = Windows XP version 5.1 running on x86
>>>>
>>>> Java; VM; Vendor = 1.6.0_07; Java HotSpot(TM) Client VM
>>> 10.0-b23;
>>>> Sun Microsystems Inc.
>>>>
>>>> Runtime = Java(TM) SE Runtime Environment
>>> 1.6.0_07-b06
>>>>
>>>> Java Home = C:\Programme\Java\jdk1.6.0_07\jre
>>>>
>>>> System Locale; Encoding = de_DE (nb); Cp1252
>>>>
>>>>
>>>>
>>>> Help welcome,
>>>>
>>>> Hartmut Lang
>>>
>>> ---------------------------------------------------------------------
>>> 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
final release for 6.1 as far as I'm concerned (currently).
For the upcoming version in 6.5 timeframe, I've recently completely
redesigned how build execution works. I've grown impatient with the
speed at which the 2.1-SNAPSHOT embedder was moving towards a stable,
backward compatible release. IMHO it's still months or years away from
release and the backward compatibility might not be in the package.
I've made the command line execution the default now. If mvn binary
can be found on PATH or is set by user, thein it's used. the embedded
build is used only as fallback and a warning is given in output
window.
(Soon to be part of binaries released on netbeans 6.5 beta update center)
The workaround for 6.1 is the same, use the command line maven for
execution (unfortunately it's not possible for stuff like run action
on webapps)
Regards
Milos
On Fri, Aug 15, 2008 at 6:37 PM, Marcelo Morales
<marcelomorales.name@...> wrote:
> Same here... I was about to ask the same. You beat me to it.
>
>
> On Fri, Aug 15, 2008 at 10:52 AM, brad hadfield
> <brad.hadfield@...> wrote:
>>
>> If anyone is having the same problem ( a few developers in my shop are ) until it is fixed...
>>
>> I've found that closing output windows after build or run file prevents the call to reset() and the resulting freeze.
>>
>> Thanks
>>
>> Brad Hadfield
>>
>> -----Original Message-----
>> From: Milos Kleint [mailto:mkleint@...]
>> Sent: August 7, 2008 2:04 AM
>> To: user@...
>> Subject: Re: [mevenide-user] problems after update netbeans maven plugin to 3.1.4
>>
>> exception should be enough.
>>
>> Thanks.
>>
>> Milos
>>
>> On Thu, Aug 7, 2008 at 8:01 AM, Hartmut Lang <hartmut.lang@...> wrote:
>>> Do you need the whole debug output or just the exception like this:
>>> [ERROR]Runtime Exception thrown during execution [ERROR]null
>>> [ERROR]Error stacktrace:
>>> [ERROR]java.lang.NullPointerException
>>> [ERROR] at
>>> org.apache.maven.plugin.DefaultPluginManager.setDescriptorClassAndArti
>>> fa
>>> ctInfo(DefaultPluginManager.java:933)
>>> [ERROR] at
>>> org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(Def
>>> au
>>> ltPluginManager.java:247)
>>> [ERROR] at
>>> org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPlugi
>>> nM
>>> anager.java:186)
>>> [ERROR] at
>>> org.apache.maven.plugin.loader.DefaultPluginLoader.loadPlugin(DefaultP
>>> lu
>>> ginLoader.java:79)
>>> [ERROR] at
>>> org.apache.maven.plugin.loader.DefaultPluginLoader.loadPlugin(DefaultP
>>> lu
>>> ginLoader.java:52)
>>> [ERROR] at
>>> org.apache.maven.lifecycle.plan.DefaultBuildPlanner.loadPluginDescript
>>> or
>>> (DefaultBuildPlanner.java:322)
>>> [ERROR] at
>>> org.apache.maven.lifecycle.plan.DefaultBuildPlanner.addReportingLifecy
>>> cl
>>> eModifiers(DefaultBuildPlanner.java:245)
>>> [ERROR] at
>>> org.apache.maven.lifecycle.plan.DefaultBuildPlanner.constructBuildPlan
>>> _a
>>> roundBody0(DefaultBuildPlanner.java:118)
>>> [ERROR] at
>>> org.apache.maven.lifecycle.plan.DefaultBuildPlanner.constructBuildPlan
>>> _a
>>> roundBody1$advice(DefaultBuildPlanner.java:403)
>>> [ERROR] at
>>> org.apache.maven.lifecycle.plan.DefaultBuildPlanner.constructBuildPlan
>>> (D
>>> efaultBuildPlanner.java:1)
>>> [ERROR] at
>>> org.codehaus.mevenide.netbeans.embedder.exec.NBBuildPlanner.constructB
>>> ui
>>> ldPlan(NBBuildPlanner.java:65)
>>> [ERROR] at
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.getLifecycleBindin
>>> gs
>>> (DefaultLifecycleExecutor.java:400)
>>> [ERROR] at
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegment
>>> Fo
>>> rProject(DefaultLifecycleExecutor.java:235)
>>> [ERROR] at
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegment
>>> s(
>>> DefaultLifecycleExecutor.java:191)
>>> [ERROR] at
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLif
>>> ec
>>> ycleExecutor.java:149)
>>> [ERROR] at
>>> org.codehaus.mevenide.netbeans.embedder.exec.MyLifecycleExecutor.execu
>>> te
>>> (MyLifecycleExecutor.java:72)
>>> [ERROR] at
>>> org.apache.maven.DefaultMaven.execute_aroundBody0(DefaultMaven.java:22
>>> 3)
>>> [ERROR] at
>>> org.apache.maven.DefaultMaven.execute_aroundBody1$advice(DefaultMaven.
>>> ja
>>> va:304)
>>> [ERROR] at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:1)
>>> [ERROR] at
>>> org.apache.maven.embedder.MavenEmbedder.execute_aroundBody2(MavenEmbed
>>> de
>>> r.java:904)
>>> [ERROR] at
>>> org.apache.maven.embedder.MavenEmbedder.execute_aroundBody3$advice(Mav
>>> en
>>> Embedder.java:304)
>>> [ERROR] at
>>> org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:1)
>>> [ERROR] at
>>> org.codehaus.mevenide.netbeans.execute.MavenJavaExecutor.run(MavenJava
>>> Ex
>>> ecutor.java:215)
>>> [ERROR] at
>>> org.netbeans.core.execution.RunClassThread.run(RunClassThread.java:151
>>> )
>>>
>>>
>>> Hartmut Lang
>>>
>>> --
>>>
>>> hartmut.lang@...
>>>
>>>
>>> -----Original Message-----
>>> From: Milos Kleint [mailto:mkleint@...]
>>> Sent: Donnerstag, 7. August 2008 07:57
>>> To: user@...
>>> Subject: Re: [mevenide-user] problems after update netbeans maven
>>> plugin to 3.1.4
>>>
>>> we did upgrade the maven embedder between 3.1.3 and 3.1.4. It was to
>>> fix a different issue (long dependency version caused
>>> NumberFormatException)
>>> Can you file a bug report at
>>> http://www.netbeans.org/issues/enter_bug.cgi?component=maven
>>> and also attach the debug maven output. That should show what the
>>> exception is about.
>>>
>>> as a workaround, you can setup netbeans to run with command line maven.
>>>
>>> Hope that helps.
>>>
>>> Milos
>>>
>>> On Thu, Aug 7, 2008 at 7:40 AM, Hartmut Lang
>>> <hartmut.lang@...>
>>> wrote:
>>>>
>>>>
>>>> I have updated to maven plugin 3.1.4 in netbeans.
>>>>
>>>>
>>>>
>>>> After this my build for an unchanged projects fails with:
>>>>
>>>> Scanning for projects...
>>>>
>>>> project-execute
>>>>
>>>> [ERROR]Runtime Exception thrown during execution
>>>>
>>>> [ERROR]null
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> I use the cxf-codegen-plugin which seems to cause the problem. But it
>>>> does/did work with the 3.1.3 version of the maven plugin.
>>>>
>>>>
>>>>
>>>> <plugin>
>>>>
>>>> <groupId>org.apache.cxf</groupId>
>>>>
>>>> <artifactId>cxf-codegen-plugin</artifactId>
>>>>
>>>> <version>2.1.1</version>
>>>>
>>>> <dependencies>
>>>>
>>>> <dependency>
>>>>
>>>> <groupId>org.apache.cxf</groupId>
>>>>
>>>> <artifactId>cxf-codegen-plugin</artifactId>
>>>>
>>>> <version>2.1.1</version>
>>>>
>>>> </dependency>
>>>>
>>>> <dependency>
>>>>
>>>> <groupId>org.apache.cxf</groupId>
>>>>
>>>> <artifactId>cxf-xjc-ts</artifactId>
>>>>
>>>> <version>2.1.1</version>
>>>>
>>>> </dependency>
>>>>
>>>> </dependencies>
>>>>
>>>> <executions>
>>>>
>>>> <execution>
>>>>
>>>> <id>generate-sources</id>
>>>>
>>>> <phase>generate-sources</phase>
>>>>
>>>> <goals>
>>>>
>>>> <goal>wsdl2java</goal>
>>>>
>>>> </goals>
>>>>
>>>> </execution>
>>>>
>>>> </executions>
>>>>
>>>> </plugin>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> Product Version = NetBeans IDE 6.1 (Build 080707)
>>>>
>>>> Operating System = Windows XP version 5.1 running on x86
>>>>
>>>> Java; VM; Vendor = 1.6.0_07; Java HotSpot(TM) Client VM
>>> 10.0-b23;
>>>> Sun Microsystems Inc.
>>>>
>>>> Runtime = Java(TM) SE Runtime Environment
>>> 1.6.0_07-b06
>>>>
>>>> Java Home = C:\Programme\Java\jdk1.6.0_07\jre
>>>>
>>>> System Locale; Encoding = de_DE (nb); Cp1252
>>>>
>>>>
>>>>
>>>> Help welcome,
>>>>
>>>> Hartmut Lang
>>>
>>> ---------------------------------------------------------------------
>>> 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: problems after update netbeans maven plugin to 3.1.4
| Free embeddable forum powered by Nabble | Forum Help |
