[JBoss JIRA] Created: (JBDS-1696) seemingly irrelevant warning/error thrown when installing JBDS 4 / 5 on Fedora 12 32-bit - can we suppress that?
by Nick Boldt (JIRA)
seemingly irrelevant warning/error thrown when installing JBDS 4 / 5 on Fedora 12 32-bit - can we suppress that?
----------------------------------------------------------------------------------------------------------------
Key: JBDS-1696
URL: https://issues.jboss.org/browse/JBDS-1696
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: installer
Affects Versions: 4.1.0.CR2, 5.0.0.M2
Reporter: Nick Boldt
Assignee: Denis Golovin
An error like this is thrown EVERY TIME I install JBDS onto Fedora 12 32-bit.
Is this a problem @ my end or something we can fix or at least suppress?
$ java -jar jbdevstudio-product-linux-gtk-5.0.0.v201106180702R-H3-M2.jar
Jun 20, 2011 12:06:03 PM com.sun.corba.se.impl.ior.IORImpl getProfile
WARNING: "IOP00511201: (INV_OBJREF) IOR must have at least one IIOP profile"
org.omg.CORBA.INV_OBJREF: vmcid: SUN minor code: 1201 completed: No
at com.sun.corba.se.impl.logging.IORSystemException.iorMustHaveIiopProfile(IORSystemException.java:473)
at com.sun.corba.se.impl.logging.IORSystemException.iorMustHaveIiopProfile(IORSystemException.java:495)
at com.sun.corba.se.impl.ior.IORImpl.getProfile(IORImpl.java:334)
at com.sun.corba.se.impl.encoding.CDRInputStream_1_0.read_Object(CDRInputStream_1_0.java:787)
at com.sun.corba.se.impl.encoding.CDRInputStream_1_0.read_Object(CDRInputStream_1_0.java:761)
at com.sun.corba.se.impl.encoding.CDRInputStream.read_Object(CDRInputStream.java:231)
at com.sun.corba.se.impl.resolver.INSURLOperationImpl.getIORFromString(INSURLOperationImpl.java:120)
at com.sun.corba.se.impl.resolver.INSURLOperationImpl.operate(INSURLOperationImpl.java:130)
at com.sun.corba.se.impl.orb.ORBImpl.string_to_object(ORBImpl.java:836)
at org.GNOME.Accessibility.AccessUtil.getRegistryObject(AccessUtil.java:143)
at org.GNOME.Accessibility.JavaBridge.registerApplication(JavaBridge.java:1099)
at org.GNOME.Accessibility.JavaBridge.<init>(JavaBridge.java:364)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:532)
at java.lang.Class.newInstance0(Class.java:372)
at java.lang.Class.newInstance(Class.java:325)
at java.awt.Toolkit.loadAssistiveTechnologies(Toolkit.java:786)
at java.awt.Toolkit.getDefaultToolkit(Toolkit.java:875)
at com.jgoodies.looks.LookUtils.isLowResolution(LookUtils.java:480)
at com.jgoodies.looks.LookUtils.<clinit>(LookUtils.java:249)
at com.jgoodies.looks.plastic.PlasticLookAndFeel.<clinit>(PlasticLookAndFeel.java:135)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:264)
at javax.swing.SwingUtilities.loadSystemClass(SwingUtilities.java:1875)
at javax.swing.UIManager.setLookAndFeel(UIManager.java:573)
at com.izforge.izpack.installer.GUIInstaller.loadLookAndFeel(Unknown Source)
at com.izforge.izpack.installer.GUIInstaller.init(Unknown Source)
at com.izforge.izpack.installer.GUIInstaller.<init>(Unknown Source)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:532)
at java.lang.Class.newInstance0(Class.java:372)
at java.lang.Class.newInstance(Class.java:325)
at com.izforge.izpack.installer.Installer.main(Unknown Source)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 6 months
[JBoss JIRA] (JBIDE-12121) The openshift profile is added to newly created maven projects, regardless of their packaging type
by Fred Bricon (JIRA)
Fred Bricon created JBIDE-12121:
-----------------------------------
Summary: The openshift profile is added to newly created maven projects, regardless of their packaging type
Key: JBIDE-12121
URL: https://issues.jboss.org/browse/JBIDE-12121
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 3.3.0.CR1
Reporter: Fred Bricon
Assignee: Andre Dietisheim
Fix For: 3.3.1
I created a project using the org.openarchetypes:multi-javaee6-archetype:0.0.1-SNAPSHOT from http://open-archetypes.github.com/maven-repo/snapshots/archetype-catalog.xml (Maven > Archetypes > Add Remote Catalog)
This creates a multi module project, containing a parent pom, an ear, war, ejb and utility projects. This openshift profile was added to the pom project :
{code:xml}
<profiles>
<profile>
<!-- When built in OpenShift the openshift profile will be used when invoking mvn. -->
<!-- Use this profile for any OpenShift specific customization your app will need. -->
<!-- By default that is to put the resulting archive into the deployments folder. -->
<!-- http://maven.apache.org/guides/mini/guide-building-for-different-environm... -->
<id>openshift</id>
<build>
<finalName>hello</finalName>
<plugins>
<plugin>
<artifactId>maven-war-plugin</artifactId>
<version>2.1.1</version>
<configuration>
<outputDirectory>deployments</outputDirectory>
<warName>ROOT</warName>
</configuration>
</plugin>
</plugins>
</build>
</profile>
{code}
Actually, it should :
- check the packaging type of *all* the generated projects
- if some EARs are found, then add the following to the parent pom (pay attention to the <pluginManagement> section) :
{code:xml}
<profile>
<id>openshift</id>
<build>
<pluginManagement>
<plugins>
<plugin>
<artifactId>maven-ear-plugin</artifactId>
<version>2.7</version>
<configuration>
<outputDirectory>deployments</outputDirectory>
</configuration>
</plugin>
</plugins>
</pluginManagement>
</build>
</profile>
{code}
- if there are no EARs but some WARs are found (count them), then add the following to the parent pom (pay attention to the <pluginManagement> section) :
{code:xml}
<profiles>
<profile>
<id>openshift</id>
<build>
<pluginManagement>
<plugins>
<plugin>
<artifactId>maven-war-plugin</artifactId>
<version>2.2</version>
<configuration>
<outputDirectory>deployments</outputDirectory>
<!-- Add warName ROOT ONLY if there's ONE War, otherwise, skip it -->
<warName>ROOT</warName>
</configuration>
</plugin>
</plugins>
</pluginManagement>
</build>
</profile>
{code}
The finalName is irrelevant to openshift, only the warName counts.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 6 months
[JBoss JIRA] (JBIDE-12098) OpenShift Explorer: Timeout exception when forcing domain deletion
by Stefan Bunciak (JIRA)
Stefan Bunciak created JBIDE-12098:
--------------------------------------
Summary: OpenShift Explorer: Timeout exception when forcing domain deletion
Key: JBIDE-12098
URL: https://issues.jboss.org/browse/JBIDE-12098
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 3.3.0.CR1
Reporter: Stefan Bunciak
Assignee: Andre Dietisheim
Priority: Critical
Fix For: 3.3.0.CR1, 3.3.x
Attachments: deletedomain.png
Tried to force domain deletion while having (medium geared) application on OpenShift.
Screenshot:
!deletedomain.png|thumbnail!
Stack trace:
{code}
com.openshift.client.OpenShiftTimeoutException: Could not request url https://openshift.redhat.com/broker/rest/domains/rhdomain, connection timed out
at com.openshift.internal.client.RestService.request(RestService.java:109)
at com.openshift.internal.client.RestService.request(RestService.java:89)
at com.openshift.internal.client.RestService.request(RestService.java:74)
at com.openshift.internal.client.AbstractOpenShiftResource$ServiceRequest.execute(AbstractOpenShiftResource.java:137)
at com.openshift.internal.client.DomainResource$DeleteDomainRequest.execute(DomainResource.java:329)
at com.openshift.internal.client.DomainResource.destroy(DomainResource.java:166)
at org.jboss.tools.openshift.express.internal.ui.action.DeleteDomainAction$1.run(DeleteDomainAction.java:94)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 6 months