April 2013 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-860) Forge should not allow addition of repositories pointing to the same file location

by George Gastaldi (JIRA)

George Gastaldi created FORGE-860: ------------------------------------- Summary: Forge should not allow addition of repositories pointing to the same file location Key: FORGE-860 URL: https://issues.jboss.org/browse/FORGE-860 Project: Forge Issue Type: Feature Request Components: Container Affects Versions: 2.0.0.Alpha2 Reporter: George Gastaldi Fix For: 2.0.0.Alpha3 -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-859) ACCEPT_DEFAULTS should be more fine grained

by Lincoln Baxter III (JIRA)

Lincoln Baxter III created FORGE-859: ---------------------------------------- Summary: ACCEPT_DEFAULTS should be more fine grained Key: FORGE-859 URL: https://issues.jboss.org/browse/FORGE-859 Project: Forge Issue Type: Enhancement Components: UI - Shell, Usability Affects Versions: 1.2.3.Final Reporter: Lincoln Baxter III Fix For: 1.2.4.Final, 2.0.0.Alpha1 01:19:24 PM) Pete Muir: also, the other one i wanted to ask about (01:19:29 PM) Pete Muir: was the ACCEPT_DEFAULTS thing (01:19:34 PM) Pete Muir: atm it's a little to coarse (01:19:42 PM) Pete Muir: i want to accept quite a lot of defaults, but not all of them (01:19:58 PM) Pete Muir: e.g. i want to accept default versions (01:20:06 PM) Pete Muir: but perhaps not questions about scaffolding (01:20:17 PM) Pete Muir: perhaps this needs to be an enum, not a true/false (01:21:39 PM) Lincoln: possible to do but would require converting the accept default functionality to an enum or value based check (01:22:24 PM) Pete Muir: consider it (01:22:33 PM) Pete Muir: because atm running without accept defaults is painful (01:22:41 PM) Pete Muir: but with it, you miss critical questions (01:23:26 PM) Lincoln: most questions are engineered for safe use of <ENTER> (01:23:30 PM) Lincoln: prompts (01:23:35 PM) Pete Muir: yeah (01:23:37 PM) Pete Muir: but some aren't -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGEPLUGINS-84) Create a VRaptor plugin

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGEPLUGINS-84?page=com.atlassian.jira.p... ] George Gastaldi closed FORGEPLUGINS-84. --------------------------------------- Resolution: Done Plugin created and added to repository.yaml > Create a VRaptor plugin > ----------------------- > > Key: FORGEPLUGINS-84 > URL: https://issues.jboss.org/browse/FORGEPLUGINS-84 > Project: Forge Plugins > Issue Type: Feature Request > Reporter: George Gastaldi > Assignee: Rubens Saraiva > > It would be interesting to create a scaffold and a specific plugin for dealing with the VRaptor framework (http://vraptor.caelum.com.br/) -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-820) No XPathFactory implementation found inside a forge addon

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-820?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-820: ---------------------------------- Fix Version/s: 2.0.0.Final (was: 2.0.0.Alpha1) > No XPathFactory implementation found inside a forge addon > --------------------------------------------------------- > > Key: FORGE-820 > URL: https://issues.jboss.org/browse/FORGE-820 > Project: Forge > Issue Type: Bug > Components: Container > Affects Versions: 2.0.0.Alpha1 > Reporter: George Gastaldi > Fix For: 2.0.0.Final > > > The following test fails: > {code:java} > @RunWith(Arquillian.class) > public class XPathContainerTest > { > @Deployment > public static ForgeArchive getDeployment() > { > ForgeArchive archive = ShrinkWrap.create(ForgeArchive.class) > .addClasses(XPathContainerTest.class) > .addBeansXML(); > return archive; > } > @Test > public void testContainerStartup() > { > Assert.assertNotNull(XPathFactory.newInstance().newXPath()); > } > } > {code} -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-857) Forge 1 Configuration Folder should be configurable

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-857?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-857: ---------------------------------- Forum Reference: https://community.jboss.org/message/807965 > Forge 1 Configuration Folder should be configurable > --------------------------------------------------- > > Key: FORGE-857 > URL: https://issues.jboss.org/browse/FORGE-857 > Project: Forge > Issue Type: Feature Request > Affects Versions: 1.2.3.Final > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 1.2.4.Final > > -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-857) Forge 1 Configuration Folder should be configurable

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-857?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-857: ---------------------------------- Component/s: Init Scripts > Forge 1 Configuration Folder should be configurable > --------------------------------------------------- > > Key: FORGE-857 > URL: https://issues.jboss.org/browse/FORGE-857 > Project: Forge > Issue Type: Feature Request > Components: Init Scripts > Affects Versions: 1.2.3.Final > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 1.2.4.Final > > -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-858) Forge can't find dependencies from Maven Central if there is an active profile with repository setup in settings.xml

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-858?page=com.atlassian.jira.plugin.... ] George Gastaldi closed FORGE-858. --------------------------------- Fix Version/s: 1.2.4.Final Resolution: Done Fixed > Forge can't find dependencies from Maven Central if there is an active profile with repository setup in settings.xml > -------------------------------------------------------------------------------------------------------------------- > > Key: FORGE-858 > URL: https://issues.jboss.org/browse/FORGE-858 > Project: Forge > Issue Type: Bug > Components: Maven Integration > Affects Versions: 1.2.3.Final > Reporter: Tomas Repel > Assignee: George Gastaldi > Fix For: 1.2.4.Final > > > It seems that Forge does not recognize the dependencies form Maven Central. This happens when there is an active profile with some repository setup in settings.xml file. > I experience this when using Forge with Ticket Monster (https://github.com/jboss-jdf/ticket-monster) and empty maven local repository. > settings.xml snippet: > {noformat} > </profiles> > <profile> > <id>test-profile</id> > <repositories> > <repository> > <id>obsolete-enterprise-repository</id> > <name>Obsolete Enterprise Repository</name> > <url>file:///home/trepel/maven/some-repo-with-missing-dependencies</url> > <layout>default</layout> > <releases> > <enabled>true</enabled> > <updatePolicy>never</updatePolicy> > </releases> > <snapshots> > <enabled>false</enabled> > <updatePolicy>never</updatePolicy> > </snapshots> > </repository> > </repositories> > </profile> > </profiles> > <activeProfiles> > <activeProfile>test-profile</activeProfile> > </activeProfiles> > {noformat} > Running Forge in ticket-monster/demo directory results in following: > {noformat} > Using Forge at /home/trepel/workspace/apps/forge-distribution-1.2.3.Final > _____ > | ___|__ _ __ __ _ ___ > | |_ / _ \| `__/ _` |/ _ \ \\ > | _| (_) | | | (_| | __/ // > |_| \___/|_| \__, |\___| > |___/ > > Error during Startup event > org.jboss.forge.project.ProjectModelException: org.apache.maven.project.ProjectBuildingException: 29 problems were encountered while building the effective model for org.jboss.jdf.examples:ticket-monster:2.1.2-SNAPSHOT > [ERROR] Non-resolvable import POM: Could not find artifact org.jboss.bom:jboss-javaee-6.0-with-tools:pom:1.0.5.CR2 in obsolete-enterprise-repository (file:///home/trepel/maven/some-repo-with-missing-dependencies) @ line 50, column 25 > {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, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-858) Forge can't find dependencies from Maven Central if there is an active profile with repository setup in settings.xml

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-858?page=com.atlassian.jira.plugin.... ] Work on FORGE-858 started by George Gastaldi. > Forge can't find dependencies from Maven Central if there is an active profile with repository setup in settings.xml > -------------------------------------------------------------------------------------------------------------------- > > Key: FORGE-858 > URL: https://issues.jboss.org/browse/FORGE-858 > Project: Forge > Issue Type: Bug > Components: Maven Integration > Affects Versions: 1.2.3.Final > Reporter: Tomas Repel > Assignee: George Gastaldi > > It seems that Forge does not recognize the dependencies form Maven Central. This happens when there is an active profile with some repository setup in settings.xml file. > I experience this when using Forge with Ticket Monster (https://github.com/jboss-jdf/ticket-monster) and empty maven local repository. > settings.xml snippet: > {noformat} > </profiles> > <profile> > <id>test-profile</id> > <repositories> > <repository> > <id>obsolete-enterprise-repository</id> > <name>Obsolete Enterprise Repository</name> > <url>file:///home/trepel/maven/some-repo-with-missing-dependencies</url> > <layout>default</layout> > <releases> > <enabled>true</enabled> > <updatePolicy>never</updatePolicy> > </releases> > <snapshots> > <enabled>false</enabled> > <updatePolicy>never</updatePolicy> > </snapshots> > </repository> > </repositories> > </profile> > </profiles> > <activeProfiles> > <activeProfile>test-profile</activeProfile> > </activeProfiles> > {noformat} > Running Forge in ticket-monster/demo directory results in following: > {noformat} > Using Forge at /home/trepel/workspace/apps/forge-distribution-1.2.3.Final > _____ > | ___|__ _ __ __ _ ___ > | |_ / _ \| `__/ _` |/ _ \ \\ > | _| (_) | | | (_| | __/ // > |_| \___/|_| \__, |\___| > |___/ > > Error during Startup event > org.jboss.forge.project.ProjectModelException: org.apache.maven.project.ProjectBuildingException: 29 problems were encountered while building the effective model for org.jboss.jdf.examples:ticket-monster:2.1.2-SNAPSHOT > [ERROR] Non-resolvable import POM: Could not find artifact org.jboss.bom:jboss-javaee-6.0-with-tools:pom:1.0.5.CR2 in obsolete-enterprise-repository (file:///home/trepel/maven/some-repo-with-missing-dependencies) @ line 50, column 25 > {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, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-858) Forge can't find dependencies from Maven Central if there is an active profile with repository setup in settings.xml

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-858?page=com.atlassian.jira.plugin.... ] George Gastaldi reassigned FORGE-858: ------------------------------------- Assignee: George Gastaldi > Forge can't find dependencies from Maven Central if there is an active profile with repository setup in settings.xml > -------------------------------------------------------------------------------------------------------------------- > > Key: FORGE-858 > URL: https://issues.jboss.org/browse/FORGE-858 > Project: Forge > Issue Type: Bug > Components: Maven Integration > Affects Versions: 1.2.3.Final > Reporter: Tomas Repel > Assignee: George Gastaldi > > It seems that Forge does not recognize the dependencies form Maven Central. This happens when there is an active profile with some repository setup in settings.xml file. > I experience this when using Forge with Ticket Monster (https://github.com/jboss-jdf/ticket-monster) and empty maven local repository. > settings.xml snippet: > {noformat} > </profiles> > <profile> > <id>test-profile</id> > <repositories> > <repository> > <id>obsolete-enterprise-repository</id> > <name>Obsolete Enterprise Repository</name> > <url>file:///home/trepel/maven/some-repo-with-missing-dependencies</url> > <layout>default</layout> > <releases> > <enabled>true</enabled> > <updatePolicy>never</updatePolicy> > </releases> > <snapshots> > <enabled>false</enabled> > <updatePolicy>never</updatePolicy> > </snapshots> > </repository> > </repositories> > </profile> > </profiles> > <activeProfiles> > <activeProfile>test-profile</activeProfile> > </activeProfiles> > {noformat} > Running Forge in ticket-monster/demo directory results in following: > {noformat} > Using Forge at /home/trepel/workspace/apps/forge-distribution-1.2.3.Final > _____ > | ___|__ _ __ __ _ ___ > | |_ / _ \| `__/ _` |/ _ \ \\ > | _| (_) | | | (_| | __/ // > |_| \___/|_| \__, |\___| > |___/ > > Error during Startup event > org.jboss.forge.project.ProjectModelException: org.apache.maven.project.ProjectBuildingException: 29 problems were encountered while building the effective model for org.jboss.jdf.examples:ticket-monster:2.1.2-SNAPSHOT > [ERROR] Non-resolvable import POM: Could not find artifact org.jboss.bom:jboss-javaee-6.0-with-tools:pom:1.0.5.CR2 in obsolete-enterprise-repository (file:///home/trepel/maven/some-repo-with-missing-dependencies) @ line 50, column 25 > {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, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-858) Forge can't find dependencies from Maven Central if there is an active profile with repository setup in settings.xml

by Tomas Repel (JIRA)

Tomas Repel created FORGE-858: --------------------------------- Summary: Forge can't find dependencies from Maven Central if there is an active profile with repository setup in settings.xml Key: FORGE-858 URL: https://issues.jboss.org/browse/FORGE-858 Project: Forge Issue Type: Bug Components: Maven Integration Affects Versions: 1.2.3.Final Reporter: Tomas Repel It seems that Forge does not recognize the dependencies form Maven Central. This happens when there is an active profile with some repository setup in settings.xml file. I experience this when using Forge with Ticket Monster (https://github.com/jboss-jdf/ticket-monster) and empty maven local repository. settings.xml snippet: {noformat} </profiles> <profile> <id>test-profile</id> <repositories> <repository> <id>obsolete-enterprise-repository</id> <name>Obsolete Enterprise Repository</name> <url>file:///home/trepel/maven/some-repo-with-missing-dependencies</url> <layout>default</layout> <releases> <enabled>true</enabled> <updatePolicy>never</updatePolicy> </releases> <snapshots> <enabled>false</enabled> <updatePolicy>never</updatePolicy> </snapshots> </repository> </repositories> </profile> </profiles> <activeProfiles> <activeProfile>test-profile</activeProfile> </activeProfiles> {noformat} Running Forge in ticket-monster/demo directory results in following: {noformat} Using Forge at /home/trepel/workspace/apps/forge-distribution-1.2.3.Final _____ | ___|__ _ __ __ _ ___ | |_ / _ \| `__/ _` |/ _ \ \\ | _| (_) | | | (_| | __/ // |_| \___/|_| \__, |\___| |___/ Error during Startup event org.jboss.forge.project.ProjectModelException: org.apache.maven.project.ProjectBuildingException: 29 problems were encountered while building the effective model for org.jboss.jdf.examples:ticket-monster:2.1.2-SNAPSHOT [ERROR] Non-resolvable import POM: Could not find artifact org.jboss.bom:jboss-javaee-6.0-with-tools:pom:1.0.5.CR2 in obsolete-enterprise-repository (file:///home/trepel/maven/some-repo-with-missing-dependencies) @ line 50, column 25 {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, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues April 2013