[JBoss JIRA] (JBIDE-12815) Create a JBoss Tools Orbit
by Mickael Istria (JIRA)
Mickael Istria created JBIDE-12815:
--------------------------------------
Summary: Create a JBoss Tools Orbit
Key: JBIDE-12815
URL: https://issues.jboss.org/browse/JBIDE-12815
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Build/Releng, UpStream
Reporter: Mickael Istria
Assignee: Paul Richardson
Since all JBoss Eclipse-based project probably share some needs for usual libraries, we should create a JBoss Tools Orbit project in which one we would provide those 3rd-party dependencies packaged as OSGi Bundle in a p2 repository.
In a first time, we could simply create some OSGi "wrappers" around those jars.
--
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
13 years, 4 months
[JBoss JIRA] (JBIDE-12505) ensure all JBT SOA components have published exploded update sites on http://download.jboss.org/jbosstools/updates/
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-12505:
----------------------------------
Summary: ensure all JBT SOA components have published exploded update sites on http://download.jboss.org/jbosstools/updates/
Key: JBIDE-12505
URL: https://issues.jboss.org/browse/JBIDE-12505
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng, SOA Tooling, updatesite
Affects Versions: 3.3.0.Final-SOA, 4.0.0.M1-SOA
Reporter: Nick Boldt
Assignee: Nick Boldt
For each of the JBT SOA components, we should ensure that they're all publishing into standard locations on http://download.jboss.org/jbosstools/updates/.
This issue should be a container for child issues assigned to each project's releng person.
Done:
* SwitchYard - JBIDE-10672 - http://download.jboss.org/jbosstools/updates/stable/indigo/soa-tooling/sw...
Publishes elsewhere, manually symlinked:
* Drools/jbpm5 - JBRULES-3470 - http://download.jboss.org/jbosstools/updates/stable/indigo/soa-tooling/dr...
Publishes elsewhere:
* Modeshape Tools - JBBUILD-720, MODE-1506 - http://download.jboss.org/modeshape/builds/staging/modeshape-tools-contin... ?
* Savara - http://download.jboss.org/savara/releases/updates/2.0.x/
* pi4soa - http://pi4soa.sourceforge.net/updates/
Publishes as zip only:
* Teiid Designer - https://www.jboss.org/teiiddesigner/downloads/ -> http://sourceforge.net/projects/teiid/files/teiid-designer/7.7/teiid_desi...
No publishing strategy (staging only):
* ESB - staging site only, eg., http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.3_trunk....
* jbpm3 - staging site only, eg., http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.3_trunk....
* JBoss BPEL - staging site only, eg., http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.3_trunk....
--
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
13 years, 4 months
[JBoss JIRA] (JBIDE-12615) allow as7 classpath containers have access restrictions
by Rob Stryker (JIRA)
Rob Stryker created JBIDE-12615:
-----------------------------------
Summary: allow as7 classpath containers have access restrictions
Key: JBIDE-12615
URL: https://issues.jboss.org/browse/JBIDE-12615
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: JBossAS/Servers
Affects Versions: 4.0.0.Alpha1
Reporter: Rob Stryker
Assignee: Rob Stryker
Fix For: 4.0.0.Alpha2
We will eventually have access restrictions on the as7 jars provided. This will require the classpath container in charge of making the entries to provide the classpath acces rules.
ClientAllRuntimeClasspathProvider:
protected IClasspathEntry getEntry(Entry entry) {
IPath p = entry.getPath();
IAccessRule[] rules = null;
if( p.toString().contains("picketbox")) {
IPath filePattern= new Path("**/ssl/**");
rules = new IAccessRule[]{JavaCore.newAccessRule(filePattern, IAccessRule.K_NON_ACCESSIBLE)};
System.out.println("break here");
}
IClasspathEntry e = JavaCore.newLibraryEntry(entry.getPath(), null, null,
rules == null ? ClasspathEntry.NO_ACCESS_RULES : rules,
ClasspathEntry.NO_EXTRA_ATTRIBUTES,
false/*not exported*/);
Above is example code.
--
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
13 years, 4 months