History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: IDE-603
Type: New Feature New Feature
Status: Reopened Reopened
Priority: Major Major
Assignee: Christian Dupuis
Reporter: Imported
Votes: 5
Watchers: 7
Operations

If you were logged in you would be able to see more operations.
Spring IDE

Maven plugin for creating .springBeans and .springWebflow configuration files

Created: 07/Jun/07 09:50 PM   Updated: 23/May/08 05:31 PM
Component/s: maven.plugin
Affects Version/s: None
Fix Version/s: None

Time Tracking:
Not Specified


 Description  « Hide
Currently, can use Maven to add Spring Project Nature and Spring Project Builder when generating Eclipse Projects. However, would like a Maven plugin to create
.springBeans
and
.springWebflow
configuration files.

 All   Comments   Work Log   Change History   FishEye   Related Builds      Sort Order: Ascending order - Click to sort in descending order
Christian Dupuis - 07/Jun/07 09:58 PM

nicolas de loof - 20/Apr/08 04:40 AM
As a Maven committer, I can propose some help here.

I plan to create a sandbox plugin for spring at mojo.codehaus.org. It will use a (simplified) spring context files description to generate a .springbeans configuration file with base options that may cover most cases. When some spring IDE fine tweaks are requied, it would be simplier to commit the .springBEan on SCM.

The idea is to configure something like :

<plugin>
<artifactId>springide-maven-plugin</artifactId>
<configuration>
<springContext>
<include>${basedir}/src/main/resources/META-INF/spring/*.xml<include>
<springContext>
</configuration>
</plugin>

This will generate a .springBean config file with a single config set (artifactId as name) including all the declared spring context files.

In many cases, I think this will cover most user requirements


Domingo Suarez Torres - 20/Apr/08 11:11 AM
I like that.

But the plugin must support search in classpath too. Sometimes Spring context files are in jar files.

Cheers


Carlos Sanchez - 22/Apr/08 02:31 PM
At Q4E (Maven integration for Eclipse) http://code.google.com/p/q4e/ we added extension points so other plugins (ie SpringIDE) can contribute behavior to the Maven project import so you don't need to use the maven-eclipse-plugin in your pom anymore.
You can right click - import - existing maven 2 project and point to the directory where it is.

It would avoid a lot of user configuration if SpringIDE could contribute to Q4E import extension points and add the necessary files/natures/... for Spring projects



Christian Dupuis - 22/Apr/08 04:03 PM
Carlos, can you point me to the extension point documentation that you are referring to. I want to have a look to see how much effort it needs to get this extension point integration done.


nicolas de loof - 16/May/08 04:31 AM
Basic plugin created on mojo (http://mojo.codehaus.org/springide-maven-plugin/)

It scans the project (source, resources and target/generated-*) using includes/excludes patterns for spring configuration files and create .springBeans based on it.

I could also scan the project dependencies but I can't find how this would apply to the .springBeans file. Using SpringIDE 2.0.5, I have no option in my project to include files from other eclipse projects or from classpaht jars (did I miss something ?).

About support from SpringIDE for maven / eclipse integration, please also consider m2Eclispe that also has a plugable "Configurator" API.

m2Eclipse and q4e are concurrent projects for maven / eclipse integration, with no plan to merge efforts


nicolas de loof - 16/May/08 04:33 AM
I also would need some suggest about how to create the .springWebflow file, as I'm not (yet) a webflow user

Eugene Kuleshov - 23/May/08 04:40 PM
I'd would like to say that using SpringIDE API for configuring project is probably a better idea then generating .springBeans and .springWebflow files outside of Eclipse.

The project configuration extension points we created in m2eclipse allows to use tools own API for configuring projects and other settings. It still allow to call Maven plugins (and there is a generic implementation for that), but it is probably should be used as a last resort.

Please see more details on the wiki at http://docs.codehaus.org/display/M2ECLIPSE/Extensible+project+configuration+framework

Anyways, this kind of integration is probably should be owned by the tool vendors, such as SpringIDE and since m2eclipse is being provisioned at eclipse.org I wonder if SpringIDE is interested in taking ownership for implementing project configurator for m2eclipse?

PS: Nicolas, you should not be speaking on behalf of m2eclipse that there is no plans to merge efforts


Christian Dupuis - 23/May/08 05:31 PM
From a maven user and Spring IDE perspective I think it makes most sense to just support the command line integration that Nicolas implemented (many thanks for this).

I don't see myself implementing and maintaining support for two Eclipse projects (assuming that both projects pass the creation review) that both deal with Maven integration but have a totally different and incompatible approach for their extension points. IMHO it would be best for the community to have one great Maven plugin that can then gather as many extension providers instead of having two of them.

I still need to look into how much effort it would take to implement the extension points but just the fact that there are two projects at Eclipse confuse me and I honestly don't think that this is healthy and good for adoption.

Just my 2cents.

Christian