[JBoss JIRA] (JBIDE-15250) Explode utility jars in EAR/WAR deployments
by Kevin Formsma (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15250?page=com.atlassian.jira.plugi... ]
Kevin Formsma commented on JBIDE-15250:
---------------------------------------
First, apologies for the slow response.
We are not copying the jar's into the ear project. In the EAR deployment assembly, we have these jars being deployed to the standard lib folder. Other projects can then reference these using their EAR Libraries classpath entries. However, when the ear is deployed, the jars are not exploded in the lib folder - so we don't get any incremental updates to the utility projects.
> Explode utility jars in EAR/WAR deployments
> -------------------------------------------
>
> Key: JBIDE-15250
> URL: https://issues.jboss.org/browse/JBIDE-15250
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: server
> Affects Versions: 4.0.1.Final
> Reporter: Kevin Formsma
>
> For larger projects that utilize utility jars within the EAR, it would be nice to have these deployed exploded as well. This would allow hot code replacement for those utility projects.
> A current work around is to make the utility projects modules so that the tooling treats them as a EJB module and deploys them exploded.
--
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
12 years, 7 months
[JBoss JIRA] (JBDS-2734) Forge 2 in JBDS
by Lincoln Baxter III (JIRA)
[ https://issues.jboss.org/browse/JBDS-2734?page=com.atlassian.jira.plugin.... ]
Lincoln Baxter III commented on JBDS-2734:
------------------------------------------
Hey Michelle,
That sounds good. Here is what we are planning to provide from a functionality point-of-view:
* Edit Addons
-- Install Addons
-- Remove Addons
-- Build and Install an Addon
* Create a new project with Forge 2 wizard.
-- Maven Java
-- Maven Resources
-- Maven Forge Addon
* Java EE
-- Setup CDI
-- Setup REST
-- Setup JPA
* New Entity
* New Field
-- Setup EJB
-- Setup JSF
-- Setup Servlet
* Reverse Engineer Database
-- Creates JPA entities in existing Project or Folder
* Scaffold
-- Setup
-- From JPA Entities
*** Our BHAG is a Multi-step Wizard that will Step the User through creating a new project, reverse engineering a database, setting up necessary EE specs, and generating scaffolding.
However, this does not address how users will/should interact with Forge1 and Forge2. Here is what I would like, and what I believe you suggested in your comments:
CTRL+4 should default to Forge 2 out-of-box. The user may then utilize the Eclipse standard "Keys preferences" page to change that setting to Forge1. Via this same mechanism, they may also configure the key to allow them to select Forge1 or Forge2 each time it is pressed. Max can confirm, but I believe this is standard Eclipse config and should not require much implementation on our part.
We should not need to change the Forge preferences pane in this release AFAIK.
> Forge 2 in JBDS
> ---------------
>
> Key: JBDS-2734
> URL: https://issues.jboss.org/browse/JBDS-2734
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: forge
> Reporter: Burr Sutter
>
> Is Forge 2 ready to be included 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
12 years, 7 months
[JBoss JIRA] (JBIDE-6065) Default Invm Scope to GLOBAL - Usability
by Brian Fitzpatrick (JIRA)
[ https://issues.jboss.org/browse/JBIDE-6065?page=com.atlassian.jira.plugin... ]
Brian Fitzpatrick resolved JBIDE-6065.
--------------------------------------
Resolution: Won't Fix
With less emphasis on the ESB editor and more on the SwitchYard editor, this bug is less relevant moving forward.
> Default Invm Scope to GLOBAL - Usability
> ----------------------------------------
>
> Key: JBIDE-6065
> URL: https://issues.jboss.org/browse/JBIDE-6065
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: esb
> Affects Versions: 3.0.0.GA
> Reporter: Burr Sutter
> Assignee: Brian Fitzpatrick
> Fix For: LATER
>
> Attachments: INVM_Scope.png
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> I have found that I normally forget to set the INVM Scope to GLOBAL when creating a new service. Forgetting to set this attribute results in a runtime error message upon deployment.
> It is very common to forget the attribute because of is placement - at the service level instead of the listener level.
> User will tend to follow these steps:
> - Add a Service
> - Add a HTTP Listener with a urlpattern
> - Add a SOAPProxy Action
> and forget to go back to the Service screen and flip INVM scope to Global
> see screen shot
--
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
12 years, 7 months
[JBoss JIRA] (JBIDE-13438) jboss-packaging-maven-plugin jboss-esb + m2e
by Brian Fitzpatrick (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13438?page=com.atlassian.jira.plugi... ]
Brian Fitzpatrick resolved JBIDE-13438.
---------------------------------------
Resolution: Rejected
Though this would be a good idea if we were going to support ESB into the future, I believe it is supported by the SwitchYard project, which is its spiritual successor. Maven integration was built into SwitchYard from the beginning.
> jboss-packaging-maven-plugin jboss-esb + m2e
> --------------------------------------------
>
> Key: JBIDE-13438
> URL: https://issues.jboss.org/browse/JBIDE-13438
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: esb, integration-platform, maven
> Reporter: Manosh C
> Assignee: Brian Fitzpatrick
> Fix For: 4.2.x
>
> Attachments: testparent.zip
>
>
> Hi,
>
> Does jboss-packaging-maven-plugin m2e connector work for jboss-esb? When I import a maven jboss-esb project into eclipse (m2e installed), it does not covert it into an Eclipse JBoss ESB (facet is not enabled and dependecies are not set) project. I tried almost all versions of eclipse, m2e, jboss tools and jboss soa tools, to make it work, but no use. This is my work around for now
>
> 1. Turn on facet nature and enable JBOSS ESB nature.
> 2. Then it get recognized as a deployable artifact on JBoss server.
> 3. Manually add all dependencies in "Deployment and Assembly section".
>
> What I was expecting was all steps should have been done by m2e jboss esb (jboss-packaging-maven-plugin) connector. I could not find a relevant post or article related to it. Does this feature ever supported?
>
> Thank you in advance.
> Manosh
--
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
12 years, 7 months
[JBoss JIRA] (JBIDE-6085) Implement Validation of ESB config file
by Brian Fitzpatrick (JIRA)
[ https://issues.jboss.org/browse/JBIDE-6085?page=com.atlassian.jira.plugin... ]
Brian Fitzpatrick resolved JBIDE-6085.
--------------------------------------
Resolution: Done
Slava started implementing some validation in the ESB editor a few releases ago, but we didn't get far.
The new SwitchYard tooling has much more validation in place already so I think the spiritual successor to the ESB editor has this wrapped up.
> Implement Validation of ESB config file
> ---------------------------------------
>
> Key: JBIDE-6085
> URL: https://issues.jboss.org/browse/JBIDE-6085
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: esb
> Affects Versions: 3.1.0.GA
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Labels: new_and_noteworthy
> Fix For: 4.2.x
>
> Attachments: ESBValidation_Marker.png, ESBValidatorPreferences .png, jboss-esb-brp-ObjectPath.png, jboss-esb-brp-ruleAuditInterval.png
>
>
> We have no validation implemented for consistency of objects, especially of actions that formally may be supplied by any set of properties while each action class requires a specific configuration.
> We should implement validation similar to that we have for beans in Seam and CDI. Documentation on ESB contains many rules on consistency of ESB objects not covered by simply complying with xml schema.
--
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
12 years, 7 months
[JBoss JIRA] (JBIDE-2070) SOA Modeler
by Brian Fitzpatrick (JIRA)
[ https://issues.jboss.org/browse/JBIDE-2070?page=com.atlassian.jira.plugin... ]
Brian Fitzpatrick closed JBIDE-2070.
------------------------------------
Assignee: Brian Fitzpatrick
Resolution: Out of Date
This bug is 5 years old. We have ESB tooling that supports the JBoss ESB product and SwitchYard tooling that supports the JBoss SwitchYard project. The SY tooling actually approaches this in a much more graphical way, so I suspect the spirit of this JIRA has been addressed even if we didn't take the specific approach suggested by the documents attached.
> SOA Modeler
> -----------
>
> Key: JBIDE-2070
> URL: https://issues.jboss.org/browse/JBIDE-2070
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: esb
> Reporter: Mark Little
> Assignee: Brian Fitzpatrick
> Fix For: LATER
>
> Attachments: Service Modeler 02.doc, Service Modeler 02.pdf
>
>
> Thomas Erl donated IP to us around the SOA Modeler.
--
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
12 years, 7 months
[JBoss JIRA] (JBIDE-15335) Consider removing update site zips from jboss.org/tools
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15335?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-15335:
------------------------------------
+1, I was hoping we'd get community feedback here. Hate having to support things no one uses, but more than happy to support things people DO use. Thanks for speaking up!
> Consider removing update site zips from jboss.org/tools
> -------------------------------------------------------
>
> Key: JBIDE-15335
> URL: https://issues.jboss.org/browse/JBIDE-15335
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: updatesite
> Affects Versions: 4.0.1.Final, 4.1.0.Final
> Reporter: Nick Boldt
> Assignee: Max Rydahl Andersen
>
> Based on anecdotal evidence, it would appear that JBT 4.x is downloaded MANY MORE TIMES from Eclipse Marketplace than from jboss.org/tools:
> As of 2013-08-12 12:48pm:
> * Download stats from http://jboss.org/tools/download/stable/4_1 : 378 + 140 = *518 installs* (could be more if the zip's passed around w/in an org?)
> * Install stats for JBT 4.1.0 from Eclipse Marketplace for 2013/08: *3,678 installs* ({color:red}*7.1x*{color} as many)
> * Download stats from http://jboss.org/tools/download/stable/4_0 : 2441 + 899 = *3,340 installs* (could be more if the zip's passed around w/in an org?)
> * Install stats for JBT 4.0.1 from Eclipse Marketplace for 2013/04 - 2013/08: 11280 + 10421 + 9552 + 6246 + 1635 = *39,134 installs* ({color:red}*11.7x*{color} as many)
> So, is it time to stop providing a zip of the JBT update site? Seems like very few users want JBT delivered via zip.
> Note too that the stats collected above include a partial month (August 2013) during which many people are on vacation. To get a real sense of the download rates we ought to check these numbers again in September and October.
--
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
12 years, 7 months
[JBoss JIRA] (JBDS-2724) Include "Mylyn Builds Connector: Hudson/Jenkins" org.eclipse.mylyn.hudson.feature in both JBT & JBDS Central
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2724?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-2724:
----------------------------------
Nothing you've said so far is impossible to implement, but bear in mind that any renames/reorgs for JBDS 7.1 will magically appear in front of JBDS 7.0.0 users, which MIGHT be confusing. Of course they can always use the search box to find a connector if the categorization is confusing.
[~maxandersen] [~mmurray] [~ldimaggio] any objections to changing "Testing" to "Utilities" as per [~burrsutter]'s suggestion above?
> Include "Mylyn Builds Connector: Hudson/Jenkins" org.eclipse.mylyn.hudson.feature in both JBT & JBDS Central
> ------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-2724
> URL: https://issues.jboss.org/browse/JBDS-2724
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: discovery
> Reporter: Burr Sutter
> Attachments: JBDS7_central.png
>
>
> We should make it easier to work with jenkins for our devops users.
> Start by including the Jenkins plugin (from Max: Mylyn build plugin)
--
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
12 years, 7 months
[JBoss JIRA] (JBTIS-163) Failed to resolve target definition
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBTIS-163?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBTIS-163:
-----------------------------
Fix Version/s: 4.1.4-TP
(was: 4.1.2)
> Failed to resolve target definition
> -----------------------------------
>
> Key: JBTIS-163
> URL: https://issues.jboss.org/browse/JBTIS-163
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: target-platform
> Affects Versions: 4.1.2, 4.1.3
> Reporter: Andrej Podhradsky
> Assignee: Paul Leacu
> Priority: Blocker
> Fix For: 4.1.4-TP
>
>
> During building with target platform 4.1.2-SNAPSHOT / 4.1.2.Final (the same for 4.1.3) I'm getting the following error:
> [ERROR] Internal error: java.lang.RuntimeException: Failed to resolve target definition /home/apodhrad/.m2/repository/org/jboss/tools/integration-stack/target-platform/4.1.2-SNAPSHOT/target-platform-4.1.2-SNAPSHOT-base.target: Could not find "org.jboss.tools.locus.jcip.annotations/1.0.0.Final-v20130729-2113-B39" in the repositories of the current location -> [Help 1]
--
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
12 years, 7 months