November 2013 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-1245) Importer+#requiresImport() should return false for types in same package

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1245?page=com.atlassian.jira.plugin... ] George Gastaldi reopened FORGE-1245: ------------------------------------ > Importer+#requiresImport() should return false for types in same package > ------------------------------------------------------------------------ > > Key: FORGE-1245 > URL: https://issues.jboss.org/browse/FORGE-1245 > Project: Forge > Issue Type: Feature Request > Components: Parsers / File Manipulation > Affects Versions: 2.x Future > Reporter: Matt Benson > Assignee: Matt Benson > Fix For: 2.x Future > > > The simple approach of comparing the package name of the Importer to the longest subsequence before any final dot in the name of the proposed import should suffice: the only exceptional case should be inner classes, which would require an import in any case in order to refer to one such by its simple name. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (FORGE-1249) JavaAnnotationImpl should not implement InterfaceCapable

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1249?page=com.atlassian.jira.plugin... ] George Gastaldi resolved FORGE-1249. ------------------------------------ Fix Version/s: 2.x Future (was: 2.0.0.Beta4) Resolution: Done > JavaAnnotationImpl should not implement InterfaceCapable > -------------------------------------------------------- > > Key: FORGE-1249 > URL: https://issues.jboss.org/browse/FORGE-1249 > Project: Forge > Issue Type: Feature Request > Components: Parsers / File Manipulation > Affects Versions: 2.x Future > Reporter: Matt Benson > Assignee: Matt Benson > Fix For: 2.x Future > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (FORGE-1245) Importer+#requiresImport() should return false for types in same package

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1245?page=com.atlassian.jira.plugin... ] George Gastaldi resolved FORGE-1245. ------------------------------------ Resolution: Done > Importer+#requiresImport() should return false for types in same package > ------------------------------------------------------------------------ > > Key: FORGE-1245 > URL: https://issues.jboss.org/browse/FORGE-1245 > Project: Forge > Issue Type: Feature Request > Components: Parsers / File Manipulation > Affects Versions: 2.x Future > Reporter: Matt Benson > Assignee: Matt Benson > Fix For: 2.x Future > > > The simple approach of comparing the package name of the Importer to the longest subsequence before any final dot in the name of the proposed import should suffice: the only exceptional case should be inner classes, which would require an import in any case in order to refer to one such by its simple name. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (FORGE-1244) Types.isJavaLang() returns true for types in java.lang subpackages

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1244?page=com.atlassian.jira.plugin... ] George Gastaldi reopened FORGE-1244: ------------------------------------ > Types.isJavaLang() returns true for types in java.lang subpackages > ------------------------------------------------------------------ > > Key: FORGE-1244 > URL: https://issues.jboss.org/browse/FORGE-1244 > Project: Forge > Issue Type: Feature Request > Components: Parsers / File Manipulation > Affects Versions: 2.x Future > Reporter: Matt Benson > Assignee: Matt Benson > Fix For: 2.x Future > > > Since this method is used to implement Importer#requiresImport(), it leads to incorrect results. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (FORGE-796) Refactor JavaParser to distinguish between Mutable and Immutable Type Models in a typesafe way

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-796?page=com.atlassian.jira.plugin.... ] George Gastaldi resolved FORGE-796. ----------------------------------- Fix Version/s: 2.x Future (was: 2.0.0.Final) Resolution: Done > Refactor JavaParser to distinguish between Mutable and Immutable Type Models in a typesafe way > ---------------------------------------------------------------------------------------------- > > Key: FORGE-796 > URL: https://issues.jboss.org/browse/FORGE-796 > Project: Forge > Issue Type: Feature Request > Components: Parsers / File Manipulation > Reporter: Lincoln Baxter III > Assignee: Matt Benson > Fix For: 2.x Future > > > The Java Parser Type Hierarchy should support Read-only and writeable Types. Thus we could implement the Parser using things like Java Reflection for Read-only access, or with Javassist CtClass / Apache BCEL for reading and writing .class files. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (FORGE-1248) Redesign parser generics API: permit management of type variable bounds

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1248?page=com.atlassian.jira.plugin... ] George Gastaldi resolved FORGE-1248. ------------------------------------ Resolution: Done > Redesign parser generics API: permit management of type variable bounds > ----------------------------------------------------------------------- > > Key: FORGE-1248 > URL: https://issues.jboss.org/browse/FORGE-1248 > Project: Forge > Issue Type: Feature Request > Components: Parsers / File Manipulation > Affects Versions: 2.x Future > Reporter: Matt Benson > Assignee: Matt Benson > Fix For: 2.x Future > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (FORGE-1250) All Java types are not necessarily MemberHolders

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1250?page=com.atlassian.jira.plugin... ] George Gastaldi resolved FORGE-1250. ------------------------------------ Resolution: Done > All Java types are not necessarily MemberHolders > ------------------------------------------------ > > Key: FORGE-1250 > URL: https://issues.jboss.org/browse/FORGE-1250 > Project: Forge > Issue Type: Feature Request > Components: Parsers / File Manipulation > Affects Versions: 2.x Future > Reporter: Matt Benson > Assignee: Matt Benson > Fix For: 2.x Future > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (FORGE-796) Refactor JavaParser to distinguish between Mutable and Immutable Type Models in a typesafe way

by Matt Benson (JIRA)

[ https://issues.jboss.org/browse/FORGE-796?page=com.atlassian.jira.plugin.... ] Work on FORGE-796 started by Matt Benson. > Refactor JavaParser to distinguish between Mutable and Immutable Type Models in a typesafe way > ---------------------------------------------------------------------------------------------- > > Key: FORGE-796 > URL: https://issues.jboss.org/browse/FORGE-796 > Project: Forge > Issue Type: Feature Request > Components: Parsers / File Manipulation > Reporter: Lincoln Baxter III > Assignee: Matt Benson > Fix For: 2.0.0.Final > > > The Java Parser Type Hierarchy should support Read-only and writeable Types. Thus we could implement the Parser using things like Java Reflection for Read-only access, or with Javassist CtClass / Apache BCEL for reading and writing .class files. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

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

by George Gastaldi (JIRA)

George Gastaldi created FORGE-1341: -------------------------------------- Summary: Support Eclipse Undo/Redo operations Key: FORGE-1341 URL: https://issues.jboss.org/browse/FORGE-1341 Project: Forge Issue Type: Feature Request Components: Brainstorming, UI - Eclipse Affects Versions: 2.0.0.Beta3 Reporter: George Gastaldi Fix For: 2.0.0.Beta4 {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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (FORGE-1321) Failure to install addons when using secure repositories

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-1321?page=com.atlassian.jira.plugin... ] Vineet Reynolds edited comment on FORGE-1321 at 11/27/13 1:56 AM: ------------------------------------------------------------------ [~gastaldi], I was able to reproduce this against my local Nexus instance. I got this stacktrace dumped on the error: {noformat} Downloading: http://localhost:8081/nexus/content/groups/public/org/jboss/forge/addon/p... java.lang.RuntimeException: org.eclipse.aether.resolution.DependencyResolutionException: The following artifacts could not be resolved: org.jboss.forge.addon:configuration:jar:forge-addon:2.0.0-SNAPSHOT, org.jboss.forge.addon:configuration-api:jar:2.0.0-SNAPSHOT, org.jboss.forge.addon:configuration-impl:jar:2.0.0-SNAPSHOT, org.jboss.forge.addon:resources:jar:forge-addon:2.0.0-SNAPSHOT, org.jboss.forge.addon:projects:jar:forge-addon:2.0.0-SNAPSHOT: Could not transfer artifact org.jboss.forge.addon:configuration:jar:forge-addon:2.0.0-20131120.220705-132 from/to nexus-local-repo (http://localhost:8081/nexus/content/groups/public/): Access denied to: http://localhost:8081/nexus/content/groups/public/org/jboss/forge/addon/c... at org.jboss.forge.furnace.manager.maven.addon.MavenAddonDependencyResolver.resolveResources(MavenAddonDependencyResolver.java:105) 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.LockManagerImpl.performLocked(LockManagerImpl.java:48) 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.bootstrap.Bootstrap.install(Bootstrap.java:229) at org.jboss.forge.bootstrap.Bootstrap.<init>(Bootstrap.java:147) at org.jboss.forge.bootstrap.Bootstrap.main(Bootstrap.java:91) {noformat} But I'd like to state that this is most likely an issue with older Maven metadata present in the .m2/repository directory. Or it has something to do with incorrect server settings that ought to be removed from settings.xml (unnecessary entries do not cause any issue from what I've seen). Going by the Lightweight HTTP wagon internals, unnecessary entries do not cause any issue. With the lightweight HTTP wagon, the passwords are used only when a challenge is issued. The URLConnection and Authenticator classes in the JRE work together to request the password retrieved from the settings.xml (which is done only when the server requires authentication and not otherwise). We could treat this issue as resolved. was (Author: vineet.reynolds): [~gastaldi], I was able to reproduce this against my local Nexus instance. I got this stacktrace dumped on the error: {noformat} Downloading: http://localhost:8081/nexus/content/groups/public/org/jboss/forge/addon/p... java.lang.RuntimeException: org.eclipse.aether.resolution.DependencyResolutionException: The following artifacts could not be resolved: org.jboss.forge.addon:configuration:jar:forge-addon:2.0.0-SNAPSHOT, org.jboss.forge.addon:configuration-api:jar:2.0.0-SNAPSHOT, org.jboss.forge.addon:configuration-impl:jar:2.0.0-SNAPSHOT, org.jboss.forge.addon:resources:jar:forge-addon:2.0.0-SNAPSHOT, org.jboss.forge.addon:projects:jar:forge-addon:2.0.0-SNAPSHOT: Could not transfer artifact org.jboss.forge.addon:configuration:jar:forge-addon:2.0.0-20131120.220705-132 from/to nexus-local-repo (http://localhost:8081/nexus/content/groups/public/): Access denied to: http://localhost:8081/nexus/content/groups/public/org/jboss/forge/addon/c... at org.jboss.forge.furnace.manager.maven.addon.MavenAddonDependencyResolver.resolveResources(MavenAddonDependencyResolver.java:105) 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.LockManagerImpl.performLocked(LockManagerImpl.java:48) 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.bootstrap.Bootstrap.install(Bootstrap.java:229) at org.jboss.forge.bootstrap.Bootstrap.<init>(Bootstrap.java:147) at org.jboss.forge.bootstrap.Bootstrap.main(Bootstrap.java:91) {noformat} Going by this, and the Lightweight HTTP wagon internals, I'd concur that unnecessary or incorrect server settings should be removed from settings.xml. With the lightweight HTTP wagon, the passwords are used only when a challenge is issued. For some reason, the URLConnection and Authenticator classes in the JRE work together to request the password retrieved from the settings.xml (which is done only when the server requires authentication; obviously the server requested authentication even though anonymous access was sufficient). > Failure to install addons when using secure repositories > -------------------------------------------------------- > > Key: FORGE-1321 > URL: https://issues.jboss.org/browse/FORGE-1321 > Project: Forge > Issue Type: Bug > Components: Build Tools - Maven > Affects Versions: 2.0.0.Beta3 > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > Fix For: 2.0.0.Beta4 > > > After FORGE-1307, Forge seems to be able to access secure repositories, but fails to install the addon: > {noformat} > forge-distribution-2.0.0.Beta2$ ./bin/forge --install shell > Using Forge at forge-distribution-2.0.0.Beta2 > Warning: JAVA_HOME environment variable is not set. > Downloading: http://xxxxxx/artifactory/repo/org/jboss/forge/addon/shell/maven-metadata... > Downloading: http://xxxxxx/artifactory/repo/org/jboss/forge/addon/shell/maven-metadata... > java.lang.IllegalArgumentException: No Artifact version found for org.jboss.forge.addon:shell > at org.jboss.forge.bootstrap.Bootstrap.install(Bootstrap.java:199) > at org.jboss.forge.bootstrap.Bootstrap.<init>(Bootstrap.java:144) > at org.jboss.forge.bootstrap.Bootstrap.main(Bootstrap.java:88) > > Forge version [2.0.0.Beta1] > {noformat} > The Artifactory repository used this feature: http://www.jfrog.com/confluence/display/RTF/Centrally+Secure+Passwords > Additional info: > {noformat} > <dbeer> think I have found part of issue I have removed security constraint briefly from our server and is now downloading a load of forge addon snapshots, will investigate the security further tomorrow > {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues November 2013