call for action: test the upcoming new version 3.1

View: New views
19 Messages — Rating Filter:   Alert me  

call for action: test the upcoming new version 3.1

by Milos Kleint-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hello everybody,

I'd like to ask you to become beta testers for the new 3.1 version of
mevenide. It's packed with new features, includes many fixes..
Some highlights:
1. remote repository browsing and in general incorporating remote
repositories content in the UI
2. latest 2.1-SNAPSHOT maven embedder bundled, most problems caused by
the old embedder should be gone.
3. j2ee integration improved - deployment of ears, webframeworks can
be added to maven projects.
4. the maven build can be examined visually in terms of browsing what
gets executed. (new action on output window toolbar)
5. alternate configurations for action mappings, allow to load the
project with some profiles activated.
6.probably more and more stuff I can't recall right now.

Testing it out is really easy.

Installing the bits is really easy.
1. download the 6.1 RC (well, 6.0 final would do as well)
2. download the zip file with maven support nbm files from
http://deadlock.netbeans.org/hudson/job/mevenide/lastSuccessfulBuild/artifact/mevenide-AU-SNAPSHOT.zip
3. start the IDE, preferably with the --userdir <temp location> switch
to to be on the safe side..
4. install the nbm files from the zip via Tools/Plugins dialog
(Downloaded tab). That should be it.

I'm interested in bug reports, comments on usability, general rants.
However I'd like to push the bits to the default netbeans update
center for 6.0 and 6.1 in a week or two, so I'm primarily looking for
showstoppers. The upgrade to new maven embedder should fix old
problems but could have introduced new ones. I'd like make sure all or
most projects load correctly. The more complex setup you have the
better.

Regards and thanks..

Milos

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

    http://xircles.codehaus.org/manage_email



Re: call for action: test the upcoming new version 3.1

by Andreas Andreou :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi, is it normal that Maven [3.0.12] also adds itself to the installation list
(probably because some of the nbms in the zip depend on it?)

On Mon, Apr 21, 2008 at 1:00 PM, Milos Kleint <mkleint@...> wrote:

> Hello everybody,
>
>  I'd like to ask you to become beta testers for the new 3.1 version of
>  mevenide. It's packed with new features, includes many fixes..
>  Some highlights:
>  1. remote repository browsing and in general incorporating remote
>  repositories content in the UI
>  2. latest 2.1-SNAPSHOT maven embedder bundled, most problems caused by
>  the old embedder should be gone.
>  3. j2ee integration improved - deployment of ears, webframeworks can
>  be added to maven projects.
>  4. the maven build can be examined visually in terms of browsing what
>  gets executed. (new action on output window toolbar)
>  5. alternate configurations for action mappings, allow to load the
>  project with some profiles activated.
>  6.probably more and more stuff I can't recall right now.
>
>  Testing it out is really easy.
>
>  Installing the bits is really easy.
>  1. download the 6.1 RC (well, 6.0 final would do as well)
>  2. download the zip file with maven support nbm files from
>  http://deadlock.netbeans.org/hudson/job/mevenide/lastSuccessfulBuild/artifact/mevenide-AU-SNAPSHOT.zip
>  3. start the IDE, preferably with the --userdir <temp location> switch
>  to to be on the safe side..
>  4. install the nbm files from the zip via Tools/Plugins dialog
>  (Downloaded tab). That should be it.
>
>  I'm interested in bug reports, comments on usability, general rants.
>  However I'd like to push the bits to the default netbeans update
>  center for 6.0 and 6.1 in a week or two, so I'm primarily looking for
>  showstoppers. The upgrade to new maven embedder should fix old
>  problems but could have introduced new ones. I'd like make sure all or
>  most projects load correctly. The more complex setup you have the
>  better.
>
>  Regards and thanks..
>
>  Milos
>
>  ---------------------------------------------------------------------
>  To unsubscribe from this list, please visit:
>
>     http://xircles.codehaus.org/manage_email
>
>
>



--
Andreas Andreou - andyhot@... - http://blog.andyhot.gr
Tapestry / Tacos developer
Open Source / JEE Consulting

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

    http://xircles.codehaus.org/manage_email



Re: call for action: test the upcoming new version 3.1

by Milos Kleint-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

that would be a bug in the plugin manager in 6.0. I think the 6.1
version should be fine. A workaround is to temporarily disable all
update centers when installing teh modules (the Settings tab)

Milos

On Mon, Apr 21, 2008 at 12:17 PM, Andreas Andreou <andreoua@...> wrote:

> Hi, is it normal that Maven [3.0.12] also adds itself to the installation list
>  (probably because some of the nbms in the zip depend on it?)
>
>
>
>  On Mon, Apr 21, 2008 at 1:00 PM, Milos Kleint <mkleint@...> wrote:
>  > Hello everybody,
>  >
>  >  I'd like to ask you to become beta testers for the new 3.1 version of
>  >  mevenide. It's packed with new features, includes many fixes..
>  >  Some highlights:
>  >  1. remote repository browsing and in general incorporating remote
>  >  repositories content in the UI
>  >  2. latest 2.1-SNAPSHOT maven embedder bundled, most problems caused by
>  >  the old embedder should be gone.
>  >  3. j2ee integration improved - deployment of ears, webframeworks can
>  >  be added to maven projects.
>  >  4. the maven build can be examined visually in terms of browsing what
>  >  gets executed. (new action on output window toolbar)
>  >  5. alternate configurations for action mappings, allow to load the
>  >  project with some profiles activated.
>  >  6.probably more and more stuff I can't recall right now.
>  >
>  >  Testing it out is really easy.
>  >
>  >  Installing the bits is really easy.
>  >  1. download the 6.1 RC (well, 6.0 final would do as well)
>  >  2. download the zip file with maven support nbm files from
>  >  http://deadlock.netbeans.org/hudson/job/mevenide/lastSuccessfulBuild/artifact/mevenide-AU-SNAPSHOT.zip
>  >  3. start the IDE, preferably with the --userdir <temp location> switch
>  >  to to be on the safe side..
>  >  4. install the nbm files from the zip via Tools/Plugins dialog
>  >  (Downloaded tab). That should be it.
>  >
>  >  I'm interested in bug reports, comments on usability, general rants.
>  >  However I'd like to push the bits to the default netbeans update
>  >  center for 6.0 and 6.1 in a week or two, so I'm primarily looking for
>  >  showstoppers. The upgrade to new maven embedder should fix old
>  >  problems but could have introduced new ones. I'd like make sure all or
>  >  most projects load correctly. The more complex setup you have the
>  >  better.
>  >
>  >  Regards and thanks..
>  >
>  >  Milos
>  >
>  >  ---------------------------------------------------------------------
>  >  To unsubscribe from this list, please visit:
>  >
>  >     http://xircles.codehaus.org/manage_email
>  >
>  >
>  >
>
>
>
>  --
>  Andreas Andreou - andyhot@... - http://blog.andyhot.gr
>  Tapestry / Tacos developer
>  Open Source / JEE Consulting
>
>  ---------------------------------------------------------------------
>  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: call for action: test the upcoming new version 3.1

by Andreas Andreou :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

That was 6.1RC1 running in a newly created userdir...
I went on with the install and the plugin manager shows the 3.1
version as installed,
so ...

On Mon, Apr 21, 2008 at 2:03 PM, Milos Kleint <mkleint@...> wrote:

> that would be a bug in the plugin manager in 6.0. I think the 6.1
>  version should be fine. A workaround is to temporarily disable all
>  update centers when installing teh modules (the Settings tab)
>
>  Milos
>
>
>
>  On Mon, Apr 21, 2008 at 12:17 PM, Andreas Andreou <andreoua@...> wrote:
>  > Hi, is it normal that Maven [3.0.12] also adds itself to the installation list
>  >  (probably because some of the nbms in the zip depend on it?)
>  >
>  >
>  >
>  >  On Mon, Apr 21, 2008 at 1:00 PM, Milos Kleint <mkleint@...> wrote:
>  >  > Hello everybody,
>  >  >
>  >  >  I'd like to ask you to become beta testers for the new 3.1 version of
>  >  >  mevenide. It's packed with new features, includes many fixes..
>  >  >  Some highlights:
>  >  >  1. remote repository browsing and in general incorporating remote
>  >  >  repositories content in the UI
>  >  >  2. latest 2.1-SNAPSHOT maven embedder bundled, most problems caused by
>  >  >  the old embedder should be gone.
>  >  >  3. j2ee integration improved - deployment of ears, webframeworks can
>  >  >  be added to maven projects.
>  >  >  4. the maven build can be examined visually in terms of browsing what
>  >  >  gets executed. (new action on output window toolbar)
>  >  >  5. alternate configurations for action mappings, allow to load the
>  >  >  project with some profiles activated.
>  >  >  6.probably more and more stuff I can't recall right now.
>  >  >
>  >  >  Testing it out is really easy.
>  >  >
>  >  >  Installing the bits is really easy.
>  >  >  1. download the 6.1 RC (well, 6.0 final would do as well)
>  >  >  2. download the zip file with maven support nbm files from
>  >  >  http://deadlock.netbeans.org/hudson/job/mevenide/lastSuccessfulBuild/artifact/mevenide-AU-SNAPSHOT.zip
>  >  >  3. start the IDE, preferably with the --userdir <temp location> switch
>  >  >  to to be on the safe side..
>  >  >  4. install the nbm files from the zip via Tools/Plugins dialog
>  >  >  (Downloaded tab). That should be it.
>  >  >
>  >  >  I'm interested in bug reports, comments on usability, general rants.
>  >  >  However I'd like to push the bits to the default netbeans update
>  >  >  center for 6.0 and 6.1 in a week or two, so I'm primarily looking for
>  >  >  showstoppers. The upgrade to new maven embedder should fix old
>  >  >  problems but could have introduced new ones. I'd like make sure all or
>  >  >  most projects load correctly. The more complex setup you have the
>  >  >  better.
>  >  >
>  >  >  Regards and thanks..
>  >  >
>  >  >  Milos
>  >  >
>  >  >  ---------------------------------------------------------------------
>  >  >  To unsubscribe from this list, please visit:
>  >  >
>  >  >     http://xircles.codehaus.org/manage_email
>  >  >
>  >  >
>  >  >
>  >
>  >
>  >
>  >  --
>  >  Andreas Andreou - andyhot@... - http://blog.andyhot.gr
>  >  Tapestry / Tacos developer
>  >  Open Source / JEE Consulting
>  >
>  >  ---------------------------------------------------------------------
>  >  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
>
>
>



--
Andreas Andreou - andyhot@... - http://blog.andyhot.gr
Tapestry / Tacos developer
Open Source / JEE Consulting

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

    http://xircles.codehaus.org/manage_email



Re: call for action: test the upcoming new version 3.1

by Anuradha G :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Some  more highlights:
  1.Editor  search class Dependency Quick fix hint
  2.Artifact SCM  checkout action using pluggable SCM providers for checking out projects from various source code management                 systems (SCM).
  3.Find Usage of Artifact in open projects and local repository
  4.Repository browser "Add as Dependency"
 


--
Anuradha G 
{Mevenide Commiter}


On Mon, Apr 21, 2008 at 3:30 PM, Milos Kleint <mkleint@...> wrote:
Hello everybody,

I'd like to ask you to become beta testers for the new 3.1 version of
mevenide. It's packed with new features, includes many fixes..
Some highlights:
1. remote repository browsing and in general incorporating remote
repositories content in the UI
2. latest 2.1-SNAPSHOT maven embedder bundled, most problems caused by
the old embedder should be gone.
3. j2ee integration improved - deployment of ears, webframeworks can
be added to maven projects.
4. the maven build can be examined visually in terms of browsing what
gets executed. (new action on output window toolbar)
5. alternate configurations for action mappings, allow to load the
project with some profiles activated.
6.probably more and more stuff I can't recall right now.

Testing it out is really easy.

Installing the bits is really easy.
1. download the 6.1 RC (well, 6.0 final would do as well)
2. download the zip file with maven support nbm files from
http://deadlock.netbeans.org/hudson/job/mevenide/lastSuccessfulBuild/artifact/mevenide-AU-SNAPSHOT.zip
3. start the IDE, preferably with the --userdir <temp location> switch
to to be on the safe side..
4. install the nbm files from the zip via Tools/Plugins dialog
(Downloaded tab). That should be it.

I'm interested in bug reports, comments on usability, general rants.
However I'd like to push the bits to the default netbeans update
center for 6.0 and 6.1 in a week or two, so I'm primarily looking for
showstoppers. The upgrade to new maven embedder should fix old
problems but could have introduced new ones. I'd like make sure all or
most projects load correctly. The more complex setup you have the
better.

Regards and thanks..

Milos

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

   http://xircles.codehaus.org/manage_email







Re: call for action: test the upcoming new version 3.1

by Milos Kleint-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

yeah. I've just tried and for me it showed it needs to install
Maven[3.0.12] in addition to the downloaded bits. When I proceeded
with the install it did install 3.1... The workaround I mention is
necessary in 6.0 I think where one would not be able to install the
downloaded modules at all.

Milos

On Mon, Apr 21, 2008 at 1:10 PM, Andreas Andreou <andreoua@...> wrote:

> That was 6.1RC1 running in a newly created userdir...
>  I went on with the install and the plugin manager shows the 3.1
>  version as installed,
>  so ...
>
>
>
>  On Mon, Apr 21, 2008 at 2:03 PM, Milos Kleint <mkleint@...> wrote:
>  > that would be a bug in the plugin manager in 6.0. I think the 6.1
>  >  version should be fine. A workaround is to temporarily disable all
>  >  update centers when installing teh modules (the Settings tab)
>  >
>  >  Milos
>  >
>  >
>  >
>  >  On Mon, Apr 21, 2008 at 12:17 PM, Andreas Andreou <andreoua@...> wrote:
>  >  > Hi, is it normal that Maven [3.0.12] also adds itself to the installation list
>  >  >  (probably because some of the nbms in the zip depend on it?)
>  >  >
>  >  >
>  >  >
>  >  >  On Mon, Apr 21, 2008 at 1:00 PM, Milos Kleint <mkleint@...> wrote:
>  >  >  > Hello everybody,
>  >  >  >
>  >  >  >  I'd like to ask you to become beta testers for the new 3.1 version of
>  >  >  >  mevenide. It's packed with new features, includes many fixes..
>  >  >  >  Some highlights:
>  >  >  >  1. remote repository browsing and in general incorporating remote
>  >  >  >  repositories content in the UI
>  >  >  >  2. latest 2.1-SNAPSHOT maven embedder bundled, most problems caused by
>  >  >  >  the old embedder should be gone.
>  >  >  >  3. j2ee integration improved - deployment of ears, webframeworks can
>  >  >  >  be added to maven projects.
>  >  >  >  4. the maven build can be examined visually in terms of browsing what
>  >  >  >  gets executed. (new action on output window toolbar)
>  >  >  >  5. alternate configurations for action mappings, allow to load the
>  >  >  >  project with some profiles activated.
>  >  >  >  6.probably more and more stuff I can't recall right now.
>  >  >  >
>  >  >  >  Testing it out is really easy.
>  >  >  >
>  >  >  >  Installing the bits is really easy.
>  >  >  >  1. download the 6.1 RC (well, 6.0 final would do as well)
>  >  >  >  2. download the zip file with maven support nbm files from
>  >  >  >  http://deadlock.netbeans.org/hudson/job/mevenide/lastSuccessfulBuild/artifact/mevenide-AU-SNAPSHOT.zip
>  >  >  >  3. start the IDE, preferably with the --userdir <temp location> switch
>  >  >  >  to to be on the safe side..
>  >  >  >  4. install the nbm files from the zip via Tools/Plugins dialog
>  >  >  >  (Downloaded tab). That should be it.
>  >  >  >
>  >  >  >  I'm interested in bug reports, comments on usability, general rants.
>  >  >  >  However I'd like to push the bits to the default netbeans update
>  >  >  >  center for 6.0 and 6.1 in a week or two, so I'm primarily looking for
>  >  >  >  showstoppers. The upgrade to new maven embedder should fix old
>  >  >  >  problems but could have introduced new ones. I'd like make sure all or
>  >  >  >  most projects load correctly. The more complex setup you have the
>  >  >  >  better.
>  >  >  >
>  >  >  >  Regards and thanks..
>  >  >  >
>  >  >  >  Milos
>  >  >  >
>  >  >  >  ---------------------------------------------------------------------
>  >  >  >  To unsubscribe from this list, please visit:
>  >  >  >
>  >  >  >     http://xircles.codehaus.org/manage_email
>  >  >  >
>  >  >  >
>  >  >  >
>  >  >
>  >  >
>  >  >
>  >  >  --
>  >  >  Andreas Andreou - andyhot@... - http://blog.andyhot.gr
>  >  >  Tapestry / Tacos developer
>  >  >  Open Source / JEE Consulting
>  >  >
>  >  >  ---------------------------------------------------------------------
>  >  >  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
>  >
>  >
>  >
>
>
>
>  --
>  Andreas Andreou - andyhot@... - http://blog.andyhot.gr
>  Tapestry / Tacos developer
>  Open Source / JEE Consulting
>
>  ---------------------------------------------------------------------
>  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



AW: call for action: test the upcoming new version 3.1

by Mohni, Daniel :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hello Milos

I installed the latest build for testing...

I had one problem after the restart of Netbeans, some of my open project showed up
as invalid, after resaving the pom, they are fine. maybe an encoding problem somewhere....

the other problem I now have, is that I use the assembly-plugin to get my application
to look like it has to, copying files from different locations to the right destination

eg. I have a config folder at /src/main/config (then it shows up in Netbeans) and I copy
this one to target/<application>/config any some other stuff....

This worked without any problems the projects are run the old way, but is a bit slow I agree...

but to get my project to run the new way I have to make a lot of workarounds when I load files
or reference some other artefacts. We had to do that in the old maven1 times....

No I would like to have an option to swich from the two run types, in the config panel

- slow jar run
- fast exec:exec

[] use fast execution mode...

something like this

Regards

Daniel

I go back to 3.0.12 to get my current work out on time...



> -----Ursprüngliche Nachricht-----
> Von: Milos Kleint [mailto:mkleint@...]
> Gesendet: Montag, 21. April 2008 12:01
> An: Mevenide
> Betreff: [mevenide-user] call for action: test the upcoming new version 3.1
>
> Hello everybody,
>
> I'd like to ask you to become beta testers for the new 3.1 version of
> mevenide. It's packed with new features, includes many fixes..
> Some highlights:
> 1. remote repository browsing and in general incorporating remote
> repositories content in the UI
> 2. latest 2.1-SNAPSHOT maven embedder bundled, most problems caused by
> the old embedder should be gone.
> 3. j2ee integration improved - deployment of ears, webframeworks can
> be added to maven projects.
> 4. the maven build can be examined visually in terms of browsing what
> gets executed. (new action on output window toolbar)
> 5. alternate configurations for action mappings, allow to load the
> project with some profiles activated.
> 6.probably more and more stuff I can't recall right now.
>
> Testing it out is really easy.
>
> Installing the bits is really easy.
> 1. download the 6.1 RC (well, 6.0 final would do as well)
> 2. download the zip file with maven support nbm files from
> http://deadlock.netbeans.org/hudson/job/mevenide/lastSuccessfulBuild/artifact/meve
> nide-AU-SNAPSHOT.zip
> 3. start the IDE, preferably with the --userdir <temp location> switch
> to to be on the safe side..
> 4. install the nbm files from the zip via Tools/Plugins dialog
> (Downloaded tab). That should be it.
>
> I'm interested in bug reports, comments on usability, general rants.
> However I'd like to push the bits to the default netbeans update
> center for 6.0 and 6.1 in a week or two, so I'm primarily looking for
> showstoppers. The upgrade to new maven embedder should fix old
> problems but could have introduced new ones. I'd like make sure all or
> most projects load correctly. The more complex setup you have the
> better.
>
> Regards and thanks..
>
> Milos
>
> ---------------------------------------------------------------------
> 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



AW: call for action: test the upcoming new version 3.1

by Mohni, Daniel :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

I answer myself....

> the other problem I now have, is that I use the assembly-plugin to get
my
> application
> to look like it has to, copying files from different locations to the
right
> destination
>
> eg. I have a config folder at /src/main/config (then it shows up in
Netbeans) and
> I copy
> this one to target/<application>/config any some other stuff....
>

setting the workdir to src/main helps for starting...

Regards
Daniel


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

    http://xircles.codehaus.org/manage_email



Re: call for action: test the upcoming new version 3.1

by Milos Kleint-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

On Tue, Apr 22, 2008 at 6:32 AM, Mohni, Daniel
<daniel.mohni@...> wrote:
> Hello Milos
>
>  I installed the latest build for testing...
>
>  I had one problem after the restart of Netbeans, some of my open project showed up
>  as invalid, after resaving the pom, they are fine. maybe an encoding problem somewhere....

hmm.. that's indeed strange. Resaving basically means the project gets
reloaded. so it could be that the embedder failed to load the
projects. Did you get any exception? (in 6.0 FCS and 6.1 RC1/2 in
means jus a small red sign in bottom rigght corner, in dev builds a
popup window)


>
>  the other problem I now have, is that I use the assembly-plugin to get my application
>  to look like it has to, copying files from different locations to the right destination
>
>  eg. I have a config folder at /src/main/config (then it shows up in Netbeans) and I copy
>  this one to target/<application>/config any some other stuff....

the config folder is not meant to be part of the jar file right?

>
>  This worked without any problems the projects are run the old way, but is a bit slow I agree...
>
>  but to get my project to run the new way I have to make a lot of workarounds when I load files
>  or reference some other artefacts. We had to do that in the old maven1 times....
>
>  No I would like to have an option to swich from the two run types, in the config panel
>
>  - slow jar run
>  - fast exec:exec
>
>  [] use fast execution mode...

I'd rather avoid having options that most people don't understand or
have use for. However the old code stayed there. if you have the old
settings setup, the run panel should respect that (if I've done my
testing right)


Thanks

Milos

>
>  something like this
>
>  Regards
>
>  Daniel
>
>  I go back to 3.0.12 to get my current work out on time...
>
>
>
>  > -----Ursprüngliche Nachricht-----
>  > Von: Milos Kleint [mailto:mkleint@...]
>  > Gesendet: Montag, 21. April 2008 12:01
>  > An: Mevenide
>  > Betreff: [mevenide-user] call for action: test the upcoming new version 3.1
>
>
> >
>  > Hello everybody,
>  >
>  > I'd like to ask you to become beta testers for the new 3.1 version of
>  > mevenide. It's packed with new features, includes many fixes..
>  > Some highlights:
>  > 1. remote repository browsing and in general incorporating remote
>  > repositories content in the UI
>  > 2. latest 2.1-SNAPSHOT maven embedder bundled, most problems caused by
>  > the old embedder should be gone.
>  > 3. j2ee integration improved - deployment of ears, webframeworks can
>  > be added to maven projects.
>  > 4. the maven build can be examined visually in terms of browsing what
>  > gets executed. (new action on output window toolbar)
>  > 5. alternate configurations for action mappings, allow to load the
>  > project with some profiles activated.
>  > 6.probably more and more stuff I can't recall right now.
>  >
>  > Testing it out is really easy.
>  >
>  > Installing the bits is really easy.
>  > 1. download the 6.1 RC (well, 6.0 final would do as well)
>  > 2. download the zip file with maven support nbm files from
>  > http://deadlock.netbeans.org/hudson/job/mevenide/lastSuccessfulBuild/artifact/meve
>  > nide-AU-SNAPSHOT.zip
>  > 3. start the IDE, preferably with the --userdir <temp location> switch
>  > to to be on the safe side..
>  > 4. install the nbm files from the zip via Tools/Plugins dialog
>  > (Downloaded tab). That should be it.
>  >
>  > I'm interested in bug reports, comments on usability, general rants.
>  > However I'd like to push the bits to the default netbeans update
>  > center for 6.0 and 6.1 in a week or two, so I'm primarily looking for
>  > showstoppers. The upgrade to new maven embedder should fix old
>  > problems but could have introduced new ones. I'd like make sure all or
>  > most projects load correctly. The more complex setup you have the
>  > better.
>  >
>  > Regards and thanks..
>  >
>  > Milos
>  >
>
>
> > ---------------------------------------------------------------------
>  > 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



AW: call for action: test the upcoming new version 3.1

by Mohni, Daniel :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi Milos

answers inline...

> -----Ursprüngliche Nachricht-----
> Von: Milos Kleint [mailto:mkleint@...]
> Gesendet: Dienstag, 22. April 2008 08:04
> An: user@...
> Betreff: Re: [mevenide-user] call for action: test the upcoming new version 3.1
>
> On Tue, Apr 22, 2008 at 6:32 AM, Mohni, Daniel
> <daniel.mohni@...> wrote:
> > Hello Milos
> >
> >  I installed the latest build for testing...
> >
> >  I had one problem after the restart of Netbeans, some of my open project showed
> up
> >  as invalid, after resaving the pom, they are fine. maybe an encoding problem
> somewhere....
>
> hmm.. that's indeed strange. Resaving basically means the project gets
> reloaded. so it could be that the embedder failed to load the
> projects. Did you get any exception? (in 6.0 FCS and 6.1 RC1/2 in
> means jus a small red sign in bottom rigght corner, in dev builds a
> popup window)
>

I didn't see an exception, I also tried to reload the project, this didn't help only
after modifying the pom (add line remove line) and save fixed the problem...

>
> >
> >  the other problem I now have, is that I use the assembly-plugin to get my
> application
> >  to look like it has to, copying files from different locations to the right
> destination
> >
> >  eg. I have a config folder at /src/main/config (then it shows up in Netbeans)
> and I copy
> >  this one to target/<application>/config any some other stuff....
>
> the config folder is not meant to be part of the jar file right?

yes, there are also some binaries that I put in a /bin folder ( -> JavaService.exe, ..)
to be used with Runtime.getRuntime().exec()

my Swing app needs the feature to be installed as a service in windows, the gui is only for configuration
and the configuration is stored on the file system in /config


>
> >
> >  This worked without any problems the projects are run the old way, but is a bit
> slow I agree...
> >
> >  but to get my project to run the new way I have to make a lot of workarounds
> when I load files
> >  or reference some other artefacts. We had to do that in the old maven1
> times....
> >
> >  No I would like to have an option to swich from the two run types, in the
> config panel
> >
> >  - slow jar run
> >  - fast exec:exec
> >
> >  [] use fast execution mode...
>
> I'd rather avoid having options that most people don't understand or
> have use for. However the old code stayed there. if you have the old
> settings setup, the run panel should respect that (if I've done my
> testing right)
>

hmmm

just tested again with a working nbactions.xml in my project (NB6.1RC2)
application starts using run-jar

changed userconfig to new mevenide and started NB6.1RC2.
when I try to run the project, it ask fort he run class, as in the
old style run the main class iss et in the netbeans-public profile

-> it does not run out of the box with the old nbactions.xml

even activating the profile does not help

the debug project also ask's for a mainclass...

>
> Thanks
>
> Milos
>
> >
> >  something like this
> >
> >  Regards
> >
> >  Daniel
> >
> >  I go back to 3.0.12 to get my current work out on time...
> >
> >
> >
> >  > -----Ursprüngliche Nachricht-----
> >  > Von: Milos Kleint [mailto:mkleint@...]
> >  > Gesendet: Montag, 21. April 2008 12:01
> >  > An: Mevenide
> >  > Betreff: [mevenide-user] call for action: test the upcoming new version 3.1
> >
> >
> > >
> >  > Hello everybody,
> >  >
> >  > I'd like to ask you to become beta testers for the new 3.1 version of
> >  > mevenide. It's packed with new features, includes many fixes..
> >  > Some highlights:
> >  > 1. remote repository browsing and in general incorporating remote
> >  > repositories content in the UI
> >  > 2. latest 2.1-SNAPSHOT maven embedder bundled, most problems caused by
> >  > the old embedder should be gone.
> >  > 3. j2ee integration improved - deployment of ears, webframeworks can
> >  > be added to maven projects.
> >  > 4. the maven build can be examined visually in terms of browsing what
> >  > gets executed. (new action on output window toolbar)
> >  > 5. alternate configurations for action mappings, allow to load the
> >  > project with some profiles activated.
> >  > 6.probably more and more stuff I can't recall right now.
> >  >
> >  > Testing it out is really easy.
> >  >
> >  > Installing the bits is really easy.
> >  > 1. download the 6.1 RC (well, 6.0 final would do as well)
> >  > 2. download the zip file with maven support nbm files from
> >  >
> http://deadlock.netbeans.org/hudson/job/mevenide/lastSuccessfulBuild/artifact/meve
> >  > nide-AU-SNAPSHOT.zip
> >  > 3. start the IDE, preferably with the --userdir <temp location> switch
> >  > to to be on the safe side..
> >  > 4. install the nbm files from the zip via Tools/Plugins dialog
> >  > (Downloaded tab). That should be it.
> >  >
> >  > I'm interested in bug reports, comments on usability, general rants.
> >  > However I'd like to push the bits to the default netbeans update
> >  > center for 6.0 and 6.1 in a week or two, so I'm primarily looking for
> >  > showstoppers. The upgrade to new maven embedder should fix old
> >  > problems but could have introduced new ones. I'd like make sure all or
> >  > most projects load correctly. The more complex setup you have the
> >  > better.
> >  >
> >  > Regards and thanks..
> >  >
> >  > Milos
> >  >
> >
> >
> > > ---------------------------------------------------------------------
> >  > 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: call for action: test the upcoming new version 3.1

by Marek Nowicki-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

> I'm interested in bug reports, comments on usability, general rants.
> However I'd like to push the bits to the default netbeans update
> center for 6.0 and 6.1 in a week or two, so I'm primarily looking for
> showstoppers. The upgrade to new maven embedder should fix old
> problems but could have introduced new ones. I'd like make sure all or
> most projects load correctly. The more complex setup you have the
> better.

I cannot change global custom definitions  
(tools/options/miscellaneous/maven2/Edit Global Custom Definitions...).
When I click that button red circle appears in right bottom corner of  
NetBeans and that is stack trace:
--- CUT ---
java.lang.NullPointerException
        at  
org.codehaus.mevenide.netbeans.customizer.ActionMappings.setupConfigurations(ActionMappings.java:924)
        at  
org.codehaus.mevenide.netbeans.customizer.ActionMappings.addNotify(ActionMappings.java:243)
        at java.awt.Container.addNotify(Container.java:2592)
        at javax.swing.JComponent.addNotify(JComponent.java:4665)
        at java.awt.Container.addNotify(Container.java:2592)
        at javax.swing.JComponent.addNotify(JComponent.java:4665)
        at java.awt.Container.addNotify(Container.java:2592)
        at javax.swing.JComponent.addNotify(JComponent.java:4665)
        at javax.swing.JRootPane.addNotify(JRootPane.java:735)
        at java.awt.Container.addNotify(Container.java:2592)
        at java.awt.Window.addNotify(Window.java:635)
        at java.awt.Dialog.addNotify(Dialog.java:744)
        at  
org.netbeans.core.windows.services.NbPresenter.addNotify(NbPresenter.java:338)
        at java.awt.Window.pack(Window.java:663)
        at  
org.netbeans.core.windows.services.NbPresenter.initialize(NbPresenter.java:236)
        at  
org.netbeans.core.windows.services.NbPresenter.<init>(NbPresenter.java:166)
        at org.netbeans.core.windows.services.NbDialog.<init>(NbDialog.java:64)
        at  
org.netbeans.core.windows.services.DialogDisplayerImpl$1AWTQuery.showDialog(DialogDisplayerImpl.java:204)
        at  
org.netbeans.core.windows.services.DialogDisplayerImpl.notify(DialogDisplayerImpl.java:245)
        at  
org.netbeans.core.windows.services.DialogDisplayerImpl.notify(DialogDisplayerImpl.java:144)
        at  
org.codehaus.mevenide.netbeans.options.SettingsPanel.btnGoalsActionPerformed(SettingsPanel.java:650)
        at  
org.codehaus.mevenide.netbeans.options.SettingsPanel.access$700(SettingsPanel.java:68)
        at  
org.codehaus.mevenide.netbeans.options.SettingsPanel$7.actionPerformed(SettingsPanel.java:471)
        at  
javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1995)
        at  
javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2318)
        at  
javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:387)
        at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:242)
        at  
javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:236)
        at java.awt.Component.processMouseEvent(Component.java:6038)
        at javax.swing.JComponent.processMouseEvent(JComponent.java:3260)
        at java.awt.Component.processEvent(Component.java:5803)
        at java.awt.Container.processEvent(Container.java:2058)
        at java.awt.Component.dispatchEventImpl(Component.java:4410)
        at java.awt.Container.dispatchEventImpl(Container.java:2116)
        at java.awt.Component.dispatchEvent(Component.java:4240)
        at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4322)
        at java.awt.LightweightDispatcher.processMouseEvent(Container.java:3986)
        at java.awt.LightweightDispatcher.dispatchEvent(Container.java:3916)
        at java.awt.Container.dispatchEventImpl(Container.java:2102)
        at java.awt.Window.dispatchEventImpl(Window.java:2429)
        at java.awt.Component.dispatchEvent(Component.java:4240)
[catch] at java.awt.EventQueue.dispatchEvent(EventQueue.java:599)
        at  
org.netbeans.core.TimableEventQueue.dispatchEvent(TimableEventQueue.java:104)
        at  
java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:273)
        at  
java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:183)
        at  
java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:173)
        at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:168)
        at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:160)
        at java.awt.EventDispatchThread.run(EventDispatchThread.java:121)
--- CUT ---

I have NetBeans 6.1 RC2 installed and today downloaded  
mevenide-AU-SNAPSHOT.zip.


Additionally at start I have one project (main project) named set to  
"<Badly formed Maven project>" but 2nd have good name. After a while name  
of "<Badly formed Maven project>" is corrected.

regards,
Marek

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

    http://xircles.codehaus.org/manage_email



Re: call for action: test the upcoming new version 3.1

by Milos Kleint-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

thanks.

I'll look into the exception. I've done stuff in this area and broke
this usecase it seems.

The <Badly formed Maven project> problem basically means the maven
embedder failed to load the project. Can you send me the
~/.netbeans/6.1/var/log/messages.log file? maybe a stacktrace could
hint to the problem.

Milos

On Wed, Apr 23, 2008 at 3:24 PM, Marek Nowicki <faramir2@...> wrote:

>
> > I'm interested in bug reports, comments on usability, general rants.
> > However I'd like to push the bits to the default netbeans update
> > center for 6.0 and 6.1 in a week or two, so I'm primarily looking for
> > showstoppers. The upgrade to new maven embedder should fix old
> > problems but could have introduced new ones. I'd like make sure all or
> > most projects load correctly. The more complex setup you have the
> > better.
> >
>
>  I cannot change global custom definitions
> (tools/options/miscellaneous/maven2/Edit Global Custom Definitions...).
>  When I click that button red circle appears in right bottom corner of
> NetBeans and that is stack trace:
>  --- CUT ---
>  java.lang.NullPointerException
>         at
> org.codehaus.mevenide.netbeans.customizer.ActionMappings.setupConfigurations(ActionMappings.java:924)
>         at
> org.codehaus.mevenide.netbeans.customizer.ActionMappings.addNotify(ActionMappings.java:243)
>         at java.awt.Container.addNotify(Container.java:2592)
>         at javax.swing.JComponent.addNotify(JComponent.java:4665)
>         at java.awt.Container.addNotify(Container.java:2592)
>         at javax.swing.JComponent.addNotify(JComponent.java:4665)
>         at java.awt.Container.addNotify(Container.java:2592)
>         at javax.swing.JComponent.addNotify(JComponent.java:4665)
>         at javax.swing.JRootPane.addNotify(JRootPane.java:735)
>         at java.awt.Container.addNotify(Container.java:2592)
>         at java.awt.Window.addNotify(Window.java:635)
>         at java.awt.Dialog.addNotify(Dialog.java:744)
>         at
> org.netbeans.core.windows.services.NbPresenter.addNotify(NbPresenter.java:338)
>         at java.awt.Window.pack(Window.java:663)
>         at
> org.netbeans.core.windows.services.NbPresenter.initialize(NbPresenter.java:236)
>         at
> org.netbeans.core.windows.services.NbPresenter.<init>(NbPresenter.java:166)
>         at
> org.netbeans.core.windows.services.NbDialog.<init>(NbDialog.java:64)
>         at
> org.netbeans.core.windows.services.DialogDisplayerImpl$1AWTQuery.showDialog(DialogDisplayerImpl.java:204)
>         at
> org.netbeans.core.windows.services.DialogDisplayerImpl.notify(DialogDisplayerImpl.java:245)
>         at
> org.netbeans.core.windows.services.DialogDisplayerImpl.notify(DialogDisplayerImpl.java:144)
>         at
> org.codehaus.mevenide.netbeans.options.SettingsPanel.btnGoalsActionPerformed(SettingsPanel.java:650)
>         at
> org.codehaus.mevenide.netbeans.options.SettingsPanel.access$700(SettingsPanel.java:68)
>         at
> org.codehaus.mevenide.netbeans.options.SettingsPanel$7.actionPerformed(SettingsPanel.java:471)
>         at
> javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1995)
>         at
> javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2318)
>         at
> javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:387)
>         at
> javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:242)
>         at
> javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:236)
>         at java.awt.Component.processMouseEvent(Component.java:6038)
>         at javax.swing.JComponent.processMouseEvent(JComponent.java:3260)
>         at java.awt.Component.processEvent(Component.java:5803)
>         at java.awt.Container.processEvent(Container.java:2058)
>         at java.awt.Component.dispatchEventImpl(Component.java:4410)
>         at java.awt.Container.dispatchEventImpl(Container.java:2116)
>         at java.awt.Component.dispatchEvent(Component.java:4240)
>         at
> java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4322)
>         at
> java.awt.LightweightDispatcher.processMouseEvent(Container.java:3986)
>         at java.awt.LightweightDispatcher.dispatchEvent(Container.java:3916)
>         at java.awt.Container.dispatchEventImpl(Container.java:2102)
>         at java.awt.Window.dispatchEventImpl(Window.java:2429)
>         at java.awt.Component.dispatchEvent(Component.java:4240)
>  [catch] at java.awt.EventQueue.dispatchEvent(EventQueue.java:599)
>         at
> org.netbeans.core.TimableEventQueue.dispatchEvent(TimableEventQueue.java:104)
>         at
> java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:273)
>         at
> java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:183)
>         at
> java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:173)
>         at
> java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:168)
>         at
> java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:160)
>         at java.awt.EventDispatchThread.run(EventDispatchThread.java:121)
>  --- CUT ---
>
>  I have NetBeans 6.1 RC2 installed and today downloaded
> mevenide-AU-SNAPSHOT.zip.
>
>
>  Additionally at start I have one project (main project) named set to
> "<Badly formed Maven project>" but 2nd have good name. After a while name of
> "<Badly formed Maven project>" is corrected.
>
>  regards,
>  Marek
>
>
>
>  ---------------------------------------------------------------------
>  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: call for action: test the upcoming new version 3.1

by Milos Kleint-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

i've fixed the exception yesterday.. still investigating the badly
formed project issue.

Milos

On Wed, Apr 23, 2008 at 3:24 PM, Marek Nowicki <faramir2@...> wrote:

>
> > I'm interested in bug reports, comments on usability, general rants.
> > However I'd like to push the bits to the default netbeans update
> > center for 6.0 and 6.1 in a week or two, so I'm primarily looking for
> > showstoppers. The upgrade to new maven embedder should fix old
> > problems but could have introduced new ones. I'd like make sure all or
> > most projects load correctly. The more complex setup you have the
> > better.
> >
>
>  I cannot change global custom definitions
> (tools/options/miscellaneous/maven2/Edit Global Custom Definitions...).
>  When I click that button red circle appears in right bottom corner of
> NetBeans and that is stack trace:
>  --- CUT ---
>  java.lang.NullPointerException
>         at
> org.codehaus.mevenide.netbeans.customizer.ActionMappings.setupConfigurations(ActionMappings.java:924)
>         at
> org.codehaus.mevenide.netbeans.customizer.ActionMappings.addNotify(ActionMappings.java:243)
>         at java.awt.Container.addNotify(Container.java:2592)
>         at javax.swing.JComponent.addNotify(JComponent.java:4665)
>         at java.awt.Container.addNotify(Container.java:2592)
>         at javax.swing.JComponent.addNotify(JComponent.java:4665)
>         at java.awt.Container.addNotify(Container.java:2592)
>         at javax.swing.JComponent.addNotify(JComponent.java:4665)
>         at javax.swing.JRootPane.addNotify(JRootPane.java:735)
>         at java.awt.Container.addNotify(Container.java:2592)
>         at java.awt.Window.addNotify(Window.java:635)
>         at java.awt.Dialog.addNotify(Dialog.java:744)
>         at
> org.netbeans.core.windows.services.NbPresenter.addNotify(NbPresenter.java:338)
>         at java.awt.Window.pack(Window.java:663)
>         at
> org.netbeans.core.windows.services.NbPresenter.initialize(NbPresenter.java:236)
>         at
> org.netbeans.core.windows.services.NbPresenter.<init>(NbPresenter.java:166)
>         at
> org.netbeans.core.windows.services.NbDialog.<init>(NbDialog.java:64)
>         at
> org.netbeans.core.windows.services.DialogDisplayerImpl$1AWTQuery.showDialog(DialogDisplayerImpl.java:204)
>         at
> org.netbeans.core.windows.services.DialogDisplayerImpl.notify(DialogDisplayerImpl.java:245)
>         at
> org.netbeans.core.windows.services.DialogDisplayerImpl.notify(DialogDisplayerImpl.java:144)
>         at
> org.codehaus.mevenide.netbeans.options.SettingsPanel.btnGoalsActionPerformed(SettingsPanel.java:650)
>         at
> org.codehaus.mevenide.netbeans.options.SettingsPanel.access$700(SettingsPanel.java:68)
>         at
> org.codehaus.mevenide.netbeans.options.SettingsPanel$7.actionPerformed(SettingsPanel.java:471)
>         at
> javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1995)
>         at
> javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2318)
>         at
> javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:387)
>         at
> javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:242)
>         at
> javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:236)
>         at java.awt.Component.processMouseEvent(Component.java:6038)
>         at javax.swing.JComponent.processMouseEvent(JComponent.java:3260)
>         at java.awt.Component.processEvent(Component.java:5803)
>         at java.awt.Container.processEvent(Container.java:2058)
>         at java.awt.Component.dispatchEventImpl(Component.java:4410)
>         at java.awt.Container.dispatchEventImpl(Container.java:2116)
>         at java.awt.Component.dispatchEvent(Component.java:4240)
>         at
> java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4322)
>         at
> java.awt.LightweightDispatcher.processMouseEvent(Container.java:3986)
>         at java.awt.LightweightDispatcher.dispatchEvent(Container.java:3916)
>         at java.awt.Container.dispatchEventImpl(Container.java:2102)
>         at java.awt.Window.dispatchEventImpl(Window.java:2429)
>         at java.awt.Component.dispatchEvent(Component.java:4240)
>  [catch] at java.awt.EventQueue.dispatchEvent(EventQueue.java:599)
>         at
> org.netbeans.core.TimableEventQueue.dispatchEvent(TimableEventQueue.java:104)
>         at
> java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:273)
>         at
> java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:183)
>         at
> java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:173)
>         at
> java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:168)
>         at
> java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:160)
>         at java.awt.EventDispatchThread.run(EventDispatchThread.java:121)
>  --- CUT ---
>
>  I have NetBeans 6.1 RC2 installed and today downloaded
> mevenide-AU-SNAPSHOT.zip.
>
>
>  Additionally at start I have one project (main project) named set to
> "<Badly formed Maven project>" but 2nd have good name. After a while name of
> "<Badly formed Maven project>" is corrected.
>
>  regards,
>  Marek
>
>
>
>  ---------------------------------------------------------------------
>  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: call for action: test the upcoming new version 3.1

by Marek Nowicki-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

How can I replace old packages with today snapshot?

I got message: Plugin "NetBeans Maven2 apisupport bridge" is already  
installed.
and so on...

Marek

Dnia 24-04-2008 o 08:58:04 Milos Kleint <mkleint@...> napisał:

> i've fixed the exception yesterday.. still investigating the badly
> formed project issue.
>
> Milos
>
> On Wed, Apr 23, 2008 at 3:24 PM, Marek Nowicki <faramir2@...>  
> wrote:
>>
>> > I'm interested in bug reports, comments on usability, general rants.
>> > However I'd like to push the bits to the default netbeans update
>> > center for 6.0 and 6.1 in a week or two, so I'm primarily looking for
>> > showstoppers. The upgrade to new maven embedder should fix old
>> > problems but could have introduced new ones. I'd like make sure all or
>> > most projects load correctly. The more complex setup you have the
>> > better.
>> >
>>
>>  I cannot change global custom definitions
>> (tools/options/miscellaneous/maven2/Edit Global Custom Definitions...).
>>  When I click that button red circle appears in right bottom corner of
>> NetBeans and that is stack trace:
>>  --- CUT ---
>>  java.lang.NullPointerException
>>         at
>> org.codehaus.mevenide.netbeans.customizer.ActionMappings.setupConfigurations(ActionMappings.java:924)
>>         at
>> org.codehaus.mevenide.netbeans.customizer.ActionMappings.addNotify(ActionMappings.java:243)
>>         at java.awt.Container.addNotify(Container.java:2592)
>>         at javax.swing.JComponent.addNotify(JComponent.java:4665)
>>         at java.awt.Container.addNotify(Container.java:2592)
>>         at javax.swing.JComponent.addNotify(JComponent.java:4665)
>>         at java.awt.Container.addNotify(Container.java:2592)
>>         at javax.swing.JComponent.addNotify(JComponent.java:4665)
>>         at javax.swing.JRootPane.addNotify(JRootPane.java:735)
>>         at java.awt.Container.addNotify(Container.java:2592)
>>         at java.awt.Window.addNotify(Window.java:635)
>>         at java.awt.Dialog.addNotify(Dialog.java:744)
>>         at
>> org.netbeans.core.windows.services.NbPresenter.addNotify(NbPresenter.java:338)
>>         at java.awt.Window.pack(Window.java:663)
>>         at
>> org.netbeans.core.windows.services.NbPresenter.initialize(NbPresenter.java:236)
>>         at
>> org.netbeans.core.windows.services.NbPresenter.<init>(NbPresenter.java:166)
>>         at
>> org.netbeans.core.windows.services.NbDialog.<init>(NbDialog.java:64)
>>         at
>> org.netbeans.core.windows.services.DialogDisplayerImpl$1AWTQuery.showDialog(DialogDisplayerImpl.java:204)
>>         at
>> org.netbeans.core.windows.services.DialogDisplayerImpl.notify(DialogDisplayerImpl.java:245)
>>         at
>> org.netbeans.core.windows.services.DialogDisplayerImpl.notify(DialogDisplayerImpl.java:144)
>>         at
>> org.codehaus.mevenide.netbeans.options.SettingsPanel.btnGoalsActionPerformed(SettingsPanel.java:650)
>>         at
>> org.codehaus.mevenide.netbeans.options.SettingsPanel.access$700(SettingsPanel.java:68)
>>         at
>> org.codehaus.mevenide.netbeans.options.SettingsPanel$7.actionPerformed(SettingsPanel.java:471)
>>         at
>> javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1995)
>>         at
>> javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2318)
>>         at
>> javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:387)
>>         at
>> javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:242)
>>         at
>> javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:236)
>>         at java.awt.Component.processMouseEvent(Component.java:6038)
>>         at  
>> javax.swing.JComponent.processMouseEvent(JComponent.java:3260)
>>         at java.awt.Component.processEvent(Component.java:5803)
>>         at java.awt.Container.processEvent(Container.java:2058)
>>         at java.awt.Component.dispatchEventImpl(Component.java:4410)
>>         at java.awt.Container.dispatchEventImpl(Container.java:2116)
>>         at java.awt.Component.dispatchEvent(Component.java:4240)
>>         at
>> java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4322)
>>         at
>> java.awt.LightweightDispatcher.processMouseEvent(Container.java:3986)
>>         at  
>> java.awt.LightweightDispatcher.dispatchEvent(Container.java:3916)
>>         at java.awt.Container.dispatchEventImpl(Container.java:2102)
>>         at java.awt.Window.dispatchEventImpl(Window.java:2429)
>>         at java.awt.Component.dispatchEvent(Component.java:4240)
>>  [catch] at java.awt.EventQueue.dispatchEvent(EventQueue.java:599)
>>         at
>> org.netbeans.core.TimableEventQueue.dispatchEvent(TimableEventQueue.java:104)
>>         at
>> java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:273)
>>         at
>> java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:183)
>>         at
>> java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:173)
>>         at
>> java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:168)
>>         at
>> java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:160)
>>         at  
>> java.awt.EventDispatchThread.run(EventDispatchThread.java:121)
>>  --- CUT ---
>>
>>  I have NetBeans 6.1 RC2 installed and today downloaded
>> mevenide-AU-SNAPSHOT.zip.
>>
>>
>>  Additionally at start I have one project (main project) named set to
>> "<Badly formed Maven project>" but 2nd have good name. After a while  
>> name of
>> "<Badly formed Maven project>" is corrected.
>>
>>  regards,
>>  Marek
>>
>>
>>
>>  ---------------------------------------------------------------------
>>  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: call for action: test the upcoming new version 3.1

by Milos Kleint-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

the most part can be deleted from the Tools/Plugins ui by selecting
the "Maven" entry and triggering "Uninstall". However some collateral
modules will be kept. The bullet proof method is either to delete the
whole user directory or some selective files.
your's user directory would be somethign like ~/.netbeans/dev or
~/netbeans/6.0 or similar based on what version of netbeans you use.
remove mevenide related files from the following folders
modules
update_tracking
config/Modules

that should do it.

Milos

On Thu, Apr 24, 2008 at 9:49 PM, Marek Nowicki <faramir2@...> wrote:

> How can I replace old packages with today snapshot?
>
>  I got message: Plugin "NetBeans Maven2 apisupport bridge" is already
> installed.
>  and so on...
>
>  Marek
>
>  Dnia 24-04-2008 o 08:58:04 Milos Kleint <mkleint@...> napisał:
>
>
>
> > i've fixed the exception yesterday.. still investigating the badly
> > formed project issue.
> >
> > Milos
> >
> > On Wed, Apr 23, 2008 at 3:24 PM, Marek Nowicki <faramir2@...> wrote:
> >
> > >
> > > > I'm interested in bug reports, comments on usability, general rants.
> > > > However I'd like to push the bits to the default netbeans update
> > > > center for 6.0 and 6.1 in a week or two, so I'm primarily looking for
> > > > showstoppers. The upgrade to new maven embedder should fix old
> > > > problems but could have introduced new ones. I'd like make sure all or
> > > > most projects load correctly. The more complex setup you have the
> > > > better.
> > > >
> > >
> > >  I cannot change global custom definitions
> > > (tools/options/miscellaneous/maven2/Edit Global Custom Definitions...).
> > >  When I click that button red circle appears in right bottom corner of
> > > NetBeans and that is stack trace:
> > >  --- CUT ---
> > >  java.lang.NullPointerException
> > >        at
> > >
> org.codehaus.mevenide.netbeans.customizer.ActionMappings.setupConfigurations(ActionMappings.java:924)
> > >        at
> > >
> org.codehaus.mevenide.netbeans.customizer.ActionMappings.addNotify(ActionMappings.java:243)
> > >        at java.awt.Container.addNotify(Container.java:2592)
> > >        at javax.swing.JComponent.addNotify(JComponent.java:4665)
> > >        at java.awt.Container.addNotify(Container.java:2592)
> > >        at javax.swing.JComponent.addNotify(JComponent.java:4665)
> > >        at java.awt.Container.addNotify(Container.java:2592)
> > >        at javax.swing.JComponent.addNotify(JComponent.java:4665)
> > >        at javax.swing.JRootPane.addNotify(JRootPane.java:735)
> > >        at java.awt.Container.addNotify(Container.java:2592)
> > >        at java.awt.Window.addNotify(Window.java:635)
> > >        at java.awt.Dialog.addNotify(Dialog.java:744)
> > >        at
> > >
> org.netbeans.core.windows.services.NbPresenter.addNotify(NbPresenter.java:338)
> > >        at java.awt.Window.pack(Window.java:663)
> > >        at
> > >
> org.netbeans.core.windows.services.NbPresenter.initialize(NbPresenter.java:236)
> > >        at
> > >
> org.netbeans.core.windows.services.NbPresenter.<init>(NbPresenter.java:166)
> > >        at
> > > org.netbeans.core.windows.services.NbDialog.<init>(NbDialog.java:64)
> > >        at
> > >
> org.netbeans.core.windows.services.DialogDisplayerImpl$1AWTQuery.showDialog(DialogDisplayerImpl.java:204)
> > >        at
> > >
> org.netbeans.core.windows.services.DialogDisplayerImpl.notify(DialogDisplayerImpl.java:245)
> > >        at
> > >
> org.netbeans.core.windows.services.DialogDisplayerImpl.notify(DialogDisplayerImpl.java:144)
> > >        at
> > >
> org.codehaus.mevenide.netbeans.options.SettingsPanel.btnGoalsActionPerformed(SettingsPanel.java:650)
> > >        at
> > >
> org.codehaus.mevenide.netbeans.options.SettingsPanel.access$700(SettingsPanel.java:68)
> > >        at
> > >
> org.codehaus.mevenide.netbeans.options.SettingsPanel$7.actionPerformed(SettingsPanel.java:471)
> > >        at
> > > javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1995)
> > >        at
> > >
> javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2318)
> > >        at
> > >
> javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:387)
> > >        at
> > > javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:242)
> > >        at
> > >
> javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:236)
> > >        at java.awt.Component.processMouseEvent(Component.java:6038)
> > >        at javax.swing.JComponent.processMouseEvent(JComponent.java:3260)
> > >        at java.awt.Component.processEvent(Component.java:5803)
> > >        at java.awt.Container.processEvent(Container.java:2058)
> > >        at java.awt.Component.dispatchEventImpl(Component.java:4410)
> > >        at java.awt.Container.dispatchEventImpl(Container.java:2116)
> > >        at java.awt.Component.dispatchEvent(Component.java:4240)
> > >        at
> > > java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4322)
> > >        at
> > > java.awt.LightweightDispatcher.processMouseEvent(Container.java:3986)
> > >        at
> java.awt.LightweightDispatcher.dispatchEvent(Container.java:3916)
> > >        at java.awt.Container.dispatchEventImpl(Container.java:2102)
> > >        at java.awt.Window.dispatchEventImpl(Window.java:2429)
> > >        at java.awt.Component.dispatchEvent(Component.java:4240)
> > >  [catch] at java.awt.EventQueue.dispatchEvent(EventQueue.java:599)
> > >        at
> > >
> org.netbeans.core.TimableEventQueue.dispatchEvent(TimableEventQueue.java:104)
> > >        at
> > >
> java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:273)
> > >        at
> > >
> java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:183)
> > >        at
> > >
> java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:173)
> > >        at
> > > java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:168)
> > >        at
> > > java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:160)
> > >        at java.awt.EventDispatchThread.run(EventDispatchThread.java:121)
> > >  --- CUT ---
> > >
> > >  I have NetBeans 6.1 RC2 installed and today downloaded
> > > mevenide-AU-SNAPSHOT.zip.
> > >
> > >
> > >  Additionally at start I have one project (main project) named set to
> > > "<Badly formed Maven project>" but 2nd have good name. After a while
> name of
> > > "<Badly formed Maven project>" is corrected.
> > >
> > >  regards,
> > >  Marek
> > >
> > >
> > >
> > >  ---------------------------------------------------------------------
> > >  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: call for action: test the upcoming new version 3.1

by Marek Nowicki-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Thanks. I don't see more bugs right now :).

I have one future feature idea for mevenide.. Now it is possible to  
download javadocs for all library javadocs by clicking on Libraries in  
project explorer. Sometimes, eg. after adding dependency library, should  
be helpful to right click on library and select "download javadoc for that  
library".

Marek

Dnia 24-04-2008 o 08:58:04 Milos Kleint <mkleint@...> napisał:

> i've fixed the exception yesterday.. still investigating the badly
> formed project issue.
>
> Milos
>
> On Wed, Apr 23, 2008 at 3:24 PM, Marek Nowicki <faramir2@...>  
> wrote:
>>
>> > I'm interested in bug reports, comments on usability, general rants.
>> > However I'd like to push the bits to the default netbeans update
>> > center for 6.0 and 6.1 in a week or two, so I'm primarily looking for
>> > showstoppers. The upgrade to new maven embedder should fix old
>> > problems but could have introduced new ones. I'd like make sure all or
>> > most projects load correctly. The more complex setup you have the
>> > better.
>> >
>>
>>  I cannot change global custom definitions
>> (tools/options/miscellaneous/maven2/Edit Global Custom Definitions...).
>>  When I click that button red circle appears in right bottom corner of
>> NetBeans and that is stack trace:
>>  --- CUT ---
>>  java.lang.NullPointerException
>>         at
>> org.codehaus.mevenide.netbeans.customizer.ActionMappings.setupConfigurations(ActionMappings.java:924)
>>         at
>> org.codehaus.mevenide.netbeans.customizer.ActionMappings.addNotify(ActionMappings.java:243)
>>         at java.awt.Container.addNotify(Container.java:2592)
>>         at javax.swing.JComponent.addNotify(JComponent.java:4665)
>>         at java.awt.Container.addNotify(Container.java:2592)
>>         at javax.swing.JComponent.addNotify(JComponent.java:4665)
>>         at java.awt.Container.addNotify(Container.java:2592)
>>         at javax.swing.JComponent.addNotify(JComponent.java:4665)
>>         at javax.swing.JRootPane.addNotify(JRootPane.java:735)
>>         at java.awt.Container.addNotify(Container.java:2592)
>>         at java.awt.Window.addNotify(Window.java:635)
>>         at java.awt.Dialog.addNotify(Dialog.java:744)
>>         at
>> org.netbeans.core.windows.services.NbPresenter.addNotify(NbPresenter.java:338)
>>         at java.awt.Window.pack(Window.java:663)
>>         at
>> org.netbeans.core.windows.services.NbPresenter.initialize(NbPresenter.java:236)
>>         at
>> org.netbeans.core.windows.services.NbPresenter.<init>(NbPresenter.java:166)
>>         at
>> org.netbeans.core.windows.services.NbDialog.<init>(NbDialog.java:64)
>>         at
>> org.netbeans.core.windows.services.DialogDisplayerImpl$1AWTQuery.showDialog(DialogDisplayerImpl.java:204)
>>         at
>> org.netbeans.core.windows.services.DialogDisplayerImpl.notify(DialogDisplayerImpl.java:245)
>>         at
>> org.netbeans.core.windows.services.DialogDisplayerImpl.notify(DialogDisplayerImpl.java:144)
>>         at
>> org.codehaus.mevenide.netbeans.options.SettingsPanel.btnGoalsActionPerformed(SettingsPanel.java:650)
>>         at
>> org.codehaus.mevenide.netbeans.options.SettingsPanel.access$700(SettingsPanel.java:68)
>>         at
>> org.codehaus.mevenide.netbeans.options.SettingsPanel$7.actionPerformed(SettingsPanel.java:471)
>>         at
>> javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1995)
>>         at
>> javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2318)
>>         at
>> javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:387)
>>         at
>> javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:242)
>>         at
>> javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:236)
>>         at java.awt.Component.processMouseEvent(Component.java:6038)
>>         at  
>> javax.swing.JComponent.processMouseEvent(JComponent.java:3260)
>>         at java.awt.Component.processEvent(Component.java:5803)
>>         at java.awt.Container.processEvent(Container.java:2058)
>>         at java.awt.Component.dispatchEventImpl(Component.java:4410)
>>         at java.awt.Container.dispatchEventImpl(Container.java:2116)
>>         at java.awt.Component.dispatchEvent(Component.java:4240)
>>         at
>> java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4322)
>>         at
>> java.awt.LightweightDispatcher.processMouseEvent(Container.java:3986)
>>         at  
>> java.awt.LightweightDispatcher.dispatchEvent(Container.java:3916)
>>         at java.awt.Container.dispatchEventImpl(Container.java:2102)
>>         at java.awt.Window.dispatchEventImpl(Window.java:2429)
>>         at java.awt.Component.dispatchEvent(Component.java:4240)
>>  [catch] at java.awt.EventQueue.dispatchEvent(EventQueue.java:599)
>>         at
>> org.netbeans.core.TimableEventQueue.dispatchEvent(TimableEventQueue.java:104)
>>         at
>> java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:273)
>>         at
>> java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:183)
>>         at
>> java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:173)
>>         at
>> java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:168)
>>         at
>> java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:160)
>>         at  
>> java.awt.EventDispatchThread.run(EventDispatchThread.java:121)
>>  --- CUT ---
>>
>>  I have NetBeans 6.1 RC2 installed and today downloaded
>> mevenide-AU-SNAPSHOT.zip.
>>
>>
>>  Additionally at start I have one project (main project) named set to
>> "<Badly formed Maven project>" but 2nd have good name. After a while  
>> name of
>> "<Badly formed Maven project>" is corrected.
>>
>>  regards,
>>  Marek
>>
>>
>>
>>  ---------------------------------------------------------------------
>>  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: call for action: test the upcoming new version 3.1

by Daniel Mutch :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


I know you're looking for show stoppers but can you please sort the list of configurations in the configuration list and associated toolbar combo-box?

thanks
Dan


Milos Kleint wrote:
Hello everybody,

I'd like to ask you to become beta testers for the new 3.1 version of
mevenide. It's packed with new features, includes many fixes..
Some highlights:
1. remote repository browsing and in general incorporating remote
repositories content in the UI
2. latest 2.1-SNAPSHOT maven embedder bundled, most problems caused by
the old embedder should be gone.
3. j2ee integration improved - deployment of ears, webframeworks can
be added to maven projects.
4. the maven build can be examined visually in terms of browsing what
gets executed. (new action on output window toolbar)
5. alternate configurations for action mappings, allow to load the
project with some profiles activated.
6.probably more and more stuff I can't recall right now.

Testing it out is really easy.

Installing the bits is really easy.
1. download the 6.1 RC (well, 6.0 final would do as well)
2. download the zip file with maven support nbm files from
http://deadlock.netbeans.org/hudson/job/mevenide/lastSuccessfulBuild/artifact/mevenide-AU-SNAPSHOT.zip
3. start the IDE, preferably with the --userdir <temp location> switch
to to be on the safe side..
4. install the nbm files from the zip via Tools/Plugins dialog
(Downloaded tab). That should be it.

I'm interested in bug reports, comments on usability, general rants.
However I'd like to push the bits to the default netbeans update
center for 6.0 and 6.1 in a week or two, so I'm primarily looking for
showstoppers. The upgrade to new maven embedder should fix old
problems but could have introduced new ones. I'd like make sure all or
most projects load correctly. The more complex setup you have the
better.

Regards and thanks..

Milos

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

    http://xircles.codehaus.org/manage_email


Re: call for action: test the upcoming new version 3.1

by Milos Kleint-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

sort by what?

Milos

On Wed, May 7, 2008 at 4:39 AM, Daniel Mutch
<daniel.mutch@...> wrote:

>
>
>  I know you're looking for show stoppers but can you please sort the list of
>  configurations in the configuration list and associated toolbar combo-box?
>
>  thanks
>  Dan
>
>
>
>
>
>  Milos Kleint wrote:
>  >
>  > Hello everybody,
>  >
>  > I'd like to ask you to become beta testers for the new 3.1 version of
>  > mevenide. It's packed with new features, includes many fixes..
>  > Some highlights:
>  > 1. remote repository browsing and in general incorporating remote
>  > repositories content in the UI
>  > 2. latest 2.1-SNAPSHOT maven embedder bundled, most problems caused by
>  > the old embedder should be gone.
>  > 3. j2ee integration improved - deployment of ears, webframeworks can
>  > be added to maven projects.
>  > 4. the maven build can be examined visually in terms of browsing what
>  > gets executed. (new action on output window toolbar)
>  > 5. alternate configurations for action mappings, allow to load the
>  > project with some profiles activated.
>  > 6.probably more and more stuff I can't recall right now.
>  >
>  > Testing it out is really easy.
>  >
>  > Installing the bits is really easy.
>  > 1. download the 6.1 RC (well, 6.0 final would do as well)
>  > 2. download the zip file with maven support nbm files from
>  > http://deadlock.netbeans.org/hudson/job/mevenide/lastSuccessfulBuild/artifact/mevenide-AU-SNAPSHOT.zip
>  > 3. start the IDE, preferably with the --userdir <temp location> switch
>  > to to be on the safe side..
>  > 4. install the nbm files from the zip via Tools/Plugins dialog
>  > (Downloaded tab). That should be it.
>  >
>  > I'm interested in bug reports, comments on usability, general rants.
>  > However I'd like to push the bits to the default netbeans update
>  > center for 6.0 and 6.1 in a week or two, so I'm primarily looking for
>  > showstoppers. The upgrade to new maven embedder should fix old
>  > problems but could have introduced new ones. I'd like make sure all or
>  > most projects load correctly. The more complex setup you have the
>  > better.
>  >
>  > Regards and thanks..
>  >
>  > Milos
>  >
>
> > ---------------------------------------------------------------------
>  > To unsubscribe from this list, please visit:
>  >
>  >     http://xircles.codehaus.org/manage_email
>  >
>  >
>  >
>  >
>
>  --
>  View this message in context: http://www.nabble.com/call-for-action%3A-test-the-upcoming-new-version-3.1-tp16806928p17093825.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: call for action: test the upcoming new version 3.1

by Daniel Mutch :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


By name, i.e. they are listed alphabetically...

Milos Kleint wrote:
sort by what?

Milos

On Wed, May 7, 2008 at 4:39 AM, Daniel Mutch
<daniel.mutch@barclayscapital.com> wrote:
>
>
>  I know you're looking for show stoppers but can you please sort the list of
>  configurations in the configuration list and associated toolbar combo-box?
>
>  thanks
>  Dan
>
>
>
>
>
>  Milos Kleint wrote:
>  >
>  > Hello everybody,
>  >
>  > I'd like to ask you to become beta testers for the new 3.1 version of
>  > mevenide. It's packed with new features, includes many fixes..
>  > Some highlights:
>  > 1. remote repository browsing and in general incorporating remote
>  > repositories content in the UI
>  > 2. latest 2.1-SNAPSHOT maven embedder bundled, most problems caused by
>  > the old embedder should be gone.
>  > 3. j2ee integration improved - deployment of ears, webframeworks can
>  > be added to maven projects.
>  > 4. the maven build can be examined visually in terms of browsing what
>  > gets executed. (new action on output window toolbar)
>  > 5. alternate configurations for action mappings, allow to load the
>  > project with some profiles activated.
>  > 6.probably more and more stuff I can't recall right now.
>  >
>  > Testing it out is really easy.
>  >
>  > Installing the bits is really easy.
>  > 1. download the 6.1 RC (well, 6.0 final would do as well)
>  > 2. download the zip file with maven support nbm files from
>  > http://deadlock.netbeans.org/hudson/job/mevenide/lastSuccessfulBuild/artifact/mevenide-AU-SNAPSHOT.zip
>  > 3. start the IDE, preferably with the --userdir <temp location> switch
>  > to to be on the safe side..
>  > 4. install the nbm files from the zip via Tools/Plugins dialog
>  > (Downloaded tab). That should be it.
>  >
>  > I'm interested in bug reports, comments on usability, general rants.
>  > However I'd like to push the bits to the default netbeans update
>  > center for 6.0 and 6.1 in a week or two, so I'm primarily looking for
>  > showstoppers. The upgrade to new maven embedder should fix old
>  > problems but could have introduced new ones. I'd like make sure all or
>  > most projects load correctly. The more complex setup you have the
>  > better.
>  >
>  > Regards and thanks..
>  >
>  > Milos
>  >
>
> > ---------------------------------------------------------------------
>  > To unsubscribe from this list, please visit:
>  >
>  >     http://xircles.codehaus.org/manage_email
>  >
>  >
>  >
>  >
>
>  --
>  View this message in context: http://www.nabble.com/call-for-action%3A-test-the-upcoming-new-version-3.1-tp16806928p17093825.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