[jbosstools-issues] [JBoss JIRA] (JBIDE-14003) Automatically discover library sources for non-maven projects

[Snjezana Peco (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-14003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12768866#comment-12768866 ] 

Snjezana Peco commented on JBIDE-14003:
---------------------------------------

{quote}
"m2e can break this behaviour and add a hardcoded source attachment. It won't fix such a source attachment and users could have an invalid attachment if don't use the Source Lookup plugin no matter whether we add that dialog or not, even though all have m2e."

I'm not fully following what you refer to here. What behavior is it that m2e can break ? doesn't the source lookup you make "fix" the missing/invalid attachments.
{quote}

The Source Lookup will fix missing/invalid attachments, but the issue can occur if users don't have the Source Lookup plugin.
                
> Automatically discover library sources for non-maven projects
> -------------------------------------------------------------
>
>                 Key: JBIDE-14003
>                 URL: https://issues.jboss.org/browse/JBIDE-14003
>             Project: Tools (JBoss Tools)
>          Issue Type: Sub-task
>          Components: maven
>    Affects Versions: 4.1.0.Alpha1
>            Reporter: Fred Bricon
>            Assignee: Snjezana Peco
>             Fix For: 4.1.0.Beta1
>
>         Attachments: test13848a.zip
>
>
> As a follow up of JBIDE-13848, enable automatic discovery of library sources for non-maven projects.
> * This feature should be turned on/off in the preferences
> * If the source file referenced in .classpath doesn't exist, it should attempt to discover a new, valid one.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira