[JBoss JIRA] (JBIDE-22021) For JBIDE 4.3.1.CR1: Prepare for Final/GA [JavaEE]
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22021?page=com.atlassian.jira.plugi... ]
Alexey Kazakov closed JBIDE-22021.
----------------------------------
Assignee: Alexey Kazakov
Resolution: Done
> For JBIDE 4.3.1.CR1: Prepare for Final/GA [JavaEE]
> --------------------------------------------------
>
> Key: JBIDE-22021
> URL: https://issues.jboss.org/browse/JBIDE-22021
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: cdi, cdi-extensions, jsf, seam2
> Reporter: Nick Boldt
> Assignee: Alexey Kazakov
> Priority: Blocker
> Labels: task
> Fix For: 4.3.1.CR1
>
>
> For JBIDE 4.3.1.CR1 [JavaEE]: Please perform the following tasks:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.1.CR1 or Final
> [Unresolved JIRAs with fixVersion = 4.3.1.CR1, 4.3.1.Final, 9.1.0.CR1, 9.1.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JB...]
> 1. Check out your existing *{color:blue}jbosstools-4.3.x{color}* branch:
> {code}
> git checkout jbosstools-4.3.x
> {code}
> 2. Update your *{color:blue}jbosstools-4.3.x branch{color}* root pom to use the latest parent pom version, *{color:blue}4.3.1.Final-SNAPSHOT{color}*:
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.1.Final-SNAPSHOT</version>
> </parent>
> {code}
> Now, your root pom will use parent pom version:
> * *{color:blue}4.3.1.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.x{color}* branch
> 3a. Ensure you've *built your code* using the latest *minimum* target platform version 4.50.2.Final-SNAPSHOT (4.50 = Eclipse Mars.0)
> {code}
> mvn clean verify -Dtpc.version=4.50.2.Final-SNAPSHOT
> {code}
> 3b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.52.0.Final-SNAPSHOT (4.52 = Eclipse Mars.2)
> {code}
> mvn clean verify -Dtpc.version=4.52.0.Final-SNAPSHOT
> {code}
> 4. Close (do not resolve) this JIRA when done.
> 5. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for JavaEE task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-21981) Error during rsync
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21981?page=com.atlassian.jira.plugi... ]
Xavier Coulon commented on JBIDE-21981:
---------------------------------------
The steps I found to reproduce the issue:
- start the server (adapter) for the OpenShift service
- from CLI, {{rm -rf <workspace>/.metadata/.plugins/org.jboss.ide.eclipse.as.core/<project>@<service>/deploy}} to remove all previous deployments
- back in the IDE, select the server adapter and call the {{Publish}} command
- after a few seconds, get the error message below:
{code}
Error renaming <workspace>/.metadata/.plugins/org.eclipse.wst.server.core/tmp6503077788092990412.MF to <workspace>/runtime-Eclipse-mars.2/.metadata/.plugins/org.jboss.ide.eclipse.as.core/sample(a)eap-app/deploy/ROOT.war/META-INF/MANIFEST.MF.
This may be caused by incorrect file permissions, or your server's temporary deploy directory may be on a different filesystem than the final destination.
You may adjust these settings in the server editor.
{code}
> Error during rsync
> ------------------
>
> Key: JBIDE-21981
> URL: https://issues.jboss.org/browse/JBIDE-21981
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Xavier Coulon
> Assignee: Rob Stryker
> Priority: Blocker
> Fix For: 4.3.1.CR1
>
>
> While testing the debugging support on the server adapter, I got the following error:
> {code}
> Could not sync all pods to folder /Users/xcoulon/workspaces/runtime-Eclipse-mars.2/.metadata/.plugins/org.jboss.ide.eclipse.as.core/sample@eap-app/deploy
> OpenShiftBinaryCapability process exited: rsync: delete_file: rmdir "/Users/xcoulon/workspaces/runtime-Eclipse-mars.2/.metadata/.plugins/org.jboss.ide.eclipse.as.core/sample(a)eap-app/deploy/ROOT.war" failed: Directory not empty (66)
> rsync error: some files could not be transferred (code 23) at /SourceCache/rsync/rsync-45/rsync/main.c(1400) [generator=2.6.9]
> error: exit status 23
> {code}
> The content of the {{.../deploy}} directory was:
> {code}
> drwxr-xr-x 9 xcoulon staff 306 Mar 25 12:19 ./
> drwxr-xr-x 4 xcoulon staff 136 Mar 25 11:55 ../
> -rw-r--r-- 1 xcoulon staff 9041 Mar 27 2015 README.txt
> drwxr-xr-x 7 xcoulon staff 238 Mar 25 11:59 ROOT.war/
> -rw-r--r-- 1 xcoulon staff 8 Mar 23 17:59 ROOT.war.deployed
> -rw-r--r-- 1 xcoulon staff 8 Mar 25 12:18 ROOT.war.isdeploying
> -rw-r--r-- 1 xcoulon staff 8415373 Aug 11 2015 activemq-rar.rar
> -rw-r--r-- 1 xcoulon staff 16 Aug 11 2015 activemq-rar.rar.deployed
> -rw-r--r-- 1 xcoulon staff 16 Mar 25 12:18 activemq-rar.rar.isdeploying
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22015) For JBIDE 4.3.1.CR1: Prepare for Final/GA [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch]
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22015?page=com.atlassian.jira.plugi... ]
Nick Boldt closed JBIDE-22015.
------------------------------
Assignee: Nick Boldt
Resolution: Done
> For JBIDE 4.3.1.CR1: Prepare for Final/GA [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch]
> ------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-22015
> URL: https://issues.jboss.org/browse/JBIDE-22015
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: build
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Labels: task
> Fix For: 4.3.1.CR1
>
>
> For JBIDE 4.3.1.CR1 [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch]: Please perform the following tasks:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.1.CR1 or Final
> [Unresolved JIRAs with fixVersion = 4.3.1.CR1, 4.3.1.Final, 9.1.0.CR1, 9.1.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JB...]
> 1. Check out your existing *{color:blue}jbosstools-4.3.x{color}* branch:
> {code}
> git checkout jbosstools-4.3.x
> {code}
> 2. Update your *{color:blue}jbosstools-4.3.x branch{color}* root pom to use the latest parent pom version, *{color:blue}4.3.1.Final-SNAPSHOT{color}*:
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.1.Final-SNAPSHOT</version>
> </parent>
> {code}
> Now, your root pom will use parent pom version:
> * *{color:blue}4.3.1.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.x{color}* branch
> 3a. Ensure you've *built your code* using the latest *minimum* target platform version 4.50.2.Final-SNAPSHOT (4.50 = Eclipse Mars.0)
> {code}
> mvn clean verify -Dtpc.version=4.50.2.Final-SNAPSHOT
> {code}
> 3b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.52.0.Final-SNAPSHOT (4.52 = Eclipse Mars.2)
> {code}
> mvn clean verify -Dtpc.version=4.52.0.Final-SNAPSHOT
> {code}
> 4. Close (do not resolve) this JIRA when done.
> 5. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months