[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:
-----------------------------------
If the TP features are showing up as available to install, the solution is simple, remove the child entry for the TP and add an associateSite entry to the site, which would be a relative path (e.g. ../7.1.0.Beta1-jbds-is-tp). This will still produce a transportable site that can be located anywhere.
> 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] (JBIDE-15375) File permissions for OpenShift actions hooks are sometimes incorrect when cloning repo
by Andy Goldstein (JIRA)
Andy Goldstein created JBIDE-15375:
--------------------------------------
Summary: File permissions for OpenShift actions hooks are sometimes incorrect when cloning repo
Key: JBIDE-15375
URL: https://issues.jboss.org/browse/JBIDE-15375
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Environment: Windows
Reporter: Andy Goldstein
(filing on behalf of another user who is having login issues)
When I clone a git repo (git@...:user/myapp.git) using the Eclipse plugins, the file permissions for my action_hooks are set as:
/cygdrive/c/Users/user/git/myapp/.openshift/action_hooks
$ ls -l
total 45
-rwx------+ 1 Administrators Domain Users 265 Aug 22 14:38 build
-rwx------+ 1 Administrators Domain Users 264 Aug 22 14:38 deploy
-rwx------+ 1 Administrators Domain Users 186 Aug 22 14:38 post_deploy
-rwx------+ 1 Administrators Domain Users 645 Aug 22 14:38 post_start_jbossas-7
-rwx------+ 1 Administrators Domain Users 645 Aug 22 14:38 post_stop_jbossas-7
-rwx------+ 1 Administrators Domain Users 640 Aug 22 14:38 pre_build
-rwx------+ 1 Administrators Domain Users 272 Aug 22 14:38 pre_build_jbossas-7
-rwx------+ 1 Administrators Domain Users 645 Aug 22 14:38 pre_start_jbossas-7
-rwx------+ 1 Administrators Domain Users 645 Aug 22 14:38 pre_stop_jbossas-7
When they are pushed to OpenShift, they can't be executed.
On a different machine, when I clone using Eclipse, the file permission are set as expected:
-rwxr-xr-x 1 Administrators Domain Users 270 Aug 22 11:25 build
-rwxr-xr-x 1 Administrators Domain Users 271 Aug 22 11:25 deploy
-rwxr-xr-x 1 Administrators Domain Users 189 Aug 22 11:25 post_deploy
-rwxr-xr-x 1 Administrators Domain Users 659 Aug 22 11:25 post_start_jbossas-7
-rwxr-xr-x 1 Administrators Domain Users 659 Aug 22 11:25 post_stop_jbossas-7
-rwxr-xr-x 1 Administrators Domain Users 650 Aug 22 11:25 pre_build
-rwxr-xr-x 1 Administrators Domain Users 277 Aug 22 11:25 pre_build_jbossas-7
-rwxr-xr-x 1 Administrators Domain Users 659 Aug 22 11:25 pre_start_jbossas-7
-rwxr-xr-x 1 Administrators Domain Users 659 Aug 22 11:25 pre_stop_jbossas-7
Is it possible to set the file perms to +x on the action_hooks?
--
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:
-----------------------------------
The reason I recommend the zip is because it is an artifact that is easy to move around, whether you want to use it specifically for offline installation or not. If you'd rather leave this as a directory, that's fine too. To compare it to a normal site project, it's the same as the site in your project's target directory or the site zip in the target directory, use whichever is better for you.
One other thing, given that these will roll up under something like 7.0/integration-stack/ where there may be many (e.g. 7.1.0, 7.1.1, etc.), it probably makes sense to remove the 7.1.0 directory from the hierarchy, as that is probably where this site would live, otherwise, you'll be modifying the composite files on the servers. So, the server might look something like: (at <integration-stack-root>
./compositeContent.xml (child entries for 7.1.0, 7.1.1, etc.)
./compositeArtifacts.xml (child entries for 7.1.0, 7.1.1, etc.)
./7.1.0 (composite site listed above; i.e. unzip it into the 7.1.0 directory)
Just my two cents. If you'd like, I can modify the project. We need to get something done.
Paul, when you test this site, do you see things like Graphiti? or just the IS bits?
> 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)
[ https://issues.jboss.org/browse/JBTIS-158?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBTIS-158:
----------------------------------
{quote}
If the associate site references to JBT core are the actual matching stable urls and not version specific urls then I don't see much problem.
{quote}
Yes, they are:
https://github.com/jbosstools/jbosstools-integration-stack/blob/master/jb...
FWIW, the same is true for JBT itself, as JBT refers to a specific TP site and therefore it too cannot be tested in isolation (eg., installation against a different TP):
https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregat...
So... we're good (or as good as possible w/o extra install-time complication).
[~maxandersen] Is a zip of JBTIS + JBTIS TP still required, given the new "Thou Shalt Only Use Central" directive?
> 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-2733) Make Cordova tooling and CordovaSim available from software/update tab
by Burr Sutter (JIRA)
[ https://issues.jboss.org/browse/JBDS-2733?page=com.atlassian.jira.plugin.... ]
Burr Sutter commented on JBDS-2733:
-----------------------------------
Linked in JBIDE-14456
In any case, the default Cordova-focused project should allow for its .html, .css and .js files to be editable via the VPE & jQuery Mobile Palette. Granted, the "visual" aspect (Visual/Source and Preview) will likely display a relatively poor representation of any page that leverages JS to component rendering, as jQuery Mobile does. With that said, we can and should expect that a Cordova-focused developer, who uses our Cordova project wizard will then open the index.html in our VPE and leverage our jQuery Mobile Palette for editing it.
> Make Cordova tooling and CordovaSim available from software/update tab
> -----------------------------------------------------------------------
>
> Key: JBDS-2733
> URL: https://issues.jboss.org/browse/JBDS-2733
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Burr Sutter
>
> Cordova should be available from JBDS, but it is not fully supported tech yet thus should be included/marked as a Technology Preview
--
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] (JBIDE-15349) content assist for filenames in html
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15349?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-15349:
---------------------------------------------
you're right about that. nice improvement!
> content assist for filenames in html
> ------------------------------------
>
> Key: JBIDE-15349
> URL: https://issues.jboss.org/browse/JBIDE-15349
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: jsp/jsf/xml/html source editing
> Reporter: Max Rydahl Andersen
> Assignee: Alexey Kazakov
> Labels: new_and_noteworthy
> Fix For: 4.2.0.Alpha1
>
>
> given
> <script type="text/javascript" src="|"></script>
> and app.js, lib/angular.js exists relative to the file being edited.
> then content assist at | should offer app.js and lib/angular.js as options.
> given src="a|" then content assist should at least offer app.js as completion but also nice if lib/angular.js is offered so it user does not need to remember the full path. This "secondary" location should be lower than app.js in priority.
--
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 Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-2735?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBDS-2735:
-------------------------------------------
For me the priority would be that we have scaffolding that can target either "plain" HTML5 or Cordova HTML5.
If that content can be made so it is possible to copy the content between www and webcontent folders that is awesome.
But the requirement of being able to drag'n'drop and expect it to magically work ( we would need to transform users files content ) is for me a sinkhole of work that would have very little benefit and definitely not within scope for a bugfix release.
> 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-2734) Forge 2 in JBDS
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-2734?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBDS-2734:
-------------------------------------------
Yes, we said we would need to keep Forge 1 if that was necessary for compatibility with the things that haven't moved yet; switchyard was just an example and used by upcoming product hence why I was wondering how we could/would handle that.
About Cmd+4 and Cmd+5 ...couldn't we avoid using both and just have one ?
> 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