January 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-13320) CLONE - Execute permissions modified in merged openshift projects ("use existing") causing action hoooks to not execute

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13320?page=com.atlassian.jira.plugi... ] Len DiMaggio updated JBIDE-13320: --------------------------------- Labels: respin-b (was: ) > 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 > Labels: respin-b > 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13348) Cannot deploy BPEL project

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13348?page=com.atlassian.jira.plugi... ] Andrej Podhradsky updated JBIDE-13348: -------------------------------------- Environment: (was: http://download.jboss.org/jbosstools/updates/JBossTools-3.3.2.CR2.core/) > Cannot deploy BPEL project > -------------------------- > > Key: JBIDE-13348 > URL: https://issues.jboss.org/browse/JBIDE-13348 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: JBossAS/Servers, SOA Tooling > Affects Versions: 3.3.2 > Reporter: Andrej Podhradsky > Assignee: Rob Stryker > Priority: Blocker > > After installing AS feature from JBoss Tools CR2 core the bpel project cannot be deployed to server. > See JBDS-2437 -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13348) Cannot deploy BPEL project

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13348?page=com.atlassian.jira.plugi... ] Andrej Podhradsky updated JBIDE-13348: -------------------------------------- Steps to Reproduce: 1. Install eclipse indigo for jee developers SR2 2. Install AS from http://download.jboss.org/jbosstools/updates/JBossTools-3.3.2.CR2.core/ 3. Install BPEL from http://download.jboss.org/jbosstools/updates/stable/indigo/soa-tooling/ 4. Deploy a bpel project into server > Cannot deploy BPEL project > -------------------------- > > Key: JBIDE-13348 > URL: https://issues.jboss.org/browse/JBIDE-13348 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: JBossAS/Servers, SOA Tooling > Affects Versions: 3.3.2 > Environment: http://download.jboss.org/jbosstools/updates/JBossTools-3.3.2.CR2.core/ > Reporter: Andrej Podhradsky > Assignee: Rob Stryker > Priority: Blocker > > After installing AS feature from JBoss Tools CR2 core the bpel project cannot be deployed to server. > See JBDS-2437 -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13348) Cannot deploy BPEL project

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13348?page=com.atlassian.jira.plugi... ] Andrej Podhradsky updated JBIDE-13348: -------------------------------------- Environment: http://download.jboss.org/jbosstools/updates/JBossTools-3.3.2.CR2.core/ (was: http://download.jboss.org/jbosstools/updates/JBossTools-3.3.2.CR2.core/ http://download.jboss.org/jbosstools/updates/stable/indigo/soa-tooling/) > Cannot deploy BPEL project > -------------------------- > > Key: JBIDE-13348 > URL: https://issues.jboss.org/browse/JBIDE-13348 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: JBossAS/Servers, SOA Tooling > Affects Versions: 3.3.2 > Environment: http://download.jboss.org/jbosstools/updates/JBossTools-3.3.2.CR2.core/ > Reporter: Andrej Podhradsky > Assignee: Rob Stryker > Priority: Blocker > > After installing AS feature from JBoss Tools CR2 core the bpel project cannot be deployed to server. > See JBDS-2437 -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13348) Cannot deploy BPEL project

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13348?page=com.atlassian.jira.plugi... ] Andrej Podhradsky updated JBIDE-13348: -------------------------------------- Environment: http://download.jboss.org/jbosstools/updates/JBossTools-3.3.2.CR2.core/ http://download.jboss.org/jbosstools/updates/stable/indigo/soa-tooling/ was:http://download.jboss.org/jbosstools/updates/JBossTools-3.3.2.CR2.core/ > Cannot deploy BPEL project > -------------------------- > > Key: JBIDE-13348 > URL: https://issues.jboss.org/browse/JBIDE-13348 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: JBossAS/Servers, SOA Tooling > Affects Versions: 3.3.2 > Environment: http://download.jboss.org/jbosstools/updates/JBossTools-3.3.2.CR2.core/ > http://download.jboss.org/jbosstools/updates/stable/indigo/soa-tooling/ > Reporter: Andrej Podhradsky > Assignee: Rob Stryker > Priority: Blocker > > After installing AS feature from JBoss Tools CR2 core the bpel project cannot be deployed to server. > See JBDS-2437 -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13347) Add deltaspike jars into nexus repository (releases/snapshots)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13347?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-13347: ------------------------------------ Latest parent pom refs both snapshots and release repos: {code} <repositories> <repository> <id>jboss-releases</id> <name>JBoss Releases Maven Repository</name> <url>https://repository.jboss.org/nexus/content/repositories/releases/</url> <releases> <enabled>true</enabled> </releases> </repository> <repository> <id>jboss-snapshots-repository</id> <name>JBoss Snapshots Repository</name> <url>https://repository.jboss.org/nexus/content/repositories/snapshots/</url> <snapshots> <enabled>true</enabled> </snapshots> </repository> </repositories> {code} Bounce to [~mickael_istria] -- what could be missing? Maybe the swtbot tests aren't using the latest parent pom? [~jjankovi] can you point to your sources? How do you build the tests? > Add deltaspike jars into nexus repository (releases/snapshots) > -------------------------------------------------------------- > > Key: JBIDE-13347 > URL: https://issues.jboss.org/browse/JBIDE-13347 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: UpStream > Reporter: Jaroslav Jankovič > Assignee: Mickael Istria > > Now, deltaspike libraries are not in jboss nexus repositories defined in our shared settins.xml (releases/snapshots). They are part of central jboss nexus repo but this one is not used when building swtbot tests. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13347) Add deltaspike jars into nexus repository (releases/snapshots)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13347?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-13347: ------------------------------- Assignee: Mickael Istria (was: Nick Boldt) > Add deltaspike jars into nexus repository (releases/snapshots) > -------------------------------------------------------------- > > Key: JBIDE-13347 > URL: https://issues.jboss.org/browse/JBIDE-13347 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: UpStream > Reporter: Jaroslav Jankovič > Assignee: Mickael Istria > > Now, deltaspike libraries are not in jboss nexus repositories defined in our shared settins.xml (releases/snapshots). They are part of central jboss nexus repo but this one is not used when building swtbot tests. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13348) Cannot deploy BPEL project

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13348?page=com.atlassian.jira.plugi... ] Andrej Podhradsky commented on JBIDE-13348: ------------------------------------------- I don't know if the the problem is in AS or BPEL feature, but take into account the following 1. installing bpel feature 1.1.0.v20120717-1107-H8-GA-SOA from http://download.jboss.org/jbosstools/updates/stable/indigo/soa-tooling is NOT working 2. installing bpel feature 1.1.0.v20121212-2316-H52-Nightly-SOA from http://download.jboss.org/jbosstools/builds/staging/_composite_/soa-tooli... works The weird thing is that both bpel features are of the same verion (1.1.0) > Cannot deploy BPEL project > -------------------------- > > Key: JBIDE-13348 > URL: https://issues.jboss.org/browse/JBIDE-13348 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: JBossAS/Servers, SOA Tooling > Affects Versions: 3.3.2 > Environment: http://download.jboss.org/jbosstools/updates/JBossTools-3.3.2.CR2.core/ > Reporter: Andrej Podhradsky > Assignee: Rob Stryker > Priority: Blocker > > After installing AS feature from JBoss Tools CR2 core the bpel project cannot be deployed to server. > See JBDS-2437 -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13349) JBoss Way 'about' page refers to JBDS5|OBJ| - can we update this to refer to JBDS6?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13349?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-13349: ------------------------------- Component/s: website > JBoss Way 'about' page refers to JBDS5|OBJ| - can we update this to refer to JBDS6? > ----------------------------------------------------------------------------------- > > Key: JBIDE-13349 > URL: https://issues.jboss.org/browse/JBIDE-13349 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: website > Reporter: Len DiMaggio > Assignee: Michelle Murray > Attachments: Screenshot-2.png > > > See attached screenshot -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13349) JBoss Way 'about' page refers to JBDS5|OBJ| - can we update this to refer to JBDS6?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13349?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-13349: ------------------------------- Assignee: Ray Ploski (was: Michelle Murray) > JBoss Way 'about' page refers to JBDS5|OBJ| - can we update this to refer to JBDS6? > ----------------------------------------------------------------------------------- > > Key: JBIDE-13349 > URL: https://issues.jboss.org/browse/JBIDE-13349 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: website > Reporter: Len DiMaggio > Assignee: Ray Ploski > Attachments: Screenshot-2.png > > > See attached screenshot -- 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, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues January 2013