Thanks for the quick reply. I was actually wanted 3 things:
1) see the generated code
2) have code completion for the generated code
3) have the classpath include the declared dependencies (include the ones of type "pom", not just "jar")
Looking into the various project behavioral properties for Maven (see http://maven.apache.org/reference/user-guide.html#Behavioural_Properties), it seems that if you use the maven.build.src property for each of the (sub)projects, this would allow to include the generated source code.
I'm happy to be the first tester if you need help.
Philippe
The 0.2 version doens't only display folder designated by the <sourcedirectory> tag, but also for example picks up the war plugin's maven.war.src property and checks if such a folder exist. if yes, it will show it in the projects view.
Currenly the project tries to open anything it can, be it sources/test sources/resources/maven plugin scripts. The assumption there is that while maven project definition is quite general, one would not have both maven plugin script and webapp sources together. I'd not like to have the projects view bloated, but show just the important parts of the project. For less important (read: less frequently used) files and file structure, the Files view is a quite good fallback.
The list of such "important" files/trees is definitely not complete, ear sources come to mind for example.
why do you want to have the generated sources in the projects view you want to browse it? As I understand it, editing is no option there since it always gets regenerated by andromda.
Or is the actual problem not the project view but that the generated sources don't show up in the code completion when you edit other sources? That can be fixed quite easily, I just need to know how to find the generated sources root. Is there a maven property that handles this?
Support for sourcemodification can be also written but currently I don't understand this part of maven at all. I only once read something about it on the maven users list and as far as I rememeber it was recommended not to use it at all. It was said to disappear in maven 2.0 altogether.
Regards
Milos Kleint
-------- Original Message --------
Subject: [Andromda-user] Using Mevenide on NetBeans 4.0 to edit/build/debug AndroMDA Date: Wed, 08 Sep 2004 14:02:04 -0500 From: Philippe Monnet <[EMAIL PROTECTED]> To: [EMAIL PROTECTED], [EMAIL PROTECTED]
Today I decided to try out the new version of Mevenide for NetBeans 4.0 beta 1. It is a very cool plug-in: once you open the root project, Mevenide automatically parses the subprojects and "mounts" them in the IDE and sets the classpaths based on declared dependencies. This greatly makes life easier for Maven projects especially when using the Multiproject pattern.However when I use the AndroMDA tool , which uses multiprojects and use 2 types of source directories per project (one for always-re-generated code , and one for generated but to-be-tailored code), Mevenide only picks up the source directory declared in the project.xml (seems logical). I'm trying to figure out how to setup Maven/Mevenide so that both directories will be mounted in NetBeans. Does anyone have experience with this? Thanks in advance. Philippe PS - Milos, I'm copying you since you are involved in Mevenide. I'm not sure if you're familiar with AndroMDA ( http://team.andromda.org). In case you are not, AndroMDA uses subprojects and XDoclet to generate various artifacts like EJBs, common components, etc. If I have a root project called mysvc in C:\mysvc, the full directory structure looks as follow: project.properties - root project.xml .\ejb - subproject for the EJB components .\ejb\project.xml .\ejb\src\java --contains source code to be tailored by the developer (generated only once by AndroMDA through XDoclet ) .\ejb\src\java\org\mddtut\mddtut2\MySvcBeanImpl.java .\ejb\target .\ejb\target\classes ... .\ejb\target\classes\org\mddtut\mddtut2\MySvcBean.class .\ejb\target\classes\org\mddtut\mddtut2\MySvcBeanImpl.class ... .\ejb\target\src\ - contains source code always re-/generated by AndroMDA through XDoclet ... .\ejb\target\src\org\mddtut\mddtut2\MySvcBean.java ... .\ejb\target\xdoclet\ .\mda - subproject containing the UML model driving the AndroMDA generation .\mda\project.xml .\mda\src\uml\mddtut2a-model.xmi .. If you look at the ejb subproject, you will notice the 2 source code directories: .\ejb\src\java --contains source code to be tailored by the developer (generated only once by AndroMDA through XDoclet ) .\ejb\target\src\ - contains source code always re-/generated by AndroMDA through XDoclet In .\ejb\project.xml, the sourceDirectory points to src\java. However, since we also have code in target\java, that directory does not get mounted in NetBeans. I have tried to add a <sourceModifications> section but I must not know how to set that up properly: <build> <sourceDirectory>src/java</sourceDirectory> <sourceModifications> <sourceModification> <className>MySvcBean</className> <includes> <include>target/src/**/*.java</include> </includes> </sourceModification> </sourceModifications> </build> ------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click _______________________________________________ Andromda-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/andromda-user
------------------------------------------------------- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 13. Go here: http://sf.net/ppc_contest.php _______________________________________________ Andromda-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/andromda-user
