[JBoss JIRA] (JBIDE-18985) provide tool to audit BUILD_ALIAS in feature qualifiers when aggregated
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18985?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-18985:
---------------------------------------------
A few observations:
- not sure it fits in an enforcer plugin since enforcer rules are executed *before* the build and used to check if the conditions of the build are correct - these versions checks are more a check of the build result.
- *why* should the buildalias be the same for all ? that implies we are rebuilding everything when we are trying to move to builds that only update components that actually needed to change.
- and shouldn't this test be more about ensuring that the *delta* between the builds are consistent. i.e. that it is not going back, always incrementing and if the SHA's are different for the binary content that the versions/qualifiers have changed accordingly. i.e. between two non-released milestones (4.2.0.Alpha1 and 4.2.0.Beta2) the versions can stay the same even if content changes but the build qualifier timestamp should at least be different and higher than the former. when a milestone is released then the next milestones (i.e. 4.2.0.Final to 4.2.1.Alpha1) the content and version must be exactly the same or the version MUST have bumped. If not then we did a rebuild without actually bumping where it should have been bumped (that should be marked as Error/Red build fail)
> provide tool to audit BUILD_ALIAS in feature qualifiers when aggregated
> -----------------------------------------------------------------------
>
> Key: JBIDE-18985
> URL: https://issues.jboss.org/browse/JBIDE-18985
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, updatesite
> Affects Versions: 4.3.0.Alpha1
> Reporter: Nick Boldt
>
> Based on discussion {quote}Do you have a test for "expected BUILD_ALIAS value in feature qualifiers" ?{quote}
> Some tests we can run (forgive this pseudocode):
> {code}
> // for builds up to a x.y.0 release
> if ((BUILD_ALIAS in (Alpha*, Beta*, CR*) and jbosstools.version endsWith(".0")) {
> // make sure all features end in the same BUILD_ALIAS, or Final
> // if anything doesn't match WARN (want a build to be yellow, not red)
> }
> {code}
> {code}
> // for GA builds and followup maintenance
> if ((BUILD_ALIAS in (Final, GA)) {
> // make sure all com.* features end in GA, and all others end in Final
> // if anything doesn't match FAIL (want a build to be red)
> }
> {code}
> Once we have that coded, perhaps into a maven enforcer plugin?, we can fine tune it for cases like where Freemarker does an update in Alpha and then does nothing for 4 months, waiting for CR/GA.
> Should they have to keep updating their root pom just so the BUILD_ALIAS matches and they're building against the correct target platform?
> Or, should their code remain dormant, but their job's config.xml be updated to override the BUILD_ALIAS & TARGET_PLATFORM values to the correct versions?
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (JBIDE-18976) VPE Tag Navigation Bar looks empty when cursor located between tags without text
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18976?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov updated JBIDE-18976:
-------------------------------------------
Fix Version/s: 4.3.0.Alpha1
> VPE Tag Navigation Bar looks empty when cursor located between tags without text
> --------------------------------------------------------------------------------
>
> Key: JBIDE-18976
> URL: https://issues.jboss.org/browse/JBIDE-18976
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: visual-page-editor-core
> Affects Versions: 4.2.1.Final
> Environment: Fedora 20 Linux x86_64
> OpenJDK 7
> export SWT_GTK3=1
> Reporter: Denis Golovin
> Priority: Minor
> Fix For: 4.3.0.Alpha1
>
> Attachments: screenshot1.png
>
>
> Navigation bar is empty sometimes. It happens when cursor is between tags and there is no #text node. It should show the nodes with parent tag when it is behind closing tag. Do not forget about case for tags that has optional closing tag.
> !screenshot1.png!
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (JBIDE-18880) Visual Preview java fatal error
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18880?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov updated JBIDE-18880:
-------------------------------------------
Fix Version/s: 4.3.0.Alpha1
> Visual Preview java fatal error
> -------------------------------
>
> Key: JBIDE-18880
> URL: https://issues.jboss.org/browse/JBIDE-18880
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: visual-page-editor-core
> Affects Versions: 4.2.0.Final
> Environment: Fedora 20 x86_64
> java version "1.7.0_71"
> OpenJDK Runtime Environment (fedora-2.5.3.0.fc20-x86_64 u71-b14)
> OpenJDK 64-Bit Server VM (build 24.65-b04, mixed mode)
> Reporter: Denis Golovin
> Fix For: 4.3.0.Alpha1
>
> Attachments: hs_error.log
>
>
> JJVM crashes with console output:
> {code}
> #
> # A fatal error has been detected by the Java Runtime Environment:
> #
> # SIGSEGV (0xb) at pc=0x00007f49a16acbcc, pid=15823, tid=139957761074944
> #
> # JRE version: OpenJDK Runtime Environment (7.0_71-b14) (build 1.7.0_71-mockbuild_2014_10_15_17_02-b00)
> # Java VM: OpenJDK 64-Bit Server VM (24.65-b04 mixed mode linux-amd64 compressed oops)
> # Derivative: IcedTea 2.5.3
> # Distribution: Built on Fedora release 20 (Heisenbug) (Wed Oct 15 17:02:58 UTC 2014)
> # Problematic frame:
> # C [libjavascriptcoregtk-3.0.so.0+0x2e2bcc] void JSC::ConservativeRoots::genericAddSpan<JSC::CompositeMarkHook<JSC::JITStubRoutineSet, SC::DFGCodeBlocks> >(void*, void*, JSC::CompositeMarkHook<JSC::JITStubRoutineSet, JSC::DFGCodeBlocks>&)+0x7c
> #
> # Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
> #
> # An error report file with more information is saved as:
> # /tmp/jvm-15823/hs_error.log
> #
> # If you would like to submit a bug report, please include
> # instructions on how to reproduce the bug and visit:
> # http://icedtea.classpath.org/bugzilla
> #
> {code}
> see attached [^hs_error.log]
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (JBIDE-18987) [VIsual Preview] IllegalArgumentException: Path must include project and resource name: /favicon.ico
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18987?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov updated JBIDE-18987:
-------------------------------------------
Fix Version/s: 4.3.0.Alpha1
> [VIsual Preview] IllegalArgumentException: Path must include project and resource name: /favicon.ico
> ----------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18987
> URL: https://issues.jboss.org/browse/JBIDE-18987
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: visual-page-editor-core
> Affects Versions: 4.2.1.Final
> Environment: Ubuntu Linux x86_64
> OpenJDK 7
> SWT_GTK3=1
> Reporter: Denis Golovin
> Priority: Minor
> Fix For: 4.3.0.Alpha1
>
>
> {code}Exception in thread "Thread-902" java.lang.IllegalArgumentException: Path must include project and resource name: /favicon.ico
> at org.eclipse.core.runtime.Assert.isLegal(Assert.java:63)
> at org.eclipse.core.internal.resources.Workspace.newResource(Workspace.java:2137)
> at org.eclipse.core.internal.resources.Container.getFile(Container.java:208)
> at org.jboss.tools.vpe.preview.core.transform.VpvController.getResource(VpvController.java:54)
> at org.jboss.tools.vpe.preview.core.server.VpvSocketProcessor.processRequest(VpvSocketProcessor.java:83)
> at org.jboss.tools.vpe.preview.core.server.VpvSocketProcessor.run(VpvSocketProcessor.java:68)
> at java.lang.Thread.run(Thread.java:745)
> Exception in thread "Thread-905" java.lang.IllegalArgumentException: Path must include project and resource name: /favicon.ico
> at org.eclipse.core.runtime.Assert.isLegal(Assert.java:63)
> at org.eclipse.core.internal.resources.Workspace.newResource(Workspace.java:2137)
> at org.eclipse.core.internal.resources.Container.getFile(Container.java:208)
> at org.jboss.tools.vpe.preview.core.transform.VpvController.getResource(VpvController.java:54)
> at org.jboss.tools.vpe.preview.core.server.VpvSocketProcessor.processRequest(VpvSocketProcessor.java:83)
> at org.jboss.tools.vpe.preview.core.server.VpvSocketProcessor.run(VpvSocketProcessor.java:68)
> at java.lang.Thread.run(Thread.java:745)
> Exception in thread "Thread-919" java.lang.IllegalArgumentException: Path must include project and resource name: /favicon.ico
> at org.eclipse.core.runtime.Assert.isLegal(Assert.java:63)
> at org.eclipse.core.internal.resources.Workspace.newResource(Workspace.java:2137)
> at org.eclipse.core.internal.resources.Container.getFile(Container.java:208)
> at org.jboss.tools.vpe.preview.core.transform.VpvController.getResource(VpvController.java:54)
> at org.jboss.tools.vpe.preview.core.server.VpvSocketProcessor.processRequest(VpvSocketProcessor.java:83)
> at org.jboss.tools.vpe.preview.core.server.VpvSocketProcessor.run(VpvSocketProcessor.java:68)
> at java.lang.Thread.run(Thread.java:745){code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (JBIDE-18977) JBoss HTML Editor pollutes log with NullPointerExceptions
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18977?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov updated JBIDE-18977:
-------------------------------------------
Fix Version/s: 4.3.0.Alpha1
> JBoss HTML Editor pollutes log with NullPointerExceptions
> ---------------------------------------------------------
>
> Key: JBIDE-18977
> URL: https://issues.jboss.org/browse/JBIDE-18977
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: visual-page-editor-core
> Reporter: Denis Golovin
> Fix For: 4.3.0.Alpha1
>
>
> {code}java.lang.NullPointerException
> at org.jboss.tools.vpe.preview.editor.VpvEditor$10.documentChanged(VpvEditor.java:671)
> at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument._fireDocumentChanged(BasicStructuredDocument.java:460)
> at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.fireStructuredDocumentEvent(BasicStructuredDocument.java:1184)
> at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.internalReplaceText(BasicStructuredDocument.java:1964)
> at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.replaceText(BasicStructuredDocument.java:2423)
> at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.replaceText(BasicStructuredDocument.java:2408)
> at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.access$2(JobSafeStructuredDocument.java:1)
> at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument$3.run(JobSafeStructuredDocument.java:141)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.wst.sse.ui.EditorExecutionContext.execute(EditorExecutionContext.java:149)
> at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.replaceText(JobSafeStructuredDocument.java:144)
> at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.replace(BasicStructuredDocument.java:2368)
> at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.access$0(JobSafeStructuredDocument.java:1)
> at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument$1.run(JobSafeStructuredDocument.java:103)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.wst.sse.ui.EditorExecutionContext.execute(EditorExecutionContext.java:149)
> at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.replace(JobSafeStructuredDocument.java:106)
> at org.eclipse.jface.text.projection.ProjectionTextStore.replace(ProjectionTextStore.java:111)
> at org.eclipse.jface.text.AbstractDocument.replace(AbstractDocument.java:1184)
> at org.eclipse.jface.text.AbstractDocument.replace(AbstractDocument.java:1210)
> at org.eclipse.jface.text.projection.ProjectionDocument.replace(ProjectionDocument.java:629)
> at org.eclipse.jface.text.DefaultDocumentAdapter.replaceTextRange(DefaultDocumentAdapter.java:248)
> at org.eclipse.swt.custom.StyledText.modifyContent(StyledText.java:7268)
> at org.eclipse.swt.custom.StyledText.sendKeyEvent(StyledText.java:8111)
> at org.eclipse.swt.custom.StyledText.doBackspace(StyledText.java:2285)
> at org.eclipse.swt.custom.StyledText.invokeAction(StyledText.java:7058)
> at org.eclipse.swt.custom.StyledText.handleKey(StyledText.java:5959)
> at org.eclipse.swt.custom.StyledText.handleKeyDown(StyledText.java:5986)
> at org.eclipse.swt.custom.StyledText$7.handleEvent(StyledText.java:5663)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4454)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1412)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1397)
> at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1424)
> at org.eclipse.swt.widgets.Widget.gtk_key_press_event(Widget.java:824)
> at org.eclipse.swt.widgets.Control.gtk_key_press_event(Control.java:3272)
> at org.eclipse.swt.widgets.Composite.gtk_key_press_event(Composite.java:769)
> at org.eclipse.swt.widgets.Widget.windowProc(Widget.java:2098)
> at org.eclipse.swt.widgets.Control.windowProc(Control.java:5513)
> at org.eclipse.swt.widgets.Display.windowProc(Display.java:4668)
> at org.eclipse.swt.internal.gtk.OS._gtk_main_do_event(Native Method)
> at org.eclipse.swt.internal.gtk.OS.gtk_main_do_event(OS.java:9106)
> at org.eclipse.swt.widgets.Display.eventProc(Display.java:1253)
> at org.eclipse.swt.internal.gtk.OS._g_main_context_iteration(Native Method)
> at org.eclipse.swt.internal.gtk.OS.g_main_context_iteration(OS.java:2477)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3407)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1438)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (JBIDE-18983) Project cannot be built. Possible open file handle
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18983?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-18983:
---------------------------------------------
afaics, this does not relate to anything related to p2's inability to handle copying/moving of files between different volumes.
This bug is caused by either an eclipse plugin or part of the server is holding on to the persistence.xml via for example a forgotten file close or classloader leak.
We've had similar issues with jsf resources in past being locked by a bug in richfaces libraries use of classloader (now long time fixed) and similar bug in one of our editors forgot to close the file during save causing locking on windows (but seem to worked fine on linux/osx...and those we know about are fixed too)
[~clerum] can you help locate wether it is the server or eclipse that is holding onto the file so we can know where to look ?
You can use Process Explorer (http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx) to locate it (tutorial here: http://www.techsupportalert.com/content/how-find-out-which-windows-proces...)
> Project cannot be built. Possible open file handle
> --------------------------------------------------
>
> Key: JBIDE-18983
> URL: https://issues.jboss.org/browse/JBIDE-18983
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, jsp/jsf/xml/html source editing, updatesite
> Affects Versions: 4.2.1.Final
> Environment: luna x64 windows 8.1 x64
> java 8u25 x64
> Reporter: Cody Lerum
> Assignee: Nick Boldt
> Fix For: 4.2.x, 4.3.x
>
>
> Frequently when working in a Java EE7 project I will get an error like.
> "The project was not built due to "Could not delete '/gp-server/target/classes/META-INF`.". Fix the problem, then try refreshing this project and building since it may be inconsistent.
> I've looked into a process explorer in windows and then this case is happening there is always a javaw.exe process with a file handle to "V:\workspace\gp-server\target\classes\META-INF\persistence.xml
> It looks like either jboss tools or eclipse is holding on to a file handle for this.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months