August 2014 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-1488) Build command does not display build's log

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1488?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1488. ---------------------------------- Assignee: George Gastaldi (was: Ricardo Martinelli Oliveira) Fix Version/s: 2.7.3.Final (was: 2.x Future) Resolution: Done Sorry [~rimolive], I had to fix this :) > Build command does not display build's log > ------------------------------------------ > > Key: FORGE-1488 > URL: https://issues.jboss.org/browse/FORGE-1488 > Project: Forge > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Build Tools - Maven > Affects Versions: 2.0.0.CR1 > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 2.7.3.Final > > > {code} > [bin]$ cd demo > [demo]$ build > ***SUCCESS*** Build Success > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1973) Introduce a --quiet flag to Build command

by George Gastaldi (JIRA)

George Gastaldi created FORGE-1973: -------------------------------------- Summary: Introduce a --quiet flag to Build command Key: FORGE-1973 URL: https://issues.jboss.org/browse/FORGE-1973 Project: Forge Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Build Tools - Maven Affects Versions: 2.7.2.Final Reporter: George Gastaldi Priority: Trivial Fix For: 2.x Future If the user wants to skip the build output log. Maven uses the {{--quiet}} flag for that, so it's just a matter of adding it to the argument list -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1488) Build command does not display build's log

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1488?page=com.atlassian.jira.plugin... ] George Gastaldi commented on FORGE-1488: ---------------------------------------- Created another issue for the flag: FORGE-1973 > Build command does not display build's log > ------------------------------------------ > > Key: FORGE-1488 > URL: https://issues.jboss.org/browse/FORGE-1488 > Project: Forge > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Build Tools - Maven > Affects Versions: 2.0.0.CR1 > Reporter: George Gastaldi > Assignee: Ricardo Martinelli Oliveira > Fix For: 2.x Future > > > {code} > [bin]$ cd demo > [demo]$ build > ***SUCCESS*** Build Success > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1341) Support Eclipse Undo/Redo operations

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1341?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1341. ---------------------------------- Fix Version/s: (was: 2.x Future) Resolution: Won't Fix Marking as "Won't Fix". Reopen if needed > Support Eclipse Undo/Redo operations > ------------------------------------ > > Key: FORGE-1341 > URL: https://issues.jboss.org/browse/FORGE-1341 > Project: Forge > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Brainstorming, UI - Eclipse > Affects Versions: 2.0.0.Beta3 > Reporter: George Gastaldi > > {quote} > <gastaldi> koentsje, is it possible to undo the operations done by a Forge addon using the Eclipse Undo feature (Edit -> Undo) ? > <gastaldi> can we somehow make the current plugin aware of this? > <koentsje> hm, i think that will be a very tough one > <gastaldi> I am reading http://help.eclipse.org/indigo/index.jsp?topic=%2Forg.eclipse.platform.do... to understand how undoable operations work in Eclipse > <gastaldi> It would be nice if we could somehow store a Delta of the modifications an addon does > <gastaldi> so it's possible to undo/redo operations > <koentsje> i would need to revisit that mechanism, it's probably five years ago since i used it :) > <gastaldi> can we somehow create savepoints in Eclipse ? > <gastaldi> at least you used it, this is totally new for me :) > <koentsje> yes it should be possible > <gastaldi> so I was thinking that maybe we could create a snapshot of the current project state before executing an operation, execute the addon, create another snapshot and then compare both to have a delta > <gastaldi> this in turn could be undo/redoable > <gastaldi> this could aid us in implementing the Accept Merges feature too > <gastaldi> duh > <gastaldi> Accept Changes > <gastaldi> however that is a different subject > <koentsje> the resource delta stuff exists already in eclipse > <gastaldi> this is interesting, so it should be possible as you said > <gastaldi> this would motivate people to use Forge inside Eclipse > <koentsje> hm, i thought we went through all the ide pain because people want to use it in their ide? :) > <gastaldi> yeah, that's the spirit :) > {quote} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1727) Add PathResource based on the Java 7 NIO Files API

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1727?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1727. ---------------------------------- Fix Version/s: 3.0.0.Alpha1 (was: 3.x Future) Resolution: Done > Add PathResource based on the Java 7 NIO Files API > -------------------------------------------------- > > Key: FORGE-1727 > URL: https://issues.jboss.org/browse/FORGE-1727 > Project: Forge > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Resources > Affects Versions: 2.3.0.Final > Reporter: Shane Bryzak > Assignee: Shane Bryzak > Fix For: 3.0.0.Alpha1 > > > Also update all addons to use this. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (FORGE-331) Get online help from plugin's javadoc

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-331?page=com.atlassian.jira.plugin.... ] George Gastaldi closed FORGE-331. --------------------------------- Fix Version/s: (was: 2.x Future) Resolution: Won't Fix We already generate a "man" page for the commands dynamically, based on the command parameters > Get online help from plugin's javadoc > ------------------------------------- > > Key: FORGE-331 > URL: https://issues.jboss.org/browse/FORGE-331 > Project: Forge > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Plugin API > Reporter: Jonathan Fuerth > Priority: Minor > > IDEs already have lots of great tooling to help write good javadoc and keep it neatly formatted and up to date. It would be excellent if forge's source of help text for plugins came straight from the javadoc. This could be done either via a doclet that operates on the Java source code, or by scraping the output of the default doclet (like Eclipse will do if you attach generated JavaDoc rather than library source code). > Lowering the barrier to providing high-quality documentation should help encourage plugin authors to provide good help, and in turn that should help everyone pick up and learn Forge faster. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1226) API to manipulate JavaDoc

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1226?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1226. ---------------------------------- Fix Version/s: (was: 2.x Future) Resolution: Duplicate Issue Duplicate of ROASTER-28 > API to manipulate JavaDoc > ------------------------- > > Key: FORGE-1226 > URL: https://issues.jboss.org/browse/FORGE-1226 > Project: Forge > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Parsers / File Manipulation > Affects Versions: 2.0.0.Alpha12 > Reporter: Michael Schwartz > Priority: Minor > > I would like to manipulate - namely read, insert and modify javadoc at class-, field- and method-level. > The underlying AST library supports this however forge does not currently. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1867) Enable sorting of UIInputs added to UIBuilder

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1867?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1867. ---------------------------------- Fix Version/s: (was: 2.x Future) Resolution: Won't Fix Marking as "Won't fix", since there isn't a use case for this > Enable sorting of UIInputs added to UIBuilder > --------------------------------------------- > > Key: FORGE-1867 > URL: https://issues.jboss.org/browse/FORGE-1867 > Project: Forge > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: UI - API > Affects Versions: 2.6.0.Final > Reporter: Lincoln Baxter III > Priority: Minor > Labels: starter > > builder.add(input1).add(input2).add(input3).sort(new Sorter() {...}) -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1107) Avoiding setters in DependencyBuilder

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1107?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1107. ---------------------------------- Fix Version/s: (was: 2.x Future) Resolution: Won't Fix As described by [~lincolnthree], that might introduce API changes and unnecessary builders > Avoiding setters in DependencyBuilder > ------------------------------------- > > Key: FORGE-1107 > URL: https://issues.jboss.org/browse/FORGE-1107 > Project: Forge > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Plugin API > Affects Versions: 2.0.0.Alpha10 > Environment: DependencyBuilder Class > Reporter: Rajmahendra Hegde > Priority: Minor > > As the name suggests "Builder" we can better remove some of general setter naming of the properties like > setGroupId > setArtifactId > setVersion > etc > and make them > groupId > artifactId > version > etc > So its easy to type. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (FORGE-908) LinkageError while using ShrinkWrap classes in Arquillian

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-908?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III commented on FORGE-908: ------------------------------------------ This was an internal bug that was fixed in Forge. The way to avoid this is "don't import any additional copies of shrinkwrap or arquillian into the test case" > LinkageError while using ShrinkWrap classes in Arquillian > --------------------------------------------------------- > > Key: FORGE-908 > URL: https://issues.jboss.org/browse/FORGE-908 > Project: Forge > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Java EE > Affects Versions: 2.0.0.Alpha4 > Reporter: George Gastaldi > Assignee: Lincoln Baxter III > Fix For: 2.0.0.Alpha5 > > > In javaee-tests, if you remove the @Ignore from the test test.org.jboss.forge.javaee.servlet.ServletFacetTest.testWebXMLCreatedWhenInstalled() you get the following exception: > {code} > Caused by: java.lang.LinkageError: loader constraint violation: loader (instance of org/jboss/modules/ModuleClassLoader) previously initiated loading for a different type with name "org/jboss/shrinkwrap/descriptor/api/webapp30/WebAppDescriptor" > at java.lang.ClassLoader.defineClass1(Native Method) > at java.lang.ClassLoader.defineClassCond(ClassLoader.java:631) > at java.lang.ClassLoader.defineClass(ClassLoader.java:615) > at org.jboss.modules.ModuleClassLoader.doDefineOrLoadClass(ModuleClassLoader.java:344) > at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:422) > at org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:260) > at org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:75) > at org.jboss.modules.Module.loadModuleClass(Module.java:528) > at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:188) > at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:444) > at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:432) > at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:399) > at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:374) > at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:119) > at test.org.jboss.forge.javaee.servlet.ServletFacetTest.testWebXMLCreatedWhenInstalled(ServletFacetTest.java:63) > ... 88 more > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues August 2014