July 2014 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-1948) Avoid adding JavaEE6 pom when JavaEE7 artifacts are installed?

by Michal Matloka (JIRA)

[ https://issues.jboss.org/browse/FORGE-1948?page=com.atlassian.jira.plugin... ] Michal Matloka updated FORGE-1948: ---------------------------------- Description: Execution of the following commands {noformat} [bin]$ project-new --named forge-demo --topLevelPackage com.packtpub.wflydevelop ment.appendix projectFolder forge-demo ***SUCCESS*** Project named 'forge-demo' has been created. [forge-demo]$ jpa-setup --jpaVersion 2.1 --provider HIBERNATE --container WILDFL Y --dbType POSTGRES --dataSourceName ja-va:jboss/datasources/PostgreSqlDS ***SUCCESS*** Persistence (JPA) is installed. [persistence.xml]$ {noformat} Results in pom.xml: {noformat} <?xml version="1.0" encoding="UTF-8"?> <project xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd" xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <modelVersion>4.0.0</modelVersion> <groupId>com.packtpub.wflydevelopment.appendix</groupId> <artifactId>forge-demo</artifactId> <version>1.0.0-SNAPSHOT</version> <packaging>war</packaging> <properties> <maven.compiler.source>1.7</maven.compiler.source> <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding> <maven.compiler.target>1.7</maven.compiler.target> </properties> <dependencyManagement> <dependencies> <dependency> <groupId>org.jboss.spec</groupId> <artifactId>jboss-javaee-6.0</artifactId> <version>3.0.2.Final</version> <type>pom</type> <scope>import</scope> </dependency> <dependency> <groupId>org.hibernate.javax.persistence</groupId> <artifactId>hibernate-jpa-2.1-api</artifactId> <version>1.0.0.Draft-16</version> <scope>provided</scope> </dependency> </dependencies> </dependencyManagement> <dependencies> <dependency> <groupId>org.hibernate.javax.persistence</groupId> <artifactId>hibernate-jpa-2.1-api</artifactId> <scope>provided</scope> </dependency> </dependencies> <build> <plugins> <plugin> <artifactId>maven-war-plugin</artifactId> <version>2.4</version> <configuration> <failOnMissingWebXml>false</failOnMissingWebXml> </configuration> </plugin> </plugins> </build> </project> {noformat} I rather expected to get javaee 7 api instead of jboss-javaee-6.0 ;) was: Execution of the following commands {noformat} [bin]$ project-new --named forge-demo --topLevelPackage com.packtpub.wflydevelop ment.appendix projectFolder forge-demo ***SUCCESS*** Project named 'forge-demo' has been created. [forge-demo]$ jpa-setup --jpaVersion 2.1 --provider HIBERNATE --container WILDFL Y --dbType POSTGRES --dataSourceName ja-va:jboss/datasources/PostgreSqlDS ***SUCCESS*** Persistence (JPA) is installed. [persistence.xml]$ {noformat} Results in pom.xml: {noformat} <?xml version="1.0" encoding="UTF-8"?> <project xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd" xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <modelVersion>4.0.0</modelVersion> <groupId>com.packtpub.wflydevelopment.appendix</groupId> <artifactId>forge-demo</artifactId> <version>1.0.0-SNAPSHOT</version> <packaging>war</packaging> <properties> <maven.compiler.source>1.7</maven.compiler.source> <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding> <maven.compiler.target>1.7</maven.compiler.target> </properties> <dependencyManagement> <dependencies> <dependency> <groupId>org.jboss.spec</groupId> <artifactId>jboss-javaee-6.0</artifactId> <version>3.0.2.Final</version> <type>pom</type> <scope>import</scope> </dependency> <dependency> <groupId>org.hibernate.javax.persistence</groupId> <artifactId>hibernate-jpa-2.1-api</artifactId> <version>1.0.0.Draft-16</version> <scope>provided</scope> </dependency> </dependencies> </dependencyManagement> <dependencies> <dependency> <groupId>org.hibernate.javax.persistence</groupId> <artifactId>hibernate-jpa-2.1-api</artifactId> <scope>provided</scope> </dependency> </dependencies> <build> <plugins> <plugin> <artifactId>maven-war-plugin</artifactId> <version>2.4</version> <configuration> <failOnMissingWebXml>false</failOnMissingWebXml> </configuration> </plugin> </plugins> </build> </project> {noformat} > Avoid adding JavaEE6 pom when JavaEE7 artifacts are installed? > -------------------------------------------------------------- > > Key: FORGE-1948 > URL: https://issues.jboss.org/browse/FORGE-1948 > Project: Forge > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 2.7.0.Final > Reporter: Michal Matloka > > Execution of the following commands > {noformat} > [bin]$ project-new --named forge-demo --topLevelPackage com.packtpub.wflydevelop > ment.appendix projectFolder forge-demo > ***SUCCESS*** Project named 'forge-demo' has been created. > [forge-demo]$ jpa-setup --jpaVersion 2.1 --provider HIBERNATE --container WILDFL > Y --dbType POSTGRES --dataSourceName ja-va:jboss/datasources/PostgreSqlDS > ***SUCCESS*** Persistence (JPA) is installed. > [persistence.xml]$ > {noformat} > Results in pom.xml: > {noformat} > <?xml version="1.0" encoding="UTF-8"?> > <project xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd" xmlns="http://maven.apache.org/POM/4.0.0" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> > <modelVersion>4.0.0</modelVersion> > <groupId>com.packtpub.wflydevelopment.appendix</groupId> > <artifactId>forge-demo</artifactId> > <version>1.0.0-SNAPSHOT</version> > <packaging>war</packaging> > <properties> > <maven.compiler.source>1.7</maven.compiler.source> > <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding> > <maven.compiler.target>1.7</maven.compiler.target> > </properties> > <dependencyManagement> > <dependencies> > <dependency> > <groupId>org.jboss.spec</groupId> > <artifactId>jboss-javaee-6.0</artifactId> > <version>3.0.2.Final</version> > <type>pom</type> > <scope>import</scope> > </dependency> > <dependency> > <groupId>org.hibernate.javax.persistence</groupId> > <artifactId>hibernate-jpa-2.1-api</artifactId> > <version>1.0.0.Draft-16</version> > <scope>provided</scope> > </dependency> > </dependencies> > </dependencyManagement> > <dependencies> > <dependency> > <groupId>org.hibernate.javax.persistence</groupId> > <artifactId>hibernate-jpa-2.1-api</artifactId> > <scope>provided</scope> > </dependency> > </dependencies> > <build> > <plugins> > <plugin> > <artifactId>maven-war-plugin</artifactId> > <version>2.4</version> > <configuration> > <failOnMissingWebXml>false</failOnMissingWebXml> > </configuration> > </plugin> > </plugins> > </build> > </project> > {noformat} > I rather expected to get javaee 7 api instead of jboss-javaee-6.0 ;) -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1947) SimpleContainer fails to return services on Windows causing InflectorServiceTest to fail

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1947?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1947. ---------------------------------- Resolution: Done InflectorServiceTest now should pass > SimpleContainer fails to return services on Windows causing InflectorServiceTest to fail > ---------------------------------------------------------------------------------------- > > Key: FORGE-1947 > URL: https://issues.jboss.org/browse/FORGE-1947 > Project: Forge > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Furnace Simple > Affects Versions: 2.7.1.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 2.7.2.Final > > > This bug occurs in the reading of the Service provider file. It is not considering \r in Windows environments. > This is the main cause for the InflectorServiceTest to fail. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1947) SimpleContainer fails to return services on Windows causing InflectorServiceTest to fail

by George Gastaldi (JIRA)

George Gastaldi created FORGE-1947: -------------------------------------- Summary: SimpleContainer fails to return services on Windows causing InflectorServiceTest to fail Key: FORGE-1947 URL: https://issues.jboss.org/browse/FORGE-1947 Project: Forge Issue Type: Bug Security Level: Public (Everyone can see) Components: Furnace Simple Affects Versions: 2.7.1.Final Reporter: George Gastaldi Assignee: George Gastaldi Fix For: 2.7.2.Final This bug occurs in the reading of the Service provider file. It is not considering \r in Windows environments. This is the main cause for the InflectorServiceTest to fail. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1946) Update Furnace-CDI to Weld 2.2.4.Final

by George Gastaldi (JIRA)

George Gastaldi created FORGE-1946: -------------------------------------- Summary: Update Furnace-CDI to Weld 2.2.4.Final Key: FORGE-1946 URL: https://issues.jboss.org/browse/FORGE-1946 Project: Forge Issue Type: Component Upgrade Security Level: Public (Everyone can see) Components: Furnace CDI Affects Versions: 2.7.1.Final Reporter: George Gastaldi Assignee: George Gastaldi Priority: Trivial Fix For: 2.x Future -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 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: ---------------------------------------- I vote for a {{--quiet}} flag (default:false) > 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, 6 months

1
0
0 / 0

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

by Ricardo Martinelli Oliveira (JIRA)

[ https://issues.jboss.org/browse/FORGE-1488?page=com.atlassian.jira.plugin... ] Ricardo Martinelli Oliveira commented on FORGE-1488: ---------------------------------------------------- Wouldn't be better if build command had a --debug or --showLog option? I'm affraid this change might show too much output where sometimes we don't want/need. > 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, 6 months

1
0
0 / 0

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

by Ricardo Martinelli Oliveira (JIRA)

[ https://issues.jboss.org/browse/FORGE-1488?page=com.atlassian.jira.plugin... ] Ricardo Martinelli Oliveira reassigned FORGE-1488: -------------------------------------------------- Assignee: Ricardo Martinelli Oliveira > 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, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1945) Display current Forge version on downloads page

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1945?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1945. ---------------------------------- Fix Version/s: 2.7.2.Final Resolution: Done > Display current Forge version on downloads page > ----------------------------------------------- > > Key: FORGE-1945 > URL: https://issues.jboss.org/browse/FORGE-1945 > Project: Forge > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Website > Reporter: Lincoln Baxter III > Assignee: George Gastaldi > Fix For: 2.7.2.Final > > > Right now there's no way to tell (without looking at the link location) what version of forge is being downloaded -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1945) Display current Forge version on downloads page

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1945?page=com.atlassian.jira.plugin... ] George Gastaldi reassigned FORGE-1945: -------------------------------------- Assignee: George Gastaldi > Display current Forge version on downloads page > ----------------------------------------------- > > Key: FORGE-1945 > URL: https://issues.jboss.org/browse/FORGE-1945 > Project: Forge > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Website > Reporter: Lincoln Baxter III > Assignee: George Gastaldi > > Right now there's no way to tell (without looking at the link location) what version of forge is being downloaded -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1945) Display current Forge version on downloads page

by Lincoln Baxter III (JIRA)

Lincoln Baxter III created FORGE-1945: ----------------------------------------- Summary: Display current Forge version on downloads page Key: FORGE-1945 URL: https://issues.jboss.org/browse/FORGE-1945 Project: Forge Issue Type: Task Security Level: Public (Everyone can see) Components: Website Reporter: Lincoln Baxter III Right now there's no way to tell (without looking at the link location) what version of forge is being downloaded -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues July 2014