[JBoss JIRA] (FORGE-1541) Problems running tests when conflicting Javassist version is on the classpath
by Lincoln Baxter III (JIRA)
[ https://issues.jboss.org/browse/FORGE-1541?page=com.atlassian.jira.plugin... ]
Lincoln Baxter III commented on FORGE-1541:
-------------------------------------------
This is due to the inclusion of an older version of javassist on the classpath. We will need to shade our javassist to prevent future issues.
> Problems running tests when conflicting Javassist version is on the classpath
> -----------------------------------------------------------------------------
>
> Key: FORGE-1541
> URL: https://issues.jboss.org/browse/FORGE-1541
> Project: Forge
> Issue Type: Bug
> Components: Test Harness
> Affects Versions: 2.0.0.Final
> Environment: Mac OS X Mavericks
> java version "1.7.0_45"
> Apache Maven 3.1.0 (893ca28a1da9d5f51ac03827af98bb730128f9f2; 2013-06-27 22:15:32-0400)
> Reporter: Tom Cunningham
> Assignee: Lincoln Baxter III
> Attachments: org.switchyard.tools.forge.plugin.SwitchyardConfigurationTest.txt
>
>
> Problems deploying addons in 2.0.0.Final :
> org.switchyard.tools.forge.BasicFacetTest Time elapsed: -379,976.917 sec <<< ERROR!
> org.jboss.arquillian.container.spi.client.container.DeploymentException: AddonDependency org.switchyard.forge:switchyard-addon,2.0.0-SNAPSHOT failed to deploy.
> at org.jboss.forge.arquillian.ForgeDeployableContainer.waitForDeploymentCompletion(ForgeDeployableContainer.java:202)
> at org.jboss.forge.arquillian.ForgeDeployableContainer.deploy(ForgeDeployableContainer.java:116)
> at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$3.call(ContainerDeployController.java:161)
> at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$3.call(ContainerDeployController.java:128)
> at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.executeOperation(ContainerDeployController.java:271)
> at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.deploy(ContainerDeployController.java:127)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> To reproduce :
> git clone https://github.com/forge/plugin-switchyard.git
> git checkout 2.0
> mvn clean install
--
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
12 years, 2 months
[JBoss JIRA] (FORGE-1541) Problems running tests when conflicting Javassist version is on the classpath
by Lincoln Baxter III (JIRA)
[ https://issues.jboss.org/browse/FORGE-1541?page=com.atlassian.jira.plugin... ]
Lincoln Baxter III updated FORGE-1541:
--------------------------------------
Summary: Problems running tests when conflicting Javassist version is on the classpath (was: Problems deploying addon)
> Problems running tests when conflicting Javassist version is on the classpath
> -----------------------------------------------------------------------------
>
> Key: FORGE-1541
> URL: https://issues.jboss.org/browse/FORGE-1541
> Project: Forge
> Issue Type: Bug
> Components: Test Harness
> Affects Versions: 2.0.0.Final
> Environment: Mac OS X Mavericks
> java version "1.7.0_45"
> Apache Maven 3.1.0 (893ca28a1da9d5f51ac03827af98bb730128f9f2; 2013-06-27 22:15:32-0400)
> Reporter: Tom Cunningham
> Assignee: Lincoln Baxter III
> Attachments: org.switchyard.tools.forge.plugin.SwitchyardConfigurationTest.txt
>
>
> Problems deploying addons in 2.0.0.Final :
> org.switchyard.tools.forge.BasicFacetTest Time elapsed: -379,976.917 sec <<< ERROR!
> org.jboss.arquillian.container.spi.client.container.DeploymentException: AddonDependency org.switchyard.forge:switchyard-addon,2.0.0-SNAPSHOT failed to deploy.
> at org.jboss.forge.arquillian.ForgeDeployableContainer.waitForDeploymentCompletion(ForgeDeployableContainer.java:202)
> at org.jboss.forge.arquillian.ForgeDeployableContainer.deploy(ForgeDeployableContainer.java:116)
> at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$3.call(ContainerDeployController.java:161)
> at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$3.call(ContainerDeployController.java:128)
> at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.executeOperation(ContainerDeployController.java:271)
> at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.deploy(ContainerDeployController.java:127)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> To reproduce :
> git clone https://github.com/forge/plugin-switchyard.git
> git checkout 2.0
> mvn clean install
--
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
12 years, 2 months
[JBoss JIRA] (FORGE-1541) Problems deploying addon
by Lincoln Baxter III (JIRA)
[ https://issues.jboss.org/browse/FORGE-1541?page=com.atlassian.jira.plugin... ]
Lincoln Baxter III reassigned FORGE-1541:
-----------------------------------------
Assignee: Lincoln Baxter III
> Problems deploying addon
> ------------------------
>
> Key: FORGE-1541
> URL: https://issues.jboss.org/browse/FORGE-1541
> Project: Forge
> Issue Type: Bug
> Components: Test Harness
> Affects Versions: 2.0.0.Final
> Environment: Mac OS X Mavericks
> java version "1.7.0_45"
> Apache Maven 3.1.0 (893ca28a1da9d5f51ac03827af98bb730128f9f2; 2013-06-27 22:15:32-0400)
> Reporter: Tom Cunningham
> Assignee: Lincoln Baxter III
> Attachments: org.switchyard.tools.forge.plugin.SwitchyardConfigurationTest.txt
>
>
> Problems deploying addons in 2.0.0.Final :
> org.switchyard.tools.forge.BasicFacetTest Time elapsed: -379,976.917 sec <<< ERROR!
> org.jboss.arquillian.container.spi.client.container.DeploymentException: AddonDependency org.switchyard.forge:switchyard-addon,2.0.0-SNAPSHOT failed to deploy.
> at org.jboss.forge.arquillian.ForgeDeployableContainer.waitForDeploymentCompletion(ForgeDeployableContainer.java:202)
> at org.jboss.forge.arquillian.ForgeDeployableContainer.deploy(ForgeDeployableContainer.java:116)
> at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$3.call(ContainerDeployController.java:161)
> at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$3.call(ContainerDeployController.java:128)
> at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.executeOperation(ContainerDeployController.java:271)
> at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.deploy(ContainerDeployController.java:127)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> To reproduce :
> git clone https://github.com/forge/plugin-switchyard.git
> git checkout 2.0
> mvn clean install
--
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
12 years, 2 months
[JBoss JIRA] (FORGE-1540) Have Project extends MutableFaceted<ProjectFacet> instead of Faceted<ProjectFacet>
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-1540?page=com.atlassian.jira.plugin... ]
George Gastaldi closed FORGE-1540.
----------------------------------
Resolution: Rejected
Having an uninstall method in {{FacetFactory}} is the way to go. Created FORGE-1543
> Have Project extends MutableFaceted<ProjectFacet> instead of Faceted<ProjectFacet>
> ----------------------------------------------------------------------------------
>
> Key: FORGE-1540
> URL: https://issues.jboss.org/browse/FORGE-1540
> Project: Forge
> Issue Type: Enhancement
> Components: Plugin API
> Affects Versions: 2.0.0.Final
> Reporter: Max Barkley
> Priority: Minor
>
> In order to try and uninstall a facet from a project I must check if it is an instance of MutableFaceted and then cast like so:
> {code}
> if (project instanceof MutableFaceted) {
> ((MutableFaceted<ProjectFacet>) project).uninstall(someFacet);
> }
> {code}
> But as far as I can tell, every Project implementation implements MutableFaceted, so it would be nice if Project extended MutableFaceted so that I could avoid casting.
> Alternatively, if there is a good reason for having Project implementations which are not MutableFaceted, perhaps there could be a MutableProject interface for convenience:
> {code}
> public interface MutableProject extends Project, MutableFaceted<ProjectFacet> {}
> {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
12 years, 2 months
[JBoss JIRA] (FORGE-1542) Migrate from Twitter Bootstrap 2 to 3
by Antonio Goncalves (JIRA)
Antonio Goncalves created FORGE-1542:
----------------------------------------
Summary: Migrate from Twitter Bootstrap 2 to 3
Key: FORGE-1542
URL: https://issues.jboss.org/browse/FORGE-1542
Project: Forge
Issue Type: Feature Request
Components: Scaffold
Affects Versions: 2.0.0.Final
Reporter: Antonio Goncalves
Priority: Minor
Fix For: 2.x Future
Twitter Bootstrap 3 is mobile first plus plenty of goodies. I think it would be good to migrate. Unfortunately it's not a piece of cake. I've tried to follow the migration guide (http://getbootstrap.com/migration/) and I gave up after struggling for more that one hour. That being said, I'm definitely not a designer/CSS guy ;o)
--
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
12 years, 2 months
[JBoss JIRA] (FORGE-1540) Have Project extends MutableFaceted<ProjectFacet> instead of Faceted<ProjectFacet>
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-1540?page=com.atlassian.jira.plugin... ]
George Gastaldi commented on FORGE-1540:
----------------------------------------
However IMHO it's best to follow the principle of least privilege and let the impl decide what's best
> Have Project extends MutableFaceted<ProjectFacet> instead of Faceted<ProjectFacet>
> ----------------------------------------------------------------------------------
>
> Key: FORGE-1540
> URL: https://issues.jboss.org/browse/FORGE-1540
> Project: Forge
> Issue Type: Enhancement
> Components: Plugin API
> Affects Versions: 2.0.0.Final
> Reporter: Max Barkley
> Priority: Minor
>
> In order to try and uninstall a facet from a project I must check if it is an instance of MutableFaceted and then cast like so:
> {code}
> if (project instanceof MutableFaceted) {
> ((MutableFaceted<ProjectFacet>) project).uninstall(someFacet);
> }
> {code}
> But as far as I can tell, every Project implementation implements MutableFaceted, so it would be nice if Project extended MutableFaceted so that I could avoid casting.
> Alternatively, if there is a good reason for having Project implementations which are not MutableFaceted, perhaps there could be a MutableProject interface for convenience:
> {code}
> public interface MutableProject extends Project, MutableFaceted<ProjectFacet> {}
> {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
12 years, 2 months
[JBoss JIRA] (FORGE-1540) Have Project extends MutableFaceted<ProjectFacet> instead of Faceted<ProjectFacet>
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-1540?page=com.atlassian.jira.plugin... ]
George Gastaldi commented on FORGE-1540:
----------------------------------------
Following your idea, How having {{MutableProject}} would be different from what is done currently? Perhaps having Project extending MutableFaceted might be a better choice I guess.
> Have Project extends MutableFaceted<ProjectFacet> instead of Faceted<ProjectFacet>
> ----------------------------------------------------------------------------------
>
> Key: FORGE-1540
> URL: https://issues.jboss.org/browse/FORGE-1540
> Project: Forge
> Issue Type: Enhancement
> Components: Plugin API
> Affects Versions: 2.0.0.Final
> Reporter: Max Barkley
> Priority: Minor
>
> In order to try and uninstall a facet from a project I must check if it is an instance of MutableFaceted and then cast like so:
> {code}
> if (project instanceof MutableFaceted) {
> ((MutableFaceted<ProjectFacet>) project).uninstall(someFacet);
> }
> {code}
> But as far as I can tell, every Project implementation implements MutableFaceted, so it would be nice if Project extended MutableFaceted so that I could avoid casting.
> Alternatively, if there is a good reason for having Project implementations which are not MutableFaceted, perhaps there could be a MutableProject interface for convenience:
> {code}
> public interface MutableProject extends Project, MutableFaceted<ProjectFacet> {}
> {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
12 years, 2 months
[JBoss JIRA] (FORGE-1541) Problems deploying addon
by Tom Cunningham (JIRA)
[ https://issues.jboss.org/browse/FORGE-1541?page=com.atlassian.jira.plugin... ]
Tom Cunningham updated FORGE-1541:
----------------------------------
Attachment: org.switchyard.tools.forge.plugin.SwitchyardConfigurationTest.txt
> Problems deploying addon
> ------------------------
>
> Key: FORGE-1541
> URL: https://issues.jboss.org/browse/FORGE-1541
> Project: Forge
> Issue Type: Bug
> Components: Test Harness
> Affects Versions: 2.0.0.Final
> Environment: Mac OS X Mavericks
> java version "1.7.0_45"
> Apache Maven 3.1.0 (893ca28a1da9d5f51ac03827af98bb730128f9f2; 2013-06-27 22:15:32-0400)
> Reporter: Tom Cunningham
> Attachments: org.switchyard.tools.forge.plugin.SwitchyardConfigurationTest.txt
>
>
> Problems deploying addons in 2.0.0.Final :
> org.switchyard.tools.forge.BasicFacetTest Time elapsed: -379,976.917 sec <<< ERROR!
> org.jboss.arquillian.container.spi.client.container.DeploymentException: AddonDependency org.switchyard.forge:switchyard-addon,2.0.0-SNAPSHOT failed to deploy.
> at org.jboss.forge.arquillian.ForgeDeployableContainer.waitForDeploymentCompletion(ForgeDeployableContainer.java:202)
> at org.jboss.forge.arquillian.ForgeDeployableContainer.deploy(ForgeDeployableContainer.java:116)
> at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$3.call(ContainerDeployController.java:161)
> at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$3.call(ContainerDeployController.java:128)
> at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.executeOperation(ContainerDeployController.java:271)
> at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.deploy(ContainerDeployController.java:127)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> To reproduce :
> git clone https://github.com/forge/plugin-switchyard.git
> git checkout 2.0
> mvn clean install
--
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
12 years, 2 months
[JBoss JIRA] (FORGE-1541) Problems deploying addon
by Tom Cunningham (JIRA)
Tom Cunningham created FORGE-1541:
-------------------------------------
Summary: Problems deploying addon
Key: FORGE-1541
URL: https://issues.jboss.org/browse/FORGE-1541
Project: Forge
Issue Type: Bug
Components: Test Harness
Affects Versions: 2.0.0.Final
Environment: Mac OS X Mavericks
java version "1.7.0_45"
Apache Maven 3.1.0 (893ca28a1da9d5f51ac03827af98bb730128f9f2; 2013-06-27 22:15:32-0400)
Reporter: Tom Cunningham
Attachments: org.switchyard.tools.forge.plugin.SwitchyardConfigurationTest.txt
Problems deploying addons in 2.0.0.Final :
org.switchyard.tools.forge.BasicFacetTest Time elapsed: -379,976.917 sec <<< ERROR!
org.jboss.arquillian.container.spi.client.container.DeploymentException: AddonDependency org.switchyard.forge:switchyard-addon,2.0.0-SNAPSHOT failed to deploy.
at org.jboss.forge.arquillian.ForgeDeployableContainer.waitForDeploymentCompletion(ForgeDeployableContainer.java:202)
at org.jboss.forge.arquillian.ForgeDeployableContainer.deploy(ForgeDeployableContainer.java:116)
at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$3.call(ContainerDeployController.java:161)
at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$3.call(ContainerDeployController.java:128)
at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.executeOperation(ContainerDeployController.java:271)
at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.deploy(ContainerDeployController.java:127)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
To reproduce :
git clone https://github.com/forge/plugin-switchyard.git
git checkout 2.0
mvn clean install
--
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
12 years, 2 months