org.codehaus.mevenide.netbeans/3 3.1]
Regards,
John
-Original Message-
From: Milos Kleint [mailto:[EMAIL PROTECTED]
Sent: 18 February 2008 17:58
To: Maven Users List
Subject: Re: Mavenide NetBeans
only by upgrading to the latest trunk (daily builds at
http://deadlock.netbeans.org/hudson/job/mevenide
3.1] NetBeans Maven2 project
support [module org.codehaus.mevenide.netbeans/3 3.1]
Regards,
John
-Original Message-
From: Milos Kleint [mailto:[EMAIL PROTECTED]
Sent: 18 February 2008 17:58
To: Maven Users List
Subject: Re: Mavenide NetBeans
only by upgrading
To: Maven Users List
Subject: Re: Mavenide NetBeans
I have filed it as bug against netbeans:
http://www.netbeans.org/issues/show_bug.cgi?id=127716
a workaround for the time being is
1. uninstall and remove all maven modules from your
installation (Tools/Plugins dialog should do) 2
load NB6 up again it is not recognising
Maven projects. Have I deleted too much perhaps?
John
-Original Message-
From: Milos Kleint [mailto:[EMAIL PROTECTED]
Sent: 19 February 2008 10:27
To: Maven Users List
Subject: Re: Mavenide NetBeans
I have filed it as bug against
Hi,
Our Mavenide seems to be maven 2.0.4, is there a way to put the latest
stable into the NB plugin?
TIA
John
Eurobase International Limited and its subsidiaries (Eurobase) are unable to
exercise control over the content of information in E-Mails. Any views and
opinions expressed may be
only by upgrading to the latest trunk (daily builds at
http://deadlock.netbeans.org/hudson/job/mevenide/)
that one use the latest (January/February) 2.1-SNAPSHOT.
Unfurtunately there's no way to put pre-2.1 stable releases as
embedded version (due to design problems on 2.0.x branch) Please not
In a netbeans project you can press F9 to compile a class. In a maven
project this seems to be barred.
Is there a way to get this functionality back?
TIA,
John
Eurobase International Limited and its subsidiaries (Eurobase) are unable to
exercise control over the content of information in
I'm trying to run my project using the Mavenide for NetBeans.
I notice that the NB run setup creates a profile in pom.xml, but when
you run it in NB, it expects the artefact in a project subdirectoy of
target/executable-netbeans, so the execution fails.
But the default location for the
John Coleman wrote:
I'm trying to run my project using the Mavenide for NetBeans.
I notice that the NB run setup creates a profile in pom.xml, but when
you run it in NB, it expects the artefact in a project subdirectoy of
target/executable-netbeans, so the execution fails.
But the
discrepancy with Mavenide NetBeans plugin
John Coleman wrote:
I'm trying to run my project using the Mavenide for NetBeans.
I notice that the NB run setup creates a profile in pom.xml, but when
you run it in NB, it expects the artefact in a project subdirectoy of
target/executable-netbeans, so
, and fixed?
TIA
John
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: 11 September 2007 13:15
To: Maven Users List
Subject: Re: target discrepancy with Mavenide NetBeans plugin
John Coleman wrote:
I'm trying to run my project using the Mavenide
List
Subject: Re: target discrepancy with Mavenide NetBeans plugin
what version of netbeans are you running on? Can you confirm that the
assembly-plugin executes as part of the build?
Milos
On 9/11/07, John Coleman [EMAIL PROTECTED]
wrote:
Hi,
Yes I have seen that bug before, but in this case
September 2007 14:22
To: Maven Users List
Subject: Re: target discrepancy with Mavenide NetBeans plugin
what version of netbeans are you running on? Can you confirm that the
assembly-plugin executes as part of the build?
Milos
On 9/11/07, John Coleman [EMAIL PROTECTED]
wrote:
Hi,
Yes I have
13 matches
Mail list logo
