[JBoss JIRA] (FORGE-2180) Forge offline 2.13.0 prints version as 2.13.3
by Claus Ibsen (JIRA)
[ https://issues.jboss.org/browse/FORGE-2180?page=com.atlassian.jira.plugin... ]
Claus Ibsen commented on FORGE-2180:
------------------------------------
Also I trashed my ~/.forge directory so it started from clean
> Forge offline 2.13.0 prints version as 2.13.3
> ---------------------------------------------
>
> Key: FORGE-2180
> URL: https://issues.jboss.org/browse/FORGE-2180
> Project: Forge
> Issue Type: Bug
> Reporter: Claus Ibsen
> Priority: Minor
>
> In the welcome screen it says 2.12.3. But its the 2.13.0 release.
> {code}
> davsclaus:/opt/$ tar xf ~/Downloads/forge-distribution-2.13.0.Final-offline.zip
> davsclaus:/opt/$ cd forge-distribution-2.13.0.Final/
> davsclaus:/opt/forge-distribution-2.13.0.Final/$ bin/forge
> _____
> | ___|__ _ __ __ _ ___
> | |_ / _ \| `__/ _` |/ _ \ \\
> | _| (_) | | | (_| | __/ //
> |_| \___/|_| \__, |\___|
> |__/
> JBoss Forge, version [ 2.12.3.Final ] - JBoss, by Red Hat, Inc. [ http://forge.jboss.org ]
> [forge-distribution-2.13.0.Final]$
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years
[JBoss JIRA] (FORGE-2180) Forge offline 2.13.0 prints version as 2.13.3
by Claus Ibsen (JIRA)
[ https://issues.jboss.org/browse/FORGE-2180?page=com.atlassian.jira.plugin... ]
Claus Ibsen commented on FORGE-2180:
------------------------------------
eg here
> JBoss Forge, version [ 2.12.3.Final ]
> Forge offline 2.13.0 prints version as 2.13.3
> ---------------------------------------------
>
> Key: FORGE-2180
> URL: https://issues.jboss.org/browse/FORGE-2180
> Project: Forge
> Issue Type: Bug
> Reporter: Claus Ibsen
> Priority: Minor
>
> In the welcome screen it says 2.12.3. But its the 2.13.0 release.
> {code}
> davsclaus:/opt/$ tar xf ~/Downloads/forge-distribution-2.13.0.Final-offline.zip
> davsclaus:/opt/$ cd forge-distribution-2.13.0.Final/
> davsclaus:/opt/forge-distribution-2.13.0.Final/$ bin/forge
> _____
> | ___|__ _ __ __ _ ___
> | |_ / _ \| `__/ _` |/ _ \ \\
> | _| (_) | | | (_| | __/ //
> |_| \___/|_| \__, |\___|
> |__/
> JBoss Forge, version [ 2.12.3.Final ] - JBoss, by Red Hat, Inc. [ http://forge.jboss.org ]
> [forge-distribution-2.13.0.Final]$
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years
[JBoss JIRA] (FORGE-2180) Forge offline 2.13.0 prints version as 2.13.3
by Claus Ibsen (JIRA)
Claus Ibsen created FORGE-2180:
----------------------------------
Summary: Forge offline 2.13.0 prints version as 2.13.3
Key: FORGE-2180
URL: https://issues.jboss.org/browse/FORGE-2180
Project: Forge
Issue Type: Bug
Reporter: Claus Ibsen
Priority: Minor
In the welcome screen it says 2.12.3. But its the 2.13.0 release.
{code}
davsclaus:/opt/$ tar xf ~/Downloads/forge-distribution-2.13.0.Final-offline.zip
davsclaus:/opt/$ cd forge-distribution-2.13.0.Final/
davsclaus:/opt/forge-distribution-2.13.0.Final/$ bin/forge
_____
| ___|__ _ __ __ _ ___
| |_ / _ \| `__/ _` |/ _ \ \\
| _| (_) | | | (_| | __/ //
|_| \___/|_| \__, |\___|
|__/
JBoss Forge, version [ 2.12.3.Final ] - JBoss, by Red Hat, Inc. [ http://forge.jboss.org ]
[forge-distribution-2.13.0.Final]$
{code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years
[JBoss JIRA] (FORGE-2179) project-list-dependencies command
by Claus Ibsen (JIRA)
[ https://issues.jboss.org/browse/FORGE-2179?page=com.atlassian.jira.plugin... ]
Claus Ibsen commented on FORGE-2179:
------------------------------------
There is also this command, but I think the word facets don't mean much for the end users
{code}
[mydemo]$ project-list-facets
ConfigurationFacetImpl [org.jboss.forge.addon.configuration.ConfigurationFacetImpl@38bc685a]
MavenJavaCompilerFacet [org.jboss.forge.addon.maven.projects.facets.MavenJavaCompilerFacet@38bc685a]
MavenJavaSourceFacet [org.jboss.forge.addon.maven.projects.facets.MavenJavaSourceFacet@38bc685a]
MavenWebResourcesFacet [org.jboss.forge.addon.maven.projects.facets.MavenWebResourcesFacet@38bc685a]
MavenResourcesFacet [org.jboss.forge.addon.maven.projects.facets.MavenResourcesFacet@38bc685a]
MavenDependencyFacet [org.jboss.forge.addon.maven.projects.facets.MavenDependencyFacet@38bc685a]
MavenPackagingFacet [org.jboss.forge.addon.maven.projects.facets.MavenPackagingFacet@38bc685a]
MavenMetadataFacet [org.jboss.forge.addon.maven.projects.facets.MavenMetadataFacet@38bc685a]
MavenPluginFacetImpl [org.jboss.forge.addon.maven.projects.MavenPluginFacetImpl@38bc685a]
MavenFacetImpl [org.jboss.forge.addon.maven.projects.MavenFacetImpl@38bc685a]
{code}
And the output is kinda more of debug output that the end users cannot make sense of.
> project-list-dependencies command
> ---------------------------------
>
> Key: FORGE-2179
> URL: https://issues.jboss.org/browse/FORGE-2179
> Project: Forge
> Issue Type: Feature Request
> Affects Versions: 2.12.3.Final
> Reporter: Claus Ibsen
> Priority: Minor
>
> It would be good to have a command that can list all the project dependencies in a nice table structure that can be used from the shell.
> Today there is no such command.
> There is a project-has-dependencies which is rather useless, it requires the user to type in a group + artifact id, to see if its added or not, and you just get a kinda true|false response.
> When you work with a project, you often want to be able to add / remove dependencies, and therefore also want to see the current list. And also their scope etc, which are compile | test scoped etc.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years
[JBoss JIRA] (FORGE-2179) project-list-dependencies command
by Claus Ibsen (JIRA)
[ https://issues.jboss.org/browse/FORGE-2179?page=com.atlassian.jira.plugin... ]
Claus Ibsen commented on FORGE-2179:
------------------------------------
As a workaround today I use
more pom.xml
> project-list-dependencies command
> ---------------------------------
>
> Key: FORGE-2179
> URL: https://issues.jboss.org/browse/FORGE-2179
> Project: Forge
> Issue Type: Feature Request
> Affects Versions: 2.12.3.Final
> Reporter: Claus Ibsen
> Priority: Minor
>
> It would be good to have a command that can list all the project dependencies in a nice table structure that can be used from the shell.
> Today there is no such command.
> There is a project-has-dependencies which is rather useless, it requires the user to type in a group + artifact id, to see if its added or not, and you just get a kinda true|false response.
> When you work with a project, you often want to be able to add / remove dependencies, and therefore also want to see the current list. And also their scope etc, which are compile | test scoped etc.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years
[JBoss JIRA] (FORGE-2179) project-list-dependencies command
by Claus Ibsen (JIRA)
[ https://issues.jboss.org/browse/FORGE-2179?page=com.atlassian.jira.plugin... ]
Claus Ibsen updated FORGE-2179:
-------------------------------
Summary: project-list-dependencies command (was: project-has-dependencies command)
> project-list-dependencies command
> ---------------------------------
>
> Key: FORGE-2179
> URL: https://issues.jboss.org/browse/FORGE-2179
> Project: Forge
> Issue Type: Feature Request
> Affects Versions: 2.12.3.Final
> Reporter: Claus Ibsen
> Priority: Minor
>
> It would be good to have a command that can list all the project dependencies in a nice table structure that can be used from the shell.
> Today there is no such command.
> There is a project-has-dependencies which is rather useless, it requires the user to type in a group + artifact id, to see if its added or not, and you just get a kinda true|false response.
> When you work with a project, you often want to be able to add / remove dependencies, and therefore also want to see the current list. And also their scope etc, which are compile | test scoped etc.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years
[JBoss JIRA] (FORGE-2179) project-has-dependencies command
by Claus Ibsen (JIRA)
Claus Ibsen created FORGE-2179:
----------------------------------
Summary: project-has-dependencies command
Key: FORGE-2179
URL: https://issues.jboss.org/browse/FORGE-2179
Project: Forge
Issue Type: Feature Request
Affects Versions: 2.12.3.Final
Reporter: Claus Ibsen
Priority: Minor
It would be good to have a command that can list all the project dependencies in a nice table structure that can be used from the shell.
Today there is no such command.
There is a project-has-dependencies which is rather useless, it requires the user to type in a group + artifact id, to see if its added or not, and you just get a kinda true|false response.
When you work with a project, you often want to be able to add / remove dependencies, and therefore also want to see the current list. And also their scope etc, which are compile | test scoped etc.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years
[JBoss JIRA] (FORGE-2178) DependencyInstaller.install - Installs as managed dependency
by Claus Ibsen (JIRA)
Claus Ibsen created FORGE-2178:
----------------------------------
Summary: DependencyInstaller.install - Installs as managed dependency
Key: FORGE-2178
URL: https://issues.jboss.org/browse/FORGE-2178
Project: Forge
Issue Type: Bug
Affects Versions: 2.12.3.Final
Reporter: Claus Ibsen
Priority: Minor
I am developing a camel addon, and we have a command to enable Camel to a project.
So we use this code
{code}
@Override
public Result execute(UIExecutionContext context) throws Exception {
Project project = getSelectedProject(context);
// does the project already have camel?
Dependency core = findCamelCoreDependency(project);
if (core != null) {
return Results.success("Camel already enabled on project");
}
DependencyBuilder builder = DependencyBuilder.create().setGroupId("org.apache.camel").setArtifactId("camel-core");
if (version.getValue() != null) {
builder.setVersion(version.getValue());
}
core = builder;
// add camel-core
dependencyInstaller.install(project, core);
return Results.success("Added camel-core to project");
}
{code}
Notice we use
{code}
dependencyInstaller.install(project, core);
{code}
Which according to javadoc installs the dependency as non-managed. As there is a installManaged method for that.
But the pom.xml gets generated as managed,
{code}
[mydemo]$ more 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.mydemo</groupId>
<artifactId>mydemo</artifactId>
<version>1.0.0-SNAPSHOT</version>
<packaging>war</packaging>
<properties>
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
<maven.compiler.source>1.7</maven.compiler.source>
<maven.compiler.target>1.7</maven.compiler.target>
</properties>
<dependencyManagement>
<dependencies>
<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-core</artifactId>
<version>2.14.1</version>
</dependency>
</dependencies>
</dependencyManagement>
<dependencies>
<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-core</artifactId>
</dependency>
</dependencies>
<build>
<finalName>mydemo</finalName>
<plugins>
<plugin>
<artifactId>maven-war-plugin</artifactId>
<version>2.4</version>
<configuration>
<failOnMissingWebXml>false</failOnMissingWebXml>
</configuration>
</plugin>
</plugins>
</build>
</project>
{code}
Notice the dependencyManagement section in the pom.xml.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years
[JBoss JIRA] (FORGE-2047) Commands to add and remove Maven plugins into pom.xml
by Lincoln Baxter III (JIRA)
[ https://issues.jboss.org/browse/FORGE-2047?page=com.atlassian.jira.plugin... ]
Lincoln Baxter III commented on FORGE-2047:
-------------------------------------------
The maven-impl-projects project is probably the right place for this; however, I think we do need to qualify this as a maven plugin:
So the name of the command should probably be:
"project-add-maven-plugin"
"project-remove-maven-plugin"
Because I don't think this will work for anything other than maven plugins. And if it's going to live in the maven project, it needs to be clear that it's not a general purpose thing. The description and help verbiage should also reflect this.
> Commands to add and remove Maven plugins into pom.xml
> -----------------------------------------------------
>
> Key: FORGE-2047
> URL: https://issues.jboss.org/browse/FORGE-2047
> Project: Forge
> Issue Type: Sub-task
> Components: UI - Shell
> Affects Versions: 2.10.1.Final
> Reporter: Antonio Goncalves
> Labels: starter
> Fix For: 2.x Future
>
>
> Today we have commands to add/remove dependencies into a `pom.xml` :
> {code}
> project-add-dependencies
> project-remove-dependencies
> project-add-managed-dependencies
> project-remove-managed-dependencies
> {code}
> We need to same functionnalites but for plugins. Commands such as :
> {code}
> project-add-plugin-dependencies
> project-remove-plugin-dependencies
> {code}
> So a command like this :
> {code}
> project-add-plugin-dependencies org.codehaus.mojo:exec-maven-plugin:1.3.1
> {code}
> Would add the following to the {{pom.xml}} :
> {code}
> <plugins>
> <plugin>
> <groupId>org.codehaus.mojo</groupId>
> <artifactId>exec-maven-plugin</artifactId>
> <version>1.3.1</version>
> </plugin>
> </plugins>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years