[JBoss JIRA] (JBIDE-13372) improve usability of jiralint emails
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13372?page=com.atlassian.jira.plugi... ]
Nick Boldt closed JBIDE-13372.
------------------------------
Resolution: Done
> improve usability of jiralint emails
> ------------------------------------
>
> Key: JBIDE-13372
> URL: https://issues.jboss.org/browse/JBIDE-13372
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build
> Affects Versions: 4.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Minor
> Fix For: 4.2.0.Final
>
>
> Could these be reformatted to list the names of the offenders at the top of the email, so we don't have to waste time scanning to see whose name is associated w/ the incorrectly versioned jiras?
> Better, can they simply be sent to the people who've set bad fixVersions, rather than the whole list? The only person who needs to see the email below is Snjezana.
> {code}
> -------- Original Message --------
> Subject: Weekly jira sanity check - jbosstools-jiralint - Build # 138 - Still Unstable!
> Date: Sun, 13 Jan 2013 00:01:28 -0500 (EST)
> From: ci-builds(a)redhat.com
> To: external-exadel-list(a)redhat.com
> This is the weekly check for jira problems.
> Please fix the issues outlined below if there are any. Thank you!
> jbosstools-jiralint - Build # 138 - Still Unstable:
> Check console output at http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-jiralint/138/ to view the results.
> 1 tests 1 failure(s) / -2
> 1 tests failed.
> FAILED: ToolsIllegalFixVersion.ToolsIllegalFixVersion.JBIDE-13332_snjeza
> Error Message:
> https://jira.jboss.org/browse/JBIDE-13332 (last update: 22 days, 10:21:51.551414) -> Issue have been resolved with an illegal fix version, i.e. an .x version, LATER or no fix version at all. This means it will not be shown in the right release notes so neither developers or users can see where things happend. Please adjust the issue so it correctly states the proper fix version! Thank you! See http://bit.ly/aTUeGq for how to track down right fix versions.
> Stack Trace:
> JBIDE-13332: Update list of quickstarts to be consistent with current goals(https://jira.jboss.org/browse/JBIDE-13332)
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-19271) p2 director install fails because Central site includes an undefined reference to jboss.discovery.earlyaccess.site.url
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19271?page=com.atlassian.jira.plugi... ]
Nick Boldt closed JBIDE-19271.
------------------------------
> p2 director install fails because Central site includes an undefined reference to jboss.discovery.earlyaccess.site.url
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-19271
> URL: https://issues.jboss.org/browse/JBIDE-19271
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: arquillian, build
> Affects Versions: 4.3.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Critical
> Fix For: 4.3.0.Alpha1
>
>
> Now that Arquillian is in the Central discovery plugin, but is located on the EA site, the p2 director install test is failing.
> {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-install-p2director.install-tests.matrix_4.3.mars/9/INSTALL_PLAN=http%3A%2F%2Fdownload.jboss.org%2Fjbosstools%2Fupdates%2Fnightly%2Fcore%2F4.3.mars%2F%3Bhttp%3A%2F%2Fdownload.jboss.org%2Fjbosstools%2Fdiscovery%2Fnightly%2Fcore%2F4.3.mars%2Fjbosstools-directory.xml,eclipseBundleVersion=mars.M5,jdk=java1.8,label_exp=%28RHEL7||beaker||jboss-prod%29&&!ia64&&!rhts/console}
> 22:35:15 run.director:
> 22:35:15 [echo] Profile Name: epp.package.jee
> 22:35:15 [echo] Install Path: /mnt/hudson_workspace/workspace/jbosstools-install-p2director.install-tests.matrix_4.3.mars/467eb389/eclipse
> 22:35:15 [echo] Source Sites: http://download.jboss.org/jbosstools/updates/nightly/core/4.3.mars/,http:...
> 22:35:15 [echo] IUS to Install:
> 22:35:15 [echo] com.android.ide.eclipse.adt.feature.feature.group,com.android.ide.eclipse.ddms.feature.feature.group,com.android.ide.eclipse.gldebugger.feature.feature.group,com.android.ide.eclipse.hierarchyviewer.feature.feature.group,com.android.ide.eclipse.traceview.feature.feature.group,com.atlassian.connector.eclipse.feature.group,com.atlassian.connector.eclipse.jira.feature.group,com.atlassian.connector.eclipse.monitor.feature.group,com.collabnet.subversion.merge.feature.feature.group,com.github.sevntu.checkstyle.checks.feature.feature.group,edu.umd.cs.findbugs.plugin.eclipse.feature.group,net.java.dev.jna.feature.group,net.sf.eclipsecs.feature.group,net.sourceforge.pmd.eclipse.feature.group,org.eclipse.egit.feature.group,org.eclipse.egit.mylyn.feature.group,org.eclipse.jgit.feature.group,org.eclipse.jst.server_adapters.feature.feature.group,org.eclipse.jst.server_core.feature.feature.group,org.eclipse.jst.server_ui.feature.feature.group,org.eclipse.jst.server_userdoc.feature.feature.group,org.eclipse.m2e.feature.feature.group,org.eclipse.m2e.wtp.feature.feature.group,org.eclipse.m2e.wtp.jaxrs.feature.feature.group,org.eclipse.m2e.wtp.jpa.feature.feature.group,org.eclipse.m2e.wtp.jsf.feature.feature.group,org.eclipse.mylyn.bugzilla_feature.feature.group,org.eclipse.mylyn.commons.feature.group,org.eclipse.mylyn.context_feature.feature.group,org.eclipse.mylyn_feature.feature.group,org.eclipse.mylyn.git.feature.group,org.eclipse.mylyn.github.feature.feature.group,org.eclipse.mylyn.hudson.feature.group,org.eclipse.mylyn.ide_feature.feature.group,org.eclipse.mylyn.java_feature.feature.group,org.eclipse.mylyn.pde_feature.feature.group,org.eclipse.mylyn.team_feature.feature.group,org.eclipse.mylyn.versions.feature.group,org.jboss.ide.eclipse.as.feature.feature.group,org.jboss.tools.aerogear.thym.feature.feature.group,org.jboss.tools.arquillian.feature.feature.group,org.jboss.tools.common.mylyn.feature.feature.group,org.jboss.tools.feedhenry.feature.feature.group,org.jboss.tools.forge.feature.feature.group,org.jboss.tools.forge.m2e.feature.feature.group,org.jboss.tools.jst.angularjs.feature.feature.group,org.jboss.tools.jst.jsdt.feature.feature.group,org.jboss.tools.livereload.feature.feature.group,org.jboss.tools.m2e.wro4j.feature.feature.group,org.jboss.tools.maven.apt.feature.feature.group,org.jboss.tools.maven.cdi.feature.feature.group,org.jboss.tools.maven.feature.feature.group,org.jboss.tools.maven.hibernate.feature.feature.group,org.jboss.tools.maven.jbosspackaging.feature.feature.group,org.jboss.tools.maven.portlet.feature.feature.group,org.jboss.tools.maven.seam.feature.feature.group,org.jboss.tools.openshift.egit.integration.feature.feature.group,org.jboss.tools.openshift.express.feature.feature.group,org.jboss.tools.project.examples.seam.feature.feature.group,org.jboss.tools.runtime.seam.detector.feature.feature.group,org.jboss.tools.seam.feature.feature.group,org.jboss.tools.vpe.browsersim.feature.feature.group,org.jboss.tools.vpe.cordovasim.feature.feature.group,org.sonatype.m2e.egit.feature.feature.group,org.springframework.ide.eclipse.ajdt.feature.feature.group,org.springframework.ide.eclipse.aop.feature.feature.group,org.springframework.ide.eclipse.autowire.feature.feature.group,org.springframework.ide.eclipse.batch.feature.feature.group,org.springframework.ide.eclipse.data.feature.feature.group,org.springframework.ide.eclipse.feature.feature.group,org.springframework.ide.eclipse.integration.feature.feature.group,org.springframework.ide.eclipse.maven.feature.feature.group,org.springframework.ide.eclipse.mylyn.feature.feature.group,org.springframework.ide.eclipse.osgi.feature.feature.group,org.springframework.ide.eclipse.security.feature.feature.group,org.springframework.ide.eclipse.webflow.feature.feature.group,org.springsource.ide.eclipse.commons.feature.group,org.testng.eclipse.feature.group,org.tigris.subversion.clientadapter.feature.feature.group,org.tigris.subversion.clientadapter.svnkit.feature.feature.group,org.tigris.subversion.subclipse.feature.group,org.tigris.subversion.subclipse.graph.feature.feature.group,org.tigris.subversion.subclipse.mylyn.feature.group,org.tmatesoft.svnkit.feature.group,org.zeroturnaround.eclipse.feature.feature.group,org.zeroturnaround.eclipse.m2e.feature.feature.group,org.zeroturnaround.eclipse.wtp.feature.feature.group
> 22:35:33 [p2.dir] java.lang.IllegalArgumentException: Location must be absolute: $%7Bjboss.discovery.earlyaccess.site.url%7D
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-19453) Remote host information does not fit in the server editor
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19453?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-19453:
-------------------------------------
Very strange. It looks perfect now in my environment, where the size of the widget inside the group are perfectly constrained by the group. I can see the full button. Can you have this tested on other OS's? I'm pretty sure (if I remember correctly) that akazakov also tested this for me and it worked for him.
> Remote host information does not fit in the server editor
> ---------------------------------------------------------
>
> Key: JBIDE-19453
> URL: https://issues.jboss.org/browse/JBIDE-19453
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.3.Beta1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.3.0.Beta1
>
> Attachments: remote-runtime-does-not-fit.png, server-editor-2.png
>
>
> Today I noticed this. When I set up a remote server and then open it in the Server editor, the part under Server Behavior where it shows the remote host configuration (e.g. Remote Server Home) does not fix - it needs more space to the right, but it's hidden and there is no way to scroll to view it.
> !remote-runtime-does-not-fit.png!
> The same problem applies to both JBDS 8.1.0.Beta1 and JBDS 9.0.0.Alpha1. So you may want to clone this for 4.3.x.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-19688) Eclipse m2e, workspace resolution and Wildfly deployment issues
by Sylvain Paillé (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19688?page=com.atlassian.jira.plugi... ]
Sylvain Paillé edited comment on JBIDE-19688 at 4/23/15 12:13 PM:
------------------------------------------------------------------
There is a set of 2 projetcs demonstrating the issue. ( see Attachments "manger-test-ko.zip" )
Switch "Enable / Disable workspace resolution" to observe issue.
In the "Enable workspace resolution" jar is exploded into directory.
When deploying app, we have a ClassNotFoundException Utilisateur.class because Wildfly doesn't explore the directory.
was (Author: trix13):
There is a set of 2 projetcs demonstrating the issue.
Switch "Enable / Disable workspace resolution" to observe issue.
In the "Enable workspace resolution" jar is exploded into directory.
When deploying app, we have a ClassNotFoundException Utilisateur.class because Wildfly doesn't explore the directory.
> Eclipse m2e, workspace resolution and Wildfly deployment issues
> ---------------------------------------------------------------
>
> Key: JBIDE-19688
> URL: https://issues.jboss.org/browse/JBIDE-19688
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven, server
> Reporter: Sylvain Paillé
> Assignee: Fred Bricon
> Attachments: manager-test-ko.zip
>
>
> Hello !
> I just found on Wildfly a Jboss (resolved ?) related bug.
> See : https://issues.jboss.org/browse/AS7-4704
> When using Eclipse and m2e plugin, deploy with "workspace resolution" make WEB-INF/lib/ jar to be exploded into directories ...
> Wildfly simply ignore them when running app.
> Disabling Workspace resolution is a workaround.
> Have you met a similar bug ?
> Thx
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years