Clone Tools
  • last updated a few minutes ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
FUSETOOLS-3244 - create the Camel test case in right folder

src/test/java if it exists, if not, in src/main/java if it exists.

Otherwise in the same one than the Camel file

Signed-off-by: Aurélien Pupier <apupier@redhat.com>

  1. … 2 more files in changeset.
FUSETOOLS-3244 - wait project has been built

now that the project is a Maven one, we need to wait the end of the

build.

Another point is that now the version is cached automatically during the

first build of the Maven project which is forcing to not use the cache

in this test. The case when it will happen in real-life should be very

rare.

Signed-off-by: Aurélien Pupier <apupier@redhat.com>

FUSETOOLS-3244 - Enable Maven Nature for "dummy" project used in test

it is required to have Maven Project Registry working with newer m2e

version 1.12

Without it, it is recreating a MavenFacade everytime we need it.

the tests will be slightly slower than with previous version but will be

more accurate.

Signed-off-by: Aurélien Pupier <apupier@redhat.com>

  1. … 1 more file in changeset.
FUSETOOLS-3097 - Avoid resetting elements if they are at the correct place

it avoids to mess up comments just by displaying diagram.

Please note that modification of the xml is still done in the graphical

which should not occur by design. it would be better to do it in Model

element directly.

Signed-off-by: Aurélien Pupier <apupier@redhat.com>

  1. … 4 more files in changeset.
FUSETOOLS-3084 - Support pure CDATA in attributes

- does not support completely when there is a mix of CDATA and

non-CDATA. In this case it will put everything in CDATA in an equivalent

semantic way.

Signed-off-by: Aurélien Pupier <apupier@redhat.com>

  1. … 2 more files in changeset.
FUSETOOLS-2564 - avoid o.jboss.tools.common which is breaking tests by using xalan parser

Signed-off-by: Aurélien Pupier <apupier@redhat.com>

  1. … 1 more file in changeset.
FUSETOOLS-2564 - use a logger

Signed-off-by: Aurélien Pupier <apupier@redhat.com>

  1. … 1 more file in changeset.
FUSETOOLS-2564 - extract templates of pom for test in files

Signed-off-by: Aurélien Pupier <apupier@redhat.com>

  1. … 2 more files in changeset.
FUSETOOLS-2564 - fixed FuseProject

Signed-off-by: Brian Fitzpatrick <bfitzpat@redhat.com>

FUSETOOLS-2564 - a few improvements and new tests

* removed duplicated "find resource" method and streamlined

* added new tests to ensure Blueprint path is working

* improved FuseProject class with better Blueprint support

Signed-off-by: Brian Fitzpatrick <bfitzpat@redhat.com>

  1. … 4 more files in changeset.
FUSETOOLS-2870: Update the description + other small changes

Signed-off-by: Andrej Podhradsky <apodhrad@redhat.com>

  1. … 2 more files in changeset.
FUSETOOLS-2870: Display ID value only if it is not overridden by a user label

Signed-off-by: Andrej Podhradsky <apodhrad@redhat.com>

  1. … 1 more file in changeset.
FUSETOOLS-2870: Get back the option for specifying ID value for all EIPs

Signed-off-by: Andrej Podhradsky <apodhrad@redhat.com>

  1. … 7 more files in changeset.
FUSETOOLS-2707: Some parameters are not displayed when setting a preferred label

Signed-off-by: Andrej Podhradsky <apodhrad@redhat.com>

  1. … 1 more file in changeset.
FUSETOOLS-2492 - Provide Fuse version corresponding to Camel version

- created a Label provider taking values from an online files (so that

we can update when adding new release version)

- used the label provide in New Fuse Integration Wizard and Change Camel

version

Signed-off-by: Aurélien Pupier <apupier@redhat.com>

  1. … 8 more files in changeset.
FUSETOOLS-2431 - Write basic non-regression test for generating Camel test class

ideas to improve:

- test that the generated test executes well

- use a project template for a more complex cases respecting all

conventional project structure

Signed-off-by: Aurélien Pupier <apupier@redhat.com>

  1. … 11 more files in changeset.
FUSETOOLS-2635 - code cleanup

Signed-off-by: Lars Heinemann <lhein.smx@gmail.com>

FUSETOOLS-1856: Apply improvements suggested by Aurelien

Signed-off-by: Andrej Podhradsky <apodhrad@redhat.com>

  1. … 9 more files in changeset.
FUSETOOLS-2514 - Avoid to have error when pom.xml is missing

- not found a way to reproduce the reported error

- try to provide more robust way to retrieve the Maven project

- add test to cover more usecase

Signed-off-by: Aurélien Pupier <apupier@redhat.com>

  1. … 2 more files in changeset.
FUSETOOLS-2644 - Support routeContext

Signed-off-by: Aurélien Pupier <apupier@redhat.com>

  1. … 19 more files in changeset.
FUSETOOLS-2451 - Provide a CamelContext EIP from Catalog for 2.18- version

it was missing from Camel catalog by default, it was provided since

Camel 2.18

json catalog were created manually based on the 2.18.x and removing

elements introduced by comparing CamelContextFactoryBean from tag to tag

Signed-off-by: Aurélien Pupier <apupier@redhat.com>

  1. … 9 more files in changeset.
FUSETOOLS-2578 - ensure test is using the corresponding Camel version

previously it was always using the catalog from the most recent fuse

version

Signed-off-by: Aurélien Pupier <apupier@redhat.com>

  1. … 1 more file in changeset.
FUSETOOLS-2460 - Fix data loss of Factory bean when model is reloaded

  1. … 3 more files in changeset.
FUSETOOLS-2422 - Handle ids for non-camel elements but with tag name colliding with a camel eip

  1. … 9 more files in changeset.
FUSETOOLS-2422 - Add non-regression test when a prefix is used for Camel namespace

  1. … 2 more files in changeset.
added new file to define which camel versions to test against

  1. … 9 more files in changeset.
fixed broken itest and extracted inner class from CamelBean

  1. … 15 more files in changeset.
rebase with bean global config PR from Brian

  1. … 4 more files in changeset.
FUSETOOLS-2432 - avoid NPE

- extract in a separated class for ID unicity concerns

- provide more precautions to avoid NPE

- provide test class

  1. … 6 more files in changeset.
FUSETOOLS-1585 - beginnings of adding bean support (#880)

* FUSETOOLS-1585 - beginnings of adding bean support

-- adding to Global Configuration page as an "Add" possibility

-- started work on the Bean wizard

-- started on property page for bean properties

-- have basic bean property page working

-- added ID validation for global configuration elements

-- added browse button for bean class in wizard page

-- added class name validation in wizard page

-- added class name validation on property page

-- added class browse button on property page

-- added method browse button on property page

-- added method validation on property page

-- added first cut of property and argument table controls to wizard

-- added support for defining arguments and properties in config

-- some Sonar cleanup

-- added edit buttons to property & argument tables

-- more sonar cleanup

-- addressing comments from Aurelien and more cleanup

-- additional sonar cleanup of lambdas and an icon issue

-- more sonar cleanup and addition of property name uniqueness

validation plus bean id uniqueness validation in property page

-- even more sonar suggested fixes

-- addressing a NPE and some other suggestions made by Aurelien

-- more sonar fixes

-- added edit functionality for properties and arguments

-- added a few sonar & Aurelien-requested changes

-- fixed issue with xml not being added/updated correctly

-- fixed some property name validation issues

-- fixed issue with adding wrong constructor argument tag name to

blueprint

-- further correction to method used to find namespace for blueprint

-- adding beginnings of IT test

-- updated test so it works and refactored some code for easier testing

-- beefed up test to cover basic use cases and blueprint vs. spring

testing

-- added additional tests for creation and editing of beans

-- did a little test refactoring

-- added factory-method/factory-bean functionality to property page and

tests for it

-- added ability to create new class from bean wizards and property page

* FUSETOOLS-1585 - set new java class wizard to not auto-open

Discovered that the new java class wizard opens the new class for

editing immediately after clicking Finish. For this case, we don't want

it to open, since focus would then shift from the Camel Editor.

* FUSETOOLS-1585 - addressing some of Aurelien's feedback,

adding a new test, and correcting a couple of labels

* FUSETOOLS-1585 - moving some XML attribute setting/getting code back to

the CamelBean model object. Adding a test to ensure that it can be

loaded properly and changed via the CamelBean object.

* FUSETOOLS-1585 - adding more tests and functionality to CamelBean

* FUSETOOLS-1585 - small code improvements

* Fixed issue with refresh

* Fixing issue where src/main/java not created yet

* FUSETOOLS-1585 - Factorize code and leverage java 8 streams

* Attempting to fix test issues with Shells

* Updates to PropertyInputDialogTest as suggested by @apupier

* Update to fix one issue

* fix the swt / cocoa lib failures from CI

* fixes model problem

* Specialize bean extension to not clash with SAP

* Addressing an issue found by the Core model test

-- also includes feedback from Aurelien on a couple of code tweaks

* Addressing more comments - test for SAP extension, code cleanup

* Externalizing strings for the Bean work

* Fixes for next round of comments

* Updates to allow specialization of Globel elements and a sonar fix

* FUSETOOLS-1585 - addressed more feedback

- factorized code requested in AdvancedBeanPropertiesSection and

AdvancedEndpointPropertiesSection

- updated developer name in javadocs to be consistent

- fixed validation issues with Property and Argument dialogs so

validation prevents OK button from being active

- removed code around potential WRONG_DOCUMENT_ERR since the last round

of model updates seems to have removed the necessity

* FUSETOOLS-1585 - Avoid having two times the same WizardPage

Before the pages on the wizard are added twice in

org.fusesource.ide.camel.editor.globalconfiguration.beans.BeanConfigUtil.handleNewClassWizard(IProject,

Shell) , there is a addPages() called which is also called when

wizard.open() is called which was causing that nothing happened when

clicking "Next"

Now, it is called a single time. No next button is displayed.

  1. … 49 more files in changeset.