Nabble - mevenide - user

Re: Re: Mavenide seems not to use settings.xml when downloading javadoc and sources

2009-09-03T01:48:53Z

Bonjour,

Je suis absent du 1 au 11 septembre inclus.
Je prendrai connaissance de votre mail le 14 septembre.
En cas de besoin, vous pouvez contacter Thierry Billard (thierry.billard@...).

Cordialement

Charles Bosquet
axYus
Tel: 05 56 42 90 05

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

Re: Mavenide seems not to use settings.xml when downloading javadoc and sources

2009-09-03T01:39:25Z

Mavenide seems not to use settings.xml when downloading javadoc and sources

2009-09-03T01:22:57Z

When I select "Download Javadoc" or "Download Sources" from the UI in NB
6.7.1, the downloader doesn't seem to check the settings.xml file for mirror
locations. Even though I have specified a mirror for central, AND specified
additional artifact repositories, maven seems to try to download from the
standard maven repo, and ignores my additional mirrors. This is also if I
specify a parent project that exists on a internal repository and not on the
central repo.

Is there any where I can edit the settings.xml file that the mavenide use for
these kind of opperations?

I am using NB 6.7.1 and Maven 2.0.9.

Regards
Magne
--
Magne Nordtveit <mn@...>
System Engineer
Offshore Simulator Centre AS

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

RE: Netbeans 6.7RC and dependencies with version ranges.

2009-05-18T02:50:12Z

>From: Milos Kleint [mailto:mkleint@...]
>Sent: 18 May 2009 10:41
>To: user@...
>Subject: Re: [mevenide-user] Netbeans 6.7RC and dependencies with version ranges.
>
>please try with the latest dailies and file as issue if it persists, I've done a lot of fixing and hacking in >the maven embedder before and after 6.7 beta, so might have broken something (or might have fixed since then)
>
>Milos

Sorry about the last mail, stupid outlook mail client...

Anyway, the issue still persists, although in a different way. The exception is gone, but the dependency doesn't show up in the libraries list, and the classes is not available through NBs intellisense (lots of red squiglies appear). The code compiles just dandy, so the external maven compiler finds the correct classes and artifacts without any problems. I will see if I can get something filed in the issue tracker.

Thanks Milos!

Magne
--
Magne Nordtveit <mn@...>
System Engineer
Offshore Simulator Centre AS

RE: Netbeans 6.7RC and dependencies with version ranges.

2009-05-18T02:43:14Z

From: Milos Kleint [mailto:mkleint@...]
Sent: 18 May 2009 10:41
To: user@...
Subject: Re: [mevenide-user] Netbeans 6.7RC and dependencies with version ranges.

please try with the latest dailies and file as issue if it persists, I've done a lot of fixing and hacking in the maven embedder before and after 6.7 beta, so might have broken something (or might have fixed since then)

Milos

Re: Netbeans 6.7RC and dependencies with version ranges.

2009-05-18T01:41:02Z

On Mon, May 18, 2009 at 10:09 AM, Magne Nordtveit <Magne.Nordtveit@...> wrote:

Hi,

I am having some problems with version dependencies with version ranges some of my projects...

When adding a dependency to a project with a version range both on junit at scope test, and a dependency with a version range at the compile scope. When expanding the dependency node, I get the following exception.

This is working fine in NB6.5 but not in any of the 6.7 releases. The artifact with the range, is NOT the artifact mentioned in the exception either, so I’m abit baffled...

I will try to reproduce it in a “controlled” environment for a bug report. Unless there is something that is already fixed, or something you guys (devs) are aware of.

java.lang.IllegalStateException: Artifact xml-apis:xml-apis:jar:1.3.04 is not resolved and is missing the file association in local repository. Please report at issue #140253.

                at org.netbeans.modules.maven.nodes.DependencyNode.<init>(DependencyNode.java:168)

                at org.netbeans.modules.maven.nodes.DependenciesNode$DependenciesChildren.createNodes(DependenciesNode.java:180)

                at org.netbeans.modules.maven.nodes.DependenciesNode$DependenciesChildren.createNodes(DependenciesNode.java:149)

                at org.openide.nodes.Children$Keys$KE.nodes(Children.java:1609)

                at org.openide.nodes.ChildrenArray.nodesFor(ChildrenArray.java:168)

                at org.openide.nodes.EntrySupport$Default$Info.nodes(EntrySupport.java:916)

                at org.openide.nodes.EntrySupport$Default.justComputeNodes(EntrySupport.java:244)

                at org.openide.nodes.ChildrenArray.nodes(ChildrenArray.java:101)

                at org.openide.nodes.EntrySupport$Default.getNodes(EntrySupport.java:173)

                at org.openide.nodes.EntrySupport$Default.getNodes(EntrySupport.java:219)

                at org.openide.nodes.Children.getNodes(Children.java:440)

                at org.openide.nodes.Children.findChild(Children.java:385)

                at org.openide.nodes.EntrySupport$Default.getNodes(EntrySupport.java:212)

                at org.openide.nodes.Children.getNodes(Children.java:472)

                at org.openide.nodes.FilterNode$Children$DefaultSupport.callGetNodesCount(FilterNode.java:1656)

                at org.openide.nodes.FilterNode$Children.getNodesCount(FilterNode.java:1608)

                at org.openide.explorer.view.TreeView$6.run(TreeView.java:912)

                at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:573)

[catch] at org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:1005)

With regards,

Magne

--

Magne Nordtveit <mn@...>

System Engineer

Offshore Simulator Centre AS

Netbeans 6.7RC and dependencies with version ranges.

2009-05-18T01:09:13Z

Hi,

I am having some problems with version dependencies with version ranges some of my projects...

When adding a dependency to a project with a version range both on junit at scope test, and a dependency with a version range at the compile scope. When expanding the dependency node, I get the following exception.

This is working fine in NB6.5 but not in any of the 6.7 releases. The artifact with the range, is NOT the artifact mentioned in the exception either, so I’m abit baffled...

I will try to reproduce it in a “controlled” environment for a bug report. Unless there is something that is already fixed, or something you guys (devs) are aware of.

java.lang.IllegalStateException: Artifact xml-apis:xml-apis:jar:1.3.04 is not resolved and is missing the file association in local repository. Please report at issue #140253.

at org.netbeans.modules.maven.nodes.DependencyNode.<init>(DependencyNode.java:168)

at org.netbeans.modules.maven.nodes.DependenciesNode$DependenciesChildren.createNodes(DependenciesNode.java:180)

at org.netbeans.modules.maven.nodes.DependenciesNode$DependenciesChildren.createNodes(DependenciesNode.java:149)

at org.openide.nodes.Children$Keys$KE.nodes(Children.java:1609)

at org.openide.nodes.ChildrenArray.nodesFor(ChildrenArray.java:168)

at org.openide.nodes.EntrySupport$Default$Info.nodes(EntrySupport.java:916)

at org.openide.nodes.EntrySupport$Default.justComputeNodes(EntrySupport.java:244)

at org.openide.nodes.ChildrenArray.nodes(ChildrenArray.java:101)

at org.openide.nodes.EntrySupport$Default.getNodes(EntrySupport.java:173)

at org.openide.nodes.EntrySupport$Default.getNodes(EntrySupport.java:219)

at org.openide.nodes.Children.getNodes(Children.java:440)

at org.openide.nodes.Children.findChild(Children.java:385)

at org.openide.nodes.EntrySupport$Default.getNodes(EntrySupport.java:212)

at org.openide.nodes.Children.getNodes(Children.java:472)

at org.openide.nodes.FilterNode$Children$DefaultSupport.callGetNodesCount(FilterNode.java:1656)

at org.openide.nodes.FilterNode$Children.getNodesCount(FilterNode.java:1608)

at org.openide.explorer.view.TreeView$6.run(TreeView.java:912)

at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:573)

[catch] at org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:1005)

With regards,

Magne

Magne Nordtveit <mn@...>

System Engineer

Offshore Simulator Centre AS

Re: 3.1.5 compatibility issue?

2009-03-10T10:34:17Z

Hi Milos,

No JCAPS is not part of the distro. In fact it is totally seperate and includes a specially modified NetBeans6.1 as it's IDE. For that reason I suspect that I would not be able to upgrade to 6.5. I guess if I have to stick with Eclipse for my Java development that wouldn't be a bad thing (I really prefer Eclipse over Netbeans anyway). I wasn't very hopeful that anyone here would be familiar with JCAPS, but it was worth a shot. I've already tried the JCAPS and Netbeans forums. One more resource that I can try.

Thanks again,
Dave Derry

Milos Kleint wrote:

Hello,

First I would suggest using NetBeans 6.5. I have no idea how the
JCAPS projects work (they are not part of the standard distro are
they?) and if they support 6.5 though..

I would suggest creating a thread dump while the "initialiazing
project" message gets stuck and file an issue against JCAPS.

Milos

On Tue, Mar 10, 2009 at 1:49 PM, dderry <Dave.Derry@equifax.com> wrote:
>
> Well hopefully someone here will have an idea. I'm using Netbeans 6.1 with
> the Maven plugin 3.1.5. I'm also working on JCAPS applications, while
> developing some functionality in independent jar files (hence the need for
> the Maven plugin). However, since installing the plugin, I am not able to
> open my JCAPS projects (some simple test JCAPS6 apps, and a couple of real
> JCAPS5.1.3 apps taht have been imported. I get an "Initializing project..."
> message that never goes away. After disabling the plugin I am able to open
> the projects.
>
> I have the plugin configured to use an external maven (2.0.8). Is the plugin
> somehow imcompatible with JCAPS?
>
> Thanks,
> Dave Derry
> --
> View this message in context: http://www.nabble.com/3.1.5-compatibility-issue--tp22433532p22433532.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: 3.1.5 compatibility issue?

2009-03-10T06:06:44Z

Hello,

First I would suggest using NetBeans 6.5. I have no idea how the
JCAPS projects work (they are not part of the standard distro are
they?) and if they support 6.5 though..

I would suggest creating a thread dump while the "initialiazing
project" message gets stuck and file an issue against JCAPS.

Milos

On Tue, Mar 10, 2009 at 1:49 PM, dderry <Dave.Derry@...> wrote:

>
> Well hopefully someone here will have an idea. I'm using Netbeans 6.1 with
> the Maven plugin 3.1.5. I'm also working on JCAPS applications, while
> developing some functionality in independent jar files (hence the need for
> the Maven plugin). However, since installing the plugin, I am not able to
> open my JCAPS projects (some simple test JCAPS6 apps, and a couple of real
> JCAPS5.1.3 apps taht have been imported. I get an "Initializing project..."
> message that never goes away. After disabling the plugin I am able to open
> the projects.
>
> I have the plugin configured to use an external maven (2.0.8). Is the plugin
> somehow imcompatible with JCAPS?
>
> Thanks,
> Dave Derry
> --
> View this message in context: http://www.nabble.com/3.1.5-compatibility-issue--tp22433532p22433532.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

3.1.5 compatibility issue?

2009-03-10T05:49:53Z

Well hopefully someone here will have an idea. I'm using Netbeans 6.1 with the Maven plugin 3.1.5. I'm also working on JCAPS applications, while developing some functionality in independent jar files (hence the need for the Maven plugin). However, since installing the plugin, I am not able to open my JCAPS projects (some simple test JCAPS6 apps, and a couple of real JCAPS5.1.3 apps taht have been imported. I get an "Initializing project..." message that never goes away. After disabling the plugin I am able to open the projects.

I have the plugin configured to use an external maven (2.0.8). Is the plugin somehow imcompatible with JCAPS?

Thanks,
Dave Derry

Re: Maven Webapp Archetyp and JEE 5

2009-03-05T12:47:24Z

Exactly, I've forgotten about it..

actually the new wizards in 6.7 M2+ are simple archetypes I've created
at mojo.codehaus.org, so they are accessible in 6.5 as well (and other
IDEs)

Milos

On Thu, Mar 5, 2009 at 9:30 PM, Marcin Kwapisz <mkwapisz@...> wrote:

>> you will have to change the web.xml file and change the version there.
>>
>> alternatively you can download the netbeans 7.0 M2 and use the new
>> project wizard that lest you select the j2ee level.
>>
>> Milos
>>
>> >
>> > I created a new maven project and used the Webapp Archetyp. In the
>> > properties, I saw that it selected J2EE Version 1.3 by default. How
>> can I
>> > change this to use JEE 5. I'm using Glassfish V2.1 as application
>> server.
> [Marcin Kwapisz]
> You can also create a project using JEE 5 web application archetype (see Archetypes from remote Maven Repositories)
>
> Regards
> --
> Marcin Kwapisz
> Division of Computer Networks
> Technical Univeristy of Lodz, Poland
>
>
>
>
> ---------------------------------------------------------------------
> 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: Maven Webapp Archetyp and JEE 5

2009-03-05T12:30:16Z

> you will have to change the web.xml file and change the version there.
>
> alternatively you can download the netbeans 7.0 M2 and use the new
> project wizard that lest you select the j2ee level.
>
> Milos
>
> >
> > I created a new maven project and used the Webapp Archetyp. In the
> > properties, I saw that it selected J2EE Version 1.3 by default. How
> can I
> > change this to use JEE 5. I'm using Glassfish V2.1 as application
> server.

[Marcin Kwapisz]
You can also create a project using JEE 5 web application archetype (see Archetypes from remote Maven Repositories)

Regards
--
Marcin Kwapisz
Division of Computer Networks
Technical Univeristy of Lodz, Poland

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

Re: Netbeans 6.7M2 - Missing J2EE support module

2009-03-05T11:40:58Z

It's issue 159717

Regards,

Cyrill

On 05.03.2009, at 20:11, Milos Kleint wrote:

> Great to hear it worked.
>
> please file it as issue in netbeans. org issue tracking against the
> "ide" component, subcomponent "ergonomics" so that the issue gets
> properly fixed in 6.7 final. The workaround I mentioned is not nice..
>
> Thanks
>
> Milos
>
> On Thu, Mar 5, 2009 at 7:55 PM, Cyrill Rüttimann <ruettimac@...>
> wrote:
>> Hi Milos,
>>
>> That helped. Now it works!
>>
>>
>> Thanks for the good work supporting maven inside of netbeans. I
>> really look
>> forward to the 6.7 release and the maven support improvements.
>>
>>
>> Regards,
>>
>> Cyrill
>>
>> On 05.03.2009, at 18:48, Milos Kleint wrote:
>>
>>> probably related to the "ergonomics" feature that disables stuff to
>>> keep the IDE slim.. It has it's weak points..
>>> the simpliest way is to get into the netbeans installation
>>> directory,
>>> delete the "ergonomics1" subfolder and restart the IDE.
>>>
>>> Regards
>>>
>>> Milos
>>>
>>> On Thu, Mar 5, 2009 at 6:01 PM, Cyrill Rüttimann
>>> <ruettimac@...> wrote:
>>>>
>>>> Hello,
>>>>
>>>> The following error is displayed on all J2EE project types (EJB/
>>>> EAR/WAR):
>>>>
>>>> You are missing the Maven J2EE support module in your
>>>> installation. That
>>>> means all J2EE related functionality (like Deployment, File
>>>> templates and
>>>> others) is missing. The most probable cause is that part of the
>>>> general
>>>> J2EE
>>>> support is missing as well. Please go to Tools/Plugins and
>>>> install the
>>>> J2EE
>>>> related plugins.
>>>>
>>>>
>>>> I am not able to download another maven plugin - I have already
>>>> all maven
>>>> plugins installed. Is this a well known error message?
>>>>
>>>>
>>>> Regards,
>>>>
>>>> Cyrill
>>>>
>>>> ---------------------------------------------------------------------
>>>> 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: Netbeans 6.7M2 - Missing J2EE support module

2009-03-05T11:11:54Z

Great to hear it worked.

please file it as issue in netbeans. org issue tracking against the
"ide" component, subcomponent "ergonomics" so that the issue gets
properly fixed in 6.7 final. The workaround I mentioned is not nice..

Thanks

Milos

On Thu, Mar 5, 2009 at 7:55 PM, Cyrill Rüttimann <ruettimac@...> wrote:

> Hi Milos,
>
> That helped. Now it works!
>
>
> Thanks for the good work supporting maven inside of netbeans. I really look
> forward to the 6.7 release and the maven support improvements.
>
>
> Regards,
>
> Cyrill
>
> On 05.03.2009, at 18:48, Milos Kleint wrote:
>
>> probably related to the "ergonomics" feature that disables stuff to
>> keep the IDE slim.. It has it's weak points..
>> the simpliest way is to get into the netbeans installation directory,
>> delete the "ergonomics1" subfolder and restart the IDE.
>>
>> Regards
>>
>> Milos
>>
>> On Thu, Mar 5, 2009 at 6:01 PM, Cyrill Rüttimann <ruettimac@...> wrote:
>>>
>>> Hello,
>>>
>>> The following error is displayed on all J2EE project types (EJB/EAR/WAR):
>>>
>>> You are missing the Maven J2EE support module in your installation. That
>>> means all J2EE related functionality (like Deployment, File templates and
>>> others) is missing. The most probable cause is that part of the general
>>> J2EE
>>> support is missing as well. Please go to Tools/Plugins and install the
>>> J2EE
>>> related plugins.
>>>
>>>
>>> I am not able to download another maven plugin - I have already all maven
>>> plugins installed. Is this a well known error message?
>>>
>>>
>>> Regards,
>>>
>>> Cyrill
>>>
>>> ---------------------------------------------------------------------
>>> 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: Netbeans 6.7M2 - Missing J2EE support module

2009-03-05T10:55:47Z

Hi Milos,

That helped. Now it works!

Thanks for the good work supporting maven inside of netbeans. I really
look forward to the 6.7 release and the maven support improvements.

Regards,

Cyrill

On 05.03.2009, at 18:48, Milos Kleint wrote:

> probably related to the "ergonomics" feature that disables stuff to
> keep the IDE slim.. It has it's weak points..
> the simpliest way is to get into the netbeans installation directory,
> delete the "ergonomics1" subfolder and restart the IDE.
>
> Regards
>
> Milos
>
> On Thu, Mar 5, 2009 at 6:01 PM, Cyrill Rüttimann <ruettimac@...>
> wrote:
>> Hello,
>>
>> The following error is displayed on all J2EE project types (EJB/EAR/
>> WAR):
>>
>> You are missing the Maven J2EE support module in your installation.
>> That
>> means all J2EE related functionality (like Deployment, File
>> templates and
>> others) is missing. The most probable cause is that part of the
>> general J2EE
>> support is missing as well. Please go to Tools/Plugins and install
>> the J2EE
>> related plugins.
>>
>>
>> I am not able to download another maven plugin - I have already all
>> maven
>> plugins installed. Is this a well known error message?
>>
>>
>> Regards,
>>
>> Cyrill
>>
>> ---------------------------------------------------------------------
>> 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: Netbeans 6.7M2 - Missing J2EE support module

2009-03-05T09:48:53Z

probably related to the "ergonomics" feature that disables stuff to
keep the IDE slim.. It has it's weak points..
the simpliest way is to get into the netbeans installation directory,
delete the "ergonomics1" subfolder and restart the IDE.

Regards

Milos

On Thu, Mar 5, 2009 at 6:01 PM, Cyrill Rüttimann <ruettimac@...> wrote:

> Hello,
>
> The following error is displayed on all J2EE project types (EJB/EAR/WAR):
>
> You are missing the Maven J2EE support module in your installation. That
> means all J2EE related functionality (like Deployment, File templates and
> others) is missing. The most probable cause is that part of the general J2EE
> support is missing as well. Please go to Tools/Plugins and install the J2EE
> related plugins.
>
>
> I am not able to download another maven plugin - I have already all maven
> plugins installed. Is this a well known error message?
>
>
> Regards,
>
> Cyrill
>
> ---------------------------------------------------------------------
> 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

Netbeans 6.7M2 - Missing J2EE support module

2009-03-05T09:01:06Z

Hello,

The following error is displayed on all J2EE project types (EJB/EAR/
WAR):

You are missing the Maven J2EE support module in your installation.
That means all J2EE related functionality (like Deployment, File
templates and others) is missing. The most probable cause is that part
of the general J2EE support is missing as well. Please go to Tools/
Plugins and install the J2EE related plugins.

I am not able to download another maven plugin - I have already all
maven plugins installed. Is this a well known error message?

Regards,

Cyrill

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

Re: Maven Webapp Archetyp and JEE 5

2009-03-05T08:08:47Z

you will have to change the web.xml file and change the version there.

alternatively you can download the netbeans 7.0 M2 and use the new
project wizard that lest you select the j2ee level.

Milos

On Thu, Mar 5, 2009 at 4:54 PM, m.s. <mathis.schwuchow@...> wrote:

>
> I created a new maven project and used the Webapp Archetyp. In the
> properties, I saw that it selected J2EE Version 1.3 by default. How can I
> change this to use JEE 5. I'm using Glassfish V2.1 as application server.
>
> Thanks,
> M.S.
> --
> View this message in context: http://www.nabble.com/Maven-Webapp-Archetyp-and-JEE-5-tp22354379p22354379.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

Maven Webapp Archetyp and JEE 5

2009-03-05T07:54:11Z

I created a new maven project and used the Webapp Archetyp. In the properties, I saw that it selected J2EE Version 1.3 by default. How can I change this to use JEE 5. I'm using Glassfish V2.1 as application server.

Thanks,
M.S.

Re: Debug problems with NB 6.5 and maven 2

2009-01-07T14:10:37Z

here : http://www.netbeans.org/issues/enter_bug.cgi?component=maven

Laurent.

On Wed, Jan 7, 2009 at 3:19 PM, Zoltan Farkas <zoly@...> wrote:

I would like to file a issue regarding this, where should where should I file this?

--zoly

From: Zoltan Farkas [mailto:zoly@...]
Sent: Thursday, December 18, 2008 4:51 PM

To: user@...
Subject: RE: [mevenide-user] Debug problems with NB 6.5 and maven 2

Ok, Figured it out myself, changed the Debug Test properties to:

jpda.listen=true
maven.surefire.debug="-Xdebug -Djava.compiler=none -Xnoagent -Xrunjdwp:transport=dt_socket,server=n,address=${jpda.address}"
jpda.stopclass=${packageClassName}
forkMode=once
test=${className}

and it works now, I gues it was related with my fork settings on the surefire plugin (for for every test).

however with argLine debugging did not work...

--zoly

From: Zoltan Farkas [mailto:zoly@...]
Sent: Thursday, December 18, 2008 2:14 PM
To: user@...
Subject: [mevenide-user] Debug problems with NB 6.5 and maven 2

I am new to m2/nb5 combination, and I have some problems getting debug working.

I am trying to debug a unit test and I am running it with: "debug test"

here is the output:

NetBeans: JPDA Listening Start...
JPDA Address: z:52116
Port:52116
NetBeans: Executing '/opt/apache-maven-2.0.9/bin/mvn -Djpda.listen=true -Djpda.stopclass=MyClassName -Djpda.address=52116 -DargLine=-Xdebug -Djava.compiler=none -Xnoagent -Xrunjdwp:transport=dt_socket,server=localhost,address=52116 -DforkMode=once -Dtest=EventExpertProcessorTest test-compile surefire:test'
NetBeans: JAVA_HOME =/usr/java

......

The debugger console displays: Listening on 52116

However I never see the debugger attaching to the process ....

Am I missing something? I had no problems doing this with M1/nb5.5

thanks

--zoly

RE: Debug problems with NB 6.5 and maven 2

2009-01-07T06:19:52Z

I would like to file a issue regarding this, where should where should I file this?

--zoly

From: Zoltan Farkas [mailto:zoly@...]
Sent: Thursday, December 18, 2008 4:51 PM
To: user@...
Subject: RE: [mevenide-user] Debug problems with NB 6.5 and maven 2

Ok, Figured it out myself, changed the Debug Test properties to:

jpda.listen=true
maven.surefire.debug="-Xdebug -Djava.compiler=none -Xnoagent -Xrunjdwp:transport=dt_socket,server=n,address=${jpda.address}"
jpda.stopclass=${packageClassName}
forkMode=once
test=${className}

and it works now, I gues it was related with my fork settings on the surefire plugin (for for every test).

however with argLine debugging did not work...

--zoly

From: Zoltan Farkas [mailto:zoly@...]
Sent: Thursday, December 18, 2008 2:14 PM
To: user@...
Subject: [mevenide-user] Debug problems with NB 6.5 and maven 2

I am new to m2/nb5 combination, and I have some problems getting debug working.

I am trying to debug a unit test and I am running it with: "debug test"

here is the output:

NetBeans: JPDA Listening Start...
JPDA Address: z:52116
Port:52116
NetBeans: Executing '/opt/apache-maven-2.0.9/bin/mvn -Djpda.listen=true -Djpda.stopclass=MyClassName -Djpda.address=52116 -DargLine=-Xdebug -Djava.compiler=none -Xnoagent -Xrunjdwp:transport=dt_socket,server=localhost,address=52116 -DforkMode=once -Dtest=EventExpertProcessorTest test-compile surefire:test'
NetBeans: JAVA_HOME =/usr/java

......

The debugger console displays: Listening on 52116

However I never see the debugger attaching to the process ....

Am I missing something? I had no problems doing this with M1/nb5.5

thanks

--zoly

Maven multi module project

2008-12-27T07:53:07Z

Hi,
I recently converted our projects to a maven multi-module project. I
have a webapp project which is the entrypoint for the whole
application which is one of the modules.

It works fine to deploy the application to the tomcat container when I
select the Webapp project, however what I want to do is to do the same
for the Multi-module project so all dependencies will be compiled if
changed aswell. However I cannot find any information on how to do
this in netbeans / maven.

I first tried to solve the problem by adding this to the multi-module
project pom:
<properties>
<netbeans.hint.packaging>war</netbeans.hint.packaging>
<netbeans.hint.deploy.server>Tomcat60</netbeans.hint.deploy.server>
</properties>

This made the deploy icon show up at least but it does not deploy the
war itself so I think Im way off here.

Any suggestions/help on how to handle this problem the right way would
be appreciated

Best regards,
Jonas Trollvik

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

RE: Debug problems with NB 6.5 and maven 2

2008-12-18T13:50:43Z

Ok, Figured it out myself, changed the Debug Test properties to:

and it works now, I gues it was related with my fork settings on the surefire plugin (for for every test).

however with argLine debugging did not work...

--zoly

From: Zoltan Farkas [mailto:zoly@...]
Sent: Thursday, December 18, 2008 2:14 PM
To: user@...
Subject: [mevenide-user] Debug problems with NB 6.5 and maven 2

I am new to m2/nb5 combination, and I have some problems getting debug working.

I am trying to debug a unit test and I am running it with: "debug test"

here is the output:

......

The debugger console displays: Listening on 52116

However I never see the debugger attaching to the process ....

Am I missing something? I had no problems doing this with M1/nb5.5

thanks

--zoly

Debug problems with NB 6.5 and maven 2

2008-12-18T11:14:15Z

I am new to m2/nb5 combination, and I have some problems getting debug working.

I am trying to debug a unit test and I am running it with: "debug test"

here is the output:

......

The debugger console displays: Listening on 52116

However I never see the debugger attaching to the process ....

Am I missing something? I had no problems doing this with M1/nb5.5

thanks

--zoly

RE: Deploy assembly to glassfish

2008-12-08T15:08:38Z

> a sample project demonstrating the setup, files as issue in netbeans
> issue tracking system
> (http://www.netbeans.org/issues/enter_bug.cgi?component=maven)
> would help.
[Marcin Kwapisz]
I will try to describe the problem and a workaround here.

1. ejb-plugin configuration

<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-ejb-plugin</artifactId>
<configuration>
<archive>
<manifest>
<addClasspath>true</addClasspath>
</manifest>
</archive>
<generateClient>true</generateClient>
<clientIncludes>
<clientInclude>pl/zsk/sos/ejb/endpoint/*Remote.class</clientInclude>
</clientIncludes>
<ejbVersion>3.0</ejbVersion>
</configuration>
</plugin>

2. Assembly plugin configuration
<plugin>
<artifactId>maven-assembly-plugin</artifactId>
<version>2.2-beta-2</version>
<executions>
<execution>
<id>create-ejb-module</id>
<phase>package</phase>
<goals>
<goal>single</goal>
</goals>
<configuration>
<archiverConfig>
<duplicateBehavior>fail</duplicateBehavior>
</archiverConfig>
<descriptors>
<descriptor>src/main/assembly/ejbModule.xml</descriptor>
</descriptors>
</configuration>
</execution>
</executions>
</plugin>

The ejb-plugin creates two jars:
PersonAccountModule-1.0-SNAPSHOT.jar
PersonAccountModule-1.0-SNAPSHOT-client.jar

The assembly-plugin creates third jar:
PersonAccountModule-1.0-SNAPSHOT-ejb-with-dependencies.jar
The name of this jar is ${project.build.finalName}-assembly_id.jar, where assembly_id is assembly id in ejbModule.xml descriptor (ejb-with-dependencies, see below)

3. Assembly descriptor (ejbModule.xml)

<?xml version="1.0" encoding="UTF-8"?>
<assembly>
<id>ejb-with-dependencies</id>
<formats>
<format>jar</format>
</formats>
<includeBaseDirectory>false</includeBaseDirectory>
<dependencySets>
<dependencySet>
<outputDirectory></outputDirectory>
<outputFileNameMapping></outputFileNameMapping>
<useProjectArtifact>false</useProjectArtifact>
<unpack>true</unpack>
<unpackOptions>
<excludes>
<exclude>**/META-INF/*.xml</exclude>
</excludes>
</unpackOptions>
<scope>runtime</scope>
<useTransitiveDependencies>false</useTransitiveDependencies>
</dependencySet>
</dependencySets>
<fileSets>
<fileSet>
<directory>target/classes</directory>
<outputDirectory></outputDirectory>
</fileSet>
</fileSets>
</assembly>

In that situation NB65 tries to deploy on Glassfish PersonAccountModule-1.0-SNAPSHOT.jar, what is wrong.
The workaround is very simple -> assembly_id in assembly descriptor should be empty
...
<assembly>
<id></id>
<formats>...

PersonAccountModule-1.0-SNAPSHOT.jar created by the ejb-plugin is overwritten by a jar created by the assembly-plugin now, so the correct one is deployed on Glassfish.

I do not know if it is correct to have empty id in assembly descriptor, but it works.

Regards
--
Marcin Kwapisz
Division of Computer Networks
Technical Univeristy of Lodz, Poland

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

Re: Deploy assembly to glassfish

2008-12-08T05:44:38Z

a sample project demonstrating the setup, files as issue in netbeans
issue tracking system
(http://www.netbeans.org/issues/enter_bug.cgi?component=maven)
would help.

Milos

On Mon, Dec 8, 2008 at 2:35 PM, Marcin Kwapisz <mkwapisz@...> wrote:

>> One option may be to use the Maven GlassFish plugin, see
>>
>> https://maven-glassfish-plugin.dev.java.net/
>
> [Marcin Kwapisz]
> Yes, I think it could be the solution. I will check that plugin. Thanks.
>
> Maven support was integrated into NB6.5. I think it should be possible to choose what artifact is deployed to glassfish from IDE.
> Below is log from my NB. PersonAccountModule-1.0-SNAPSHOT.jar is chosen by default. This is wrong jar, due to missing configuration which is added during assembly process.
>
> NetBeans: Deploying on GlassFish V2
> debug mode: false
> force redeploy: true
> Checking for missing drivers
> Start registering the project's server resources
> Finished registering server resources
> Distributing D:\JavaProg\MySamples\EJB\Samplev7\JEEMavenProject2\PersonAccountModule\target\PersonAccountModule-1.0-SNAPSHOT.jar to [localhost:4848_server]
> Start registering the project's server resources
> Finished registering server resources
> deployment started : 0%
> Deploying application in domain failed; Error loading deployment descriptors for module [PersonAccountModule-1.0-SNAPSHOT] -- Invalid ejb jar [D:\AppServer\glassfish-v2ur2\domains\domain1\applications\j2ee-modules\PersonAccountModule-1.0-SNAPSHOT]: it contains zero ejb.
>
>
> ---------------------------------------------------------------------
> 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: Deploy assembly to glassfish

2008-12-08T05:35:08Z

> One option may be to use the Maven GlassFish plugin, see
>
> https://maven-glassfish-plugin.dev.java.net/

[Marcin Kwapisz]
Yes, I think it could be the solution. I will check that plugin. Thanks.

Maven support was integrated into NB6.5. I think it should be possible to choose what artifact is deployed to glassfish from IDE.
Below is log from my NB. PersonAccountModule-1.0-SNAPSHOT.jar is chosen by default. This is wrong jar, due to missing configuration which is added during assembly process.

NetBeans: Deploying on GlassFish V2
debug mode: false
force redeploy: true
Checking for missing drivers
Start registering the project's server resources
Finished registering server resources
Distributing D:\JavaProg\MySamples\EJB\Samplev7\JEEMavenProject2\PersonAccountModule\target\PersonAccountModule-1.0-SNAPSHOT.jar to [localhost:4848_server]
Start registering the project's server resources
Finished registering server resources
deployment started : 0%
Deploying application in domain failed; Error loading deployment descriptors for module [PersonAccountModule-1.0-SNAPSHOT] -- Invalid ejb jar [D:\AppServer\glassfish-v2ur2\domains\domain1\applications\j2ee-modules\PersonAccountModule-1.0-SNAPSHOT]: it contains zero ejb.

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

Re: Deploy assembly to glassfish

2008-12-08T03:06:27Z

Hi,

On Mon, Dec 08, 2008 at 11:58:08AM +0100, Marcin Kwapisz wrote:
> Is it possible to deploy jar (ejb) created by assembly plugin to glassfish server?
> Now, when I choose "Run project", maven tries to deploy jar package without dependencies (and of course fails). The only one solution is to deploy assembled jar package manually.

One option may be to use the Maven GlassFish plugin, see

https://maven-glassfish-plugin.dev.java.net/

HTH, Wouter van Reeven

--

People: "If she weighs the same as a Duck, she's made of wood!"
Sir Bedevere: "And therefore...?"

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

Deploy assembly to glassfish

2008-12-08T02:58:08Z

Hi,
Is it possible to deploy jar (ejb) created by assembly plugin to glassfish server?
Now, when I choose "Run project", maven tries to deploy jar package without dependencies (and of course fails). The only one solution is to deploy assembled jar package manually.

My assembly plugin configuration is as follows:
<plugin>
<artifactId>maven-assembly-plugin</artifactId>
<version>2.2-beta-2</version>
<executions>
<execution>
<id>create-ejb-module</id>
<phase>package</phase>
<goals>
<goal>single</goal>
</goals>
<configuration>
<archiverConfig>
<duplicateBehavior>fail</duplicateBehavior>
</archiverConfig>
<descriptors>
<descriptor>src/main/assembly/ejbModule.xml</descriptor>
</descriptors>
<archive>
</archive>
</configuration>
</execution>
</executions>
</plugin>

Thanks in advance
Regards
--
Marcin Kwapisz
Division of Computer Networks
Technical Univeristy of Lodz, Poland

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

RE: mevenide 4.0.5 and runtime classpathScope

2008-11-25T23:52:21Z

Ok, that's great.

Thanks,
Hartmut Lang

-----Original Message-----
From: Milos Kleint [mailto:mkleint@...]
Sent: Mittwoch, 26. November 2008 08:49
To: user@...
Subject: Re: [mevenide-user] mevenide 4.0.5 and runtime classpathScope

either it becomes the default in the exec plugin or the default action
mappings will make it a default in the IDE. either way you should not
need to tweak anything in the nbactions.xml file.

Milos

On Wed, Nov 26, 2008 at 8:45 AM, Hartmut Lang
<hartmut.lang@...> wrote:

> Milos,
>
> Thanks for this info.
> Do you expect "runtime" to be the default classpathScope in the next
> release of exec-maven plugin?
> Or do we have to add that to our nbactions.xml file?
>
> Regards,
> Hartmut Lang
>
> -----Original Message-----
> From: Milos Kleint [mailto:mkleint@...]
> Sent: Dienstag, 25. November 2008 14:06
> To: user@...
> Subject: Re: [mevenide-user] mevenide 4.0.5 and runtime classpathScope
>
> On Tue, Nov 25, 2008 at 1:11 PM, Hartmut Lang
> <hartmut.lang@...> wrote:
>> Milos,
>>
>> We are using netbeans 6.5 with mevenide 4.0.5.
>> We are facing the problem that on running a maven-project the
> exec-maven
>> plugin is only called with "compile" as classpathScope. And we would
>> need "runtime".
>> I also saw that you fixed an exec-maven plugin issue related to using
>> "runtime".
>> Do you plan to introduce "runtime" classpathScope in your mevenide
>> netbeans plugin?
>
> once the exec plugin gets released, then the maven support will start
> using the new version by default and will use the correct scope. I'm
> not even sure why compile was chosen as default scope, doesn't make
> much sense to me..
>
> the current workaround for now is to use the test scope instead of
> runtime in case you need it. (test extends runtime)
>
> in 7.0 codebase, I've fixed the issue of main() classes in test
> sources and the test scope for the exec plugin is added there by
> default.
>
> Regards
>
> Milos
>
>>
>>
>> Regards,
>> Hartmut
>>
>> ---------------------------------------------------------------------
>> 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: mevenide 4.0.5 and runtime classpathScope

2008-11-25T23:48:51Z

either it becomes the default in the exec plugin or the default action
mappings will make it a default in the IDE. either way you should not
need to tweak anything in the nbactions.xml file.

Milos

On Wed, Nov 26, 2008 at 8:45 AM, Hartmut Lang <hartmut.lang@...> wrote:

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

RE: mevenide 4.0.5 and runtime classpathScope

2008-11-25T23:45:10Z

Milos,

Thanks for this info.
Do you expect "runtime" to be the default classpathScope in the next
release of exec-maven plugin?
Or do we have to add that to our nbactions.xml file?

Regards,
Hartmut Lang

-----Original Message-----
From: Milos Kleint [mailto:mkleint@...]
Sent: Dienstag, 25. November 2008 14:06
To: user@...
Subject: Re: [mevenide-user] mevenide 4.0.5 and runtime classpathScope

On Tue, Nov 25, 2008 at 1:11 PM, Hartmut Lang
<hartmut.lang@...> wrote:
> Milos,
>
> We are using netbeans 6.5 with mevenide 4.0.5.
> We are facing the problem that on running a maven-project the
exec-maven
> plugin is only called with "compile" as classpathScope. And we would
> need "runtime".
> I also saw that you fixed an exec-maven plugin issue related to using
> "runtime".
> Do you plan to introduce "runtime" classpathScope in your mevenide
> netbeans plugin?

once the exec plugin gets released, then the maven support will start
using the new version by default and will use the correct scope. I'm
not even sure why compile was chosen as default scope, doesn't make
much sense to me..

the current workaround for now is to use the test scope instead of
runtime in case you need it. (test extends runtime)

in 7.0 codebase, I've fixed the issue of main() classes in test
sources and the test scope for the exec plugin is added there by
default.

Regards

Milos

>
>
> Regards,
> Hartmut
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
> http://xircles.codehaus.org/manage_email
>
>
>

Re: mevenide 4.0.5 and runtime classpathScope

2008-11-25T05:05:38Z

On Tue, Nov 25, 2008 at 1:11 PM, Hartmut Lang <hartmut.lang@...> wrote:

> Milos,
>
> We are using netbeans 6.5 with mevenide 4.0.5.
> We are facing the problem that on running a maven-project the exec-maven
> plugin is only called with "compile" as classpathScope. And we would
> need "runtime".
> I also saw that you fixed an exec-maven plugin issue related to using
> "runtime".
> Do you plan to introduce "runtime" classpathScope in your mevenide
> netbeans plugin?

once the exec plugin gets released, then the maven support will start
using the new version by default and will use the correct scope. I'm
not even sure why compile was chosen as default scope, doesn't make
much sense to me..

the current workaround for now is to use the test scope instead of
runtime in case you need it. (test extends runtime)

in 7.0 codebase, I've fixed the issue of main() classes in test
sources and the test scope for the exec plugin is added there by
default.

Regards

Milos

>
>
> Regards,
> Hartmut
>
> ---------------------------------------------------------------------
> 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

mevenide 4.0.5 and runtime classpathScope

2008-11-25T04:11:48Z

Milos,

We are using netbeans 6.5 with mevenide 4.0.5.
We are facing the problem that on running a maven-project the exec-maven
plugin is only called with "compile" as classpathScope. And we would
need "runtime".
I also saw that you fixed an exec-maven plugin issue related to using
"runtime".
Do you plan to introduce "runtime" classpathScope in your mevenide
netbeans plugin?

Regards,
Hartmut

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

Re: [ANN] Maven 1.1 & Netbeans 6

2008-11-24T09:46:02Z

Eric,

I never was able to get Netbeans 6 running right (Sun's fault, not yours). Now that 6.5 is out, I have downloaded your mevenide1 port and installed it. The build process works fine, but the build JDK is not connecting to the code complete JDK as it does in NB 5.5.

For example, I have a project that builds on JDK 1.5. In Netbeans 5.5, the IDE picks this up and uses JDK 1.5 for error checking / code complete. In Netbeans 6.5, the IDE keeps using the default JDK (the one NB runs on), which in my case is JDK 1.6.

Do you have any idea for how this problem can be solved? I'd love to switch to Maven 2, but the company I work for will not switch.

Thanks,

Jeff Costello

Eric Hartmann-2 wrote:

Hi everybody,

The mevenide plugin for Netbeans 6.0 has been released and it's working with
Netbeans 6.0rc1 and 6.0rc2.
You can download all the nbm here :
http://mevenide.codehaus.org/download/mevenide-netbeans-1.2.zip or use the
following update center :
http://mevenide.codehaus.org/nbm_release/NBM_AutoUpdate_60.xml
This plugin requires Maven 1.1 and the j2ee and cargo part are no more
maintained.
A remaning bug has not been solved and sometimes a project is empty after
Netbeans restart you need to close and reopen the project to use it.

Have a nice day,

-eric