[Bug 221781] Maven NB RCP changes to moduleType and various other module meta-data related features do not take effect without cleaning the module

  • From:
  • To:
  • Subject: [Bug 221781] Maven NB RCP changes to moduleType and various other module meta-data related features do not take effect without cleaning the module
  • Date: Thu, 17 Jan 2013 23:36:26 +0000
  • Auto-submitted: auto-generated

http://netbeans.org/bugzilla/show_bug.cgi?id=221781

_ wadechandler 
< >
 changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|INCOMPLETE                  |

--- Comment #8 from _ wadechandler 
< >
 2013-01-17 23:36:26 UTC ---
Jarda, I'm reopening. I'm going to attach a couple projects. One is Ant based,
and the other is Maven. This maybe needs assigned back to Milos. I don't know.
These projects I'm going to attach do not get into the moduleType, but instead
deal with @ServiceProvider. In the Ant project, if you add a new 
"FakeProvider"
class, and you will see, I suggest you add one called JardaFakeProvider, and
then build and run the app, then you will see that show fine in the provided
top component.

In the Maven project if you add a new FakeProvider to the
netbeans-221781-maven-main project, lets call it JardaFakeProvider or
MilosFakeProvider and do something similar to what I have done there, such as
return "Jarda" or "Milos" from the getName method, right click and build
netbeans-221781-maven-main, then right click and build
netbeans-221781-maven-parent, then right click and run
netbeans-221781-maven-app, you will not see the new FakeProvider(s) show up in
the provided top component.

So, it seems other than the moduleType issue, everything else is specific to
Maven based NB RCP projects. Whether a module is eager or not etc...sure
perhaps one can live with having to clean to change that, and of course it is 
a
pain to figure out since nothing really tells you...hey if you change this
clean and build, but these other things make it nearly unbearable for a good
sized app where things are being added and refactored all the time. The issues
with @Messages, @ServiceProvider, as well as new top components all appear to
be mvn RCP related and require "mvn clean install" before they will show up.

You can try to add a new top component to netbeans-221781-maven-main and can
see what I'm talking about. I'm using NetBeans 7.2.1 and JDK 7 along with 
Maven
3.0.4.

I will try to put together use cases which demonstrate how the @Messages
annotations causes issues in mvn based NB RCP projects as well.

-- 
Configure bugmail: http://netbeans.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA Contact for the bug.


[Bug 221781] Maven NB RCP changes to moduleType and various other module meta-data related features do not take effect without cleaning the module

wadechandler 01/17/2013

<Possible follow-up(s)>

[Bug 221781] Maven NB RCP changes to moduleType and various other module meta-data related features do not take effect without cleaning the module

wadechandler 01/17/2013

[Bug 221781] Maven NB RCP changes to moduleType and various other module meta-data related features do not take effect without cleaning the module

wadechandler 01/17/2013

[Bug 221781] Maven NB RCP changes to moduleType and various other module meta-data related features do not take effect without cleaning the module

wadechandler 01/17/2013

[Bug 221781] Maven NB RCP changes to moduleType and various other module meta-data related features do not take effect without cleaning the module

wadechandler 01/21/2013

[Bug 221781] Maven NB RCP changes to moduleType and various other module meta-data related features do not take effect without cleaning the module

mkleint 01/21/2013

[Bug 221781] Maven NB RCP changes to moduleType and various other module meta-data related features do not take effect without cleaning the module

wadechandler 01/23/2013

[Bug 221781] Maven NB RCP changes to moduleType and various other module meta-data related features do not take effect without cleaning the module

wadechandler 01/23/2013

[Bug 221781] Maven NB RCP changes to moduleType and various other module meta-data related features do not take effect without cleaning the module

mkleint 01/23/2013

[Bug 221781] Maven NB RCP changes to moduleType and various other module meta-data related features do not take effect without cleaning the module

wadechandler 01/23/2013

[Bug 221781] Maven NB RCP changes to moduleType and various other module meta-data related features do not take effect without cleaning the module

wadechandler 01/23/2013

Project Features

About this Project

APIsupport was started in November 2009, is owned by Antonin Nebuzelsky, and has 43 members.
By use of this website, you agree to the NetBeans Policies and Terms of Use (revision 20131025.e7cbc9d). © 2013, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo
 
 
Close
loading
Please Confirm
Close