[JBoss JIRA] Created: (JBDS-1839) JAX-RS maven integration plugin is missing in extra site
by Libor Zoubek (JIRA)
JAX-RS maven integration plugin is missing in extra site
--------------------------------------------------------
Key: JBDS-1839
URL: https://issues.jboss.org/browse/JBDS-1839
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: 3rdPartyCertification, maven
Affects Versions: 5.0.0.M3
Reporter: Libor Zoubek
Fix For: 5.0.0.M4
I was verifying JBIDE-9290 on JBDS with m2e. JAX-RS configurator is missing there. It will definitely make sence to include this plugin when jax-rs tooling becomes part of JBDS. But it might make sense to include it before.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 9 months
[JBoss JIRA] Created: (JBIDE-9309) Easily adding full JBoss AS source
by arjan tijms (JIRA)
Easily adding full JBoss AS source
----------------------------------
Key: JBIDE-9309
URL: https://issues.jboss.org/browse/JBIDE-9309
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: JBossAS
Reporter: arjan tijms
Assignee: Rob Stryker
The JBoss AS server runtime from JBoss tools adds a library container to the classpath of an Eclipse project. This container provides a large amount of jar files that make up JBoss AS itself and the Java EE services it offers.
Attaching the source code for this is notoriously difficult. Because it concerns a large amount of jar files, attaching source code for each jar is a rather tedious job.
For JBoss AS 5, the fact that the location of jars in the source archive was completely different from the structure exposed in Eclipse or the binary build of JBoss AS, made it very hard to actually locate the correct source jar. Sometimes even names were different, making it even harder.
For JBoss AS 6, the source archive does not even contain the source for the majority of the JBoss AS artifacts. Source for 'core functionality' (from the point of view of the Java EE developer), like Servlet and JSF is missing. The user has to hunt the Internet to find the correct source for the correct version that JBoss AS 6 uses. This makes an already tedious job even more tedious.
I would like to request functionality where the user can point to a single _jboss-src.xyz_ file that contains all sources. JBoss tools should then automatically attach the right source from the archive to the right jar from the library container. Alternatively the user could point to a maven repository (but this should not make the Eclipse project dependent on maven).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 10 months
[JBoss JIRA] Created: (JBIDE-9688) Add JBoss public repository to list of default repositories in Eclipse
by Rob Cernich (JIRA)
Add JBoss public repository to list of default repositories in Eclipse
----------------------------------------------------------------------
Key: JBIDE-9688
URL: https://issues.jboss.org/browse/JBIDE-9688
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: maven
Reporter: Rob Cernich
Assignee: Fred Bricon
Priority: Minor
M2e exposes an extension point, which allows plugins to contribute repositories to be indexed. Automatically registering the JBoss repository seems like a sensible thing for JBoss Tools. This would allow the user to access the JBoss public repository from the tooling (e.g. add dependency) without requiring them to add the JBoss public repository to their settings.xml file. Of course, the user would still need to ensure that the repository was correctly configured within their pom so the project will build correctly.
The following is all that is required (in plugin.xml):
<extension
point="org.eclipse.m2e.core.indexes">
<index
indexId="JBOSS_NEXUS"
isShort="true"
repositoryUrl="http://repository.jboss.org/nexus/content/groups/public">
</index>
</extension>
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 10 months