[JBoss JIRA] (JBDS-4191) problem installing atlassian: depends on javax.servlet 3.1.0 -- remove atlassian from Central
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4191?page=com.atlassian.jira.plugin.... ]
Nick Boldt reassigned JBDS-4191:
--------------------------------
Assignee: Nick Boldt (was: Jeff MAURY)
> problem installing atlassian: depends on javax.servlet 3.1.0 -- remove atlassian from Central
> ---------------------------------------------------------------------------------------------
>
> Key: JBDS-4191
> URL: https://issues.jboss.org/browse/JBDS-4191
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Sub-task
> Components: central-update, rpm
> Affects Versions: 10.2.0.AM3
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 10.3.0.AM1
>
>
> atlassian: depends on javax.servlet 3.1.0 (via req-bundle on javax.xml.rpc 1.1.0 from c.a.conn.eclipse.jira.core)
> : also depends on org.eclipse.core.runtime.compatibility.auth
> : also depends on mortbay, which breaks because of javax/servlet/Servlet
> {code}
> !MESSAGE Authorization infrastructure (org.eclipse.core.runtime.compatibility.auth) not installed.
> !STACK 0
> java.lang.ClassNotFoundException: org.eclipse.core.internal.runtime.auth.AuthorizationDatabase cannot be found by org.eclipse.core.runtime_3.12.0.v20160920-1429
> at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:461)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:372)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:364)
> at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:161)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:264)
> at org.eclipse.core.internal.runtime.AuthorizationHandler.getAuthClass(AuthorizationHandler.java:48)
> at org.eclipse.core.internal.runtime.AuthorizationHandler.loadKeyring(AuthorizationHandler.java:69)
> at org.eclipse.core.internal.runtime.AuthorizationHandler.flushAuthorizationInfo(AuthorizationHandler.java:231)
> at org.eclipse.core.runtime.Platform.flushAuthorizationInfo(Platform.java:590)
> at com.atlassian.connector.eclipse.internal.commons.ui.MigrateToSecureStorageJob.migrateToSecureStorage(MigrateToSecureStorageJob.java:89)
> at com.atlassian.connector.eclipse.internal.commons.ui.MigrateToSecureStorageJob.runInUIThread(MigrateToSecureStorageJob.java:60)
> !ENTRY org.eclipse.core.jobs 4 2 2016-11-17 21:09:30.244
> !MESSAGE An internal error occurred during: "Start Embedded Web Server".
> !STACK 0
> java.lang.LinkageError: loader constraint violation: when resolving method "org.mortbay.jetty.servlet.ServletHolder.<init>(Ljavax/servlet/Servlet;)V" the class loader (instance of org/eclipse/osgi/internal/loader/EquinoxClassLoader) of the current class, com/atlassian/connector/eclipse/internal/directclickthrough/ui/DirectClickThroughUiPlugin$2, and the class loader (instance of org/eclipse/osgi/internal/loader/EquinoxClassLoader) for the method's defining class, org/mortbay/jetty/servlet/ServletHolder, have different Class objects for the type javax/servlet/Servlet used in the signature
> at com.atlassian.connector.eclipse.internal.directclickthrough.ui.DirectClickThroughUiPlugin$2.runImpl(DirectClickThroughUiPlugin.java:88)
> at com.atlassian.connector.eclipse.internal.core.jobs.JobWithStatus.run(JobWithStatus.java:50)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> depends on and installs javax.servlet:
> * com.atlassian.connector.eclipse.bamboo.feature
> * com.atlassian.connector.eclipse.directclickthrough.feature
> * com.atlassian.connector.eclipse.jira.feature
> * com.atlassian.connector.commons.feature -> connector.commons -> javax.xml.rpc 1.1.0 -> javax.servlet 3.1.0
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (JBIDE-18507) JavaEE tests timeout after 7 hours
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18507?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-18507:
-------------------------------
Fix Version/s: 4.4.2.Final
(was: 4.3.x)
> JavaEE tests timeout after 7 hours
> ----------------------------------
>
> Key: JBIDE-18507
> URL: https://issues.jboss.org/browse/JBIDE-18507
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html-source-editing
> Affects Versions: 4.2.0.CR2
> Reporter: Nick Boldt
> Assignee: Jeff MAURY
> Fix For: 4.4.2.Final
>
>
> Since latest changes on Oct 3, JavaEE job [1] now takes more than 7hrs to complete all tests.
> [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
> {code}
> #62 (Oct 3, 2014 10:04:12 PM)
> JBIDE-18504 4 Test Failure(s) in JBIDE 4.2.0.CR2 for jsf component (commit: f6fdec31b78be882f2690c232aa5d5f69c6b25bb) — akazakov / detail
> #61 (Oct 3, 2014 4:01:13 PM)
> JBIDE-18350: Loader constraint violation while generating Seam entities (commit: c1577645b20dca5626bade26819250227f90d391) — koen.aers / detail
> Updated paren pom to 4.2.0.CR2 (commit: 3ca8e2ca64d981bd48412fd1e95919da1ec76d99) — akazakov / detail
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (JBIDE-6343) Create a "sanity check plugin/feature" tool for running on integration builds
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-6343?page=com.atlassian.jira.plugin... ]
Nick Boldt closed JBIDE-6343.
-----------------------------
Resolution: Won't Fix
Closing as this was started by Max 6 years ago re: SVN stuff, and he's moved on without ever linking to the code-in-progress. So... WONTFIX.
> Create a "sanity check plugin/feature" tool for running on integration builds
> -----------------------------------------------------------------------------
>
> Key: JBIDE-6343
> URL: https://issues.jboss.org/browse/JBIDE-6343
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: build
> Reporter: Max Rydahl Andersen
> Assignee: Jeff MAURY
> Priority: Minor
> Fix For: 4.4.2.Final
>
>
> I keep seeing the following antipatterns or oversights happening in our codebase, most of them I believe we could mechanically check for.
> No duplicate names in .project since it makes it impossible to import into Eclipse
> bin folders should be svn:ignored and not be committed (causes problems when doing svn synchronization and all the .class files are showing up and some even commits it)
> things in svn:ignore should be committed (either someone overrode svn:ignore or the svn:ignore were added later)
> if pom.xml file exists target should be svn:ignored too.
> Execution environment should be specified in manifest.mf's
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (JBIDE-6343) Create a "sanity check plugin/feature" tool for running on integration builds
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-6343?page=com.atlassian.jira.plugin... ]
Nick Boldt updated JBIDE-6343:
------------------------------
Fix Version/s: 4.4.2.Final
(was: LATER)
> Create a "sanity check plugin/feature" tool for running on integration builds
> -----------------------------------------------------------------------------
>
> Key: JBIDE-6343
> URL: https://issues.jboss.org/browse/JBIDE-6343
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: build
> Reporter: Max Rydahl Andersen
> Assignee: Jeff MAURY
> Priority: Minor
> Fix For: 4.4.2.Final
>
>
> I keep seeing the following antipatterns or oversights happening in our codebase, most of them I believe we could mechanically check for.
> No duplicate names in .project since it makes it impossible to import into Eclipse
> bin folders should be svn:ignored and not be committed (causes problems when doing svn synchronization and all the .class files are showing up and some even commits it)
> things in svn:ignore should be committed (either someone overrode svn:ignore or the svn:ignore were added later)
> if pom.xml file exists target should be svn:ignored too.
> Execution environment should be specified in manifest.mf's
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (JBDS-3439) Unable to add a new Forge Runtime
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/JBDS-3439?page=com.atlassian.jira.plugin.... ]
George Gastaldi commented on JBDS-3439:
---------------------------------------
Can we reject this issue? For the reasons explained above
> Unable to add a new Forge Runtime
> ---------------------------------
>
> Key: JBDS-3439
> URL: https://issues.jboss.org/browse/JBDS-3439
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Quality Risk
> Components: forge
> Affects Versions: 8.0.0.GA, 8.1.0.GA
> Environment: Fedora 20, jdk1.7.0_67, JBoss Developer Studio 8+
> Reporter: Miguel Angel Morales Pedraza
> Assignee: Jeff MAURY
> Priority: Optional
> Labels: forge, runtime
> Fix For: 8.x
>
>
> Unable to add a new Forge runtime on JBDS 8.0.0 and 8.1.0. The button "Add" it doesn't shown anymore.
> On the JBDS v7.1.1 this button appears.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months