[JBoss JIRA] (JBDS-2442) Cannot start a SOA-P 5.2 or EAP 5.1.2 server from JBDS 5.0.2
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBDS-2442?page=com.atlassian.jira.plugin.... ]
Len DiMaggio updated JBDS-2442:
-------------------------------
Attachment: Screenshot-1.png
> Cannot start a SOA-P 5.2 or EAP 5.1.2 server from JBDS 5.0.2
> ------------------------------------------------------------
>
> Key: JBDS-2442
> URL: https://issues.jboss.org/browse/JBDS-2442
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: servers
> Affects Versions: 5.0.2.GA
> Environment: Version: 5.0.2.GA
> Build id: v20130103-0154-H238-GA
> Build date: 20130103-0154
> SOA-P 5.2.GA
> Reporter: Len DiMaggio
> Assignee: Rob Stryker
> Priority: Blocker
> Labels: respin-b
> Fix For: 5.0.2.GA
>
> Attachments: Screenshot-1.png
>
>
> This is a regression relative to JBDS 5.0.1
> When a SOA-P 5.2 server is started in JBDS 5.0.2 - this exception is raised:
> Exception in thread "main" java.lang.NoClassDefFoundError: org/jboss/bootstrap/BaseServerConfig
> at org.jboss.bootstrap.AbstractServerImpl.doInit(AbstractServerImpl.java:190)
> at org.jboss.bootstrap.AbstractServerImpl.init(AbstractServerImpl.java:173)
> at org.jboss.bootstrap.AbstractServerImpl.init(AbstractServerImpl.java:143)
> at org.jboss.Main.boot(Main.java:218)
> at org.jboss.Main$1.run(Main.java:556)
> at java.lang.Thread.run(Thread.java:722)
> Caused by: java.lang.ClassNotFoundException: org.jboss.bootstrap.BaseServerConfig
> at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:423)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:356)
> ... 6 more
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 months
[JBoss JIRA] (JBIDE-13347) Add deltaspike jars into nexus repository (releases/snapshots)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13347?page=com.atlassian.jira.plugi... ]
Nick Boldt closed JBIDE-13347.
------------------------------
Fix Version/s: 4.1.0.Alpha1
Resolution: Done
That's also how we resolve Nexus in JBT builds except it's added via the parent pom, not via an individual pom.xml. Settings.xml only provides <mirrors> to resolve p2 deps, not m2 ones.
Closing as Jaroslav says he solved his problem.
> Add deltaspike jars into nexus repository (releases/snapshots)
> --------------------------------------------------------------
>
> Key: JBIDE-13347
> URL: https://issues.jboss.org/browse/JBIDE-13347
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: UpStream
> Reporter: Jaroslav Jankovič
> Assignee: Mickael Istria
> Fix For: 4.1.0.Alpha1
>
>
> Now, deltaspike libraries are not in jboss nexus repositories defined in our shared settins.xml (releases/snapshots). They are part of central jboss nexus repo but this one is not used when building swtbot tests.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 months
[JBoss JIRA] (JBDS-2442) Cannot start a SOA-P 5.2 or EAP 5.1.2 server from JBDS 5.0.2
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBDS-2442?page=com.atlassian.jira.plugin.... ]
Len DiMaggio updated JBDS-2442:
-------------------------------
Summary: Cannot start a SOA-P 5.2 or EAP 5.1.2 server from JBDS 5.0.2 (was: Cannot start a SOA-P 5.2 server from JBDS 5.0.2)
> Cannot start a SOA-P 5.2 or EAP 5.1.2 server from JBDS 5.0.2
> ------------------------------------------------------------
>
> Key: JBDS-2442
> URL: https://issues.jboss.org/browse/JBDS-2442
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: servers
> Affects Versions: 5.0.2.GA
> Environment: Version: 5.0.2.GA
> Build id: v20130103-0154-H238-GA
> Build date: 20130103-0154
> SOA-P 5.2.GA
> Reporter: Len DiMaggio
> Assignee: Rob Stryker
> Priority: Blocker
> Labels: respin-b
> Fix For: 5.0.2.GA
>
>
> This is a regression relative to JBDS 5.0.1
> When a SOA-P 5.2 server is started in JBDS 5.0.2 - this exception is raised:
> Exception in thread "main" java.lang.NoClassDefFoundError: org/jboss/bootstrap/BaseServerConfig
> at org.jboss.bootstrap.AbstractServerImpl.doInit(AbstractServerImpl.java:190)
> at org.jboss.bootstrap.AbstractServerImpl.init(AbstractServerImpl.java:173)
> at org.jboss.bootstrap.AbstractServerImpl.init(AbstractServerImpl.java:143)
> at org.jboss.Main.boot(Main.java:218)
> at org.jboss.Main$1.run(Main.java:556)
> at java.lang.Thread.run(Thread.java:722)
> Caused by: java.lang.ClassNotFoundException: org.jboss.bootstrap.BaseServerConfig
> at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:423)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:356)
> ... 6 more
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 months
[JBoss JIRA] (JBIDE-13329) should unified.target includes sources?
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13329?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-13329 at 1/10/13 2:50 PM:
-------------------------------------------------------------
Should not remove sdkbundle as jbt gwt stuff requires it. Could include the plugin if you want to omit the feature, I suppose.
{code}
** [1] ./plugins/org.jboss.tools.gwt.core/META-INF/MANIFEST.MF **
9- org.jboss.tools.common;bundle-version="[3.2.0,4.0.0)",
10- com.google.gwt.eclipse.core,
11: com.google.gwt.eclipse.sdkbundle;bundle-version="[2.4.0,3.0.0)",
12- com.google.gdt.eclipse.suite;bundle-version="3.0.1",
13- org.eclipse.core.runtime;bundle-version="[3.5.0,4.0.0)",
** [2] ./plugins/org.jboss.tools.gwt.core/src/org/jboss/tools/gwt/core/IGoogleEclipsePluginConstants.java **
57- public static final String WELCOME_FILE = "Gwt_jboss.html"; //$NON-NLS-1$
58-
59: public static final String GWT_SDK_BUNDLENAME = "com.google.gwt.eclipse.sdkbundle"; //$NON-NLS-1$
60-
61- public static final String GWT_SERVLET_NAME = "gwt-servlet.jar"; //$NON-NLS-1$
{code}
Also, should these changes be applied against the 40x branch instead of master? I would expect master to include a TP for 4.3.0.M4, not 4.2.0/4.2.1.
was (Author: nickboldt):
Should not remove sdkbundle as jbt gwt stuff requires it. Could include the plugin if you want to omit the feature, I suppose.
{code}
** [1] ./plugins/org.jboss.tools.gwt.core/META-INF/MANIFEST.MF **
9- org.jboss.tools.common;bundle-version="[3.2.0,4.0.0)",
10- com.google.gwt.eclipse.core,
11: com.google.gwt.eclipse.sdkbundle;bundle-version="[2.4.0,3.0.0)",
12- com.google.gdt.eclipse.suite;bundle-version="3.0.1",
13- org.eclipse.core.runtime;bundle-version="[3.5.0,4.0.0)",
** [2] ./plugins/org.jboss.tools.gwt.core/src/org/jboss/tools/gwt/core/IGoogleEclipsePluginConstants.java **
57- public static final String WELCOME_FILE = "Gwt_jboss.html"; //$NON-NLS-1$
58-
59: public static final String GWT_SDK_BUNDLENAME = "com.google.gwt.eclipse.sdkbundle"; //$NON-NLS-1$
60-
61- public static final String GWT_SERVLET_NAME = "gwt-servlet.jar"; //$NON-NLS-1$
{code}
> should unified.target includes sources?
> ---------------------------------------
>
> Key: JBIDE-13329
> URL: https://issues.jboss.org/browse/JBIDE-13329
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform
> Affects Versions: 4.0.0.Final
> Reporter: Nick Boldt
> Assignee: Mickael Istria
> Fix For: 4.1.0.Alpha1
>
>
> I was under the impression that the generated multiple.target would include source features, while the generated unified.target would not.
> However:
> {code}
> unified-4.2.1.a-20121220.173723-14-unified.target:
> <location includeAllPlatforms="false" includeMode="planner" includeSource="true" type="InstallableUnit">
> multiple-4.2.1.a-20121220.173233-14-multiple.target:
> <location includeAllPlatforms="false" includeMode="planner" type="InstallableUnit" includeSource="true">
> {code}
> And the generated update site for 4.2.1.a (SR1a) target platform contains many feature.source bundles:
> http://download.jboss.org/jbosstools/updates/juno/SR1a/REPO/features/
> Is this intentional? Or is there a bug in your flatten mojo?
> https://github.com/jbosstools/jbosstools-maven-plugins/blob/master/tycho-...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 months
[JBoss JIRA] (JBIDE-12847) VPE throws StackOverflowError and visual part is blank
by Yahor Radtsevich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12847?page=com.atlassian.jira.plugi... ]
Yahor Radtsevich edited comment on JBIDE-12847 at 1/10/13 2:47 PM:
-------------------------------------------------------------------
Denis, please approve [^JBIDE-12847.diff] to be applied in jbosstools-3.3.x SVN branch. Among the changes you linked above, it also contains a JUnit test.
I tested it localy - everything seems to be fine.
was (Author: yradtsevich):
Denis, please approve [^JBIDE-12847.diff] to be applied in jbosstools-3.3.x SVN branch. Among the changed you linked it also contains a JUnit test.
I tested it localy - everything seems to be fine.
> VPE throws StackOverflowError and visual part is blank
> ------------------------------------------------------
>
> Key: JBIDE-12847
> URL: https://issues.jboss.org/browse/JBIDE-12847
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Visual Page Editor core
> Reporter: Yahor Radtsevich
> Assignee: Yahor Radtsevich
> Labels: respin-b
> Fix For: 3.3.2
>
> Attachments: JBIDE-12847.diff, screenshot.png
>
>
> # Create new RichFaces project from JBoss Central View
> # Open richfaces-webapp/src/main/webapp/WEB-INF/templates/mobile.xhtml in VPE
> *Result:*
> VPE is blank:
> !screenshot.png|thumbnail!
> {code}
> java.lang.StackOverflowError
> at java.util.regex.Pattern$GroupHead.match(Pattern.java:4556)
> at java.util.regex.Pattern$Loop.match(Pattern.java:4683)
> at java.util.regex.Pattern$GroupTail.match(Pattern.java:4615)
> at java.util.regex.Pattern$BranchConn.match(Pattern.java:4466)
> at java.util.regex.Pattern$CharProperty.match(Pattern.java:3694)
> at java.util.regex.Pattern$Branch.match(Pattern.java:4502)
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 months
[JBoss JIRA] (JBIDE-13351) Dialogs look and fill problems
by Daniel Azarov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13351?page=com.atlassian.jira.plugi... ]
Daniel Azarov updated JBIDE-13351:
----------------------------------
Description:
Follow
1. New->Other->JBoss Tools->Configure MavenRepositories
ConfigureMavenRepositoriesWizard.java
Wizard banner has wrong high less than 66 pixels
!ConfigureMavenRepositories.png!
2. Window->Preferences, JBoss Tools->Remote Repositories, button "Add..."
EditNexusRepositoryDialog.java
Dialog should have a banner:
!NewRepositoryDialog.png!
3. Window->Preferences, JBoss Tools->JBoss Maven Integration, button "Configure Maven Repositories"
Dialog should have a not empty banner:
!ConfigureMavenRepositories2.png!
4. Window->Preferences, JBoss Tools->JBoss ESB Runtimes, button "Add". BTW it should be "Add..."
Dialog should have a not empty banner:
!NewJBossESBRuntime.png!
5.Window->Preferences, JBoss Tools->JBoss Runtime Detection, button "Download..."
Dialog should have a not empty banner:
!DownloadRuntimes.png!
6. Window->Preferences, JBoss Tools->Web->Custom Capabilities, buttons "Add" (button should be "Add...")
Dialogs should have a not default bunner:
!AddCapability.png!
!AddLibraryReference.png!
7. Window->Preferences, JBoss Tools->Web->Editors->Visual Page Editor, tab Visual Templates, buttons "Add..." and "Import..."
Dialogs should have a not default bunner:
!UserSpecifiedTagTemplate.png!
!ImportUserSpecifiedTagTemplates.png!
8. Window->Preferences, JBoss Tools->Web->Expression Language->Variables, buttons "Add" (button should be "Add...")
Dialog should have a not default bunner:
!AddELReferences.png!
was:
Follow
1. New->Other->JBoss Tools->Configure MavenRepositories
ConfigureMavenRepositoriesWizard.java
Wizard banner has wrong high less than 66 pixels
!ConfigureMavenRepositories.png!
2. Window->Preferences, JBoss Tools->Remote Repositories, button "Add..."
EditNexusRepositoryDialog.java
Dialog should have a banner:
!NewRepositoryDialog.png!
3. Window->Preferences, JBoss Tools->JBoss Maven Integration, button "Configure Maven Repositories"
Dialog should have a not empty banner:
!ConfigureMavenRepositories2.png!
4. Window->Preferences, JBoss Tools->JBoss ESB Runtimes, button "Add". BTW it should be "Add..."
Dialog should have a not empty banner:
!NewJBossESBRuntime.png!
5.Window->Preferences, JBoss Tools->JBoss Runtime Detection, button "Download..."
Dialog should have a not empty banner:
!DownloadRuntimes.png!
6. Window->Preferences, JBoss Tools->Web->Custom Capabilities, buttons "Add" (button should be "Add...")
Dialogs should have a not default bunner:
!AddCapability.png!
!AddLibraryReference.png!
7. Window->Preferences, JBoss Tools->Web->Editors->Visual Page Editor, tab Visual Templates, buttons "Add..." and "Import..."
Dialogs should have a not default bunner:
!UserSpecifiedTagTemplate.png!
!ImportUserSpecifiedTagTemplates.png!
> Dialogs look and fill problems
> ------------------------------
>
> Key: JBIDE-13351
> URL: https://issues.jboss.org/browse/JBIDE-13351
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JSF, runtime-detection, Seam 2, Visual Page Editor Templates
> Affects Versions: 4.1.0.Alpha1
> Reporter: Daniel Azarov
> Assignee: Daniel Azarov
> Priority: Trivial
> Fix For: 4.1.x
>
> Attachments: AddCapability.png, AddELReeference.png, ADDJBossToolsRuntimeDialog.png, AddLibraryReference.png, BrowseFontDialog.png, ConfigureMavenRepositories.png, ConfigureMavenRepositories2.png, DownloadRuntimes.png, EditServletClassDialog.png, EditTLDFilesDialog.png, ImportUserSpecifiedTagTemplates.png, NewJBossESBRuntime.png, NewRepositoryDialog.png, NewTemplateDialog.png, UserSpecifiedTagTemplate.png
>
>
> Follow
> 1. New->Other->JBoss Tools->Configure MavenRepositories
> ConfigureMavenRepositoriesWizard.java
> Wizard banner has wrong high less than 66 pixels
> !ConfigureMavenRepositories.png!
> 2. Window->Preferences, JBoss Tools->Remote Repositories, button "Add..."
> EditNexusRepositoryDialog.java
> Dialog should have a banner:
> !NewRepositoryDialog.png!
> 3. Window->Preferences, JBoss Tools->JBoss Maven Integration, button "Configure Maven Repositories"
> Dialog should have a not empty banner:
> !ConfigureMavenRepositories2.png!
> 4. Window->Preferences, JBoss Tools->JBoss ESB Runtimes, button "Add". BTW it should be "Add..."
> Dialog should have a not empty banner:
> !NewJBossESBRuntime.png!
> 5.Window->Preferences, JBoss Tools->JBoss Runtime Detection, button "Download..."
> Dialog should have a not empty banner:
> !DownloadRuntimes.png!
> 6. Window->Preferences, JBoss Tools->Web->Custom Capabilities, buttons "Add" (button should be "Add...")
> Dialogs should have a not default bunner:
> !AddCapability.png!
> !AddLibraryReference.png!
> 7. Window->Preferences, JBoss Tools->Web->Editors->Visual Page Editor, tab Visual Templates, buttons "Add..." and "Import..."
> Dialogs should have a not default bunner:
> !UserSpecifiedTagTemplate.png!
> !ImportUserSpecifiedTagTemplates.png!
> 8. Window->Preferences, JBoss Tools->Web->Expression Language->Variables, buttons "Add" (button should be "Add...")
> Dialog should have a not default bunner:
> !AddELReferences.png!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 months