[JBoss JIRA] (JBIDE-9921) Investigate if we can add quickfixes for missing dependencies/packages based on JDT and M2E error markers
2:32 a.m.
Investigate if we can add quickfixes for missing dependencies/packages based on JDT and
M2E error markers
---------------------------------------------------------------------------------------------------------
Key: JBIDE-9921
URL: https://issues.jboss.org/browse/JBIDE-9921
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: maven
Reporter: Max Rydahl Andersen
Assignee: Fred Bricon
Priority: Critical
Fix For: 3.3.0.Beta1
users of maven and our examples might bump into not being able to resolve artifacts from
jboss.org or Maven EAP repository.
This should show up as error markers for packages in JDT and if user uses maven missing
dependencies in Maven.
We could provide quick fixes for JDT on certain set of package names (i.e. if error
related to something under org.jboss.modules.* then we could suggeest adding either
jboss.org community repo or maven eap repo to settings.xml)
If the missing depedency mentions -redhat as the suffix then the user might want to get
access to Maven EAP repo.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:13 a.m.
[
https://issues.jboss.org/browse/JBIDE-9921?page=com.atlassian.jira.plugin...
]
Fred Bricon commented on JBIDE-9921:
------------------------------------
I don't think hooking into JDT compilation errors is a good idea. If there is a
compilation problem, that means there's a missing dependency : that's where I
would try to add the quick fix (markers on the pom/project level)
If we consider there's a high probability we can achieve hooking up to the Dependency
Error markers, I can imagine adding the jboss.org repos to the settings.xml but we'd
need to know where the EAP repo is coming from (user install / remote repo?) before adding
the relevant snippet. Maybe add a dialog box before changing the settings?
Investigate if we can add quickfixes for missing
dependencies/packages based on JDT and M2E error markers
---------------------------------------------------------------------------------------------------------
Key: JBIDE-9921
URL: https://issues.jboss.org/browse/JBIDE-9921
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: maven
Reporter: Max Rydahl Andersen
Assignee: Fred Bricon
Priority: Critical
Fix For: 3.3.0.Beta1
users of maven and our examples might bump into not being able to resolve artifacts from
jboss.org or Maven EAP repository.
This should show up as error markers for packages in JDT and if user uses maven missing
dependencies in Maven.
We could provide quick fixes for JDT on certain set of package names (i.e. if error
related to something under org.jboss.modules.* then we could suggeest adding either
jboss.org community repo or maven eap repo to settings.xml)
If the missing depedency mentions -redhat as the suffix then the user might want to get
access to Maven EAP repo.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:07 a.m.
[
https://issues.jboss.org/browse/JBIDE-9921?page=com.atlassian.jira.plugin...
]
Max Rydahl Andersen commented on JBIDE-9921:
--------------------------------------------
about JDT compilation errors then that is actually easy to do - and other plugins do it
already, i.e. if you import org.junit.* but dont have it on the classpath the junit plugin
will suggest to add its classpath container (evil ;)
Similar Maven does or I think did do it previously to search Maven repositories for it -
but I believe they removed that.
But sure at pom level it becomes relevant and this is where we could ask the user to point
to a zip/directory and we set it up in maven settings.xml (optimally be able to download
it via the "downloadruntime" extension point snjezna made)
And yes - use the eclipse preview dialog before finishing the changes
Investigate if we can add quickfixes for missing
dependencies/packages based on JDT and M2E error markers
---------------------------------------------------------------------------------------------------------
Key: JBIDE-9921
URL: https://issues.jboss.org/browse/JBIDE-9921
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: maven
Reporter: Max Rydahl Andersen
Assignee: Fred Bricon
Priority: Critical
Fix For: 3.3.0.Beta1
users of maven and our examples might bump into not being able to resolve artifacts from
jboss.org or Maven EAP repository.
This should show up as error markers for packages in JDT and if user uses maven missing
dependencies in Maven.
We could provide quick fixes for JDT on certain set of package names (i.e. if error
related to something under org.jboss.modules.* then we could suggeest adding either
jboss.org community repo or maven eap repo to settings.xml)
If the missing depedency mentions -redhat as the suffix then the user might want to get
access to Maven EAP repo.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:08 p.m.
[
https://issues.jboss.org/browse/JBIDE-9921?page=com.atlassian.jira.plugin...
]
Fred Bricon commented on JBIDE-9921:
------------------------------------
Tested a quick POC to see how we can plug ourselves to the dependency resolution error
markers.
Turns out we'll have to manually parse the error message to retrieve the missing
dependency information. Yuck!
Long term solution will require changes upstream :
https://bugs.eclipse.org/bugs/show_bug.cgi?id=361445
Investigate if we can add quickfixes for missing
dependencies/packages based on JDT and M2E error markers
---------------------------------------------------------------------------------------------------------
Key: JBIDE-9921
URL: https://issues.jboss.org/browse/JBIDE-9921
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: maven
Reporter: Max Rydahl Andersen
Assignee: Fred Bricon
Priority: Critical
Fix For: 3.3.0.Beta1
users of maven and our examples might bump into not being able to resolve artifacts from
jboss.org or Maven EAP repository.
This should show up as error markers for packages in JDT and if user uses maven missing
dependencies in Maven.
We could provide quick fixes for JDT on certain set of package names (i.e. if error
related to something under org.jboss.modules.* then we could suggeest adding either
jboss.org community repo or maven eap repo to settings.xml)
If the missing depedency mentions -redhat as the suffix then the user might want to get
access to Maven EAP repo.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
6 a.m.
[
https://issues.jboss.org/browse/JBIDE-9921?page=com.atlassian.jira.plugin...
]
Max Rydahl Andersen commented on JBIDE-9921:
--------------------------------------------
annoying having to parse, or just look for "-redhat" - but otherwise excellent
news!
Investigate if we can add quickfixes for missing
dependencies/packages based on JDT and M2E error markers
---------------------------------------------------------------------------------------------------------
Key: JBIDE-9921
URL: https://issues.jboss.org/browse/JBIDE-9921
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: maven
Reporter: Max Rydahl Andersen
Assignee: Fred Bricon
Priority: Critical
Fix For: 3.3.0.Beta1
users of maven and our examples might bump into not being able to resolve artifacts from
jboss.org or Maven EAP repository.
This should show up as error markers for packages in JDT and if user uses maven missing
dependencies in Maven.
We could provide quick fixes for JDT on certain set of package names (i.e. if error
related to something under org.jboss.modules.* then we could suggeest adding either
jboss.org community repo or maven eap repo to settings.xml)
If the missing depedency mentions -redhat as the suffix then the user might want to get
access to Maven EAP repo.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:05 a.m.
[
https://issues.jboss.org/browse/JBIDE-9921?page=com.atlassian.jira.plugin...
]
Fred Bricon updated JBIDE-9921:
-------------------------------
Attachment: jboss-quickfix.png
redhat-quickfix.png
If a missing dependency groupId is prefixed with "org.jboss", then the quickfix
says "See how to setup JBoss repositories in your settings.xml" and will open
http://community.jboss.org/wiki/SettingUpTheJBossEnterpriseRepositories in the browser :
!jboss-quickfix.png!
Similarly, if the missing dependency version contains "-redhat", the quickfix
label will be "See how to setup JBoss Enterprise repositories in your
settings.xml" and will open
http://community.jboss.org/wiki/SettingUpTheJBossEnterpriseRepositories :
!redhat-quickfix.png!
Investigate if we can add quickfixes for missing
dependencies/packages based on JDT and M2E error markers
---------------------------------------------------------------------------------------------------------
Key: JBIDE-9921
URL: https://issues.jboss.org/browse/JBIDE-9921
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: maven
Reporter: Max Rydahl Andersen
Assignee: Fred Bricon
Priority: Critical
Fix For: 3.3.0.M5
Attachments: jboss-quickfix.png, redhat-quickfix.png
users of maven and our examples might bump into not being able to resolve artifacts from
jboss.org or Maven EAP repository.
This should show up as error markers for packages in JDT and if user uses maven missing
dependencies in Maven.
We could provide quick fixes for JDT on certain set of package names (i.e. if error
related to something under org.jboss.modules.* then we could suggeest adding either
jboss.org community repo or maven eap repo to settings.xml)
If the missing depedency mentions -redhat as the suffix then the user might want to get
access to Maven EAP repo.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:10 a.m.
[
https://issues.jboss.org/browse/JBIDE-9921?page=com.atlassian.jira.plugin...
]
Fred Bricon resolved JBIDE-9921.
--------------------------------
Labels: maven new_and_noteworthy quickfix (was: )
Resolution: Done
Investigate if we can add quickfixes for missing
dependencies/packages based on JDT and M2E error markers
---------------------------------------------------------------------------------------------------------
Key: JBIDE-9921
URL: https://issues.jboss.org/browse/JBIDE-9921
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: maven
Reporter: Max Rydahl Andersen
Assignee: Fred Bricon
Priority: Critical
Labels: new_and_noteworthy, maven, quickfix
Fix For: 3.3.0.M5
Attachments: jboss-quickfix.png, redhat-quickfix.png
users of maven and our examples might bump into not being able to resolve artifacts from
jboss.org or Maven EAP repository.
This should show up as error markers for packages in JDT and if user uses maven missing
dependencies in Maven.
We could provide quick fixes for JDT on certain set of package names (i.e. if error
related to something under org.jboss.modules.* then we could suggeest adding either
jboss.org community repo or maven eap repo to settings.xml)
If the missing depedency mentions -redhat as the suffix then the user might want to get
access to Maven EAP repo.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:12 a.m.
[
https://issues.jboss.org/browse/JBIDE-9921?page=com.atlassian.jira.plugin...
]
Fred Bricon edited comment on JBIDE-9921 at 11/26/11 8:11 AM:
--------------------------------------------------------------
If a missing dependency groupId is prefixed with "org.jboss", then the quickfix
says "See how to setup JBoss repositories in your settings.xml" and will open
http://community.jboss.org/wiki/MavenGettingStarted-Users in the browser :
!jboss-quickfix.png!
Similarly, if the missing dependency version contains "-redhat", the quickfix
label will be "See how to setup JBoss Enterprise repositories in your
settings.xml" and will open
http://community.jboss.org/wiki/SettingUpTheJBossEnterpriseRepositories :
!redhat-quickfix.png!
was (Author: fbricon):
If a missing dependency groupId is prefixed with "org.jboss", then the
quickfix says "See how to setup JBoss repositories in your settings.xml" and
will open http://community.jboss.org/wiki/SettingUpTheJBossEnterpriseRepositories in the
browser :
!jboss-quickfix.png!
Similarly, if the missing dependency version contains "-redhat", the quickfix
label will be "See how to setup JBoss Enterprise repositories in your
settings.xml" and will open
http://community.jboss.org/wiki/SettingUpTheJBossEnterpriseRepositories :
!redhat-quickfix.png!
Investigate if we can add quickfixes for missing
dependencies/packages based on JDT and M2E error markers
---------------------------------------------------------------------------------------------------------
Key: JBIDE-9921
URL: https://issues.jboss.org/browse/JBIDE-9921
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: maven
Reporter: Max Rydahl Andersen
Assignee: Fred Bricon
Priority: Critical
Labels: maven, new_and_noteworthy, quickfix
Fix For: 3.3.0.M5
Attachments: jboss-quickfix.png, redhat-quickfix.png
users of maven and our examples might bump into not being able to resolve artifacts from
jboss.org or Maven EAP repository.
This should show up as error markers for packages in JDT and if user uses maven missing
dependencies in Maven.
We could provide quick fixes for JDT on certain set of package names (i.e. if error
related to something under org.jboss.modules.* then we could suggeest adding either
jboss.org community repo or maven eap repo to settings.xml)
If the missing depedency mentions -redhat as the suffix then the user might want to get
access to Maven EAP repo.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:15 a.m.
[
https://issues.jboss.org/browse/JBIDE-9921?page=com.atlassian.jira.plugin...
]
Fred Bricon commented on JBIDE-9921:
------------------------------------
Implementing quick fixes for JDT error markers doesn't make sense in my opinion, as it
could very well be caused by dependencies not being declared in the pom.xml
Investigate if we can add quickfixes for missing
dependencies/packages based on JDT and M2E error markers
---------------------------------------------------------------------------------------------------------
Key: JBIDE-9921
URL: https://issues.jboss.org/browse/JBIDE-9921
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: maven
Reporter: Max Rydahl Andersen
Assignee: Fred Bricon
Priority: Critical
Labels: maven, new_and_noteworthy, quickfix
Fix For: 3.3.0.M5
Attachments: jboss-quickfix.png, redhat-quickfix.png
users of maven and our examples might bump into not being able to resolve artifacts from
jboss.org or Maven EAP repository.
This should show up as error markers for packages in JDT and if user uses maven missing
dependencies in Maven.
We could provide quick fixes for JDT on certain set of package names (i.e. if error
related to something under org.jboss.modules.* then we could suggeest adding either
jboss.org community repo or maven eap repo to settings.xml)
If the missing depedency mentions -redhat as the suffix then the user might want to get
access to Maven EAP repo.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:17 a.m.
New subject: [JBoss JIRA] (JBIDE-9921) Add quickfixes for missing dependencies/packages based on M2E error markers
[
https://issues.jboss.org/browse/JBIDE-9921?page=com.atlassian.jira.plugin...
]
Fred Bricon updated JBIDE-9921:
-------------------------------
Summary: Add quickfixes for missing dependencies/packages based on M2E error markers
(was: Investigate if we can add quickfixes for missing dependencies/packages based on JDT
and M2E error markers)
Add quickfixes for missing dependencies/packages based on M2E error
markers
---------------------------------------------------------------------------
Key: JBIDE-9921
URL: https://issues.jboss.org/browse/JBIDE-9921
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: maven
Reporter: Max Rydahl Andersen
Assignee: Fred Bricon
Priority: Critical
Labels: maven, new_and_noteworthy, quickfix
Fix For: 3.3.0.M5
Attachments: jboss-quickfix.png, redhat-quickfix.png
users of maven and our examples might bump into not being able to resolve artifacts from
jboss.org or Maven EAP repository.
This should show up as error markers for packages in JDT and if user uses maven missing
dependencies in Maven.
We could provide quick fixes for JDT on certain set of package names (i.e. if error
related to something under org.jboss.modules.* then we could suggeest adding either
jboss.org community repo or maven eap repo to settings.xml)
If the missing depedency mentions -redhat as the suffix then the user might want to get
access to Maven EAP repo.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:17 a.m.
New subject: [JBoss JIRA] (JBIDE-9921) Add quickfixes for missing dependencies/packages based on M2E error markers
[
https://issues.jboss.org/browse/JBIDE-9921?page=com.atlassian.jira.plugin...
]
Fred Bricon updated JBIDE-9921:
-------------------------------
Issue Type: Feature Request (was: Bug)
Add quickfixes for missing dependencies/packages based on M2E error
markers
---------------------------------------------------------------------------
Key: JBIDE-9921
URL: https://issues.jboss.org/browse/JBIDE-9921
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: maven
Reporter: Max Rydahl Andersen
Assignee: Fred Bricon
Priority: Critical
Labels: maven, new_and_noteworthy, quickfix
Fix For: 3.3.0.M5
Attachments: jboss-quickfix.png, redhat-quickfix.png
users of maven and our examples might bump into not being able to resolve artifacts from
jboss.org or Maven EAP repository.
This should show up as error markers for packages in JDT and if user uses maven missing
dependencies in Maven.
We could provide quick fixes for JDT on certain set of package names (i.e. if error
related to something under org.jboss.modules.* then we could suggeest adding either
jboss.org community repo or maven eap repo to settings.xml)
If the missing depedency mentions -redhat as the suffix then the user might want to get
access to Maven EAP repo.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:22 a.m.
New subject: [JBoss JIRA] (JBIDE-9921) Add quickfixes for missing dependencies/packages based on M2E error markers
[
https://issues.jboss.org/browse/JBIDE-9921?page=com.atlassian.jira.plugin...
]
Fred Bricon edited comment on JBIDE-9921 at 11/26/11 8:22 AM:
--------------------------------------------------------------
As I already said, implementing quick fixes for JDT error markers doesn't make sense
in my opinion, as it could very well be caused by dependencies not being declared in the
pom.xml.
Regarding automatic download of the missing repos via the runtime detection mechanism, we
need to be able to access these repos via a public url.
Will open an enhancement request when that is available.
was (Author: fbricon):
Implementing quick fixes for JDT error markers doesn't make sense in my opinion,
as it could very well be caused by dependencies not being declared in the pom.xml
Add quickfixes for missing dependencies/packages based on M2E error
markers
---------------------------------------------------------------------------
Key: JBIDE-9921
URL: https://issues.jboss.org/browse/JBIDE-9921
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: maven
Reporter: Max Rydahl Andersen
Assignee: Fred Bricon
Priority: Critical
Labels: maven, new_and_noteworthy, quickfix
Fix For: 3.3.0.M5
Attachments: jboss-quickfix.png, redhat-quickfix.png
users of maven and our examples might bump into not being able to resolve artifacts from
jboss.org or Maven EAP repository.
This should show up as error markers for packages in JDT and if user uses maven missing
dependencies in Maven.
We could provide quick fixes for JDT on certain set of package names (i.e. if error
related to something under org.jboss.modules.* then we could suggeest adding either
jboss.org community repo or maven eap repo to settings.xml)
If the missing depedency mentions -redhat as the suffix then the user might want to get
access to Maven EAP repo.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:05 a.m.
New subject: [JBoss JIRA] (JBIDE-9921) Add quickfixes for missing dependencies/packages based on M2E error markers
[
https://issues.jboss.org/browse/JBIDE-9921?page=com.atlassian.jira.plugin...
]
Max Rydahl Andersen commented on JBIDE-9921:
--------------------------------------------
runtime detection does not need a public url - just need to scan a directory and detect
its a maven repository.
But the more I think about it the more tricky this will be to setup this way since we
can't automatically setup this repo in users settings.xml.
Add quickfixes for missing dependencies/packages based on M2E error
markers
---------------------------------------------------------------------------
Key: JBIDE-9921
URL: https://issues.jboss.org/browse/JBIDE-9921
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: maven
Reporter: Max Rydahl Andersen
Assignee: Fred Bricon
Priority: Critical
Labels: maven, new_and_noteworthy, quickfix
Fix For: 3.3.0.M5
Attachments: jboss-quickfix.png, redhat-quickfix.png
users of maven and our examples might bump into not being able to resolve artifacts from
jboss.org or Maven EAP repository.
This should show up as error markers for packages in JDT and if user uses maven missing
dependencies in Maven.
We could provide quick fixes for JDT on certain set of package names (i.e. if error
related to something under org.jboss.modules.* then we could suggeest adding either
jboss.org community repo or maven eap repo to settings.xml)
If the missing depedency mentions -redhat as the suffix then the user might want to get
access to Maven EAP repo.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:08 a.m.
New subject: [JBoss JIRA] (JBIDE-9921) Add quickfixes for missing dependencies/packages based on M2E error markers
[
https://issues.jboss.org/browse/JBIDE-9921?page=com.atlassian.jira.plugin...
]
Lucia Jelinkova closed JBIDE-9921.
----------------------------------
Verified in JBDS 5.0.0.v201112111508M-H55-M5
Add quickfixes for missing dependencies/packages based on M2E error
markers
---------------------------------------------------------------------------
Key: JBIDE-9921
URL: https://issues.jboss.org/browse/JBIDE-9921
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: maven
Reporter: Max Rydahl Andersen
Assignee: Fred Bricon
Priority: Critical
Labels: maven, new_and_noteworthy, quickfix
Fix For: 3.3.0.M5
Attachments: jboss-quickfix.png, redhat-quickfix.png
users of maven and our examples might bump into not being able to resolve artifacts from
jboss.org or Maven EAP repository.
This should show up as error markers for packages in JDT and if user uses maven missing
dependencies in Maven.
We could provide quick fixes for JDT on certain set of package names (i.e. if error
related to something under org.jboss.modules.* then we could suggeest adding either
jboss.org community repo or maven eap repo to settings.xml)
If the missing depedency mentions -redhat as the suffix then the user might want to get
access to Maven EAP repo.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:36 p.m.
New subject: [JBoss JIRA] (JBIDE-9921) Add quickfixes for missing dependencies/packages based on M2E error markers
[
https://issues.jboss.org/browse/JBIDE-9921?page=com.atlassian.jira.plugin...
]
Isaac Rooskov updated JBIDE-9921:
---------------------------------
Release Notes Docs Status: Not Required
Writer: irooskov
Release Notes Text: As Maven integration is new for JBDS 5, a release note of
this feature is not required. All Maven functionality will be covered in the Overview
section of the Release Notes and in the documentation.
Add quickfixes for missing dependencies/packages based on M2E error
markers
---------------------------------------------------------------------------
Key: JBIDE-9921
URL: https://issues.jboss.org/browse/JBIDE-9921
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: maven
Reporter: Max Rydahl Andersen
Assignee: Fred Bricon
Priority: Critical
Labels: maven, new_and_noteworthy, quickfix
Fix For: 3.3.0.M5
Attachments: jboss-quickfix.png, redhat-quickfix.png
users of maven and our examples might bump into not being able to resolve artifacts from
jboss.org or Maven EAP repository.
This should show up as error markers for packages in JDT and if user uses maven missing
dependencies in Maven.
We could provide quick fixes for JDT on certain set of package names (i.e. if error
related to something under org.jboss.modules.* then we could suggeest adding either
jboss.org community repo or maven eap repo to settings.xml)
If the missing depedency mentions -redhat as the suffix then the user might want to get
access to Maven EAP repo.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:36 p.m.
New subject: [JBoss JIRA] (JBIDE-9921) Add quickfixes for missing dependencies/packages based on M2E error markers
[
https://issues.jboss.org/browse/JBIDE-9921?page=com.atlassian.jira.plugin...
]
Isaac Rooskov closed JBIDE-9921.
--------------------------------
Resolution: Done
Re-closing issue now that release note status has been set
Add quickfixes for missing dependencies/packages based on M2E error
markers
---------------------------------------------------------------------------
Key: JBIDE-9921
URL: https://issues.jboss.org/browse/JBIDE-9921
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: maven
Reporter: Max Rydahl Andersen
Assignee: Fred Bricon
Priority: Critical
Labels: maven, new_and_noteworthy, quickfix
Fix For: 3.3.0.M5
Attachments: jboss-quickfix.png, redhat-quickfix.png
users of maven and our examples might bump into not being able to resolve artifacts from
jboss.org or Maven EAP repository.
This should show up as error markers for packages in JDT and if user uses maven missing
dependencies in Maven.
We could provide quick fixes for JDT on certain set of package names (i.e. if error
related to something under org.jboss.modules.* then we could suggeest adding either
jboss.org community repo or maven eap repo to settings.xml)
If the missing depedency mentions -redhat as the suffix then the user might want to get
access to Maven EAP repo.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5112
days inactive
5289
days old
jbosstools-issues@lists.jboss.org
15 comments
8 participants
participants (8)
-
Fred Bricon (Commented) (JIRA) -
Fred Bricon (Issue Comment Edited) (JIRA)
-
Fred Bricon (Resolved) (JIRA)
-
Fred Bricon (Updated) (JIRA)
-
Isaac Rooskov (JIRA)
-
Lucia Jelinkova (Closed) (JIRA)
-
Max Rydahl Andersen (Commented) (JIRA)
-
Max Rydahl Andersen (Created) (JIRA)