[JBoss JIRA] (JBIDE-13232) refactor target platforms' GAVs, names, labels (was target platforms has the same name)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13232?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-13232:
------------------------------------
Discussion in build.next etherpad [1] on Wednesday decided on this new publishing scheme for target platforms:
[1] http://ether-man.rhcloud.com/p/build.next
{quote}
http://download.jboss.org/jbosstools/updates/kepler -> points at latest TP
http://download.jboss.org/jbosstools/updates/kepler/integrationstack -> points at IS' latest TP
For GAV, path becomes - http://download.jboss.org/jbosstools/targetplatforms/A/V:
{code}
jbosstoolstarget-4.20.5 -> http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.2... (previously would be SR0d)
http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.2... (previously would be SR1b)
http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.2... (coming in Feb/March)
http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.3... (M4)
http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.3... (M5)
http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.3... (M6)
http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.3... (M7/RC1)
http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.3... (R)
{code}
Under each versioned folder, we'd then find:
{code}
jbosstoolstarget-4.30.0.Alpha1.zip
REPO/
composite*.xml
{code}
Similarly, Intergration Stack could have:
http://download.jboss.org/jbosstools/targetplatform/integrationstack/1.x....
And under that,
{code}
integrationstack-1.x.foo.whatever.Final.zip
REPO/
composite*.xml
{code}
{quote}
---
New jobs from mistria:
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/Targ...
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/Targ...
---
New, simpler publish script [0] for use with new jbosstools-target-platforms repo [1]:
[0] https://raw.github.com/nickboldt/jbosstools-target-platforms/master/publi...
[1]
New job [2] passes projectname and version to the publish.sh script from JOB_NAME to make things maintenance-free... just need to update the job name and it'll publish to a new location:
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/devstudiotargetplatf...
> refactor target platforms' GAVs, names, labels (was target platforms has the same name)
> ---------------------------------------------------------------------------------------
>
> Key: JBIDE-13232
> URL: https://issues.jboss.org/browse/JBIDE-13232
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Build/Releng
> Affects Versions: 4.1.0.Alpha1
> Environment:
> Reporter: Max Rydahl Andersen
> Assignee: Mickael Istria
> Fix For: 4.1.0.Alpha1
>
>
> .target files are all called "e42-wtp34-jbds6" even though they are for jbosstools and not specific to jbds6 either.
> Makes it hard to actually see which target platform to choose
--
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, 3 months
[JBoss JIRA] (JBIDE-13381) ESB Editor removes "http-client-property" property (JBDS-2446)
by Brian Fitzpatrick (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13381?page=com.atlassian.jira.plugi... ]
Brian Fitzpatrick commented on JBIDE-13381:
-------------------------------------------
Yup. Will do. Am waiting to hear from Len to see what the plan is, but will be happy to. Thanks for updating those github pull requests. All looks green now. :)
> ESB Editor removes "http-client-property" property (JBDS-2446)
> --------------------------------------------------------------
>
> Key: JBIDE-13381
> URL: https://issues.jboss.org/browse/JBIDE-13381
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: esb
> Affects Versions: 3.3.0.Final-SOA
> Reporter: Brian Fitzpatrick
> Assignee: Viacheslav Kabanovich
> Priority: Critical
> Fix For: 3.3.x, 4.0.x
>
> Attachments: jbide-13381.patch
>
>
> When editing an ESB file (jboss-esb.xml), we have two ways which are using the native XML editor or the visual way.
> When we want to use the property X. We created our service and our SOAPClient using the visual editor, then we have to add the "http-client-property" manually
> <?xml version="1.0"?>
> <jbossesb parameterReloadSecs="5"
> xmlns="http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml..."
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml... http://anonsvn.jboss.org/repos/labs/labs/jbossesb/trunk/product/etc/schem...">
> <services>
> <service category="c1" description="d1" name="s1">
> <actions>
> <action class="org.jboss.soa.esb.actions.soap.SOAPClient" name="client">
> <property name="wsdl" value="someWsdl"/>
> <property name="SOAPAction" value="noAction"/>
> <property name="endpointUrl" value="http://host/servername">
> <http-client-property name="file" value="httpclient.properties" />
> </property>
> </action>
> </actions>
> </service>
> </services>
> </jbossesb>
> Notice the "http-client-property" in the action property element. The problem is that when using visual editor of this file and adding something new or editing existing thing, the code related to this property is deleted. In the example above, I have the following result, showing what the editor removed: (in this case I just changed the service name from service-test to service-test-edited)
> <?xml version="1.0"?>
> <jbossesb parameterReloadSecs="5"
> xmlns="http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml..."
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml... http://anonsvn.jboss.org/repos/labs/labs/jbossesb/trunk/product/etc/schem...">
> <services>
> <service category="c1" description="d1" name="s1-edited">
> <actions>
> <action class="org.jboss.soa.esb.actions.soap.SOAPClient" name="client">
> <property name="wsdl" value="someWsdl"/>
> <property name="SOAPAction" value="noAction"/>
> <property name="endpointUrl" value="http://host/servername"/>
> </action>
> </actions>
> </service>
> </services>
> </jbossesb>
> One test we have done is change the XSD used by the JBDS(1.3.1 to the one used in quickstars (1.0.1). The http-client-property worked fine, but other things stopped working. So we need to know what's wrong with the schema and what should make it works fine.
--
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, 3 months
[JBoss JIRA] (JBIDE-13381) ESB Editor removes "http-client-property" property (JBDS-2446)
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13381?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-13381:
-----------------------------------------------
Brian, can you apply jbide-13381.patch to 3.3.x in SVN?
> ESB Editor removes "http-client-property" property (JBDS-2446)
> --------------------------------------------------------------
>
> Key: JBIDE-13381
> URL: https://issues.jboss.org/browse/JBIDE-13381
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: esb
> Affects Versions: 3.3.0.Final-SOA
> Reporter: Brian Fitzpatrick
> Assignee: Viacheslav Kabanovich
> Priority: Critical
> Fix For: 3.3.x, 4.0.x
>
> Attachments: jbide-13381.patch
>
>
> When editing an ESB file (jboss-esb.xml), we have two ways which are using the native XML editor or the visual way.
> When we want to use the property X. We created our service and our SOAPClient using the visual editor, then we have to add the "http-client-property" manually
> <?xml version="1.0"?>
> <jbossesb parameterReloadSecs="5"
> xmlns="http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml..."
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml... http://anonsvn.jboss.org/repos/labs/labs/jbossesb/trunk/product/etc/schem...">
> <services>
> <service category="c1" description="d1" name="s1">
> <actions>
> <action class="org.jboss.soa.esb.actions.soap.SOAPClient" name="client">
> <property name="wsdl" value="someWsdl"/>
> <property name="SOAPAction" value="noAction"/>
> <property name="endpointUrl" value="http://host/servername">
> <http-client-property name="file" value="httpclient.properties" />
> </property>
> </action>
> </actions>
> </service>
> </services>
> </jbossesb>
> Notice the "http-client-property" in the action property element. The problem is that when using visual editor of this file and adding something new or editing existing thing, the code related to this property is deleted. In the example above, I have the following result, showing what the editor removed: (in this case I just changed the service name from service-test to service-test-edited)
> <?xml version="1.0"?>
> <jbossesb parameterReloadSecs="5"
> xmlns="http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml..."
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml... http://anonsvn.jboss.org/repos/labs/labs/jbossesb/trunk/product/etc/schem...">
> <services>
> <service category="c1" description="d1" name="s1-edited">
> <actions>
> <action class="org.jboss.soa.esb.actions.soap.SOAPClient" name="client">
> <property name="wsdl" value="someWsdl"/>
> <property name="SOAPAction" value="noAction"/>
> <property name="endpointUrl" value="http://host/servername"/>
> </action>
> </actions>
> </service>
> </services>
> </jbossesb>
> One test we have done is change the XSD used by the JBDS(1.3.1 to the one used in quickstars (1.0.1). The http-client-property worked fine, but other things stopped working. So we need to know what's wrong with the schema and what should make it works fine.
--
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, 3 months