[
https://issues.jboss.org/browse/JBIDE-13928?page=com.atlassian.jira.plugi...
]
Fred Bricon commented on JBIDE-13928:
-------------------------------------
I don't see why we would need the sources *inside* JBDS.
Except for m2e and its sdk (I wonder why it's there BTW), no m2e related plugins
(m2e-* or org.jboss.tools.maven.*) are currently included in JBDS
As for having the sources available in the TP for developer consumption, there's no
reason why it should be treated differently than other plugins.
Should JBoss Tools and JBDS include
org.jboss.tools.maven.apt.feature.source, or just org.jboss.tools.maven.apt.feature?
------------------------------------------------------------------------------------------------------------------------
Key: JBIDE-13928
URL:
https://issues.jboss.org/browse/JBIDE-13928
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: maven, UpStream
Affects Versions: 4.1.0.Alpha2
Reporter: Nick Boldt
Assignee: Fred Bricon
In JBIDE-12310 a source feature was added to org.jboss.tools.maven.apt.feature, but the
second part of the JIRA was never done -- adding that feature to JBT and JBDS.
Today, I attempted to add it, and realized that unless we add
org.jboss.tools.maven.apt.feature.source to the target platform it won't be available
when creating the JBT or JBDS aggregate sites.
Do we care? Do we need the sources for this feature/plugin included in JBT and JBDS?
If we only need it in JBDS I can add the latest m2e mirror to the Central/Extras site [1]
and be able to resolve it from there.
[1]
https://devstudio.jboss.com/updates/7.0-development/extras/
--
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