[JBoss JIRA] (JBDS-2339) create Marketplace entry for JBDS 6 so we can publish the "Core Features" feature
by Nick Boldt (JIRA)
Nick Boldt created JBDS-2339:
--------------------------------
Summary: create Marketplace entry for JBDS 6 so we can publish the "Core Features" feature
Key: JBDS-2339
URL: https://issues.jboss.org/browse/JBDS-2339
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Components: Build, updatesite
Affects Versions: 6.0.0.Alpha2
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 6.0.0.Beta1
As per decisions in JBDS-2253, I need to create an Eclipse Marketplace entry for JBDS 6 so we can publish the "Core Features" feature and get people trying it out that way instead of via Early Access update site or installer.
--
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-12846) compiler error in org.jboss.ide.eclipse.archives.test blocks publishing updated archives update site to downstream
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-12846:
----------------------------------
Summary: compiler error in org.jboss.ide.eclipse.archives.test blocks publishing updated archives update site to downstream
Key: JBIDE-12846
URL: https://issues.jboss.org/browse/JBIDE-12846
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Archives
Affects Versions: 4.0.0.Beta1
Reporter: Nick Boldt
Assignee: Rob Stryker
Priority: Blocker
{code}
[INFO] Reactor Summary:
[INFO]
[INFO] archives.all ...................................... SUCCESS [5.457s]
[INFO] archives.plugins .................................. SUCCESS [0.037s]
[INFO] org.jboss.ide.eclipse.archives.core ............... SUCCESS [12.469s]
[INFO] org.jboss.ide.eclipse.archives.ui ................. SUCCESS [6.766s]
[INFO] org.jboss.ide.eclipse.archives.jdt.integration .... SUCCESS [1.737s]
[INFO] archives.features ................................. SUCCESS [0.033s]
[INFO] org.jboss.ide.eclipse.archives.feature ............ SUCCESS [0.796s]
[INFO] archives.tests .................................... SUCCESS [0.030s]
[INFO] org.jboss.ide.eclipse.archives.test ............... FAILURE [1.468s]
[INFO] org.jboss.ide.eclipse.archives.ui.test ............ SUCCESS [3.922s]
[INFO] org.jboss.tools.archives.ui.bot.test .............. SUCCESS [27.573s]
[INFO] org.jboss.ide.eclipse.archives.test.feature ....... SKIPPED
[INFO] archives.site ..................................... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 2:36.854s
[INFO] Finished at: Fri Oct 12 18:35:00 EDT 2012
[INFO] Final Memory: 59M/543M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.15.0:compile (default-compile) on project org.jboss.ide.eclipse.archives.test: Compilation failure: Compilation failure:
[ERROR] /qa/hudson_workspace/workspace/jbosstools-4.0_trunk.component--archives/sources/tests/org.jboss.ide.eclipse.archives.test/src/org/jboss/ide/eclipse/archives/test/ArchivesTestSuite.java:[23,0]
[ERROR] import org.jboss.ide.eclipse.archives.test.model.ReadWriteTest;
[ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[ERROR] The import org.jboss.ide.eclipse.archives.test.model.ReadWriteTest cannot be resolved
[ERROR] /qa/hudson_workspace/workspace/jbosstools-4.0_trunk.component--archives/sources/tests/org.jboss.ide.eclipse.archives.test/src/org/jboss/ide/eclipse/archives/test/ArchivesTestSuite.java:[42,0]
[ERROR] suite.addTestSuite(ReadWriteTest.class);
[ERROR] ^^^^^^^^^^^^
[ERROR] The method addTestSuite(Class<? extends TestCase>) in the type TestSuite is not applicable for the arguments (Class<ReadWriteTest>)
[ERROR] /qa/hudson_workspace/workspace/jbosstools-4.0_trunk.component--archives/sources/tests/org.jboss.ide.eclipse.archives.test/src/org/jboss/ide/eclipse/archives/test/ArchivesTestSuite.java:[42,0]
[ERROR] suite.addTestSuite(ReadWriteTest.class);
[ERROR] ^^^^^^^^^^^^^
[ERROR] ReadWriteTest cannot be resolved to a type
[ERROR] 3 problems (3 errors)
{code}
Also reproduced offline so this is most likely not a "Jenkins is building stuff out of order" issue.
--
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-12466) Find a new home for org.jboss.tools.runtime.as.ui.bot.test
by Rob Stryker (JIRA)
Rob Stryker created JBIDE-12466:
-----------------------------------
Summary: Find a new home for org.jboss.tools.runtime.as.ui.bot.test
Key: JBIDE-12466
URL: https://issues.jboss.org/browse/JBIDE-12466
Project: Tools (JBoss Tools)
Issue Type: Task
Components: runtime detection
Affects Versions: 4.0.0.M1
Reporter: Rob Stryker
Assignee: Len DiMaggio
Fix For: 4.0.0.M1
JIRA JBIDE-12465 will soon disable the org.jboss.tools.runtime.as.ui.bot.test plugin test. It is not the intention that this test plugin disappear; just that it get moved.
The test plugin will be disabled shortly. Once it is removed from the build, it will be safe for QE to find a new home for it. The given test plugin is more of an integration test plugin and belongs with other integration tests and integration swtbot tests.
--
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-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