[JBoss JIRA] (FORGE-378) Add "environments" as a first class construct
by Antonio Goncalves (JIRA)
[ https://issues.jboss.org/browse/FORGE-378?page=com.atlassian.jira.plugin.... ]
Antonio Goncalves commented on FORGE-378:
-----------------------------------------
I would go for something more abstract such as :
{code}
set environment CONTAINER --version JBoss-7.1.0.Final
set environment CONTAINER --version GlassFish-4.0.0.Final
set environment CONTAINER --version TomEE-1.5.0.Final
{code}
But I would also seperate the notion of Java EE version from the version of the container (you can generate a Java EE 6 app for GlassFish 4, as well as a Java EE 7 app) :
{code}
set environment JAVAEE --version JavaEE-6
set environment JAVAEE --version JavaEE-7
set environment JAVAEE --version JavaEE-7-Web.Profile
{code}
The version of the container is important for all the specific implementations, but the JavaEE version is somehow more important for compiling the application against these APIs and making sure the code is portable. Instead of the Java EE BOM of JBoss AS (or the Java EE BOM of GlassFish), why not using the generic Java EE APIs no matter what the container is :
{code}
<dependency>
<groupId>javax</groupId>
<artifactId>javaee-api</artifactId>
<version>7.0</version>
</dependency>
<dependency>
<groupId>javax</groupId>
<artifactId>javaee-api</artifactId>
<version>6.0</version>
</dependency>
<dependency>
<groupId>javax</groupId>
<artifactId>javaee-web-api</artifactId>
<version>7.0</version>
</dependency>
<dependency>
<groupId>javax</groupId>
<artifactId>javaee-web-api</artifactId>
<version>6.0</version>
</dependency>
{code}
> Add "environments" as a first class construct
> ---------------------------------------------
>
> Key: FORGE-378
> URL: https://issues.jboss.org/browse/FORGE-378
> Project: Forge
> Issue Type: Feature Request
> Components: UI - Shell, Usability
> Reporter: Pete Muir
>
> For example:
> {code}
> set environment JBOSS_AS7 --version 7.1.0.Final
> {code}
> Where JBOSS_AS7 is a built in profile that contains necessary info on various versions of JBoss AS 7.
> For example, the persistence plugin could read from this, changing
> {code}
> persistence setup --provider HIBERNATE --container JBOSS_AS7
> {code}
> to
> {code}
> persistence setup
> {code}
> Or, when setting up CDI, this would remove the need to ask ask which API to use (always use the Java EE BOM with JBoss AS), and as the metadata builds, remove the need to ask the version of the spec BOM to use.
> Lot's of other places where this could provide better defaulting, or remove the need to ask questions.
> This also seems fairly consistent with the Forge approach - good understanding of the project in question.
--
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, 10 months
[JBoss JIRA] (FORGE-1136) Forge fails to resolve dependencies across multiple password protected Maven repositories located on the same host
by Vineet Reynolds (JIRA)
[ https://issues.jboss.org/browse/FORGE-1136?page=com.atlassian.jira.plugin... ]
Vineet Reynolds updated FORGE-1136:
-----------------------------------
Description:
This is related to FORGE-1134.
When attempting to resolve dependencies from multiple repositories present on the same host, Forge (actually Maven and Aether) fails to resolve certain dependencies.
The following is an example:
{noformat}
[no project] vineet $ forge install-plugin arquillian
Connecting to remote repository [https://raw.github.com/forge/plugin-repository/master/repository.yaml]... connected!
***INFO*** Preparing to install plugin: arquillian
***INFO*** Checking out plugin source files to [/tmp/forgetemp448150160827402029] via 'git'
***INFO*** Switching to branch/tag [refs/heads/1.0.6.Final]
***WARNING*** Failed to read artifact descriptor for org.jboss.forge:forge-shell-api:jar:1.0.6.Final
Cause : Could not transfer artifact org.jboss.weld:weld-core-bom:pom:1.1.2.Final from/to nexus-local-repo (http://localhost:8081/nexus/content/groups/public/): Access denied to: http://localhost:8081/nexus/content/groups/public/org/jboss/weld/weld-cor...
***WARNING*** Failed to read artifact descriptor for org.jboss.forge:forge-shell:jar:1.0.6.Final
Cause : Could not transfer artifact org.jboss.weld:weld-core-bom:pom:1.1.2.Final from/to nexus-local-repo (http://localhost:8081/nexus/content/groups/public/): Access denied to: http://localhost:8081/nexus/content/groups/public/org/jboss/weld/weld-cor...
***WARNING*** Failed to read artifact descriptor for org.jboss.forge:forge-maven-api:jar:1.0.6.Final
Cause : Could not transfer artifact org.jboss.weld:weld-core-bom:pom:1.1.2.Final from/to nexus-local-repo (http://localhost:8081/nexus/content/groups/public/): Access denied to: http://localhost:8081/nexus/content/groups/public/org/jboss/weld/weld-cor...
***WARNING*** Failed to read artifact descriptor for org.jboss.forge:forge-test-harness:jar:1.0.6.Final
Cause : Could not transfer artifact org.jboss.weld:weld-core-bom:pom:1.1.2.Final from/to nexus-local-repo (http://localhost:8081/nexus/content/groups/public/): Access denied to: http://localhost:8081/nexus/content/groups/public/org/jboss/weld/weld-cor...
***WARNING*** Failed to read artifact descriptor for org.jboss.forge:forge-javaee-api:jar:1.0.6.Final
Cause : Could not transfer artifact org.jboss.weld:weld-core-bom:pom:1.1.2.Final from/to nexus-local-repo (http://localhost:8081/nexus/content/groups/public/): Access denied to: http://localhost:8081/nexus/content/groups/public/org/jboss/weld/weld-cor...
? The project does not appear to be a Forge Plugin Project, install anyway? [y/N]
***INFO*** Cleaning up temp workspace [/tmp/forgetemp448150160827402029]
Wrote /home/vineet/.forge/httpsrawgithubcomforgepluginrepositorymasterrepositoryyaml.yaml
Deleted /tmp/forgetemp448150160827402029
***ERROR*** Exception encountered: Installation aborted (type "set VERBOSE true" to enable stack traces)
[no project] vineet $
{noformat}
In this case, some of the dependencies (present in M2 central) were resolved successfully, while others (present in the public repo group) were not. The underlying cause was that the resolved dependencies were present in a repository or repository group via a valid username+password combination. The unresolved dependencies were also present in a repository or repository group protected by a username+password combination. Although valid credentials were provided by Forge to Maven/Aether for the second repository, this was not used by Maven/Aether.
The underlying reason is that the JVM caches the credentials used by the Maven LightweightHTTPWagon implementation since the credentials are supplied via a {{java.net.Authenticator}} instance. This forces only one set of credentials to be used at runtime; the second set of credentials will be ignored.
was:
This is related to FORGE-1134.
When attempting to resolve dependencies from multiple repositories present on the same host, Forge (actually Maven and Aether) fails to resolve certain dependencies.
The following is an example:
{noformat}
[no project] vineet $ forge install-plugin arquillian
Connecting to remote repository [https://raw.github.com/forge/plugin-repository/master/repository.yaml]... connected!
***INFO*** Preparing to install plugin: arquillian
***INFO*** Checking out plugin source files to [/tmp/forgetemp448150160827402029] via 'git'
***INFO*** Switching to branch/tag [refs/heads/1.0.6.Final]
***WARNING*** Failed to read artifact descriptor for org.jboss.forge:forge-shell-api:jar:1.0.6.Final
Cause : Could not transfer artifact org.jboss.weld:weld-core-bom:pom:1.1.2.Final from/to nexus-local-repo (http://localhost:8081/nexus/content/groups/public/): Access denied to: http://localhost:8081/nexus/content/groups/public/org/jboss/weld/weld-cor...
***WARNING*** Failed to read artifact descriptor for org.jboss.forge:forge-shell:jar:1.0.6.Final
Cause : Could not transfer artifact org.jboss.weld:weld-core-bom:pom:1.1.2.Final from/to nexus-local-repo (http://localhost:8081/nexus/content/groups/public/): Access denied to: http://localhost:8081/nexus/content/groups/public/org/jboss/weld/weld-cor...
***WARNING*** Failed to read artifact descriptor for org.jboss.forge:forge-maven-api:jar:1.0.6.Final
Cause : Could not transfer artifact org.jboss.weld:weld-core-bom:pom:1.1.2.Final from/to nexus-local-repo (http://localhost:8081/nexus/content/groups/public/): Access denied to: http://localhost:8081/nexus/content/groups/public/org/jboss/weld/weld-cor...
***WARNING*** Failed to read artifact descriptor for org.jboss.forge:forge-test-harness:jar:1.0.6.Final
Cause : Could not transfer artifact org.jboss.weld:weld-core-bom:pom:1.1.2.Final from/to nexus-local-repo (http://localhost:8081/nexus/content/groups/public/): Access denied to: http://localhost:8081/nexus/content/groups/public/org/jboss/weld/weld-cor...
***WARNING*** Failed to read artifact descriptor for org.jboss.forge:forge-javaee-api:jar:1.0.6.Final
Cause : Could not transfer artifact org.jboss.weld:weld-core-bom:pom:1.1.2.Final from/to nexus-local-repo (http://localhost:8081/nexus/content/groups/public/): Access denied to: http://localhost:8081/nexus/content/groups/public/org/jboss/weld/weld-cor...
? The project does not appear to be a Forge Plugin Project, install anyway? [y/N]
***INFO*** Cleaning up temp workspace [/tmp/forgetemp448150160827402029]
Wrote /home/vineet/.forge/httpsrawgithubcomforgepluginrepositorymasterrepositoryyaml.yaml
Deleted /tmp/forgetemp448150160827402029
***ERROR*** Exception encountered: Installation aborted (type "set VERBOSE true" to enable stack traces)
[no project] vineet $
{noformat}
In this case, some of the dependencies were resolved successfully, while others were not. The underlying cause was that the resolved dependencies were present in a repository or repository group via a valid username+password combination. The unresolved dependencies were also present in a repository or repository group protected by a username+password combination. Although valid credentials were provided by Forge to Maven/Aether for the second repository, this was not used.
The underlying reason is that the JVM caches the credentials used by the Maven LightweightHTTPWagon implementation since the credentials are supplied via a {{java.net.Authenticator}} instance. This forces only one set of credentials to be used at runtime; the second set of credentials will be ignored.
> Forge fails to resolve dependencies across multiple password protected Maven repositories located on the same host
> ------------------------------------------------------------------------------------------------------------------
>
> Key: FORGE-1136
> URL: https://issues.jboss.org/browse/FORGE-1136
> Project: Forge
> Issue Type: Bug
> Components: Build Tools - Maven
> Affects Versions: 1.4.0.Final
> Reporter: Vineet Reynolds
>
> This is related to FORGE-1134.
> When attempting to resolve dependencies from multiple repositories present on the same host, Forge (actually Maven and Aether) fails to resolve certain dependencies.
> The following is an example:
> {noformat}
> [no project] vineet $ forge install-plugin arquillian
> Connecting to remote repository [https://raw.github.com/forge/plugin-repository/master/repository.yaml]... connected!
> ***INFO*** Preparing to install plugin: arquillian
> ***INFO*** Checking out plugin source files to [/tmp/forgetemp448150160827402029] via 'git'
> ***INFO*** Switching to branch/tag [refs/heads/1.0.6.Final]
> ***WARNING*** Failed to read artifact descriptor for org.jboss.forge:forge-shell-api:jar:1.0.6.Final
> Cause : Could not transfer artifact org.jboss.weld:weld-core-bom:pom:1.1.2.Final from/to nexus-local-repo (http://localhost:8081/nexus/content/groups/public/): Access denied to: http://localhost:8081/nexus/content/groups/public/org/jboss/weld/weld-cor...
> ***WARNING*** Failed to read artifact descriptor for org.jboss.forge:forge-shell:jar:1.0.6.Final
> Cause : Could not transfer artifact org.jboss.weld:weld-core-bom:pom:1.1.2.Final from/to nexus-local-repo (http://localhost:8081/nexus/content/groups/public/): Access denied to: http://localhost:8081/nexus/content/groups/public/org/jboss/weld/weld-cor...
> ***WARNING*** Failed to read artifact descriptor for org.jboss.forge:forge-maven-api:jar:1.0.6.Final
> Cause : Could not transfer artifact org.jboss.weld:weld-core-bom:pom:1.1.2.Final from/to nexus-local-repo (http://localhost:8081/nexus/content/groups/public/): Access denied to: http://localhost:8081/nexus/content/groups/public/org/jboss/weld/weld-cor...
> ***WARNING*** Failed to read artifact descriptor for org.jboss.forge:forge-test-harness:jar:1.0.6.Final
> Cause : Could not transfer artifact org.jboss.weld:weld-core-bom:pom:1.1.2.Final from/to nexus-local-repo (http://localhost:8081/nexus/content/groups/public/): Access denied to: http://localhost:8081/nexus/content/groups/public/org/jboss/weld/weld-cor...
> ***WARNING*** Failed to read artifact descriptor for org.jboss.forge:forge-javaee-api:jar:1.0.6.Final
> Cause : Could not transfer artifact org.jboss.weld:weld-core-bom:pom:1.1.2.Final from/to nexus-local-repo (http://localhost:8081/nexus/content/groups/public/): Access denied to: http://localhost:8081/nexus/content/groups/public/org/jboss/weld/weld-cor...
> ? The project does not appear to be a Forge Plugin Project, install anyway? [y/N]
> ***INFO*** Cleaning up temp workspace [/tmp/forgetemp448150160827402029]
> Wrote /home/vineet/.forge/httpsrawgithubcomforgepluginrepositorymasterrepositoryyaml.yaml
> Deleted /tmp/forgetemp448150160827402029
> ***ERROR*** Exception encountered: Installation aborted (type "set VERBOSE true" to enable stack traces)
> [no project] vineet $
> {noformat}
> In this case, some of the dependencies (present in M2 central) were resolved successfully, while others (present in the public repo group) were not. The underlying cause was that the resolved dependencies were present in a repository or repository group via a valid username+password combination. The unresolved dependencies were also present in a repository or repository group protected by a username+password combination. Although valid credentials were provided by Forge to Maven/Aether for the second repository, this was not used by Maven/Aether.
> The underlying reason is that the JVM caches the credentials used by the Maven LightweightHTTPWagon implementation since the credentials are supplied via a {{java.net.Authenticator}} instance. This forces only one set of credentials to be used at runtime; the second set of credentials will be ignored.
--
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, 10 months
[JBoss JIRA] (FORGE-1129) Support interactive merging of changes performed on existing files
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/FORGE-1129?page=com.atlassian.jira.plugin... ]
Max Rydahl Andersen commented on FORGE-1129:
--------------------------------------------
jmerge just changes the files according to the rules defined - what you do with them afterwards (i.e. show them in the merge editor) is up to you.
what jmerge does is that your generator can be smart by just being "stupid" and generate the same code everytime, jmerge then takes the existing source possibly edited by the user and does a semantic merge of class and methods - driven and/or protected by annotations on these classes.
See http://wiki.eclipse.org/JET_FAQ_What_is_JMerge%3F (note: in this faq they use specific named annotations, but jmerge does not *need* annotations, it is just there as one option to control the merge)
> Support interactive merging of changes performed on existing files
> ------------------------------------------------------------------
>
> Key: FORGE-1129
> URL: https://issues.jboss.org/browse/FORGE-1129
> Project: Forge
> Issue Type: Feature Request
> Components: UI - API, UI - Eclipse, UI - IntelliJ IDEA, UI - Shell
> Reporter: Vineet Reynolds
> Fix For: 2.x Future
>
>
> Currently, in Forge 1, we merely prompt the users to overwrite the existing file if located. Either the existing file is lost or the changes made by Forge are not saved. No attempt is made to retain the existing file with changes performed by the user, while merging in changes performed by Forge.
> Forge should support interactive diffing and merging of the changes made on the existing file. Integration with existing diff tools in various IDEs and shells would be a plus.
> This should ideally be exposed as a service for 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, 10 months
[JBoss JIRA] (FORGE-1135) ServletFacetImpl overrides isInstalled of BaseJavaEEFacet but doesnt call super.isInstalled
by Thomas Frühbeck (JIRA)
[ https://issues.jboss.org/browse/FORGE-1135?page=com.atlassian.jira.plugin... ]
Thomas Frühbeck updated FORGE-1135:
-----------------------------------
Description:
ServletFacetImpl misses to call super.isInstalled(), so no servlet dependencies are installed in pom on setup():
@Override
public boolean isInstalled()
{
DirectoryResource webRoot = project.getFacet(WebResourceFacet.class).getWebRootDirectory();
return webRoot.exists();
}
Same seems to be true for FacesFacetImpl and FacesAPIFacetImpl.
> ServletFacetImpl overrides isInstalled of BaseJavaEEFacet but doesnt call super.isInstalled
> -------------------------------------------------------------------------------------------
>
> Key: FORGE-1135
> URL: https://issues.jboss.org/browse/FORGE-1135
> Project: Forge
> Issue Type: Bug
> Components: Java EE APIs
> Affects Versions: 1.4.0.Final
> Reporter: Thomas Frühbeck
>
> ServletFacetImpl misses to call super.isInstalled(), so no servlet dependencies are installed in pom on setup():
> @Override
> public boolean isInstalled()
> {
> DirectoryResource webRoot = project.getFacet(WebResourceFacet.class).getWebRootDirectory();
> return webRoot.exists();
> }
> Same seems to be true for FacesFacetImpl and FacesAPIFacetImpl.
--
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, 10 months