[JBoss JIRA] (JBIDE-18097) Update project configuration is not enough to update eclipse settings - need to delete .project/.classpath and reimport
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18097?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-18097:
--------------------------------
Assignee: Fred Bricon
> Update project configuration is not enough to update eclipse settings - need to delete .project/.classpath and reimport
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18097
> URL: https://issues.jboss.org/browse/JBIDE-18097
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven
> Reporter: Max Rydahl Andersen
> Assignee: Fred Bricon
> Fix For: 4.3.x
>
>
> I'm finding this more and more worrisome so wanted to record it.
> When trying to fix JBDS-2847 or rather fix javee7-samples to be able to import easily we easily end up with a set of projects where settings are wrong.
> I updated the parent pom to not have the groovy compiler enabled and ran update project configuration - and the changes regarding source paths did not take effect.
> Only way to fix was to nuke all files and reimport.
> can this be true ? no way to "force" an update ?
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18295) Errors in project after import WildFly quickstarts
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18295?page=com.atlassian.jira.plugi... ]
Fred Bricon resolved JBIDE-18295.
---------------------------------
Resolution: Done
m2e discovery catalog updated upstream.
No Maven errors are shown anymore once the 2 connectors that m2e discovers are installed
> Errors in project after import WildFly quickstarts
> --------------------------------------------------
>
> Key: JBIDE-18295
> URL: https://issues.jboss.org/browse/JBIDE-18295
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven, upstream
> Affects Versions: 4.2.0.Beta3
> Reporter: Xavier Coulon
> Assignee: Fred Bricon
> Priority: Critical
> Fix For: 4.2.0.CR2
>
>
> After importing all modules from https://github.com/wildfly/quickstart into JBDS 8.0.0.CR1b, a few projects have build errors, such as:
> {code}
> Plugin execution not covered by lifecycle configuration: org.apache.maven.plugins:maven-dependency-plugin:2.1:copy (execution: default, phase: process-sources)
> {code}
> or
> {code}
> Plugin execution not covered by lifecycle configuration: org.apache.maven.plugins:maven-ejb-plugin:2.3:ejb (execution: default, phase: package)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBDS-2978) Monitor WTP issue re: nested packed jars
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2978?page=com.atlassian.jira.plugin.... ]
Nick Boldt resolved JBDS-2978.
------------------------------
Fix Version/s: 8.0.0.CR2
(was: 8.0.0.GA)
Resolution: Done
These jars no longer throw a 'java.lang.SecurityException: SHA1 digest error':
Step 1: download eclipse-jee-luna-SR1-RC3-linux-gtk-x86_64.tar.gz and unpack it
Step 2: go into the eclipse/plugins folder under the unpacked SR1-RC3 folder and do this:
{code}
$ /opt/jdk1.8.0/bin/jarsigner -verify ./org.eclipse.wst.command.env_*.jar
jar verified.
$ /opt/jdk1.8.0/bin/jarsigner -verify ./org.eclipse.jst.ws.consumption_*.jar
jar verified.
{code}
> Monitor WTP issue re: nested packed jars
> ----------------------------------------
>
> Key: JBDS-2978
> URL: https://issues.jboss.org/browse/JBDS-2978
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Sub-task
> Components: build, requirements, target-platform, upstream
> Affects Versions: 8.0.0.Beta2
> Reporter: Nick Boldt
> Assignee: Mickael Istria
> Fix For: 8.0.0.CR2
>
>
> Adding this subtask as a reminder to myself to check in w/ WTP from time to time to see if https://bugs.eclipse.org/bugs/show_bug.cgi?id=430923 gets fixed.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18306) The obsoleted cartridges are still shown
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18306?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-18306:
------------------------------------------
There is no need for further changes in the Eclipse tooling beside using openshift-java-client 2.6.1. The embedding wizard already adds cartridges that are present in the application but not in OpenShift: this was already needed for downloadable cartridges which are present in the app but not in the list of available cartridges in OpenShift.
> The obsoleted cartridges are still shown
> ----------------------------------------
>
> Key: JBIDE-18306
> URL: https://issues.jboss.org/browse/JBIDE-18306
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.2.Final
> Reporter: Chunyun Chen
> Assignee: Andre Dietisheim
> Priority: Critical
> Fix For: 4.2.0.CR2
>
> Attachments: application-wizard-obsolete-cartridge.png, edit-embedded-cartridges.png, error-create-obsolete-cartridge.png
>
>
> The obsoleted cartridges are still shown in the cartridge list, like obsoleted cartridge zend-5.6, nodejs-0.6 and metrics-0.1, they should not be shown any more in the list.
> the issue may due to java-client not using the latest 1.7 version restapi.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18440) The obsoleted cartridges are still shown
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18440?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-18440:
-------------------------------------
Fix Version/s: 4.3.0.Alpha1
(was: 4.3.x)
> The obsoleted cartridges are still shown
> ----------------------------------------
>
> Key: JBIDE-18440
> URL: https://issues.jboss.org/browse/JBIDE-18440
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.2.Final
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Critical
> Fix For: 4.3.0.Alpha1
>
> Attachments: application-wizard-obsolete-cartridge.png, edit-embedded-cartridges.png, error-create-obsolete-cartridge.png
>
>
> The obsoleted cartridges are still shown in the cartridge list, like obsoleted cartridge zend-5.6, nodejs-0.6 and metrics-0.1, they should not be shown any more in the list.
> the issue may due to java-client not using the latest 1.7 version restapi.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18440) The obsoleted cartridges are still shown
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18440?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-18440:
-------------------------------------
Fix Version/s: 4.3.x
(was: 4.2.0.CR2)
> The obsoleted cartridges are still shown
> ----------------------------------------
>
> Key: JBIDE-18440
> URL: https://issues.jboss.org/browse/JBIDE-18440
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.2.Final
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Critical
> Fix For: 4.3.x
>
> Attachments: application-wizard-obsolete-cartridge.png, edit-embedded-cartridges.png, error-create-obsolete-cartridge.png
>
>
> The obsoleted cartridges are still shown in the cartridge list, like obsoleted cartridge zend-5.6, nodejs-0.6 and metrics-0.1, they should not be shown any more in the list.
> the issue may due to java-client not using the latest 1.7 version restapi.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18440) The obsoleted cartridges are still shown
by Andre Dietisheim (JIRA)
Andre Dietisheim created JBIDE-18440:
----------------------------------------
Summary: The obsoleted cartridges are still shown
Key: JBIDE-18440
URL: https://issues.jboss.org/browse/JBIDE-18440
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.1.2.Final
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Priority: Critical
Fix For: 4.2.0.CR2
Attachments: application-wizard-obsolete-cartridge.png, edit-embedded-cartridges.png, error-create-obsolete-cartridge.png
The obsoleted cartridges are still shown in the cartridge list, like obsoleted cartridge zend-5.6, nodejs-0.6 and metrics-0.1, they should not be shown any more in the list.
the issue may due to java-client not using the latest 1.7 version restapi.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months