[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 commented on JBIDE-13329:
----------------------------------------
m2e requires the .sdk feature since it contains the org.eclipse.m2e.tests.common bundle, required for jbosstools maven tests. Maybe we could replace inclusion of the whole feature by inclusion of this single bundle.
[~fbricon] WDYT?
> 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
> Fix For: 4.1.0.Alpha1
>
>
> 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, 6 months
[JBoss JIRA] (JBIDE-12620) openshift java client: should not load all applications when creating a new application
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12620?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-12620:
-------------------------------------
Fix Version/s: 4.1.x
(was: 4.0.x)
> openshift java client: should not load all applications when creating a new application
> ---------------------------------------------------------------------------------------
>
> Key: JBIDE-12620
> URL: https://issues.jboss.org/browse/JBIDE-12620
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 3.3.0.Final
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.1.x
>
>
> When creating a new application, the openshift-java-client would lookup if the application name already exist. When doing that it'll load the existing apps from the backend if they're not cached yet:
> {code:title=stacktrace when creating a new application}
> at com.openshift.internal.client.AbstractOpenShiftResource$ServiceRequest.execute(AbstractOpenShiftResource.java:137)
> at com.openshift.internal.client.DomainResource.loadApplications(DomainResource.java:189)
> at com.openshift.internal.client.DomainResource.getApplications(DomainResource.java:179)
> at com.openshift.internal.client.DomainResource.getApplicationByName(DomainResource.java:141)
> at com.openshift.internal.client.DomainResource.hasApplicationByName(DomainResource.java:151)
> at com.openshift.internal.client.DomainResource.createApplication(DomainResource.java:126)
> at com.openshift.internal.client.DomainResource.createApplication(DomainResource.java:112)
> {code}
> {code:title=DomainResource looks applications up, to see if the name is already used. DomainResource#createApplication}
> if (hasApplicationByName(name)) {
> throw new OpenShiftException("Application with name \"{0}\" already exists.", name);
> }
> {code}
> {code:title=DomainResource#hasApplicationByName gets the available applications:}
> return getApplicationByName(name) != null;
> {code}
> {code:title=DomainResource#getApplicationByName}
> IApplication matchingApplication = null;
> for (IApplication application : getApplications()) {
> if (application.getName().equals(name)) {
> matchingApplication = application;
> break;
> }
> }
> return matchingApplication;
> {code}
> {code:title=DomainResource#getApplications would load the applications from the backend if they're not loaded yet}
> if (this.applications == null) {
> this.applications = loadApplications();
> }
> return CollectionUtils.toUnmodifiableCopy(applications);
> {code}
--
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, 6 months
[JBoss JIRA] (JBIDE-12620) openshift java client: should not load all applications when creating a new application
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12620?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-12620:
-------------------------------------
Priority: Minor (was: Major)
> openshift java client: should not load all applications when creating a new application
> ---------------------------------------------------------------------------------------
>
> Key: JBIDE-12620
> URL: https://issues.jboss.org/browse/JBIDE-12620
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 3.3.0.Final
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Minor
> Fix For: 4.1.x
>
>
> When creating a new application, the openshift-java-client would lookup if the application name already exist. When doing that it'll load the existing apps from the backend if they're not cached yet:
> {code:title=stacktrace when creating a new application}
> at com.openshift.internal.client.AbstractOpenShiftResource$ServiceRequest.execute(AbstractOpenShiftResource.java:137)
> at com.openshift.internal.client.DomainResource.loadApplications(DomainResource.java:189)
> at com.openshift.internal.client.DomainResource.getApplications(DomainResource.java:179)
> at com.openshift.internal.client.DomainResource.getApplicationByName(DomainResource.java:141)
> at com.openshift.internal.client.DomainResource.hasApplicationByName(DomainResource.java:151)
> at com.openshift.internal.client.DomainResource.createApplication(DomainResource.java:126)
> at com.openshift.internal.client.DomainResource.createApplication(DomainResource.java:112)
> {code}
> {code:title=DomainResource looks applications up, to see if the name is already used. DomainResource#createApplication}
> if (hasApplicationByName(name)) {
> throw new OpenShiftException("Application with name \"{0}\" already exists.", name);
> }
> {code}
> {code:title=DomainResource#hasApplicationByName gets the available applications:}
> return getApplicationByName(name) != null;
> {code}
> {code:title=DomainResource#getApplicationByName}
> IApplication matchingApplication = null;
> for (IApplication application : getApplications()) {
> if (application.getName().equals(name)) {
> matchingApplication = application;
> break;
> }
> }
> return matchingApplication;
> {code}
> {code:title=DomainResource#getApplications would load the applications from the backend if they're not loaded yet}
> if (this.applications == null) {
> this.applications = loadApplications();
> }
> return CollectionUtils.toUnmodifiableCopy(applications);
> {code}
--
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, 6 months
[JBoss JIRA] (JBIDE-12852) OpenShift Server Adapter wizard should automatically validate credentials (default connection)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12852?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-12852:
-------------------------------------
Fix Version/s: 4.1.0.Alpha1
(was: 4.0.x)
> OpenShift Server Adapter wizard should automatically validate credentials (default connection)
> ----------------------------------------------------------------------------------------------
>
> Key: JBIDE-12852
> URL: https://issues.jboss.org/browse/JBIDE-12852
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: JBossAS/Servers, openshift
> Affects Versions: 4.0.0.Beta1
> Reporter: Stefan Bunciak
> Assignee: Rob Stryker
> Fix For: 4.1.0.Alpha1
>
> Attachments: import-link-disabled.png, servervalidating.png
>
>
> In New Server wizard - OpenShift Server: the default (first) connection could be automatically validated.
> In case when user has 1 OpenShift connection without any applications and opens the New Server wizard, selects OpenShift and doesn't open the combo box with connections, the credentials are not validated and the link to import/create application is disabled. Quite confusing on first sight:
> !servervalidating.png|thumbnail!
--
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, 6 months