[JBoss JIRA] (JBTIS-158) create composite site zip containing JBDS IS + dependencies for easier offline install
by Rob Cernich (JIRA)
[ https://issues.jboss.org/browse/JBTIS-158?page=com.atlassian.jira.plugin.... ]
Rob Cernich commented on JBTIS-158:
-----------------------------------
For JBTIS, we should have a single site, which includes all the IS features and makes reference to the JBT core site and the JBTIS TP (i.e. the JBTIS site is built with two associate sites). This is easy peasy and works today. The structure on jboss.org would be the same as what it has been, where the .../integration-stack URL is a composite site that contains references to each JBTIS version (e.g. ./aggregate/4.1.0, ./aggregate/4.1.1, ./aggregate/4.1.2, etc.).
> create composite site zip containing JBDS IS + dependencies for easier offline install
> --------------------------------------------------------------------------------------
>
> Key: JBTIS-158
> URL: https://issues.jboss.org/browse/JBTIS-158
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: distribution
> Affects Versions: 4.1.0.Beta1
> Reporter: Nick Boldt
> Assignee: Rob Cernich
>
> Suggested by [~rcernich]:
> {quote}For the JBDS-IS site, I was recommending creating a project that would zip the JBDS-IS and JBDS-IS TP sites into a composite site. The zip contents would look something like:
> {code}./compositeContent.xml
> ./compositeArtifacts.xml
> ./7.1.0/7.1.0.Beta1-jbds-is/
> ./7.1.0/7.1.0.Beta1-jbds-is-target-platform/{code}
> {quote}
> This will work if we assume users have already installed JBDS. If we cannot make that assumption, then the composite zip must also include the JBDS update site + JBDS TP site.
> If we did a similar thing for JBT IS, it would need to contain these sites:
> {code}
> JBT webtools aggregate site (not the full JBT aggregate site)
> JBT TP
> JBT IS
> JBT IS TP
> {code}
> Or, if we assume that users will already have JBT (or some part of it) installed, then we need only:
> {code}
> JBT IS
> JBT IS TP
> {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
12 years, 7 months
[JBoss JIRA] (JBTIS-158) create composite site zip containing JBDS IS + dependencies for easier offline install
by Rob Cernich (JIRA)
[ https://issues.jboss.org/browse/JBTIS-158?page=com.atlassian.jira.plugin.... ]
Rob Cernich commented on JBTIS-158:
-----------------------------------
I think this approach should only apply to JBDS-IS.
For JBTIS, I think it is important to include the JBT core in the list of referenced sites so that users have the ability to install just what they need. For example, if a user wants to work with SwitchYard, they can go right to JBTIS and install SwitchYard, without first having to install JBT. I think this is a legitimate use case for community.
Personally, I don't see any problem with the way the JBTIS site is setup, where it is a single site with two referenced sites: JBT core and JBTIS TP. This is simple and requires no hoop jumping.
> create composite site zip containing JBDS IS + dependencies for easier offline install
> --------------------------------------------------------------------------------------
>
> Key: JBTIS-158
> URL: https://issues.jboss.org/browse/JBTIS-158
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: distribution
> Affects Versions: 4.1.0.Beta1
> Reporter: Nick Boldt
> Assignee: Rob Cernich
>
> Suggested by [~rcernich]:
> {quote}For the JBDS-IS site, I was recommending creating a project that would zip the JBDS-IS and JBDS-IS TP sites into a composite site. The zip contents would look something like:
> {code}./compositeContent.xml
> ./compositeArtifacts.xml
> ./7.1.0/7.1.0.Beta1-jbds-is/
> ./7.1.0/7.1.0.Beta1-jbds-is-target-platform/{code}
> {quote}
> This will work if we assume users have already installed JBDS. If we cannot make that assumption, then the composite zip must also include the JBDS update site + JBDS TP site.
> If we did a similar thing for JBT IS, it would need to contain these sites:
> {code}
> JBT webtools aggregate site (not the full JBT aggregate site)
> JBT TP
> JBT IS
> JBT IS TP
> {code}
> Or, if we assume that users will already have JBT (or some part of it) installed, then we need only:
> {code}
> JBT IS
> JBT IS TP
> {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
12 years, 7 months
[JBoss JIRA] (JBTIS-158) create composite site zip containing JBDS IS + dependencies for easier offline install
by Nick Boldt (JIRA)
Nick Boldt created JBTIS-158:
--------------------------------
Summary: create composite site zip containing JBDS IS + dependencies for easier offline install
Key: JBTIS-158
URL: https://issues.jboss.org/browse/JBTIS-158
Project: JBoss Tools Integration Stack
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: distribution
Affects Versions: 4.1.0.Beta1
Reporter: Nick Boldt
Assignee: Rob Cernich
Suggested by [~rcernich]:
{quote}For the JBDS-IS site, I was recommending creating a project that would zip the JBDS-IS and JBDS-IS TP sites into a composite site. The zip contents would look something like:
{code}./compositeContent.xml
./compositeArtifacts.xml
./7.1.0/7.1.0.Beta1-jbds-is/
./7.1.0/7.1.0.Beta1-jbds-is-target-platform/{code}
{quote}
This will work if we assume users have already installed JBDS. If we cannot make that assumption, then the composite zip must also include the JBDS update site + JBDS TP site.
If we did a similar thing for JBT IS, it would need to contain these sites:
{code}
JBT webtools aggregate site (not the full JBT aggregate site)
JBT TP
JBT IS
JBT IS TP
{code}
Or, if we assume that users will already have JBT (or some part of it) installed, then we need only:
{code}
JBT IS
JBT IS TP
{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
12 years, 7 months
[JBoss JIRA] (JBDS-2735) Ensure the Forge 1 wizards work well
by Vineet Reynolds (JIRA)
[ https://issues.jboss.org/browse/JBDS-2735?page=com.atlassian.jira.plugin.... ]
Vineet Reynolds commented on JBDS-2735:
---------------------------------------
[~burrsutter], from a theoretical perspective, there is one problem I foresee. The generated AngularJS ngResource factories for the server-side JAXRS resources contain relative URLs i.e. they're not Cordova friendly. We'll need to find some scheme to have the user convert them into absolute ones. Or for that matter, we'll have to construct absolute or relative URLs based on the environment (like in TicketMonster).
I'll need to look at the behavior of the generated project in depth to see if there are other problematic areas, but I'm confident that they wont be as critical as the one described above.
> Ensure the Forge 1 wizards work well
> ------------------------------------
>
> Key: JBDS-2735
> URL: https://issues.jboss.org/browse/JBDS-2735
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Burr Sutter
>
--
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
12 years, 7 months
[JBoss JIRA] (JBDS-2735) Ensure the Forge 1 wizards work well
by Burr Sutter (JIRA)
[ https://issues.jboss.org/browse/JBDS-2735?page=com.atlassian.jira.plugin.... ]
Burr Sutter commented on JBDS-2735:
-----------------------------------
[~maxandersen]I need to see the "before" and "after" of an AngularJS project targeting old school web vs Cordova-oriented web. My guess is that the HTML, CSS and JS code is virtually identical. The one difference that I am aware of is that the Cordova project is client-side only - therefore the REST endpoints need to live in a Java EE 6 .war. Therefore the URL that the Cordova client code points too will be different.
[~vineet.reynolds]Is the AngularJS code generated by the Forge 1 scaffold compatible with Cordova? Or will it require significant end-user modification before being pulled into our Cordova project? (Gorkem's tool).
> Ensure the Forge 1 wizards work well
> ------------------------------------
>
> Key: JBDS-2735
> URL: https://issues.jboss.org/browse/JBDS-2735
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Burr Sutter
>
--
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
12 years, 7 months
[JBoss JIRA] (JBTIS-149) update BPEL in JBTIS 4.1.2 to include latest Eclipse BPEL 1.0.3
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBTIS-149?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBTIS-149 at 8/26/13 12:19 PM:
------------------------------------------------------------
Nick Boldt <nboldt(a)redhat.com> made a comment on [bug 996874|https://bugzilla.redhat.com/show_bug.cgi?id=996874]
The important part in your log is this, which shows you DID in fact install the newer version of Eclipse BPEL 1.0.3:
{code}
org.jboss.tools.bpel.feature (1.2.100.Final-v20130821-0236-B1019) "BPEL Editor"
org.eclipse.bpel.apache.ode.deploy.model (1.0.3.v20130816-0911-H221-CI) "EMF Model for ODE Deployment Descriptor" [Starting]
org.eclipse.bpel.apache.ode.deploy.ui (1.0.3.v20130816-0911-H221-CI) "UI for ODE Deployment Descriptor" [Starting]
org.eclipse.bpel.apache.ode.runtime (1.0.3.v20130816-0911-H221-CI) "Apache ODE Runtime Adapter" [Starting]
org.eclipse.bpel.common.model (1.0.3.v20130816-0911-H221-CI) "BPEL Common Model" [Active]
org.eclipse.bpel.common.ui (1.0.3.v20130816-0911-H221-CI) "BPEL Common UI" [Active]
org.eclipse.bpel.common.wsdl (1.0.3.v20130816-0911-H221-CI) "SOA Commons for WSDL and XML Schemas" [Starting]
org.eclipse.bpel.help (1.0.3.v20130816-0911-H221-CI) "BPEL Help" [Starting]
org.eclipse.bpel.cheatsheet (1.0.3.v20130816-0911-H221-CI) "BPEL Cheatsheet" [Starting]
org.eclipse.bpel.model (1.0.3.v20130816-0911-H221-CI) "BPEL Model" [Active]
org.eclipse.bpel.runtimes (1.0.3.v20130816-0911-H221-CI) "Eclipse BPEL Designer Runtimes" [Active]
org.eclipse.bpel.ui (1.0.3.v20130816-0911-H221-CI) "BPEL Editor" [Active]
org.eclipse.bpel.validator (1.0.3.v20130816-0911-H221-CI) "BPEL Validator Plug-in" [Active]
org.eclipse.bpel.wsil.model (1.0.3.v20130816-0911-H221-CI) "WSIL Model" [Active]
org.eclipse.bpel.xpath10 (1.0.3.v20130816-0911-H221-CI) "XPath Parser 1.0" [Resolved]
{code}
So... if the fix from [~bbrodt] didn't fix the problem, we need to get another fix into http://download.eclipse.org/bpel/site/1.0.3 and go through this song-and-dance again. :(
[~bbrodt], can you verify?
was (Author: jira-bugzilla-migration):
Nick Boldt <nboldt(a)redhat.com> made a comment on [bug 996874|https://bugzilla.redhat.com/show_bug.cgi?id=996874]
The important part in your log is this, which shows you DID in fact install the newer version of Eclipse BPEL 1.0.3:
org.jboss.tools.bpel.feature (1.2.100.Final-v20130821-0236-B1019) "BPEL Editor"
org.eclipse.bpel.apache.ode.deploy.model (1.0.3.v20130816-0911-H221-CI) "EMF Model for ODE Deployment Descriptor" [Starting]
org.eclipse.bpel.apache.ode.deploy.ui (1.0.3.v20130816-0911-H221-CI) "UI for ODE Deployment Descriptor" [Starting]
org.eclipse.bpel.apache.ode.runtime (1.0.3.v20130816-0911-H221-CI) "Apache ODE Runtime Adapter" [Starting]
org.eclipse.bpel.common.model (1.0.3.v20130816-0911-H221-CI) "BPEL Common Model" [Active]
org.eclipse.bpel.common.ui (1.0.3.v20130816-0911-H221-CI) "BPEL Common UI" [Active]
org.eclipse.bpel.common.wsdl (1.0.3.v20130816-0911-H221-CI) "SOA Commons for WSDL and XML Schemas" [Starting]
org.eclipse.bpel.help (1.0.3.v20130816-0911-H221-CI) "BPEL Help" [Starting]
org.eclipse.bpel.cheatsheet (1.0.3.v20130816-0911-H221-CI) "BPEL Cheatsheet" [Starting]
org.eclipse.bpel.model (1.0.3.v20130816-0911-H221-CI) "BPEL Model" [Active]
org.eclipse.bpel.runtimes (1.0.3.v20130816-0911-H221-CI) "Eclipse BPEL Designer Runtimes" [Active]
org.eclipse.bpel.ui (1.0.3.v20130816-0911-H221-CI) "BPEL Editor" [Active]
org.eclipse.bpel.validator (1.0.3.v20130816-0911-H221-CI) "BPEL Validator Plug-in" [Active]
org.eclipse.bpel.wsil.model (1.0.3.v20130816-0911-H221-CI) "WSIL Model" [Active]
org.eclipse.bpel.xpath10 (1.0.3.v20130816-0911-H221-CI) "XPath Parser 1.0" [Resolved]
So... if the fix from @Bob Brodt didn't fix the problem, we need to get another fix into http://download.eclipse.org/bpel/site/1.0.3 and go through this song-and-dance again. :(
@Bob, can you verify?
> update BPEL in JBTIS 4.1.2 to include latest Eclipse BPEL 1.0.3
> ---------------------------------------------------------------
>
> Key: JBTIS-149
> URL: https://issues.jboss.org/browse/JBTIS-149
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: BPEL, distribution
> Affects Versions: 4.1.0.Beta1
> Reporter: Nick Boldt
> Assignee: Robert (Bob) Brodt
> Fix For: 4.1.2
>
>
> New content: http://download.eclipse.org/bpel/site/1.0.3 - version 1.0.3.v20130816-0911-H221-CI
> Reason: https://bugzilla.redhat.com/show_bug.cgi?id=996874
--
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
12 years, 7 months
[JBoss JIRA] (JBTIS-149) update BPEL in JBTIS 4.1.2 to include latest Eclipse BPEL 1.0.3
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/JBTIS-149?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on JBTIS-149:
-----------------------------------------------
Nick Boldt <nboldt(a)redhat.com> made a comment on [bug 996874|https://bugzilla.redhat.com/show_bug.cgi?id=996874]
The important part in your log is this, which shows you DID in fact install the newer version of Eclipse BPEL 1.0.3:
org.jboss.tools.bpel.feature (1.2.100.Final-v20130821-0236-B1019) "BPEL Editor"
org.eclipse.bpel.apache.ode.deploy.model (1.0.3.v20130816-0911-H221-CI) "EMF Model for ODE Deployment Descriptor" [Starting]
org.eclipse.bpel.apache.ode.deploy.ui (1.0.3.v20130816-0911-H221-CI) "UI for ODE Deployment Descriptor" [Starting]
org.eclipse.bpel.apache.ode.runtime (1.0.3.v20130816-0911-H221-CI) "Apache ODE Runtime Adapter" [Starting]
org.eclipse.bpel.common.model (1.0.3.v20130816-0911-H221-CI) "BPEL Common Model" [Active]
org.eclipse.bpel.common.ui (1.0.3.v20130816-0911-H221-CI) "BPEL Common UI" [Active]
org.eclipse.bpel.common.wsdl (1.0.3.v20130816-0911-H221-CI) "SOA Commons for WSDL and XML Schemas" [Starting]
org.eclipse.bpel.help (1.0.3.v20130816-0911-H221-CI) "BPEL Help" [Starting]
org.eclipse.bpel.cheatsheet (1.0.3.v20130816-0911-H221-CI) "BPEL Cheatsheet" [Starting]
org.eclipse.bpel.model (1.0.3.v20130816-0911-H221-CI) "BPEL Model" [Active]
org.eclipse.bpel.runtimes (1.0.3.v20130816-0911-H221-CI) "Eclipse BPEL Designer Runtimes" [Active]
org.eclipse.bpel.ui (1.0.3.v20130816-0911-H221-CI) "BPEL Editor" [Active]
org.eclipse.bpel.validator (1.0.3.v20130816-0911-H221-CI) "BPEL Validator Plug-in" [Active]
org.eclipse.bpel.wsil.model (1.0.3.v20130816-0911-H221-CI) "WSIL Model" [Active]
org.eclipse.bpel.xpath10 (1.0.3.v20130816-0911-H221-CI) "XPath Parser 1.0" [Resolved]
So... if the fix from @Bob Brodt didn't fix the problem, we need to get another fix into http://download.eclipse.org/bpel/site/1.0.3 and go through this song-and-dance again. :(
@Bob, can you verify?
> update BPEL in JBTIS 4.1.2 to include latest Eclipse BPEL 1.0.3
> ---------------------------------------------------------------
>
> Key: JBTIS-149
> URL: https://issues.jboss.org/browse/JBTIS-149
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: BPEL, distribution
> Affects Versions: 4.1.0.Beta1
> Reporter: Nick Boldt
> Assignee: Robert (Bob) Brodt
> Fix For: 4.1.2
>
>
> New content: http://download.eclipse.org/bpel/site/1.0.3 - version 1.0.3.v20130816-0911-H221-CI
> Reason: https://bugzilla.redhat.com/show_bug.cgi?id=996874
--
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
12 years, 7 months
[JBoss JIRA] (JBDS-2734) Forge 2 in JBDS
by Lincoln Baxter III (JIRA)
[ https://issues.jboss.org/browse/JBDS-2734?page=com.atlassian.jira.plugin.... ]
Lincoln Baxter III commented on JBDS-2734:
------------------------------------------
To address the question of whether or not we can deliver SwitchYard functionality in Forge 2 - We've spent the last 3 days with the SwitchYard team, porting the Forge1 SwitchYard plugin over to Forge2. It works fine, we just don't have a UI on it yet because we didn't want to consume too much of the SY team's time. Putting a UI on it is a relatively trivial task, as the core addon behavior is already unit and integration tested. (We needed this for the Windup integration, which is why we didn't need a UI right away.) I estimate putting a UI on this to run in JBDS/Forge would take another 8 hours max.
> Forge 2 in JBDS
> ---------------
>
> Key: JBDS-2734
> URL: https://issues.jboss.org/browse/JBDS-2734
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Burr Sutter
>
> Is Forge 2 ready to be included in JBDS ?
--
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
12 years, 7 months
[JBoss JIRA] (JBDS-2734) Forge 2 in JBDS
by Lincoln Baxter III (JIRA)
[ https://issues.jboss.org/browse/JBDS-2734?page=com.atlassian.jira.plugin.... ]
Lincoln Baxter III commented on JBDS-2734:
------------------------------------------
Well... I was under the impression that you didn't want to remove Forge 1 from JBDS because we wouldn't be delivering exactly the same solution/commands/etc. But if that's the direction you want to go we could use the original CTRL-4 instead of CTRL-5.
I would love to go 100% to Forge 2 in November, but I don't want anyone be under the impression that things will work the same way or be backwards compatible.
> Forge 2 in JBDS
> ---------------
>
> Key: JBDS-2734
> URL: https://issues.jboss.org/browse/JBDS-2734
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Burr Sutter
>
> Is Forge 2 ready to be included in JBDS ?
--
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
12 years, 7 months