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 188037 - Maven Enterprise Application projects: Projects Tab
Summary: Maven Enterprise Application projects: Projects Tab
Status: RESOLVED WONTFIX
Alias: None
Product: javaee
Classification: Unclassified
Component: Maven (show other bugs)
Version: 6.x
Hardware: PC Windows 7 x64
: P4 normal with 1 vote (vote)
Assignee: Martin Janicek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-24 09:57 UTC by puce
Modified: 2016-07-07 08:54 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description puce 2010-06-24 09:57:42 UTC
The structure of a Maven Enterprise Application projects in the "Projects" tab differs from the Ant version:

- Java EE Modules node missing
- Configuration Files missing
- Server Resources missing
- Context Menu: "Add Java EE Module..." missing

I think at least the "Source Packages", "Test Packages" and "Other Sources" should be hidden.
Comment 1 David Konecny 2011-09-20 21:43:02 UTC
Martin, similar comment I just added to issue 188038 applies here as well. I agree that showing Source/Test packages in EAR project is nonsense. EAR does not have any Java sources.
Comment 2 Martin Janicek 2011-10-04 13:25:10 UTC
Currently the structure looks a little bit differently from the original report.
Maven Enterprise Application:

- Other sources
- Dependencies
- Project files
---> there aren't Source or Test Packages anymore

Ant Enterprise Application:

- Java EE configuration modules
- Configuration Files
- Server Resources

..I agree, that there should be some kind of consistency between a Maven and Ant based projects. 

Other Sources: 
I suggest to move Other Sources (containing manifest.mf) and Project Files (containing pom.xml and settings.xml) to newly created node Configuration Files (as a result we should have similar configuration structure as in Ant projects). 

Dependencies: 
J2EE configuration modules are in Maven projects inside of Dependencies node which looks good to me. We could also create Jave EE configuration modules node, which implicates that we would have to distinguish between "normal dependency" and related J2EE Ejb and Web module.

Server Resources:
I'm not sure what could be this node used for.


It seems that these nodes are somehow hardcoded in Maven Project so I can't solve this inside of J2EE Maven module (or at least I can't see the way how to do that so far).

What do you think about that David? (especially Dependencies are quite discuss-able). Should I go more in to the deep and find the solution somewhere in Maven base or should I move this to Jesse?
Comment 3 Martin Janicek 2011-10-04 15:49:18 UTC
Related to your comment about complexity of the implementation: 
I can say, that it's easy to implement my first point (moving Other Sources and Project Files into the Configuration Files node).

Second point, creating Jave EE Configuration Modules as a special case of some Dependencies could be a little tricky (I'm not able to say concrete required time at the moment - if we'll decide to implement such thing I can look on that in more detail)

Third point: Server Resources are easy to add if there is some useful use-case in which this node could be used for.
Comment 4 David Konecny 2011-10-06 04:04:30 UTC
(In reply to comment #2)
> Maven Enterprise Application:
> ---> there aren't Source or Test Packages anymore

Probably Jesse fixed it. Cool. This was the most important, the rest has I think lower priority (P4).

> Other Sources: 
> I suggest to move Other Sources (containing manifest.mf) and Project Files
> (containing pom.xml and settings.xml) to newly created node Configuration Files
> (as a result we should have similar configuration structure as in Ant
> projects).

Other Sources should stay as is actually - in Maven you usually have two directories: one for sources and second one for resources, properties files, etc. Other Sources root is for resources and should stay as is so that Maven users can still place their files into two different places.

It make sense to rename Project Files to Configuration Files like in Ant but I would not do that. :-) The problem is that there might be users used to this, it is probably mentioned in documentation, tutorials, etc. and this change could result into more troubles than help.

> 
> Dependencies: 
> J2EE configuration modules are in Maven projects inside of Dependencies node
> which looks good to me. We could also create Jave EE configuration modules
> node, which implicates that we would have to distinguish between "normal
> dependency" and related J2EE Ejb and Web module.

Low priority.

> Server Resources:
> I'm not sure what could be this node used for.

For example in Ant Web Project use template "New File -> GlassFish Resources -> JDBC Resource" to create a server specific file. These will appear under Server Resources node. The same node should be shown under Maven projects as well. Low priority. (see org.netbeans.modules.web.project.ui.SetupDirNodeFactory for Ant impl)

> What do you think about that David?

I would leave this open as P4 to fix Server Resources and J2EE Configuration Modules nodes. If originator (or anybody else) think this is important they can always vote for this issue or increase priority or express their opinion.

One more thing: could you look into that missing "Add Java EE Module..." action? That might be worth to fix now. Thx Martin.
Comment 5 Martin Janicek 2011-10-06 09:05:34 UTC
Ok, I've just created separately issue 203200 which is related to the "Add Java EE Module..." action. 

That means in this issue remains only:
- Add Resources Files
- Add Jave EE configuration (that could be probably easily done in context of issue 203200)
Comment 6 Martin Balin 2016-07-07 08:54:07 UTC
This old bug may not be relevant anymore. If you can still reproduce it in 8.2 development builds please reopen this issue.

Thanks for your cooperation,
NetBeans IDE 8.2 Release Boss