[JBoss JIRA] (JBIDE-19427) Redundant warning for JPA entity
by Arun Gupta (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19427?page=com.atlassian.jira.plugi... ]
Arun Gupta updated JBIDE-19427:
-------------------------------
Attachment: Screen Shot 2015-03-10 at 2.39.46 PM.png
Warning is shown in the screenshot.
> Redundant warning for JPA entity
> --------------------------------
>
> Key: JBIDE-19427
> URL: https://issues.jboss.org/browse/JBIDE-19427
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Affects Versions: 4.3.0.Alpha2
> Reporter: Arun Gupta
> Attachments: Screen Shot 2015-03-10 at 2.39.46 PM.png
>
>
> Student entity is defined as:
> @Entity
> @XmlRootElement
> @NamedQuery(name="findAllStudents", query="select s from Student s")
> public class Student implements Serializable {
> Persistence.xml is defined as:
> <?xml version="1.0" encoding="UTF-8"?>
> <persistence version="2.1"
> xmlns="http://xmlns.jcp.org/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/persistence http://xmlns.jcp.org/xml/ns/persistence/persistence_2_1.xsd">
> <persistence-unit name="HelloJavaEE7">
> <properties>
> <property name="javax.persistence.schema-generation.database.action"
> value="drop-and-create" />
> <property name="javax.persistence.schema-generation.create-source"
> value="metadata" />
> <property name="javax.persistence.schema-generation.drop-source"
> value="metadata" />
> <property name="hibernate.show_sql" value="true" />
> <property name="hibernate.format_sql" value="true" />
> </properties>
> </persistence-unit>
> </persistence>
> Editor shows a red cross on Student class declaration with the error message "Class "org.sample.Student" is managed, but is not listed in the persistence.xml file".
> By default, all entities are included and this error should not occur.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 1 month
[JBoss JIRA] (JBIDE-19427) Redundant warning for JPA entity
by Arun Gupta (JIRA)
Arun Gupta created JBIDE-19427:
----------------------------------
Summary: Redundant warning for JPA entity
Key: JBIDE-19427
URL: https://issues.jboss.org/browse/JBIDE-19427
Project: Tools (JBoss Tools)
Issue Type: Bug
Affects Versions: 4.3.0.Alpha2
Reporter: Arun Gupta
Student entity is defined as:
@Entity
@XmlRootElement
@NamedQuery(name="findAllStudents", query="select s from Student s")
public class Student implements Serializable {
Persistence.xml is defined as:
<?xml version="1.0" encoding="UTF-8"?>
<persistence version="2.1"
xmlns="http://xmlns.jcp.org/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/persistence http://xmlns.jcp.org/xml/ns/persistence/persistence_2_1.xsd">
<persistence-unit name="HelloJavaEE7">
<properties>
<property name="javax.persistence.schema-generation.database.action"
value="drop-and-create" />
<property name="javax.persistence.schema-generation.create-source"
value="metadata" />
<property name="javax.persistence.schema-generation.drop-source"
value="metadata" />
<property name="hibernate.show_sql" value="true" />
<property name="hibernate.format_sql" value="true" />
</properties>
</persistence-unit>
</persistence>
Editor shows a red cross on Student class declaration with the error message "Class "org.sample.Student" is managed, but is not listed in the persistence.xml file".
By default, all entities are included and this error should not occur.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 1 month
[JBoss JIRA] (JBDS-3371) The method openFileDialog(null, null) is undefined for the type FileOpenService
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3371?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov updated JBDS-3371:
---------------------------------
Description:
Im getting "The method openFileDialog(null, null) is undefined for the type FileOpenService" error wen trying to run the code bellow.:
{code}
package com.hrtrust.ps.scanner;
// add javaws.jar to the classpath during compilation
import javax.jnlp.FileOpenService;
import javax.jnlp.FileSaveService;
import javax.jnlp.FileContents;
import javax.jnlp.ServiceManager;
import javax.jnlp.UnavailableServiceException;
import java.io.*;
import javax.jnlp.ExtendedService;
public class FileHandler {
static private FileOpenService fos = null;
static private FileSaveService fss = null;
static private FileContents fc = null;
static private ExtendedService exs = null;
// retrieves a reference to the JNLP services
private static synchronized void initialize() {
if (fss != null) {
return;
}
try {
fos = (FileOpenService) ServiceManager.lookup("javax.jnlp.FileOpenService");
fss = (FileSaveService) ServiceManager.lookup("javax.jnlp.FileSaveService");
exs = (ExtendedService) ServiceManager.lookup("javax.jnlp.ExtendedService");
} catch (UnavailableServiceException e) {
fos = null;
fss = null;
exs = null;
}
}
public static FileContents getDLL(File dllFile) {
initialize();
try {
fc = exs.openFile(dllFile);
} catch (IOException ioe) {
ioe.printStackTrace(System.out);
return null;
}
return fc;
}
// displays open file dialog and reads selected file using FileOpenService
public static String open() {
initialize();
try {
fc = fos.openFileDialog(null, null);
return readFromFile(fc);
} catch (IOException ioe) {
ioe.printStackTrace(System.out);
return null;
}
}
// displays saveFileDialog and saves file using FileSaveService
public static void save(String txt) {
initialize();
try {
// Show save dialog if no name is already given
if (fc == null) {
fc = fss.saveFileDialog(null, null,
new ByteArrayInputStream(txt.getBytes()), null);
// file saved, done
return;
}
// use this only when filename is known
if (fc != null) {
writeToFile(txt, fc);
}
} catch (IOException ioe) {
ioe.printStackTrace(System.out);
}
}
// displays saveAsFileDialog and saves file using FileSaveService
public static void saveAs(String txt) {
initialize();
try {
if (fc == null) {
// If not already saved. Save-as is like save
save(txt);
} else {
fc = fss.saveAsFileDialog(null, null, fc);
save(txt);
}
} catch (IOException ioe) {
ioe.printStackTrace(System.out);
}
}
private static void writeToFile(String txt, FileContents fc) throws IOException {
int sizeNeeded = txt.length() * 2;
if (sizeNeeded > fc.getMaxLength()) {
fc.setMaxLength(sizeNeeded);
}
BufferedWriter os = new BufferedWriter(new OutputStreamWriter(fc.getOutputStream(true)));
os.write(txt);
os.close();
}
private static String readFromFile(FileContents fc) throws IOException {
if (fc == null) {
return null;
}
BufferedReader br = new BufferedReader(new InputStreamReader(fc.getInputStream()));
StringBuffer sb = new StringBuffer((int) fc.getLength());
String line = br.readLine();
while (line != null) {
sb.append(line);
sb.append("\n");
line = br.readLine();
}
br.close();
return sb.toString();
}
}
{code}
NB. fc = fos.openFileDialog(null, null); is the line that gives an error. (FileOpenService)....FileSaveService and FileContents works just fine.
was:
Im getting "The method openFileDialog(null, null) is undefined for the type FileOpenService" error wen trying to run the code bellow.:
package com.hrtrust.ps.scanner;
// add javaws.jar to the classpath during compilation
import javax.jnlp.FileOpenService;
import javax.jnlp.FileSaveService;
import javax.jnlp.FileContents;
import javax.jnlp.ServiceManager;
import javax.jnlp.UnavailableServiceException;
import java.io.*;
import javax.jnlp.ExtendedService;
public class FileHandler {
static private FileOpenService fos = null;
static private FileSaveService fss = null;
static private FileContents fc = null;
static private ExtendedService exs = null;
// retrieves a reference to the JNLP services
private static synchronized void initialize() {
if (fss != null) {
return;
}
try {
fos = (FileOpenService) ServiceManager.lookup("javax.jnlp.FileOpenService");
fss = (FileSaveService) ServiceManager.lookup("javax.jnlp.FileSaveService");
exs = (ExtendedService) ServiceManager.lookup("javax.jnlp.ExtendedService");
} catch (UnavailableServiceException e) {
fos = null;
fss = null;
exs = null;
}
}
public static FileContents getDLL(File dllFile) {
initialize();
try {
fc = exs.openFile(dllFile);
} catch (IOException ioe) {
ioe.printStackTrace(System.out);
return null;
}
return fc;
}
// displays open file dialog and reads selected file using FileOpenService
public static String open() {
initialize();
try {
fc = fos.openFileDialog(null, null);
return readFromFile(fc);
} catch (IOException ioe) {
ioe.printStackTrace(System.out);
return null;
}
}
// displays saveFileDialog and saves file using FileSaveService
public static void save(String txt) {
initialize();
try {
// Show save dialog if no name is already given
if (fc == null) {
fc = fss.saveFileDialog(null, null,
new ByteArrayInputStream(txt.getBytes()), null);
// file saved, done
return;
}
// use this only when filename is known
if (fc != null) {
writeToFile(txt, fc);
}
} catch (IOException ioe) {
ioe.printStackTrace(System.out);
}
}
// displays saveAsFileDialog and saves file using FileSaveService
public static void saveAs(String txt) {
initialize();
try {
if (fc == null) {
// If not already saved. Save-as is like save
save(txt);
} else {
fc = fss.saveAsFileDialog(null, null, fc);
save(txt);
}
} catch (IOException ioe) {
ioe.printStackTrace(System.out);
}
}
private static void writeToFile(String txt, FileContents fc) throws IOException {
int sizeNeeded = txt.length() * 2;
if (sizeNeeded > fc.getMaxLength()) {
fc.setMaxLength(sizeNeeded);
}
BufferedWriter os = new BufferedWriter(new OutputStreamWriter(fc.getOutputStream(true)));
os.write(txt);
os.close();
}
private static String readFromFile(FileContents fc) throws IOException {
if (fc == null) {
return null;
}
BufferedReader br = new BufferedReader(new InputStreamReader(fc.getInputStream()));
StringBuffer sb = new StringBuffer((int) fc.getLength());
String line = br.readLine();
while (line != null) {
sb.append(line);
sb.append("\n");
line = br.readLine();
}
br.close();
return sb.toString();
}
}
NB. fc = fos.openFileDialog(null, null); is the line that gives an error. (FileOpenService)....FileSaveService and FileContents works just fine.
> The method openFileDialog(null, null) is undefined for the type FileOpenService
> -------------------------------------------------------------------------------
>
> Key: JBDS-3371
> URL: https://issues.jboss.org/browse/JBDS-3371
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Environment: JBoss Developer Studio Version: 8.0.2.GA
> Reporter: Ludumo Sankobe
>
> Im getting "The method openFileDialog(null, null) is undefined for the type FileOpenService" error wen trying to run the code bellow.:
> {code}
> package com.hrtrust.ps.scanner;
> // add javaws.jar to the classpath during compilation
> import javax.jnlp.FileOpenService;
> import javax.jnlp.FileSaveService;
> import javax.jnlp.FileContents;
> import javax.jnlp.ServiceManager;
> import javax.jnlp.UnavailableServiceException;
> import java.io.*;
> import javax.jnlp.ExtendedService;
> public class FileHandler {
> static private FileOpenService fos = null;
> static private FileSaveService fss = null;
> static private FileContents fc = null;
> static private ExtendedService exs = null;
> // retrieves a reference to the JNLP services
> private static synchronized void initialize() {
> if (fss != null) {
> return;
> }
> try {
> fos = (FileOpenService) ServiceManager.lookup("javax.jnlp.FileOpenService");
> fss = (FileSaveService) ServiceManager.lookup("javax.jnlp.FileSaveService");
> exs = (ExtendedService) ServiceManager.lookup("javax.jnlp.ExtendedService");
>
> } catch (UnavailableServiceException e) {
> fos = null;
> fss = null;
> exs = null;
> }
> }
> public static FileContents getDLL(File dllFile) {
> initialize();
> try {
> fc = exs.openFile(dllFile);
> } catch (IOException ioe) {
> ioe.printStackTrace(System.out);
> return null;
> }
> return fc;
> }
> // displays open file dialog and reads selected file using FileOpenService
> public static String open() {
> initialize();
> try {
> fc = fos.openFileDialog(null, null);
> return readFromFile(fc);
> } catch (IOException ioe) {
> ioe.printStackTrace(System.out);
> return null;
> }
> }
> // displays saveFileDialog and saves file using FileSaveService
> public static void save(String txt) {
> initialize();
> try {
> // Show save dialog if no name is already given
> if (fc == null) {
> fc = fss.saveFileDialog(null, null,
> new ByteArrayInputStream(txt.getBytes()), null);
> // file saved, done
> return;
> }
> // use this only when filename is known
> if (fc != null) {
> writeToFile(txt, fc);
> }
> } catch (IOException ioe) {
> ioe.printStackTrace(System.out);
> }
> }
> // displays saveAsFileDialog and saves file using FileSaveService
> public static void saveAs(String txt) {
> initialize();
> try {
> if (fc == null) {
> // If not already saved. Save-as is like save
> save(txt);
> } else {
> fc = fss.saveAsFileDialog(null, null, fc);
> save(txt);
> }
> } catch (IOException ioe) {
> ioe.printStackTrace(System.out);
> }
> }
> private static void writeToFile(String txt, FileContents fc) throws IOException {
> int sizeNeeded = txt.length() * 2;
> if (sizeNeeded > fc.getMaxLength()) {
> fc.setMaxLength(sizeNeeded);
> }
> BufferedWriter os = new BufferedWriter(new OutputStreamWriter(fc.getOutputStream(true)));
> os.write(txt);
> os.close();
> }
> private static String readFromFile(FileContents fc) throws IOException {
> if (fc == null) {
> return null;
> }
> BufferedReader br = new BufferedReader(new InputStreamReader(fc.getInputStream()));
> StringBuffer sb = new StringBuffer((int) fc.getLength());
> String line = br.readLine();
> while (line != null) {
> sb.append(line);
> sb.append("\n");
> line = br.readLine();
> }
> br.close();
> return sb.toString();
> }
> }
> {code}
> NB. fc = fos.openFileDialog(null, null); is the line that gives an error. (FileOpenService)....FileSaveService and FileContents works just fine.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 1 month
[JBoss JIRA] (JBIDE-19140) After installing JBT 4.2.2, seeing non-fatal class cast exception when starting eclipse
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19140?page=com.atlassian.jira.plugi... ]
Len DiMaggio closed JBIDE-19140.
--------------------------------
Verified with 4.2.3.beta1
> After installing JBT 4.2.2, seeing non-fatal class cast exception when starting eclipse
> ---------------------------------------------------------------------------------------
>
> Key: JBIDE-19140
> URL: https://issues.jboss.org/browse/JBIDE-19140
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.2.2.Final
> Environment: RHEL6
> Java 7
> Reporter: Len DiMaggio
> Assignee: Nick Boldt
> Fix For: 4.2.3.Beta1
>
> Attachments: jbosstools-diagnostics-20150130124300.zip
>
>
> See the attached log file for this exception:
> java.lang.ClassCastException: org.eclipse.osgi.internal.framework.EquinoxConfiguration$1 cannot be cast to java.lang.String
> at org.eclipse.m2e.logback.configuration.LogHelper.logJavaProperties(LogHelper.java:26)
> at org.eclipse.m2e.logback.configuration.LogPlugin.loadConfiguration(LogPlugin.java:189)
> at org.eclipse.m2e.logback.configuration.LogPlugin.configureLogback(LogPlugin.java:144)
> at org.eclipse.m2e.logback.configuration.LogPlugin.access$2(LogPlugin.java:107)
> at org.eclipse.m2e.logback.configuration.LogPlugin$1.run(LogPlugin.java:62)
> at java.util.TimerThread.mainLoop(Timer.java:555)
> at java.util.TimerThread.run(Timer.java:505)
> ipse.m2e.logback.configuration.LogHelper.logJavaProperties(LogHelper.java:26)
> at org.eclipse.m2e.logback.configuration.LogPlugin.loadConfiguration(LogPlugin.java:189)
> at org.eclipse.m2e.logback.configuration.LogPlugin.configureLogback(LogPlugin.java:144)
> at org.ecl
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 1 month
[JBoss JIRA] (JBTIS-408) Update JBoss ESB tooling to 4.2.1.Final and fix test error
by Brian Fitzpatrick (JIRA)
[ https://issues.jboss.org/browse/JBTIS-408?page=com.atlassian.jira.plugin.... ]
Brian Fitzpatrick commented on JBTIS-408:
-----------------------------------------
Done - [~pleacu] will take the new JBTIS-esb-4.2.x/70/ build and use it with the 8.0.1. stack so we're up to date again
Thanks Paul & [~nickboldt] for all the help with this!
> Update JBoss ESB tooling to 4.2.1.Final and fix test error
> ----------------------------------------------------------
>
> Key: JBTIS-408
> URL: https://issues.jboss.org/browse/JBTIS-408
> Project: JBoss Tools Integration Stack
> Issue Type: Component Upgrade
> Components: ESB
> Affects Versions: 4.1.3.Final
> Reporter: Brian Fitzpatrick
> Assignee: Brian Fitzpatrick
> Fix For: 8.0.1.GA
>
>
> We hit some test failures after some files were removed upstream. Looks like someone deleted soa-p-5.3.0.ER5.zip.
> {code}
> [ERROR] Failed to execute goal com.googlecode.maven-download-plugin:maven-download-plugin:1.1.0:wget (install-soa-p-5.0) on project org.jboss.tools.esb.project.core.test: IO Error: /home/hudson/static_build_env/jbds/download-cache/soa-p-5.3.0.ER5.zip (No such file or directory) -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal com.googlecode.maven-download-plugin:maven-download-plugin:1.1.0:wget (install-soa-p-5.0) on project org.jboss.tools.esb.project.core.test: IO Error
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> Caused by: org.apache.maven.plugin.MojoExecutionException: IO Error
> at com.googlecode.WGet.execute(WGet.java:203)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
> ... 19 more
> Caused by: java.io.FileNotFoundException: /home/hudson/static_build_env/jbds/download-cache/soa-p-5.3.0.ER5.zip (No such file or directory)
> at java.io.FileInputStream.open(Native Method)
> at java.io.FileInputStream.<init>(FileInputStream.java:120)
> at com.googlecode.SignatureUtils.computeSignatureAsString(SignatureUtils.java:45)
> at com.googlecode.SignatureUtils.getMD5(SignatureUtils.java:61)
> at com.googlecode.DownloadCache.getEntry(DownloadCache.java:54)
> at com.googlecode.DownloadCache.getArtifact(DownloadCache.java:73)
> at com.googlecode.WGet.execute(WGet.java:165)
> ... 21 more
> {code}
> To fix this error, we will update that to soa-p-5.3.0.GA.zip.
> And at the same time we will upgrade the JBTIS Target Platform version to 4.2.1.Final and bump the versions.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 1 month
[JBoss JIRA] (JBTIS-408) Update JBoss ESB tooling to 4.2.1.Final and fix test error
by Brian Fitzpatrick (JIRA)
[ https://issues.jboss.org/browse/JBTIS-408?page=com.atlassian.jira.plugin.... ]
Brian Fitzpatrick commented on JBTIS-408:
-----------------------------------------
Updated in master and 4.2.x branches
> Update JBoss ESB tooling to 4.2.1.Final and fix test error
> ----------------------------------------------------------
>
> Key: JBTIS-408
> URL: https://issues.jboss.org/browse/JBTIS-408
> Project: JBoss Tools Integration Stack
> Issue Type: Component Upgrade
> Components: ESB
> Affects Versions: 4.1.3.Final
> Reporter: Brian Fitzpatrick
> Assignee: Brian Fitzpatrick
> Fix For: 8.0.1.GA
>
>
> We hit some test failures after some files were removed upstream. Looks like someone deleted soa-p-5.3.0.ER5.zip.
> {code}
> [ERROR] Failed to execute goal com.googlecode.maven-download-plugin:maven-download-plugin:1.1.0:wget (install-soa-p-5.0) on project org.jboss.tools.esb.project.core.test: IO Error: /home/hudson/static_build_env/jbds/download-cache/soa-p-5.3.0.ER5.zip (No such file or directory) -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal com.googlecode.maven-download-plugin:maven-download-plugin:1.1.0:wget (install-soa-p-5.0) on project org.jboss.tools.esb.project.core.test: IO Error
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> Caused by: org.apache.maven.plugin.MojoExecutionException: IO Error
> at com.googlecode.WGet.execute(WGet.java:203)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
> ... 19 more
> Caused by: java.io.FileNotFoundException: /home/hudson/static_build_env/jbds/download-cache/soa-p-5.3.0.ER5.zip (No such file or directory)
> at java.io.FileInputStream.open(Native Method)
> at java.io.FileInputStream.<init>(FileInputStream.java:120)
> at com.googlecode.SignatureUtils.computeSignatureAsString(SignatureUtils.java:45)
> at com.googlecode.SignatureUtils.getMD5(SignatureUtils.java:61)
> at com.googlecode.DownloadCache.getEntry(DownloadCache.java:54)
> at com.googlecode.DownloadCache.getArtifact(DownloadCache.java:73)
> at com.googlecode.WGet.execute(WGet.java:165)
> ... 21 more
> {code}
> To fix this error, we will update that to soa-p-5.3.0.GA.zip.
> And at the same time we will upgrade the JBTIS Target Platform version to 4.2.1.Final and bump the versions.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 1 month
[JBoss JIRA] (JBIDE-19426) Need to add cordova-4.3.0 support
by Ilya Buziuk (JIRA)
Ilya Buziuk created JBIDE-19426:
-----------------------------------
Summary: Need to add cordova-4.3.0 support
Key: JBIDE-19426
URL: https://issues.jboss.org/browse/JBIDE-19426
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: aerogear-hybrid, cordovasim
Affects Versions: 4.3.0.Alpha1
Reporter: Ilya Buziuk
Assignee: Ilya Buziuk
Fix For: 4.3.0.Alpha2
Apache Cordova 4.3.0 is out - need to add support for cordovasim and thym
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 1 month
[JBoss JIRA] (JBTIS-407) Cannot update all BPMN2 features from 7.0.3.GA to 7.1.0.CR2
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-407?page=com.atlassian.jira.plugin.... ]
Paul Leacu resolved JBTIS-407.
------------------------------
Assignee: Paul Leacu (was: Robert (Bob) Brodt)
Fix Version/s: 7.1.0.CR3
4.1.7.CR3
Resolution: Done
Issue corrected in bpmn2 - feature restored to name.
I'll add to my handoff checklist a test against the last installed JBDSIS.
https://github.com/jbosstools/jbosstools-integration-stack/commit/f994f92...
Greetings,
The latest Eclipse-Kepler capable, JBDS 7.1.1.GA compatible Integration Stack candidate release
tooling is available for QE testing. This capture contains updated:
* BPMN2 1.0.0.Final (updated) https://issues.jboss.org/browse/JBTIS-407
* JBTIS TP 4.1.11.Final
This release is for *internal consumption only* until after QE has sanctioned it.
JBDSIS 7.1.0.CR3, JBTIS 4.1.7.CR3
1. If installing from Eclipse Luna:
Help > Eclipse Marketplace...
- in the 'Search' tab enter 'jbds' in the 'Find' input widget
- select the 'Go' button
- install 'Red Hat JBoss Developer Studio 7.1.1.GA'
2. Start jbdevstudio or eclipse-with-jbds from step 1, then:
Help > Install New Software...
Add...
- use this for 'Location:' for the production integration stack:
http://www.qa.jboss.com/binaries/RHDS/updates/development/kepler/integrat...
Done!
JBoss Central is supported for the production capture (JBDSIS):
* Specify the integration stack discovery artifact:
./jbdevstudio -vmargs -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/7.1.0.CR3/devstudio-integration-stack-directory.xml
-Djboss.discovery.site.integration-stack.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/7.1.0.CR3
The standard p2 installer is available for the .CR2 community capture (JBTIS):
* Install JBoss Tools 4.1.2.Final:
Help > Eclipse Marketplace...
- in the 'Search' tab enter 'jboss tools' in the 'Find' input widget
- select the 'Go' button
- install 'JBoss Tools 4.1.2.Final'
* Help > Install New Software...
Add...
- use this for 'Location:' for the production integration stack:
http://download.jboss.org/jbosstools/updates/development/kepler/integrati...
JBoss Central is supported for the .Final community capture (JBTIS):
* Start eclipse-with-jboss-tools, then:
* Specify the integration stack discovery artifact:
./eclipse -vmargs -Djboss.discovery.directory.url=http://download.jboss.org/jbosstools/discovery/development/integration-stack/4.1.7.CR3/jbosstools-integration-stack-directory.xml
-Djboss.discovery.site.integration-stack.url=http://download.jboss.org/jbosstools/discovery/development/integration-stack/4.1.7.CR3
Offline zip files are supported for both production and community installs:
1. http://www.qa.jboss.com/binaries/RHDS/updates/development/kepler/integrat...
http://www.qa.jboss.com/binaries/RHDS/updates/development/kepler/integrat...
2. http://download.jboss.org/jbosstools/updates/development/kepler/integrati...
http://download.jboss.org/jbosstools/updates/development/kepler/integrati...
For component and QE test developers - the JBTIS target platforms are:
https://repository.jboss.org/nexus/content/repositories/releases/org/jbos...
http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.1.11.F...
Note that the integration stack update site is in a QE development area until after it's validated. If you have
trouble accessing the server add these lines to your /etc/hosts or C:\windows\system32\drivers\etc\hosts
file:
10.16.89.17 dev39.mw.lab.eng.bos.redhat.com www.qa.jboss.com
10.16.90.43 hudson.qa.jboss.com
Thanks!
> Cannot update all BPMN2 features from 7.0.3.GA to 7.1.0.CR2
> -----------------------------------------------------------
>
> Key: JBTIS-407
> URL: https://issues.jboss.org/browse/JBTIS-407
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: distribution
> Affects Versions: 7.1.0.CR2
> Environment: Installed: JBDS 7.1.1.GA + JBDS-IS 7.0.3.GA
> Update to: JBDS-IS 7.1.0.CR2
> Reporter: Andrej Podhradsky
> Assignee: Paul Leacu
> Priority: Blocker
> Fix For: 7.1.0.CR3, 4.1.7.CR3
>
>
> The follwoing error orrcurs when updating from JBDS-IS 7.0.3.GA to JBDS-IS 7.1.0.CR2
> Cannot complete the install because of a conflicting dependency.
> Software being installed: BPMN2 Metamodel 1.0.0.Final (org.eclipse.bpmn2.feature.group 1.0.0.Final)
> Software currently installed: BPMN2 Project Feature 0.7.0.201308220617 (org.eclipse.bpmn2.feature.feature.group 0.7.0.201308220617)
> Only one of the following can be installed at once:
> BPMN2 Edit Support 0.7.0.201308220617 (org.eclipse.bpmn2.edit 0.7.0.201308220617)
> BPMN2 Edit Support 1.0.0.Final (org.eclipse.bpmn2.edit 1.0.0.Final)
> Cannot satisfy dependency:
> From: BPMN2 Project Feature 0.7.0.201308220617 (org.eclipse.bpmn2.feature.feature.group 0.7.0.201308220617)
> To: org.eclipse.bpmn2.edit [0.7.0.201308220617]
> Cannot satisfy dependency:
> From: BPMN2 Metamodel 1.0.0.Final (org.eclipse.bpmn2.feature.group 1.0.0.Final)
> To: org.eclipse.bpmn2.edit [1.0.0.Final]
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 1 month
[JBoss JIRA] (JBIDE-19371) Allow OpenShiftRedirectionStrategy to determine the auth scheme
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19371?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-19371:
-------------------------------------
Summary: Allow OpenShiftRedirectionStrategy to determine the auth scheme (was: Refactor the OpenShiftRedirectionStrategy to get auth scheme)
> Allow OpenShiftRedirectionStrategy to determine the auth scheme
> ---------------------------------------------------------------
>
> Key: JBIDE-19371
> URL: https://issues.jboss.org/browse/JBIDE-19371
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.0.Alpha2
> Reporter: Jeff Cantrill
> Fix For: 4.3.0.Alpha2
>
>
> Introducing an authorization client which is able to determine how to authenticate when it gets a 401 and includes the following headers:
> (org.apache.http.Header[]) [Www-Authenticate: Basic realm="openshift", Date: Wed, 25 Feb 2015 20:11:49 GMT, Content-Length: 0, Content-Type: text/plain; charset=utf-8]
> Add method to identify the auth scheme and return the realm. Update the 'canconnect' endpoint to use this function.
> This was achieved by trying to auth with empty username and password
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 1 month