[ http://jira.jboss.com/jira/browse/JBSEAM-2026?page=all ] Pete Muir updated JBSEAM-2026: ------------------------------ Component/s: Tools -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBSEAM-2026?page=com.atlassian.jira.pl... ] Neil Crow commented on JBSEAM-2026: ----------------------------------- The maven archetypes shouldn't be aware of which IDE is to be used. They should generate the maven project structure and fill in the dependencies in the pom. Once the maven project has been created, the developer should cd to the project directory and then use the maven plugins to generate their IDE files, e.g. mvn eclipse:eclipse or mvn idea:idea These maven plugins should be responsible for generating the metadata that best supports the IDE. These plugins will read the pom to calculate the classpath requirements and other settings, it may be necessary for the archetypes mentioned above to add additional information to the pom that can be used by the IDE plugins to fine tune their configuration. However any information added to the pom should preferably be ignorant of the IDE that is going to be used. Often the IDE files (.project and .classpath) are not committed to the source control repository for maven projects as they can be generated. There are also tools available that will generate these files as part of the checkout process. Neil. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBSEAM-2026?page=com.atlassian.jira.pl... ] Mariusz Smykula commented on JBSEAM-2026: ----------------------------------------- Denis, look at http://maven.apache.org/plugins/maven-ear-plugin/modules.html#ejb3Module. Maven Eclipse plugin can generate metadata for EJB3 projects configured with this plugin for Eclipse and Eclipse WTP. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBSEAM-2026?page=com.atlassian.jira.pl... ] Denis Zjukow commented on JBSEAM-2026: -------------------------------------- Thank you for your replies. Recently I found that MyEclipse has great support for Maven. Currently, it supports both WAR and EJB modules. And they are planning to support EAR "mavenization" in the future. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBSEAM-2026?page=com.atlassian.jira.pl... ] yan langlois commented on JBSEAM-2026: -------------------------------------- I agree, m2eclipse is the best plugin. How about using maven-archetype-j2ee-simple (http://maven.apache.org/plugins/maven-archetype-plugin/examples/j2ee-simp...). The only thing to add is the seam dependencies, isn't it ? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBSEAM-2026?page=com.atlassian.jira.pl... ] Dan Allen commented on JBSEAM-2026: ----------------------------------- I'm going to make a general comment, but keep the m2eclipse discussion going around it. I know many of you have waited a long time for this issue to be addressed. We'll get there, I promise. That said, I want Seam to have an official archetype so people don't have to go hunting the web for something that may or may not be up to date. I see too many initiatives trying to talk at once and not listening and learning from each other. We can come to some sort of a consensus in the Seam SVN tree. We would certainly encourage you to use this official archetype as a starting point and customize it to suit your needs. That's how I see it at least. I should be kicking off the initiative sometime soon. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBSEAM-2026?page=com.atlassian.jira.pl... ] Neil Crow commented on JBSEAM-2026: ----------------------------------- Dan, Will you go as far as adopting default maven directory structures? http://maven.apache.org/guides/introduction/introduction-to-the-standard-... This convention over configuration approach usually results in simpler poms, for example the compile and test goals would not need to be configured if the resources were in the default expected locations. Although by far the biggest challenges with this would be migrating existing project structures and aligning the defaults with the rest of the tooling jbtools and seam-gen. Another issue is that the default layout expects a single location for java sources compared to seam-gen which separates model and action. Given the above I can imagine what the answer is going to be, although it may not be as daunting as it first appears because most of the locations in the existing tooling is probably already parameterized. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBSEAM-2026?page=com.atlassian.jira.pl... ] Siarhei Dudzin commented on JBSEAM-2026: ---------------------------------------- I have to partially agree with Dan (except for belief part :) ). Archetypes wont be able to replace seam-gen, besides that would be a misuse of maven because the scope of seam-gen is much broader than that of what archetypes are for (and maven itself if we go that far)... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBSEAM-2026?page=com.atlassian.jira.pl... ] Dan Allen commented on JBSEAM-2026: ----------------------------------- I welcome the idea of Maven's archetype plugin becoming more flexible. The biggest issue right now is that like many Maven features in the past, it ain't ready yet. Therefore, it's not useful yet. I want to briefly mention (since this is not a forum and we shouldn't be threading opinions) why I don't think Maven is best for our users. First, "ant explode" is extremely fast and that is not something Maven can do because it has to go through its whole life cycle. Plus, Maven does not have built-in support for dual source directories, so doing hot deployment of Java classes is a huge hack. Times will change I am sure, but seam-gen has to stick with what works today and evolve as time goes on. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBSEAM-2026?page=com.atlassian.jira.pl... ] Pete Muir updated JBSEAM-2026: ------------------------------ Comment: was deleted -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira