[JBoss JIRA] (JBIDE-13316) Improve versioning for TP using standard Maven way
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13316?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-13316:
----------------------------------------
> Also not really keen to change stuff that works in the Juno stream. Why wouldn't we refactor/fix/improve this for Kepler, then MAYBE backport changes to 6.0.1/6.0.2 if needed? This issue is targeted for Kepler (4.1.0.Alpha1) but you're making changes that affect the 6.x stream. :confused:
This is for sure something I want to change for Kepler. But our Kepler 6.x stream is currently using the same targets as our Juno stream. jbosstools-build repo is already branch for 5.0.x so making changes in master is not that critical as long as we can build the 5.0.x branch.
> I personally don't like "tp-" as a prefix, as it's vague. Why not "target-" or "target-platform-"
Ok with "target-platforms-".
--
The issue is that we actively maintain 2 streams of Target Platforms. Those streams are fully independent one from the other, and independent from parent. So it's not very clear why some versions are in master whereas they may not be the one available in parent.
That's why I'm suggesting such a change.
About making local diffs, it would mean that we'd need to rename the target/REPO folder locally to checkout another branch and then compare. I don't think it's that complicated.
> Improve versioning for TP using standard Maven way
> --------------------------------------------------
>
> Key: JBIDE-13316
> URL: https://issues.jboss.org/browse/JBIDE-13316
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: target-platform
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Fix For: 4.1.0.Alpha1
>
>
> Currently, we deal with explicit versions in folder names that make it confusing to understand how target-platforms are versioned.
> Instead, we should use usual Maven way and Git branches: one Git branch for each version of TPs.
--
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, 4 months
[JBoss JIRA] (JBIDE-11858) Empty tooltips in Server View
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-11858?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-11858:
---------------------------------------
I verified the same with JBDS 5.0.2.GA B235. Ports still has an empty tooltip, but that's because of a bug in WTP described in JBIDE-12291 and won't be fixed in 3.3.x.
> Empty tooltips in Server View
> -----------------------------
>
> Key: JBIDE-11858
> URL: https://issues.jboss.org/browse/JBIDE-11858
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JBossAS/Servers
> Affects Versions: 3.3.0.Beta3
> Reporter: Daniel Azarov
> Assignee: Rob Stryker
> Priority: Minor
> Fix For: 3.3.2, 4.0.0.Alpha1
>
> Attachments: ServerViewTooltip1.png, ServerViewTooltip2.png
>
>
> For some nodes (XML Configuration, Ports, Filesets) in Server View, Tooltips are empty
--
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, 4 months
[JBoss JIRA] (JBIDE-12100) AS7 poller is set to as7 management by default while EAP6 is set to web port
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12100?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-12100:
---------------------------------------
Verified the same in JBDS 5.0.2.GA B235
> AS7 poller is set to as7 management by default while EAP6 is set to web port
> ----------------------------------------------------------------------------
>
> Key: JBIDE-12100
> URL: https://issues.jboss.org/browse/JBIDE-12100
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JBossAS/Servers
> Affects Versions: 3.3.0.CR1
> Environment: JBDS 5.0.0.CR1a
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Minor
> Fix For: 3.3.2, 4.0.0.Alpha1
>
>
> Feel free to push this to a future version. But I just found out about this and it seems odd.
> When I add a local AS7 server, it is, by default, set to AS7 management startup poller. But when I create a local EAP6 server, it is set to web poller. Why is that? This applies to both adding manually or using jboss runtime detection plugin.
--
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, 4 months
[JBoss JIRA] (JBIDE-13320) CLONE - Execute permissions modified in merged openshift projects ("use existing") causing action hoooks to not execute
by Stefan Bunciak (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13320?page=com.atlassian.jira.plugi... ]
Stefan Bunciak commented on JBIDE-13320:
----------------------------------------
In the latest build we recieved I can reproduce
{code}
Found 127.9.239.1:8080 listening port
/usr/libexec/openshift/cartridges/abstract/info/lib/util: line 1004: /var/lib/openshift/4c4415c2a7114920be5c2ddfdaaecbbb/app-root/runtime/repo/.openshift/action_hooks/post_start_jbossas-7: Permission denied
Failed to start jbossas-7
{code}
using JBoss Developer Studio
Version: 5.0.2.GA
Build id: v20121213-1624-H235-GA
Build date: 20121213-1624
fix for JBIDE-13217 was not pushed to the 3.3.2 branch i'd guess.
> CLONE - Execute permissions modified in merged openshift projects ("use existing") causing action hoooks to not execute
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-13320
> URL: https://issues.jboss.org/browse/JBIDE-13320
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 3.3.2
> Environment: Linux, Mac (NOT Windows)
> Reporter: Stefan Bunciak
> Assignee: Andre Dietisheim
> Priority: Blocker
> Fix For: 3.3.2
>
> Attachments: hook-premissions-windows.jpg
>
>
> 1. EXEC: Create and import new app
> 2. ASSERT: execute permissions on action_hooks get resetted.
> {code}
> diff --git a/.openshift/action_hooks/build b/.openshift/action_hooks/build
> old mode 100755
> new mode 100644
> diff --git a/.openshift/action_hooks/deploy b/.openshift/action_hooks/deploy
> old mode 100755
> new mode 100644
> diff --git a/.openshift/action_hooks/post_deploy b/.openshift/action_hooks/post_deploy
> old mode 100755
> new mode 100644
> diff --git a/.openshift/action_hooks/post_start_jbosseap-6.0 b/.openshift/action_hooks/post_start_jbosseap-6.0
> old mode 100755
> new mode 100644
> diff --git a/.openshift/action_hooks/post_stop_jbosseap-6.0 b/.openshift/action_hooks/post_stop_jbosseap-6.0
> old mode 100755
> new mode 100644
> diff --git a/.openshift/action_hooks/pre_build b/.openshift/action_hooks/pre_build
> old mode 100755
> new mode 100644
> diff --git a/.openshift/action_hooks/pre_build_jbosseap-6.0 b/.openshift/action_hooks/pre_build_jbosseap-6.0
> old mode 100755
> new mode 100644
> diff --git a/.openshift/action_hooks/pre_start_jbosseap-6.0 b/.openshift/action_hooks/pre_start_jbosseap-6.0
> old mode 100755
> new mode 100644
> diff --git a/.openshift/action_hooks/pre_stop_jbosseap-6.0 b/.openshift/action_hooks/pre_stop_jbosseap-6.0
> old mode 100755
> new mode 100644
> diff --git a/.openshift/cron/weekly/chronograph b/.openshift/cron/weekly/chronograph
> {code}
> 3. EXEC: publish the application to OpenShift
> Result:
> {code}
> /usr/libexec/openshift/cartridges/abstract/info/lib/util: line 992: /var/lib/openshift/1e6a743963104f30bdcdebdff460d42b/app-root/runtime/repo/.openshift/action_hooks/post_start_jbossas-7: Permission denied
> Failed to start jbossas-7
> {code}
> ...but the server is started.
--
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, 4 months
[JBoss JIRA] (JBIDE-13320) CLONE - Execute permissions modified in merged openshift projects ("use existing") causing action hoooks to not execute
by Stefan Bunciak (JIRA)
Stefan Bunciak created JBIDE-13320:
--------------------------------------
Summary: CLONE - Execute permissions modified in merged openshift projects ("use existing") causing action hoooks to not execute
Key: JBIDE-13320
URL: https://issues.jboss.org/browse/JBIDE-13320
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.0.0.CR1
Environment: Linux, Mac (NOT Windows)
Reporter: Stefan Bunciak
Assignee: Andre Dietisheim
Priority: Blocker
Fix For: 4.0.0.CR1
Attachments: hook-premissions-windows.jpg
1. EXEC: Create and import new app
2. ASSERT: execute permissions on action_hooks get resetted.
{code}
diff --git a/.openshift/action_hooks/build b/.openshift/action_hooks/build
old mode 100755
new mode 100644
diff --git a/.openshift/action_hooks/deploy b/.openshift/action_hooks/deploy
old mode 100755
new mode 100644
diff --git a/.openshift/action_hooks/post_deploy b/.openshift/action_hooks/post_deploy
old mode 100755
new mode 100644
diff --git a/.openshift/action_hooks/post_start_jbosseap-6.0 b/.openshift/action_hooks/post_start_jbosseap-6.0
old mode 100755
new mode 100644
diff --git a/.openshift/action_hooks/post_stop_jbosseap-6.0 b/.openshift/action_hooks/post_stop_jbosseap-6.0
old mode 100755
new mode 100644
diff --git a/.openshift/action_hooks/pre_build b/.openshift/action_hooks/pre_build
old mode 100755
new mode 100644
diff --git a/.openshift/action_hooks/pre_build_jbosseap-6.0 b/.openshift/action_hooks/pre_build_jbosseap-6.0
old mode 100755
new mode 100644
diff --git a/.openshift/action_hooks/pre_start_jbosseap-6.0 b/.openshift/action_hooks/pre_start_jbosseap-6.0
old mode 100755
new mode 100644
diff --git a/.openshift/action_hooks/pre_stop_jbosseap-6.0 b/.openshift/action_hooks/pre_stop_jbosseap-6.0
old mode 100755
new mode 100644
diff --git a/.openshift/cron/weekly/chronograph b/.openshift/cron/weekly/chronograph
{code}
3. EXEC: publish the application to OpenShift
Result:
{code}
/usr/libexec/openshift/cartridges/abstract/info/lib/util: line 992: /var/lib/openshift/1e6a743963104f30bdcdebdff460d42b/app-root/runtime/repo/.openshift/action_hooks/post_start_jbossas-7: Permission denied
Failed to start jbossas-7
{code}
...but the server is started.
--
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, 4 months
[JBoss JIRA] (JBIDE-13320) CLONE - Execute permissions modified in merged openshift projects ("use existing") causing action hoooks to not execute
by Stefan Bunciak (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13320?page=com.atlassian.jira.plugi... ]
Stefan Bunciak updated JBIDE-13320:
-----------------------------------
Labels: (was: new_an_noteworthy respin-c)
> CLONE - Execute permissions modified in merged openshift projects ("use existing") causing action hoooks to not execute
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-13320
> URL: https://issues.jboss.org/browse/JBIDE-13320
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.0.0.CR1
> Environment: Linux, Mac (NOT Windows)
> Reporter: Stefan Bunciak
> Assignee: Andre Dietisheim
> Priority: Blocker
> Fix For: 4.0.0.CR1
>
> Attachments: hook-premissions-windows.jpg
>
>
> 1. EXEC: Create and import new app
> 2. ASSERT: execute permissions on action_hooks get resetted.
> {code}
> diff --git a/.openshift/action_hooks/build b/.openshift/action_hooks/build
> old mode 100755
> new mode 100644
> diff --git a/.openshift/action_hooks/deploy b/.openshift/action_hooks/deploy
> old mode 100755
> new mode 100644
> diff --git a/.openshift/action_hooks/post_deploy b/.openshift/action_hooks/post_deploy
> old mode 100755
> new mode 100644
> diff --git a/.openshift/action_hooks/post_start_jbosseap-6.0 b/.openshift/action_hooks/post_start_jbosseap-6.0
> old mode 100755
> new mode 100644
> diff --git a/.openshift/action_hooks/post_stop_jbosseap-6.0 b/.openshift/action_hooks/post_stop_jbosseap-6.0
> old mode 100755
> new mode 100644
> diff --git a/.openshift/action_hooks/pre_build b/.openshift/action_hooks/pre_build
> old mode 100755
> new mode 100644
> diff --git a/.openshift/action_hooks/pre_build_jbosseap-6.0 b/.openshift/action_hooks/pre_build_jbosseap-6.0
> old mode 100755
> new mode 100644
> diff --git a/.openshift/action_hooks/pre_start_jbosseap-6.0 b/.openshift/action_hooks/pre_start_jbosseap-6.0
> old mode 100755
> new mode 100644
> diff --git a/.openshift/action_hooks/pre_stop_jbosseap-6.0 b/.openshift/action_hooks/pre_stop_jbosseap-6.0
> old mode 100755
> new mode 100644
> diff --git a/.openshift/cron/weekly/chronograph b/.openshift/cron/weekly/chronograph
> {code}
> 3. EXEC: publish the application to OpenShift
> Result:
> {code}
> /usr/libexec/openshift/cartridges/abstract/info/lib/util: line 992: /var/lib/openshift/1e6a743963104f30bdcdebdff460d42b/app-root/runtime/repo/.openshift/action_hooks/post_start_jbossas-7: Permission denied
> Failed to start jbossas-7
> {code}
> ...but the server is started.
--
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, 4 months
[JBoss JIRA] (JBIDE-13320) CLONE - Execute permissions modified in merged openshift projects ("use existing") causing action hoooks to not execute
by Stefan Bunciak (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13320?page=com.atlassian.jira.plugi... ]
Stefan Bunciak updated JBIDE-13320:
-----------------------------------
Affects Version/s: 3.3.2
(was: 4.0.0.CR1)
> CLONE - Execute permissions modified in merged openshift projects ("use existing") causing action hoooks to not execute
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-13320
> URL: https://issues.jboss.org/browse/JBIDE-13320
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 3.3.2
> Environment: Linux, Mac (NOT Windows)
> Reporter: Stefan Bunciak
> Assignee: Andre Dietisheim
> Priority: Blocker
> Fix For: 4.0.0.CR1
>
> Attachments: hook-premissions-windows.jpg
>
>
> 1. EXEC: Create and import new app
> 2. ASSERT: execute permissions on action_hooks get resetted.
> {code}
> diff --git a/.openshift/action_hooks/build b/.openshift/action_hooks/build
> old mode 100755
> new mode 100644
> diff --git a/.openshift/action_hooks/deploy b/.openshift/action_hooks/deploy
> old mode 100755
> new mode 100644
> diff --git a/.openshift/action_hooks/post_deploy b/.openshift/action_hooks/post_deploy
> old mode 100755
> new mode 100644
> diff --git a/.openshift/action_hooks/post_start_jbosseap-6.0 b/.openshift/action_hooks/post_start_jbosseap-6.0
> old mode 100755
> new mode 100644
> diff --git a/.openshift/action_hooks/post_stop_jbosseap-6.0 b/.openshift/action_hooks/post_stop_jbosseap-6.0
> old mode 100755
> new mode 100644
> diff --git a/.openshift/action_hooks/pre_build b/.openshift/action_hooks/pre_build
> old mode 100755
> new mode 100644
> diff --git a/.openshift/action_hooks/pre_build_jbosseap-6.0 b/.openshift/action_hooks/pre_build_jbosseap-6.0
> old mode 100755
> new mode 100644
> diff --git a/.openshift/action_hooks/pre_start_jbosseap-6.0 b/.openshift/action_hooks/pre_start_jbosseap-6.0
> old mode 100755
> new mode 100644
> diff --git a/.openshift/action_hooks/pre_stop_jbosseap-6.0 b/.openshift/action_hooks/pre_stop_jbosseap-6.0
> old mode 100755
> new mode 100644
> diff --git a/.openshift/cron/weekly/chronograph b/.openshift/cron/weekly/chronograph
> {code}
> 3. EXEC: publish the application to OpenShift
> Result:
> {code}
> /usr/libexec/openshift/cartridges/abstract/info/lib/util: line 992: /var/lib/openshift/1e6a743963104f30bdcdebdff460d42b/app-root/runtime/repo/.openshift/action_hooks/post_start_jbossas-7: Permission denied
> Failed to start jbossas-7
> {code}
> ...but the server is started.
--
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, 4 months
[JBoss JIRA] (JBIDE-12361) PRoblem with WorkspaceFIlesetVirtualComponent, publish using fileset virtual component
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12361?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-12361:
---------------------------------------
Verified the same for JBDS 5.0.2.GA B235
> PRoblem with WorkspaceFIlesetVirtualComponent, publish using fileset virtual component
> --------------------------------------------------------------------------------------
>
> Key: JBIDE-12361
> URL: https://issues.jboss.org/browse/JBIDE-12361
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JBossAS/Servers
> Affects Versions: 3.3.1
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: 3.3.2, 4.0.0.Alpha1
>
> Attachments: JBIDE-12361.33x.patch, JBIDE-12361.33x.v2.patch
>
>
> Steps to reproduce:
> 1) Create a dynamic web project
> 2) Create a POJP
> 3) Inside POJP, make some file structure (foldera, foldera/file1.txt, foldera/file2.txt, folderb, folderb/b1.txt, etc)
> 4) Right-click web project, go to deployment assembly page
> 5) click add
> 6) click 'fileset'
> 7) set root to /pojp
> 8) set includes pattern to **/file1*
> 9) finish
> 10) publish this to some server
> You will note that matching files inside a subdirectory that is not explicitly included in the includes pattern does not get included. In this case, foldera/file1.txt will not be included, and folder 'foldera' will also not be created in the deployment. This is a bug.
> Part of this commit has been made over at JBIDE-12360 by accident
--
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, 4 months