[JBoss JIRA] (JBIDE-13405) Deploying a RAR with JAR inside fails using remote systems via SSH
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13405?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-13405:
-------------------------------------
Chris, can you attach some sample projects to help us troubleshoot the problem?
> Deploying a RAR with JAR inside fails using remote systems via SSH
> ------------------------------------------------------------------
>
> Key: JBIDE-13405
> URL: https://issues.jboss.org/browse/JBIDE-13405
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JBossAS/Servers
> Affects Versions: 4.0.0.Final
> Environment: JBoss AS 7.1.1 Final, Eclipse Juno SR1, JBoss Tools 4.0.0 Final
> Reporter: Chris Roberts
> Assignee: Fred Bricon
>
> Exploding dependant jars seems to have issues for rars. I didn't work out if this is a problem in JBoss Tools or RSE. I suspect a little of both. It seems looking at the source that only the 'Local' RSE adapter correctly explodes deployments?
> 1) Create a maven project, set the packaging to rar
> 2) Create a second maven project, set the packaging to jar
> 3) Include the jar as a maven compile dependency of the rar
> 4) Import both into eclipse
> 5) Deploy to a remote (JBoss AS) server via RSE SSH/dstore/FTP fails
> It seems the JBoss Server Adapter (I think) creates the directory:
> xxxxx-1.0.rar/xxxxx-1.0.jar/
> on deployment. It then requests upload for the jar over the top of the directory which fails. With FTP this looks like:
> CD xxxxx-1.0.rar/
> MKD xxxxx-1.0.jar
> STOR xxxxx-1.0.jar <fails because directory exists>
> This is my first bug opened on JBoss/eclipse, so please point me on if you think this should be opened on RSE, but I think looking at the source it belongs here.
--
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
13 years, 2 months
[JBoss JIRA] (JBIDE-13405) Deploying a RAR with JAR inside fails using remote systems via SSH
by Chris Roberts (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13405?page=com.atlassian.jira.plugi... ]
Chris Roberts commented on JBIDE-13405:
---------------------------------------
I did a bunch more research on this last night. It seems org.jboss.ide.eclipse.as.core/AbstractServerToolsPublisher.java expects the RSE handlers to be able to identify and package jars, related to the forceZip code.
This seems to work for local (it seems the RSE local handler deals with the archive, possibly with copyFromArchive), but the RSE SSH/FTP/dstore connectors don't seem to be prepared to deal with forceZip. So JBoss makes the directory expecting the handler to uncompress the jar into it, and for SSH/FTP/dstore this doesn't work. I tried to modify the SFTP connector to deal with the JBoss forceZipped archives, but I couldn't get something in the time I had.
I was able to make a workaround for myself for disabling forceZip (forceZip = false) in org.jboss.ide.eclipse.as.core/AbstractServerToolsPublisher.java. This obviously means for remote systems the upload takes a long time with a lot of class files & I'm relying on a patched org.jboss.ide.eclipse.as.core, but I've got something working for now.
> Deploying a RAR with JAR inside fails using remote systems via SSH
> ------------------------------------------------------------------
>
> Key: JBIDE-13405
> URL: https://issues.jboss.org/browse/JBIDE-13405
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JBossAS/Servers
> Affects Versions: 4.0.0.Final
> Environment: JBoss AS 7.1.1 Final, Eclipse Juno SR1, JBoss Tools 4.0.0 Final
> Reporter: Chris Roberts
> Assignee: Fred Bricon
>
> Exploding dependant jars seems to have issues for rars. I didn't work out if this is a problem in JBoss Tools or RSE. I suspect a little of both. It seems looking at the source that only the 'Local' RSE adapter correctly explodes deployments?
> 1) Create a maven project, set the packaging to rar
> 2) Create a second maven project, set the packaging to jar
> 3) Include the jar as a maven compile dependency of the rar
> 4) Import both into eclipse
> 5) Deploy to a remote (JBoss AS) server via RSE SSH/dstore/FTP fails
> It seems the JBoss Server Adapter (I think) creates the directory:
> xxxxx-1.0.rar/xxxxx-1.0.jar/
> on deployment. It then requests upload for the jar over the top of the directory which fails. With FTP this looks like:
> CD xxxxx-1.0.rar/
> MKD xxxxx-1.0.jar
> STOR xxxxx-1.0.jar <fails because directory exists>
> This is my first bug opened on JBoss/eclipse, so please point me on if you think this should be opened on RSE, but I think looking at the source it belongs here.
--
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
13 years, 2 months
[JBoss JIRA] (JBDS-2364) Cannot resolve org.eclipse.m2e.jdt when installing build-helper-maven-plugin
by Rastislav Wagner (JIRA)
[ https://issues.jboss.org/browse/JBDS-2364?page=com.atlassian.jira.plugin.... ]
Rastislav Wagner closed JBDS-2364.
----------------------------------
Closing.
> Cannot resolve org.eclipse.m2e.jdt when installing build-helper-maven-plugin
> ----------------------------------------------------------------------------
>
> Key: JBDS-2364
> URL: https://issues.jboss.org/browse/JBDS-2364
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: installer, maven, updatesite
> Affects Versions: 5.0.0.GA, 5.0.1.GA
> Reporter: Martin Malina
> Assignee: Nick Boldt
> Fix For: 5.0.2.GA
>
> Attachments: install-error.png
>
>
> Steps to reproduce:
> 1. Clone git://github.com/jbossas/jboss-as.git somewhere
> 2. File -> Import -> Existing maven project
> 3. Select <jboss_git_checkout>/cmp/pom.xml and try to import
> 4. build-helper-maven-plugin will be required - try to have it resolved
> 5. build-helper-maven-plugin will fail on dependencies - cannot satisfy org.eclipse.m2e.jdt
> When you try to import for example the cmp project from as7 (git://github.com/jbossas/jboss-as.git) you will need to install build-helper-maven-plugin. But that will fail because of unsatisfied dependency for org.eclipse.m2e.jdt .
> The problem is that org.eclipse.m2e.jdt is available, but only in version 1.0.x whereas the required version is [1.1.0,2.0.0).
> This is the error message:
> {code}
> Cannot complete the install because one or more required items could not be found.
> Software being installed: m2e connector for build-helper-maven-plugin 0.15.0.201207090124 (org.sonatype.m2e.buildhelper.feature.feature.group 0.15.0.201207090124)
> Missing requirement: m2e connector for build-helper-maven-plugin 0.15.0.201207090124 (org.sonatype.m2e.buildhelper 0.15.0.201207090124) requires 'bundle org.eclipse.m2e.jdt [1.1.0,2.0.0)' but it could not be found
> Cannot satisfy dependency:
> From: m2e connector for build-helper-maven-plugin 0.15.0.201207090124 (org.sonatype.m2e.buildhelper.feature.feature.group 0.15.0.201207090124)
> To: org.sonatype.m2e.buildhelper [0.15.0.201207090124]
> {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
13 years, 2 months
[JBoss JIRA] (JBIDE-13361) Update version of GWT archetype in JBT 3 / JBDS 5 Central
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13361?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-13361.
---------------------------------
Closing, not a real issue.
> Update version of GWT archetype in JBT 3 / JBDS 5 Central
> ---------------------------------------------------------
>
> Key: JBIDE-13361
> URL: https://issues.jboss.org/browse/JBIDE-13361
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, maven
> Affects Versions: 3.3.2
> Environment: JBDS 5.0.2.CR2 H238
> Reporter: Martin Malina
> Assignee: Snjezana Peco
> Fix For: 3.3.2
>
>
> I started testing JBDS 5.0.2 and found out I cannot run mvn package on the GWT project from JBoss Central.
> I thought it was using the same mechanism as JBDS 6, but apparently not. And the archetype version is set to org.jboss.errai.archetypes:jboss-errai-kitchensink-archetype:2.0.0.Final while the current version in JBDs 6 is 2.1.1.Final. Can we update it?
> The 2.0.0.Final gives this error when trying to run Maven Build... clean package:
> {code}
> [INFO] [ERROR] Errors in '/Users/rasp/jbossqa/JBDS/5.0.2/workspace-eap-238/gwt-kitchensink/target/.generated/org/jboss/tools/gwt/kitchensink/client/shared/_MemberValidatorImpl.java'
> [INFO] [ERROR] Line 430: The method validate(GwtValidationContext<T>, Set<ConstraintViolation<T>>, Member, V, ConstraintValidator<A,? super V>, ConstraintDescriptorImpl<A>, Class<?>[]) in the type AbstractGwtSpecificValidator<Member> is not applicable for the arguments (GwtValidationContext<T>, Set<ConstraintViolation<T>>, Member, String, SizeValidatorForMap, ConstraintDescriptorImpl<Size>, Class<?>[])
> [INFO] [ERROR] Line 452: The method validate(GwtValidationContext<T>, Set<ConstraintViolation<T>>, Member, V, ConstraintValidator<A,? super V>, ConstraintDescriptorImpl<A>, Class<?>[]) in the type AbstractGwtSpecificValidator<Member> is not applicable for the arguments (GwtValidationContext<T>, Set<ConstraintViolation<T>>, Member, String, SizeValidatorForMap, ConstraintDescriptorImpl<Size>, Class<?>[])
> [INFO] [ERROR] Line 477: The method validate(GwtValidationContext<T>, Set<ConstraintViolation<T>>, Member, V, ConstraintValidator<A,? super V>, ConstraintDescriptorImpl<A>, Class<?>[]) in the type AbstractGwtSpecificValidator<Member> is not applicable for the arguments (GwtValidationContext<T>, Set<ConstraintViolation<T>>, Member, String, SizeValidatorForMap, ConstraintDescriptorImpl<Size>, Class<?>[])
> [INFO] [ERROR] Cannot proceed due to previous errors
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 33.994s
> [INFO] Finished at: Wed Jan 09 15:11:42 CET 2013
> [INFO] Final Memory: 27M/205M
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal org.codehaus.mojo:gwt-maven-plugin:2.4.0:compile (default) on project gwt-kitchensink: Command [[
> [ERROR] /bin/sh -c /Library/Java/JavaVirtualMachines/jdk1.7.0_07.jdk/Contents/Home/jre/bin/java -Xmx512m -classpath /Users/rasp/jbossqa/JBDS/5.0.2/workspace-eap-238/gwt-kitchensink/src/main/java:/Users/rasp/jbossqa/JBDS/5.0.2/workspace-eap-238/gwt-kitchensink/src/main/resources:/Users/rasp/jbossqa/JBDS/5.0.2/workspace-eap-238/gwt-kitchensink/target/classes:/Users/rasp/.m2/repository/javax/enterprise/cdi-api/1.0-SP4/cdi-api-1.0-SP4.jar:/Users/rasp/.m2/repository/org/jboss/spec/javax/interceptor/jboss-interceptors-api_1.1_spec/1.0.1.Final/jboss-interceptors-api_1.1_spec-1.0.1.Final.jar:/Users/rasp/.m2/repository/javax/inject/javax.inject/1/javax.inject-1.jar:/Users/rasp/.m2/repository/org/jboss/spec/javax/transaction/jboss-transaction-api_1.1_spec/1.0.1.Final/jboss-transaction-api_1.1_spec-1.0.1.Final.jar:/Users/rasp/.m2/repository/org/jboss/spec/javax/annotation/jboss-annotations-api_1.1_spec/1.0.1.Final/jboss-annotations-api_1.1_spec-1.0.1.Final.jar:/Users/rasp/.m2/repository/org/jboss/spec/javax/ws/rs/jboss-jaxrs-api_1.1_spec/1.0.0.Final/jboss-jaxrs-api_1.1_spec-1.0.0.Final.jar:/Users/rasp/.m2/repository/org/hibernate/javax/persistence/hibernate-jpa-2.0-api/1.0.1.Final/hibernate-jpa-2.0-api-1.0.1.Final.jar:/Users/rasp/.m2/repository/org/jboss/spec/javax/ejb/jboss-ejb-api_3.1_spec/1.0.2.Final/jboss-ejb-api_3.1_spec-1.0.2.Final.jar:/Users/rasp/.m2/repository/javax/validation/validation-api/1.0.0.GA/validation-api-1.0.0.GA.jar:/Users/rasp/.m2/repository/org/hibernate/hibernate-validator/4.2.0.Final/hibernate-validator-4.2.0.Final.jar:/Users/rasp/.m2/repository/org/hibernate/hibernate-validator/4.2.0.Final/hibernate-validator-4.2.0.Final-sources.jar:/Users/rasp/.m2/repository/javax/validation/validation-api/1.0.0.GA/validation-api-1.0.0.GA-sources.jar:/Users/rasp/.m2/repository/org/jboss/errai/errai-bus/2.0.0.Final/errai-bus-2.0.0.Final.jar:/Users/rasp/.m2/repository/org/jboss/errai/errai-common/2.0.0.Final/errai-common-2.0.0.Final.jar:/Users/rasp/.m2/repository/org/jboss/errai/reflections/reflections/2.0.0.Final/reflections-2.0.0.Final.jar:/Users/rasp/.m2/repository/com/google/guava/guava/10.0.1/guava-10.0.1.jar:/Users/rasp/.m2/repository/com/google/code/findbugs/jsr305/1.3.9/jsr305-1.3.9.jar:/Users/rasp/.m2/repository/dom4j/dom4j/1.6.1/dom4j-1.6.1.jar:/Users/rasp/.m2/repository/xml-apis/xml-apis/1.0.b2/xml-apis-1.0.b2.jar:/Users/rasp/.m2/repository/org/jboss/errai/errai-marshalling/2.0.0.Final/errai-marshalling-2.0.0.Final.jar:/Users/rasp/.m2/repository/com/google/inject/guice/3.0/guice-3.0.jar:/Users/rasp/.m2/repository/aopalliance/aopalliance/1.0/aopalliance-1.0.jar:/Users/rasp/.m2/repository/org/mvel/mvel2/2.1.Beta8/mvel2-2.1.Beta8.jar:/Users/rasp/.m2/repository/org/slf4j/slf4j-api/1.6.1/slf4j-api-1.6.1.jar:/Users/rasp/.m2/repository/org/slf4j/slf4j-log4j12/1.6.1/slf4j-log4j12-1.6.1.jar:/Users/rasp/.m2/repository/log4j/log4j/1.2.16/log4j-1.2.16.jar:/Users/rasp/.m2/repository/org/javassist/javassist/3.15.0-GA/javassist-3.15.0-GA.jar:/Users/rasp/.m2/repository/org/jboss/errai/io/netty/netty/4.0.0.Alpha1.errai.r1/netty-4.0.0.Alpha1.errai.r1.jar:/Users/rasp/.m2/repository/org/jboss/errai/errai-ioc/2.0.0.Final/errai-ioc-2.0.0.Final.jar:/Users/rasp/.m2/repository/org/jboss/errai/errai-codegen/2.0.0.Final/errai-codegen-2.0.0.Final.jar:/Users/rasp/.m2/repository/org/jboss/errai/errai-tools/2.0.0.Final/errai-tools-2.0.0.Final.jar:/Users/rasp/.m2/repository/hsqldb/hsqldb/1.8.0.7/hsqldb-1.8.0.7.jar:/Users/rasp/.m2/repository/org/jboss/errai/errai-cdi-client/2.0.0.Final/errai-cdi-client-2.0.0.Final.jar:/Users/rasp/.m2/repository/org/jboss/errai/errai-javax-enterprise/2.0.0.Final/errai-javax-enterprise-2.0.0.Final.jar:/Users/rasp/.m2/repository/org/jboss/errai/errai-weld-integration/2.0.0.Final/errai-weld-integration-2.0.0.Final.jar:/Users/rasp/.m2/repository/com/google/gwt/gwt-user/2.4.0/gwt-user-2.4.0.jar:/Users/rasp/.m2/repository/com/google/gwt/gwt-dev/2.4.0/gwt-dev-2.4.0.jar:/Users/rasp/.m2/repository/org/hibernate/hibernate-jpamodelgen/1.1.1.Final/hibernate-jpamodelgen-1.1.1.Final.jar:/Users/rasp/.m2/repository/com/google/gwt/gwt-user/2.4.0/gwt-user-2.4.0.jar:/Users/rasp/.m2/repository/javax/validation/validation-api/1.0.0.GA/validation-api-1.0.0.GA.jar:/Users/rasp/.m2/repository/javax/validation/validation-api/1.0.0.GA/validation-api-1.0.0.GA-sources.jar:/Users/rasp/.m2/repository/com/google/gwt/gwt-dev/2.4.0/gwt-dev-2.4.0.jar com.google.gwt.dev.Compiler -gen /Users/rasp/jbossqa/JBDS/5.0.2/workspace-eap-238/gwt-kitchensink/target/.generated -logLevel INFO -style OBF -war /Users/rasp/jbossqa/JBDS/5.0.2/workspace-eap-238/gwt-kitchensink/src/main/webapp -localWorkers 4 org.jboss.tools.gwt.kitchensink.KitchenSink
> [ERROR] ]] failed with status 1
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> {code}
> I tried doing this in JBDS 6 with the newer version and it worked for me. Then I removed my whole local maven repo and tried again in JBDS 5.0.2 and now it works. Something is wrong here - the idea of maven is that it should always get the right dependencies, no?
--
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
13 years, 2 months
[JBoss JIRA] (JBIDE-13139) Improve libs import for EAP 6
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13139?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-13139:
-------------------------------------
I will say this is related to JBIDE-12615, access restrictions when reading the jboss modules, but since that bug is stalled, it's hard to justify work on this one.
The question here is whether I'd like to add in, either as a dependent library or as raw source, the jboss-modules-poc project which deals with investigating jboss modules. If we can't make a decision on that, then this could be hard to do without that lib.
> Improve libs import for EAP 6
> -----------------------------
>
> Key: JBIDE-13139
> URL: https://issues.jboss.org/browse/JBIDE-13139
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: JBossAS/Servers
> Affects Versions: 3.3.0.Final
> Environment: JBDS 4.x
> EAP 6/AS 7
> Reporter: William Siqueira
> Assignee: Rob Stryker
> Fix For: 4.1.0.Alpha1
>
>
> In previous version of EAP, we could create a LIB and all our JARs files to the application build path, so we didn't have problem with imports. in EAP 6(AS 7), we have the modules new concept.
> The problem is that when migrating from older EAP version to EAP 6, we have to create modules to represent our libs and when setting a server to your project, it is not bringing our custom modules which our application is dependent.
> What is needed is a way to select which modules will be in the project classpath whn adding a server lib to the project or perhaps automatically import all modules based on the jboss-deployment-structure.xml descriptor.
--
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
13 years, 2 months