[JBoss JIRA] (JBIDE-12732) jboss-packaging-maven-plugin jboss-sar + m2e + JBT = NPE
by Manosh C (JIRA)
Manosh C created JBIDE-12732:
--------------------------------
Summary: jboss-packaging-maven-plugin jboss-sar + m2e + JBT = NPE
Key: JBIDE-12732
URL: https://issues.jboss.org/browse/JBIDE-12732
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: maven
Environment: Eclipse Helios, indigo and Juno
Reporter: Manosh C
Assignee: Fred Bricon
Not able to use maven SAR project inside eclipse (Tried Helios, indigo and even Juno with latest jboss tools dev build). In fact I have to close SAR project in order to add any other web/esb projects to JBoss EAP/ESB.
I am also attaching the maven code to recreate the issue. One thing I observed is maven jboss packaging m2e plugin is not generating the eclipse files correctly for SAR. Contents of the "org.eclipse.wst.common.component", in .setting folder, is missing an attribute 'handle'(in this case it should be handle="module:/resource/test-common/test-common"). With out the "handle" attribute, i could not open "deployment Assembly" page in properties (right click on sar project -> properties -> Deployment Assembly). Once I have the handle defined i could open Deployment Assembly page and SAR project shows up in the list to add to the server.
Here is the .settings/"org.eclipse.wst.common.component" file contents
<?xml version="1.0" encoding="UTF-8"?>
<project-modules id="moduleCoreId" project-version="1.5.0">
<wb-module deploy-name="test-sar">
<wb-resource deploy-path="/" source-path="/src/main/resources"/>
<wb-resource deploy-path="/" source-path="/src/main/java"/>
<wb-resource deploy-path="/" source-path="/src/test/java"/>
<dependent-module archiveName="test-common-1.0-SNAPSHOT.jar" deploy-path="/lib">
<dependency-type>uses</dependency-type>
</dependent-module>
<property name="java-output-path" value="target/classes"/>
</wb-module>
</project-modules>
Please let me know if you need any more details.
--
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, 3 months
[JBoss JIRA] (JBIDE-12527) Improve maven conversion of lib jars
by Fred Bricon (JIRA)
Fred Bricon created JBIDE-12527:
-----------------------------------
Summary: Improve maven conversion of lib jars
Key: JBIDE-12527
URL: https://issues.jboss.org/browse/JBIDE-12527
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: maven
Affects Versions: 4.0.0.Alpha1
Reporter: Fred Bricon
Assignee: Fred Bricon
Fix For: 4.0.0.Alpha2
As a follow up on JBIDE-8973, we should be able to also convert project dependencies that are not classpath entries.
Use case : convert an EAR project to maven. All the jars in <earproject>/lib/ and all jars referenced as virtual components in .settings/org.eclipse.wst.common.component should be identified and converted
--
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, 3 months
[JBoss JIRA] (JBIDE-12530) Warn the user about unresolvable dependencies during maven conversion
by Fred Bricon (JIRA)
Fred Bricon created JBIDE-12530:
-----------------------------------
Summary: Warn the user about unresolvable dependencies during maven conversion
Key: JBIDE-12530
URL: https://issues.jboss.org/browse/JBIDE-12530
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: maven
Affects Versions: 4.0.0.Alpha1
Reporter: Fred Bricon
Assignee: Fred Bricon
Fix For: 4.0.0.Alpha2
When identifying jars as maven dependencies, if dependencies are identified against some remote nexus repository, the maven dependency won't be resolvable if that repo was not added to the maven settings.xml
We should display a warning image in that case.
We could also provide a way to manage/add repositories from the conversion wizard.
--
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, 3 months
[JBoss JIRA] (JBIDE-12702) All groovy jars unidentified during project conversion
by Fred Bricon (JIRA)
Fred Bricon created JBIDE-12702:
-----------------------------------
Summary: All groovy jars unidentified during project conversion
Key: JBIDE-12702
URL: https://issues.jboss.org/browse/JBIDE-12702
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: maven
Affects Versions: 4.0.0.Alpha2
Reporter: Fred Bricon
Assignee: Fred Bricon
Fix For: 4.0.0.Beta1
- Create a dynamic web project
- Copy all jars from a groovy distro lib directory into <project>/WebContent/WEB-INF/lib
- Right click on project > Configure > Convert to Maven...
- Set GAV and packaging = war
- The identification wizard tries to identify all the jars
ASSERT : all jars are identified <- FAILS : all groovy jars are unidentified
--
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, 3 months
[JBoss JIRA] (JBIDE-12854) JBoss Developer Framework Quickstarts - > in requirements
by Rastislav Wagner (JIRA)
Rastislav Wagner created JBIDE-12854:
----------------------------------------
Summary: JBoss Developer Framework Quickstarts - > in requirements
Key: JBIDE-12854
URL: https://issues.jboss.org/browse/JBIDE-12854
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: project-examples
Affects Versions: 4.0.0.Beta1
Reporter: Rastislav Wagner
Assignee: Snjezana Peco
Fix For: 4.0.0.CR1
There's a typo in requirements for examples:
m2e >=1.1.
m2e-wtp >=0.16.0.
(shows > instead of >)
Affected examples are:
Hello World JSF
Hello World JMS
Hello World Errai
Hello World OSGi
under JBoss Developer Framework Quickstarts
--
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, 3 months
[JBoss JIRA] (JBIDE-12608) Replace local.* properties and profiles by Maven mirroring
by Mickael Istria (JIRA)
Mickael Istria created JBIDE-12608:
--------------------------------------
Summary: Replace local.* properties and profiles by Maven mirroring
Key: JBIDE-12608
URL: https://issues.jboss.org/browse/JBIDE-12608
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: Build/Releng
Affects Versions: 4.0.0.Alpha2
Reporter: Mickael Istria
Assignee: Mickael Istria
Fix For: 4.0.0.Beta1
Currently, we deal with optimization for Jenkins by multiple local.* properties and local.* profiles.
Those properties and profiles are just used in order to replace repository URL.
Maven has the concept of mirroring for that, and without adding a profile, we can tell Maven to consume another URL for a given repo. Moreover, Tycho will support mirrors for repo in .target files starting from 0.16.0.
WE should move to the mirror approach since it keeps things clear and separate issues: pom describe build, mirror allow to override repo without any change.
Seems like Maven supports having 2 settings.xml files as input (one with -gs and one with -s), so no big difficulty 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, 3 months
[JBoss JIRA] (JBIDE-12575) Problem with CDI validator
by Jaroslav Jankovič (JIRA)
Jaroslav Jankovič created JBIDE-12575:
-----------------------------------------
Summary: Problem with CDI validator
Key: JBIDE-12575
URL: https://issues.jboss.org/browse/JBIDE-12575
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: CDI
Affects Versions: 4.0.0.Alpha1
Reporter: Jaroslav Jankovič
Assignee: Alexey Kazakov
Fix For: 4.0.0.Alpha1
There is a problem to force CDI validator to work. In my case, I created simple dynamic web project without CDI support, added some bean with Multiple beans eligible case (message not present yet). Add CDI support into project. Expected validation messages won't appear - cleaning the project doesn't help either.
--
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, 3 months