[JBoss JIRA] (JBIDE-12419) archives core should not have references to NLS class in src/main
by Rob Stryker (JIRA)
Rob Stryker created JBIDE-12419:
-----------------------------------
Summary: archives core should not have references to NLS class in src/main
Key: JBIDE-12419
URL: https://issues.jboss.org/browse/JBIDE-12419
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Archives
Affects Versions: 3.3.1
Reporter: Rob Stryker
Assignee: Rob Stryker
Fix For: 3.3.2, 3.4.0.M1
The old use case to run project archives from cmd line requires a strict set of jars. References to NLS class are not allowed. Problem can be seen in build unit test SimpleAntTest
Error Message
The ant task did not successfully complete. BUILD FAILED /mnt/hudson_workspace/workspace/jbosstools-3.3_trunk.component--archives/sources/tests/org.jboss.ide.eclipse.archives.test/target/work/data/AntTest/build.xml:25: java.lang.NoClassDefFoundError: org/eclipse/osgi/util/NLS
Stacktrace
junit.framework.AssertionFailedError: The ant task did not successfully complete.
BUILD FAILED
/mnt/hudson_workspace/workspace/jbosstools-3.3_trunk.component--archives/sources/tests/org.jboss.ide.eclipse.archives.test/target/work/data/AntTest/build.xml:25: java.lang.NoClassDefFoundError: org/eclipse/osgi/util/NLS
--
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
11 years, 5 months
[JBoss JIRA] (JBIDE-12088) merge all Teiid requirement builders (7.4 - 8.0) into a single target?
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-12088:
----------------------------------
Summary: merge all Teiid requirement builders (7.4 - 8.0) into a single target?
Key: JBIDE-12088
URL: https://issues.jboss.org/browse/JBIDE-12088
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: teiid
Affects Versions: 3.3.0.CR1, 3.4.0.M1
Reporter: Nick Boldt
Assignee: Barry LaFond
Currently, there are 5 requirements builders for Teiid, from 7.4 - 8.0.Alpha1.
You could, like with SOAP, merge these into a single builder so that it's easier to run tests against all supported runtimes via a single target.
Thus your tests' requirements.properties file would read:
{code}requirements=teiid{code}
instead of
{code}requirements=teiid-7.4.0.Final,teiid-7.5.0.Final,teiid-7.6.0.Final,teiid-8.0.0.Alpha1<code{
Would this be useful?
If so, see attached patch.
--
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
11 years, 5 months
[JBoss JIRA] (JBIDE-12307) unified.target appears broken
by Paul Richardson (JIRA)
Paul Richardson created JBIDE-12307:
---------------------------------------
Summary: unified.target appears broken
Key: JBIDE-12307
URL: https://issues.jboss.org/browse/JBIDE-12307
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: target-platform
Affects Versions: 3.4.x
Environment: Either installed Eclipse Indigo or Juno
Reporter: Paul Richardson
Assignee: Nick Boldt
Use of the unified.target fails as PDE target platform for both Indigo and Juno.
*Indigo IDE*
Use of the trunk version of unified.target results in org.lucene.core 3.5-4 not being found, which is true since only version 2.91 is available in the update site - http://download.jboss.org/jbosstools/updates/target-platform_3.4.juno.SR0...
*Juno IDE*
Use of the trunk version of unified.target results in package org.xmlpull.mxp1 not being found as a requirement of XStream.
Both errors imply an incomplete target platform but does the fact that they are different errors imply that plugins in the installed IDE are assumed to be there?
Should it not be possible to take an eclipse Indigo and develop against a Juno target platform?
--
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
11 years, 5 months
[JBoss JIRA] Created: (JBIDE-8973) Provide a way to convert pure java libs into maven provided dependencies
by Max Rydahl Andersen (JIRA)
Provide a way to convert pure java libs into maven provided dependencies
------------------------------------------------------------------------
Key: JBIDE-8973
URL: https://issues.jboss.org/browse/JBIDE-8973
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Reporter: Max Rydahl Andersen
Fix For: 3.3.0.M3
Execute: multiple select lib dependencies, then right click and choose "Build path > Convert to Maven dependencies"
Assert: UI is shown that shows which jars misses metadata and what can be automatically detected based on maven metadata in the jar. UI has option to delete jars from project.
Execute: Press Ok
Assert: The jars are removed from classpath container, and now available in the classpath container and if user chose to delete then the files are removed from the project.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 5 months