problems after update netbeans maven plugin to 3.1.4
|
View:
New views
15 Messages
—
Rating Filter:
Alert me
|
 |
problems after update netbeans maven plugin to 3.1.4
by Hartmut Lang
::
Rate this Message:
Some parts of this message have been removed.
Learn more about Nabble's security policy.
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 |
|
|
Re: problems after update netbeans maven plugin to 3.1.4
by Bugzilla from mkleint@gmail.com
::
Rate this Message:
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 |
|
|
RE: problems after update netbeans maven plugin to 3.1.4
by Hartmut Lang
::
Rate this Message:
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.setDescriptorClassAndArtifa ctInfo(DefaultPluginManager.java:933) [ERROR] at org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(Defau ltPluginManager.java:247) [ERROR] at org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginM anager.java:186) [ERROR] at org.apache.maven.plugin.loader.DefaultPluginLoader.loadPlugin(DefaultPlu ginLoader.java:79) [ERROR] at org.apache.maven.plugin.loader.DefaultPluginLoader.loadPlugin(DefaultPlu ginLoader.java:52) [ERROR] at org.apache.maven.lifecycle.plan.DefaultBuildPlanner.loadPluginDescriptor (DefaultBuildPlanner.java:322) [ERROR] at org.apache.maven.lifecycle.plan.DefaultBuildPlanner.addReportingLifecycl 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.constructBui ldPlan(NBBuildPlanner.java:65) [ERROR] at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getLifecycleBindings (DefaultLifecycleExecutor.java:400) [ERROR] at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmentFo rProject(DefaultLifecycleExecutor.java:235) [ERROR] at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments( DefaultLifecycleExecutor.java:191) [ERROR] at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec ycleExecutor.java:149) [ERROR] at org.codehaus.mevenide.netbeans.embedder.exec.MyLifecycleExecutor.execute (MyLifecycleExecutor.java:72) [ERROR] at org.apache.maven.DefaultMaven.execute_aroundBody0(DefaultMaven.java:223) [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(MavenEmbedde r.java:904) [ERROR] at org.apache.maven.embedder.MavenEmbedder.execute_aroundBody3$advice(Maven Embedder.java:304) [ERROR] at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:1) [ERROR] at org.codehaus.mevenide.netbeans.execute.MavenJavaExecutor.run(MavenJavaEx 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 > 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 |
|
|
Re: problems after update netbeans maven plugin to 3.1.4
by Bugzilla from mkleint@gmail.com
::
Rate this Message:
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.setDescriptorClassAndArtifa > ctInfo(DefaultPluginManager.java:933) > [ERROR] at > org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(Defau > ltPluginManager.java:247) > [ERROR] at > org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginM > anager.java:186) > [ERROR] at > org.apache.maven.plugin.loader.DefaultPluginLoader.loadPlugin(DefaultPlu > ginLoader.java:79) > [ERROR] at > org.apache.maven.plugin.loader.DefaultPluginLoader.loadPlugin(DefaultPlu > ginLoader.java:52) > [ERROR] at > org.apache.maven.lifecycle.plan.DefaultBuildPlanner.loadPluginDescriptor > (DefaultBuildPlanner.java:322) > [ERROR] at > org.apache.maven.lifecycle.plan.DefaultBuildPlanner.addReportingLifecycl > 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.constructBui > ldPlan(NBBuildPlanner.java:65) > [ERROR] at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.getLifecycleBindings > (DefaultLifecycleExecutor.java:400) > [ERROR] at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmentFo > rProject(DefaultLifecycleExecutor.java:235) > [ERROR] at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments( > DefaultLifecycleExecutor.java:191) > [ERROR] at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec > ycleExecutor.java:149) > [ERROR] at > org.codehaus.mevenide.netbeans.embedder.exec.MyLifecycleExecutor.execute > (MyLifecycleExecutor.java:72) > [ERROR] at > org.apache.maven.DefaultMaven.execute_aroundBody0(DefaultMaven.java:223) > [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(MavenEmbedde > r.java:904) > [ERROR] at > org.apache.maven.embedder.MavenEmbedder.execute_aroundBody3$advice(Maven > Embedder.java:304) > [ERROR] at > org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:1) > [ERROR] at > org.codehaus.mevenide.netbeans.execute.MavenJavaExecutor.run(MavenJavaEx > 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 |
|
|
RE: problems after update netbeans maven plugin to 3.1.4
by brad hadfield
::
Rate this Message:
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 |
|
|
Re: problems after update netbeans maven plugin to 3.1.4
by Marcelo Morales-2
::
Rate this Message:
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 |
|
|
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 |
|
|
Re: problems after update netbeans maven plugin to 3.1.4
by Dietrich
::
Rate this Message:
Are you aware of the costs and the effects on an organization which uses mevenide in their projects - developers innocently upgrade their netbeans, their build stops working and nobody is there to help them until someone finds this post? This certainly gives everybody the impression that there is no strong commitment to the "stable" mevenide build system. Please reconsider your decision not to fix this. Or at least, please consider revoking the 3.1.4 update on plugins.netbeans.org if you are not going to fix this. |
|
|
Re: problems after update netbeans maven plugin to 3.1.4
by Bugzilla from mkleint@gmail.com
::
Rate this Message:
On Thu, Aug 28, 2008 at 5:02 AM, Dietrich <ds@...> wrote:
> > > > Milos Kleint wrote: >> >> 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). >> >> > > Are you aware of the costs and the effects on an organization which uses > mevenide in their projects - developers innocently upgrade their netbeans, > their build stops working and nobody is there to help them until someone > finds this post? This certainly gives everybody the impression that there is > no strong commitment to the "stable" mevenide build system. Please > reconsider your decision not to fix this. > Or at least, please consider revoking the 3.1.4 update on > plugins.netbeans.org if you are not going to fix this. > Well, I can ask a similar set of emotional questions. Like, are you aware of the cost that is involved in production of the free software you use? I've started this project in my free time, only recently it was backed up by my manager at Sun, but still a lot of my (and other commiter's) work is done in our free time that we could spend on some other activities instead, like sport, family, games or work that actually pays. On the technical level, you are actually "crying at the wrong grave" as we say here.. Unfortunately I've spend the 3.1.x releases (and before in unreleased snapshots) hunting down for a maven embedder binary snapshot that would actually work. None really do, but that's not my fault. I've spent the last 2 years waiting for a stable 2.1 embeddable maven, it's not here and will not be for a while as the 2.1 version was renamed to 3.0 in maven sourcebase and is being heavily refactored. Complain at dev@... please. I'd like to have embeddable maven that works just as you. However the reality is different. One has to do compromises, and the previous versions had more severe problems with "LOADING" the project as opposed to this problem which is only about building and can be workarounded by building with command line tools. As I said before I've given up on the embedder building right now and for the next version (in nb 6.5) I will try using command line maven whenever possible (when found on PATH). Sorry if the upgrade caused trouble to you, it helped someone else. Milos > -- > View this message in context: http://www.nabble.com/problems-after-update-netbeans-maven-plugin-to-3.1.4-tp18864420p19193461.html > Sent from the mevenide - user mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > 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 |
|
|
RE: problems after update netbeans maven plugin to 3.1.4
by Andy Law
::
Rate this Message:
> Milos Kleint wrote:
> > > > 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). > > > Are you aware of the costs and the effects on an organization > which uses mevenide in their projects - developers innocently > upgrade their netbeans, their build stops working and nobody > is there to help them until someone finds this post? This > certainly gives everybody the impression that there is no > strong commitment to the "stable" mevenide build system. I have to say, that thought crossed my mind too. > Please reconsider your decision not to fix this. > Or at least, please consider revoking the 3.1.4 update on > plugins.netbeans.org if you are not going to fix this. Please? Later, Andy ------------- Yada, yada, yada... The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336 Disclaimer: This e-mail and any attachments are confidential and intended solely for the use of the recipient(s) to whom they are addressed. If you have received it in error, please destroy all copies and inform the sender. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
Re: problems after update netbeans maven plugin to 3.1.4
by Cyrill Rüttimann-2
::
Rate this Message:
Hello,
This topic (Companies depending on OpenSource Software) is a really interesting one! We are using for example JasperReports and JFreeChart. We always have to make clear to the customer what is means to have free beer software as a dependency. No one is responsible to fix a certain bug in this type of software and thus we can not commit to have a certain functionality the customer wants to have implemented by the requested date. Enhance or fix an open source library/programm means: - someone from the dev team has to pick up the bug report or feature request dependend of the time they can spend and the importance of the bug/feature request - Do it yourself and hope one of the developers will pick up the patch - Spend some money to have it fixed immediately (JasperReport model) In my eyes it is not a good idea to stop fixing the 3.1.x branch for Netbeans 6.1 before the next version is out the doors, but we have to respect the decision of the maintainers. They have for sure a good reason to do so! I have written myself a maven plugin (original author of the findbugs plugin) and I was surprised how many email you receive with feature requests. Your whole life apart from the daily job gets filled up if you like to make everyone happy. Regards, Cyrill On 28.08.2008, at 05:02, Dietrich wrote: > > > > Milos Kleint wrote: >> >> 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). >> >> > > Are you aware of the costs and the effects on an organization which > uses > mevenide in their projects - developers innocently upgrade their > netbeans, > their build stops working and nobody is there to help them until > someone > finds this post? This certainly gives everybody the impression that > there is > no strong commitment to the "stable" mevenide build system. Please > reconsider your decision not to fix this. > Or at least, please consider revoking the 3.1.4 update on > plugins.netbeans.org if you are not going to fix this. > > -- > View this message in context: http://www.nabble.com/problems-after-update-netbeans-maven-plugin-to-3.1.4-tp18864420p19193461.html > Sent from the mevenide - user mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > 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 |
|
|
RE: problems after update netbeans maven plugin to 3.1.4
by Hartmut Lang
::
Rate this Message:
Milos,
Thanks for your work at mevenide! Can you give any hints how we can install an earlier version of the plugin like 3.1.3 instead of 3.1.4. Because this versions seems to work pretty well for us. Thanks, Hartmut -----Original Message----- From: Milos Kleint [mailto:mkleint@...] Sent: Donnerstag, 28. August 2008 21:43 To: user@... Subject: Re: [mevenide-user] problems after update netbeans maven plugin to 3.1.4 On Thu, Aug 28, 2008 at 5:02 AM, Dietrich <ds@...> wrote: > > > > Milos Kleint wrote: >> >> 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). >> >> > > Are you aware of the costs and the effects on an organization which > mevenide in their projects - developers innocently upgrade their netbeans, > their build stops working and nobody is there to help them until someone > finds this post? This certainly gives everybody the impression that there is > no strong commitment to the "stable" mevenide build system. Please > reconsider your decision not to fix this. > Or at least, please consider revoking the 3.1.4 update on > plugins.netbeans.org if you are not going to fix this. > Well, I can ask a similar set of emotional questions. Like, are you aware of the cost that is involved in production of the free software you use? I've started this project in my free time, only recently it was backed up by my manager at Sun, but still a lot of my (and other commiter's) work is done in our free time that we could spend on some other activities instead, like sport, family, games or work that actually pays. On the technical level, you are actually "crying at the wrong grave" as we say here.. Unfortunately I've spend the 3.1.x releases (and before in unreleased snapshots) hunting down for a maven embedder binary snapshot that would actually work. None really do, but that's not my fault. I've spent the last 2 years waiting for a stable 2.1 embeddable maven, it's not here and will not be for a while as the 2.1 version was renamed to 3.0 in maven sourcebase and is being heavily refactored. Complain at dev@... please. I'd like to have embeddable maven that works just as you. However the reality is different. One has to do compromises, and the previous versions had more severe problems with "LOADING" the project as opposed to this problem which is only about building and can be workarounded by building with command line tools. As I said before I've given up on the embedder building right now and for the next version (in nb 6.5) I will try using command line maven whenever possible (when found on PATH). Sorry if the upgrade caused trouble to you, it helped someone else. Milos > -- > View this message in context: http://www.nabble.com/problems-after-update-netbeans-maven-plugin-to-3.1 .4-tp18864420p19193461.html > Sent from the mevenide - user mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > 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 |
|
|
Re: problems after update netbeans maven plugin to 3.1.4
by Bugzilla from mkleint@gmail.com
::
Rate this Message:
I've checked last week and only 311 and 314 are available as zips at
m.c.org/download i'll put 313 there as well once i get back online (next week). Milos On 9/3/08, Hartmut Lang <hartmut.lang@...> wrote: > Milos, > > Thanks for your work at mevenide! > > Can you give any hints how we can install an earlier version of the > plugin like 3.1.3 instead of 3.1.4. Because this versions seems to work > pretty well for us. > > Thanks, > Hartmut > > -----Original Message----- > From: Milos Kleint [mailto:mkleint@...] > Sent: Donnerstag, 28. August 2008 21:43 > To: user@... > Subject: Re: [mevenide-user] problems after update netbeans maven plugin > to 3.1.4 > > On Thu, Aug 28, 2008 at 5:02 AM, Dietrich <ds@...> wrote: >> >> >> >> Milos Kleint wrote: >>> >>> 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). >>> >>> >> >> Are you aware of the costs and the effects on an organization which > uses >> mevenide in their projects - developers innocently upgrade their > netbeans, >> their build stops working and nobody is there to help them until > someone >> finds this post? This certainly gives everybody the impression that > there is >> no strong commitment to the "stable" mevenide build system. Please >> reconsider your decision not to fix this. >> Or at least, please consider revoking the 3.1.4 update on >> plugins.netbeans.org if you are not going to fix this. >> > > Well, I can ask a similar set of emotional questions. > Like, are you aware of the cost that is involved in production of the > free software you use? I've started this project in my free time, only > recently it was backed up by my manager at Sun, but still a lot of my > (and other commiter's) work is done in our free time that we could > spend on some other activities instead, like sport, family, games or > work that actually pays. > > On the technical level, you are actually "crying at the wrong grave" > as we say here.. Unfortunately I've spend the 3.1.x releases (and > before in unreleased snapshots) hunting down for a maven embedder > binary snapshot that would actually work. None really do, but that's > not my fault. I've spent the last 2 years waiting for a stable 2.1 > embeddable maven, it's not here and will not be for a while as the 2.1 > version was renamed to 3.0 in maven sourcebase and is being heavily > refactored. Complain at dev@... please. I'd like to have > embeddable maven that works just as you. However the reality is > different. One has to do compromises, and the previous versions had > more severe problems with "LOADING" the project as opposed to this > problem which is only about building and can be workarounded by > building with command line tools. > > As I said before I've given up on the embedder building right now and > for the next version (in nb 6.5) I will try using command line maven > whenever possible (when found on PATH). > > Sorry if the upgrade caused trouble to you, it helped someone else. > > Milos > >> -- >> View this message in context: > http://www.nabble.com/problems-after-update-netbeans-maven-plugin-to-3.1 > .4-tp18864420p19193461.html >> Sent from the mevenide - user mailing list archive at Nabble.com. >> >> >> --------------------------------------------------------------------- >> 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 |
|
|
Re: problems after update netbeans maven plugin to 3.1.4
by Bugzilla from mkleint@gmail.com
::
Rate this Message:
I have uploaded the 3.1.3 version (zip with nbm files) to
http://mevenide.codehaus.org/download page. Regards Milos On Wed, Sep 3, 2008 at 8:25 PM, Milos Kleint <mkleint@...> wrote: > I've checked last week and only 311 and 314 are available as zips at > m.c.org/download i'll put 313 there as well once i get back online > (next week). Milos > > On 9/3/08, Hartmut Lang <hartmut.lang@...> wrote: >> Milos, >> >> Thanks for your work at mevenide! >> >> Can you give any hints how we can install an earlier version of the >> plugin like 3.1.3 instead of 3.1.4. Because this versions seems to work >> pretty well for us. >> >> Thanks, >> Hartmut >> >> -----Original Message----- >> From: Milos Kleint [mailto:mkleint@...] >> Sent: Donnerstag, 28. August 2008 21:43 >> To: user@... >> Subject: Re: [mevenide-user] problems after update netbeans maven plugin >> to 3.1.4 >> >> On Thu, Aug 28, 2008 at 5:02 AM, Dietrich <ds@...> wrote: >>> >>> >>> >>> Milos Kleint wrote: >>>> >>>> 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). >>>> >>>> >>> >>> Are you aware of the costs and the effects on an organization which >> uses >>> mevenide in their projects - developers innocently upgrade their >> netbeans, >>> their build stops working and nobody is there to help them until >> someone >>> finds this post? This certainly gives everybody the impression that >> there is >>> no strong commitment to the "stable" mevenide build system. Please >>> reconsider your decision not to fix this. >>> Or at least, please consider revoking the 3.1.4 update on >>> plugins.netbeans.org if you are not going to fix this. >>> >> >> Well, I can ask a similar set of emotional questions. >> Like, are you aware of the cost that is involved in production of the >> free software you use? I've started this project in my free time, only >> recently it was backed up by my manager at Sun, but still a lot of my >> (and other commiter's) work is done in our free time that we could >> spend on some other activities instead, like sport, family, games or >> work that actually pays. >> >> On the technical level, you are actually "crying at the wrong grave" >> as we say here.. Unfortunately I've spend the 3.1.x releases (and >> before in unreleased snapshots) hunting down for a maven embedder >> binary snapshot that would actually work. None really do, but that's >> not my fault. I've spent the last 2 years waiting for a stable 2.1 >> embeddable maven, it's not here and will not be for a while as the 2.1 >> version was renamed to 3.0 in maven sourcebase and is being heavily >> refactored. Complain at dev@... please. I'd like to have >> embeddable maven that works just as you. However the reality is >> different. One has to do compromises, and the previous versions had >> more severe problems with "LOADING" the project as opposed to this >> problem which is only about building and can be workarounded by >> building with command line tools. >> >> As I said before I've given up on the embedder building right now and >> for the next version (in nb 6.5) I will try using command line maven >> whenever possible (when found on PATH). >> >> Sorry if the upgrade caused trouble to you, it helped someone else. >> >> Milos >> >>> -- >>> View this message in context: >> http://www.nabble.com/problems-after-update-netbeans-maven-plugin-to-3.1 >> .4-tp18864420p19193461.html >>> Sent from the mevenide - user mailing list archive at Nabble.com. >>> >>> >>> --------------------------------------------------------------------- >>> 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 |
|
|
Re: problems after update netbeans maven plugin to 3.1.4
by Dietrich
::
Rate this Message:
Of course you are right, while some people *are* paid for their work on open source projects, most still aren't. Thank you for reminding me and thank you for explaining that the originating problem cannot be fixed by you within a reasonable time frame. I did not mean to offend you.
I should use some more care when complaining at dev@maven.apache.org ;-) I'll try to find the time to dig deeper into this problem and file a proper bug report. |
| Free embeddable forum powered by Nabble | Forum Help |
