[JBoss JIRA] (JBDS-3579) Fuse archetype catalog cannot be added with JBDS 9
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBDS-3579?page=com.atlassian.jira.plugin.... ]
Fred Bricon updated JBDS-3579:
------------------------------
Fix Version/s: 9.1.0.CR1
(was: 10.0.0.Alpha1)
> Fuse archetype catalog cannot be added with JBDS 9
> --------------------------------------------------
>
> Key: JBDS-3579
> URL: https://issues.jboss.org/browse/JBDS-3579
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: maven
> Affects Versions: 9.0.0.GA
> Reporter: Keith Babo
> Assignee: Fred Bricon
> Fix For: 9.1.0.CR1
>
>
> When adding the Fuse Integration Services archetype catalog to JBDS 9, the IDE reports that the catalog is empty. This works in Eclipse and I've heard reports that it also works in earlier versions of JBDS (although I have not confirmed this personally).
> Archetype catalog in question:
> https://repo.fusesource.com/nexus/content/groups/public/io/fabric8/archet...
> Steps to reproduce:
> - Preferences -> Maven -> Archetypes -> Add Remote Catalog
> - Add URL above for Catalog File
> - Click Verify ... and you get the message "Remote catalog is empty"
> - Click Finish and try to use the catalog from the New Maven Project wizard and the message is "No archetypes available for this catalog."
> Impact here is that Fuse customers looking to use Fuse on OpenShift cannot use JBDS to create new projects using our Maven archetypes (the primary means of getting started).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21716) Don't re-prompt for password
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21716?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-21716:
---------------------------------------------
main issue is how we get the password from the installer to eclipse in a secure manner.
eclipse itself will store it in its secure storage that is different based on the OS.
We'll need to get node.js to talk to eclipse secure storage mechanism to solve this, but even then - the user can start a new workspace and he'll be asked again.
So that will fail most times too.
Best thing I can think of is in the case of starting eclipse from the installer we can start it in an environment where the password is in an environment variable ...then it is at least not easily available; but it will only work the very first time.
> Don't re-prompt for password
> ----------------------------
>
> Key: JBIDE-21716
> URL: https://issues.jboss.org/browse/JBIDE-21716
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: cdk
> Reporter: Pete Muir
> Priority: Critical
> Fix For: 4.3.1.CR1, 4.4.0.Alpha1
>
>
> Having installed JBDS and CDK from the installer, and entered your password there, you get re-prompted for your password for the customer portal. This is a poor user experience.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21119) Update 4.5y.x TP to m2e 1.6.x (with fix for apache commons collections 3.2.2 / COLLECTIONS-580 / JBDS-3560)
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21119?page=com.atlassian.jira.plugi... ]
Fred Bricon reassigned JBIDE-21119:
-----------------------------------
Assignee: Nick Boldt (was: Fred Bricon)
> Update 4.5y.x TP to m2e 1.6.x (with fix for apache commons collections 3.2.2 / COLLECTIONS-580 / JBDS-3560)
> -----------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21119
> URL: https://issues.jboss.org/browse/JBIDE-21119
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven, target-platform, upstream
> Affects Versions: 4.3.0.Final
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.3.1.CR1
>
>
> Fred said: {quote}So the m2e archetype feature also embeds a version of vulnerable commons-collections, that we need to fix upstream (even though it's not really vulnerable, just makes people cringy) -- JBDS-3560
> {quote}
> So, we need a new version of m2e 1.6.x (with fix for apache commons collections 3.2.2 / COLLECTIONS-580 / JBDS-3560) and we can then mirror it and update the 4.50.x and 4.51.x TPs (for JBDS 9.1, not 9.0.1).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21716) Don't re-prompt for password
by Pete Muir (JIRA)
Pete Muir created JBIDE-21716:
---------------------------------
Summary: Don't re-prompt for password
Key: JBIDE-21716
URL: https://issues.jboss.org/browse/JBIDE-21716
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: cdk
Reporter: Pete Muir
Priority: Critical
Having installed JBDS and CDK from the installer, and entered your password there, you get re-prompted for your password for the customer portal. This is a poor user experience.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-20687) Deployed war is NOT the specified war name
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20687?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-20687:
-------------------------------------
Punted to the Neon release :-/
> Deployed war is NOT the specified war name
> ------------------------------------------
>
> Key: JBIDE-20687
> URL: https://issues.jboss.org/browse/JBIDE-20687
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven, server, upstream
> Affects Versions: 4.3.0.CR1
> Reporter: ehsavoie Hugonnet
> Assignee: Fred Bricon
> Priority: Critical
> Fix For: 4.4.0.Alpha1
>
>
> The deployed war name is the *artifactId* and not the specified *warName* from the war plugin nor the *finalName*.
> Sample pom.xml which exibits the issue
> {code:xml}<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
> <modelVersion>4.0.0</modelVersion>
> <groupId>org.glassfish-samples</groupId>
> <artifactId>auction</artifactId>
> <version>4.0-SNAPSHOT</version>
> <packaging>war</packaging>
> <name>WebSocket Auction Sample Application</name>
>
> <dependencies>
> <dependency>
> <groupId>javax</groupId>
> <artifactId>javaee-api</artifactId>
> <version>7.0</version>
> <scope>provided</scope>
> </dependency>
> </dependencies>
>
> <build>
> <finalName>websocket-auction</finalName>
> <plugins>
> <plugin>
> <artifactId>maven-compiler-plugin</artifactId>
> <version>3.1</version>
> <configuration>
> <source>1.8</source>
> <target>1.8</target>
> </configuration>
> </plugin>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-war-plugin</artifactId>
> <version>2.3</version>
> <configuration>
> <failOnMissingWebXml>false</failOnMissingWebXml>
> <warName>websocket-auction</warName>
> </configuration>
> </plugin>
> </plugins>
> </build>
> </project>
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-20687) Deployed war is NOT the specified war name
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20687?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-20687:
--------------------------------
Fix Version/s: 4.4.0.Alpha1
(was: 4.3.1.CR1)
> Deployed war is NOT the specified war name
> ------------------------------------------
>
> Key: JBIDE-20687
> URL: https://issues.jboss.org/browse/JBIDE-20687
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven, server, upstream
> Affects Versions: 4.3.0.CR1
> Reporter: ehsavoie Hugonnet
> Assignee: Fred Bricon
> Priority: Critical
> Fix For: 4.4.0.Alpha1
>
>
> The deployed war name is the *artifactId* and not the specified *warName* from the war plugin nor the *finalName*.
> Sample pom.xml which exibits the issue
> {code:xml}<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
> <modelVersion>4.0.0</modelVersion>
> <groupId>org.glassfish-samples</groupId>
> <artifactId>auction</artifactId>
> <version>4.0-SNAPSHOT</version>
> <packaging>war</packaging>
> <name>WebSocket Auction Sample Application</name>
>
> <dependencies>
> <dependency>
> <groupId>javax</groupId>
> <artifactId>javaee-api</artifactId>
> <version>7.0</version>
> <scope>provided</scope>
> </dependency>
> </dependencies>
>
> <build>
> <finalName>websocket-auction</finalName>
> <plugins>
> <plugin>
> <artifactId>maven-compiler-plugin</artifactId>
> <version>3.1</version>
> <configuration>
> <source>1.8</source>
> <target>1.8</target>
> </configuration>
> </plugin>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-war-plugin</artifactId>
> <version>2.3</version>
> <configuration>
> <failOnMissingWebXml>false</failOnMissingWebXml>
> <warName>websocket-auction</warName>
> </configuration>
> </plugin>
> </plugins>
> </build>
> </project>
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month