[mevenide-dev] [jira] Commented: (MEVENIDE-610) mevenide2: generated sources are not on source paths list for autocompletion and autocompile

    [ http://jira.codehaus.org/browse/MEVENIDE-610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_126453 ] 

Milos Kleint commented on MEVENIDE-610:
---------------------------------------

The workaround and only solution is to generate your sources into ${basedir}/target/generated-sources/foo-bar directory where foo-bar is a directory name of your choice.
That's where most source generating plugins generate content into by default.

The IDE listens on this directory and adds any such folders on classpath of the project. Maven doesn't currently allow to recognise such folders from the project model without actually building the project. That's an unacceptable solution for me, since especially on startup when you have 10+ projects opened, the penalty is very high. 

I don't intend to change the current behaviour any time soon (unless maven itself comes up with a declarative way of registering generated source roots). But I'm not sure your ant-run-plugin usecase would be covered by that either.

-> wontfix unfortunately.



> mevenide2: generated sources are not on source paths list for autocompletion and autocompile
> --------------------------------------------------------------------------------------------
>
>                 Key: MEVENIDE-610
>                 URL: http://jira.codehaus.org/browse/MEVENIDE-610
>             Project: mevenide
>          Issue Type: Bug
>          Components: mevenide2-netbeans
>         Environment: windows xp pro, netbeans 6.0, mevenide2 v3.0.10, jdk 1.5
>            Reporter: David Siefert
>            Assignee: Milos Kleint
>
> As part of my build process I use the maven-antrun-plugin to generate proxies for web services.  The antrun plugin allows you to specify a sources path (see sample below) that will be added to the compilers source paths.  The IDE autocompile (which causes red squiqqly underlines) and autocomplete dropdowns do not use this making it very unproductive to develop (since I have to manually look for package names, class names, method names, etc).  Is there any workaround that would allow me to manually specify additional source paths for the time being?
> Sample POM specification:
> <plugin>
> 	<groupId>org.apache.maven.plugins</groupId>
> 	<artifactId>maven-antrun-plugin</artifactId>
> 	<executions>
> 		<execution>
> 			<phase>generate-sources</phase>
> 			<configuration>
> 				<sourceRoot>${path.to.generated.sources}</sourceRoot>
> 			</configuration>
> 			<goals>
> 				<goal>run</goal>
> 			</goals>
> 		</execution>
> 	</executions>
> </plugin>

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email