This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 106955

Summary:	Add Framework support like in other java projects
Product:	projects	Reporter:	tomzi <tomzi>
Component:	Maven	Assignee:	Milos Kleint <mkleint>
Status:	RESOLVED FIXED
Severity:	blocker	CC:	ppisl
Priority:	P3
Version:	6.x
Hardware:	All
OS:	All
Issue Type:	ENHANCEMENT	Exception Reporter:
Bug Depends on:
Bug Blocks:	89008

Description tomzi 2007-06-18 09:40:36 UTC

It would be helpful to have an option where I add JSP, JSF, Spring, Hibernate... support to a maven web(jar...) project
and the maven module would add just the right dependencies, palettes, context menues, ... to the current maven project.

Comment 1 Milos Kleint 2007-06-18 10:58:00 UTC

the framework's themselves would have to support maven based projects. That requires support from all development teams
(not likely in 6.0 timeframe)

Comment 2 tomzi 2007-06-19 13:30:43 UTC

But its not even possible to add a framework to a maven project, isn't it?

Comment 3 Milos Kleint 2007-06-19 13:40:33 UTC

nope.
the frameworks assume an ant based project.
a framework basically adds some configuration files, adds libraries and maybe tweaks ant script (? not sure here)
to support maven projects, we would have to do the library -> set of maven dependencies conversion, and have the the
framework's config files placed at the correct location for maven project. Possibly also modify the pom.xml with
additional plugins or configurations..

adding ppisl on cc who is the framworks api guy.

Comment 4 tomzi 2007-08-21 09:39:47 UTC

So, you mean the Framework api needs to be extended in a way that
.) it is independend of the project type
.) and/or that used framework provides different implementations for eg adding jars, ...

Comment 5 Milos Kleint 2007-08-21 13:11:44 UTC

what is needed:
1. either extend the API to add library<->maven dependency conversion or come up with a creative way of figuring out
automatically. (eg. MD5 checksums could work but so far I had mixed results with that)
2. either extend API to allow embedding of customizer/project creation wizard cod for web framework extensions.
Alternatively copy that codebase to maven projects.
3. Cross fingers and pray that none of the frameworks extends build scripts and hardcodes relative paths for
configuration files.

contrary to my expectations, there is not an explicit dependency on ant projects, but only an implicit one.

Comment 6 Milos Kleint 2007-10-07 07:10:35 UTC

this issue is related #113284

Comment 7 Milos Kleint 2008-02-25 20:07:02 UTC

more or less done in trunk (3.1-SNAPSHOT). 
projects with war packaging now have new WebFrameworks panel in properties dialog. The new project wizard will not
include frameworks. 
There are still outstanding issues with individual frameworks (visual web doesn't fully work) but that's bugs only.