[JBoss JIRA] (FORGE-440) A pom.xml which contains comments loses all of them after Forge operates on it.
by Lennart Jörelid (JIRA)
[ https://issues.jboss.org/browse/FORGE-440?page=com.atlassian.jira.plugin.... ]
Lennart Jörelid edited comment on FORGE-440 at 2/29/16 11:32 AM:
-----------------------------------------------------------------
This is exactly the reason why I have not been able to use Forge in any of the bigger enterprise
projects the last 3 years.
Keeping readability, XML comments and indentation for reasons of readability are
also - to some extent - reasons to promote usability and maintainability.
Basically, being able to read through - and quickly understand - parts of the POM contributes more to
maintainabilty of the POM (and, hence the Maven build reactor) than the ability to edit it using tools
such as Forge.
Let's go with an example, where it is important to preserve the comment within the POM
to avoid removing an important snippet. While I understand that the Maven library to create
structures within the POM is tasty to work with, I believe that Forge needs to paint with a
bigger brush, to handle all parts of an XML file.
{code:xml}
<!--
Due to problems in the Maven 3 site plugin you must enter the configuration twice,
once for the pluginManagement section and once for the site, see
http://jira.codehaus.org/browse/MSITE-516 and http://jira.codehaus.org/browse/MSITE-523
-->
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-pmd-plugin</artifactId>
<version>${pmd.plugin.version}</version>
<configuration>
<rulesets>
<ruleset>${project.build.outputDirectory}/codestyle/pmd-rules.xml</ruleset>
</rulesets>
<targetJdk>${jdk.version}</targetJdk>
<sourceEncoding>UTF-8</sourceEncoding>
</configuration>
</plugin>
{code}
was (Author: lennartj):
This is exactly the reason why I have not been able to use Forge in any of the bigger enterprise
projects the last 3 years.
Keeping readability, XML comments and indentation for reasons of readability are
also - to some extent - reasons to promote usability and maintainability.
Basically, being able to read through - and quickly understand - parts of the POM contributes more to
maintainabilty of the POM (and, hence the Maven build reactor) than the ability to edit it using tools
such as Forge.
Let's go with an example, where it is important to preserve the comment within the POM
to avoid removing an important snippet:
{code:xml}
<!--
Due to problems in the Maven 3 site plugin you must enter the configuration twice,
once for the pluginManagement section and once for the site, see
http://jira.codehaus.org/browse/MSITE-516 and http://jira.codehaus.org/browse/MSITE-523
-->
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-pmd-plugin</artifactId>
<version>${pmd.plugin.version}</version>
<configuration>
<rulesets>
<ruleset>${project.build.outputDirectory}/codestyle/pmd-rules.xml</ruleset>
</rulesets>
<targetJdk>${jdk.version}</targetJdk>
<sourceEncoding>UTF-8</sourceEncoding>
</configuration>
</plugin>
{code}
> A pom.xml which contains comments loses all of them after Forge operates on it.
> -------------------------------------------------------------------------------
>
> Key: FORGE-440
> URL: https://issues.jboss.org/browse/FORGE-440
> Project: Forge
> Issue Type: Bug
> Components: Build Tools - Maven
> Affects Versions: 1.0.6.Final
> Environment: HEAD
> Reporter: Pete Muir
> Fix For: 3.x Future
>
> Attachments: pomComments.png
>
>
> Also looses formatting, but this is less of an issue.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 1 month
[JBoss JIRA] (FORGE-440) A pom.xml which contains comments loses all of them after Forge operates on it.
by Lennart Jörelid (JIRA)
[ https://issues.jboss.org/browse/FORGE-440?page=com.atlassian.jira.plugin.... ]
Lennart Jörelid commented on FORGE-440:
---------------------------------------
This is exactly the reason why I have not been able to use Forge in any of the bigger enterprise
projects the last 3 years.
Keeping readability, XML comments and indentation for reasons of readability are
also - to some extent - reasons to promote usability and maintainability.
Basically, being able to read through - and quickly understand - parts of the POM contributes more to
maintainabilty of the POM (and, hence the Maven build reactor) than the ability to edit it using tools
such as Forge.
Let's go with an example, where it is important to preserve the comment within the POM
to avoid removing an important snippet:
{code:xml}
<!--
Due to problems in the Maven 3 site plugin you must enter the configuration twice,
once for the pluginManagement section and once for the site, see
http://jira.codehaus.org/browse/MSITE-516 and http://jira.codehaus.org/browse/MSITE-523
-->
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-pmd-plugin</artifactId>
<version>${pmd.plugin.version}</version>
<configuration>
<rulesets>
<ruleset>${project.build.outputDirectory}/codestyle/pmd-rules.xml</ruleset>
</rulesets>
<targetJdk>${jdk.version}</targetJdk>
<sourceEncoding>UTF-8</sourceEncoding>
</configuration>
</plugin>
{code}
> A pom.xml which contains comments loses all of them after Forge operates on it.
> -------------------------------------------------------------------------------
>
> Key: FORGE-440
> URL: https://issues.jboss.org/browse/FORGE-440
> Project: Forge
> Issue Type: Bug
> Components: Build Tools - Maven
> Affects Versions: 1.0.6.Final
> Environment: HEAD
> Reporter: Pete Muir
> Fix For: 3.x Future
>
> Attachments: pomComments.png
>
>
> Also looses formatting, but this is less of an issue.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 1 month
[JBoss JIRA] (FORGE-440) A pom.xml which contains comments loses all of them after Forge operates on it.
by Claus Ibsen (JIRA)
[ https://issues.jboss.org/browse/FORGE-440?page=com.atlassian.jira.plugin.... ]
Claus Ibsen commented on FORGE-440:
-----------------------------------
Frankly as JBoss Tools also supports maven editing it would be awesome if there was a XML tool we all could use that could update XML files without changing the structure. The Camel tools in JBoss Tools also has this problem, when you use its GUI editor, then the Camel XML is also re-created each time and loosing comments and formatting.
There are great git diff tools, so I wonder if maybe they could somehow be used, to try to merge the changes into the existing old xml file?
> A pom.xml which contains comments loses all of them after Forge operates on it.
> -------------------------------------------------------------------------------
>
> Key: FORGE-440
> URL: https://issues.jboss.org/browse/FORGE-440
> Project: Forge
> Issue Type: Bug
> Components: Build Tools - Maven
> Affects Versions: 1.0.6.Final
> Environment: HEAD
> Reporter: Pete Muir
> Fix For: 3.x Future
>
> Attachments: pomComments.png
>
>
> Also looses formatting, but this is less of an issue.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 1 month
[JBoss JIRA] (FORGE-440) A pom.xml which contains comments loses all of them after Forge operates on it.
by Claus Ibsen (JIRA)
[ https://issues.jboss.org/browse/FORGE-440?page=com.atlassian.jira.plugin.... ]
Claus Ibsen commented on FORGE-440:
-----------------------------------
Here is an example of before vs after. We have a fabric8-setup command that makes a maven project ready for openshift/fabric8.
{code}
[dude]$ cat pom.xml
<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
<modelVersion>4.0.0</modelVersion>
<groupId>org.dude</groupId>
<artifactId>dude</artifactId>
<packaging>jar</packaging>
<version>1.0.0-SNAPSHOT</version>
<name>A Camel Spring Route</name>
<url>http://www.myorganization.org</url>
<properties>
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
<project.reporting.outputEncoding>UTF-8</project.reporting.outputEncoding>
</properties>
<dependencies>
<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-core</artifactId>
<version>2.16.2</version>
</dependency>
<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-spring</artifactId>
<version>2.16.2</version>
</dependency>
<!-- logging -->
<dependency>
<groupId>org.slf4j</groupId>
<artifactId>slf4j-api</artifactId>
<version>1.7.12</version>
</dependency>
<dependency>
<groupId>org.slf4j</groupId>
<artifactId>slf4j-log4j12</artifactId>
<version>1.7.12</version>
</dependency>
<dependency>
<groupId>log4j</groupId>
<artifactId>log4j</artifactId>
<version>1.2.17</version>
</dependency>
<!-- testing -->
<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-test-spring</artifactId>
<version>2.16.2</version>
<scope>test</scope>
</dependency>
</dependencies>
<build>
<defaultGoal>install</defaultGoal>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<version>3.3</version>
<configuration>
<source>1.7</source>
<target>1.7</target>
</configuration>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-resources-plugin</artifactId>
<version>2.6</version>
<configuration>
<encoding>UTF-8</encoding>
</configuration>
</plugin>
<!-- allows the route to be ran via 'mvn camel:run' -->
<plugin>
<groupId>org.apache.camel</groupId>
<artifactId>camel-maven-plugin</artifactId>
<version>2.16.2</version>
</plugin>
</plugins>
</build>
</project>
{code}
And now after
{code}
[dude]$ fabric8-setup
***SUCCESS*** Added Fabric8 Maven support with base Docker image: fabric8/java-jboss-openjdk8-jdk:1.0.10. Added the following Maven profiles [f8-build, f8-deploy, f8-local-deploy] to make building the project easier, e.g. mvn -Pf8-local-deploy
[dude]$ cat pom.xml
<?xml version="1.0" encoding="UTF-8"?>
<project xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd" xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<modelVersion>4.0.0</modelVersion>
<groupId>org.dude</groupId>
<artifactId>dude</artifactId>
<version>1.0.0-SNAPSHOT</version>
<name>A Camel Spring Route</name>
<url>http://www.myorganization.org</url>
<properties>
<docker.assemblyDescriptorRef>artifact-with-dependencies</docker.assemblyDescriptorRef>
<docker.from>docker.io/fabric8/java-jboss-openjdk8-jdk:1.0.10</docker.from>
<docker.image>fabric8/${project.artifactId}:${project.version}</docker.image>
<docker.port.container.jolokia>8778</docker.port.container.jolokia>
<fabric8.iconRef>icons/camel</fabric8.iconRef>
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
<project.reporting.outputEncoding>UTF-8</project.reporting.outputEncoding>
</properties>
<dependencies>
<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-core</artifactId>
<version>2.16.2</version>
</dependency>
<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-spring</artifactId>
<version>2.16.2</version>
</dependency>
<dependency>
<groupId>org.slf4j</groupId>
<artifactId>slf4j-api</artifactId>
<version>1.7.12</version>
</dependency>
<dependency>
<groupId>org.slf4j</groupId>
<artifactId>slf4j-log4j12</artifactId>
<version>1.7.12</version>
</dependency>
<dependency>
<groupId>log4j</groupId>
<artifactId>log4j</artifactId>
<version>1.2.17</version>
</dependency>
<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-test-spring</artifactId>
<version>2.16.2</version>
<scope>test</scope>
</dependency>
</dependencies>
<build>
<defaultGoal>install</defaultGoal>
<plugins>
<plugin>
<artifactId>maven-compiler-plugin</artifactId>
<version>3.3</version>
<configuration>
<source>1.7</source>
<target>1.7</target>
</configuration>
</plugin>
<plugin>
<artifactId>maven-resources-plugin</artifactId>
<version>2.6</version>
<configuration>
<encoding>UTF-8</encoding>
</configuration>
</plugin>
<plugin>
<groupId>org.apache.camel</groupId>
<artifactId>camel-maven-plugin</artifactId>
<version>2.16.2</version>
</plugin>
<plugin>
<groupId>io.fabric8</groupId>
<artifactId>docker-maven-plugin</artifactId>
<version>0.14.1</version>
<configuration>
<images>
<image>
<name>${docker.image}</name>
<build>
<from>${docker.from}</from>
<assembly>
<basedir>/app</basedir>
<descriptorRef>${docker.assemblyDescriptorRef}</descriptorRef>
</assembly>
<env>
<JAVA_MAIN_CLASS>org.apache.camel.spring.Main</JAVA_MAIN_CLASS>
</env>
</build>
</image>
</images>
</configuration>
</plugin>
<plugin>
<groupId>io.fabric8</groupId>
<artifactId>fabric8-maven-plugin</artifactId>
<version>2.2.96</version>
<executions>
<execution>
<id>json</id>
<phase>generate-resources</phase>
<goals>
<goal>json</goal>
</goals>
</execution>
<execution>
<id>attach</id>
<phase>package</phase>
<goals>
<goal>attach</goal>
</goals>
</execution>
</executions>
</plugin>
</plugins>
</build>
<profiles>
<profile>
<id>f8-build</id>
<build>
<defaultGoal>clean install docker:build fabric8:json</defaultGoal>
</build>
</profile>
<profile>
<id>f8-deploy</id>
<build>
<defaultGoal>clean install docker:build docker:push fabric8:json fabric8:apply</defaultGoal>
</build>
<properties>
<fabric8.recreate>true</fabric8.recreate>
<fabric8.imagePullPolicySnapshot>Always</fabric8.imagePullPolicySnapshot>
</properties>
</profile>
<profile>
<id>f8-local-deploy</id>
<build>
<defaultGoal>clean install docker:build fabric8:json fabric8:apply</defaultGoal>
</build>
<properties>
<fabric8.recreate>true</fabric8.recreate>
</properties>
</profile>
</profiles>
</project>
{code}
> A pom.xml which contains comments loses all of them after Forge operates on it.
> -------------------------------------------------------------------------------
>
> Key: FORGE-440
> URL: https://issues.jboss.org/browse/FORGE-440
> Project: Forge
> Issue Type: Bug
> Components: Build Tools - Maven
> Affects Versions: 1.0.6.Final
> Environment: HEAD
> Reporter: Pete Muir
> Fix For: 3.x Future
>
> Attachments: pomComments.png
>
>
> Also looses formatting, but this is less of an issue.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 1 month
[JBoss JIRA] (FORGE-2595) addon-install doesn't work
by Claus Ibsen (JIRA)
[ https://issues.jboss.org/browse/FORGE-2595?page=com.atlassian.jira.plugin... ]
Claus Ibsen commented on FORGE-2595:
------------------------------------
Remove your local .m2/repository/io/fabric8/forge directory if you have old versions and old maven cache filed. Then it forces mvn to update and load from central.
And then latest release 2.2.129 is in central and works. You need minimum to use Forge 3.0 RC1 as the Camel commands uses some APIs introduced in that build.
> addon-install doesn't work
> --------------------------
>
> Key: FORGE-2595
> URL: https://issues.jboss.org/browse/FORGE-2595
> Project: Forge
> Issue Type: Bug
> Components: Addon Manager
> Affects Versions: 2.20.2.Final
> Reporter: Paolo Antinori
>
> Hi, I'm trying to install addon in Forge 2.x without luck.
> This is what I'm doing:
> {code}
> [pantinor]$ addon-install --coordinate io.fabric8.forge:camel-commands,2.2.121
> ***ERROR*** Error while executing 'addon-install'
> java.lang.RuntimeException: org.eclipse.aether.resolution.DependencyResolutionException: Failure to find io.fabric8.forge:camel-commands:jar:forge-addon:2.2.121 in http://repo1.maven.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced
> at org.jboss.forge.furnace.manager.maven.addon.MavenAddonDependencyResolver.resolveResources(MavenAddonDependencyResolver.java:172)
> at org.jboss.forge.furnace.manager.maven.addon.LazyAddonInfo.resolveResources(LazyAddonInfo.java:88)
> at org.jboss.forge.furnace.manager.maven.addon.LazyAddonInfo.getResources(LazyAddonInfo.java:39)
> at org.jboss.forge.furnace.manager.impl.request.DeployRequestImpl.deploy(DeployRequestImpl.java:59)
> at org.jboss.forge.furnace.manager.impl.request.DeployRequestImpl$1.call(DeployRequestImpl.java:49)
> at org.jboss.forge.furnace.impl.lock.LockManagerImpl.performLocked(LockManagerImpl.java:55)
> at org.jboss.forge.furnace.manager.impl.request.DeployRequestImpl.execute(DeployRequestImpl.java:44)
> at org.jboss.forge.furnace.manager.impl.request.AbstractAddonActionRequest.perform(AbstractAddonActionRequest.java:57)
> at org.jboss.forge.furnace.manager.impl.request.InstallRequestImpl.perform(InstallRequestImpl.java:39)
> at org.jboss.forge.addon.manager.impl.ui.AddonInstallCommand.execute(AddonInstallCommand.java:118)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor$1.call(ClassLoaderInterceptor.java:87)
> at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42)
> at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor.invoke(ClassLoaderInterceptor.java:103)
> at org.jboss.forge.addon.manager.impl.ui.AddonInstallCommand_$$_javassist_09c5cd7e-e8c0-47cd-9630-ef7affd443d4.execute(AddonInstallCommand_$$_javassist_09c5cd7e-e8c0-47cd-9630-ef7affd443d4.java)
> at org.jboss.forge.addon.ui.impl.controller.SingleCommandControllerImpl.execute(SingleCommandControllerImpl.java:94)
> at org.jboss.forge.addon.shell.aesh.CommandAdapter.execute(CommandAdapter.java:98)
> at org.jboss.forge.addon.shell.aesh.ForgeCommandContainer.executeCommand(ForgeCommandContainer.java:90)
> at org.jboss.aesh.console.AeshConsoleImpl$AeshConsoleCallbackImpl.execute(AeshConsoleImpl.java:311)
> at org.jboss.aesh.console.AeshProcess.run(AeshProcess.java:53)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: org.eclipse.aether.resolution.DependencyResolutionException: Failure to find io.fabric8.forge:camel-commands:jar:forge-addon:2.2.121 in http://repo1.maven.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced
> at org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:384)
> at org.jboss.forge.furnace.manager.maven.addon.MavenAddonDependencyResolver.resolveResources(MavenAddonDependencyResolver.java:168)
> ... 25 more
> Caused by: org.eclipse.aether.resolution.ArtifactResolutionException: Failure to find io.fabric8.forge:camel-commands:jar:forge-addon:2.2.121 in http://repo1.maven.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:444)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:246)
> at org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:367)
> ... 26 more
> Caused by: org.eclipse.aether.transfer.ArtifactNotFoundException: Failure to find io.fabric8.forge:camel-commands:jar:forge-addon:2.2.121 in http://repo1.maven.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced
> at org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.newException(DefaultUpdateCheckManager.java:231)
> at org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.checkArtifact(DefaultUpdateCheckManager.java:206)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.gatherDownloads(DefaultArtifactResolver.java:585)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.performDownloads(DefaultArtifactResolver.java:503)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:421)
> ... 28 more
> ***ERROR*** Addon io.fabric8.forge:camel-commands,2.2.121 could not be installed.
> {code}
> The artifact is correctly there in Maven:
> http://repo1.maven.org/maven2/io/fabric8/forge/camel/2.2.121/
> It fails also when I try to install a core addon:
> {code}
> addon-install --coordinate org.jboss.forge.addon:slf4j,1.7.13
> {code}
> {code}
> [pantinor]$ version
> JBoss Forge, version [ 2.20.2.Final ] - JBoss, by Red Hat, Inc. [ http://jboss.org/forge ]
> [pantinor]$ forge-update
> ***INFO*** Forge is up to date! Enjoy!
> [pantinor]$ system-property-get | grep java
> [pantinor]$ java.runtime.name=Java(TM) SE Runtime Environment
> sun.boot.library.path=/usr/java/jdk1.7.0_76/jre/lib/amd64
> java.vm.version=24.76-b04
> java.vm.vendor=Oracle Corporation
> java.vendor.url=http\://java.oracle.com/
> java.vm.name=Java HotSpot(TM) 64-Bit Server VM
> sun.java.launcher=SUN_STANDARD
> java.vm.specification.name=Java Virtual Machine Specification
> java.runtime.version=1.7.0_76-b13
> java.awt.graphicsenv=sun.awt.X11GraphicsEnvironment
> java.endorsed.dirs=/usr/java/jdk1.7.0_76/jre/lib/endorsed
> java.io.tmpdir=/tmp
> java.vm.specification.vendor=Oracle Corporation
> java.util.logging.manager=org.jboss.logmanager.LogManager
> java.library.path=/usr/java/packages/lib/amd64\:/usr/lib64\:/lib64\:/lib\:/usr/lib
> java.specification.name=Java Platform API Specification
> java.class.version=51.0
> java.awt.printerjob=sun.print.PSPrinterJob
> java.specification.version=1.7
> java.class.path=/data/software/redhat/utils/forge/lib/furnace-manager-spi-2.22.10.Final.jar\:/data/software/redhat/utils/forge/lib/wagon-provider-api-1.0.jar\:/data/software/redhat/utils/forge/lib/jboss-logmanager-1.4.1.Final.jar\:/data/software/redhat/utils/forge/lib/plexus-interpolation-1.21.jar\:/data/software/redhat/utils/forge/lib/aether-api-1.0.2.v20150114.jar\:/data/software/redhat/utils/forge/lib/furnace-2.22.10.Final.jar\:/data/software/redhat/utils/forge/lib/aether-spi-1.0.2.v20150114.jar\:/data/software/redhat/utils/forge/lib/jsoup-1.7.2.jar\:/data/software/redhat/utils/forge/lib/maven-settings-builder-3.3.3.jar\:/data/software/redhat/utils/forge/lib/furnace-manager-api-2.22.10.Final.jar\:/data/software/redhat/utils/forge/lib/plexus-cipher-1.4.jar\:/data/software/redhat/utils/forge/lib/forge-bootstrap-2.20.2.Final.jar\:/data/software/redhat/utils/forge/lib/maven-model-builder-3.3.3.jar\:/data/software/redhat/utils/forge/lib/aether-impl-1.0.2.v20150114.jar\:/data/software/redhat/utils/forge/lib/guava-18.0.jar\:/data/software/redhat/utils/forge/lib/maven-settings-3.3.3.jar\:/data/software/redhat/utils/forge/lib/plexus-utils-3.0.20.jar\:/data/software/redhat/utils/forge/lib/commons-lang-2.6.jar\:/data/software/redhat/utils/forge/lib/maven-builder-support-3.3.3.jar\:/data/software/redhat/utils/forge/lib/aether-connector-basic-1.0.2.v20150114.jar\:/data/software/redhat/utils/forge/lib/jboss-modules-1.3.1.Final-forge.jar\:/data/software/redhat/utils/forge/lib/wagon-http-lightweight-2.8.jar\:/data/software/redhat/utils/forge/lib/commons-io-2.2.jar\:/data/software/redhat/utils/forge/lib/furnace-manager-resolver-maven-2.22.10.Final.jar\:/data/software/redhat/utils/forge/lib/xml-parser-1.0.0.Final.jar\:/data/software/redhat/utils/forge/lib/jgrapht-0.8.3.jar\:/data/software/redhat/utils/forge/lib/furnace-api-2.22.10.Final.jar\:/data/software/redhat/utils/forge/lib/maven-repository-metadata-3.3.3.jar\:/data/software/redhat/utils/forge/lib/maven-model-3.3.3.jar\:/data/software/redhat/utils/forge/lib/aether-util-1.0.2.v20150114.jar\:/data/software/redhat/utils/forge/lib/wagon-file-2.8.jar\:/data/software/redhat/utils/forge/lib/plexus-sec-dispatcher-1.3.jar\:/data/software/redhat/utils/forge/lib/wagon-http-shared-2.8.jar\:/data/software/redhat/utils/forge/lib/maven-aether-provider-3.3.3.jar\:/data/software/redhat/utils/forge/lib/plexus-component-annotations-1.5.5.jar\:/data/software/redhat/utils/forge/lib/forge-javassist-2.jar\:/data/software/redhat/utils/forge/lib/furnace-proxy-2.22.10.Final.jar\:/data/software/redhat/utils/forge/lib/furnace-manager-2.22.10.Final.jar\:/data/software/redhat/utils/forge/lib/aether-transport-wagon-1.0.2.v20150114.jar
> java.vm.specification.version=1.7
> sun.java.command=org.jboss.forge.bootstrap.Bootstrap --immutableAddonDir /data/software/redhat/utils/forge/addons/
> java.home=/usr/java/jdk1.7.0_76/jre
> java.specification.vendor=Oracle Corporation
> java.vm.info=mixed mode
> java.version=1.7.0_76
> java.ext.dirs=/usr/java/jdk1.7.0_76/jre/lib/ext\:/usr/java/packages/lib/ext
> sun.boot.class.path=/usr/java/jdk1.7.0_76/jre/lib/resources.jar\:/usr/java/jdk1.7.0_76/jre/lib/rt.jar\:/usr/java/jdk1.7.0_76/jre/lib/sunrsasign.jar\:/usr/java/jdk1.7.0_76/jre/lib/jsse.jar\:/usr/java/jdk1.7.0_76/jre/lib/jce.jar\:/usr/java/jdk1.7.0_76/jre/lib/charsets.jar\:/usr/java/jdk1.7.0_76/jre/lib/jfr.jar\:/usr/java/jdk1.7.0_76/jre/classes
> java.vendor=Oracle Corporation
> java.vendor.url.bug=http\://bugreport.sun.com/bugreport/
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 1 month
[JBoss JIRA] (FORGE-2606) Forge addon - Changing the current file may cause a "file has changed in file vs memory" issue in Eclipse
by Claus Ibsen (JIRA)
[ https://issues.jboss.org/browse/FORGE-2606?page=com.atlassian.jira.plugin... ]
Claus Ibsen commented on FORGE-2606:
------------------------------------
The only work around is to manually save the file with ctrl + s before running the forge command.
> Forge addon - Changing the current file may cause a "file has changed in file vs memory" issue in Eclipse
> ---------------------------------------------------------------------------------------------------------
>
> Key: FORGE-2606
> URL: https://issues.jboss.org/browse/FORGE-2606
> Project: Forge
> Issue Type: Bug
> Affects Versions: 3.0.0.CR1
> Reporter: Claus Ibsen
> Attachments: eclipse-add.png
>
>
> Similar problem as FORGE-2605 but this time its in Eclipse.
> See the attached screenshot, where I have edited the file camel-context.xml, and then run my forge command, which would insert a Camel endpoint at the cursor position. But eclipse has detected a file conflict as in that dialog.
> I wonder if the fix should be like in IDEA to save the file before the command is run.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 1 month