[JBoss JIRA] (JBDS-2394) CLONE - ESB projects cannot be deployed using Server Add/Remove
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-2394?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBDS-2394:
-------------------------------------------
no, JBIDE-13209 does not require a 4.12 to be added to work. JBIDE-13209 is about the esb plugin first, as tools second.
> 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
13 years, 4 months
[JBoss JIRA] (JBIDE-13332) Update list of quickstarts to be consistent with current goals
by Pete Muir (JIRA)
Pete Muir created JBIDE-13332:
---------------------------------
Summary: Update list of quickstarts to be consistent with current goals
Key: JBIDE-13332
URL: https://issues.jboss.org/browse/JBIDE-13332
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: central
Environment: JBDS 6.0
Reporter: Pete Muir
Assignee: Snjezana Peco
We should update the list of quickstarts to be consistent with the things we want to promote right now.
Here is the current list, in this order:
* kitchensink-html5-mobile
* kitchensink
* greeter
* helloworld
* kitchensink-rf
* jax-rs-client
--
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, 4 months
[JBoss JIRA] (JBIDE-13331) Names of quickstarts are wrong
by Pete Muir (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13331?page=com.atlassian.jira.plugi... ]
Pete Muir updated JBIDE-13331:
------------------------------
Issue Type: Bug (was: Feature Request)
> Names of quickstarts are wrong
> ------------------------------
>
> Key: JBIDE-13331
> URL: https://issues.jboss.org/browse/JBIDE-13331
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Environment: JBDS 6.0
> Reporter: Pete Muir
> Assignee: Snjezana Peco
>
> We should use consistent names for quickstarts in all locations, which are governed by the quickstarts themselves:
> * Hello World -> helloworld
> * Hello World JMS -> helloworld-jms
> * Hello World Errai -> helloworld-errai
> * Hello World OSGi -> *remove it entirely*
> * Kitchensink -> kitchensink
> * Number Guess -> numberguess
> * Aerogear HTML5/Mobile -> kitchensink-html5-mobile
> * Greeter -> greeter
--
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, 4 months
[JBoss JIRA] (JBIDE-13331) Names of quickstarts are wrong
by Pete Muir (JIRA)
Pete Muir created JBIDE-13331:
---------------------------------
Summary: Names of quickstarts are wrong
Key: JBIDE-13331
URL: https://issues.jboss.org/browse/JBIDE-13331
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: central
Environment: JBDS 6.0
Reporter: Pete Muir
Assignee: Snjezana Peco
We should use consistent names for quickstarts in all locations, which are governed by the quickstarts themselves:
* Hello World -> helloworld
* Hello World JMS -> helloworld-jms
* Hello World Errai -> helloworld-errai
* Hello World OSGi -> *remove it entirely*
* Kitchensink -> kitchensink
* Number Guess -> numberguess
* Aerogear HTML5/Mobile -> kitchensink-html5-mobile
* Greeter -> greeter
--
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, 4 months
[JBoss JIRA] (JBIDE-13329) should unified.target includes sources?
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13329?page=com.atlassian.jira.plugi... ]
Mickael Istria edited comment on JBIDE-13329 at 12/21/12 3:13 AM:
------------------------------------------------------------------
We see sources in multiple.target because we include some ".sdk" feature. Those should simply be removed from target-platforms.
About the "includeSources=true" in unified, I think it's good to keep it. Although site should not contain sources, in case it does, it's still better if one can see them in IDE.
was (Author: mickael_istria):
We see sources in multiple.target because we include some ".sdk" feature. Those should simply be removed from target-platforms.
> 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
>
> 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, 4 months