[
https://jira.jboss.org/browse/JBIDE-6927?page=com.atlassian.jira.plugin.s...
]
Gary Brown edited comment on JBIDE-6927 at 8/31/10 6:09 AM:
------------------------------------------------------------
Added you to svn, however would prefer if the plugins/features/site/tests could remain in
the tools subfolder, as it separates them off from the other parts of the Savara build
(i.e. docs, runtime components etc).
Wouldn't it be useful to be able to specify an optional subfolder for the Eclipse
tools in the publish.sh script, as I am sure this requirement may come up again in the
future?
was (Author: objectiser):
Added you to svn, however would prefer if the plugins/features/site/tests could remain
in the tools subfolder, as it separates them off from the other parts of the Savara build
(i.e. docs, runtime components etc).
Wouldn't it be useful to be able to specify a subfolder for the Eclipse tools in the
publish.sh script, as I am sure this requirement may come up again in the future?
Integrate Savara plugins into JBoss Tools
-----------------------------------------
Key: JBIDE-6927
URL:
https://jira.jboss.org/browse/JBIDE-6927
Project: Tools (JBoss Tools)
Issue Type: Task
Reporter: Gary Brown
Assignee: Nick Boldt
Fix For: 3.2.0.Beta
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
The requested information is:
a) where Savara's build job is located (URL)
Savara-1.0.x is the currently released version, which was not built using Tycho - so this
version should not be integrated.
Savara-1.1.0 (which is currently trunk) hudson job is here:
http://hudson.qa.jboss.com/hudson/job/savara/
The tools part is located in a 'tools' sub-folder, within trunk.
b) where Savara's update site is published (URL)
Originally was publishing using the publish.sh script as part of jboss tools, but a
change was made that causes it to fail, I think due to the fact that the Eclipse
plugins/features/site are within a sub-folder, and not at the root of the build job. So
currently the hudson job just provides the link to the latest built artifacts, which
include the update site zip.
The hudson job also builds a runtime distribution for Savara.
c) the category name / label / description for the aggregate update site
(chunk of XML)
Savara / Savara / Tooling support for the Savara "Testable Architecture"
capabilities.
d) any other categories in which the Savara stuff needs to be included
(chunk(s) of XML)
e) the full list of Savara feature names to be included (plain text, as
pulled from your feature.xml's ID field(s))
org.jboss.savara.tools.feature
org.jboss.savara.experimental.feature
org.scribble.protocol.feature
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira