Quantcast

[jira] Created: (MNGECLIPSE-378) Update Source Folders adds resources folders as source folders, not as class folders

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
13 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[jira] Created: (MNGECLIPSE-378) Update Source Folders adds resources folders as source folders, not as class folders

JIRA jira@codehaus.org
Update Source Folders adds resources folders as source folders, not as class folders
------------------------------------------------------------------------------------

                 Key: MNGECLIPSE-378
                 URL: http://jira.codehaus.org/browse/MNGECLIPSE-378
             Project: Maven Integration for Eclipse
          Issue Type: Bug
    Affects Versions: 0.0.10
            Reporter: Howard M. Lewis Ship


When you perform an "update source folders", the plugin adds all your resource folders as source folders.  It then does a wierd thing: adding exclusions to the folders so that nothing is copied (this is really bad, because it gets in the way of runtime resource resolution).

What it should do is what I do manually, add resource folders as Eclipse Class Folders, which are added to the runtime class path (but do no have resources copied to the output folder).  This is also very close to what Maven does with resource folders at runtime.

--
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

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[jira] Commented: (MNGECLIPSE-378) Update Source Folders adds resources folders as source folders, not as class folders

JIRA jira@codehaus.org

    [ http://jira.codehaus.org/browse/MNGECLIPSE-378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103600 ]

Eugene Kuleshov commented on MNGECLIPSE-378:
--------------------------------------------

Howard, do you mind to create sample project that would allow to reproduce issue you are troubled with. Thanks.

I've been thinking to add resources ass class folders, but then there is a concern that they won't be visible trough "Open Resource" dialog.

> Update Source Folders adds resources folders as source folders, not as class folders
> ------------------------------------------------------------------------------------
>
>                 Key: MNGECLIPSE-378
>                 URL: http://jira.codehaus.org/browse/MNGECLIPSE-378
>             Project: Maven Integration for Eclipse
>          Issue Type: Bug
>    Affects Versions: 0.0.10
>            Reporter: Howard M. Lewis Ship
>
> When you perform an "update source folders", the plugin adds all your resource folders as source folders.  It then does a wierd thing: adding exclusions to the folders so that nothing is copied (this is really bad, because it gets in the way of runtime resource resolution).
> What it should do is what I do manually, add resource folders as Eclipse Class Folders, which are added to the runtime class path (but do no have resources copied to the output folder).  This is also very close to what Maven does with resource folders at runtime.

--
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

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[jira] Commented: (MNGECLIPSE-378) Update Source Folders adds resources folders as source folders, not as class folders

JIRA jira@codehaus.org
In reply to this post by JIRA jira@codehaus.org

    [ http://jira.codehaus.org/browse/MNGECLIPSE-378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103603 ]

Howard M. Lewis Ship commented on MNGECLIPSE-378:
-------------------------------------------------

For a *large* example, the Tapestry 5 source (available via SVN) demonstrates what I'd like, and uses class folders, not source folders, for resources.  Of course, I have to manually maintain it.

I'll try and find time to do a smaller example.

Open Resources works fine with resources in class folders; I do this all the time.

> Update Source Folders adds resources folders as source folders, not as class folders
> ------------------------------------------------------------------------------------
>
>                 Key: MNGECLIPSE-378
>                 URL: http://jira.codehaus.org/browse/MNGECLIPSE-378
>             Project: Maven Integration for Eclipse
>          Issue Type: Bug
>    Affects Versions: 0.0.10
>            Reporter: Howard M. Lewis Ship
>
> When you perform an "update source folders", the plugin adds all your resource folders as source folders.  It then does a wierd thing: adding exclusions to the folders so that nothing is copied (this is really bad, because it gets in the way of runtime resource resolution).
> What it should do is what I do manually, add resource folders as Eclipse Class Folders, which are added to the runtime class path (but do no have resources copied to the output folder).  This is also very close to what Maven does with resource folders at runtime.

--
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

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[jira] Commented: (MNGECLIPSE-378) Update Source Folders adds resources folders as source folders, not as class folders

JIRA jira@codehaus.org
In reply to this post by JIRA jira@codehaus.org

    [ http://jira.codehaus.org/browse/MNGECLIPSE-378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103604 ]

Eugene Kuleshov commented on MNGECLIPSE-378:
--------------------------------------------

Thanks Howard. A small example would be very useful. It would be also great if you'd add some code that access these resources (i.e. unit test that we could run from eclipse and with maven cli).

> Update Source Folders adds resources folders as source folders, not as class folders
> ------------------------------------------------------------------------------------
>
>                 Key: MNGECLIPSE-378
>                 URL: http://jira.codehaus.org/browse/MNGECLIPSE-378
>             Project: Maven Integration for Eclipse
>          Issue Type: Bug
>    Affects Versions: 0.0.10
>            Reporter: Howard M. Lewis Ship
>
> When you perform an "update source folders", the plugin adds all your resource folders as source folders.  It then does a wierd thing: adding exclusions to the folders so that nothing is copied (this is really bad, because it gets in the way of runtime resource resolution).
> What it should do is what I do manually, add resource folders as Eclipse Class Folders, which are added to the runtime class path (but do no have resources copied to the output folder).  This is also very close to what Maven does with resource folders at runtime.

--
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

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[jira] Commented: (MNGECLIPSE-378) Update Source Folders adds resources folders as source folders, not as class folders

JIRA jira@codehaus.org
In reply to this post by JIRA jira@codehaus.org

    [ http://jira.codehaus.org/browse/MNGECLIPSE-378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_107532 ]

Eugene Kuleshov commented on MNGECLIPSE-378:
--------------------------------------------

Howard, any change you could make a smaller example for this? Or maybe you can at least point me at the exact location of your projects.

> Update Source Folders adds resources folders as source folders, not as class folders
> ------------------------------------------------------------------------------------
>
>                 Key: MNGECLIPSE-378
>                 URL: http://jira.codehaus.org/browse/MNGECLIPSE-378
>             Project: Maven Integration for Eclipse
>          Issue Type: Bug
>    Affects Versions: 0.0.10
>            Reporter: Howard M. Lewis Ship
>
> When you perform an "update source folders", the plugin adds all your resource folders as source folders.  It then does a wierd thing: adding exclusions to the folders so that nothing is copied (this is really bad, because it gets in the way of runtime resource resolution).
> What it should do is what I do manually, add resource folders as Eclipse Class Folders, which are added to the runtime class path (but do no have resources copied to the output folder).  This is also very close to what Maven does with resource folders at runtime.

--
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

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[jira] Closed: (MNGECLIPSE-378) Update Source Folders adds resources folders as source folders, not as class folders

JIRA jira@codehaus.org
In reply to this post by JIRA jira@codehaus.org

     [ http://jira.codehaus.org/browse/MNGECLIPSE-378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eugene Kuleshov closed MNGECLIPSE-378.
--------------------------------------

    Resolution: Incomplete

Please reopen if you can provide requested info. Thanks.

> Update Source Folders adds resources folders as source folders, not as class folders
> ------------------------------------------------------------------------------------
>
>                 Key: MNGECLIPSE-378
>                 URL: http://jira.codehaus.org/browse/MNGECLIPSE-378
>             Project: Maven Integration for Eclipse
>          Issue Type: Bug
>    Affects Versions: 0.0.10
>            Reporter: Howard M. Lewis Ship
>
> When you perform an "update source folders", the plugin adds all your resource folders as source folders.  It then does a wierd thing: adding exclusions to the folders so that nothing is copied (this is really bad, because it gets in the way of runtime resource resolution).
> What it should do is what I do manually, add resource folders as Eclipse Class Folders, which are added to the runtime class path (but do no have resources copied to the output folder).  This is also very close to what Maven does with resource folders at runtime.

--
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

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[jira] Updated: (MNGECLIPSE-378) Update Source Folders adds resources folders as source folders, not as class folders

JIRA jira@codehaus.org
In reply to this post by JIRA jira@codehaus.org

     [ http://jira.codehaus.org/browse/MNGECLIPSE-378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Christian Gruber updated MNGECLIPSE-378:
----------------------------------------

    Attachment: mngeclipse378-sample.zip

Here's a simple project that illustrates the issue.  Just try to import it into eclipse, and /src/test/resources and /src/main/resources are entered into the classpath as source folders, when they aren't (in the sense that eclipse means it).  They're resource folders, which eclipse should process as "class folders" since they need to be on the classpath, but not part of the sources.

I'll post a two more files - one that's the project as the eclipse plugin currently generates, and the same project as I want to see it (and I suspect howard does too.)

> Update Source Folders adds resources folders as source folders, not as class folders
> ------------------------------------------------------------------------------------
>
>                 Key: MNGECLIPSE-378
>                 URL: http://jira.codehaus.org/browse/MNGECLIPSE-378
>             Project: Maven Integration for Eclipse
>          Issue Type: Bug
>    Affects Versions: 0.0.10
>            Reporter: Howard M. Lewis Ship
>         Attachments: mngeclipse378-sample.zip
>
>
> When you perform an "update source folders", the plugin adds all your resource folders as source folders.  It then does a wierd thing: adding exclusions to the folders so that nothing is copied (this is really bad, because it gets in the way of runtime resource resolution).
> What it should do is what I do manually, add resource folders as Eclipse Class Folders, which are added to the runtime class path (but do no have resources copied to the output folder).  This is also very close to what Maven does with resource folders at runtime.

--
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


Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[jira] Updated: (MNGECLIPSE-378) Update Source Folders adds resources folders as source folders, not as class folders

JIRA jira@codehaus.org
In reply to this post by JIRA jira@codehaus.org

     [ http://jira.codehaus.org/browse/MNGECLIPSE-378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Christian Gruber updated MNGECLIPSE-378:
----------------------------------------

    Attachment: mngeclipse378-samples-and-diff.zip

And here's a zip with 2 projects, one imported with the current plugin, and one altered to the state it should be.  Finally, there's a diff on the .classpath files.  It's very simple, ultimately, the desired change.  I'm also pasting the diff here:

------------------
--- mngeclipse378-sample-2/.classpath   2008-04-16 19:43:49.000000000 -0400
+++ mngeclipse378-sample-3/.classpath   2008-04-16 19:48:28.000000000 -0400
@@ -6,9 +6,9 @@
                        <attribute name="maven.type" value="test"/>
                </attributes>
        </classpathentry>
-       <classpathentry excluding="**" kind="src" output="src/main/resources" path="src/main/resources"/>
-       <classpathentry excluding="**" kind="src" output="src/test/resources" path="src/test/resources"/>
        <classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER"/>
        <classpathentry kind="con" path="org.maven.ide.eclipse.MAVEN2_CLASSPATH_CONTAINER"/>
+       <classpathentry kind="lib" path="src/main/resources"/>
+       <classpathentry kind="lib" path="src/test/resources"/>
        <classpathentry kind="output" path="target-eclipse/classes"/>
 </classpath>
------------------------

> Update Source Folders adds resources folders as source folders, not as class folders
> ------------------------------------------------------------------------------------
>
>                 Key: MNGECLIPSE-378
>                 URL: http://jira.codehaus.org/browse/MNGECLIPSE-378
>             Project: Maven Integration for Eclipse
>          Issue Type: Bug
>    Affects Versions: 0.0.10
>            Reporter: Howard M. Lewis Ship
>         Attachments: mngeclipse378-sample.zip, mngeclipse378-samples-and-diff.zip
>
>
> When you perform an "update source folders", the plugin adds all your resource folders as source folders.  It then does a wierd thing: adding exclusions to the folders so that nothing is copied (this is really bad, because it gets in the way of runtime resource resolution).
> What it should do is what I do manually, add resource folders as Eclipse Class Folders, which are added to the runtime class path (but do no have resources copied to the output folder).  This is also very close to what Maven does with resource folders at runtime.

--
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


Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[jira] Updated: (MNGECLIPSE-378) Update Source Folders adds resources folders as source folders, not as class folders

JIRA jira@codehaus.org
In reply to this post by JIRA jira@codehaus.org

     [ http://jira.codehaus.org/browse/MNGECLIPSE-378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Christian Gruber updated MNGECLIPSE-378:
----------------------------------------

    Attachment: mngeclipse378-sample.diff

ok that paste didn't work, as jira formatted the stuff.  I'm attaching the raw diff file for easy linking.

> Update Source Folders adds resources folders as source folders, not as class folders
> ------------------------------------------------------------------------------------
>
>                 Key: MNGECLIPSE-378
>                 URL: http://jira.codehaus.org/browse/MNGECLIPSE-378
>             Project: Maven Integration for Eclipse
>          Issue Type: Bug
>    Affects Versions: 0.0.10
>            Reporter: Howard M. Lewis Ship
>         Attachments: mngeclipse378-sample.diff, mngeclipse378-sample.zip, mngeclipse378-samples-and-diff.zip
>
>
> When you perform an "update source folders", the plugin adds all your resource folders as source folders.  It then does a wierd thing: adding exclusions to the folders so that nothing is copied (this is really bad, because it gets in the way of runtime resource resolution).
> What it should do is what I do manually, add resource folders as Eclipse Class Folders, which are added to the runtime class path (but do no have resources copied to the output folder).  This is also very close to what Maven does with resource folders at runtime.

--
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


Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[jira] Reopened: (MNGECLIPSE-378) Update Source Folders adds resources folders as source folders, not as class folders

JIRA jira@codehaus.org
In reply to this post by JIRA jira@codehaus.org

     [ http://jira.codehaus.org/browse/MNGECLIPSE-378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship reopened MNGECLIPSE-378:
---------------------------------------------


Christian has add some examples and a diff between the .classpath files from the current source folder approach vs. the resources-as-lib approach -- thanks for picking up my slack, Christian!

> Update Source Folders adds resources folders as source folders, not as class folders
> ------------------------------------------------------------------------------------
>
>                 Key: MNGECLIPSE-378
>                 URL: http://jira.codehaus.org/browse/MNGECLIPSE-378
>             Project: Maven Integration for Eclipse
>          Issue Type: Bug
>    Affects Versions: 0.0.10
>            Reporter: Howard M. Lewis Ship
>         Attachments: mngeclipse378-sample.diff, mngeclipse378-sample.zip, mngeclipse378-samples-and-diff.zip
>
>
> When you perform an "update source folders", the plugin adds all your resource folders as source folders.  It then does a wierd thing: adding exclusions to the folders so that nothing is copied (this is really bad, because it gets in the way of runtime resource resolution).
> What it should do is what I do manually, add resource folders as Eclipse Class Folders, which are added to the runtime class path (but do no have resources copied to the output folder).  This is also very close to what Maven does with resource folders at runtime.

--
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


Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[jira] Commented: (MNGECLIPSE-378) Update Source Folders adds resources folders as source folders, not as class folders

JIRA jira@codehaus.org
In reply to this post by JIRA jira@codehaus.org

    [ http://jira.codehaus.org/browse/MNGECLIPSE-378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=131056#action_131056 ]

Eugene Kuleshov commented on MNGECLIPSE-378:
--------------------------------------------

Christian, thanks for the projects, but what is the actual problem you have with current configuration? What is exactly that does not work for you? Please also indicate if you are using latest 0.9.x m2eclipse build.

> Update Source Folders adds resources folders as source folders, not as class folders
> ------------------------------------------------------------------------------------
>
>                 Key: MNGECLIPSE-378
>                 URL: http://jira.codehaus.org/browse/MNGECLIPSE-378
>             Project: Maven Integration for Eclipse
>          Issue Type: Bug
>    Affects Versions: 0.0.10
>            Reporter: Howard M. Lewis Ship
>         Attachments: mngeclipse378-sample.diff, mngeclipse378-sample.zip, mngeclipse378-samples-and-diff.zip
>
>
> When you perform an "update source folders", the plugin adds all your resource folders as source folders.  It then does a wierd thing: adding exclusions to the folders so that nothing is copied (this is really bad, because it gets in the way of runtime resource resolution).
> What it should do is what I do manually, add resource folders as Eclipse Class Folders, which are added to the runtime class path (but do no have resources copied to the output folder).  This is also very close to what Maven does with resource folders at runtime.

--
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


Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[jira] Commented: (MNGECLIPSE-378) Update Source Folders adds resources folders as source folders, not as class folders

JIRA jira@codehaus.org
In reply to this post by JIRA jira@codehaus.org

    [ http://jira.codehaus.org/browse/MNGECLIPSE-378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=131063#action_131063 ]

Christian Gruber commented on MNGECLIPSE-378:
---------------------------------------------

I am, and the problem is that you can put .java files in to /src/*/resource folders and maven will not compile them (expected behaviour) but eclipse will (unexpected behaviour) .  So it basically means that the meaning of these folders is subtly different, which can cause error.  One of the goals should be to make preventable errors prevented categorically.  

For me, however, it amounts to an annoying thing I need to do each time I import a project.  I now use maven for all my projects I no longer version eclipse configuration files (except in very very odd cases like FlexBuilder projects).  Because of this, all the metadata is in pom.xml files, and so "opening" a project is actually an import with m2eclipse.  So basically I end up with a 3 step import.  1. Import the maven project.  2. remove the /src/*/resource  folders from the build path.  3. add src/*/resource folders as class folder libraries.  Not gonna kill me, but annoying.  And since I contend that the semantic of the current configuration is incorrect, I can't see a good reason not to do this.

> Update Source Folders adds resources folders as source folders, not as class folders
> ------------------------------------------------------------------------------------
>
>                 Key: MNGECLIPSE-378
>                 URL: http://jira.codehaus.org/browse/MNGECLIPSE-378
>             Project: Maven Integration for Eclipse
>          Issue Type: Bug
>    Affects Versions: 0.0.10
>            Reporter: Howard M. Lewis Ship
>         Attachments: mngeclipse378-sample.diff, mngeclipse378-sample.zip, mngeclipse378-samples-and-diff.zip
>
>
> When you perform an "update source folders", the plugin adds all your resource folders as source folders.  It then does a wierd thing: adding exclusions to the folders so that nothing is copied (this is really bad, because it gets in the way of runtime resource resolution).
> What it should do is what I do manually, add resource folders as Eclipse Class Folders, which are added to the runtime class path (but do no have resources copied to the output folder).  This is also very close to what Maven does with resource folders at runtime.

--
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


Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[jira] Commented: (MNGECLIPSE-378) Update Source Folders adds resources folders as source folders, not as class folders

JIRA jira@codehaus.org
In reply to this post by JIRA jira@codehaus.org

    [ http://jira.codehaus.org/browse/MNGECLIPSE-378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=131064#action_131064 ]

Christian Gruber commented on MNGECLIPSE-378:
---------------------------------------------

Oh yeah, and I'm using 0.9.1.200803311600.

> Update Source Folders adds resources folders as source folders, not as class folders
> ------------------------------------------------------------------------------------
>
>                 Key: MNGECLIPSE-378
>                 URL: http://jira.codehaus.org/browse/MNGECLIPSE-378
>             Project: Maven Integration for Eclipse
>          Issue Type: Bug
>    Affects Versions: 0.0.10
>            Reporter: Howard M. Lewis Ship
>         Attachments: mngeclipse378-sample.diff, mngeclipse378-sample.zip, mngeclipse378-samples-and-diff.zip
>
>
> When you perform an "update source folders", the plugin adds all your resource folders as source folders.  It then does a wierd thing: adding exclusions to the folders so that nothing is copied (this is really bad, because it gets in the way of runtime resource resolution).
> What it should do is what I do manually, add resource folders as Eclipse Class Folders, which are added to the runtime class path (but do no have resources copied to the output folder).  This is also very close to what Maven does with resource folders at runtime.

--
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


Loading...