[JBoss JIRA] (JBDS-2439) jbdevstudio-unity execution fails when called from different working directory
by Ondrej Skutka (JIRA)
[ https://issues.jboss.org/browse/JBDS-2439?page=com.atlassian.jira.plugin.... ]
Ondrej Skutka commented on JBDS-2439:
-------------------------------------
An easy fix is to replace the {code}./studio/jbdevstudio{code} with {code}$(dirname "$0")/studio/jbdevstudio{code}
> jbdevstudio-unity execution fails when called from different working directory
> ------------------------------------------------------------------------------
>
> Key: JBDS-2439
> URL: https://issues.jboss.org/browse/JBDS-2439
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Affects Versions: 6.0.0.GA
> Reporter: Ondrej Skutka
>
> jbdevstudio-unity script fails with {code}line 17: ./studio/jbdevstudio: No such file or directory{code} when called from a working directory different from jbdevstudio install dir.
> This is caused by relative path in the script (??./studio/jbdevstudio??) introduced by the fix in JBDS-1781.
--
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
11 years, 5 months
[JBoss JIRA] (JBDS-2439) jbdevstudio-unity execution fails when called from different working directory
by Ondrej Skutka (JIRA)
Ondrej Skutka created JBDS-2439:
-----------------------------------
Summary: jbdevstudio-unity execution fails when called from different working directory
Key: JBDS-2439
URL: https://issues.jboss.org/browse/JBDS-2439
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Affects Versions: 6.0.0.GA
Reporter: Ondrej Skutka
jbdevstudio-unity script fails with {code}line 17: ./studio/jbdevstudio: No such file or directory{code} when called from a working directory different from jbdevstudio install dir.
This is caused by relative path in the script (??./studio/jbdevstudio??) introduced by the fix in JBDS-1781.
--
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
11 years, 5 months
[JBoss JIRA] (JBIDE-13076) Marker Resolution Generators should check if IMarker exists
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13076?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-13076:
----------------------------------------
Pushed the new PR to master
> Marker Resolution Generators should check if IMarker exists
> ------------------------------------------------------------
>
> Key: JBIDE-13076
> URL: https://issues.jboss.org/browse/JBIDE-13076
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: CDI, central, common/jst/core, JSF, Seam 2
> Affects Versions: 4.0.0.Beta2
> Environment: Ubuntu, jbdevstudio-product-eap-universal-6.0.0.Beta2-v20121107-1854-B62.jar
> Reporter: Daniel Azarov
> Assignee: Daniel Azarov
> Fix For: 4.1.0.Alpha1
>
>
> When Marker Resolution Generator tries to find quick fixes for Problem Marker marker may not be exist any more. In that case we can get follow Exception:
> {code}
> org.eclipse.core.internal.resources.ResourceException: Marker id 5 not found.
> at org.eclipse.core.internal.resources.Marker.checkInfo(Marker.java:57)
> at org.eclipse.core.internal.resources.Marker.getType(Marker.java:195)
> at org.jboss.tools.common.ui.marker.ConfigureProblemSeverityResolutionGenerator.getProblemType(ConfigureProblemSeverityResolutionGenerator.java:140)
> at org.jboss.tools.common.ui.marker.ConfigureProblemSeverityResolutionGenerator.hasResolutions(ConfigureProblemSeverityResolutionGenerator.java:124)
> at org.eclipse.ui.internal.ide.registry.MarkerHelpRegistry.hasResolution(MarkerHelpRegistry.java:191)
> at org.eclipse.ui.internal.ide.registry.MarkerHelpRegistry.hasResolutions(MarkerHelpRegistry.java:160)
> at org.eclipse.ui.views.markers.MarkerField.annotateImage(MarkerField.java:76)
> at org.eclipse.ui.internal.views.markers.MarkerProblemSeverityAndMessageField.update(MarkerProblemSeverityAndMessageField.java:86)
> at org.eclipse.ui.internal.views.markers.MarkerColumnLabelProvider.update(MarkerColumnLabelProvider.java:62)
> at org.eclipse.jface.viewers.ViewerColumn.refresh(ViewerColumn.java:152)
> at org.eclipse.jface.viewers.AbstractTreeViewer.doUpdateItem(AbstractTreeViewer.java:953)
> at org.eclipse.ui.internal.views.markers.MarkersTreeViewer.doUpdateItem(MarkersTreeViewer.java:73)
> at org.eclipse.jface.viewers.AbstractTreeViewer$UpdateItemSafeRunnable.run(AbstractTreeViewer.java:113)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49)
> at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175)
> at org.eclipse.jface.viewers.AbstractTreeViewer.doUpdateItem(AbstractTreeViewer.java:1033)
> at org.eclipse.jface.viewers.StructuredViewer$UpdateItemSafeRunnable.run(StructuredViewer.java:485)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49)
> at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175)
> at org.eclipse.jface.viewers.StructuredViewer.updateItem(StructuredViewer.java:2167)
> at org.eclipse.jface.viewers.AbstractTreeViewer.updateChildren(AbstractTreeViewer.java:2753)
> at org.eclipse.jface.viewers.AbstractTreeViewer.internalRefreshStruct(AbstractTreeViewer.java:1923)
> at org.eclipse.jface.viewers.TreeViewer.internalRefreshStruct(TreeViewer.java:721)
> at org.eclipse.jface.viewers.AbstractTreeViewer.internalRefreshStruct(AbstractTreeViewer.java:1930)
> at org.eclipse.jface.viewers.TreeViewer.internalRefreshStruct(TreeViewer.java:721)
> at org.eclipse.jface.viewers.AbstractTreeViewer.internalRefresh(AbstractTreeViewer.java:1898)
> at org.eclipse.jface.viewers.AbstractTreeViewer.internalRefresh(AbstractTreeViewer.java:1855)
> at org.eclipse.jface.viewers.StructuredViewer$8.run(StructuredViewer.java:1535)
> at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1443)
> at org.eclipse.jface.viewers.TreeViewer.preservingSelection(TreeViewer.java:403)
> at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1404)
> at org.eclipse.jface.viewers.StructuredViewer.refresh(StructuredViewer.java:1533)
> at org.eclipse.jface.viewers.ColumnViewer.refresh(ColumnViewer.java:548)
> at org.eclipse.jface.viewers.StructuredViewer.refresh(StructuredViewer.java:1490)
> at org.eclipse.ui.internal.views.markers.UIUpdateJob.runInUIThread(UIUpdateJob.java:108)
> at org.eclipse.ui.progress.UIJob$1.run(UIJob.java:95)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3529)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3182)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1029)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:923)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:86)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:588)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:543)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:353)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180)
> 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:601)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:629)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1438)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1414)
> {code}
> I saw such exceptions only when I was working in Visual Page Editor.
> May by this is WTP related issue.
> So lets add check IMarker.exists() to hasResolutions(IMarker) methods to all our Marker Resolution Generators which work with jsp, xhtml and xml files:
> *jbosstools-javaee*
> 1. org.jboss.tools.cdi.ui.marker.CDIProblemMarkerResolutionGenerator
> 2. org.jboss.tools.seam.ui.marker.SeamProblemMarkerResolutionGenerator
> 3. org.jboss.tools.jsf.ui.marker.DisableFaceletHTMLValidatorResolutionGenerator
> 4. org.jboss.tools.jsf.web.validation.jsf2.action.JSF2ComponentResolutionGenerator
> *jbosstools-jst*
> 1. org.jboss.tools.jst.web.ui.action.JSPProblemMarkerResolutionGenerator
> *jbosstools-base*
> 1. org.jboss.tools.common.ui.marker.ConfigureProblemSeverityResolutionGenerator
--
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
11 years, 5 months
[JBoss JIRA] (JBIDE-9719) Deploys Teiid artifacts to deploy folder configured in JBDS
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/JBIDE-9719?page=com.atlassian.jira.plugin... ]
Barry LaFond commented on JBIDE-9719:
-------------------------------------
For Designer 8.0 we implemented the changes necessary to maintain current feature set. This includes deploying VDB's and creating Data Sources through Teiid's API. VDB's get deployed as "metadata", not as standard artifacts. For Data Sources, Teiid utilizes AS7 functionality and Designer will deploy the connection profile jars to the appropriate server folder.
> Deploys Teiid artifacts to deploy folder configured in JBDS
> -----------------------------------------------------------
>
> Key: JBIDE-9719
> URL: https://issues.jboss.org/browse/JBIDE-9719
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: teiid
> Reporter: Joao Viragine
> Assignee: Barry LaFond
> Fix For: 4.0.0.Alpha1-SOA
>
>
> When we deploy Teiid artifacts (like Datasources, VDB), JBDS *always* deploys the artifacts to JBoss deploy folder. It should use deploy folder configured in JBDS.
--
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
11 years, 5 months
[JBoss JIRA] (JBIDE-13232) refactor target platforms' GAVs, names, labels (was target platforms has the same name)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13232?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-13232 at 1/2/13 10:38 AM:
-------------------------------------------------------------
(Edited by Max to have the repo path only show the relevant parts)
Here's my proposal:
{quote}
* *Path:*
*JBT 4.0 (current):*
{code}
jbosstools-build/target-platforms/
jbdevstudio-{4.2.0.c,4.2.1.a}/
jbosstools-{4.2.0.c,4.2.1.a}/
pom.xml
multiple/pom.xml
multiple/multiple.target
unified/pom.xml
{code}
*JBT 4.1 (proposed):*
{code}
jbosstools-build/target-platforms/
{minimum,maximum}/
pom.xml
jbosstools-tp-with-sources/pom.xml
jbosstools-tp-with-sources/jbosstools-tp-with-sources.target
jbosstools-tp-no-sources/pom.xml
jbdevstudio-tp-with-sources/pom.xml
jbdevstudio-tp-with-sources/jbdevstudio-tp-with-sources.target
jbdevstudio-tp-no-sources/pom.xml
{code}
* *Pom version:*
*JBT 4.0 (current):*
{code}
root: 4.1.0.Alpha1-SNAPSHOT (used to be tied to parent pom version, then later just the same version)
minimums: 4.2.0-SNAPSHOT, 4.2.0.a-SNAPSHOT, 4.2.0.b-SNAPSHOT, 4.2.0.c-SNAPSHOT
maximums: 4.2.1.a-SNAPSHOT, 4.2.1-SNAPSHOT
{code}
*JBT 4.1 (proposed):*
{code}
root: 4.1.0-SNAPSHOT (not published, shouldn't have to increment it unless testing new version of Tycho or adding new profiles?)
minimum: 1.430.0, 1.430.1, ... (note that SNAPSHOT is dropped)
maximum (after July release): 1.431.0, 1.431.1, ... (note that SNAPSHOT is dropped)
{code}
* *Pom Params:*
*JBT 4.0 (current):*
{code}
<name>jbosstools Multiple (Composite) Target Platform 4.2.1.a</name>
<groupId>org.jboss.tools.target-platforms.jbosstools</groupId>
<artifactId>multiple</artifactId>
<version>4.2.1.a-SNAPSHOT</version>
<name>jbosstools Unified (Aggregate) Target Platform 4.2.1.a</name>
<groupId>org.jboss.tools.target-platforms.jbosstools</groupId>
<artifactId>unified</artifactId>
<version>4.2.1.a-SNAPSHOT</version>
{code}
*JBT 4.1 (proposed):*
{code}
<name>JBoss Tools Target Platform - Multiple URLs With Sources</name>
<groupId>org.jboss.tools.target-platforms</groupId> (drops the ".jbosstools" segment)
<artifactId>jbosstools-tp-with-sources</artifactId>
<version>1.430.0-SNAPSHOT</version> (**MODIFIED 2013-01-02: -SNAPSHOT gets dropped only when we're satisfied and want to *RELEASE* it)
<name>JBoss Tools Target Platform - Unified URL Without Sources</name>
<groupId>org.jboss.tools.target-platforms</groupId> (drops the ".jbosstools" segment)
<artifactId>jbosstools-tp-no-sources</artifactId>
<version>1.430.0-SNAPSHOT</version> (**MODIFIED 2013-01-02: -SNAPSHOT gets dropped only when we're satisfied and want to *RELEASE* it)
{code}
* *.target file name attribute:*
*JBT 4.0 (current):*
{code}
<target name="jbosstools-4.2.1.a">
<target name="jbdevstudio-4.2.1.a">
{code}
*JBT 4.1 (proposed):*
{code}
<target name="jbosstools-tp-with-sources-1.430.0">
<target name="jbdevstudio-tp-with-sources-1.430.0">
{code}
* *Maven/POM Path:*
*JBT 4.0 (current):*
{code}
<snapshot-repo>/org/jboss/tools/target-platforms/jbosstools/multiple/4.2.0.c-SNAPSHOT/
<snapshot-repo>/org/jboss/tools/target-platforms/jbosstools/unified/4.2.0.c-SNAPSHOT/
<snapshot-repo>/org/jboss/tools/target-platforms/jbosstools/multiple/4.2.1.a-SNAPSHOT/
<snapshot-repo>/org/jboss/tools/target-platforms/jbosstools/unified/4.2.1.a-SNAPSHOT/
{code}
*JBT 4.1 (proposed):*
{code}
(**MODIFIED 2013-01-02: -SNAPSHOT gets dropped only when we're satisfied and want to *RELEASE* it)
<snapshot-repo>/org/jboss/tools/target-platforms/jbosstools-tp-with-sources/1.430.0-SNAPSHOT
<snapshot-repo>/org/jboss/tools/target-platforms/jbosstools-tp-no-sources/1.430.0-SNAPSHOT
<snapshot-repo>/org/jboss/tools/target-platforms/jbosstools-tp-with-sources/1.431.0-SNAPSHOT
<snapshot-repo>/org/jboss/tools/target-platforms/jbosstools-tp-no-sources/1.431.0-SNAPSHOT
(**MODIFIED 2013-01-02: then later when we want to release it, -SNAPSHOT gets dropped)
<release-repo>/org/jboss/tools/target-platforms/jbosstools-tp-with-sources/1.430.0
<release-repo>/org/jboss/tools/target-platforms/jbosstools-tp-no-sources/1.430.0
<release-repo>/org/jboss/tools/target-platforms/jbosstools-tp-with-sources/1.431.0
<release-repo>/org/jboss/tools/target-platforms/jbosstools-tp-no-sources/1.431.0
{code}
{quote}
was (Author: nickboldt):
(Edited by Max to have the repo path only show the relevant parts)
Here's my proposal:
{quote}
* *Path:*
*JBT 4.0 (current):*
{code}
jbosstools-build/target-platforms/
jbdevstudio-{4.2.0.c,4.2.1.a}/
jbosstools-{4.2.0.c,4.2.1.a}/
pom.xml
multiple/pom.xml
multiple/multiple.target
unified/pom.xml
{code}
*JBT 4.1 (proposed):*
{code}
jbosstools-build/target-platforms/
{minimum,maximum}/
pom.xml
jbosstools-tp-with-sources/pom.xml
jbosstools-tp-with-sources/jbosstools-tp-with-sources.target
jbosstools-tp-no-sources/pom.xml
jbdevstudio-tp-with-sources/pom.xml
jbdevstudio-tp-with-sources/jbdevstudio-tp-with-sources.target
jbdevstudio-tp-no-sources/pom.xml
{code}
* *Pom version:*
*JBT 4.0 (current):*
{code}
root: 4.1.0.Alpha1-SNAPSHOT (used to be tied to parent pom version, then later just the same version)
minimums: 4.2.0-SNAPSHOT, 4.2.0.a-SNAPSHOT, 4.2.0.b-SNAPSHOT, 4.2.0.c-SNAPSHOT
maximums: 4.2.1.a-SNAPSHOT, 4.2.1-SNAPSHOT
{code}
*JBT 4.1 (proposed):*
{code}
root: 4.1.0-SNAPSHOT (not published, shouldn't have to increment it unless testing new version of Tycho or adding new profiles?)
minimum: 1.430.0, 1.430.1, ... (note that SNAPSHOT is dropped)
maximum (after July release): 1.431.0, 1.431.1, ... (note that SNAPSHOT is dropped)
{code}
* *Pom Params:*
*JBT 4.0 (current):*
{code}
<name>jbosstools Multiple (Composite) Target Platform 4.2.1.a</name>
<groupId>org.jboss.tools.target-platforms.jbosstools</groupId>
<artifactId>multiple</artifactId>
<version>4.2.1.a-SNAPSHOT</version>
<name>jbosstools Unified (Aggregate) Target Platform 4.2.1.a</name>
<groupId>org.jboss.tools.target-platforms.jbosstools</groupId>
<artifactId>unified</artifactId>
<version>4.2.1.a-SNAPSHOT</version>
{code}
*JBT 4.1 (proposed):*
{code}
<name>JBoss Tools Target Platform - Multiple URLs With Sources</name>
<groupId>org.jboss.tools.target-platforms</groupId> (drops the ".jbosstools" segment)
<artifactId>jbosstools-tp-with-sources</artifactId>
<version>1.430.0</version>
<name>JBoss Tools Target Platform - Unified URL Without Sources</name>
<groupId>org.jboss.tools.target-platforms</groupId> (drops the ".jbosstools" segment)
<artifactId>jbosstools-tp-no-sources</artifactId>
<version>1.430.0</version>
{code}
* *.target file name attribute:*
*JBT 4.0 (current):*
{code}
<target name="jbosstools-4.2.1.a">
<target name="jbdevstudio-4.2.1.a">
{code}
*JBT 4.1 (proposed):*
{code}
<target name="jbosstools-tp-with-sources-1.430.0">
<target name="jbdevstudio-tp-with-sources-1.430.0">
{code}
* *Maven/POM Path:*
*JBT 4.0 (current):*
{code}
<snapshot-repo>/org/jboss/tools/target-platforms/jbosstools/multiple/4.2.0.c-SNAPSHOT/
<snapshot-repo>/org/jboss/tools/target-platforms/jbosstools/unified/4.2.0.c-SNAPSHOT/
<snapshot-repo>/org/jboss/tools/target-platforms/jbosstools/multiple/4.2.1.a-SNAPSHOT/
<snapshot-repo>/org/jboss/tools/target-platforms/jbosstools/unified/4.2.1.a-SNAPSHOT/
{code}
*JBT 4.1 (proposed):*
{code}
<release-repo>/org/jboss/tools/target-platforms/jbosstools-tp-with-sources/1.430.0
<release-repo>/org/jboss/tools/target-platforms/jbosstools-tp-no-sources/1.430.0
<release-repo>/org/jboss/tools/target-platforms/jbosstools-tp-with-sources/1.431.0
<release-repo>/org/jboss/tools/target-platforms/jbosstools-tp-no-sources/1.431.0
{code}
{quote}
> refactor target platforms' GAVs, names, labels (was target platforms has the same name)
> ---------------------------------------------------------------------------------------
>
> Key: JBIDE-13232
> URL: https://issues.jboss.org/browse/JBIDE-13232
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Build/Releng
> Affects Versions: 4.1.0.Alpha1
> Environment:
> Reporter: Max Rydahl Andersen
> Assignee: Mickael Istria
> Fix For: 4.1.0.Alpha1
>
>
> .target files are all called "e42-wtp34-jbds6" even though they are for jbosstools and not specific to jbds6 either.
> Makes it hard to actually see which target platform to choose
--
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
11 years, 5 months
[JBoss JIRA] (JBDS-2394) CLONE - ESB projects cannot be deployed using Server Add/Remove
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBDS-2394?page=com.atlassian.jira.plugin.... ]
Len DiMaggio commented on JBDS-2394:
------------------------------------
Max - I don't understand your comment from December 21 - we DO want this fix in so that we can support both SOA-P 5.3 and any future SOA releases that include newer versions of JBoss ESB.
> CLONE - ESB projects cannot be deployed using Server Add/Remove
> ---------------------------------------------------------------
>
> Key: JBDS-2394
> URL: https://issues.jboss.org/browse/JBDS-2394
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: SOA Tooling / Platform
> Affects Versions: 5.0.0.GA-SOA
> Environment: Fedora, jdk7
> Reporter: Rob Stryker
> Assignee: Nick Boldt
> Priority: Critical
> Fix For: 5.0.2.GA
>
> Attachments: JBDS2394-add-4.12.patch.txt, JBDS2394.patch-with-5-lines-changed-in-plugin.xml-and-all-feature-and-plugin-manifests-and-poms-upversioned-to-2.3.2.txt, JBDS2394.patch.txt
>
>
> * Create a new server runtime for SOA-P 5.3
> -- Preferences -> Server -> Runtime Environments
> * Create a new ESB project with the defaults
> * Right click the server and chosse "Add and Remove" and the project cannot be added. Error message is, "The server does not support version 4.11 of the JBoss ESB Module specification.
> The project can be deployed after right clicking and choosing "Mark as deployable," but it can never be added using "Add and Remove."
--
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
11 years, 5 months