[JBoss JIRA] Created: (JBIDE-9822) Allow project examples to be created in a user-defined location
by Fred Bricon (JIRA)
Allow project examples to be created in a user-defined location
---------------------------------------------------------------
Key: JBIDE-9822
URL: https://issues.jboss.org/browse/JBIDE-9822
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: maven, project-examples
Affects Versions: 3.3.0.M3
Reporter: Fred Bricon
Assignee: Snjezana Peco
Fix For: 3.3.0.M4
In the wake of JBIDE-9368, we want to be able to let the user kickstart new projects from Maven Archetypes (for starters).
Kickstart/Quickstart projects, as opposed to project examples, are meant to be actually used by users, i.e. added to SCM, as sub modules to existing maven projects;
Problem is, if we choose to use Archetype-based project examples (and I think we should), projects are generated under *<workspace>/.JBossToolsMavenProjects/*
We should be able to change that location, to use the workspace root (or another directory) for example. That means we should change the IImportProjectExample interface to add setLocation(IPath path)/IPath getLocation() methods (or something else)
We need to make sure these projects can be added as maven sub modules.
Also, we must make sure the delete existing example stuff doesn't impede this feature (see JBIDE-9821)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months
[JBoss JIRA] Created: (JBIDE-8425) add capability to chain jobs so that successor jobs dont get executed if predecessors are canceled / fail
by Andre Dietisheim (JIRA)
add capability to chain jobs so that successor jobs dont get executed if predecessors are canceled / fail
---------------------------------------------------------------------------------------------------------
Key: JBIDE-8425
URL: https://issues.jboss.org/browse/JBIDE-8425
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: deltacloud
Affects Versions: 3.2.0.CR1
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Priority: Minor
Fix For: 3.3.x
The current implementation of ChainedJob chains jobs so that all of them are executed regardless if the predecessors are canceled or fail.
In the context of deltacloud there's no need to create an RSE (successor job) if launching the instance (predecessor job) was canceled/failed. There's no way for the RSE creation job to know if the launch was canceled/failed. It may only guess so if the instance is null or has no hostname.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months