Integrate gmaps4jsf libraries with core NetBeans distribution

[GoogleCodeExporter]

There are two options to do this. First option is the NetBeans Update Center 
and the second is NetDEV program.

Note: the following text is copied verbatim from a NetBeans rep that I question 
about the process of getting the gmaps4jsf libraris included in there core 
distribution:

   "In the former case please read the process description [1] in Wiki. Sources can be anywhere (sourceforge.net, kenai.com, google.code etc.), you build NBM files and as a result the plugin(s) will be available to all NetBeans users via "Tools > Plugins" action from main menu.

[1] http://wiki.netbeans.org/UpdateCenterProcess

   The other option is a true contribution of sources into community-main repository that will get into development builds. The process is again described [2] in a Wiki.

[2] http://wiki.netbeans.org/NetDEV"

Note that both approaches have one strong requirement that there must be an 
owner for communication and problem resolution tasks.

Thanks,

-- Robert

Original issue reported on code.google.com by robert2...@gmail.com on 6 Aug 2010 at 4:30

[GoogleCodeExporter]

This is a great feature.

Robert, Can you be the owner of this task?

Original comment by Hazem.sa...@gmail.com on 13 Aug 2010 at 1:02

[GoogleCodeExporter]

Sure, I'll run with this... I'll dig into it tonight.

Original comment by robert2...@gmail.com on 13 Aug 2010 at 1:09

[GoogleCodeExporter]

This is great.
Thanks.

Original comment by Hazem.sa...@gmail.com on 13 Aug 2010 at 1:19

[GoogleCodeExporter]

Okay... I'm moving forward with this, but I would like to respectfully request 
a general refinment release to ensure quality for once the jar is integrated 
into the NetBeans standard distribution. 

Can we please target the following to be completed prior to the inclusion into 
NetBeans... 

I would also like to include a GMaps4JSF sample project for NetBeans if 
possible.

General checklist ensuring quality of the GMaps4JSF project (note this is just 
general items from brainstorming that I did): 

(1) Ensure the GMaps4JSF project is maintained in a leading IDE such as 
NetBeans, Eclipse, JDeveloper or IntelliJ IDEA.

(2) Ensure GMaps4JSF logging is properly established (e.g. appropriate debug 
levels are available for development purposes)

(3) Check the GMaps4JSF source code against software quality tools
    -- Resolve flagged issues found by Findbugs
    -- Resolve flagged issues found by Checkstyle
    -- Resolve flagged issues found by PMD

(4) Ensure proper coding conventions are used within the GMaps4JSF project
   --  Note: thhe Elements of Java Style is an excellent resource, however software quality tools will find coding convention issues as well; http://www.ambysoft.com/books/elementsJavaStyle.html.

(5) Perform general refactorings where necessary against the GMaps4JSF source 
code
    -- Format all source code files
    -- Include toString methods 
    -- Refactor to make use of most applicable design patterns
    -- etc.

(6) Update GMaps4JSF source code documenation and generate Javadoc

(7) Update GMaps4JSF tag library documentation

(8) Ensure attributes are appropriately used (designed) in regards to standard 
features of basic, html and dhtml-event component tag attributes

Thanks,
Robert

Original comment by robert2...@gmail.com on 14 Aug 2010 at 1:11

[GoogleCodeExporter]

Original comment by Hazem.sa...@gmail.com on 30 Oct 2010 at 12:29

• Added labels: Priority-Low
• Removed labels: Priority-Medium

[GoogleCodeExporter]

You can close this out, as the issue is now maintained under a NetBeans issue: 
http://netbeans.org/bugzilla/show_bug.cgi?id=191481.

I'm going to run point on this action as I mentioned, I just need to figure out 
the right path to move forward.

Original comment by robert2...@gmail.com on 30 Oct 2010 at 12:55

[GoogleCodeExporter]

Original comment by Hazem.sa...@gmail.com on 14 Mar 2013 at 12:11

• Changed state: Fixed