[JBoss JIRA] (JBDS-3126) For JBDS 8.0.0.CR1: Code Freeze + Branch
by Mickael Istria (JIRA)
Mickael Istria created JBDS-3126:
------------------------------------
Summary: For JBDS 8.0.0.CR1: Code Freeze + Branch
Key: JBDS-3126
URL: https://issues.jboss.org/browse/JBDS-3126
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Task
Security Level: Public (Everyone can see)
Components: installer
Reporter: Mickael Istria
Priority: Blocker
Fix For: 8.0.0.CR1
For JBDS 8.0.0.CR1: Please perform the following tasks:
0. If nothing has changed in your component since 4.1.1.Final / 7.1.0.GA (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*.
Otherwise:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.CR1
[Unresolved JIRAs with fixVersion = 4.2.0.CR1, 8.0.0.CR1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...]
1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1.
*NOTE:* If you already did this for the previous milestone you do *not* need to do so again.
{code}
mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:0.21.0:set-version -DnewVersion=1.0.1-SNAPSHOT
{code}
2. Update your root pom to use parent pom version 4.2.0.CR1-SNAPSHOT;
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.2.0.CR1-SNAPSHOT</version>
</parent>
{code}
3. Ensure you've built & run your plugin tests using the latest target platform version 4.40.0.CR1-SNAPSHOT;
{code}
mvn clean verify -Dtpc.version=4.40.0.CR1 # (if the TP is already released)
or
mvn clean verify -Dtpc.version=4.40.0.CR1-SNAPSHOT # (if still being staged)
{code}
4. Branch from your existing master branch into a new *{color:blue}jbosstools-4.2.x{color}* branch;
{code}
git fetch origin master
git checkout FETCH_HEAD
git checkout -b jbosstools-4.2.x
git push origin jbosstools-4.2.x
{code}
5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*.
{code}
git checkout master
git pull origin master
{code}
6. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.2.0.CR2-SNAPSHOT{color}*:
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.2.0.CR2-SNAPSHOT</version>
</parent>
{code}
Now, your root pom will use parent pom version:
* *{color:blue}4.2.0.CR1-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.2.x{color}* branch, and
* *{color:orange}4.2.0.CR2-SNAPSHOT{color}* in your *{color:orange}master{color}* branch.
7. Close (do not resolve) this JIRA when done.
8. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next.
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-12200) Forge: bad location exception in pick-up command, forge runtime cannot recover
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12200?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen closed JBIDE-12200.
---------------------------------------
Resolution: Won't Fix
upstream FORGE-607 wont be fixed thus same for this issue.
> Forge: bad location exception in pick-up command, forge runtime cannot recover
> ------------------------------------------------------------------------------
>
> Key: JBIDE-12200
> URL: https://issues.jboss.org/browse/JBIDE-12200
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Affects Versions: 3.3.0.Final
> Reporter: Pavol Srna
> Assignee: Koen Aers
> Fix For: 4.2.x
>
>
> [test] model $ pick-up testproject/src/main/java/com/example/testproject/model/C***ERROR*** Exception encountered: [UnknownFileResource] can have no children (type "set VERBOSE true" to enable stack traces)
> Exception Stack Trace:
> =======================================
> org.eclipse.jface.text.BadLocationException
> at org.eclipse.jface.text.AbstractDocument.replace(AbstractDocument.java:1179)
> at org.eclipse.jface.text.AbstractDocument.replace(AbstractDocument.java:1210)
> at org.jboss.tools.forge.ui.document.ForgeDocument.handleAvailableOutput(ForgeDocument.java:106)
> at org.jboss.tools.forge.ui.document.ForgeDocument.access$0(ForgeDocument.java:100)
> at org.jboss.tools.forge.ui.document.ForgeDocument$1.outputAvailable(ForgeDocument.java:66)
> at org.jboss.tools.forge.core.io.ForgeAnsiCommandFilter.outputAvailable(ForgeAnsiCommandFilter.java:45)
> at org.jboss.tools.forge.core.io.ForgeHiddenOutputFilter.outputAvailable(ForgeHiddenOutputFilter.java:70)
> at org.jboss.tools.forge.ui.document.ForgeDocument$SyncForgeCommandFilter.access$0(ForgeDocument.java:1)
> at org.jboss.tools.forge.ui.document.ForgeDocument$SyncForgeCommandFilter$1.run(ForgeDocument.java:37)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3563)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3212)
> at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701)
> at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665)
> at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499)
> at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1410)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1386)
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18071) Newly created JPA Entity did not appear in the Project Explorer
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18071?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-18071:
---------------------------------------------
eclipse integration refreshes the workspace based on initial selection so ifyou generate files outside that they are not refreshed.
> Newly created JPA Entity did not appear in the Project Explorer
> ---------------------------------------------------------------
>
> Key: JBIDE-18071
> URL: https://issues.jboss.org/browse/JBIDE-18071
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Affects Versions: 4.2.0.Beta3
> Reporter: Xavier Coulon
> Assignee: Koen Aers
> Priority: Blocker
> Fix For: 4.2.0.CR1
>
>
> Following the Ticket Monster example, the {{Event}} JPA entity did not automatically appear in the Project Explorer. It was visible after clicking on 'Refresh' at the package level, though.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months