February 2014 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-1564) Expose functionality for starting processes

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1564?page=com.atlassian.jira.plugin... ] Lincoln Baxter III updated FORGE-1564: -------------------------------------- Labels: Starter (was: ) > Expose functionality for starting processes > ------------------------------------------- > > Key: FORGE-1564 > URL: https://issues.jboss.org/browse/FORGE-1564 > Project: Forge > Issue Type: Enhancement > Affects Versions: 2.0.1.Final > Reporter: Ivan St. Ivanov > Labels: Starter > > In Forge 1 there was an utility for the plugins to execute OS processes. It was implemented in the static method org.jboss.forge.shell.util.NativeSystemCall.execFromPath > Now in Forge 2 nearly the same functionality can be found in the maven-impl-projects addon. It is in the NativeSystemCall class. However, it is not reachable by other addons. -- 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

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGEPLUGINS-161) Create a PicketLink plugin

by Bruno Georges (JIRA)

[ https://issues.jboss.org/browse/FORGEPLUGINS-161?page=com.atlassian.jira.... ] Bruno Georges commented on FORGEPLUGINS-161: -------------------------------------------- Hi Shane, with the increase in Mobile type development I'd like to see the plugin to cover REST endpoints as well. Cheers, Bruno > Create a PicketLink plugin > -------------------------- > > Key: FORGEPLUGINS-161 > URL: https://issues.jboss.org/browse/FORGEPLUGINS-161 > Project: Forge Plugins > Issue Type: Feature Request > Reporter: Shane Bryzak > Assignee: Shane Bryzak > > George has currently implemented this: > https://github.com/forge/plugin-picketlink > We need a Forge plugin that will create a working security configuration for PicketLink. It should allow the developer to configure one or more identity stores, and optionally create the entity beans for a simple database schema. -- 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

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGEPLUGINS-161) Create a PicketLink plugin

by Shane Bryzak (JIRA)

[ https://issues.jboss.org/browse/FORGEPLUGINS-161?page=com.atlassian.jira.... ] Shane Bryzak reassigned FORGEPLUGINS-161: ----------------------------------------- Assignee: Shane Bryzak > Create a PicketLink plugin > -------------------------- > > Key: FORGEPLUGINS-161 > URL: https://issues.jboss.org/browse/FORGEPLUGINS-161 > Project: Forge Plugins > Issue Type: Feature Request > Reporter: Shane Bryzak > Assignee: Shane Bryzak > > George has currently implemented this: > https://github.com/forge/plugin-picketlink > We need a Forge plugin that will create a working security configuration for PicketLink. It should allow the developer to configure one or more identity stores, and optionally create the entity beans for a simple database schema. -- 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

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGEPLUGINS-161) Create a PicketLink plugin

by Shane Bryzak (JIRA)

Shane Bryzak created FORGEPLUGINS-161: ----------------------------------------- Summary: Create a PicketLink plugin Key: FORGEPLUGINS-161 URL: https://issues.jboss.org/browse/FORGEPLUGINS-161 Project: Forge Plugins Issue Type: Feature Request Reporter: Shane Bryzak George has currently implemented this: https://github.com/forge/plugin-picketlink We need a Forge plugin that will create a working security configuration for PicketLink. It should allow the developer to configure one or more identity stores, and optionally create the entity beans for a simple database schema. -- 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

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1500) ProjectFactoryImpl.findProject() should iterate over directories first then over build systems

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1500?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1500: ----------------------------------- Status: Closed (was: Pull Request Sent) Fix Version/s: 2.0.1.Final (was: 2.x Future) Resolution: Done Merged, thanks > ProjectFactoryImpl.findProject() should iterate over directories first then over build systems > ---------------------------------------------------------------------------------------------- > > Key: FORGE-1500 > URL: https://issues.jboss.org/browse/FORGE-1500 > Project: Forge > Issue Type: Bug > Components: Builtin Plugins > Affects Versions: 2.0.0.CR1 > Reporter: Adam Wyłuda > Assignee: Adam Wyłuda > Fix For: 2.0.1.Final > > > https://github.com/forge/core/blob/2.0/projects/impl/src/main/java/org/jb... > In case we have a project structure: > a/pom.xml > a/b/build.gradle > Starting from a/b/, if registry.getServices(BuildSystem.class) returns MavenBuildSystem as first, then it will pick up a/pom.xml. > My solution is inverting loops: > for (each build system) { for (each directory) { ... } } ---> for (each dir) { for (each build system) { ... } } > This causes problems in Gradle addon Maven build as temporary projects are run inside target/ directory, which has always pom.xml above. -- 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

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1568) ui-test-harness should be moved to package org.jboss.forge.addon.ui.test

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1568?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1568. ---------------------------------- Assignee: George Gastaldi Resolution: Done > ui-test-harness should be moved to package org.jboss.forge.addon.ui.test > ------------------------------------------------------------------------ > > Key: FORGE-1568 > URL: https://issues.jboss.org/browse/FORGE-1568 > Project: Forge > Issue Type: Task > Components: Test Harness > Affects Versions: 2.0.0.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 2.0.1.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

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1568) ui-test-harness should be moved to package org.jboss.forge.addon.ui.test

by George Gastaldi (JIRA)

George Gastaldi created FORGE-1568: -------------------------------------- Summary: ui-test-harness should be moved to package org.jboss.forge.addon.ui.test Key: FORGE-1568 URL: https://issues.jboss.org/browse/FORGE-1568 Project: Forge Issue Type: Task Components: Test Harness Affects Versions: 2.0.0.Final Reporter: George Gastaldi Fix For: 2.0.1.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

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-925) Publish JavaDoc to our Forge Website

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-925?page=com.atlassian.jira.plugin.... ] George Gastaldi closed FORGE-925. --------------------------------- Assignee: George Gastaldi Fix Version/s: 2.0.1.Final (was: 1.x Future) Resolution: Deferred Added link in README.asciidoc > Publish JavaDoc to our Forge Website > ------------------------------------ > > Key: FORGE-925 > URL: https://issues.jboss.org/browse/FORGE-925 > Project: Forge > Issue Type: Task > Components: Documentation, Website > Affects Versions: 1.3.0.Final, 2.0.0.Alpha4 > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 2.0.1.Final > > > We should have the javadocs published in our website -- 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

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1567) JavaParser should allow visiting the element tree

by George Gastaldi (JIRA)

George Gastaldi created FORGE-1567: -------------------------------------- Summary: JavaParser should allow visiting the element tree Key: FORGE-1567 URL: https://issues.jboss.org/browse/FORGE-1567 Project: Forge Issue Type: Feature Request Components: Parsers / File Manipulation Affects Versions: 2.0.0.Final Reporter: George Gastaldi Fix For: 2.x Future The idea here is to introduce a visitor pattern for a JavaClass in a similar way that AST does. -- 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

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1549) Add unitName to @PersistenceContext

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-1549?page=com.atlassian.jira.plugin... ] Antonio Goncalves updated FORGE-1549: ------------------------------------- Status: Closed (was: Pull Request Sent) Fix Version/s: 2.0.1.Final (was: 2.x Future) Resolution: Done > Add unitName to @PersistenceContext > ----------------------------------- > > Key: FORGE-1549 > URL: https://issues.jboss.org/browse/FORGE-1549 > Project: Forge > Issue Type: Feature Request > Components: Scaffold > Affects Versions: 2.0.0.Final > Reporter: Antonio Goncalves > Assignee: Antonio Goncalves > Labels: Starter > Fix For: 2.0.1.Final > > > The scaffolding generates this kind of code in terms of persistence context (e.g. below is for JSF) : > {code} > @PersistenceContext(type = PersistenceContextType.EXTENDED) > {code} > Because it doesn't have any {{unitName}} it takes the default one, if there is only one persistence unit. It would be better to explicitelly add the {{unitName}} so the code still deploys if there are several persistence unit. As per [FORGE-1513], the persistence unit name is the project name with -{{persistence-unit}} : > {code} > @PersistenceContext(unitName = "myproject-persistence-unit", type = PersistenceContextType.EXTENDED) > {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

10 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues February 2014