6:50 a.m.
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
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
12:08 p.m.
New subject: [JBoss JIRA] Updated: (JBIDE-6927) Integrate Savara plugins into JBoss Tools
[
https://jira.jboss.org/browse/JBIDE-6927?page=com.atlassian.jira.plugin.s...
]
Brian Fitzpatrick updated JBIDE-6927:
-------------------------------------
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
Fix Version/s: 3.2.0.Beta
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
11:08 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6927) Integrate Savara plugins into JBoss Tools
[
https://jira.jboss.org/browse/JBIDE-6927?page=com.atlassian.jira.plugin.s...
]
Nick Boldt commented on JBIDE-6927:
-----------------------------------
If you move your site/ folder into the root next to plugins/ and features/ then the
publish script will work without needing to support your special case, and I can integrate
your features into the trunk builds of JBT.
Or, give me write access to your SVN repo and I'll do the refactoring for you.
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
5:10 a.m.
New subject: [JBoss JIRA] Issue Comment Edited: (JBIDE-6927) Integrate Savara plugins into JBoss Tools
[
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
12:08 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6927) Integrate Savara plugins into JBoss Tools
[
https://jira.jboss.org/browse/JBIDE-6927?page=com.atlassian.jira.plugin.s...
]
Nick Boldt commented on JBIDE-6927:
-----------------------------------
Moving stuff around turns out to be unnecessary. Latest Savara build is here:
http://hudson.qa.jboss.com/hudson/job/savara/69/
http://download.jboss.org/jbosstools/builds/staging/savara/ (build folder)
http://download.jboss.org/jbosstools/builds/staging/savara/tools/ (update site)
And the latest aggregate that integrates it is here:
http://hudson.qa.jboss.com/hudson/job/jbosstools-3.2.0.Beta1.aggregate/95... (still
running)
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
2:52 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6927) Integrate Savara plugins into JBoss Tools
[
https://jira.jboss.org/browse/JBIDE-6927?page=com.atlassian.jira.plugin.s...
]
Gary Brown commented on JBIDE-6927:
-----------------------------------
I've added ", **/savara-*.zip" to the 'Files to archive' field, as I
need the zips from the distributions/target folder to be available on the 'latest
artifacts' list aswell.
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
5 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6927) Integrate Savara plugins into JBoss Tools
[
https://jira.jboss.org/browse/JBIDE-6927?page=com.atlassian.jira.plugin.s...
]
Gary Brown commented on JBIDE-6927:
-----------------------------------
Just checked out the
http://hudson.qa.jboss.com/hudson/job/jbosstools-3.2.0.Beta1.aggregate/ page and found
that the link at the top (Updated sites and zips published here) is pointing to 3.2.helios
which is still being used for M2. Is this going to move to beta1 eventually, or does the
link need to be updated to point to another location?
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
1:13 p.m.
New subject: [JBoss JIRA] Updated: (JBIDE-6927) Integrate Savara plugins into JBoss Tools
[
https://jira.jboss.org/browse/JBIDE-6927?page=com.atlassian.jira.plugin.s...
]
Nick Boldt updated JBIDE-6927:
------------------------------
Attachment: Screenshot-JBDS4M2-with-teiid-and-savara-installed-from-trunk.png
Successfully installed Savara category (three features) into JBDS 4.0.0.M2 from the
http://download.jboss.org/jbosstools/updates/nightly/trunk/ (build H99).
[14:00:29]nboldt@x2lappy:~/jbdevstudio-4.0.0.v201009122325R-H468-M2-eap
$ find . -maxdepth 3 -name "*sava*" -o -name "*scrib*"
./eclipse/features/org.jboss.savara.tools.feature_1.1.0.v20100913-0349-H70-SNAPSHOT
./eclipse/features/org.scribble.protocol.feature_1.1.0.v20100913-0349-H70-SNAPSHOT
./eclipse/features/org.jboss.savara.experimental.feature_1.1.0.v20100913-0349-H70-SNAPSHOT
./eclipse/plugins/org.jboss.savara.contract.model_1.1.0.v20100913-0349-H70-SNAPSHOT.jar
./eclipse/plugins/org.scribble.lang.comparator_1.1.0.v20100913-0349-H70-SNAPSHOT.jar
./eclipse/plugins/org.scribble.core_1.1.0.v20100913-0349-H70-SNAPSHOT.jar
./eclipse/plugins/org.scribble.conversation.export.text_1.1.0.v20100913-0349-H70-SNAPSHOT.jar
./eclipse/plugins/org.scribble.eclipse_1.1.0.v20100913-0349-H70-SNAPSHOT.jar
./eclipse/plugins/org.jboss.savara.pi4soa.cdm_1.1.0.v20100913-0349-H70-SNAPSHOT.jar
./eclipse/plugins/org.jboss.savara.tools.wsdl_1.1.0.v20100913-0349-H70-SNAPSHOT.jar
./eclipse/plugins/org.jboss.savara.protocol.contract_1.1.0.v20100913-0349-H70-SNAPSHOT.jar
./eclipse/plugins/org.jboss.savara.tap.model_1.1.0.v20100913-0349-H70-SNAPSHOT.jar
./eclipse/plugins/org.scribble.expression.xpath_1.1.0.v20100913-0349-H70-SNAPSHOT.jar
./eclipse/plugins/org.scribble.conversation.projector_1.1.0.v20100913-0349-H70-SNAPSHOT.jar
./eclipse/plugins/org.scribble.conversation.model_1.1.0.v20100913-0349-H70-SNAPSHOT.jar
./eclipse/plugins/org.scribble.conversation.comparator_1.1.0.v20100913-0349-H70-SNAPSHOT.jar
./eclipse/plugins/org.scribble.lang.model_1.1.0.v20100913-0349-H70-SNAPSHOT.jar
./eclipse/plugins/org.jboss.savara.tools.monitor_1.1.0.v20100913-0349-H70-SNAPSHOT.jar
./eclipse/plugins/org.scribble.conversation.validation_1.1.0.v20100913-0349-H70-SNAPSHOT.jar
./eclipse/plugins/org.scribble.conformance_1.1.0.v20100913-0349-H70-SNAPSHOT.jar
./eclipse/plugins/org.jboss.savara.tools.bpel_1.1.0.v20100913-0349-H70-SNAPSHOT.jar
./eclipse/plugins/org.jboss.savara.tools.bpmn_1.1.0.v20100913-0349-H70-SNAPSHOT.jar
./eclipse/plugins/org.jboss.savara.tools.validator_1.1.0.v20100913-0349-H70-SNAPSHOT.jar
./eclipse/plugins/org.scribble.conversation.parser_1.1.0.v20100913-0349-H70-SNAPSHOT.jar
Note that the Savara stuff is not currently in the "All JBoss Tools" category,
only in its own Savara category, as this is what was requested in the JIRA above. (It
could be in both categories if you wanted.)
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
Attachments: Screenshot-JBDS4M2-with-teiid-and-savara-installed-from-trunk.png
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
1:31 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6927) Integrate Savara plugins into JBoss Tools
[
https://jira.jboss.org/browse/JBIDE-6927?page=com.atlassian.jira.plugin.s...
]
Nick Boldt commented on JBIDE-6927:
-----------------------------------
Link is fixed. You can look here:
http://hudson.qa.jboss.com/hudson/job/jbosstools-3.2.0.Beta1.aggregate/ ->
http://download.jboss.org/jbosstools/builds/nightly/ and
http://download.jboss.org/jbosstools/builds/staging/
From within nightly, pick the latest build. Or look at
http://download.jboss.org/jbosstools/updates/nightly/ for latest update site.
Savara stuff is published into /staging/ and into
http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.2.0.Beta...
Hope that helps!
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: Gary Brown
Fix For: 3.2.0.Beta
Attachments: Screenshot-JBDS4M2-with-teiid-and-savara-installed-from-trunk.png
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
3:23 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6927) Integrate Savara plugins into JBoss Tools
[
https://jira.jboss.org/browse/JBIDE-6927?page=com.atlassian.jira.plugin.s...
]
Gary Brown commented on JBIDE-6927:
-----------------------------------
Confirmed that the plugins load and work fine - thanks.
In terms of the categories, sorry I don't think I thought it through carefully enough
based on the current JBT categories. I think it would be better if the 'pi4soa
core' and the three Savara features were includes in All and SOA Development, instead
of their own category.
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: Gary Brown
Fix For: 3.2.0.Beta
Attachments: Screenshot-JBDS4M2-with-teiid-and-savara-installed-from-trunk.png
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
3:54 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6927) Integrate Savara plugins into JBoss Tools
[
https://jira.jboss.org/browse/JBIDE-6927?page=com.atlassian.jira.plugin.s...
]
Gary Brown commented on JBIDE-6927:
-----------------------------------
As per Max's email, I have created a branch for pi4soa and Savara.
https://pi4soa.svn.sourceforge.net/svnroot/pi4soa/branches/pi4soa-3.1.x
https://svn.jboss.org/repos/savara/branches/1.1.x
I wasn't sure what to do regarding the hudson jobs - I could just copy the existing
jobs, but not sure how the result gets aggregated to the particular release, so wanted to
check what I should do first.
The existing jobs (savara and jbosstools-pi4soa) are pointing to trunk, so I guess they
should still point at trunk, but need to publish their results somewhere else?
Once I know what changes need to be made to the current trunk jobs, then I can create
savara-1.1.x and jbosstools-pi4soa-3.1.x jobs as duplicates of the current jobs.
One final point - a minor change that is not urgent, but in case you have time - I have
made the pi4soa core and scribble protocol features dependencies on the Savara feature, so
they get pulled in automatically. Currently the pi4soa feature is only in the All
category, so was wondering whether it would actually be better for the Scribble protocol
feature to also just be in the All category rather than SOA development?
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
Attachments: Screenshot-JBDS4M2-with-teiid-and-savara-installed-from-trunk.png
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
7:12 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6927) Integrate Savara plugins into JBoss Tools
[
https://jira.jboss.org/browse/JBIDE-6927?page=com.atlassian.jira.plugin.s...
]
Nick Boldt commented on JBIDE-6927:
-----------------------------------
how the result gets aggregated
This is controlled by the aggregate build's config files:
http://anonsvn.jboss.org/repos/jbosstools/trunk/build/aggregate/site/pom.xml lists the
URLs from which we suck in jars.
Thus if you publish to a new URL, I'll just have to update the pom.xml accordingly.
Feel free to copy the jobs and re-assign this to me to update the above file (or if you
have write access, you can DIY in both the 3.2.0.Beta1 branch and in trunk).
To move your feature(s) into different categor(ies) simply edit this
file:
http://anonsvn.jboss.org/repos/jbosstools/trunk/build/aggregate/site/site...
Whether or not you should be in ALL, SOA, or both is not for me to decide: ask Max.
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.Beta1
Attachments: Screenshot-JBDS4M2-with-teiid-and-savara-installed-from-trunk.png
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
7:12 p.m.
New subject: [JBoss JIRA] Issue Comment Edited: (JBIDE-6927) Integrate Savara plugins into JBoss Tools
[
https://jira.jboss.org/browse/JBIDE-6927?page=com.atlassian.jira.plugin.s...
]
Nick Boldt edited comment on JBIDE-6927 at 9/23/10 8:11 PM:
------------------------------------------------------------
how the result gets aggregated
This is controlled by the aggregate build's config files:
http://anonsvn.jboss.org/repos/jbosstools/trunk/build/aggregate/site/pom.xml lists the
URLs from which we suck in jars.
Thus if you publish to a new URL, I'll just have to update the pom.xml accordingly.
Feel free to copy the jobs and re-assign this to me to update the above file (or if you
have write access, you can DIY in both the 3.2.0.Beta1 branch and in trunk).
Currently the pi4soa feature is only in the All category
To move your feature(s) into different categor(ies) simply edit this file:
http://anonsvn.jboss.org/repos/jbosstools/trunk/build/aggregate/site/site...
Whether or not you should be in ALL, SOA, or both is not for me to decide: ask Max.
was (Author: nickboldt):
how the result gets aggregated
This is controlled by the aggregate build's config files:
http://anonsvn.jboss.org/repos/jbosstools/trunk/build/aggregate/site/pom.xml lists the
URLs from which we suck in jars.
Thus if you publish to a new URL, I'll just have to update the pom.xml accordingly.
Feel free to copy the jobs and re-assign this to me to update the above file (or if you
have write access, you can DIY in both the 3.2.0.Beta1 branch and in trunk).
To move your feature(s) into different categor(ies) simply edit this
file:
http://anonsvn.jboss.org/repos/jbosstools/trunk/build/aggregate/site/site...
Whether or not you should be in ALL, SOA, or both is not for me to decide: ask Max.
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.Beta1
Attachments: Screenshot-JBDS4M2-with-teiid-and-savara-installed-from-trunk.png
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
4:53 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6927) Integrate Savara plugins into JBoss Tools
[
https://jira.jboss.org/browse/JBIDE-6927?page=com.atlassian.jira.plugin.s...
]
Gary Brown commented on JBIDE-6927:
-----------------------------------
Created new savara job: http://hudson.qa.jboss.com/hudson/view/SAVARA/job/savara-1.1.x/
Updated the SVN URLs to point to savara-1.1.x branch and jbosstools-3.2.0.Beta1 branch.
Not sure what to do about Beta2 aggregate job at the moment, as once Beta1 is released,
Beta2 aggregate job should point to this savara hudson job. So for now either Beta2 should
not include Savara, or it could point to trunk, but then potentially new feature work in
savara trunk may briefly end up in Beta2 build, before Beta2 is switched to the
savara-1.1.x job.
Don't know if this is much of an issue for a week?
After Beta1 is out, not sure what should happen with the savara hudson job? Currently I
have removed the link to the aggregate project, and commented out the publish, as because
it references the jbosstools trunk, it means that it would publish the Savara trunk
artifacts to the Beta2 publish site - which would not be correct (as Savara trunk will be
for new development).
The only other way would be to create tags for beta1 and beta2, and separate hudson jobs,
but this would be overkill as there is unlikely to be any changes over the following week
until beta1 is released. So possibly best to leave Savara hudson job detached for now, and
then when JBT3.3.x builds start, then aggregate it again.
(will see about pi4soa next)
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: Gary Brown
Fix For: 3.2.0.Beta1
Attachments: Screenshot-JBDS4M2-with-teiid-and-savara-installed-from-trunk.png
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
4:55 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6927) Integrate Savara plugins into JBoss Tools
[
https://jira.jboss.org/browse/JBIDE-6927?page=com.atlassian.jira.plugin.s...
]
Gary Brown commented on JBIDE-6927:
-----------------------------------
Based on email discussion with Max, could you move pi4soa core feature to SOA category
(instead of All), and not list the Scribble Protocol feature. I assume this can be done,
but still have the feature bundled?
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: Gary Brown
Fix For: 3.2.0.Beta1
Attachments: Screenshot-JBDS4M2-with-teiid-and-savara-installed-from-trunk.png
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
5:02 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6927) Integrate Savara plugins into JBoss Tools
[
https://jira.jboss.org/browse/JBIDE-6927?page=com.atlassian.jira.plugin.s...
]
Gary Brown commented on JBIDE-6927:
-----------------------------------
Create new pi4soa job: http://hudson.qa.jboss.com/hudson/view/SAVARA/job/pi4soa-3.1.x/
(renamed from jbosstools-pi4soa to pi4soa and defined under the Savara group - hope that
is ok, if not rename/move as appropriate)
Same issues apply as above. Once resolved for savara jobs, I will apply the same
resolution for the jbosstools-pi4soa job - but currently I will leave it publishing to the
3.2.0.Beta1 location.
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: Gary Brown
Fix For: 3.2.0.Beta1
Attachments: Screenshot-JBDS4M2-with-teiid-and-savara-installed-from-trunk.png
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
11:12 p.m.
New subject: [JBoss JIRA] Updated: (JBIDE-6927) Integrate Savara plugins into JBoss Tools
[
https://jira.jboss.org/browse/JBIDE-6927?page=com.atlassian.jira.plugin.s...
]
Nick Boldt updated JBIDE-6927:
------------------------------
Attachment: Screenshot-3.png
Screenshot-2.png
OK, you can have a hidden feature (not in a category) but it still shows up in the
uncategorized list (Screenshot-3.png).
However, even when hidden, it's resolved as a dependency when I ask to install just
the Savara feature (Screenshot-2.png), so we're set here. I'll port this change
into Beta1 branch.
--
One thing I should mention, finally, is that your features contain the word
"Feature", where most others do not. For consistency, should this suffix be
removed?
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: Gary Brown
Fix For: 3.2.0.Beta1
Attachments: Screenshot-2.png, Screenshot-3.png,
Screenshot-JBDS4M2-with-teiid-and-savara-installed-from-trunk.png
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
11:15 p.m.
New subject: [JBoss JIRA] Updated: (JBIDE-6927) Integrate Savara plugins into JBoss Tools
[
https://jira.jboss.org/browse/JBIDE-6927?page=com.atlassian.jira.plugin.s...
]
Nick Boldt updated JBIDE-6927:
------------------------------
Attachment: Screenshot-4.png
Did you want the Savara feature in both ALL and SOA categories (Screenshot-4.png)?
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: Gary Brown
Fix For: 3.2.0.Beta1
Attachments: Screenshot-2.png, Screenshot-3.png, Screenshot-4.png,
Screenshot-JBDS4M2-with-teiid-and-savara-installed-from-trunk.png
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
3:39 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6927) Integrate Savara plugins into JBoss Tools
[
https://jira.jboss.org/browse/JBIDE-6927?page=com.atlassian.jira.plugin.s...
]
Gary Brown commented on JBIDE-6927:
-----------------------------------
No I think from Max's description, it should not be in the All category.
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: Gary Brown
Fix For: 3.2.0.Beta1
Attachments: Screenshot-2.png, Screenshot-3.png, Screenshot-4.png,
Screenshot-JBDS4M2-with-teiid-and-savara-installed-from-trunk.png
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
10:50 a.m.
New subject: [JBoss JIRA] Resolved: (JBIDE-6927) Integrate Savara plugins into JBoss Tools
[
https://jira.jboss.org/browse/JBIDE-6927?page=com.atlassian.jira.plugin.s...
]
Nick Boldt resolved JBIDE-6927.
-------------------------------
Resolution: Done
OK, done. Savara is now only in the SOATools category
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.Beta1
Attachments: Screenshot-2.png, Screenshot-3.png, Screenshot-4.png,
Screenshot-JBDS4M2-with-teiid-and-savara-installed-from-trunk.png
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
5674
days inactive
5705
days old
jbosstools-issues@lists.jboss.org
19 comments
3 participants
participants (3)
-
Brian Fitzpatrick (JIRA) -
Gary Brown (JIRA)
-
Nick Boldt (JIRA)