[JBoss JIRA] (FORGE-2230) CoordinateBuilder should set null for empty parts of G:A:P:C:V
by Ondrej Zizka (JIRA)
[ https://issues.jboss.org/browse/FORGE-2230?page=com.atlassian.jira.plugin... ]
Ondrej Zizka updated FORGE-2230:
--------------------------------
Description:
CoordinateBuilder, when given "G:A:::V", should set P and C to null. Having them empty strings is no good.
Consider machine-provided lists contaning:
org.foo:foo-bar:::4.1.2
This should end with the same result as parsing
org.foo:foo-bar:4.1.2
whereas it ends up with P and C set to empty strings, and forces the user of the api to do extra check for an empty string value.
Related:
"Malformed coordinate. Should be groupId:artifactId:[packaging]:[classifier]:[version]");
should read
"Malformed coordinate. Should be groupId:artifactId:[packaging:[classifier:]][version]");
was:
CoordinateBuilder, when given "G:A:::V", should set P and C to null. Having them empty strings is no good.
Consider machine-provided lists contaning:
org.foo:foo-bar:::4.1.2
This should end with the same result as parsing
org.foo:foo-bar:4.1.2
whereas it ends up with P and C set to empty strings, and forces the user of the api to do extra check for an empty string value.
> CoordinateBuilder should set null for empty parts of G:A:P:C:V
> --------------------------------------------------------------
>
> Key: FORGE-2230
> URL: https://issues.jboss.org/browse/FORGE-2230
> Project: Forge
> Issue Type: Enhancement
> Components: Dependencies
> Affects Versions: 2.14.0.Final
> Reporter: Ondrej Zizka
>
> CoordinateBuilder, when given "G:A:::V", should set P and C to null. Having them empty strings is no good.
> Consider machine-provided lists contaning:
> org.foo:foo-bar:::4.1.2
> This should end with the same result as parsing
> org.foo:foo-bar:4.1.2
> whereas it ends up with P and C set to empty strings, and forces the user of the api to do extra check for an empty string value.
> Related:
> "Malformed coordinate. Should be groupId:artifactId:[packaging]:[classifier]:[version]");
> should read
> "Malformed coordinate. Should be groupId:artifactId:[packaging:[classifier:]][version]");
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 4 months
[JBoss JIRA] (FORGE-2230) CoordinateBuilder should set null for empty parts of G:A:P:C:V
by Ondrej Zizka (JIRA)
[ https://issues.jboss.org/browse/FORGE-2230?page=com.atlassian.jira.plugin... ]
Ondrej Zizka updated FORGE-2230:
--------------------------------
Component/s: Dependencies
> CoordinateBuilder should set null for empty parts of G:A:P:C:V
> --------------------------------------------------------------
>
> Key: FORGE-2230
> URL: https://issues.jboss.org/browse/FORGE-2230
> Project: Forge
> Issue Type: Enhancement
> Components: Dependencies
> Affects Versions: 2.14.0.Final
> Reporter: Ondrej Zizka
>
> CoordinateBuilder, when given "G:A:::V", should set P and C to null. Having them empty strings is no good.
> Consider machine-provided lists contaning:
> org.foo:foo-bar:::4.1.2
> This should end with the same result as parsing
> org.foo:foo-bar:4.1.2
> whereas it ends up with P and C set to empty strings, and forces the user of the api to do extra check for an empty string value.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 4 months
[JBoss JIRA] (FORGE-2230) CoordinateBuilder should set null for empty parts of G:A:P:C:V
by Ondrej Zizka (JIRA)
[ https://issues.jboss.org/browse/FORGE-2230?page=com.atlassian.jira.plugin... ]
Ondrej Zizka updated FORGE-2230:
--------------------------------
Affects Version/s: 2.14.0.Final
> CoordinateBuilder should set null for empty parts of G:A:P:C:V
> --------------------------------------------------------------
>
> Key: FORGE-2230
> URL: https://issues.jboss.org/browse/FORGE-2230
> Project: Forge
> Issue Type: Enhancement
> Affects Versions: 2.14.0.Final
> Reporter: Ondrej Zizka
>
> CoordinateBuilder, when given "G:A:::V", should set P and C to null. Having them empty strings is no good.
> Consider machine-provided lists contaning:
> org.foo:foo-bar:::4.1.2
> This should end with the same result as parsing
> org.foo:foo-bar:4.1.2
> whereas it ends up with P and C set to empty strings, and forces the user of the api to do extra check for an empty string value.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 4 months
[JBoss JIRA] (FORGE-2230) CoordinateBuilder should set null for empty parts of G:A:P:C:V
by Ondrej Zizka (JIRA)
Ondrej Zizka created FORGE-2230:
-----------------------------------
Summary: CoordinateBuilder should set null for empty parts of G:A:P:C:V
Key: FORGE-2230
URL: https://issues.jboss.org/browse/FORGE-2230
Project: Forge
Issue Type: Enhancement
Reporter: Ondrej Zizka
CoordinateBuilder, when given "G:A:::V", should set P and C to null. Having them empty strings is no good.
Consider machine-provided lists contaning:
org.foo:foo-bar:::4.1.2
This should end with the same result as parsing
org.foo:foo-bar:4.1.2
whereas it ends up with P and C set to empty strings, and forces the user of the api to do extra check for an empty string value.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 4 months
[JBoss JIRA] (FORGEPLUGINS-115) Wildfly/AS plugin should be able to "run" the current application
by Jérémie Lagarde (JIRA)
[ https://issues.jboss.org/browse/FORGEPLUGINS-115?page=com.atlassian.jira.... ]
Jérémie Lagarde commented on FORGEPLUGINS-115:
----------------------------------------------
I'm not sure if I understand this request.
By "run" you mean :
1) build the application ('build' forge command)
2) start the server ('as-start' forge command)
3) deploy the application ('as-deploy' forge command)
4) browse the deployment directory ('open target/wildfly-dist/standalone/deployments/' forge command)
Can you clarify this?
Regards,
Jérémie
> Wildfly/AS plugin should be able to "run" the current application
> -----------------------------------------------------------------
>
> Key: FORGEPLUGINS-115
> URL: https://issues.jboss.org/browse/FORGEPLUGINS-115
> Project: Forge Plugins/Addons
> Issue Type: Bug
> Components: JBoss AS Plugin
> Reporter: Lincoln Baxter III
> Assignee: James Perkins
> Priority: Minor
>
> This would involve starting the server, doing a deployment, reporting errors, and opening the default browser to the correct deployment path.
> New file changes should be sync'd to the deployment (exploded deployment,) and debug mode should pick up the new changes.
> Shutdown would also be required.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 4 months